Communication method and device

Abstract

A communication method and apparatus, the method comprising: a first device determines information on a service flow arrival time, the service flow arrival time information comprising the service flow arrival time or the offset of the service flow arrival time relative to a reference time, the service flow arrival time being the time when the first service flow arrives at the second device, and the first service flow being a periodic service flow to be transmitted between an access network device and a user plane network element. The first device determines information on a service flow sending time based on the service flow arrival time information, and the first device instructs the second device to wait until the service flow sending time to send the first service flow after receiving the first service flow. If the first service flow is an uplink service flow, the second device is the access network device or a converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is the user plane network element. The above method can be used to meet the deterministic delay requirements of the first service flow and improve the overall performance of the network.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of wireless communications, and in particular to a communication method and apparatus. Background Art

[0002] During packet forwarding on traditional Ethernet networks, when a large number of data packets arrive at the forwarding port in an instant, it can cause long forwarding delays or packet loss. Therefore, traditional Ethernet cannot provide high reliability and guaranteed transmission delay services, and cannot meet the needs of automotive control, industrial Internet and other fields.

[0003] To meet the demand for reliable time-delay transmission, the Institute of Electrical and Electronics Engineers (IEEE) has defined the Time Sensitive Networking (TSN) standard. This standard can provide reliable time-delay transmission services based on Layer 2 switching, ensuring the reliability of data transmission for delay-sensitive services and predictable end-to-end transmission delay.

[0004] like Figure 1 As shown in the figure, the TSN system can include a centralized network configuration (CNC) network element, a centralized user configuration (CUC) network element, a TSN terminal (end station) and each switching node (TSN Bridge). The TSN terminal includes a transmitter (talker) and a receiver (listener).

[0005] The 5G system (5GS) as a whole can be used as a switching node, and the CNC network element can configure each switching node based on the information reported by the 5GS and other switching nodes to ensure deterministic end-to-end latency (from TSN talker to TSN listener). Figure 2As shown in the figure, a 5G system 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 referred to as the network side TT (NW-TT), the next generation NodeB (gNB); a user equipment (UE), and a TT on the UE side (hereinafter referred to as the device side TT (DS-TT). Taking the downlink data packet as an example, the data packet is transmitted from the TSN system to the NW-TT, and the NW-TT sends the data packet to the DS-TT through the UPF network element, gNB and UE.

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

[0007] In a first aspect, the present application provides a communication method, the method comprising:

[0008] The first device determines information about a service flow arrival time, where the information about the service flow arrival time includes the service flow arrival time or the offset of the service flow arrival time relative to a reference time. 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 to be transmitted between an access network device and a user plane network element. The first device determines information about a service flow sending time based on the information about the service flow arrival time. The first device instructs the second device to wait until the service flow sending time to send the first service flow after receiving the first service flow. If the first service flow is an uplink service flow, the second device is the access network device or a converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is a user plane network element.

[0009] Using the above method, the first device first determines the information of the service flow arrival time, and determines the service flow sending time information based on the service flow arrival time information, so that after receiving the first service flow, the second device can wait until the service flow sending time to send the first service flow. In other words, the first device will configure the time for the second device to send the first service flow, and the second device will wait until the specified service flow sending time to send the first service flow according to the configuration and instructions of the first device. Through the coordinated configuration of the first device, even if the second device receives multiple service flows at the same time or within a certain time period, congestion will not occur, thereby meeting the deterministic delay requirements of each flow, thereby improving the overall performance of the network.

[0010] In one possible design, after the first device instructs the second device to receive the first service flow, while waiting until the service flow sending time to send the first service flow, the first device sends information about the service flow sending time to the second device.

[0011] In one possible design, the information of the service flow sending time includes the service flow sending time or the offset of the service flow sending time relative to the reference time; the service flow sending time is no later than the latest sending time, and the latest sending time is determined based on the information of the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the latest sending time is determined based on the information of the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache length of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time does not exceed the maximum offset, and the maximum offset is determined based on the information of the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the maximum offset is determined based on the information of the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache length of the first service flow on the second device.

[0012] With the above design, the service flow sending time is no later than the latest sending time, or the offset of the service flow sending time relative to the reference time does not exceed the maximum offset, so that the second device sending the first service flow can meet the delay requirement of the first service flow.

[0013] In one possible design, the service flow sending time is no earlier than or later than the earliest sending time, and the earliest sending time is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time is greater than or equal to the minimum offset, and the minimum offset is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device.

[0014] In one possible design, the parameters used to determine the latest sending time or the maximum offset or the earliest sending time or the minimum offset also include a jitter delay associated with the first service flow.

[0015] In one possible design, the service flow sending time of the second service flow sent by the second device determined by the first device is different from the service flow sending time of the first service flow sent by the second device determined by the first device. The second service flow is a periodic service flow to be transmitted between the access network device and the user plane network element. The second service flow arrives at the second device at the same time as the first service flow, or the difference between the time when the second service flow arrives at the second device and the time when the first service flow arrives at the second device is less than or equal to a threshold.

[0016] By adopting the above design, the first device can avoid congestion of the first business flow and the second business flow by determining different business flow sending times for the first business flow and the second business flow, and ensure the deterministic delay requirements of the first business flow and the second business flow respectively.

[0017] In one possible design, when the first device determines information about the service flow sending 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 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 sending time relative to the reference time and less than or equal to the offset of the latest sending time relative to the reference time. The first device determines information about the service flow sending time based on the offset selection value.

[0018] Using the above design, the first device first determines the minimum offset and the maximum offset, or the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time, and then obtains the offset selection value, and determines the information of the service flow sending time based on the offset selection value.

[0019] In one possible design, when the first device obtains the offset selection value, the first device sends the minimum offset and the maximum offset, or the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time to the fourth device, and the first device receives the offset selection value from the fourth device.

[0020] In one possible design, when the first device obtains the offset selection value, the first device determines the delay requirement for the transmission of the first service flow between the second device and the third device based on the packet delay budget for the transmission of the first service flow between the second device and the third device, the processing time of the first service flow on the second device, and the processing time of the first service flow on the third device, and the first device sends the delay requirement to the fourth device. The third device is the device to receive the first service flow; if the first service flow is an uplink service flow, the third device is the user plane network element; if the first service flow is a downlink service flow, the third device is the access network device or a converter corresponding to the access network device;

[0021] With the above design, the fourth device can determine the selected offset value based on the above latency requirements. Furthermore, the first device sends the priority of the first service flow to the fourth device. It is understood that the fourth device can refer to multiple parameters when determining the selected offset value, and this application does not limit how the fourth device determines the selected offset value.

[0022] In one possible design, when the first device determines the information of the service flow sending time based on the offset selection value, the first device determines the information of the service flow sending time based on the offset selection value and the jitter delay associated with the first service flow.

[0023] In one possible design, the information about the service flow transmission time includes a gating scheduling parameter. The first device may determine the gating scheduling parameter using the following method: the first device obtains a period 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 gating scheduling parameter based on the period of the first service flow, the maximum frame size of the first service flow, and the offset selection value.

[0024] With the above design, the first device can determine the gating scheduling parameters based on the period of the first service flow, the maximum burst size of the first service flow, and the offset selection value. The gating scheduling parameters here are gating scheduling parameters for the second device.

[0025] In one possible design, when the first service flow is an uplink service flow, the first service flow reaches the second device through the terminal device; when the first device determines the information of the service flow arrival time, the first device obtains the information of the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget of the first service flow transmitted between the terminal device and the second device; the first device determines the information of the service flow arrival time based on the information of the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget of the first service flow transmitted between the terminal device and the second device.

[0026] With the above design, the first device can determine information about the service flow arrival time in a scenario where the first service flow is an uplink service flow.

[0027] In one possible design, the first device is a delay-sensitive network TSN application function network element; when the first device obtains information about the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first service flow between the terminal device and the second device, the first device determines information about the time when the first service flow arrives at the converter on the terminal device side, and the first device receives the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first service flow between the terminal device and the second device from the session management network element.

[0028] In one possible design, the first device is a session management network element; when the first device obtains information about the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first service flow between the terminal device and the second device, the first device receives information about the time when the first service flow arrives at the converter on the terminal device side from the policy control network element, the first device receives the residence time of the first service flow in the terminal device and in the converter on the terminal device side from the terminal device, and the first device determines the packet delay budget for transmission of the first service flow between the terminal device and the second device.

[0029] In the second aspect, the present application provides a communication method, which includes: a second device receives 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; the second device receives information about the service flow sending time from the first device; the second device waits until the service flow sending time indicated by the information about the service flow sending time to send 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 converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is the user plane network element.

[0030] Using the above method, after the second device receives the first service flow at the service flow arrival time, it waits until the service flow sending time indicated by the first device to send the first service flow. Therefore, the second device can send the first service flow according to the service flow sending time indicated by the first device. In other words, the first device will configure the time for the second device to send the first service flow, and the second device will wait until the specified service flow sending time to send the first service flow according to the configuration and instructions of the first device. Through the coordinated configuration of the first device, even if the second device receives multiple service flows at the same time or within a certain time period, congestion will not occur, thereby meeting the deterministic delay requirements of each flow, thereby improving the overall performance of the network.

[0031] In one possible design, the service flow sending time of the second device sending the second service flow is different from the service flow sending time of the second device sending the first service flow, the second service flow is a periodic service flow to be transmitted between the access network device and the user plane network element, the second service flow arrives at the second device at the same time as the first service flow, or the difference between the time when the second service flow arrives at the second device and the time when the first service flow arrives at the second device is less than or equal to a threshold.

[0032] In one possible design, the information on the service flow sending time includes the service flow sending time or the offset of the service flow sending time relative to a reference time; wherein, the service flow sending time is no later than the latest sending time, and the latest sending time is determined based on the information on the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the latest sending time is determined based on the information on the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache duration of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time does not exceed the maximum offset, and the maximum offset is determined based on the information on the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the maximum offset is determined based on the information on the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache duration of the first service flow on the second device.

[0033] In one possible design, the service flow sending time is not earlier than the earliest sending time, and the earliest sending time is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time is greater than or equal to the minimum offset, and the minimum offset is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device.

[0034] In one possible design, the parameters used to determine the latest sending time or the maximum offset or the earliest sending time or the minimum offset also include a jitter delay associated with the first service flow.

[0035] In one possible design, the information on the service flow sending time includes gating scheduling parameters.

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

[0037] In a third aspect, the present application provides a communication device, which is a first device or a device having the functions of a first device, and includes:

[0038] A processing unit is configured to determine information about a service flow arrival time, the information about the service flow arrival time including the service flow arrival time or the offset of the service flow arrival time relative to a reference time, the service flow arrival time being the time when a first service flow arrives at a second device, wherein the first service flow is a periodic service flow to be transmitted between an access network device and a user plane network element; the processing unit is configured to determine information about a service flow sending time based on the information about the service flow arrival time; and the transceiver unit is configured to instruct the second device to wait until the service flow sending time to send the first service flow after receiving the first service flow. If the first service flow is an uplink service flow, the second device is an access network device or a converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is a user plane network element.

[0039] In one possible design, the transceiver unit is used to send information about the service flow sending time to the second device after instructing the second device to receive the first service flow and wait until the service flow sending time to send the first service flow.

[0040] In one possible design, the information of the service flow sending time includes the service flow sending time or the offset of the service flow sending time relative to the reference time; the service flow sending time is no later than the latest sending time, and the latest sending time is determined based on the information of the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the latest sending time is determined based on the information of the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache length of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time does not exceed the maximum offset, and the maximum offset is determined based on the information of the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the maximum offset is determined based on the information of the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache length of the first service flow on the second device.

[0041] In one possible design, the service flow sending time is not earlier than the earliest sending time, and the earliest sending time is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time is greater than or equal to the minimum offset, and the minimum offset is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device.

[0042] In one possible design, the parameters used to determine the latest sending time or the maximum offset or the earliest sending time or the minimum offset also include a jitter delay associated with the first service flow.

[0043] In one possible design, the service flow sending time of the second service flow sent by the second device determined by the first device is different from the service flow sending time of the first service flow sent by the second device determined by the first device. The second service flow is a periodic service flow to be transmitted between the access network device and the user plane network element. The second service flow arrives at the second device at the same time as the first service flow, or the difference between the time when the second service flow arrives at the second device and the time when the first service flow arrives at the second device is less than or equal to a threshold.

[0044] In one possible design, the processing unit is used to obtain an offset selection value when determining the information of the service flow sending time based on the information of the service flow arrival time, and 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 sending time relative to the reference time and less than or equal to the offset of the latest sending time relative to the reference time; determine the information of the service flow sending time based on the offset selection value.

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

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

[0047] In one possible design, the processing unit is used to determine the information of the service flow sending time based on the offset selection value and the jitter delay associated with the first service flow when determining the information of the service flow sending time based on the offset selection value.

[0048] In one possible design, the information on the service flow sending time includes gating scheduling parameters; the processing unit is used to obtain the period of the first service flow and the maximum burst size of the first service flow; determine the size of the maximum frame of the first service flow based on the maximum burst size of the first service flow; determine the gating scheduling parameters based on the period of the first service flow, the maximum frame size of the first service flow and the offset selection value.

[0049] In one possible design, when the first business flow is an uplink business flow, the first business flow reaches the second device through the terminal device; the processing unit is used to obtain information on the time when the first business flow arrives at the converter on the terminal device side, the residence time of the first business flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first business flow between the terminal device and the second device when determining the information on the arrival time of the business flow; determine the information on the arrival time of the business flow based on information on the time when the first business flow arrives at the converter on the terminal device side, the residence time of the first business flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first business flow between the terminal device and the second device.

[0050] In one possible design, the first device is a delay-sensitive network TSN application function network element; the processing unit is used to determine the information of the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first service flow between the terminal device and the second device when obtaining information of the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first service flow between the terminal device and the second device from the session management network element.

[0051] In one possible design, the first device is a session management network element; the transceiver unit is used to receive information about the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for the first service flow transmitted between the terminal device and the second device from the policy control network element, and receive the residence time of the first service flow in the terminal device and in the converter on the terminal device side from the terminal device; the processing unit is used to determine the packet delay budget for the transmission of the first service flow between the terminal device and the second device.

[0052] In a fourth aspect, the present application provides a communication device, which is a second device or a device having the functions of a second device, and the device includes: a transceiver unit for receiving 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 information about a service flow sending time from the first device; the processing unit for waiting for the service flow sending time indicated by the information about the service flow sending time to send the first service flow to the third device; wherein, if the first service flow is an uplink service flow, the second device is the access network device or a converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is the user plane network element.

[0053] In one possible design, the information on the service flow sending time includes the service flow sending time or the offset of the service flow sending time relative to a reference time; wherein, the service flow sending time is no later than the latest sending time, and the latest sending time is determined based on the information on the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the latest sending time is determined based on the information on the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache duration of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time does not exceed the maximum offset, and the maximum offset is determined based on the information on the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the maximum offset is determined based on the information on the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache duration of the first service flow on the second device.

[0054] In one possible design, the service flow sending time is not earlier than the earliest sending time, and the earliest sending time is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time is greater than or equal to the minimum offset, and the minimum offset is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device.

[0055] In one possible design, the parameters used to determine the latest sending time or the maximum offset or the earliest sending time or the minimum offset also include a jitter delay associated with the first service flow.

[0056] In one possible design, the service flow sending time of the second device sending the second service flow is different from the service flow sending time of the second device sending the first service flow. The second service flow is a periodic service flow to be transmitted by the second device between the access network device and the user plane network element. The second service flow arrives at the second device at the same time as the first service flow, or the difference between the time when the second service flow arrives at the second device and the time when the first service flow arrives at the second device is less than or equal to a threshold.

[0057] In one possible design, the information on the service flow sending time includes gating scheduling parameters.

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

[0059] In a fifth aspect, the present application further provides an apparatus. The apparatus can execute the above-mentioned method design. The apparatus can be a chip or circuit capable of executing the functions corresponding to the above-mentioned method, or a device including the chip or circuit.

[0060] In one possible implementation, the apparatus includes: a memory for storing computer-executable program code; and a processor coupled to the memory. The program code stored in the memory includes instructions that, when executed by the processor, cause the apparatus or a device equipped with the apparatus to perform any of the methods described above.

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

[0062] In one possible design, the device includes corresponding functional units for implementing the steps in the above method. The functions can be implemented by hardware or by hardware executing corresponding software implementations. The hardware or software includes one or more units corresponding to the above functions.

[0063] In a sixth aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program runs on a device, it executes the method in any one of the possible designs described above.

[0064] In a seventh aspect, the present application provides a computer program product, which includes a computer program. When the computer program runs on a device, it executes the method in any one of the possible designs described above.

[0065] In an eighth aspect, the present application provides a communication system, comprising a first device and a second device, wherein the first device is used to execute a method in any possible design in the above-mentioned first aspect, and the second device is used to execute a method in any possible design in the above-mentioned second aspect.

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

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

[0068] In one possible design, the system also includes a third device, which is a device to receive 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 converter corresponding to the access network device.

[0069] In a ninth aspect, the present application provides a communication system, comprising a second device and a third device, wherein the second device is configured to execute the method in any one of the possible designs of the second aspect. The third device is a device to receive the first service flow.

[0070] For example, if the first service flow is an uplink service flow, the second device is the access network device or a converter corresponding to the 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 the user plane network element. The third device is an access network device or a converter corresponding to the access network device. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] Figure 1 Schematic diagram of the fully centralized configuration model for the TSN system;

[0073] Figure 2 Schematic diagram of a forwarding path of a first service flow in a 5G system;

[0074] Figure 3 This is a schematic diagram of the evolved packet system architecture;

[0075] Figure 4A This is a system architecture diagram for interoperability between 3GPP networks and TSN systems;

[0076] Figure 4B This is a system architecture diagram for interoperability between 3GPP networks and non-TSN systems;

[0077] Figure 5 Schematic diagram of the long tail effect;

[0078] Figure 6A A schematic diagram of the architecture used in the embodiments of this application;

[0079] Figure 6B This is another schematic diagram of an architecture used in an embodiment of the present application;

[0080] Figure 7A This is another schematic diagram of an architecture used in the embodiments of the present application;

[0081] Figure 7B This is another schematic diagram of an architecture used in the embodiments of the present application;

[0082] Figure 8 This is a flowchart summarizing a communication method in an embodiment of the present application;

[0083] Figure 9 This is a schematic diagram of a forwarding path of a first service flow when the first service flow is an uplink service flow in an embodiment of the present application;

[0084] Figure 10 This is a schematic diagram of a forwarding path of a first service flow when the first service flow is a downlink service flow in an embodiment of the present application;

[0085] Figure 11 This is a schematic diagram of the gating state corresponding to the transmission queue in the embodiment of the present application;

[0086] Figure 12A Schematic diagram of the gate control state in the embodiment of the present application;

[0087] Figure 12B This is another schematic diagram of a gating state in an embodiment of the present application;

[0088] Figure 12C This is another schematic diagram of a gating state in an embodiment of the present application;

[0089] Figure 12D This is another schematic diagram of a gating state in an embodiment of the present application;

[0090] Figure 12E This is another schematic diagram of a gating state in an embodiment of the present application;

[0091] Figure 13 This is a transmission flow chart of the first service flow in an embodiment of the present application;

[0092] Figure 14 This is another transmission flow chart of the first service flow in an embodiment of the present application;

[0093] Figure 15 This is another transmission flow chart of the first service flow in an embodiment of the present application;

[0094] Figure 16 This is another transmission flow chart of the first service flow in an embodiment of the present application;

[0095] Figure 17 This is another schematic diagram of an architecture used in the embodiments of the present application;

[0096] Figure 18 is another transmission flow chart in an embodiment of the present application;

[0097] Figure 19 This is a schematic structural diagram of a device in an embodiment of the present application;

[0098] Figure 20 This is another structural schematic diagram of a device in an embodiment of the present application. DETAILED DESCRIPTION

[0099] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all of the embodiments. The terms "first", "second" and corresponding terminology labels in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, and this is merely a way of distinguishing objects of the same properties when describing the embodiments of the present application. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, so that a process, method, system, product or device that includes a series of units is not necessarily limited to those units, but may include other units that are not clearly listed or inherent to these processes, methods, products or devices.

[0100] In the description of this application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this application is merely a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of this application, "at least one" refers to one or more items, and "multiple items" refers to two or more items. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0101] The technical solutions provided in the embodiments of this application can be applied to various communication systems. For example, they can be applied to long-term evolution (LTE) systems or 5G systems, and can also be applied to other future-oriented new systems, such as programmable user plane systems, which are not specifically limited in the embodiments of this application. In addition, the term "system" and "network" can be used interchangeably.

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

[0103] The following combination Figure 3 A brief description of the devices involved in the embodiments of this application is given below:

[0104] The terminal device can be connected to the access network device to access the communication system. The terminal device can also be called a terminal, UE, mobile station, mobile terminal, etc. The terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in remote surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of this application do not limit the specific technology and specific device form adopted by the terminal device. Figure 3 As shown, the terminal device may be a UE.

[0105] The access network device can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a gNB, a base station in a future mobile communication system, or an access node in a WiFi system, etc.; it can also be a module or unit that completes part of the functions of a base station, for example, it can be a centralized unit (CU) or a distributed unit (DU). The embodiments of the present application do not limit the specific technology and specific device form adopted by the access network device. Figure 3 As shown, the access network device may be an NR-RAN device.

[0106] Access management network element: used for mobility management and access management, such as terminal device location update, terminal device registration network, terminal device switching, etc. The access management network element can be the mobility management entity (MME) function in the 4G mobile communication system or the AMF network element in the 5G mobile communication system. In future mobile communication systems such as 6G mobile communication systems, the access management network element can still be an AMF network element, or have other names, which is not limited in this application. Namf is a service-based interface provided by AMF. AMF can communicate with other network functions through Namf. Figure 3 As shown, the access management network element can be an AMF network element.

[0107] Session management network element: used for session management. For example, session establishment, modification, and release. The session management network element is also used to allocate Internet Protocol (IP) addresses to terminal devices, select UPFs that provide data packet forwarding functions, etc. In 5G mobile communication systems, the session management network element can be an SMF network element. In future mobile communication systems such as 6G mobile communication systems, the session management function network element can still be an SMF network element, or have other names, which is not limited in this application. Nsmf is a service-based interface provided by SMF. SMF can communicate with other network functions through Nsmf. Figure 3 As shown, the session management network element can be an SMF network element.

[0108] Policy control network element: used to provide policy rule information for access management network element or session management network element. For example, Quality of Service (QoS) policy, slice selection policy, etc. In 5G mobile communication system, policy control network element can be PCF network element. In future mobile communication system such as 6G mobile communication system, policy control function network element can still be PCF network element, or have other names, which is not limited in this application. Figure 3 As shown, the policy control network element may be a PCF network element.

[0109] Data management network element: used to store data of terminal devices, such as contract information, authentication / authorization information. In 5G mobile communication systems, data management network elements can be UDM network elements. In future mobile communication systems such as 6G mobile communication systems, data management network elements can still be UDM network elements, or have other names. This application does not limit this. Figure 3 As shown, the data management network element may be a UDM network element.

[0110] The data storage network element is responsible for storing structured data, including contract data and policy data, externally exposed structured data, and application-related data. In a 5G mobile communication system, this data storage network element can be a UDR network element.

[0111] In future communication systems such as 6G mobile communication systems, the data storage network element may still be a UDR network element, or may have other names, which is not limited in this application.

[0112] The authentication service function network element is mainly responsible for providing authentication functions and supporting authentication for 3GPP access and non-3GPP access. In the 5G mobile communication system, the authentication service function network element can be an authentication service function AUSF network element.

[0113] In future communication systems such as 6G mobile communication systems, the authentication service function network element can still be an AUSF network element, or it can have other names, which is not limited in this application.

[0114] The network open function network element mainly provides services that enable the 3GPP network to securely provide network service capabilities to third-party service provider application function network elements. In the 5G communication system, the network open function network element can be a NEF network element.

[0115] In future communication systems such as 6G mobile communication systems, the network open function network element can still be a NEF network element, or it can have other names, which is not limited in this application.

[0116] Application function network element: used to provide services to the 3GPP network, for example, to affect service routing, interact with the policy control network element for policy control, etc. In 5G communication, the application function network element can be an AF network element. In future communications such as 6G communication, the application function network element can still be an AF network element, or have other names, which is not limited in this application. Figure 3 As shown, the application function network element may be an AF network element.

[0117] User plane network element: used to process data packets of terminal devices, such as forwarding, billing, etc. In 5G communication, the user plane network element can be a UPF network element. In future communications such as 6G communication, the user plane network element can still be a UPF network element, or have other names, which is not limited in this application. Figure 3 As shown, the user plane network element can be a UPF network element.

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

[0119] Currently, the TSN system defines a fully centralized configuration model. Figure 1 The following is a schematic diagram of the fully centralized configuration model of the TSN system. Figure 1 A brief introduction to the functions of each device in the

[0120] TSN terminals include Talker and Listener, which are senders and receivers of service flows respectively.

[0121] 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 terminal according to the instructions of the CNC network element.

[0122] The CNC network element is used to determine the end-to-end (E2E) forwarding path of the service flow and configure the switching nodes on the forwarding path based on the topology of the TSN system user plane (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.

[0123] The switching node is used to send the capability information of the switching node to the CNC network element, determine the gating scheduling parameters based on the configuration information of the CNC network element, and schedule the forwarding service flow according to the gating scheduling parameters.

[0124] like Figure 4A The following diagram shows a system architecture diagram for interoperability between a 3GPP network and a TSN system. The 5G system (5GS) functions as a switching node. The TSN application function (AF) network element in the 5GS exchanges information with nodes in the TSN system.

[0125] It should be noted that the DS-TT may be located inside the UE or outside the UE; the NW-TT may be located inside the UPF. Taking the downlink data packet as an example, the DS-TT can determine the gating scheduling parameters based on the configuration information sent by the CNC network element, and send the data packet according to the gating scheduling parameters. In order to ensure that the data packet can be sent in time, the time when the data packet arrives at the DS-TT cannot be later than a certain moment to ensure that it can be sent out during the door opening process, where the door opening process refers to the duration range of the door state being open. If the data packet arrives at the DS-TT before the start time of the door state being open indicated by the gating scheduling parameters, it needs to be buffered at the DS-TT until it is sent when the door state is open; if the data packet arrives at the DS-TT after the start time of the door state being open indicated by the gating scheduling parameters, the DS-TT needs to complete the sending of the data packet before the door state is converted to the closed state. Similarly, the NW-TT can also determine the gating scheduling parameters based on the configuration information sent by the CNC network element, and send the data packet according to the gating scheduling parameters. For example, NW-TT can send the uplink service flow received through 5GS to the switching node that is the next hop adjacent to 5GS on the forwarding path, or NW-TT can be used to receive the downlink service flow from the switching node that is the previous hop adjacent to 5GS on the forwarding path and send it to 5GS.

[0126] like Figure 4B The following diagram shows a system architecture diagram for interoperability between a 3GPP network and a non-TSN system. For non-TSN scenarios, the Time Sensitive Communication and Time Synchronization Function (TSCTSF) network element supports clock synchronization services and enables time-sensitive communication (TSC) services in non-TSN scenarios. The TSCTSF network element in the 5GS exchanges information directly with the AF network element, or the TSCTSF exchanges information with the AF network element through the NEF.

[0127] like Figure 2As shown, in deterministic low-latency scenarios, such as certain industrial control scenarios, the end-to-end latency is required to be very low, for example, the latency between UE (or DS-TT) and UPF (or NW-TT) must be less than 2ms. The transmission between gNB and UPF adopts tunnel mode, that is, when a data packet of a service flow arrives at the egress port of gNB, UPF or the transmission node between gNB and UPF (for example, a switch), as long as there are idle transmission resources, the data packet does not need to wait and is sent directly. When data packets of several service flows arrive at the egress port of one of the above nodes at the same time (that is, micro-burst scenario), congestion may cause the data packet to have a long transmission delay between gNB and UPF, for example, more than 0.5ms, so that the end-to-end transmission delay cannot meet the service requirements, for example, more than 2ms, thereby affecting the achievement of end-to-end low latency. It is understandable that the forwarding path between gNB and UPF may also include at least one transmission node ( Figure 4A and Figure 4B Not shown in the figure), the transmission node may be a switch (such as Figure 2 as shown) or router, etc.

[0128] like Figure 5 As shown in the figure, in the microburst scenario, the delay distribution of data packets shows a long tail effect, such as Figure 5 As shown in the left figure, the maximum delay has no upper limit or the upper limit is a very large value, resulting in the end-to-end delay exceeding the transmission delay requirement of the service. In order to achieve low end-to-end delay, the delay of the data packet needs to be limited to a range, such as Figure 5 As shown in the right figure in , it is necessary to limit the delay jitter between gNB and UPF to a time range.

[0129] It should be noted that in the embodiments of the present application, data packets can also be referred to as messages, data messages, data frames, frames, etc. The following description will only take data packets as an example.

[0130] In one possible design, the embodiments of the present application may be applied to Figure 6A and Figure 6B The network architecture shown is used to achieve low transmission latency between gNB and UPF. Figure 6A The network architecture is suitable for TSN scenarios. Figure 6B The network architecture is suitable for non-TSN scenarios.

[0131] For example, Figure 6A As shown, Figure 6A There are two domains involved, where domain 1 uses Figure 4AIn the architecture shown, the user plane includes TSN terminals, 5GS and other switching nodes, CUC network elements, and CNC network elements are control plane network elements in the TSN system. TSN AF and CNC network elements exchange information. The dotted box in domain 1 constitutes domain 2, as shown in Figure 6A In the upper part (pointed by the arrow), domain 2 includes the gNB and UPF network elements in the 5GS, the switches between them, as well as the SMF network elements, CNC-TN network elements, TSN AF network elements, and PCF network elements. In domain 2, the user plane includes the gNB and UPF network elements in the 5GS, as well as the switches between them. The control plane includes the SMF network elements, CNC-TN network elements, TSN AF network elements, and PCF network elements.

[0132] In domain 2, a converter corresponding to the access network device is added on the gNB side. The converter corresponding to the access network device can be recorded as AN-TT (e.g. Figure 6A (as shown in the figure). AN-TT is used to implement deterministic transmission between the gNB and the UPF network element, and will be described in detail in conjunction with the following flowchart. The AN-TT can be located inside or outside the gNB. When the AN-TT is located inside the gNB, it can be understood as a functional module integrated within the gNB. Alternatively, when the AN-TT is located outside the gNB, it can be understood that the AN-TT and the gNB are two separately deployed devices. In this case, the AN-TT can be deployed between the gNB and the UE, or between the gNB and the UPF network element.

[0133] In addition, another converter corresponding to the UPF network element is added on the UPF network element side, and the converter is located inside the UPF network element. In other words, the UPF integrates two converter function modules, one of which is the aforementioned NW-TT, and the other converter can be recorded as the N3 interface converter, namely N3-TT (such as Figure 6A As shown in the figure, the newly added N3-TT is used to implement deterministic transmission between the gNB and the UPF, and will be described in detail in conjunction with the following flowchart. Alternatively, the functions of the existing NW-TT can be enhanced to have the functions of the above-mentioned N3-TT. In this way, a converter function module is retained within the UPF network element. In addition, if the path between the gNB and the UPF network element also includes an intermediate user plane network element (intermediate UPF, I-UPF), the newly added converter can be recorded as N9-TT. The following description only uses the newly added converter as N3-TT as an example.

[0134] In addition, the two newly added converters mentioned above may also have other names, which are not limited in this application.

[0135] pass Figure 6A The layout of the network architecture is such that in both domain 1 and domain 2, the user-plane devices transmitting the first service flow can meet the deterministic latency requirements of the first service flow.

[0136] exist Figure 6B The network architecture shown also includes two domains, where domain 1 uses Figure 4B In the architecture shown, the user plane includes the end station device, 5GS and other switching nodes, such as the switching nodes in the DN, and the control plane includes the various control plane network elements of the 5GS and the AF network elements. The dotted box in domain 1 constitutes domain 2, as shown in Figure 6B In the upper part pointed by the arrow, domain 2 includes the gNB and UPF network elements in 5GS and the switches between them, as well as SMF network elements, CNC-TN network elements, TSCTSF network elements, and PCF network elements. In domain 2, the user plane includes the gNB and UPF network elements in 5GS and the switches between them, and the control plane includes the SMF network elements, CNC-TN network elements, TSCTSF network elements, and PCF network elements. Similarly, in domain 2, AN-TT and N3-TT are newly added, see Figure 6A The description in , will not be repeated here. Figure 6B The layout of the network architecture is such that in domain 1 and domain 2, the user-side devices transmitting the first service flow can also meet the deterministic latency requirements of the first service flow.

[0137] exist Figure 6A and Figure 6B In the network architecture shown, the SMF in domain 2 is used to implement the functions of the subsequent first device. Figure 6A and Figure 6B In the network architecture shown, SMF is connected to CNC-TN, and information can be exchanged through the interface between SMF and CNC-TN.

[0138] In one possible design, the embodiments of the present application may be applied to Figure 7A and Figure 7B In the domain2 shown, it is used to achieve low transmission delay between gNB and UPF. Figure 7A The network architecture is suitable for TSN scenarios. Figure 7B The network architecture is suitable for non-TSN scenarios.

[0139] For example, Figure 7A As shown, domain 1 and domain 2 can refer to the above Figure 6A Related description in . Figure 6A The difference is that in Figure 7A In the example, the TSN AF network element in domain 2 can be used to implement the function of the first device in domain 2. Figure 7A In the network architecture shown, TSN AF is connected to CNC-TN, and information can be exchanged through the interface between TSN AF and CNC-TN.

[0140] For example, Figure 7B As shown, domain 1 and domain 2 can refer to the above Figure 6B Related description in . Figure 6B The difference is that in Figure 7B In the example, the TSCTSF network element can be used to implement the function of the first device in domain 2. Figure 7B In the network architecture shown, TSCTSF is connected to CNC-TN, and information can be exchanged through the interface between TSCTSF and CNC-TN.

[0141] It should be noted that for the above Figure 6A 、 Figure 6B 、 Figure 7A and Figure 7B The forwarding behavior of domains 1 and 2 on the user plane can be independent. Specifically, when controlling the forwarding behavior of the 5GS, the control plane of domain 1 treats the 5GS as a whole and disregards the transmission conditions within the 5GS, namely, between the UE and gNB, and between the gNB and UPF network elements. When controlling the forwarding behavior of the switching nodes in domain 2, the control plane of domain 2 treats the gNB and UPF network elements as the sender and receiver, respectively, when the first service flow is an uplink service flow. Alternatively, the AN-TT and N3-TT are treated as the sender and receiver, respectively, of the first service flow. When the first service flow is a downlink service flow, the UPF network element and gNB are treated as the sender and receiver, respectively, when the first service flow is a downlink service flow. Alternatively, the N3-TT and AN-TT are treated as the sender and receiver, respectively. The timing of data packet transmission by the sender is subject to the time when the 5GS node in domain 1 receives the data packet from the upstream switching node, but the specific transmission and forwarding behavior is not affected or controlled by domain 1.

[0142] This application provides a communication method that can achieve low transmission latency between gNB and UPF and improve the overall performance of the network. In this method, deterministic transmission is supported between gNB and UPF, so that data packets can reach gNB or UPF (or NW-TT) within a predetermined time window, that is, avoiding the previous Figure 5 The long tail effect shown in .

[0143] The above 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, for example, Figure 6A or Figure 6B or the first network element is a TSN application function network element, for example, Figure 7A Alternatively, the first device may be a network element having delay-sensitive communication and clock synchronization functions, for example, Figure 7B In the uplink case, the second device is an access network device or a converter corresponding to the access network device (for example, the above-mentioned AN-TT), and the third device is a user plane network element. Alternatively, in the downlink case, the second device is a user plane network element (for example, a UPF having the above-mentioned N3-TT function) and the third device is an access network device.

[0144] Optionally, the above method may also involve a fourth device. For example, the fourth device may be Figure 6A or Figure 6B or Figure 7A or Figure 7B CNC-transport network (TN) in the network, wherein CNC-TN can be a new network element having the function of a CNC network element, or CNC-TN is a functional module in the first device. This application does not limit this. For details, please refer to the following description of the fourth device.

[0145] It should be noted that, for the scenario where the first service flow is an uplink service flow (corresponding to the following scenario 1), the packet delay budget (PDB3) of the first service flow transmitted between the terminal device and the user-plane network element represents the upper limit of the delay experienced by the data packet of the first service flow from the time it is received by the terminal device to the time when the user-plane network element or NW-TT processes the data packet and sends it to the next-hop node.

[0146] When the second device is an access network device and the third device is a user plane network element, the converter corresponding to the access network device (i.e., the above-mentioned AN-TT) serves as a functional module inside the access network device. The packet delay budget (PDB1) of the first service flow transmitted between the terminal device and the access network device indicates the upper limit of the delay experienced by the data packet of the first service flow from the time it is received by the terminal device to the time it reaches the PDCP layer or SDAP layer of the access network device. The packet delay budget (PDB2) of the first service flow transmitted between the access network device and the user plane network element indicates the upper limit of the delay experienced by the data packet of the first service flow from the time it is sent from the PDCP layer or SDAP layer of the access network device to the time the user plane network element or NW-TT processes the data packet and sends it to the next hop node. PBD3 is equal to the sum of PDB1 and PDB2.

[0147] At this time, the packet delay budget of the first service flow transmitted between the second device and the third device corresponds to the above-mentioned PDB2.

[0148] When the second device is the converter corresponding to the access network device (i.e., the above-mentioned AN-TT), and the third device is the user-plane network element, AN-TT is a device independently deployed outside the access network device. The packet delay budget (PDB1') of the first service flow transmitted between the terminal device and the converter corresponding to the access network device (i.e., the above-mentioned AN-TT) indicates the upper limit of the delay experienced by the data packet of the first service flow from the time it is received by the terminal device to the time it reaches AN-TT. The packet delay budget (PDB2') of the first service flow transmitted between the converter corresponding to the access network device and the user-plane network element indicates the upper limit of the delay experienced by the data packet of the first service flow from the time it is received by AN-TT to the time the user-plane network element or NW-TT processes the data packet and sends it to the next hop node. PBD3 is equal to the sum of PDB1' and PDB2'.

[0149] At this time, the packet delay budget of the first service flow transmitted between the second device and the third device corresponds to the above-mentioned PDB2'.

[0150] Exemplarily, for the scenario where the first service flow is a downlink service flow (corresponding to the following scenario 2), the packet delay budget (PDB6) of the first service flow transmitted between the user plane network element and the terminal device represents the upper limit of the delay experienced by the message of the first service flow from the time it is received by the user plane network element or NW-TT from the previous hop switching node to the time it reaches the terminal device (for example, the application layer of the terminal device).

[0151] When the second device is a user plane network element and the third device is an access network device, the converter corresponding to the access network device (i.e., the aforementioned AN-TT) serves as a functional module within the access network device. The packet delay budget (PDB4) for the first service flow transmitted between the user plane network element and the access network device represents the upper limit of the delay experienced by the message of the first service flow from the time it is received by the user plane network element or NW-TT from the previous hop switching node to the time it is processed by the user plane general packet radio service (GPRS) tunneling protocol (GPRS Tunnel Protocol for the user plane, GTP-U) layer of the access network device; the packet delay budget (PDB5) for the first service flow transmitted between the access network device and the terminal device represents the upper limit of the delay experienced by the message of the first service flow from the time it is sent from the PDCP layer or SDAP layer of the access network device to the time it reaches the terminal device (e.g., the application layer of the terminal device). PBD6 is equal to the sum of PDB4 and PDB5.

[0152] At this time, the packet delay budget of the first service flow transmitted between the second device and the third device corresponds to the above-mentioned PDB4.

[0153] When the second device is a user-plane network element and the third device is a converter corresponding to the access network device (i.e., the above-mentioned AN-TT), the AN-TT is a device independently deployed outside the access network device. The packet delay budget (PDB4') of the first service flow transmitted between the user-plane network element and the converter corresponding to the access network device (i.e., the above-mentioned AN-TT) represents the upper limit of the delay experienced by the message of the first service flow from the time it is received by the user-plane network element or NW-TT to the time when the AN-TT processes the message; the packet delay budget (PDB5') of the first service flow transmitted between the converter corresponding to the access network device (i.e., the above-mentioned AN-TT) and the terminal device represents the upper limit of the delay experienced by the message of the first service flow from the time it is sent by the AN-TT to the time it reaches the terminal device (e.g., the application layer of the terminal device). PBD6 is equal to the sum of PDB4' and PDB5'.

[0154] At this time, the packet delay budget of the first service flow transmitted between the second device and the third device corresponds to the above-mentioned PDB4'.

[0155] The following will be combined Figure 8 The above-mentioned communication method is described. Figure 8 FIG1 shows a signaling interaction diagram of a communication method according to an embodiment of the present invention. Figure 8 As shown, the method includes:

[0156] Step 800: The first device determines information about a service flow arrival time, where the service flow arrival time is the time when the first service flow arrives at the second device, wherein the first service flow is a periodic service flow to be sent between the access network device and the user plane network element.

[0157] The information on the service flow arrival time may be the service flow arrival time itself, or may be the offset of the service flow arrival time relative to the reference time.

[0158] The first service flow may correspond to a TSN service flow, referred to as a TSN flow. For example, the first service flow may be from Figure 9 The first service flow may also be a TSN flow sent from the Talker to the Listener; the first service flow may also be an aggregated QoS flow, that is, multiple TSN flows with the same or similar characteristics are aggregated into one QoS flow. The forwarding path of the first service flow may be determined by the CNC network element in the TSN system. In one example, the switching node in the forwarding path of the first service flow includes a mobile communication system, such as a 4G system, a 5G system, a 6G system, etc., that is, the mobile communication system as a whole acts as a switching node, such as Figure 9 Switching node 2 is shown.

[0159] It is understandable that the first device can determine at least one of the service flow arrival time or the offset of the service flow arrival time relative to the reference time. In one possible implementation, the first device can first determine the offset of the service flow arrival time relative to the 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 can 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.

[0160] The following uses two scenarios as examples to illustrate a specific process of the first device determining the information about the arrival time of the service flow:

[0161] Scenario 1: When the first service flow is an uplink service flow, the second device is an access network device or a converter corresponding to the access network device, that is, the first service flow is an uplink service flow to be sent by the access network device to the user plane network element.

[0162] For example, the second device here is an access network device or a converter corresponding to the access network device, which can be understood as follows: if the converter corresponding to the access network device is deployed separately from the access network device, the second device can be the converter corresponding to the access network device. For example, the service flow arrival time can be the time when the first service flow arrives at the converter corresponding to the access network device (such as the above-mentioned AN-TT). If the converter corresponding to the access network device is a functional module inside the access network device, the second device can be an access network device that includes the converter function, that is, the second device can be the access network device. Accordingly, the service flow arrival time can be the time when the first service flow arrives at the access network device. For example, the service flow arrival time is the time when 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.

[0163] At this time, the 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. Optionally, at least one switch or router may be included between the access network device and the user plane network element on the forwarding path.

[0164] For example, Figure 9As shown, the 5G system serves as switching node 2, and the first service flow is an uplink service flow. The entire forwarding path for the first service flow is: Talker, switching node 1, switching node 2, switching node 3, Listener. The forwarding path for the first service flow in the 5G system (i.e., switching node 2) is: UE, gNB, UPF network element. Figure 9 There is no DS-TT and NW-TT mark, refer to Figure 2 The forwarding path of the first service flow in the 5G system can specifically be: DS-TT, UE, gNB, 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, i.e., AN-TT is a functional module of the gNB and is located inside the gNB), transmission node 1, transmission node 2, UPF network element (N3-TT, i.e., N3-TT is a functional module of the UPF and is located inside the UPF). Alternatively, the forwarding path of the first service flow from the gNB to the UPF network element is: gNB, AN-TT (AN-TT is deployed separately from the gNB), transmission node 1, transmission node 2, UPF network element (N3-TT). Figure 9 The following example uses AN-TT as a functional module of gNB located inside the gNB as an example.

[0165] In one implementation, the first device can obtain time information of the first service flow arriving at the converter on the terminal device side (e.g., DS-TT), the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget of the first service flow transmitted between the terminal device and the second device.

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

[0167] The residence time of the first service flow in the terminal device and in the converter on the terminal device side can be Figure 2 The residence time between DS-TT and UE is called UE-DS-TT Residence Time.

[0168] Furthermore, the first device can determine the service flow arrival time or the offset of the service flow arrival time relative to the reference time based on the time information of the first service flow arriving at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget of the first service flow transmitted between the terminal device and the second device.

[0169] For example:

[0170] T1 (uplink) = Burst Arrival Time1 + UE-DS-TT Residence time + PDB. Formula (1)

[0171] T1-offset (uplink)=Burst Arrival Time1*+UE-DS-TT Residence Time+PDB. Formula (2)

[0172] Among them, T1(uplink) represents the arrival time of the service flow in the uplink scenario, T1-offset(uplink) represents the offset of the arrival time of the service flow in the uplink scenario relative to the reference time, Burst Arrival Time1 represents the time when the first service flow arrives at DS-TT, and Burst Arrival Time1* represents the offset of the time when the first service flow arrives at DS-TT relative to the reference time. UE-DS-TT Residence Time represents the residence time of the first service flow in the terminal device and in the DS-TT, and PDB represents the packet delay budget for the first service flow transmitted between the terminal device and the second device, which can be the aforementioned PDB1 or PDB1'. Exemplarily, the residence time of each service flow in the terminal device and in the converter on the terminal device side can be the same or different.

[0173] It is understandable that when the first device is implemented by different devices, the first device obtains the above three parameters in different ways. The following uses Way 1 and Way 2 as examples to illustrate the specific process by which the first device can obtain the above three parameters:

[0174] Method 1: The first device is a session management network element (for example, Figure 6A or Figure 6B When the SMF network element is present, the first device may obtain the above three parameters in the following manner but not limited to the following manner.

[0175] Regarding the time information when the first service flow arrives at the converter on the terminal device side, the session management network element may determine the time information when the first service flow arrives at the converter on the terminal device side according to information obtained from the policy control network element.

[0176] For example, the time information when the first service flow arrives at the converter on the terminal device side specifically refers to the time information when the data packets in a certain period in the first service flow arrive at the converter on the terminal device side.

[0177] Exemplarily, the policy control network element sends parameters such as the burst arrival time information of the first service flow, the period of the first service flow, and the direction of the first service flow to the session management network element.

[0178] The burst arrival time information of the first service flow may be the time when the first data packet of the data burst of the first service flow arrives at the 5G system ingress port, or the duration of the time when the first data packet of the data burst of the first service flow arrives at the 5G system ingress port relative to the reference time or the offset relative to the reference time, wherein the reference time refers to the start time of a time domain (such as 00:00:00 on January 1, 1970). When the direction of the first service flow indicates that the first service flow is an uplink service flow, the 5G system ingress port here refers to the port of the converter on the terminal device side (for example, DS-TT), and the burst arrival time information of the first service flow at this time is the time information when the first data packet of the data burst of the first service flow arrives at the converter on the terminal device side.

[0179] In addition, the period of the first service flow can also be described as the time length between two adjacent burst start times of the first service flow.

[0180] In a possible implementation, the policy control network element can be derived from the TSN application function network element (such as Figure 6A TSN AF network elements as shown) or network elements with delay-sensitive communication and clock synchronization functions (such as Figure 6B The TSCTSF network element shown) obtains the burst arrival time information of the first service flow, the period of the first service flow, the direction of the first service flow and other parameters.

[0181] For example, for Figure 6A In the network architecture shown, the TSN AF network element serves as the control plane of the 5GS switching node. The TSN AF network element determines the above parameters based on the information obtained from the CNC network element and sends them to the policy control network element.

[0182] For example, for Figure 6B In the network architecture shown, the TSCTSF network element serves as the control plane of the 5GS switching node. The TSCTSF network element determines the above parameters based on the information obtained from the application function network element and sends them to the policy control network element.

[0183] Exemplarily, the policy control network element sends a policy control and charging (PCC) rule to the session management network element. The PCC rule includes burst arrival time information of the first service flow, the period 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 carries the burst arrival time information of the first service flow, the period of the first service flow, and the direction of the first service flow.

[0184] In addition, the PCC rule may also include service requirement description parameters. The service requirement description parameters are obtained by the policy control network element from the TSN application function network element or a network element with delay-sensitive communication and clock synchronization functions. The service requirement description parameters may include at least one of the following: maximum burst size, priority of the first service flow, delay requirement of the first service flow, maximum flow bitrate, etc.

[0185] After the session management network element receives the burst arrival time information of the first service flow, the period of the first service flow and the direction of the first service flow from the policy control network element, it can determine the time information of the data packets within a specific period in the first service flow arriving at the converter on the terminal device side based on these parameters, that is, the time information of the aforementioned first service flow arriving at the converter on the terminal device side.

[0186] That is, the Burst Arrival Time1 in the above formula (1) or the Burst Arrival Time1* in the above formula (2) can be determined in the above manner.

[0187] Regarding the residence time of the first service flow in the terminal device and in the converter 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 in the converter on the terminal device side from the terminal device.

[0188] Illustratively, during a protocol data unit (PDU) session establishment process, the session management network element may receive a PDU session establishment request message from a terminal device, where the PDU session establishment request message carries the residence time of the first service flow within the terminal device and within a converter on the terminal device side. Optionally, the PDU session establishment request message may also carry the media access control address (MAC) of the DS-TT port.

[0189] That is, the UE-DS-TTResidence time in the above formula (1) or the above formula (2) can be determined in the above manner.

[0190] With respect to the packet delay budget of the first service flow transmitted between the terminal device and the second device, the session management network element may determine the packet delay budget of the first service flow transmitted between the terminal device and the second device.

[0191] For example, the session management network element can determine PDB1 or PDB1' based on the 5G QoS Identifier (5QI) in the PCC rule. For example, if the session management network element has configured PDB2 or PDB2', it can also determine PDB3 based on the 5QI, and then calculate the difference between PDB3 and PDB2 to obtain PDB1. Alternatively, the difference between PDB3 and PDB2' can be calculated to obtain PDB1'. For details, please refer to the relevant content above.

[0192] That is, PDB1 and PDB1' can be determined by the above method. The following description will be made by taking the PDB as PDB1 as an example.

[0193] Method 2: The first device is a TSN application function network element (such as Figure 7A TSN AF network elements as shown) or network elements with delay-sensitive communication and clock synchronization functions (such as Figure 7B When the TSCTSF network element is used, the first device may obtain the above three parameters in the following manner but not limited to the following manner.

[0194] With respect to the time information when the first service flow arrives at the converter on the terminal device side, the first device may determine the time information when the first service flow arrives at the converter on the terminal device side.

[0195] For example, the time information when the first service flow arrives at the converter on the terminal device side specifically refers to the time information when the data packets in a certain period in the first service flow arrive at the converter on the terminal device side.

[0196] For example, when the first device is a TSN application function network element, the TSN application function network element also serves as the control plane of the 5GS switching node and determines parameters such as the burst arrival time information of the first service flow, the period of the first service flow, and the direction of the first service flow based on information obtained from the CNC network element. For another example, when the first device is a network element with delay-sensitive communication and clock synchronization functions, the network element with delay-sensitive communication and clock synchronization functions also serves as the control plane of the 5GS switching node and determines parameters such as the burst arrival time information of the first service flow, the period of the first service flow, and the direction of the first service flow based on information obtained from the application function network element.

[0197] The burst arrival time information of the first service flow may be the time when the first data packet of the data burst of the first service flow arrives at the 5G system ingress port, or the duration of the time when the first data packet of the data burst of the first service flow arrives at the 5G system ingress port relative to the reference time or the offset relative to the reference time, wherein the reference time refers to the start time of a time domain (such as 00:00:00 on January 1, 1970). When the direction of the first service flow indicates that the first service flow is an uplink service flow, the 5G system ingress port here refers to the port of the converter on the terminal device side (for example, DS-TT), and the burst arrival time information of the first service flow at this time is the time information when the first data packet of the data burst of the first service flow arrives at the converter on the terminal device side.

[0198] Regarding the residence time of the first service flow in the terminal device and in the converter on the terminal device side and the packet delay budget for the first service flow transmitted between the terminal device and the second device, referring to the above-mentioned method 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 in the converter on the terminal device side from the terminal device, and the session management network element can also determine the packet delay budget (i.e., PDB1 or PDB1') for the first service flow transmitted between the terminal device and the second device. Exemplarily, the first device can receive the above information directly from the session management network element, or receive the above information from the session management network element through other network elements (such as a policy control network element), or the session management network element stores the above information in a data storage 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 storage network element.

[0199] Scenario 2: When the first service flow is a downlink service flow, the second device is a user plane network element, that is, the first service flow is a downlink service flow to be sent by the user plane network element to the access network device.

[0200] At this time, the forwarding path of the first service flow in the mobile communication system is: user plane network element, access network device, terminal device. Optionally, at least one switch or router may be included between the user plane network element and the access network device.

[0201] For example, Figure 10 As shown, the 5G system serves as switching node 2, and the first service flow is a downlink service flow. The forwarding path for the first service flow is: Talker, switching node 1, switching node 2, switching node 3, Listener. The forwarding path for the first service flow in the 5G system (i.e., switching node 2) is: UPF network element, gNB, UE. Figure 10 There is no DS-TT and NW-TT mark, refer to Figure 2The forwarding path of the first service flow in the 5G system can specifically be: UPF (or NW-TT), gNB, UE, DS-TT. The forwarding path of the first service flow from the UPF network element to the gNB is: UPF network element (N3-TT, i.e., N3-TT is a functional module of the UPF and is located inside the UPF), transmission node 1, transmission node 2, gNB (AN-TT, i.e., AN-TT is a functional module of the gNB and is located inside 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), gNB. Figure 10 The following example uses AN-TT as a functional module of gNB located inside the gNB as an example.

[0202] In one implementation, the information on the service flow arrival time is the time information when the first service flow arrives at the user plane network element, or it can also be understood as the time information 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 on the service flow arrival time may include the time when the first service flow arrives at the user plane network element, or the offset of the time when the first service flow arrives at the user plane network element relative to the reference time. For example:

[0203] T1(downstream) = Burst Arrival Time2. Formula (3)

[0204] T1-offset (downstream)=Burst Arrival Time2*. Formula (4)

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

[0206] Similarly, when the first device is implemented by different devices, the manner in which the first device obtains the information about the arrival time of the service flow is also different. The following uses manner 3 and manner 4 as examples to illustrate a specific process in which the first device can obtain the information about the arrival time of the service flow:

[0207] Mode 3: The first device is a session management network element (for example, Figure 6A or Figure 6BWhen the SMF network element in the policy control network element is used, the first device can receive information about the arrival time of the service flow from the policy control network element.

[0208] Similar to method 1, the session management network element can obtain the time information of the first service flow arriving at the converter on the terminal device side from the policy control network element. The difference is that the burst arrival time information of the first service flow can be the time when the first data packet of the data burst of the first service flow arrives at the 5G system ingress port, or the time when the first data packet of the data burst of the first service flow arrives at the 5G system ingress port relative to the reference time or the offset relative to the reference time. When the direction of the first service flow indicates that the first service flow is a downlink service flow, the 5G system ingress port here refers to the port of NW-TT. At this time, the burst arrival time information of the first service flow is the time information of the first data packet of the data burst of the first service flow arriving at NW-TT.

[0209] Mode 4: When the first device is a TSN application function network element or a network element with delay-sensitive communication and clock synchronization functions, the first device can determine information about the arrival time of the service flow.

[0210] Similar to method 2, the first device can determine the time information when the first service flow arrives at the converter on the terminal device side. The difference is that the burst arrival time information of the first service flow can be the time when the first data packet of the data burst of the first service flow arrives at the 5G system ingress port, or the time when the first data packet of the data burst of the first service flow arrives at the 5G system ingress port relative to the reference time or the offset relative to the reference time. When the direction of the first service flow indicates that the first service flow is a downlink service flow, the 5G system ingress port here refers to the port of NW-TT. At this time, the burst arrival time information of the first service flow is the time information when the first data packet of the data burst of the first service flow arrives at NW-TT.

[0211] Step 810: The first device determines information about the service flow sending time based on information about the service flow arrival time.

[0212] For the first implementation method, the first device determines the earliest sending time and the latest sending time based on the service flow arrival time information. The earliest sending time can be understood as the earliest time when the second device sends the first service flow, and the latest sending time can be understood as the latest time when the second device sends the first service flow. Among them, the service flow sending time is not earlier than the earliest sending time, and the service flow sending time is not later than the latest sending time. The first device can determine a time that is not earlier than the earliest sending time and not later than the latest sending time as the service flow sending time. The service flow sending time can be understood as the time when the second device is recommended to send the service flow.

[0213] The earliest sending time is the sum of the service flow arrival time and the processing time of the first service flow on the second device.

[0214] For example, in a scenario where jitter is not considered:

[0215] T2 = T1 + processing time of the second device, formula (5-1)

[0216] Wherein, T2 represents the earliest sending time, and T1 represents the service flow arrival time, which can be T1 (uplink) obtained by the above formula (1) or T1 (downlink) obtained by the above formula (3).

[0217] For example, when the first service flow is an uplink service flow:

[0218] T2(up) = T1(up) + T AN , formula (5-2)

[0219] Among them, T AN It is the processing time of the first service flow in the access network device or AN-TT.

[0220] In addition, the first device may also omit the process of calculating T1 (uplink) and directly calculate T2 (uplink), then:

[0221] T2 (uplink) = Burst Arrival Time 1 + UE-DS-TT Residence time + PDB + T AN Formula (5-3)

[0222] For example, when the first service flow is a downlink service flow,

[0223] T2 (downlink) = T1 (downlink) + T UPF , formula (5-4)

[0224] Among them, T UPF It is the processing time of the first service flow in the user plane network element.

[0225] In addition, the first device may also omit the process of calculating T1 (downlink) and directly calculate T2 (downlink), then:

[0226] T2 (upward) = Burst Arrival Time2 + T UPF , formula (5-5)

[0227] In the scenario of jitter,

[0228] T2 = T1 + processing time of the second device + jitter, formula (6-1)

[0229] For example, when the first service flow is an uplink service flow,

[0230] T2(up) = T1(up) + T AN +Jitter, formula (6-2)

[0231] For example, when the first service flow is a downlink service flow,

[0232] T2 (downlink) = T1 (downlink) + T UPF +Jitter. Formula (6-3)

[0233] In addition, in a scenario where jitter is considered, the first device may also omit the process of calculating T1 and directly calculate T2, which will not be described in detail here.

[0234] The above-mentioned jitter represents the jitter delay associated with the first service flow, which is the transmission delay caused by the existence of a service flow with the same priority as the first service flow, and can be determined based on the size of the maximum frame of the service flow with the same priority as the first service flow.

[0235] For example, if a flow has no other flows with the same priority, the jitter value for that flow is 0. If a flow has other flows with the same priority, the jitter value for that flow is affected by the [MaxFrameSize] of all other flows with the same priority. [MaxFrameSize] refers to the time required to send the largest data packet in the service flow, or in other words, the maximum time it takes to send a frame for the service flow.

[0236] For example, streams J and K have the same priority. Based on stream J's [MaxFrameSize], the maximum time to send a frame of stream J is 120µs, while based on stream K's [MaxFrameSize], the maximum time to send a frame of stream K is 80µs. The jitter of stream K depends on the maximum time to send a frame of stream J. For example, the jitter of stream K is determined based on half the maximum time to send a frame of stream J, which is 60µs. It is understandable that because streams J and K have the same priority, they enter the same send queue. When streams J and K are simultaneously waiting to be sent in the same send queue, if stream J is sent first, stream K will have to wait for the maximum time, which is the maximum time to send a frame of stream J. If stream K is sent first, stream K will have to wait for the minimum time, which is 0. Therefore, based on probability, the jitter of stream K is defined here as half the maximum time to send a frame of stream J (120µs), which is 60µs. Similarly, the jitter of stream J is 40µs.

[0237] For another example, streams J, K, and G have the same priority. Based on stream J's [MaxFrameSize], the maximum time to send a frame of stream J is 120 us. Based on stream K's [MaxFrameSize], the maximum time to send a frame of stream K is 80 us. Based on stream G's [MaxFrameSize], the maximum time to send a frame of stream G is 100 us. Similarly, the jitter of stream J depends on the maximum time to send a frame of stream K and the maximum time to send a frame of stream G. For example, the jitter of stream J is determined by the sum of half the maximum time to send a frame of stream K and half the maximum time to send a frame of stream K, that is, the jitter of stream J is 90 us. Similarly, the jitter of stream K is 110 us, and the jitter of stream G is 100 us.

[0238] Furthermore, the processing time of the first service flow on the second device involved in the above formula can be understood as the time required for the second device to decapsulate the data packets of the first service flow after the data packets of the first service flow arrive at the second device, process the data packets of the first service flow, encapsulate the data packets of the first service flow, and transmit them to the egress port of the second device, where the egress port is the egress port corresponding to the second device transmitting the first service flow. That is, the processing time of the first service flow on the second device can be understood as the time from the second device receiving the data packets of the first service flow to the time the data packets arrive at the egress port of the second device and are ready to be transmitted. For example, assuming that the second device receives a data packet of the first service flow from the upstream node at time t1, and the data packet arrives at the egress port of the second device at time t2 after processing by the second device, waiting to be transmitted to the next device, then t2-t1 is the processing time of the first service flow on the second device. Here, time t1 corresponds to the arrival time of the above service flow, and time t2 corresponds to the earliest transmission time without considering jitter.

[0239] In one implementation, when the second device is a user-plane network element, t1 is the time it takes for a data packet of the first service flow to arrive at the ingress port of the NW-TT corresponding to the user-plane network element, and t2 is the time it takes for a data packet of the first service flow to arrive at the egress port of the user-plane network element or NW-TT. Exemplarily, when the forwarding path from the second device to the access network device does not include an I-UPF, t2 is the time it takes for a data packet of the first service flow to arrive at the egress port of N3-TT. The egress port here refers to the egress port destined for the access network device or AN-TT. Exemplarily, when the forwarding path from the second device to the access network device includes an I-UPF, t2 is the time it takes for a data packet of the first service flow to arrive at the egress port of N9-TT. The egress port here refers to the egress port destined for the I-UPF.

[0240] In another implementation, when the second device is an access network device, t1 is the time it takes for the data packet of the first service flow to reach the access network device through the air interface, for example, it may be the time it takes to reach the PDCP layer or SDAP layer of the access network device, and t2 is the time it takes for the data packet of the first service flow to arrive at the egress port after being processed by the access network device.

[0241] In another implementation, when the second device is a converter corresponding to the access network device, t1 is the time it takes for the data packet of the first service flow to reach the AN-TT outside the access network device after being transmitted through the air interface, and t2 is the time it takes for the data packet of the first service flow to reach the output port after being processed by the AN-TT.

[0242] Exemplarily, 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 on the second device according to the processing time information of the second device.

[0243] Among them, the processing time information of the second device may include 5QI and the processing time of the business flow corresponding to 5QI on the second device. Further, the first device can determine the processing time of the first business flow on the second device based on the 5QI of the first business flow and the processing time information of the second device.

[0244] Alternatively, the processing time information of the second device includes the data packet size range and the processing time of the business flow that meets the data packet size range on the second device. Furthermore, the first device can determine the data packet size range into which the data packet of the first business flow falls based on the size of the data packet of the first business flow, and determine the processing time of the first business flow on the second device based on the processing time information of the second device.

[0245] Alternatively, the processing time information of the second device includes the processing time of the business flow on the second device, that is, the processing time of all business flows on the second device takes the same time length, and then the second device determines the processing time of the business flow on the second device in the processing time information of the second device as the processing time of the first business flow on the second device.

[0246] The following describes an example of how the first device obtains the processing time information of the second device from the second device, combining the above scenarios 1 and 2:

[0247] Corresponding to the above scenario 1, when the converter corresponding to the access network device is a functional module within 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.

[0248] When the converter corresponding to the access network device is a standalone device located outside the access network device, the converter corresponding to the access network device can send the processing time information of the second device to the access network device. The first device can obtain the processing time information of the second device from the access network device, or the processing time information of the second device can be configured on the access network device. Alternatively, the first device can obtain the processing time information of the second device from the converter 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 converter corresponding to the access network device.

[0249] Exemplarily, 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, and the NG Setup Request message carries the 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, and the RAN Configuration Update message carries the processing time information of the second device; or, during the registration process of a certain terminal device (for example, the 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 during the PDU session establishment process. Alternatively, the processing time information of the second device may also be configured on the session management network element. Alternatively, during the session establishment process of a terminal device (for example, the session establishment request carries 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.

[0250] Corresponding to the above scenario 2, the first device can obtain the processing time information of the user plane network element from the user plane network element. Exemplarily, 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, requesting the processing time information of the user plane network element. Exemplarily, the request message can be an N4 session establishment message or an N4 session modification request message. The user plane network element can send a response message to the first device in response to the request message, with the response message carrying the processing time information of the user plane network element. Exemplarily, when the request message is an N4 session establishment message, the response message is a response message to the N4 session establishment message; when the request message is an N4 session modification request message, the response message is a response message to the N4 session modification message. Alternatively, the user plane network element can directly report the processing time information of the user plane network element to the session management network element, without the session management network element requesting the user plane network element for the processing time of the first service flow on the user plane network element. Alternatively, the processing time information of the user plane network element can be configured on the session management network element.

[0251] In addition, when the first device is a device other than the session management network element, the session management network element can send the processing time of the first service flow on the second device and the processing time information of the second device to the first device. The first device can receive the above information directly from the session management network element, or receive the above information from the session management network element through other network elements (such as policy control network elements), or the session management network element stores the above information in the data storage network element (for example, UDR network element) through the data management network element (for example, UDM network element), and the first device can obtain the above information from the data storage network element, or the processing time information of the second device can also be configured on the first device.

[0252] Through the above method, the earliest sending time can be determined. In addition, the service flow sending time is not later than the latest sending time.

[0253] The latest sending time may be determined by, but not limited to, the following method A, method B, or method C:

[0254] Method A: Since the first service flow is a periodic service flow, the data packet of the first service flow currently arriving at the second device needs to be sent before the data packet of the next period of the first service flow arrives at the second device, that is, the second device needs to send the data packet of the first service flow within the duration corresponding to the period of the first service flow after the service flow arrival time. Therefore, the latest time for the second device to send the data packet of the first service flow (that is, the latest sending time) needs to be earlier than the sum of the service flow arrival time and the period of the first service flow. Furthermore, in order to achieve that before the data packet of the next period of the first service flow arrives at the second device, the data packet of the first service flow currently arriving at the second device has been sent out, rather than being sent, based on the above discussion, the latest time for the second device to send the first service flow (that is, the latest sending time) can be equal to the difference between the sum of the service flow arrival time and the period of the first service flow and the duration corresponding to sending the largest data packet of the first service flow.

[0255] Exemplarily, the latest sending time is determined according to the service flow arrival time, the period of the first service flow, and the maximum frame size of the first service flow.

[0256] In the scenario where jitter is not considered,

[0257] T3 A =T1+Interval-[MaxFrameSize], formula (7-1)

[0258] Among them, T3 A represents the latest sending time determined according to method A, T1 represents the service flow arrival time, which can be T1 (uplink) obtained by the above formula (1) or T1 (downlink) obtained by the above formula (3). Interval represents the period of the first service flow, and [MaxFrameSize] represents the duration corresponding to the transmission of a data packet of size MaxFrameSize by the outbound port of the second device, that is, the duration corresponding to the transmission of the largest data packet of the first service flow.

[0259] The period of the first service flow can be determined by referring to the relevant contents in the above-mentioned methods 1 to 4, and the MaxFrameSize can be determined based on information obtained from the service requirement description parameters, wherein the 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 can include at least one of a preamble, an IEEE802.3 packet header, a priority or a virtual local area network identifier (Vlan Identifier, VID), a cyclic redundancy check (CRC), and an interframe gap.

[0260] In addition, the first device can also omit the process of calculating T1 (uplink) and directly calculate T3 A (upper row), then

[0261] T3 A (Upstream)=Burst Arrival Time1+UE-DS-TT Residence time+PDB+Interval-[MaxFrameSize]. Formula (7-2)

[0262] Similarly, the first device can also omit the process of calculating T1 (downlink) and directly calculate T3 A (Downward)

[0263] T3 A (Downstream)=Burst Arrival Time 2+Interval-[MaxFrameSize]. Formula (7-3)

[0264] Optionally, in scenarios where jitter is a concern,

[0265] T3 A =T1+Interval-[MaxFrameSize]-Jitter. Formula (8)

[0266] It can be understood that in the scenario where jitter is taken into account, the second device sends the data packet of the first service flow earlier than T1+Interval-[MaxFrameSize]-Jitter, so that when the data packet of the next cycle of the first service flow arrives at the second device, the data packet of the current cycle of the first service flow has been sent by the second device, rather than being sent. Therefore, Jitter is subtracted here.

[0267] Similarly, the first device may also omit the process of calculating T1, which will not be described here.

[0268] Method B: After the first business flow arrives at the second device, the second device needs to process the first business flow, and is limited by the maximum cache time of the first business flow in the second device. Therefore, the latest time that the second device sends the first business flow (i.e., the latest sending time) can be equal to the sum of the business flow arrival time and the processing time of the first business flow on the second device, and the maximum cache time of the first business flow on the second device.

[0269] Exemplarily, the latest sending time is determined based on the arrival time of the service flow, the processing time of the first service flow on the second device, and the maximum cache duration of the first service flow on the second device. The maximum cache duration of the first service flow on the second device refers to the maximum duration that the first service flow can be cached on the second device.

[0270] In the scenario where jitter is not considered,

[0271] T3 B =T1+T'+T * . Formula (9-1)

[0272] Among them, T3 B represents the latest sending time determined according to method B, T1 represents the arrival time of the service flow, which can be T1 (uplink) obtained by the above formula (1) or T1 (downlink) obtained by the above formula (3). T' represents the processing time of the first service flow on the second device. * Indicates the maximum buffering time of the first service flow on the second device.

[0273] In addition, the first device can also omit the process of calculating T1 (uplink) and directly calculate T3 B (upper row), then

[0274] T3 B (Uplink)=Burst Arrival Time1+UE-DS-TT Residence time+PDB+T'+T * . Formula (9-2)

[0275] The first device can also omit the process of calculating T1 (downlink) and directly calculate T3 B (Downlink):

[0276] T3 B (Downlink) = Burst Arrival Time 2 + T' + T * . Formula (9-3)

[0277] In the scenario of jitter,

[0278] T3 B =T1+T'+T * -Jitter. Formula (10-1)

[0279] It is understandable that, in the scenario where jitter is taken into consideration, the second device needs to be earlier than T1+T'+T * -Jitter sends out the data packets of the first service flow, 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.

[0280] Similarly, the first device may also omit the process of calculating T1, which will not be described here.

[0281] The processing time T' of the first service flow on the second device used to calculate the latest sending time using method (B) can be referred to the description of how to determine the processing time of the first service flow on the second device in determining the earliest sending time, which will not be repeated here.

[0282] A possible implementation method is to use method (B) to calculate the maximum buffering time T of the first service flow in the second device to be used for the latest sending time. * It is related to the cache capacity of the second device, or the maximum cache duration of the first service flow on the second device is related to the 5QI corresponding to the first service flow, or the maximum cache duration of the first service flow on the second device is related to the packet size range. Exemplarily, the first device obtains the maximum cache duration information of the second device and determines the maximum cache duration of the first service flow on the second device based on the maximum cache duration information of the second device. For example, when the first device is a session management network element, the maximum cache duration information includes at least one 5QI and the maximum cache duration of the service flow corresponding to each 5QI on the second device. The session management network element can further determine the maximum cache duration of the first service flow on the second device based on the 5QI of the first service flow. Alternatively, the maximum cache duration information includes a packet size range and the maximum cache duration of service flows that meet the packet size range on the second device. The session management network element can further determine the maximum cache duration of the first service flow on the second device based on the packet size of the first service flow. Alternatively, the maximum cache duration information includes the maximum cache duration of the service flow on the second device, i.e., all service flows have the same maximum cache duration on the second device. The session management network element may obtain the maximum cache duration information of the second device in the same manner as 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 and will not be repeated here.

[0283] In another possible implementation, the first device determines the maximum buffering time of the first service flow on the second device based on the processing time information of the second device, the processing time information of the third device, the packet delay budget of the first service flow transmitted between the second device and the third device, and the maximum transmission delay of the first service flow between the second device and the third device. * =Packet delay budget of the first service flow transmitted between the second device and the third device - processing time of the first service flow on the third device - processing time of the first service flow on the second device - maximum transmission delay of the first service flow between the second device and the third device.

[0284] Exemplarily, when the first device is a session management network element, the session management network element can determine the packet delay budget for transmission of the first business flow between the second device and the third device based on the 5QI corresponding to the first business flow, and determine the processing time of the first business flow on the second device according to the processing time information of the second device. The session management network element can also determine the maximum transmission delay of the first business flow between the second device and the third device, and further calculate the maximum cache time of the first business flow on the second device based on the above parameters.

[0285] For example, the packet delay budget for the first service flow transmitted between the second device and the third device can refer to the relevant descriptions of PDB2 (or PDB2') and PDB4 (or PDB4') in the above scenarios 1 and 2. For example, taking the first service flow as an uplink service flow as an example, if the delay requirement for the first service flow transmitted between the terminal device and the user plane network element is 2ms, the session management network element can determine that the packet delay budget (PDB3) transmitted between the terminal device and the user plane network element is 2ms, and the packet delay budget (PDB2) transmitted between the second device and the third device is 1ms.

[0286] The processing time of the first service flow on the second device can refer to the above related description.

[0287] The maximum transmission delay 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 is used to indicate the delay required for the first service flow to be transmitted between the second device and the third device. The maximum transmission delay of the first service flow between the second device and the third device refers to the time elapsed from the second device (access network device or AN-TT) sending the data packet of the first service flow to the third device (user plane network element or N3-TT or N9-TT) receiving the data packet of the first service flow when the second device and the third device and other transmission nodes between them forward the data packet of the first service flow based on the gated scheduling parameters under the control of the CNC-TN.

[0288] Among them, the maximum transmission delay of the first service flow between the second device and the third device can be pre-configured on the session management network element. For example, the maximum transmission delay between different access network devices (or converters corresponding to access network devices) and user plane network elements can be configured on the session management network element, or it can be based on different 5QI configurations, that is, for specific access network devices (or converters corresponding to access network devices) and user plane network elements, corresponding maximum transmission delays are pre-configured for different 5QIs, or a unified value of the maximum transmission delay can be configured, that is, the 5QIs corresponding to different services are not distinguished.

[0289] The processing time of the first business flow on the third device can be understood as the time required for the third device to encapsulate the first business flow and send it to the egress port of the third device after the data packet of the first business flow arrives at the third device, the third device decapsulates and processes the data packet of the first business flow, and the third device encapsulates the first business flow and sends it to the egress port of the third device, wherein the egress port is the egress port corresponding to the third device sending the first business flow to the next-hop device. That is, the processing time of the first business flow on the third device can be understood as the time from the third device receiving the data packet of the first business flow to the time the data packet arrives at the egress port of the third device and is ready to be sent. For example, assuming that the third device receives the data packet of the first business flow from the upstream node at time t3, the data packet arrives at the egress port of the third device at time t4 after being processed by the third device, and waits to be sent to the next-hop device, then t4-t3 is the processing time of the first business flow on the third device.

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

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

[0292] In another implementation, when the third device is a converter corresponding to the access network device, t3 is the time it takes for the data packet of the first service flow to arrive 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 it takes for the data packet of the first service flow to be processed by the AN-TT.

[0293] Exemplarily, 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 on the third device according to the processing time information of the third device.

[0294] Among them, the processing time information of the third device may include 5QI and the processing time of the business flow corresponding to 5QI on the third device. Further, the first device can determine the processing time of the first business flow on the third device based on the 5QI of the first business flow and the processing time information of the third device.

[0295] Alternatively, the processing time information of the third device includes the data packet size range and the processing time of the business flow that meets the data packet size range on the third device. Further, the first device can determine the data packet size range into which the data packet of the first business flow falls based on the size of the data packet of the first business flow, and determine the processing time of the first business flow on the third device based on the processing time information of the third device.

[0296] Alternatively, the processing time information of the third device includes the processing time of the business flow in the third device, that is, the processing time of all business flows in the third device is the same length of time, and then the third device determines the processing time of the business flow in the third device in the processing time information of the third device as the processing time of the first business flow in the third device.

[0297] 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 on the third device or the processing time information of the third device to the first device.

[0298] The following describes an example of how the first device obtains the processing time information of the third device from the third device, combining the above scenarios 1 and 2:

[0299] Corresponding to the above scenario 1, the first device can 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, and the repetitions will not be repeated.

[0300] Corresponding to the above scenario 2, the first device can obtain the processing time information of the access network device or the processing time information of the converter corresponding to the access network device. For details, please refer to the above related content, and the repetitions will not be repeated.

[0301] In addition, when the first device is a device other than the session management network element, the session management network element can send the processing time of the first service flow in the third device and the processing time information of the third device to the first device. The first device can receive the above information directly from the session management network element, or receive the above information from the session management network element through other network elements (such as policy control network elements), or the session management network element stores the above information in the data storage network element (for example, UDR network element) through the data management network element (for example, UDM network element), and the first device can obtain the above information from the data storage network element, or the processing time information of the third device can also be configured on the first device.

[0302] In addition, when the first device is a device other than a session management network element, the session management network element can send the maximum cache duration information of the second device or the maximum cache duration of the first service flow on the second device to the first device, or the maximum cache duration information of the second device can also be configured on the first device.

[0303] Through the above method, the first device can determine the maximum cache duration of the first service flow in the second device, and then determine the latest sending time according to the above formula (9-1), formula (9-2), formula (9-3) or formula (10-1).

[0304] In addition, it is also possible not to first determine the maximum buffering time T of the first service flow in the second device. * , but based on the maximum cache time T of the first service flow in the second device * The latest sending time can be directly determined by combining the above formula (9-1), formula (9-2), formula (9-3) or formula (10-1).

[0305] For example, in the scenario where jitter is not considered, combined with the above formula (9-1), we can know that:

[0306] T3 B = T1 + the packet delay budget for the first service flow transmitted between the second device and the third device - the processing time of the first service flow on the third device - the maximum transmission delay of the first service flow between the second device and the third device. Formula (9-4)

[0307] In the scenario of considering jitter, combined with the above formula (10-1),

[0308] T3 B =T1+packet delay budget of the first service flow transmitted between the second device and the third device-processing time of the first service flow on the third device-maximum transmission delay of the first service flow between the second device and the third device-Jitter.

[0309] Formula (10-2)

[0310] Method C: Based on Method A and Method B, the smaller value is selected as the latest sending time according to the latest sending time determined based on Method A and Method B. For example, T3 A and T3 B The smaller value in .

[0311] It should be noted that the above three methods of determining the latest sending time are only examples.

[0312] Therefore, the first device can determine the earliest sending time and the latest sending time by combining the above methods, and then the first device can determine a time that is no earlier than the earliest sending time and no later than the latest sending time as the service flow sending time. Alternatively, the first device can further determine an offset of the service flow sending time relative to the reference time based on the determined service flow sending time as the service flow sending time information.

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

[0314] For the second implementation, the first device can determine the minimum offset and maximum offset based on the information of the service flow arrival time. The minimum offset is the minimum offset of the second device sending the first service flow relative to the reference time, which is equal to the offset of the earliest sending time relative to the reference time in the above-mentioned first implementation, and the maximum offset is the maximum offset of the second device sending the first service flow relative to the reference time, which is equal to the offset of the latest sending time relative to the reference time in the above-mentioned first implementation. Further, the first device can obtain an offset selection value, and the offset selection value is greater than or equal to the minimum offset and less than or equal to the maximum offset. Then, the first device determines the service flow sending time information based on the offset selection value. The offset selection value can be used as the offset of the service flow sending time relative to the reference time, or the difference between the offset selection value and the jitter delay associated with the first service flow can be used as the offset of the service flow sending time relative to the reference time.

[0315] Exemplarily, the minimum offset may be the earliest transmission offset (EarliestTransmitOffset) in TSpecTimeAware, which is used to define the earliest time offset at which the second device can start sending data packets relative to the reference time within the period (Interval) of the first service flow.

[0316] The first device may determine the minimum offset based on the service flow arrival time information and the processing time of the first service flow on the second device. For example, the minimum offset is the sum of the offset of the service flow arrival time relative to the reference time and the processing time of the first service flow on the second device. Alternatively, the minimum offset may be the sum of the offset of the service flow arrival time relative to the reference time, the processing time of the first service flow on the second device, and the jitter delay associated with the first service flow.

[0317] For example, in the scenario where jitter is not considered,

[0318] EarliestTransmitOffset=T1-offset+processing time of the second device. Formula (11-1)

[0319] Wherein, T1-offset represents the offset of the service flow arrival time relative to the reference time, which can be T1-offset (uplink) obtained by the above formula (2) or T1-offset (downlink) obtained by the above formula (4).

[0320] For example, when the first service flow is an uplink service flow,

[0321] Earliest TransmitOffset(uplink) = T1 - offset(uplink) + T AN . Formula (11-2)

[0322] In addition, the first device may also omit the process of calculating T1-offset (uplink) and directly calculate EarliestTransmitOffset (uplink):

[0323] EarliestTransmitOffset (uplink)=Burst Arrival Time1*+UE-DS-TT Residencetime+PDB+T AN .

[0324] Formula (11-3)

[0325] For example, when the first service flow is a downlink service flow,

[0326] Earliest TransmitOffset (downlink) = T1 - offset (downlink) + T UPF . Formula (11-4)

[0327] In addition, the first device may also omit the process of calculating T1-offset (downlink) and directly calculate EarliestTransmitOffset (downlink):

[0328] EarliestTransmitOffset (downstream)=Burst Arrival Time 2*+T UPF . Formula (11-5)

[0329] In the scenario of jitter,

[0330] Earliest TransmitOffset = T1 - offset + processing time of the second device + jitter. Formula (12-1)

[0331] For example, when the first service flow is an uplink service flow,

[0332] Earliest TransmitOffset(uplink) = T1 - offset(uplink) + T AN +Jitter. Formula (12-2)

[0333] For example, when the first service flow is a downlink service flow,

[0334] Earliest TransmitOffset (downlink) = T1 - offset (downlink) + T UPF +Jitter. Formula (12-3)

[0335] Similarly, the first device may also omit the process of calculating T1-offset, which will not be described here.

[0336] Among them, the specific method for the first device to determine the processing time of the first business flow on the second device can refer to the above related description, and the repeated parts will not be repeated.

[0337] Exemplarily, the maximum offset may be the latest transmission offset (LatestTransmitOffset) in TSpecTimeAware, and the latest transmission offset is used to define the latest time offset at which the second device can start sending frames relative to the reference time within the period (Interval) of the first service flow.

[0338] As for the maximum offset, the maximum offset corresponds to the latest sending time. Therefore, the first device can determine the maximum offset by referring to the method for determining the latest sending time.

[0339] Method A*: In the scenario where jitter is not considered,

[0340] LatestTransmitOffset=T1-offset+Interval-[MaxFrameSize]. Formula (13-1)

[0341] In addition, the first device can also omit the process of calculating T1-offset (uplink) and directly calculate LatestTransmitOffset (uplink), then

[0342] LatestTransmitOffset (uplink)=Burst Arrival Time1*+UE-DS-TT Residencetime+PDB+Interval-[MaxFrameSize]. Formula (13-2)

[0343] The first device can also omit the process of calculating T1-offset (downlink) and directly calculate LatestTransmitOffset (downlink)

[0344] LatestTransmitOffset (downstream)=Burst Arrival Time2*+Interval-[MaxFrameSize].

[0345] Formula (13-3)

[0346] In the scenario where jitter is considered, LatestTransmitOffset = T1-offset+Interval-[MaxFrameSize]-Jitter.

[0347] Formula (14)

[0348] Similarly, the first device may also omit the process of calculating T1-offset, which will not be described here.

[0349] For the above-mentioned method A*, reference may be made to the relevant description of method A corresponding to the latest sending time in the first implementation method.

[0350] Method B*: When jitter is not considered, LatestTransmitOffset = T1-offset+T'+T * . Formula (15-1)

[0351] In addition, the first device can also omit the process of calculating T1-offset (uplink) and directly calculate LatestTransmitOffset (uplink), then

[0352] LatestTransmitOffset (uplink)=Burst Arrival Time1*+UE-DS-TT Residencetime+PDB+T'+T * .

[0353] Formula (15-2)

[0354] The first device may also omit the process of calculating T1-offset (downlink) and directly calculate LatestTransmitOffset (downlink):

[0355] LatestTransmitOffset(downstream)=Burst Arrival Time2*++T'+T * . Formula (15-3)

[0356] In the scenario where jitter is considered, LatestTransmitOffset=T1-offset+T'+T * -Jitter. Formula (16)

[0357] Similarly, the first device may also omit the process of calculating T1-offset, which will not be described here.

[0358] For the above-mentioned method B*, reference may be made to the relevant description of method B corresponding to the latest sending time in the first implementation method.

[0359] Method C*: Based on methods A* and B*, the maximum offset is determined based on methods A* and B* respectively, and the smaller value is selected as the maximum offset.

[0360] For the above-mentioned method C*, reference may be made to the relevant description of method C corresponding to the latest sending time in the first implementation method.

[0361] Illustratively, after determining the minimum offset and the maximum offset in the above manner, the first device may obtain the offset selection value in the following manner, but not limited to.

[0362] In one possible design, the first device sends a minimum offset and a maximum offset to the fourth device. 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.

[0363] In addition, the above method can also be applied to the first implementation method described above. For example, the first device sends the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time to the fourth device. The fourth device can determine the offset selection value based on the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time, and send the offset selection value to the first device. The offset selection value of the first service flow is greater than or equal to the minimum offset of the first service flow and less than or equal to the maximum offset of the first service flow.

[0364] It is understandable that the offset of the earliest sending time relative to the reference time is equal to the minimum offset, and the offset of the latest sending time relative to the reference time is equal to the maximum offset. The following only uses the maximum offset and the minimum offset as examples for explanation.

[0365] In one possible implementation, in addition to the minimum offset and maximum offset of the first business flow, the fourth device can also obtain the minimum offset and maximum offset of the second business flow, where the second business flow arrives at the second device at the same time as the first business flow, or the difference between the time when the second business flow arrives at the second device and the time when the first business flow arrives at the second device is less than or equal to a threshold.

[0366] The fourth device can determine the offset selection value of the first business flow and the offset selection value of the second business flow based on the minimum offset and maximum offset of the first business flow and the minimum offset and maximum offset of the second business flow.

[0367] The offset selection value of the first service flow is greater than or equal to the minimum offset of the first service flow and less than or equal to the maximum offset of the first service flow, and the offset selection value of the second service flow is greater than or equal to the minimum offset of the second service flow and less than or equal to the maximum offset of the second service flow, thereby ensuring the deterministic delay requirements of the first service flow and the deterministic delay requirements of the second service flow. In addition, the difference between the offset selection value of the first service flow and the offset selection value of the second service flow is greater than or equal to the duration corresponding to the MaxFrameSize data packet of the first service flow (when the fourth device determines that the offset selection value of the first service flow is less than the offset selection value of the second service flow) or the duration corresponding to the MaxFrameSize data packet of the second service flow (when the fourth device determines that the offset selection value of the first service flow is greater than the offset selection value of the second service flow), thereby avoiding congestion of the first service flow and the second service flow.

[0368] Optionally, the first device may also send the priority of the first business flow to the fourth device. The fourth device may determine the offset selection value based on the obtained maximum offset and minimum offset of the first business flow, and the priority of the first business flow. For example, for business flows with higher priorities, a smaller offset selection value is set. The smaller the offset selection value, the shorter the time the data packets of the business flow are cached in the second device, and the larger the offset selection value, the longer the data packets of the business flow are cached in the second device. By setting a relatively small offset selection value for business flows with higher priorities, it can be ensured that the data packets of the business flow are sent first, thereby ensuring that their transmission delay is lower.

[0369] Further optionally, the first device may also send the priority of the second service flow to the fourth device, and the fourth device may comprehensively consider the priorities of various service flows to determine the offset selection value for each service flow.

[0370] Optionally, the first device also sends a maximum delay requirement for the transmission of the first service flow between the second device and the third device to the fourth device. The fourth device may determine an offset selection value based on the maximum delay requirement, minimum offset, and maximum offset for the transmission of the first service flow between the second device and the third device, and send the offset selection value to the first device. The maximum delay requirement for the transmission of the first service flow between the second device and the third device refers to the maximum allowable value of the time it takes for the first service flow to be sent by the second device to be received by the third device, or the time it takes for the first service flow to be sent by the third device to be received by the second device.

[0371] For example, the first device can determine the maximum delay requirement for the first business flow to be transmitted between the second device and the third device based on the packet delay budget for the first business flow to be transmitted between the second device and the third device and the processing time of the first business flow on the second device. The packet delay budget for the first business flow to be transmitted between the second device and the third device and the processing time of the first business flow on the second device can be referred to the previous description and will not be repeated here. For example, the maximum delay requirement for the first business flow to be transmitted between the second device and the third device = the packet delay budget for the first business flow to be transmitted between the second device and the third device - the processing time of the first business flow on the second device.

[0372] For another example, the first device can determine the maximum delay requirement for the first business flow to be transmitted between the second device and the third device based on the packet delay budget for the first business flow to be transmitted between the second device and the third device, the processing time of the first business flow on the second device, and the processing time of the first business flow on the third device. The processing time of the first business flow on the third device can refer to the previous description and will not be repeated here. For example, the maximum delay requirement for the first business flow to be transmitted between the second device and the third device = the packet delay budget for the first business flow to be transmitted between the second device and the third device - the processing time of the first business flow on the second device - the processing time of the first business flow on the third device.

[0373] It can be understood that the smaller the value of the maximum delay requirement, the higher the delay requirement of the business flow, and the business flow needs to be sent out as soon as possible. The larger the value of the maximum delay requirement, the lower the delay requirement of the business flow, and the business flow is not in a hurry to be sent out.

[0374] For example, when the first service flow is an uplink service flow, the SMF network element can be configured to receive the packet delay budget (PDB2) (or PDB2') of the first service flow transmitted between the second device and the third device, the processing time (T AN ) and the processing time of the first service flow in the user plane network element (T UPF ) Determine the maximum latency requirement MaxLatency between the second device and the third device. Take PDB2 as an example:

[0375] MaxLatency=PDB2-T AN -T UPF .

[0376] When the first service flow is a downlink service flow, the SMF network element can calculate the packet delay budget (PDB4) (or PDB4') of the first service flow transmitted between the second device and the third device, the processing time (T UPF ) and the processing time (T AN ) Determine the maximum latency requirement MaxLatency between the second device and the third device. Take PDB4 as an example:

[0377] MaxLatency=PDB4-T UPF -T AN .

[0378] Exemplarily, the fourth device may determine the offset selection value in the following manner, but not limited to:

[0379] In one implementation, the fourth device can determine the offset selection value based on the maximum offset and minimum offset of the obtained first business flow, and the maximum delay requirement of the above-mentioned business flow. For example, for a business flow with a smaller maximum delay requirement value for transmission between the second device and the third device, a smaller offset selection value is set. The smaller the offset selection value, the shorter the time the data packets of the business flow are cached in the second device, and the larger the offset selection value, the longer the time the data packets of the business flow are cached in the second device. By setting a relatively small offset selection value for a business flow with more stringent delay requirements, it can be ensured that the data packets of the business flow are sent first, thereby ensuring that its transmission delay is lower.

[0380] Further optionally, the first device may also send the maximum latency requirements of multiple service flows to the fourth device. The fourth device may comprehensively consider the maximum latency requirements of each service flow to determine the offset selection value for each service flow. For example, if the maximum latency requirement of a service flow between the second device and the third device is relatively small, the fourth device may determine a value closer to the minimum offset corresponding to the service flow as the offset selection value corresponding to the service flow; if the maximum latency requirement of a service flow between the second device and the third device is relatively large, the fourth device may determine a value closer to the maximum offset as the offset selection value corresponding to the service flow.

[0381] It should be noted that the present application does not limit the specific method for the fourth device to determine the offset selection value. The above content is only an example and is not intended to limit the present application, and the above various methods can be combined.

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

[0383] It can be understood that the first device and the fourth device are installed together, or the first device integrates the functions of the fourth device.

[0384] Through the above method, the first device can obtain the offset selection value and use the offset selection value as the offset of the service flow sending time relative to the reference time, or the difference between the offset selection value and the jitter delay associated with the first service flow can be used as the offset of the service flow sending time relative to the reference time, thereby obtaining the offset of the service flow sending time relative to the reference time.

[0385] Step 820: After receiving the first service flow, the first device instructs the second device to wait until the service flow sending time to send the first service flow.

[0386] 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 send time to the access network device. If the second device is an AN-TT, the first device may directly send the service flow send time information to the AN-TT; alternatively, the first device may first send the service flow send time information to the access network device, which then notifies the AN-TT. If the first service flow is a downlink service flow, the first device may send information indicating the service flow send time to the user plane network element (N3-TT).

[0387] In a first possible design, the information on the service flow sending time includes an offset of the service flow sending time relative to a reference time or the service flow sending time.

[0388] It is understood that in some special cases, the offset selection value can also be equal to the minimum offset, or in other words, the service flow transmission time can be equal to the earliest transmission time. The following description uses the offset selection value as an example. For example, at a certain moment, no other service flows arrive at the second device except the first service flow. The second device can transmit the first service flow according to the minimum offset. For another example, three service flows arrive at the second device simultaneously: service flow a, service flow b, and service flow c. For service flow a, the offset selection value corresponding to service flow a can be equal to the minimum offset corresponding to service flow a. That is, 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 can 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 (the offset selection value corresponding to service flow b is denoted as the first value). Then, after service flow b arrives at the second device and is processed by the second device, the second device needs to wait for a period of time corresponding to the difference between the first value and the minimum offset corresponding to service flow b before transmitting service flow b to the third device. For service flow c, the offset selection value corresponding to service flow c can be greater than the minimum offset corresponding to service flow c and less than or equal to the maximum offset corresponding to service flow c (the offset selection value corresponding to service flow c is recorded as the second value), and the second value is greater than the first value. After service flow c reaches the second device and is processed by the second device, the second device needs to wait for 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, by configuring different service flow sending times for each service flow through the above method, the data packets of the three service flows will not be congested, and the delay requirements of the three service flows can be met respectively.

[0389] Optionally, the difference between the first value and the minimum offset is the duration corresponding to the MaxFrameSize data packet of service flow a, and the difference between the second value and the first value is the duration corresponding to the MaxFrameSize data packet of service flow b. The above setting can ensure that after service flow a is sent, service flow b is sent, and after service flow b is sent, service flow c is sent, thereby better avoiding congestion in the sending of service flows a, b, and c, while fully utilizing network resources, thereby improving the overall performance of the network.

[0390] Exemplarily, the fourth device sends interface configuration information for the second device to the first device. The first device sends interface configuration information for the second device to the second device. Exemplarily, the interface configuration information for the second device includes the interface identifier (InterfaceID) of the second device and information on the service flow sending 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 (InterfaceName). Among them, the interface corresponding to the interface identifier of the second device is the egress port for sending the first service flow. That is to say, through the interface identifier (InterfaceID) of the second device, the second device can know which interface is used as the egress port for sending the first service flow, and combined with the information on the service flow sending time, the second device can wait at the egress port until the service flow sending time to send the first service flow according to the information on the service flow sending time.

[0391] In addition, the fourth device may also send interface configuration information for the third device to the first device, and the first device may send interface configuration information for the third device to the third device. Exemplarily, the interface configuration information for the third device includes the interface identifier of the third device. Optionally, the interface configuration information for the third device may also include information on the service flow sending time. 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 receiving port for receiving the first service flow. That is, through the interface identifier of the third device, the third device can know which interface is used as the receiving port for receiving the first service flow.

[0392] 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 data packets of the first service flow, the second device may carry the priority corresponding to the QFI in the outer MAC address, so that switching nodes on the path between the second device and the third device can determine the corresponding transmission queue based on the priority of the QFI.

[0393] For example, Figure 11 As shown, the eight transmission queues have different priorities. The second device can determine the transmission queue where the data packet of the first service flow is located according to the priority of the QoS flow identifier.

[0394] In one possible design, the information on the service flow sending time includes gating scheduling parameters.

[0395] Exemplarily, the first device may further determine a gating scheduling parameter based on the period of the first service flow, the maximum burst size of the first service flow, and the service flow transmission time. The gating scheduling parameter here refers to a first gating scheduling parameter, or in other words, the first gating scheduling parameter refers to a gating scheduling parameter determined by the first device. The first gating scheduling parameter may include an administrative value (AdminCycleTime) for the port gating cycle, an administrative value (AdminBaseTime) for the base time, and an administrative value (AdminControlList) for the port gating list.

[0396] The second device determines a second gating scheduling parameter based on the first gating scheduling parameter. In other words, the second gating scheduling parameter refers to the gating scheduling parameter determined by the second device. The second gating scheduling parameter may include an operation value (OperCycleTime) of the port gating cycle, an operation value (OperBaseTime) of the base time, a time when the gating cycle starts (CycleStartTime), and an operation value (OperControlList) of the gating list running on the port.

[0397] The relationship between the first gating scheduling parameter and the second gating scheduling parameter is introduced below:

[0398] AdminCycleTime: Used to configure the gating cycle for each port. The secondary device uses this parameter to set the OperCycleTime. AdminCycleTime and OperCycleTime can be the same or different.

[0399] AdminBaseTime: Used to configure the start time of the gating cycle for each port. AdminBaseTime typically represents the duration relative to the start time of a time domain (for example, 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: CycleStartTime = OperBaseTime + N * OperCycleTime, where N represents the Nth cycle and is a positive integer.

[0400] AdminControlList: Used to configure the gating actions of each port's transmission queue, including the gate state (gateState) and time interval (TimeInterval). GateState is the gating state (open or closed) of each port's transmission queue. If the gate state is open, the switch node can transmit traffic; if the gate state is closed, the switch node cannot transmit traffic. TimeInterval is the duration of the gating state. The switch node uses this parameter to set the operation value of OperControlList. AdminControlList and OperControlList can be the same or different.

[0401] Figure 11 A schematic diagram of an AdminControlList or an OperControlList is shown. Figure 11 The gate control list on the right side can represent the above-mentioned AdminControlList or OperControlList. The following description takes AdminControlList as an example. Figure 11 As shown, at the moment when AdminBaseTime corresponds to T00, the gating states corresponding to the eight transmission queues from sequence number 7 to sequence number 0 are: oCooCooo. Among them, C indicates that the gating state is closed, that is, the data packets in the corresponding queue cannot be sent; o indicates that the gating state is open, that is, the data packets in the corresponding queue can be sent. The duration of this state is T01 minus the duration of T00, that is, at the moment corresponding to T01, the gating state changes. At the moment corresponding to T01, the gating states corresponding to the eight transmission queues from sequence number 7 to sequence number 0 are: CoCooCCo. For example, at the moment corresponding to T05, the gating state of the transmission queue corresponding to sequence number 7 is C, that is, the second device does not transmit the data packets in the transmission queue corresponding to sequence number 7 at the moment corresponding to T05. At the moment corresponding to T05, the gating state of the transmission queue corresponding to sequence number 6 is o, that is, the second device can transmit the data packets in the transmission queue corresponding to sequence number 6 at the moment corresponding to T05.

[0402] It is understandable that the second device can be used to transmit multiple business flows, and the multiple business flows can arrive at the second device at the same time or at different times, and the priority of each business flow in the multiple business flows can be the same or different. When the priorities of the current multiple business flows are different, the second device can place them into different transmission queues according to the priority of each business flow. Multiple business flows of the same priority are placed in the same transmission queue. For each transmission queue, the first device can determine the corresponding first gating scheduling parameter based on the business flow to be transmitted in the transmission queue, and the second device can determine the second gating scheduling parameter corresponding to the transmission queue based on the first gating scheduling parameter corresponding to the transmission queue. In other words, the gating scheduling parameter corresponding to a transmission queue is used to schedule one or more business flows of the same priority transmitted through the transmission queue.

[0403] Specifically, the method for the first device to configure the first gating scheduling parameter may refer to the following example:

[0404] Example 1: When multiple business flows with the same priority arrive at the same time, the first device puts the multiple business flows into a transmission queue, and the first device sends the minimum offset and maximum offset (optionally, priority) of each business flow in the multiple business flows to the fourth device. The fourth device can configure different offset selection values ​​for each business flow. Exemplarily, the interval between the offset selection values ​​of any two adjacent business flows sent in the offset selection values ​​corresponding to the multiple business flows determined by the fourth device is not less than the duration corresponding to the maximum data packet of the business flow sent first in the two business flows, thereby achieving the sending of multiple business flows without congestion. And the offset selection value corresponding to each business flow is greater than or equal to the minimum offset corresponding to the business flow, and less than or equal to the maximum offset corresponding to the business flow, so as to meet the deterministic delay requirements corresponding to the multiple business flows. Furthermore, the first device can determine and send information on the business flow sending time of each business flow to the second device based on the offset selection values ​​corresponding to the multiple business flows.

[0405] In addition, the first device can also determine AdminBaseTime based on the minimum value of the offset selection values ​​corresponding to multiple business flows, determine AdminCycleTime based on the least common multiple of the cycles corresponding to multiple business flows, and determine the duration of the door state being open based on the duration corresponding to the maximum data packet of each business flow.

[0406] That is, in this example, the offset selection value of the service flow sent by the first device to the second device is consistent with the first gating scheduling parameter.

[0407] Exemplarily, periodic service flow J and periodic service flow K have the same priority. Periodic service flow J and periodic service flow K are both downlink service flows. Among them, EarliestTransmitOffset corresponds to the minimum offset, LatestTransmitOffset corresponds to the maximum offset, and TimeAwareOffset corresponds to the offset selection value. In the following example, the above-mentioned method A* for determining the maximum offset is used to calculate LatestTransmitOffset. It can be understood that the LatestTransmitOffset can also be calculated using method B* or method C*. This is only an example and is not intended to be a limitation of the embodiments of the present application.

[0408] The parameters for periodic service flow J are as follows:

[0409] <Maximum Burst Size in time> (represents the duration corresponding to sending the largest data packet of periodic service flow J) = (120 μs in time);

[0410] Processing time = 100us;

[0411] Interval (indicating the period of periodic service flow J) = 500 μs;

[0412] The offset of the arrival time of periodic service flow J relative to the reference time = 1600,000,000,000,110 us.

[0413] The parameters for periodic service flow K are as follows:

[0414] <Maximum Burst Size in time> (represents the duration corresponding to sending the largest data packet of periodic service flow K) = (80 μs in time);

[0415] Processing time = 100us;

[0416] Interval (indicating the period of periodic service flow J) = 500 μs;

[0417] The offset of the arrival time of periodic service flow K relative to the reference time = 1600,000,000,000,110 us.

[0418] In the scenario where delay jitter is not considered, according to the above formula (11-4) and formula (13-1), the EarliestTransmitOffset (corresponding to the minimum offset) and LatestTransmitOffset (corresponding to the maximum offset) of flow J can be calculated.

[0419] EarliestTransmitOffset = the offset of the arrival time of periodic service flow J relative to the reference time + processing time = 1600,000,000,000,210 μs;

[0420] LatestTransmitOffset = the offset of the arrival time of periodic service flow J relative to the reference time + 500–120 = 1600,000,000,000,490 μs.

[0421] In the scenario where delay jitter is not considered, according to the above formula (11-4) and formula (13-1), the EarliestTransmitOffset (corresponding to the minimum offset) and LatestTransmitOffset (corresponding to the maximum offset) of flow K can be calculated.

[0422] EarliestTransmitOffset = the offset of the arrival time of periodic service flow K relative to the reference time + 100 μs = 1600,000,000,000, 210 μs;

[0423] LatestTransmitOffset = the arrival time offset of periodic service flow K relative to the reference time + 500–80 = 1600,000,000,000,530 μs;

[0424] Assume that the TimeAwareOffset (corresponding offset selection values) returned by the fourth device are:

[0425] For periodic service flow J, TimeAwareOffset = 1600,000,000,000, 320 μs;

[0426] For periodic service flow K, TimeAwareOffset = 1600,000,000,000,440 μs;

[0427] It should be noted that the fourth device can obtain the information of streams J and K.<Maximum Burst Size in time> The above jitter is calculated. The fourth device will refer to the TimeAwareOffset of each service flow when determining the TimeAwareOffset of each service flow.<MaximumBurst Size in time> , so that the difference between the TimeAwareOffset corresponding to stream J and the TimeAwareOffset corresponding to stream K determined by the fourth device is equal to the TimeAwareOffset of stream J<Maximum Burst Size in time> , thus ensuring the deterministic transmission of stream J.

[0428] Furthermore, the first device may determine based on the above result:

[0429] The offset of the sending time of periodic service flow J relative to the reference time is 1600,000,000,000,320 μs, and the offset of the sending time of periodic service flow K relative to the reference time is 1600,000,000,000,440 μs;

[0430] The gating scheduling parameters corresponding to periodic service flows J and K are: AdminBaseTime is 1600,000,000,000, 320 μs; AdminCycleTime is 500 μs; AdminControlList, where GateState=Open, TimeInterval=200 μs; GateState=Closed, TimeInterval=300 μs.

[0431] The first device sends the determined parameters to the second device, and the second device determines based on the parameters:

[0432] The offset of the sending time of periodic service flow J relative to the reference time is 1600,000,000,000,320 μs, and the offset of the sending time of periodic service flow K relative to the reference time is 1600,000,000,000,440 μs;

[0433] OperBaseTime, OperCycleTime, and OperControlList of periodic service flow J and periodic service flow K, for example:

[0434] OperCycleTime=AdminCycleTime=500us;

[0435] OperBaseTime=AdminBaseTime=1600,000,000,000,320μs;

[0436] AdminControlList is the same as OperControlList.

[0437] The second device can send periodic service flow J to the third device based on the offset of the sending time of periodic service flow J relative to the reference time and the second gating scheduling parameters, and send periodic service flow K to the third device based on the offset of the sending time of periodic service flow K relative to the reference time and the second gating scheduling parameters. This can not only meet the deterministic delay requirements of periodic service flow J and periodic service flow K, but also avoid congestion of periodic service flow J and periodic service flow K.

[0438] Here we will combine Figure 12A Describe. Since the duration corresponding to sending the maximum data packet of periodic business flow J is 120us, and the duration corresponding to sending the maximum data packet of periodic business flow K is 80us, the difference between the TimeAwareOffset corresponding to periodic business flow J and the TimeAwareOffset corresponding to periodic business flow K can be the duration corresponding to the maximum data packet of periodic business flow J (i.e., 120us). The duration that the door state remains open in each cycle is 200us, that is, the duration that the door state remains open in each cycle is the sum of the duration corresponding to the maximum data packet of periodic business flow J and the duration corresponding to the maximum data packet of periodic business flow K. After the door state is switched to open for 200us, the door state is switched to closed. In addition, the cycle of periodic business flow J is the same as that of periodic business flow K, which is 500us. That is, after the door state is switched to closed for 300us, it enters the next cycle and the door state is switched to open again.

[0439] By adopting the above method, by configuring different service flow sending times of periodic service flow J and periodic service flow K and the gating scheduling parameters corresponding to periodic service flow J and periodic service flow K, congestion of service flows with the same priority that arrive at the second device at the same time can be avoided, and at the same time, the deterministic delay requirements of the service flows can be guaranteed.

[0440] Example 2: When multiple business flows with the same priority arrive at the same time, the first device puts the multiple business flows into a transmission queue, and the first device sends the minimum offset and maximum offset and priority of each business flow in the multiple business flows to the fourth device. The fourth device can configure an offset selection value for each business flow separately. Among them, the offset selection value corresponding to each business flow is greater than or equal to the minimum offset corresponding to the business flow, and less than or equal to the maximum offset corresponding to the business flow, so as to meet the deterministic delay requirements corresponding to the multiple business flows. The first device can determine the AdminBaseTime according to the minimum value of the difference between the offset selection value corresponding to the multiple business flows and the corresponding jitter, determine the AdminCycleTime according to the least common multiple of the cycles corresponding to the multiple business flows, and determine the duration of the door state being open according to the duration corresponding to the largest data packet of each business flow.

[0441] In this case, the first device does not need to directly configure the service flow transmission times corresponding to the multiple service flows. Instead, it implicitly indicates a service flow transmission time for the multiple service flows through AdminBaseTime. This service flow transmission time can be the service flow transmission time of any service flow among the multiple service flows. Other service flows are randomly transmitted after this service flow, that is, the transmission order of each service flow is not specified. By reserving a sufficiently long duration for the door state to be open, it is ensured that multiple service flows can be transmitted from the second device when the door state is open.

[0442] For example, the priorities of periodic service flow J and periodic service flow K are the same. For specific parameters of periodic service flow J and periodic service flow K, refer to the description in Example 1.

[0443] Similarly, based on the above description of delay jitter, the jitter of periodic service flow J and periodic service flow K can be calculated:

[0444] Periodic service flow J: Jitter = 40 μs;

[0445] Periodic service flow K: Jitter = 60 μs.

[0446] Therefore, according to the above formula (12-3) and formula (14), the EarliestTransmitOffset (corresponding to the minimum offset) and LatestTransmitOffset (corresponding to the maximum offset) of stream J can be calculated.

[0447] EarliestTransmitOffset = the offset of the arrival time of periodic service flow J relative to the reference time + processing time + jitter = 1600,000,000,000, 250 μs;

[0448] LatestTransmitOffset = the offset of the arrival time of periodic service flow J relative to the reference time + 500–120-Jitter = 1600,000,000,000,450 μs.

[0449] According to the above formula (12-3) and formula (14), the EarliestTransmitOffset (corresponding to the minimum offset) and LatestTransmitOffset (corresponding to the maximum offset) of stream K can be calculated.

[0450] EarliestTransmitOffset = the arrival time offset of periodic service flow K relative to the reference time + 100 μs + Jitter = 1600,000,000,000, 270 μs;

[0451] LatestTransmitOffset = the arrival time offset of periodic service flow K relative to the reference time + 500 – 80 – Jitter = 1600,000,000,000,470 μs;

[0452] Assume that the TimeAwareOffset (corresponding offset selection values) returned by the fourth device are:

[0453] For periodic service flow J, TimeAwareOffset = 1600,000,000,000, 320 μs;

[0454] For periodic service flow K, TimeAwareOffset = 1600,000,000,000, 340 μs;

[0455] The first device subtracts the corresponding jitter from each TimeAwareOffset, and obtains: 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. Further, the first device can determine that AdminBaseTime is 1600,000,000,000,280us based on the above results. The first device also determines that AdminCycleTime is 500μs. According to AdminCycleTime and<Maximum Burst Size in time> Configure AdminControlList, where GateState=Open, TimeInterval=200μs; GateState=Closed, TimeInterval=300μs.

[0456] It should be noted that the fourth device can determine that flow J and flow K are service flows of the same priority according to the priority of the service flow sent by the first device, and<Maximum Burst Size in time> The jitter is calculated. The fourth device refers to the jitter when determining the TimeAwareOffset of each service flow. As a result, the difference between the TimeAwareOffset corresponding to flow J determined by the first device and the corresponding jitter, and the difference between the TimeAwareOffset corresponding to flow K determined by the first device and the corresponding jitter, correspond to the same time offset, namely, AdminBaseTime.

[0457] Here we will combine Figure 12B Because the duration corresponding to sending the maximum data packet of periodic service flow J is 120µs, and the duration corresponding to sending the maximum data packet of periodic service flow K is 80µs, the gate remains open for 200µs within each cycle. That is, 200µs after the gate switches to open, it switches to closed. Furthermore, the period of periodic service flow J is the same as that of periodic service flow K, which is 500µs. That is, 300µs after the gate switches to closed, it enters the next cycle and switches back to open.

[0458] After receiving the AdminBaseTime, AdminCycleTime, and AdminControlList of periodic service flows J and K, the second device can determine the OperBaseTime, OperCycleTime, and OperControlList of periodic service flows J and K based on these parameters. For example:

[0459] OperCycleTime=AdminCycleTime=500us;

[0460] OperBaseTim=AdminBaseTime=1600,000,000,000,280us;

[0461] AdminControlList is the same as OperControlList.

[0462] like Figure 12CAs shown, since periodic service flow J and periodic service flow K have the same priority, they will be transmitted in the same transmission queue. For ease of description, it is assumed that the outbound port of the second device only supports two transmission queues. Assume 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 description of the gating 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 is transmitted when the transmission node has idle resources. Taking the time corresponding to AdminBaseTime being T00 as an example, the gating state of transmission queue 1 is open at this time, and the second device can send 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 sent first, followed by periodic service flow K, or periodic service flow K may be sent first, followed by periodic service flow J. The gate remains open for 200 μs. The second device completes sending periodic service flows J and K. At time T01, the gating state of each transmission queue changes. Transmission queue 1's gating state is now closed, and the gate remains open for 300 μs. The second device stops sending periodic service flows J and K and begins sending periodic service flow M. At time T02, the gating operation continues for one cycle, OperCycleTime (500 μs). The gating operation at time T00 is repeated.

[0463] It should be noted that in Example 2 above, whenever the gating state corresponding to periodic service flow J and periodic service flow K is on, although the first device does not indicate the order of sending periodic service flow J and periodic service flow K, that is, the order of sending periodic service flow J and periodic service flow K is uncertain, for example, the second device may send periodic service flow J first or periodic service flow K first, but it still does not cause micro-bursts and micro-congestion in the second device and the transmission nodes between the second device and the third device. The reason is that, because the first device can configure the second device to reserve a sufficiently long sending time for periodic service flow J and periodic service flow K, that is, the duration of the gating state being on is long enough, for the second device, regardless of whether periodic service flow J or periodic service flow K is sent first, the periodic service flow J and periodic service flow K can be sent within the duration of the gating state being on. Similarly, for the transmission 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 can configure the transmission node to have a fixed and sufficiently long duration of the gating state reserved for the transmission of these two periodic service flows, thereby enabling the transmission of periodic service flow J and periodic service flow K to be completed within the duration of the gating state being on. By adopting the solution provided in the embodiment of the present application, it is possible to ensure that the second device and the transmission node between the second device and the third device reserve sufficient resources for the transmission of periodic service flow J and periodic service flow K, thereby achieving the determinism of the transmission time of periodic service flow J and the determinism of the transmission time of periodic service flow K.

[0464] That is to say, in Example 2, the service flow sending time is implicitly indicated for service flows of the same priority through the gating scheduling parameters. The service flow sending time transmitted through the gating scheduling parameters can be used to send multiple service flows in the transmission queue in sequence. At the same time, the time when the gating state is turned on is sufficient to ensure that multiple service flows are transmitted, thereby achieving deterministic transmission and improving the overall performance of the network.

[0465] Example 3: When multiple service flows of different priorities do not arrive at the same time, the first device places the multiple service flows into different transmission queues. The first device can send the minimum offset and maximum offset as well as the priority of each service flow in the multiple service flows to the fourth device. The fourth device can configure different offset selection values ​​for each service flow. For example, the interval between the offset selection values ​​of any two adjacently sent service flows in the offset selection values ​​corresponding to the multiple service flows determined by the fourth device is not less than the duration corresponding to the maximum data packet of the service flow with higher priority in the two service flows, so as to ensure that the service flow with higher priority is sent before the service flow with lower priority, thereby achieving the transmission of multiple service flows without congestion. And 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, so as to meet the deterministic delay requirements corresponding to the multiple service flows. Furthermore, the first device can determine and send the service flow sending time of each service flow to the second device based on the offset selection values ​​corresponding to the multiple service flows.

[0466] In addition, the first device determines AdminBaseTime according to the minimum value of the offset selection values ​​corresponding to the multiple business flows, and determines AdminCycleTime according to the least common multiple of the cycles corresponding to the multiple business flows.

[0467] Exemplarily, the priorities of periodic service flow J and periodic service flow K are different, and the priority of periodic service flow J is higher than that of periodic service flow K, that is, relative to periodic service flow K, periodic service flow J enjoys priority sending rights. Periodic service flow J and periodic service flow K are both downlink service flows. Among them, EarliestTransmitOffset corresponds to the minimum offset, LatestTransmitOffset corresponds to the maximum offset, and TimeAwareOffset corresponds to the offset selection value. In the following example, the above-mentioned method A* for determining the maximum offset is used to calculate LatestTransmitOffset. It can be understood that the method B* or method C* can also be used to calculate LatestTransmitOffset. This is only an example and is not a limitation of the embodiments of the present application.

[0468] The parameters for periodic service flow J are as follows:

[0469] <Maximum Burst Size in time> (represents the duration corresponding to sending the largest data packet of periodic service flow J) = (120 μs in time);

[0470] Interval (indicates the period of periodic service flow J) = 400 μs;

[0471] Jitter (representing the jitter of periodic service flow J) = 0 μs; (Since there are no other service flows with the same priority as periodic service flow J, the jitter is 0);

[0472] Processing time = 100us;

[0473] The offset of the arrival time of periodic service flow J relative to the reference time = 1600,000,000,000,120 us.

[0474] Therefore, according to the above formula (11-4) and formula (13-1), the EarliestTransmitOffset (corresponding to the minimum offset) and LatestTransmitOffset (corresponding to the maximum offset) of periodic service flow J can be calculated.

[0475] EarliestTransmitOffset = the offset of the arrival time of periodic service flow J relative to the reference time + 100 μs + Jitter = 1600,000,000,000, 220 μs;

[0476] LatestTransmitOffset = the offset of the arrival time of periodic service flow J relative to the reference time + 400 – 120 – Jitter = 1600,000,000,000,400 μs.

[0477] The parameters for periodic service flow K are as follows:

[0478] <Maximum Burst Size in time> (represents the duration corresponding to sending the largest data packet of periodic service flow K) = (80 μs in time);

[0479] Interval (indicating the period of periodic service flow K) = 800 μs;

[0480] Jitter (indicates the jitter of periodic service flow K) = 0 μs;

[0481] Processing time = 100us;

[0482] The offset of the arrival time of periodic service flow K relative to the reference time = 1600,000,000,000,100 us.

[0483] Similarly, according to the above formula (11-4) and formula (13-1), the EarliestTransmitOffset (corresponding to the minimum offset) and LatestTransmitOffset (corresponding to the maximum offset) of the periodic service flow K can be calculated.

[0484] EarliestTransmitOffset = the offset of the arrival time of periodic service flow K relative to the reference time + 100us + Jitter = 1600,000,000,000, 200μs;

[0485] LatestTransmitOffset = the offset of the arrival time of periodic service flow K relative to the reference time + 800 – 80 – Jitter = 1600,000,000,000,820 μs.

[0486] The first device sends the EarliestTransmitOffset and LatestTransmitOffset of periodic service flow J, the priority of periodic service flow J, to the fourth device, and sends the EarliestTransmitOffset and LatestTransmitOffset of periodic service flow K, the priority of periodic service flow K, to the fourth device. The fourth device determines a value within the range of EarliestTransmitOffset to LatestTransmitOffset for periodic service flow J and periodic service flow K as the TimeAwareOffset (corresponding to the offset selection value). Assume that the TimeAwareOffset (corresponding to the offset selection value) of periodic service flow J and periodic service flow K returned by the fourth device are:

[0487] For periodic service flow J, TimeAwareOffset = 1600,000,000,000, 260 μs;

[0488] For periodic service flow K, TimeAwareOffset = 1600,000,000,000, 380 μs.

[0489] It should be noted that the difference between the TimeAwareOffset of periodic service flow K and the TimeAwareOffset of periodic service flow J is the TimeAwareOffset of flow K.<Maximum Burst Size in time> In this way, the periodic service flow K and the periodic service flow J can be staggered and sent without congestion. Of course, the present application is not limited to this. The difference between the TimeAwareOffset of the periodic service flow K and the TimeAwareOffset of the periodic service flow J can also be greater than the TimeAwareOffset of the periodic service flow K.<Maximum Burst Size in time> .

[0490] The first device can determine that AdminBaseTime is 1600,000,000,000,260us based on the TimeAwareOffset of the different flows (for example, taking the minimum value of the TimeAwareOffset of the different flows). The first device also determines that AdminCycleTime is 800us (that is, the least common multiple of the Interval corresponding to the periodic service flow J and the periodic service flow K respectively).<Maximum Burst Size in time> Configure AdminControlList.

[0491] Here we will combine Figure 12D For the queue containing periodic service flow J, since the duration of sending the largest data packet of periodic service flow J is 120µs, the gate state remains open for 120µs in each cycle. That is, 120µs after the gate state of the queue containing periodic service flow J switches to open, the gate state of the queue containing periodic service flow J is closed. Furthermore, the cycle of periodic service flow J is 400µs. That is, 280µs after the gate state of the queue containing periodic service flow J switches to closed, the next cycle begins and the gate state of the queue containing periodic service flow J switches to open again. Therefore, the AdminControlList of periodic service flow J includes: GateState=Open, TimeInterval=120μs (indicating that the gate state is switched to open for 120us); GateState=Closed, TimeInterval=280μs (indicating that the gate state is switched to open for 280us); GateState=Open, TimeInterval=120μs; GateState=Closed, TimeInterval=280μs.

[0492] For the queue containing periodic service flow K, the gate state is initially closed. It switches to open only after the gate state of periodic service flow J is closed. The remaining principles are similar to those for periodic service flow J. Therefore, the AdminControlList for periodic service flow K includes: GateState = Closed, TimeInterval = 120 μs; GateState = Open, TimeInterval = 80 μs; GateState = Closed, TimeInterval = 720 μs; GateState = Open, TimeInterval = 80 μs; GateState = Closed, TimeInterval = 720 μs.

[0493] It can be understood that the first device determines the AdminBaseTime, AdminCycleTime, the AdminControlList of periodic business flow J and the AdminControlList of periodic business flow K, and also determines the service flow sending time of periodic business flow J, that is, AdminBaseTime, and determines the service flow sending time of periodic business flow K, that is, according to the AdminBaseTime and the AdminControlList of periodic business flow J and the AdminControlList of periodic business flow K, determines the time when the door state of periodic business flow K is open as the service flow sending time of periodic business flow K.

[0494] After receiving the AdminBaseTime, AdminCycleTime, and AdminControlList of periodic service flows J and K, the second device may determine the OperBaseTime, OCycleTime, and OperControlList of periodic service flows J and K, as well as the service flow sending time of periodic service flow K and the service flow sending time of periodic service flow J based on these parameters, for example:

[0495] OperCycleTime=AdminCycleTime=800us;

[0496] OperBaseTime=AdminBaseTime=1600,000,000,000,260us;

[0497] AdminControlList is the same as OperControlList.

[0498] Here we will combine Figure 12D At the time offset corresponding to OperBaseTime, the queues where periodic service flow J and periodic service flow K are located are operated according to their respective OperControlLists.

[0499] For example, for periodic service flow J, at the time offset 1600,000,000,000,260us, the gate state of the transmission queue of periodic service flow J is opened. The gate state remains open for 120us. At the time offset 1600,000,000,000,380us, the gate state of the transmission queue of periodic service flow J is closed. The gate state remains closed for 280us. At the time offset 1600,000,000,000,660us, the gate state of the transmission queue of periodic service flow J is opened again, entering the next period, and so on.

[0500] For periodic service flow K, at the time offset 1600,000,000,000,260us, the gate state of the transmission queue of periodic service flow K is closed. The gate state remains closed for 120us. At the time offset 1600,000,000,000,380us, the gate state of the transmission queue of periodic service flow K is opened. The gate state remains open for 80us. At the time offset 1600,000,000,000,460us, the gate state of the transmission queue of periodic service flow K is closed again, and the next cycle begins. And so on.

[0501] like Figure 12EAs shown, due to the different priorities of periodic service flow J and periodic service flow K, they will be transmitted in different transmission queues respectively. For the convenience of description, it is assumed that periodic service flow J is transmitted in transmission queue 1 and periodic service flow K is transmitted in transmission queue 0. At the moment when AdminBaseTime corresponds to T00, the gating state of transmission queue 1 corresponding to periodic service flow J is open, and the gating state of transmission queue 0 corresponding to periodic service flow K is closed. The second device can send periodic service flow J, and the gate of transmission queue 1 is open for 120us. The second device completes the sending of periodic service flow J until the moment corresponding to T01, when the gating state of each transmission queue changes. The gating state of transmission queue 1 corresponding to periodic service flow J is closed, and the gating state of transmission queue 0 corresponding to periodic service flow K is open. The second device can send periodic service flow K, and the gate of transmission queue 0 is open for 80us. The second device completes the transmission of periodic service flow K until the time corresponding to T02, at which point the gating state of each transmission queue changes again. The gating state of transmission queue 1 corresponding to periodic service flow J is closed, and the gating state of transmission queue 0 corresponding to periodic service flow K is closed. This state lasts for 200us until the time corresponding to T03. At this time, the gating state of transmission queue 1 corresponding to periodic service flow J is open, and the gating state of transmission queue 0 corresponding to periodic service flow K is closed. The second device can send periodic service flow J. The gate is open for 120us. The second device completes the transmission of periodic service flow J until the time corresponding to T04, at which point the gating state of each transmission queue changes again. The gating state of transmission queue 1 corresponding to periodic service flow J is closed, and the gating state of transmission queue 0 corresponding to periodic service flow K is closed. This state lasts for 280us. From the time corresponding to T0 to the time corresponding to T05, the gating operation corresponds to one cycle, namely, OperCycleTime (800us). The gate control operation corresponding to the time corresponding to T00 begins to be repeated at the time corresponding to T05.

[0502] It should be noted that in the above example 1, although the priorities of periodic business flow J and periodic business flow K are different, and the time of arrival at the second device is also different, the method provided in the embodiment of the present application can ensure that the high-priority business flow is sent first. Specifically, the priority of periodic business flow J is higher than the priority of periodic business flow K. The method provided in the embodiment of the present application controls the gating state and duration corresponding to the different transmission queues of periodic business flow J and periodic business flow K. When periodic business flow K arrives at the second device before periodic business flow J, it is still possible to achieve priority sending of periodic business flow J with a higher priority, thereby avoiding the situation where periodic business flow J needs to wait until periodic business flow K is sent before it can be sent because periodic business flow K is being sent.

[0503] In some embodiments, the first device may further transmit information used to determine the gating scheduling parameters to the second device, and the second device may determine the gating scheduling parameters. The information used to determine the gating scheduling parameters may include the period of each service flow, the offset selection value of each service flow, the duration corresponding to the maximum data packet corresponding to each service flow, and the like.

[0504] In addition, it should be noted that in an embodiment of the present application, the fourth device is also used to determine the forwarding path of the first business flow (i.e., the forwarding path from the second device to the third device) based on the topology of the user plane (including access network devices, user plane network elements, and the transmission nodes between the two), the capability information of each transmission node, and the information about the first business flow sent by the first device, such as the minimum offset and maximum offset involved in the above embodiment, and configure the transmission nodes on the forwarding path, that is, send corresponding gating scheduling parameters to each transmission node. The gating scheduling parameters here are gating scheduling parameters for the transmission nodes. For example, the AdminBaseTime in the gating scheduling parameters of the next transmission node of the second device can be the AdminBaseTime in the gating scheduling parameters of the second device plus the maximum transmission delay required from the second device to the next transmission node of the second device, and the other parameters are the same. Among them, the above-mentioned transmission node can also send its own capability information to the fourth device (used by the fourth device to configure the forwarding path for the business flow and determine the corresponding gating scheduling parameters). The transmission node that receives the gating scheduling parameters forwards the first business flow based on the received gating scheduling parameters. This application does not limit how the fourth device determines the forwarding path of the first business flow and configures the transmission nodes on the forwarding path. Therefore, by configuring the second device and the transmission nodes on the forwarding path determined from the second device to the third device, it is possible to ensure the deterministic transmission delay requirement between the second device and the third device.

[0505] the following Figure 13 and Figure 14 Combined with the above Figure 6A and Figure 6B The architecture shown in FIG. 1 illustrates the transmission process of the first service flow. Figure 13 and Figure 14 In the example, SMF is used to implement the function of the first device. Figure 13 In the example, the first service flow is an uplink service flow, and the AN-TT is an independently deployed device outside the gNB, or the AN-TT serves as a functional module inside the gNB.

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

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

[0508] For details, please refer to the relevant description in the above method 1, and the repeated parts will not be repeated.

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

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

[0511] For example, when the AN-TT is a functional module within the gNB, the SMF network element can obtain the AN-TT processing time information and AN-TT port information from the gNB. In this case, the AN-TT processing time information is also called the gNB processing time information.

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

[0513] For example, the SMF network element can determine the processing time of the first service flow in the AN-TT according to the processing time information of the AN-TT. For the 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 above.

[0514] S1303: The PCF network element sends the PCC rules to the SMF network element.

[0515] The PCC rule includes a TSC auxiliary container, which contains the burst arrival time information of the first service flow, the period of the first service flow, and the direction of the first service flow. The PCC rule may also include service requirement description parameters, which may include the Maximum Burst Size. Furthermore, the TSC auxiliary container and service requirement parameters may include other parameters. For details, refer to the relevant content in the above-mentioned method 1. The burst arrival time information of the first service flow here refers to the time information when the first service flow arrives at the DS-TT.

[0516] correspond Figure 6A , the PCF network element can obtain the burst arrival time information of the first service flow, the period of the first service flow, the direction of the first service flow and the service requirement description parameters from the TSN AF network element.

[0517] correspond Figure 6B The PCF network element can obtain the burst arrival time information of the first service flow, the period of the first service flow, the direction of the first service flow and the service requirement description parameters from the TSCTSF network element.

[0518] For example, the PCF network element may generate a PCC rule based on the burst arrival time information of the first service flow, the period 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. The SMF network element associates the PCC rule with a QoS flow, which is the QoS flow corresponding to the first service flow.

[0519] In the 5GS system, the first service flow may be a service flow aggregated by TSN AF or TSCTSF, that is, TSN AF or TSCTSF aggregates multiple service flows with the same or similar characteristics into the first service flow.

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

[0521] The minimum offset can also be called the earliest offset, and the maximum offset can also be called the latest offset. For example, the SMF network element specifies TSpecTimeAware. The minimum offset corresponds to the EarliestTransmitOffset in TSpecTimeAware, and the maximum offset corresponds to the LatestTransmitOffset in TSpecTimeAware. The following example uses the minimum offset as the EarliestTransmitOffset and the maximum offset as the LatestTransmitOffset.

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

[0523] Exemplarily, the SMF network element can determine the EarliestTransmitOffset using the above formula (11-3) or formula (12-2) based on the UE-DS-TT-Residence Time in S1301, the processing time information of the gNB in ​​S1302, the burst arrival time information of the first service flow in the PCC rule in S1303, and the PDB1 determined according to the PCC rule.

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

[0525] Exemplarily, the SMF network element may determine LatestTransmitOffset according to the UE-DS-TT-Residence Time in S1301, the burst arrival time information of the first service flow in the PCC rule in S1303, the period of the first service flow, the Maximum Burst Size included in the service requirement description parameter, and the PDB1 determined according to the PCC rule using the above formula (13-2) or formula (14);

[0526] Alternatively, if the SMF network element obtains the maximum cache duration of the first service flow in the AN-TT, the SMF network element can determine the LatestTransmitOffset based on the processing time information of the AN-TT in S1302, the maximum cache duration of the first service flow in the AN-TT, the UE-DS-TT-Residence Time in S1301, the burst arrival time information of the first service flow in the PCC rule in S1303, and the PDB1 determined according to the PCC rule using formula (15-2) or formula (16). The SMF network element can obtain the maximum cache duration of the first service flow in the AN-TT by referring to the description of the relevant paragraphs above, which will not be repeated here. For example, at this time, the SMF network element also needs to obtain the processing time information of the UPF network element from the UPF network element.

[0527] Alternatively, the SMF network element may also select the smaller value as the LatestTransmitOffset after determining the above two LatestTransmitOffsets.

[0528] It is understood that when the AN-TT is a functional module within the gNB, the SMF network element determines PDB1 according to the PCC rules. When the AN-TT is a standalone device deployed outside the gNB, the SMF network element determines PDB1' according to the PCC rules, that is, the above PDB1 is replaced by PDB1'.

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

[0530] In addition, the SMF network element can also send the priority (StreamRank) of the first service flow, the period of the first service flow, the maximum frame size, the maximum delay requirement between the AN-TT and N3-TT network elements, and at least one parameter of the port information of the AN-TT to the CNC-TN network element.

[0531] The maximum frame size is determined by the Maximum Burst Size. The maximum delay requirement between AN-TT and N3-TT network elements can be determined by referring to the above. Figure 8 The relevant descriptions in the embodiments are not repeated here.

[0532] S1306: The CNC-TN network element determines the 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.

[0533] The interface configuration information may include: InterfaceID and offset selection value, where InterfaceID is used to identify a port indicated by the port information of the AN-TT in S1302.

[0534] The offset value is TimeAwareOffset. TimeAwareOffset ≥ EarliestTransmitOffset, TimeAwareOffset ≤ LatestTransmitOffset.

[0535] S1307: The SMF network element determines the gating scheduling parameters according to the offset selection value returned by the CNC-TN network element. The gating scheduling parameters include AdminBaseTime, AdminCycleTime, and AdminControlList.

[0536] Exemplarily, the SMF network element determines the gating scheduling parameters based on the offset selection value, the period of the first service flow and the Maximum Burst Size. For details, please refer to Examples 1, 2 and 3 shown in the above-mentioned periodic service flow J and periodic service flow K, which will not be repeated here.

[0537] S1308: The SMF network element sends the gating scheduling parameters.

[0538] When the AN-TT is an independently deployed device outside the gNB, the SMF network element sends the gating scheduling parameters to the AN-TT, or the SMF sends the gating scheduling parameters to the gNB, and the gNB sends the gating scheduling parameters to the AN-TT.

[0539] When AN-TT is used as a functional module within the gNB, the SMF network element sends the gating scheduling parameters to the gNB. The gNB notifies the AN-TT of the gating scheduling parameters through the internal interface.

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

[0541] Using the above method, the SMF network element configures the gating scheduling parameters associated with the first business flow for AN-TT. AN-TT transmits the business flow according to the configuration of the SMF network element to avoid congestion between the first business flow and other business flows, thereby meeting the deterministic delay requirements of the first business flow, and realizing low-latency transmission between AN-TT and N3-TT, thereby improving the overall performance of the network.

[0542] exist Figure 14 In the example, the first service flow is a downlink service flow.

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

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

[0545] Exemplarily, 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 the specific content of the processing time information of the UPF network element, reference may be made to the relevant description of the processing time information of the second device in step 810 above. In addition, the method for obtaining the processing time information of the UPF network element is similar to the method for obtaining the port information of the N3-TT. For details, reference may be made 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 above, and repeated parts will not be repeated.

[0546] S1402: The PCF network element sends the PCC rules to the SMF network element.

[0547] Exemplarily, the PCC rule includes a TSC auxiliary container, which includes the burst arrival time information of the first service flow, the period of the first service flow, and the direction of the first service flow. The PCC rule also includes service requirement description parameters, which include the Maximum Burst Size. Furthermore, the TSC auxiliary container and service requirement parameters may also include other parameters. For details, refer to the relevant content in the above-mentioned method 1. This differs from the above-mentioned S1303 in that the burst arrival time information of the first service flow here refers to the time information when the first service flow arrives at the NW-TT.

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

[0549] The minimum offset can also be called the earliest offset, and the maximum offset can also be called the latest offset. For example, the SMF network element specifies TSpecTimeAware. The minimum offset corresponds to the EarliestTransmitOffset in TSpecTimeAware, and the maximum offset corresponds to the LatestTransmitOffset in TSpecTimeAware. The following example uses the minimum offset as the EarliestTransmitOffset and the maximum offset as the LatestTransmitOffset.

[0550] (1) The SMF network element determines the EarliestTransmitOffset. For example, the SMF network element can determine the EarliestTransmitOffset using the above formula (11-5) or formula (12-3) based on the processing time information of the UPF network element in S1401 and the burst arrival time information of the first service flow in the PCC rule in S1402.

[0551] (2) The SMF network element determines the LatestTransmitOffset. For example, the SMF network element may determine the LatestTransmitOffset based on the burst arrival time information of the first service flow in the PCC rule in S1402, the period of the first service flow, and the Maximum Burst Size included in the service requirement description parameters using the above formula (13-3) or formula (14).

[0552] Alternatively, if the SMF network element determines the maximum cache duration of the first service flow in the UPF network element, the SMF network element can use formula (15-3) or formula (16) to determine LatestTransmitOffset based on the processing time information of the UPF network element in S1401, the maximum cache duration of the first service flow in the UPF, and the burst arrival time information of the first service flow in the PCC rule in S1402. The SMF network element can refer to the description of the relevant paragraphs above for obtaining the maximum cache duration of the first service flow in the UPF network element, which will not be repeated here. For example, at this time, the SMF network element also needs to obtain the processing time information of the AN-TT.

[0553] Alternatively, the SMF network element may also select the smaller value as the LatestTransmitOffset after determining the above two LatestTransmitOffsets.

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

[0555] In addition, the SMF network element can also send the priority of the first service flow, the period of the first service flow, the maximum frame size, the maximum delay requirement between the AN-TT and N3-TT network elements, and at least one parameter of the port information of N3-TT to the CNC-TN network element.

[0556] The maximum frame size is determined by the Maximum Burst Size. The maximum delay requirement between AN-TT and N3-TT network elements can be determined by referring to the above. Figure 8 The relevant descriptions in the embodiments are not repeated here.

[0557] S1405: The CNC-TN network element determines the 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.

[0558] The interface configuration information may include: InterfaceID and an offset selection value, where InterfaceID is used to identify an N3-TT port indicated by the N3-TT port information in S1401.

[0559] The offset value is TimeAwareOffset. TimeAwareOffset ≥ EarliestTransmitOffset, TimeAwareOffset ≤ LatestTransmitOffset.

[0560] S1406: The SMF network element determines the gating scheduling parameters according to the offset selection value returned by the CNC-TN network element. The gating scheduling parameters include AdminBaseTime, AdminCycleTime, and AdminControlList.

[0561] Exemplarily, the SMF network element determines the gating scheduling parameters based on the offset selection value, the period of the first service flow and the Maximum Burst Size. For details, please refer to Examples 1, 2 and 3 shown in the above-mentioned periodic service flow J and periodic service flow K, which will not be repeated here.

[0562] S1407: The SMF network element sends the gating scheduling parameters to the UPF network element.

[0563] The UPF network element can notify the gating scheduling parameters to N3-TT through the internal interface.

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

[0565] It is understandable that in Figure 13 and Figure 14 In the illustrated embodiment, the SMF network element may also not determine the gating scheduling parameters, but instead send information for determining a gating scheduling reference, or the sending time of the first service flow or the offset of the sending time of the first service flow relative to the reference time. The sending time of the first service flow or the offset of the sending time of the first service flow relative to the reference time may be determined based on TimeAwareOffset. The information used to determine the gating scheduling parameters may include periods corresponding to multiple service flows, offset selection values ​​for multiple service flows, durations corresponding to the maximum data packets corresponding to multiple service flows, priorities corresponding to multiple service flows, etc., wherein the multiple service flows include the first service flow.

[0566] Using the above method, the SMF network element configures the gating scheduling parameters associated with the first service flow for N3-TT. N3-TT transmits the service flow according to the SMF configuration to avoid congestion between the first service flow and other service flows, thereby meeting the deterministic delay requirements of the first service flow, and realizing low-latency transmission between AN-TT and N3-TT, thereby improving the overall performance of the network.

[0567] Lower combination Figure 15 and Figure 16 For the above Figure 7A The transmission process of the first business flow of the architecture shown is described. Figure 15 and Figure 16In the example, the TSN AF network element is used to implement the functions of the above SMF network element. Figure 15 In the example, the first service flow is the uplink service flow.

[0568] S1501 to S1502 may refer to the above-mentioned S1301 to S1302, and the repeated parts will not be repeated.

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

[0570] Exemplarily, the processing time information of the AN-TT and the port information of the AN-TT may be encapsulated in a container, that is, the SMF network element is invisible, or may not be encapsulated in a container, in which case the SMF network element can read the above information.

[0571] S1504: The PCF network element sends the PCC rules to the SMF network element.

[0572] For details, please refer to the above S1303.

[0573] S1505: The SMF network element determines, according to the PCC rule, either one or both of the packet delay budget (PDB1) for the first service flow transmitted between the UE and the gNB and the packet delay budget (PDB2) for the first service flow transmitted between the gNB and the UPF network element.

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

[0575] In addition, the SMF network element can send any one or both of the information obtained in S1501 to S1502, as well as the packet delay budget (PDB1) for the first service flow transmitted between the UE and the gNB, and the packet delay budget (PDB2) for the first service flow transmitted between the gNB and the UPF network element to the TSN AF network element through the PCF network element, that is, S1503 and S1506 can be combined into one step.

[0576] In addition, when the AN-TT is an independently deployed device located outside the gNB, the above PDB1 and PDB2 are replaced by PDB1' and PDB2'.

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

[0578] The method for the TSN AF network element to determine the minimum offset and the maximum offset may be the same as the method for the SMF network element to determine the minimum offset and the maximum offset. For details, please refer to the relevant description of S1304 above.

[0579] 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.

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

[0581] The interface configuration information may include: InterfaceID and offset selection value, where InterfaceID is used for a port in the port information of AN-TT.

[0582] The offset selection value may be TimeAwareOffset, where TimeAwareOffset ≥ EarliestTransmitOffset and TimeAwareOffset ≤ LatestTransmitOffset.

[0583] S1510: The TSN AF network element determines the gating scheduling parameters according to the offset selection value returned by the CNC-TN network element. The gating scheduling parameters include AdminBaseTime, AdminCycleTime, and AdminControlList.

[0584] S1511: The TSN AF network element sends the gating scheduling parameters to the SMF network element through the PCF network element. In addition, the TSN AF network element can also send the Interface ID to the SMF network element through the PCF network element.

[0585] S1512: The SMF network element sends gating scheduling parameters.

[0586] When the AN-TT is an independently deployed device outside the gNB, the SMF network element sends the gating scheduling parameters to the AN-TT, or the SMF sends the gating scheduling parameters to the gNB, and the gNB sends the gating scheduling parameters to the AN-TT.

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

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

[0589] By adopting the above method, the TSN AF network element configures the first gating scheduling parameter associated with the first service flow for the AN-TT through the SMF network element. The AN-TT transmits the service flow according to the configuration of the TSN AF, thereby avoiding the congestion problem between the first service flow and other service flows, thereby meeting the deterministic delay requirement of the first service flow, realizing low-latency transmission between the AN-TT and the N3-TT, and improving the overall performance of the network.

[0590] exist Figure 16 In the example, the first service flow is a downlink service flow.

[0591] S1601 can refer to the above S1401, and the repeated parts will not be repeated.

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

[0593] Exemplarily, the processing time information of the UPF network element and the port information of N3-TT obtained from the UPF network element can be encapsulated in a container, that is, the SMF network element is invisible, and may not be encapsulated in a container. At this time, the SMF network element can read the above information.

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

[0595] For details, please refer to the relevant description of S1403 above.

[0596] 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.

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

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

[0599] The offset selection value may be TimeAwareOffset, where TimeAwareOffset ≥ EarliestTransmitOffset and TimeAwareOffset ≤ LatestTransmitOffset.

[0600] S1606: The TSN AF network element determines the gating scheduling parameters according to the offset selection value returned by the CNC-TN network element. The gating scheduling parameters include AdminBaseTime, AdminCycleTime, and AdminControlList.

[0601] S1607: The TSN AF network element sends the gating scheduling parameters to the SMF network element through the PCF network element.

[0602] In addition, the TSN AF network element also sends the InterfaceID to the SMF network element through the PCF network element.

[0603] S1608: The SMF network element sends the gating scheduling parameters to the UPF network element.

[0604] The UPF network element notifies the N3-TT of the gating scheduling parameters.

[0605] In addition, the SMF network element sends the InterfaceID to the UPF network element, and the UPF network element notifies the N3-TT of the InterfaceID.

[0606] It is understandable that in Figure 15 and Figure 16 In the embodiment shown, the TSN AF network element may also not determine the gating scheduling parameters, but instead send information for determining the gating scheduling reference, or the sending time of the first service flow or the offset of the sending time of the first service flow relative to the reference time. The sending time of the first service flow or the offset of the sending time of the first service flow relative to the reference time can be determined according to TimeAwareOffset. The information used to determine the gating scheduling parameters may include the periods corresponding to the multiple service flows, the offset selection values ​​of the multiple service flows, the duration corresponding to the maximum data packets corresponding to the multiple service flows, the priorities corresponding to the multiple service flows, etc., wherein the multiple service flows include the first service flow.

[0607] Using the above method, the TSN AF network element configures the first gating scheduling parameter associated with the first service flow for N3-TT through the SMF network element. N3-TT transmits the service flow according to the TSN AF configuration to avoid congestion between the first service flow and other service flows, thereby meeting the deterministic delay requirement of the first service flow, achieving low-latency transmission between AN-TT and N3-TT, and improving the overall performance of the network.

[0608] It should be noted that when the above Figure 15 and Figure 16 When the TSN AF network element in the embodiment shown is replaced by a TSCTSF network element, the above embodiment can be applied to the following examples: Figure 7B The architecture shown.

[0609] In another embodiment, in addition to the above Figures 6A to 7B The network architecture can also be Figure 17 As shown, domain 1 can refer to the relevant description shown in Figure 6 above. In domain 2, the user plane includes the gNB and UPF network elements in 5GS and the switches between them, and the control plane includes the element manager (EM) network element, the network manager (NM) network element and the CNC-CN network element. Figure 17 In the example, the NM network element can be used to implement the function of the first device in domain 2.

[0610] Among them, EM network element: provides network element management function and manages one or more network elements.

[0611] NM network element: provides network management functions and manages the network between network elements managed by each EM.

[0612] The following combination Figure 18 For the above Figure 17 The transmission process of the first business flow of the architecture shown is explained.

[0613] S1801: The NM network element determines the delay requirement of the transmission link between the AN-TT and the N3-TT, and the characteristics of the flow after the flow is aggregated, based on the network planning and service planning.

[0614] For example, the characteristics of the flow after flow aggregation include the flow period, the maximum number of data packets transmitted within the period, the maximum duration of the data packets, etc.

[0615] Network planning refers to the NM network element planning the data packet processing and transmission capabilities of the AN-TT, N3-TT, and transmission nodes between the AN-TT and N3-TT network elements, as well as the network topology between the AN-TT and N3-TT network elements. Service planning refers to the NM network element pre-acquiring the various 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, and the characteristics of each type of service flow (such as cycle time, transmission time, etc.) before the network runs services. Based on the characteristics of each type of service flow, one or more converged flows are determined to subsequently determine the gating scheduling parameters of the queues corresponding to each converged flow.

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

[0617] Among them, the above information can be configured on the NM network element, or when the gNB (AN-TT is deployed inside the gNB) or AN-TT (independently deployed) is powered on, the processing time information of the AN-TT and the port information of the AN-TT are reported to the NM network element, or when the UPF network element is powered 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.

[0618] S1803: The NM network element determines the minimum offset and maximum offset based on the information obtained in S1801 and S1802. Figure 13 or Figure 14 SMF network element or Figure 15 or Figure 16 The same processing method as the TSN AF network element in the network is used to determine the minimum offset and the maximum offset based on the obtained information, which will not be repeated here.

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

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

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

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

[0623] S1806: The NM network element determines the gating scheduling parameter according to the offset selection value returned by the CNC-TN network element.

[0624] S1807A: When the first service flow is an uplink service flow, the NM network element sends a gating scheduling parameter through the EM network element.

[0625] S1807B: When the first service flow is a downlink service flow, the NM network element sends a gating scheduling parameter through the EM network element.

[0626] Using the above method, the NM network element can first determine the gating scheduling parameters in advance based on network planning and service planning, and send the gating scheduling parameters to the AN-TT or N3-TT network element, thereby meeting the deterministic latency requirements of the first service flow and achieving low-latency transmission between the AN-TT and N3-TT network elements.

[0627] Figure 19 A possible exemplary block diagram of a device involved in an embodiment of the present application is shown. Device 1900 includes a transceiver module 1910 and a processing module 1920. Transceiver module 1910 may include a receiving unit and a sending unit. Processing module 1920 is configured to control and manage the operations of device 1900. Transceiver module 1910 is configured to support communication between device 1900 and other network entities. Optionally, device 1900 may also include a storage unit configured to store program code and data of device 1900.

[0628] Optionally, each module in the device 1900 may be implemented by software.

[0629] Optionally, the processing module 1920 can be a processor or controller, for example, a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a transistor logic device, a hardware component or any combination thereof. It can implement or execute the various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of the embodiments of the present application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like. The transceiver module 1910 can be a communication interface, a transceiver or a transceiver circuit, etc., wherein the communication interface is a general term. In a specific implementation, the communication interface can include multiple interfaces, and the storage unit can be a memory.

[0630] When the apparatus 1900 is a first device or a chip in the first device, the processing module 1920 in the apparatus 1900 can support the apparatus 1900 in performing the actions of the first device in each method example above, for example, supporting the apparatus 1900 in performing Figure 8 Step 800, step 810, Figure 13 S1304, S1307, Figure 14 S1403, S1406, Figure 15 S1507 and S1510, Figure 16 S1603 and S1606, Figure 18 S1801, S1802, S1803, S1806.

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

[0632] For example,

[0633] In one implementation, processing module 1920 is configured to determine information about a service flow arrival time, the service flow arrival time information including the service flow arrival time or the offset of the service flow arrival time relative to a reference time, the service flow arrival time being the time when a first service flow arrives at a second device, wherein the first service flow is a periodic service flow to be transmitted by the second device between an access network device and a user plane network element; processing module 1920 is configured to determine information about a service flow sending time based on the service flow arrival time information; and transceiver module 1910 is configured to instruct the second device to wait until the service flow sending time to send the first service flow after receiving the first service flow. If the first service flow is an uplink service flow, the second device is the access network device or a converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is the user plane network element.

[0634] In one possible design, the transceiver module 1910 is used to send information about the service flow sending time to the second device after instructing the second device to receive the first service flow and wait until the service flow sending time to send the first service flow.

[0635] In one possible design, the information of the service flow sending time includes the service flow sending time or the offset of the service flow sending time relative to the reference time; the service flow sending time is no later than the latest sending time, and the latest sending time is determined based on the information of the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the latest sending time is determined based on the information of the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache length of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time does not exceed the maximum offset, and the maximum offset is determined based on the information of the offset of the service flow arrival time relative to the reference time, the period of the first service flow and the maximum burst size of the first service flow, and / or the maximum offset is determined based on the information of the offset of the service flow arrival time relative to the reference time, the processing time of the first service flow on the second device and the maximum cache length of the first service flow on the second device.

[0636] In one possible design, the service flow sending time is not earlier than the earliest sending time, and the earliest sending time is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time is greater than or equal to the minimum offset, and the minimum offset is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device.

[0637] In one possible design, the parameters used to determine the latest sending time or the maximum offset or the earliest sending time or the minimum offset also include a jitter delay associated with the first service flow.

[0638] In one possible design, the service flow sending time of the second device to send the second service flow determined by the first device is different from the service flow sending time of the second device to send the first service flow determined by the first device. The second service flow is a periodic service flow to be transmitted by the second device between the access network device and the user plane network element. The second service flow arrives at the second device at the same time as the first service flow, or the difference between the time when the second service flow arrives at the second device and the time when the first service flow arrives at the second device is less than or equal to a threshold.

[0639] In one possible design, the processing module 1920 is used to obtain an offset selection value when determining the information of the service flow sending time based on the information of the service flow arrival time, and 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 sending time relative to the reference time and less than or equal to the offset of the latest sending time relative to the reference time; determine the information of the service flow sending time based on the offset selection value.

[0640] In one possible design, the transceiver module 1910 is used to send the minimum offset and the maximum offset, or the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time to a fourth device; and receive the offset selection value from the fourth device.

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

[0642] In one possible design, the processing module 1920 is used to determine the information of the service flow sending time based on the offset selection value and the jitter delay associated with the first service flow when determining the information of the service flow sending time based on the offset selection value.

[0643] In one possible design, the information on the service flow sending time includes gating scheduling parameters; the processing module 1920 is used to obtain the period of the first service flow and the maximum burst size of the first service flow; determine the size of the maximum frame of the first service flow based on the maximum burst size of the first service flow; determine the gating scheduling parameters based on the period of the first service flow, the maximum frame size of the first service flow and the offset selection value.

[0644] In one possible design, when the second device is the access network device and the third device is the user plane network element, the first service flow reaches the second device through the terminal device; the processing module 1920 is used to obtain information on the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first service flow between the terminal device and the second device when determining the information on the service flow arrival time; determine the information on the service flow arrival time based on information on the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first service flow between the terminal device and the second device.

[0645] In one possible design, the first device is a delay-sensitive network TSN application function network element; the processing module 1920 is used to determine the information of the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first service flow between the terminal device and the second device when obtaining information of the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for transmission of the first service flow between the terminal device and the second device from the session management network element.

[0646] In one possible design, the first device is a session management network element; the transceiver module 1910 is used to receive information about the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget for the first service flow transmitted between the terminal device and the second device from the policy control network element, and receive the residence time of the first service flow in the terminal device and in the converter on the terminal device side from the terminal device; the processing module 1920 is used to determine the packet delay budget for the transmission of the first service flow between the terminal device and the second device.

[0647] It should be understood that the device 1900 according to the embodiment of the present application may correspond to the first device in the aforementioned method embodiment, and the operations and / or functions of the various modules in the device 1900 are respectively for implementing the corresponding steps of the method of the first device in the aforementioned method embodiment, and therefore the beneficial effects in the aforementioned method embodiment can also be achieved. For the sake of brevity, they are not elaborated here.

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

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

[0650] For example, in one implementation, the transceiver module 1910 is configured to receive a first service flow, wherein the first service flow is a periodic service flow to be transmitted by the second device between the access network device and the user plane network element; receive service flow transmission time information from the first device; and the processing module 1920 is configured to wait until the service flow transmission time indicated by the service flow transmission time information and transmit the first service flow to the third device. If the first service flow is an uplink service flow, the second device is the access network device or a converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is the user plane network element.

[0651] In one possible design, the information on the service flow sending time includes the service flow sending time or the offset of the service flow sending time relative to a reference time; wherein, the service flow sending time is no later than the latest sending time, and the latest sending time is determined based on the information on the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the latest sending time is determined based on the information on the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache duration of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time does not exceed the maximum offset, and the maximum offset is determined based on the information on the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the maximum offset is determined based on the information on the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache duration of the first service flow on the second device.

[0652] In one possible design, the service flow sending time is not earlier than the earliest sending time, and the earliest sending time is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device; or, the offset of the service flow sending time relative to the reference time is greater than or equal to the minimum offset, and the minimum offset is determined based on the information of the service flow arrival time and the processing time of the first service flow on the second device.

[0653] In one possible design, the parameters used to determine the latest sending time or the maximum offset or the earliest sending time or the minimum offset also include a jitter delay associated with the first service flow.

[0654] In one possible design, the service flow sending time of the second device sending the second service flow is different from the service flow sending time of the second device sending the first service flow. The second service flow is a periodic service flow to be transmitted by the second device between the access network device and the user plane network element. The second service flow arrives at the second device at the same time as the first service flow, or the difference between the time when the second service flow arrives at the second device and the time when the first service flow arrives at the second device is less than or equal to a threshold.

[0655] In one possible design, the information on the service flow sending time includes gating scheduling parameters.

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

[0657] It should be understood that the device 1900 according to the embodiment of the present application may correspond to the second device in the aforementioned method embodiment, and the operations and / or functions of the various modules in the device 1900 are respectively for implementing the corresponding steps of the method of the second device in the aforementioned method embodiment, and therefore the beneficial effects in the aforementioned method embodiment can also be achieved. For the sake of brevity, they are not elaborated here.

[0658] Figure 20 FIG2 shows a schematic structural diagram of a communication device 2000 according to an embodiment of the present application. Figure 20 As shown, the device 2000 includes: a processor 2001.

[0659] When the apparatus 2000 is a first device or a chip in the first device, in one possible implementation, when the processor 2001 is configured to call an interface, the processor 2001 performs the following actions:

[0660] Determine information about the arrival time of a service flow, the information about the arrival time of the service flow includes the arrival time of the service flow or the offset of the arrival time of the service flow relative to a reference time, the arrival time of the service flow being the time when the first service flow arrives at the second device, wherein the first service flow is a periodic service flow to be transmitted by the second device between the access network device and the user plane network element; determine information about the service flow sending time based on the information about the arrival time of the service flow; instruct the second device to wait until the service flow sending time to send the first service flow after receiving the first service flow. If the first service flow is an uplink service flow, the second device is the access network device or a converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is the user plane network element.

[0661] It should be understood that the apparatus 2000 may also be used to execute other steps and / or operations on the first device side in the foregoing embodiments, which are not described in detail here for the sake of brevity.

[0662] When the apparatus 2000 is a second device or a chip in the second device, in one possible implementation, when the processor 2001 is configured to call an interface, the processor 2001 performs the following actions:

[0663] Receive a first service flow, where the first service flow is a periodic service flow to be transmitted by the second device between an access network device and a user plane network element; wait for a service flow transmission time indicated by the service flow transmission time, and then transmit the first service flow to the third device. If the first service flow is an uplink service flow, the second device is the access network device or a converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is the user plane network element.

[0664] It should be understood that the apparatus 2000 may also be used to execute other steps and / or operations on the second device side in the foregoing embodiments, which are not described here for the sake of brevity.

[0665] It should be understood that the processor 2001 can call an interface to perform the above-mentioned transceiver action, wherein the called interface can be a logical interface or a physical interface, which is not limited to this. Optionally, the physical interface can be implemented by a transceiver. Optionally, the device 2000 also includes a transceiver 2003.

[0666] Optionally, the apparatus 2000 further includes a memory 2002 , which can store program codes in the above method embodiments for easy calling by the processor 2001 .

[0667] Specifically, if 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 an internal connection path to transmit control and / or data signals. In one possible design, the processor 2001, the memory 2002, and the transceiver 2003 can be implemented by a chip. The processor 2001, the memory 2002, and the transceiver 2003 can be implemented in the same chip, or they can be implemented in different chips, or any two of their functions can be combined and implemented in a single chip. The memory 2002 can store program code, and the processor 2001 calls the program code stored in the memory 2002 to implement the corresponding functions of the device 2000.

[0668] The methods disclosed in the above embodiments of the present application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, the steps of the above method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in software form. The above processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processing circuit (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chip. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0669] It is understood that the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0670] It should be understood that in the embodiments of the present application, the numbers "first", "second"... are only for distinguishing different objects, such as to distinguish different parameter information or messages, and do not constitute a limitation on the scope of the embodiments of the present application. The embodiments of the present application are not limited to this.

[0671] It should also be understood that in the various embodiments of the present application, the order of execution of the above-mentioned processes does not necessarily indicate the order in which they are executed. The order in which the processes are executed should be determined by their functions and internal logic. The various numbers or serial numbers involved in the above-mentioned processes are merely for the convenience of description and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0672] It should also be understood that the term "and / or" as used herein simply describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " as used herein generally indicates that the associated objects are in an "or" relationship.

[0673] In this application, expressions similar to “the item includes one or more of the following: A, B, and C” generally mean, unless otherwise specified, 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 other combinations of A, B and C. The above examples use A, B, and C as an example to illustrate the optional items of the item. When the expression is “the item includes at least one of the following: A, B, …, and X”, that is, when the expression contains more elements, the items applicable to the item can also be obtained according to the above rules.

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

[0675] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0676] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0677] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0678] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0679] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.

Claims

1. A communication method, characterized in that: include: The first device determines 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, and the service flow arrival time is a time when the first service flow arrives at the second device, wherein the first service flow is a periodic service flow to be transmitted between the access network device and the user plane network element; The first device determines information about a service flow sending time according to information about an arrival time of the service flow; The first device instructs the second device to wait until the service flow sending time to send the first service flow after receiving the first service flow; Among them, if the first service flow is an uplink service flow, the second device is the access network device or the converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is the user plane network element.

2. The method according to claim 1, wherein The first device instructs the second device to wait until the service flow sending time to send the first service flow after receiving the first service flow, including: The first device sends information about the service flow sending time to the second device.

3. The method according to claim 1 or 2, wherein: The service flow sending time of the second service flow sent by the second device determined by the first device is different from the service flow sending time of the first service flow sent by the second device determined by the first device. The second service flow is a periodic service flow to be transmitted by the second device between the access network device and the user plane network element. The second service flow arrives at the second device at the same time as the first service flow, or the difference between the time when the second service flow arrives at the second device and the time when the first service flow arrives at the second device is less than or equal to a threshold.

4. The method according to claim 1 or 2, wherein: The information of the service flow sending time includes the service flow sending time or the offset of the service flow sending time relative to the reference time; The service flow sending time is no later than the latest sending time, and the latest sending time is determined based on the information of the service flow arrival time, the period of the first service flow, and the maximum burst size of the first service flow, and / or the latest sending time is determined based on the information of the service flow arrival time, the processing time of the first service flow on the second device, and the maximum cache time of the first service flow on the second device; Alternatively, the offset of the service flow sending time relative to the reference time does not exceed the maximum offset, and the maximum offset is determined based on the information of the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the maximum offset is determined based on the information of the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache length of the first service flow on the second device.

5. The method according to claim 4, wherein The service flow sending time is no earlier than the earliest sending time, where the earliest sending time is determined based on information about the service flow arrival time and a processing time of the first service flow on the second device; Alternatively, the offset of the service flow sending time relative to the reference time is greater than or equal to a minimum offset, and the minimum offset is determined based on information on the service flow arrival time and the processing time of the first service flow on the second device.

6. The method according to claim 5, wherein The parameters used to determine the latest sending time or the maximum offset or the earliest sending time or the minimum offset also include a jitter delay associated with the first service flow.

7. The method according to claim 5 or 6, wherein: The first device determines information about a service flow sending time based on the information about the service flow arrival time, including: The first device acquires 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, or the offset selection value is greater than or equal to the offset of the earliest sending time relative to the reference time and less than or equal to the offset of the latest sending time relative to the reference time; The first device determines information about the service flow sending time according to the offset selection value.

8. The method according to claim 7, wherein The first device obtains the offset selection value, including: The first device sends the minimum offset and the maximum offset, or the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time to the fourth device; The first device receives the offset selection value from the fourth device.

9. The method according to claim 8, wherein The first device obtains the offset selection value, further comprising: The first device determines a delay requirement for transmission of the first service flow between the second device and the third device based on a packet delay budget for transmission of the first service flow between the second device and the third device, a processing time of the first service flow on the second device, and a processing time of the first service flow on the third device; the third device is a device to receive the first service flow; if the first service flow is an uplink service flow, the third device is the user plane network element; if the first service flow is a downlink service flow, the third device is the access network device or a converter corresponding to the access network device; The first device sends the delay requirement to the fourth device.

10. The method according to claim 8 or 9, characterized in that The first device determines information about the service flow sending time according to the offset selection value, including: The first device determines information about the service flow sending time based on the offset selection value and the jitter delay associated with the first service flow.

11. The method according to claim 8 or 9, characterized in that The information on the service flow sending time includes gating scheduling parameters; The method further comprises: The first device obtains a period of the first service flow and a maximum burst size of the first service flow; The first device determines the maximum frame size of the first service flow according to the maximum burst size of the first service flow; The first device determines the gating scheduling parameter according to the period of the first service flow, the size of the maximum frame of the first service flow and the offset selection value.

12. The method according to claim 1 or 2, wherein: When the first service flow is an uplink service flow; The information of the service flow arrival time determined by the first device includes: The first device obtains information about the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget of the first service flow transmitted between the terminal device and the second device; The first device determines the information of the arrival time of the service flow based on the information of the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget of the first service flow transmitted between the terminal device and the second device.

13. The method according to claim 12, wherein: The first device is a delay-sensitive network TSN application function network element; The first device obtains information about the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget of the first service flow transmitted between the terminal device and the second device, including: Information of time when the first service flow arrives at the converter on the terminal device side, determined by the first device; The first device receives, from a session management network element, a residence time of the first service flow in the terminal device and in a converter on the terminal device side, and a packet delay budget for transmission of the first service flow between the terminal device and the second device.

14. The method according to claim 12, wherein: The first device is a session management network element; The first device obtains information about the time when the first service flow arrives at the converter on the terminal device side, the residence time of the first service flow in the terminal device and in the converter on the terminal device side, and the packet delay budget of the first service flow transmitted between the terminal device and the second device, including: The first device receives information about the time when the first service flow arrives at the converter on the terminal device side from the policy control network element; The first device receives, from the terminal device, a residence time of the first service flow in the terminal device and in a converter on the terminal device side; The first device determines a packet delay budget for transmission of the first service flow between the terminal device and the second device.

15. A communication method, characterized in that: include: The second device receives a first service flow, wherein the first service flow is a periodic service flow to be transmitted between the access network device and the user plane network element; The second device receives information about the service flow sending time from the first device; The second device waits until the service flow sending time indicated by the information about the service flow sending time to send the first service flow; Among them, if the first service flow is an uplink service flow, the second device is the access network device or the converter corresponding to the access network device; if the first service flow is a downlink service flow, the second device is the user plane network element.

16. The method according to claim 15, wherein The service flow sending time of the second device sending the second service flow is different from the service flow sending time of the second device sending the first service flow. The second service flow is a periodic service flow to be transmitted between the access network device and the user plane network element. The second service flow arrives at the second device at the same time as the first service flow, or the difference between the time when the second service flow arrives at the second device and the time when the first service flow arrives at the second device is less than or equal to a threshold.

17. The method according to claim 15 or 16, wherein: The information of the service flow sending time includes the service flow sending time or the offset of the service flow sending time relative to the reference time; The service flow sending time is no later than the latest sending time, and the latest sending time is determined based on the information of the service flow arrival time, the period of the first service flow, and the maximum burst size of the first service flow, and / or the latest sending time is determined based on the information of the service flow arrival time, the processing time of the first service flow on the second device, and the maximum cache time of the first service flow on the second device; Alternatively, the offset of the service flow sending time relative to the reference time does not exceed the maximum offset, and the maximum offset is determined based on the information of the service flow arrival time, the period of the first service flow and the maximum burst size of the first service flow, and / or the maximum offset is determined based on the information of the service flow arrival time, the processing time of the first service flow on the second device and the maximum cache length of the first service flow on the second device.

18. The method according to claim 17, wherein The service flow sending time is no earlier than the earliest sending time, where the earliest sending time is determined based on information about the service flow arrival time and a processing time of the first service flow on the second device; Alternatively, the offset of the service flow sending time relative to the reference time is greater than or equal to a minimum offset, and the minimum offset is determined based on information on the service flow arrival time and the processing time of the first service flow on the second device.

19. The method according to claim 18, wherein The parameters used to determine the latest sending time or the maximum offset or the earliest sending time or the minimum offset also include a jitter delay associated with the first service flow.

20. The method according to any one of claims 15 or 19, wherein: The information on the service flow sending time includes gating scheduling parameters.

21. The method according to claim 15 or 16, wherein: The first device is a TSN application function network element, or the first device is a session management network element.

22. A communication device, characterized in that: The method comprises a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method according to any one of claims 1 to 14 through a logic circuit or executing code instructions.

23. A communication device, characterized in that: It includes a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method as described in any one of claims 15 to 21 through a logic circuit or executing code instructions.

24. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction, and when the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 21 is implemented.

Images