Scheduling rule determination method and apparatus

Abstract

The embodiment of the application provides a scheduling rule determination method and device, wherein the method comprises: an access network device receiving port information of a virtual switching node from a session management network element, the port information of the virtual switching node comprising ingress port information of the virtual switching node or egress port information of the virtual switching node; determining time information of a user terminal according to the egress port information of the virtual switching node or the ingress port information of the virtual switching node; determining a scheduling rule of the access network device and / or time delay information between the user terminal and the access device according to the time information of the user terminal and a scheduling capability of the access network device; and performing transmission according to the scheduling rule of the access network device and / or the time delay information between the user terminal and the access device. By using the embodiment of the application, the scheduling rules of various user plane nodes can be determined, so that the user plane nodes can transmit TSN flows according to the respective scheduling rules, thereby realizing deterministic transmission of a 5G system.

Description

Technical Field

[0001] This application relates to the field of communication technology, specifically to a method and apparatus for determining scheduling rules. Background Technology

[0002] Time-sensitive networking (TSN) enables Ethernet to achieve real-time and deterministic transmission, ensuring the reliability of time-sensitive service data transmission and predicting end-to-end transmission latency. TSN overcomes the shortcomings of traditional Ethernet in providing high reliability and guaranteeing latency, meeting the needs of fields such as automotive control and the Industrial Internet. A TSN consists of switching nodes (bridges) and data terminals (end stations). Data terminals are used to send or receive TSN streams and can be divided into talkers and listeners. Switching nodes identify TSN streams using their destination media access control (MAC) address, reserve resources according to the latency requirements of the TSN streams, and schedule and forward TSN streams according to the scheduling rules issued by the control plane network elements of the TSN system. Each switching node in the TSN system receives and sends TSN streams within a specified time window on its designated port, achieving precise scheduling. Each switching node on the forwarding path of the TSN stream strictly executes the scheduling rules, thus achieving end-to-end deterministic transmission.

[0003] In order to achieve fifth-generation mobile communication (5G) thIn 5G systems, to achieve end-to-end deterministic transmission, this paper proposes the hypothesis that the 5G system can be virtualized as a switching node in a TSN system, and that the switching node functions within the TSN can be implemented. Specifically, based on the current 5G network architecture, a control plane with TSN adaptation functions is added to the application function (AF) network elements, and a user plane with TSN adaptation functions is added to the user plane function (UPF) network elements and user equipment (UE) network elements. These three elements, together with the 5G system, form a logical switching node (logical bridge or virtual bridge, the name is not limited here), i.e., a virtual switching node, which serves as the switching node in the TSN. 5G systems utilize Quality of Service (QoS) mechanisms to control data flow forwarding. For example, they define packet delay budgets (PDBs), which set the maximum delay budget for data flows transmitted between user plane nodes (including UEs, access network devices, and UPF elements). For instance, the maximum delay budget for data flows between a UE and a UPF element might be PDB1, or PDB2 between a UE and an access network device, and PDB3 between an access network device and a UPF element. The policy control function (PCF) element in the 5G system generates QoS configuration information, which includes the PDBs between user plane nodes. The PCF element then distributes this QoS configuration information to the user plane nodes. When forwarding data flows corresponding to this QoS configuration information, the user plane nodes adhere to the PDB constraints, ensuring that the data flow transmission delay is less than the PDB, thereby guaranteeing that the end-to-end transmission delay is less than the maximum allowed delay.

[0004] The 5G system is virtualized as a switching node in the TSN system. The control plane network elements in the TSN system generate scheduling rules for this virtual switching node and distribute these rules to it. This ensures that the virtual switching node receives TSN streams within a specified time window at the ingress port and transmits TSN streams within a specified time window at the egress port, ensuring that the transmission latency of the TSN stream in the 5G system is neither greater than the maximum latency nor less than the minimum latency. When forwarding TSN streams, the TSN stream passes through the UE, access network equipment, and UPF network elements, each of which has its own transmission and scheduling latency. To ensure the forwarding latency of TSN streams in the 5G system, the user plane nodes of the 5G system need to decompose the scheduling rules of the virtual switching node to determine the scheduling rules for each user plane node. However, currently, only the scheme of using the 5G system as a virtual switching node has been proposed; a specific scheme for determining the scheduling rules for each user plane node has not been provided. Therefore, how to determine the scheduling rules for each user plane node is a technical problem that urgently needs to be solved. Summary of the Invention

[0005] The technical problem to be solved by the embodiments of this application is to provide a scheduling rule determination method and apparatus, which can determine the scheduling rules of each user plane node so that each user plane node can transmit TSN streams according to its own scheduling rules, thereby realizing deterministic transmission of 5G system.

[0006] The first aspect of this application provides a method for determining scheduling rules, including:

[0007] The access network device receives port information from the virtual switching node of the session management network element. The port information of the virtual switching node includes the ingress port information or the egress port information of the virtual switching node.

[0008] The access network device determines the user terminal's time information based on the outgoing port information or the incoming port information of the virtual switching node.

[0009] The access network device determines its scheduling rules and / or the latency information between the user terminal and the access network device based on the user terminal's time information and the access network device's scheduling capabilities.

[0010] Access network devices transmit data according to their scheduling rules and / or latency information between user terminals and access devices.

[0011] In a first aspect of this application, the access network device determines its scheduling rules and / or latency information between the user terminal and the access network device based on the user terminal's time information and its scheduling capabilities. The access network device's scheduling rules are used to limit the time information for sending and receiving messages. The latency information between the user terminal and the access network device is used to limit the time information for transmitting messages between the user terminal and the access network device. After determining the access network device's scheduling rules, the user terminal's scheduling rules can be determined. The user plane network elements can then determine their own scheduling rules, thereby determining the scheduling rules for each user plane node. This allows each user plane node to transmit TSN streams according to its respective scheduling rules, thus achieving deterministic transmission in the 5G system.

[0012] The user terminal's time information refers to the time when the user terminal, acting as the ingress port of the virtual switching node, receives packets, or the time when the user terminal, acting as the egress port of the virtual switching node, sends packets. For downlink transmission, it refers to the time when the user terminal, acting as the egress port of the virtual switching node, sends packets; for uplink transmission, it refers to the time when the user terminal, acting as the ingress port of the virtual switching node, receives packets.

[0013] In one possible implementation, the outgoing port information of the aforementioned virtual switching node includes the time information of the user terminal as the outgoing port of the virtual switching node. This method corresponds to downlink transmission. The access network device uses the time information of the user terminal as the outgoing port of the virtual switching node as the user terminal's time information. Therefore, the user terminal's time information is the time information of the user terminal sending messages as the outgoing port of the virtual switching node.

[0014] In one possible implementation, the outgoing port information of the aforementioned virtual switching node includes the time information of the user plane network element as the outgoing port of the virtual switching node. This method corresponds to uplink transmission. The access network device determines the time information of the user terminal based on the time information of the user plane network element as the outgoing port of the virtual switching node and the latency information of the virtual switching node. Then, the time information of the user terminal is the time information of the user terminal as the incoming port of the virtual switching node when receiving packets.

[0015] In one possible implementation, the access network device receives latency information from the virtual switching node of the session management network element.

[0016] In one possible implementation, the ingress port information of the aforementioned virtual switching node includes the time information of the user terminal as the ingress port of the virtual switching node. This method corresponds to uplink transmission. The access network device uses the time information of the user terminal as the ingress port of the virtual switching node as the user terminal's time information. Therefore, the user terminal's time information is the time information of the user terminal receiving packets as the ingress port of the virtual switching node.

[0017] In one possible implementation, the access network device receives clock domain offset information from the session management network element and determines the time information of the user terminal corresponding to the 5G clock domain based on the clock domain offset information. The port information of the virtual switching node received by the access network device from the session management network element may correspond to the TSN clock domain or the 5G clock domain. If it corresponds to the 5G clock domain, the access network device needs to determine the time information of the user terminal corresponding to the 5G clock domain based on the clock domain offset information. The access network device can also determine the ingress port information or egress port information corresponding to the 5G clock domain based on the clock domain offset information.

[0018] A second aspect of this application provides a method for determining scheduling rules, including:

[0019] The session management network element receives the scheduling rules of the virtual switching node, which include the outgoing port information of the virtual switching node;

[0020] The session management network element sends the port information of the virtual switching node to the access network device. The port information of the virtual switching node includes the outgoing port information or the incoming port information of the virtual switching node.

[0021] In a second aspect of the embodiments of this application, the session management network element sends the port information of the virtual switching node to the access network device so that the access network device can determine the scheduling rules of the access network device and / or the latency information between the user terminal and the access network device.

[0022] In one possible implementation, for uplink transmission, the outgoing port information of the virtual switching node includes the time information of the user plane network element as the outgoing port of the virtual switching node; the port information of the virtual switching node includes the incoming port information of the virtual switching node, and the incoming port information of the virtual switching node includes the time information of the user terminal as the incoming port of the virtual switching node.

[0023] The session management network element determines the time information of the user terminal as the ingress port of the virtual switching node based on the time information of the user plane network element as the egress port of the virtual switching node and the latency information of the virtual switching node.

[0024] In one possible implementation, for downlink transmission, the outgoing port information of the aforementioned virtual switching node includes the time information of the user terminal acting as the outgoing port of the virtual switching node, and the port information of the virtual switching node includes the outgoing port information of the virtual switching node.

[0025] In one possible implementation, for uplink transmission, the outgoing port information of the aforementioned virtual switching node includes the time information of the user plane network element as the outgoing port of the virtual switching node, and the port information of the virtual switching node includes the outgoing port information of the virtual switching node.

[0026] In one possible implementation, the session management network element sends port information and clock domain offset information of the virtual switching node corresponding to the TSN clock domain to the access network device. The clock domain offset information is the offset between the TSN clock domain and the 5G clock domain. If the session management network element sends the port information of the virtual switching node corresponding to the TSN clock domain to the access network device, the access network device needs to determine the port information of the virtual switching node corresponding to the 5G clock domain. The access network device can determine the port information of the virtual switching node corresponding to the 5G clock domain based on the clock domain offset information.

[0027] In one possible implementation, the session management network element sends port information of the virtual switching node corresponding to the 5G clock domain to the access network device.

[0028] In one possible implementation, the outgoing port information of the virtual switching node included in the scheduling rules of the aforementioned virtual switching node corresponds to the TSN clock domain. The session management network element can determine the port information of the virtual switching node corresponding to the 5G clock domain in two ways:

[0029] Method a: The session management network element obtains the clock domain offset information between the TSN clock domain and the 5G clock domain from the user plane network element; based on the clock domain offset information, it determines the port information of the virtual switching node corresponding to the 5G clock domain.

[0030] In method b, the session management network element obtains the outgoing port information included in the scheduling rules of the virtual switching node corresponding to the 5G clock domain from the user plane network element; and determines the port information of the virtual switching node corresponding to the 5G clock domain based on the outgoing port information included in the scheduling rules of the virtual switching node corresponding to the 5G clock domain.

[0031] In one possible implementation, the session management network element sends the latency information of the virtual switching node to the access network device so that the access network device can determine the time information of the user terminal as the ingress port of the virtual switching node during uplink transmission.

[0032] A third aspect of this application provides a scheduling rule determination system, including an access network device provided in the first aspect and a session management network element provided in the second aspect. For details, please refer to the steps performed by the access network device in the first aspect and the steps performed by the session management network element in the second aspect.

[0033] A fourth aspect of this application provides a method for determining scheduling rules, including:

[0034] The access network device receives latency information and first latency information from the virtual switching node of the session management network element. The first latency information includes latency information between the user plane network element and the access network device.

[0035] The access network device determines the first scheduling rule based on the latency information of the virtual switching node, the first latency information, and the scheduling capability of the access network device. The first scheduling rule includes the first latency reservation between the access network device and the user terminal.

[0036] The access network equipment determines the second scheduling rule based on the first scheduling rule and the latency information of the virtual switching node. The second scheduling rule includes a second latency reservation between the user plane network element and the access network equipment.

[0037] Access network equipment performs deterministic transmission based on the second delay reservation.

[0038] In a fourth aspect of the embodiments of this application, the access network device determines a first delay reservation and a second delay reservation based on the delay information of the virtual switching node and the first delay information, and performs deterministic transmission based on the second delay reservation, thereby realizing deterministic transmission of the 5G system.

[0039] In one possible implementation, the access network device determines a delay information from the second delay information, which includes the delay information between the access network device and the user terminal; calculates the delay difference between the delay information of the virtual switching node and the delay information; if the delay difference is within the range of the first delay information, the delay information is reserved as the first delay.

[0040] In one possible implementation, the access network device sends a first delay reservation and / or a second delay reservation to the session management network element, and the session management network element sends the first delay reservation and / or the second delay reservation to the user plane network element, so that the user plane network element can perform deterministic transmission.

[0041] A fifth aspect of this application provides a method for determining scheduling rules, including:

[0042] The session management network element sends the latency information of the virtual switching node and the first latency information to the access network device. The first latency information includes the latency information between the user plane network element and the access network device. The latency information of the virtual switching node and the first latency information are used by the access network device to determine the first scheduling rule and / or the second scheduling rule. The first scheduling rule includes the first latency reservation between the access network device and the user terminal, and the second scheduling rule includes the second latency reservation between the user plane network element and the access network device.

[0043] The session management network element receives a first delay reservation and / or a second delay reservation from the access network device;

[0044] The session management network element sends a second delay reservation to the user plane network element. The second delay reservation is used by the user plane network element for deterministic transmission.

[0045] In a fifth aspect of the embodiments of this application, the session management network element sends a virtual switching node and delay information and a first delay information to the access network device so that the access network device can determine a second delay reservation and perform deterministic transmission based on the second delay reservation. The session management network element sends the second delay reservation to the user plane network element so that the user plane network element can perform deterministic transmission based on the second delay reservation, thereby realizing deterministic transmission in the 5G system.

[0046] In one possible implementation, if the session management network element receives a first delay reservation from the access network device, then the session management network element determines a second delay reservation based on the first delay reservation and the delay information of the virtual switching node.

[0047] In one possible implementation, the session management network element sends the port information of the virtual switching node at the user terminal to the user terminal. The port information of the virtual switching node at the user terminal is used by the user terminal to perform deterministic transmission, so as to realize the deterministic transmission of the user terminal.

[0048] The sixth aspect of this application provides a scheduling rule determination system, including an access network device provided in the third aspect and a session management network element provided in the fourth aspect. For details, please refer to the steps performed by the access network device in the third aspect and the steps performed by the session management network element in the fourth aspect.

[0049] A seventh aspect of this application provides a method for determining scheduling rules, including:

[0050] The access network equipment receives the reserved scheduling interval from the access network equipment of the session management network element;

[0051] The access network equipment determines its scheduling rules based on its reserved scheduling range and scheduling capabilities.

[0052] Access network equipment performs deterministic transmission according to the access network equipment scheduling rules.

[0053] In a seventh aspect of this application, the access network device determines the scheduling rules of the access network device based on the reserved scheduling interval of the access network device sent by the session management network element, and performs deterministic transmission according to the scheduling rules of the access network device, thereby realizing deterministic transmission of the 5G system.

[0054] In one possible implementation, the reserved scheduling interval of the access network device includes the time information for the reserved transmission and reception of messages by the access network device, and the scheduling rules of the access network device include the time information for limiting the transmission and reception of messages by the access network device.

[0055] In one possible implementation, the reserved scheduling interval of the access network device also includes the time information for the reserved sending and receiving of messages by the user terminal, and the scheduling rules of the access network device include the time information for limiting the sending and receiving of messages by the user terminal.

[0056] In one possible implementation, the access network device sends its scheduling rules to the session management network element, so that the session management network element can send the access network device's scheduling rules to the user plane network element, enabling the user plane network element to determine its own scheduling rules and perform deterministic transmission.

[0057] The eighth aspect of this application provides a method for determining scheduling rules, including:

[0058] The session management network element determines the reserved scheduling interval for access network equipment;

[0059] The session management network element sends the reserved scheduling interval of the access network device to the access network device.

[0060] In an eighth aspect of this application, the session management network element sends a reserved scheduling interval of the access network device to the access network device so that the access network device can determine the scheduling rules of the access network device and perform deterministic transmission.

[0061] In one possible implementation, the reserved scheduling interval of the access network device includes the time information for the reserved transmission and reception of messages by the access network device; the session management network element determines the time information for the reserved transmission and reception of downlink messages by the access network device based on the scheduling rules of the virtual switching node and the latency information between the user plane network element and the access network device.

[0062] In one possible implementation, the reserved scheduling interval of the access network device includes the time information for the reserved sending and receiving of messages by the user terminal; the session management network element determines the time information for the reserved sending and receiving of messages by the user terminal based on the scheduling rules of the virtual switching node and the internal processing delay of the user terminal.

[0063] In one possible implementation, the session management network element receives scheduling rules from the access network device and sends these rules to the user plane network element so that the user plane network element can determine its own scheduling rules and perform deterministic transmission.

[0064] The ninth aspect of this application provides a deterministic transmission system, including an access network device provided in the seventh aspect and a session management network element provided in the eighth aspect. For details, please refer to the steps performed by the access network device in the seventh aspect and the steps performed by the session management network element in the eighth aspect.

[0065] A tenth aspect of this application provides an access network device that has the function of implementing the methods provided in the first, fourth, or seventh aspects. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0066] In one possible implementation, the access network device includes: a processing unit and a transceiver unit; the transceiver unit is configured to receive port information from a virtual switching node of a session management network element, the port information of the virtual switching node including ingress port information or egress port information of the virtual switching node; the processing unit is configured to determine the time information of the user terminal based on the egress port information or the ingress port information of the virtual switching node; determine the scheduling rules of the access network device and / or the latency information between the user terminal and the access network device based on the time information of the user terminal and the scheduling capability of the access network device; and perform transmission according to the scheduling rules of the access network device and / or the latency information between the user terminal and the access device.

[0067] In one possible implementation, the access network device includes a processor, a transceiver, and a memory. The memory stores a computer program, which includes program instructions. The processor is configured to call the program code to perform the following operations: control the transceiver to receive port information from a virtual switching node of a session management network element, the port information of which includes either the incoming port information or the outgoing port information of the virtual switching node; determine the time information of the user terminal based on the outgoing port information or the incoming port information of the virtual switching node; determine the scheduling rules of the access network device and / or the latency information between the user terminal and the access network device based on the time information of the user terminal and the scheduling capability of the access network device; and perform transmission according to the scheduling rules of the access network device and / or the latency information between the user terminal and the access device.

[0068] Based on the same inventive concept, since the principle of the access network device in solving the problem and its beneficial effects can be found in the methods described in the first aspect, the fourth aspect or the seventh aspect and the beneficial effects they bring, the implementation of the device can be found in the implementation of the method, and repeated details will not be repeated.

[0069] The eleventh aspect of this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods described in the first, fourth, or seventh aspects above.

[0070] The twelfth aspect of this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods described in the first, fourth, or seventh aspects above.

[0071] A thirteenth aspect of this application provides a session management network element that has the function of implementing the methods provided in the second, fifth, or eighth aspects. The function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0072] In one possible implementation, the session management network element includes: a processing unit and a transceiver unit; the transceiver unit is used to receive the scheduling rules of the virtual switching node, the scheduling rules of the virtual switching node including the outgoing port information of the virtual switching node; and to send the port information of the virtual switching node to the access network device, the port information of the virtual switching node including the outgoing port information or the incoming port information of the virtual switching node.

[0073] In one possible implementation, the session management network element includes a processor, a transceiver, and a memory, wherein the memory stores a computer program, which includes program instructions, and the processor is configured to call the program code to perform the following operations: controlling the transceiver to receive scheduling rules for the virtual switching node, the scheduling rules for the virtual switching node including the outgoing port information of the virtual switching node; and controlling the transceiver to send port information of the virtual switching node to the access network device, the port information of the virtual switching node including either the outgoing port information or the incoming port information of the virtual switching node.

[0074] Based on the same inventive concept, since the principle of the session management network element in solving the problem and its beneficial effects can be found in the methods described in the second, fifth or eighth aspects and the beneficial effects they bring, the implementation of the device can be found in the implementation of the method, and repeated details will not be repeated.

[0075] The fourteenth aspect of this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the methods described in the second, fifth, or eighth aspects described above.

[0076] The fifteenth aspect of this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods described in the second, fifth, or eighth aspects described above. Attached Figure Description

[0077] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0078] Figure 1 This is a schematic diagram of the network architecture of a 5G system.

[0079] Figure 2 This is a schematic diagram of the network topology of the TSN system;

[0080] Figure 3 This is a schematic diagram of the centralized management architecture of the TSN system;

[0081] Figure 4a This is a schematic diagram of a network architecture that virtualizes a 5G system as a switching node in a TSN.

[0082] Figure 4b This is a schematic diagram of the network architecture for applying embodiments of this application;

[0083] Figure 5 A schematic diagram illustrating the latency information of each user plane node provided in the embodiments of this application;

[0084] Figure 6 This is a flowchart illustrating the process of reporting latency information provided in an embodiment of this application.

[0085] Figure 7 A flowchart illustrating the scheduling rule determination method provided in Embodiment 1 of this application;

[0086] Figure 8 A flowchart illustrating the scheduling rule determination method provided in Embodiment 2 of this application;

[0087] Figure 9 A flowchart illustrating the scheduling rule determination method provided in Embodiment 3 of this application;

[0088] Figure 10 A flowchart illustrating the scheduling rule determination method provided in Embodiment 4 of this application;

[0089] Figure 11A schematic diagram of the logical structure of the communication device provided in the embodiments of this application;

[0090] Figure 12 This is a simplified schematic diagram of the physical structure of the communication device provided in the embodiments of this application. Detailed Implementation

[0091] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0092] Furthermore, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0093] The user terminals involved in the embodiments of this application may include various handheld devices, vehicle-mounted devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities; they may also include UEs, subscriber units, cellular phones, smartphones, wireless data cards, personal digital assistant (PDA) computers, tablet computers, wireless modems, handheld devices, laptop computers, cordless phones, wireless local loop (WLL) stations, machine type communication (MTC) terminals, UEs, mobile stations (MS), terminal devices, or relay user equipment, etc. Among them, relay user equipment may be, for example, a 5G residential gateway (RG). For ease of description, in the embodiments of this application, the devices mentioned above are collectively referred to as user terminals, and the user terminal is described using a UE as an example.

[0094] Please see Figure 1 This is a schematic diagram of the network architecture of a 5G system, which includes UE, access network (AN) equipment, and core network elements.

[0095] The access network equipment can also be a radio access network (RAN) equipment.

[0096] The core network elements may include the following: UPF, data network (DN), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), network slice selection function (NSSF), network exposure function (NEF), network function repository function (NRF), policy control function (PCF), unified data management (UDM), and AF.

[0097] Core network elements can be divided into control plane network elements and user plane network elements. User plane network elements, also known as UPF network elements, are mainly responsible for packet forwarding, quality of service (QoS) control, and billing information statistics. Control plane network elements are mainly responsible for service process interaction, issuing packet forwarding policies and QoS control policies to the user plane, etc. The control plane network elements involved in the embodiments of this application mainly include the following network elements: AMF, SMF, PCF, AF, and NEF.

[0098] Among them, the AMF network element is mainly responsible for user access and mobility management. The SMF network element is responsible for managing the creation and deletion of user PDU sessions, and maintaining PDU session context and user plane forwarding pipeline information. The PCF network element is used to generate and manage user, session, and QoS flow processing policies. The AF network element is a functional network element that provides various service functions, can interact with the core network through the NEF network element, and can interact with the policy management framework for policy management. The NEF network element is used to provide frameworks, authentication, and interfaces related to network capability exposure, and to transmit information between 5G system network functions and other network functions.

[0099] Figure 1The network architecture shown also indicates the communication interfaces between various network elements. The communication interfaces involved in this application embodiment include: N1, the communication interface between the UE and the core network control plane AMF network element, used to transmit non-access stratum (NAS) signaling; N2, the communication interface between the access network device and the AMF network element; N3, the communication interface between the access network device and the core network user plane UPF network element, used to transmit user data; and N4, the communication interface between the core network control plane SMF network element and the UPF network element, used to configure policies for the UPF network element, etc.

[0100] The access network equipment involved in the embodiments of this application can be an AN device or a RAN device, and can be an access network device in a 5G system, such as a gNB, or an access network device in a future communication system; the session management network element can be an SMF network element or a network element in a future communication system that has the same function as an SMF network element; the user plane function network element can be a UPF network element or a network element in a future communication system that has the same function as a UPF network element; the application function network element can be an AF network element or a network element that has the same function as an AF network element; the policy management network element can be a PCF network element or a network element that has the same function as a PCF network element.

[0101] Please see Figure 2 This is a schematic diagram of the network topology of a TSN system, using four audio-video bridging (AVB) domains as an example. AVB can also be referred to as TSN. Figure 2 The AVB field shown is also the TSN field.

[0102] TSN is based on Layer 2 transport and includes switching nodes and data terminals. Unlike link-layer Layer 2 switching, which uses Media Access Control (MAC) addresses for forwarding and obtains forwarding ports by consulting a MAC address learning table, TSN switching nodes do not forward TSN streams based on MAC address learning tables. Instead, they forward TSN streams according to scheduling rules configured or created on the switching nodes. The TSN standard defines the behavior of data terminals and switching nodes, as well as the scheduling method for switching nodes to forward TSN streams, thereby achieving reliable and low-latency transmission. Switching nodes in TSN identify TSN streams using their destination MAC address or other characteristics, and reserve resources and plan scheduling based on the latency requirements of the TSN streams, thus ensuring reliability and transmission latency according to the generated scheduling policy.

[0103] In this context, "data terminal" refers to the sender and receiver of a TSN stream. Specifically, the sender of a TSN stream can be called the "talker," and the receiver can be called the "listener." An AVB domain boundary port refers to a port within one AVB domain that connects to a switching node or data terminal in another AVB domain. For example, AVB domain 1 may have two AVB domain boundary ports: one connecting to switching node 2 in AVB domain 2, and the other connecting to switching node 5 in AVB domain 3. TSN streams do not flow into AVB domain boundary ports. It can be understood that TSN streams only circulate within switching nodes and data terminals within an AVB domain. Therefore, between AVB domain boundary ports, the local area network (LAN) carries non-AVB traffic; within the same AVB domain, the LAN carries AVB traffic.

[0104] Please see Figure 3 This diagram illustrates the centralized management architecture of a TSN system. This centralized management architecture is one of the three architectures defined in the 802.1qcc standard of TSN. It includes a transmitter, a receiver, switching nodes, a centralized network configuration (CNC) network element, and a centralized user configuration (CUC) network element. It should be noted that... Figure 3 The number and form of the network elements shown do not constitute a limitation on the embodiments of this application. Figure 3 Taking one sender, one receiver, and three switching nodes as an example, practical applications may include multiple senders, multiple receivers, or one switching node, etc.

[0105] The switching nodes reserve resources for TSN flows according to the TSN standard definition and schedule and forward TSN flows.

[0106] The CNC network element is responsible for managing the topology of the TSN system user plane (including data terminals and various switching nodes) and the capability information of each switching node. Based on the TSN flow creation request provided by the CNC network element, it creates TSN flows; based on the maintenance, topology, and switching node capability information, it calculates and generates the forwarding path of the TSN flow, as well as the scheduling rules for each switching node along the forwarding path; then, it distributes the scheduling rules on the switching nodes to the corresponding switching nodes. The capability information of a switching node may include, for example, the transmission latency and the internal processing latency between switching node ports. The transmission latency refers to the time elapsed from when the TSN flow is sent from the port of this switching node to when the TSN flow arrives at the port of the other switching node; the internal processing latency refers to the time elapsed from when the TSN flow enters from one port of this switching node to when it is sent from another port of this switching node. The scheduling rules of a switching node may include, for example, the ports for sending and receiving TSN flows and time slices. The time slice refers to the time information for when a switching node sends and receives TSN flow packets, such as receiving TSN flow packets between time t1 and t2, and sending TSN flow packets between time t3 and t4.

[0107] The CUC network element is used to collect TSN stream creation requests from data terminals. After matching the requests from the sending and receiving ends, it requests the creation of a TSN stream from the CNC network element and confirms the scheduling rules generated by the CNC network element. Matching the requests from the sending and receiving ends refers to the TSN stream creation requests sent by each end to the CUC network element. These requests include information such as the destination MAC address of the requested TSN stream. The CUC network element matches these TSN stream creation requests with the destination MAC addresses of TSN stream requests from different data terminals. If the destination MAC addresses of the TSN stream requests from two data terminals are the same, then the same TSN stream is successfully matched, and the CNC network element can create the TSN stream. Otherwise, if only the sending or receiving end has a TSN stream creation request, the CUC network element cannot request the creation of a TSN stream from the CNC network element, and therefore the CNC network element cannot create the TSN stream.

[0108] It is understandable that CNC network elements and CUC network elements are control plane network elements in the TSN system.

[0109] Figure 3The centralized management architecture shown, combined with the 802.1qbv scheduling algorithm defined by the TSN system, enables end-to-end deterministic transmission when the switching nodes and data terminals in the TSN system are synchronized. The CNC network element generates scheduling rules for each switching node on the forwarding path and sends these rules to the corresponding switching nodes. The scheduling rules include the egress port of the TSN flow or traffic class on that switching node, the time window (t3, t4) for sending packets at the egress port, and / or the ingress port and the time window (t1, t2) for receiving packets at the ingress port. Each switching node sends packets within the specified time window on the specified port according to the scheduling rules issued by the CNC network element, and optionally receives packets within the specified time window on the specified port, achieving precise scheduling. Each switching node on the TSN flow forwarding path strictly executes its own scheduling rules, thus achieving end-to-end deterministic transmission.

[0110] In order to achieve fifth-generation mobile communication (5G) th In 5G (Transmission over Generation) systems, to achieve end-to-end deterministic transmission, the hypothesis is proposed that the 5G system can be virtualized as a switching node in a TSN (Transmission over Networking System) and realize the functions of a switching node in a TSN. See details in [link to relevant documentation]. Figure 4a The network architecture diagram shows a control plane with TSN adaptation added to the AF network element, a user plane (UP) with TSN adaptation added to the UPF network element, and a UP2 with TSN adaptation added to the UE. These three, together with the 5G system, form a logical switching node, i.e., a virtual switching node, which serves as the switching node in TSN. Although Figure 4a In the diagram, UPF and UP1, UE and UP2 are drawn separately, but in reality, UP1 and UP2 are logical functions of the user plane TSN adaptation function. UP1 can be deployed on the UPF network element, or UP1 can be an internal functional module of the UPF network element; similarly, UP2 can be deployed on the UE, or UP2 can be an internal functional module of the UE.

[0111] Among them, the TSN adaptation function refers to adapting the characteristics and information of the 5G network into the information required by the TSN, and communicating with the network elements in the TSN through the interface defined by the TSN.

[0112] In this system, the AF network element and the CNC network element in the TSN system interact to transmit information. For example, the CNC network element sends the scheduling rules of the TSN stream on the virtual switching node to the AF network element.

[0113] Please see Figure 4b This is a schematic diagram of the network architecture applied in the embodiments of this application. Figure 4bIn this process, the 5G system is virtualized as a switching node in the TSN system. The ports of this virtual switching node include virtual ports on the UE side and ports on the UPF side. This virtual switching node includes UE, (R)AN, UPF network elements and AF network elements.

[0114] In the embodiments of this application, the virtual ports on the UE side included in the virtual switching node can be based on UE granularity, i.e., one UE corresponds to one virtual port, and different UEs correspond to different virtual ports; they can also be based on PDU session granularity, i.e., one PDU session corresponds to one virtual port, and different PDU sessions correspond to different virtual ports; or they can be based on TSN granularity, i.e., one TSN domain corresponds to one or more virtual ports. The virtual ports on the UE side can also be physical ports on the UE side, and can include one or more physical ports on the UE side. Therefore, a UE can include one or more virtual ports. Figure 4b The illustration shows a virtual port of the UE, which does not constitute a limitation on the embodiments of this application. In actual applications, there may be multiple UEs. If it is based on UE granularity, then the virtual switching node on the UE side may include multiple virtual ports.

[0115] In the embodiments of this application, the ports on the UPF side of the virtual switching node are the actual physical ports of the UPF network element. A UPF network element may include multiple physical ports. One physical port of the UPF network element corresponds to one virtual switching node. However, a virtual switching node may include multiple physical ports of one UPF network element, or multiple physical ports of multiple UPF network elements. Figure 4b The virtual switching node shown includes a UPF network element, which includes three physical ports. These three physical ports correspond to the same virtual switching node, but this is not intended to limit the embodiments of this application. In actual applications, a virtual switching node may include more than one UPF network element, and the ports on the UPF side of the virtual switching node may include more than one physical port of a UPF network element.

[0116] Figure 4b In this context, the user plane with TSN adaptation functionality deployed on the UE, or the user plane with TSN adaptation functionality, is an internal functional module of the UE. Figure 4a UP2 in the UPF is used to obtain the attribute information of the virtual port on the UE side and send it to the AF network element through the user plane or control plane. The attribute information of the virtual port may include the external topology information corresponding to the virtual port and the external transmission delay of the virtual port (i.e., the transmission delay on the UE side). Similarly, the user plane with TSN adaptation function deployed on the UPF or the user plane with TSN adaptation function is an internal functional module of the UPF, i.e. Figure 4aUP1 in the diagram is used to obtain the attribute information of the physical port on the UPF side and send it to the AF network element through the user plane or control plane. It can also interact with the AF network element to exchange user plane-related information and TSN parameter-related information. The attribute information of the physical port can include the external topology information corresponding to the physical port and the external transmission delay of the physical port (i.e., the transmission delay on the UPF side).

[0117] Figure 4b In this context, AF network element is a logical network element, which can be a component within another logical network element (such as a component within an SMF network element) or another control plane functional network element. Its name is not limited here.

[0118] Figure 4b In this context, the processing delay between the virtual port on the UE side and the port on the UPF side is called the internal processing delay. The internal processing delay is specific to the port pair. Different port pairs may have different internal processing delays. For example, the internal processing delay 1 between virtual port 1 and physical port 1, and the internal processing delay 2 between virtual port 1 and physical port 2 may have different values.

[0119] Figure 4b In this context, equipment 1 and equipment 2 can be equivalent to... Figure 2 The data terminal in the middle can also be equivalent to Figure 3 The device is either the sending or receiving end. Device 1 is connected to a virtual port on the UE side. This connection can be a physical link or a virtual connection (e.g., device 1 is a processing unit within the device where the UE is located); device 1 can be other terminal devices besides the UE, or it can be a switching node. Figure 4b Device 1 shown interacts with CUC network elements as a terminal device. If device 1 is a switching node, then device 1 interacts with CNC network elements (similar to...). Figure 4b (The switching node shown is connected to the UPF network element). Figure 4b The device 2 shown interacts with the CUC network element as a terminal device. Device 2 is not directly connected to the physical port of the UPF network element; it also includes a switching node between itself and the virtual switching node. This switching node can be an actual switching node in the TSN, such as a switching node in a data network (DN), or another virtual switching node. Device 2 can also be directly connected to the physical port of the UPF network element. This application does not limit the definition of each network element or the interaction method; for example, it does not limit whether there is a CUC network element or whether the terminal device interacts with the CUC network element.

[0120] Currently, 5G systems define a Programmable Data Base (PDB) to limit the maximum latency budget for data streams transmitted between user plane nodes, ensuring that the data stream transmission latency is less than the PDB, thereby guaranteeing that the end-to-end transmission latency is less than the maximum allowed latency. However, as a virtual switching node in a TSN system, the 5G system forwards TSN streams, which pass through UE, (R)AN, and UPF network elements. These user plane nodes each have their own transmission and scheduling latency. To ensure the forwarding latency of TSN streams in the 5G system, the user plane nodes of the 5G system need to decompose the scheduling rules of this virtual switching node to determine the scheduling rules for each user plane node. However, currently, only the scheme of using the 5G system as a virtual switching node has been proposed, without providing a specific scheme for determining the scheduling rules for each user plane node. Therefore, how to determine the scheduling rules for each user plane node is a technical problem that urgently needs to be solved.

[0121] In view of this, embodiments of this application provide a scheduling rule determination method and apparatus, which can determine the scheduling rules of each user plane node so that each user plane node can transmit TSN streams according to its own scheduling rules, thereby realizing deterministic transmission of the 5G system.

[0122] Please see Figure 5 This is a schematic diagram illustrating the latency information of each user plane node provided in the embodiments of this application. Figure 5 The delay information shown is exemplified by downlink transmission. The time window for receiving packets at the ingress port of the UPF network element is (t1, t2), and the time window for sending packets at the egress port of the UPF network element is (t5, t6). The time window for receiving packets at the ingress port of the (R)AN is (t7, t8), and the time window for sending packets at the egress port of the (R)AN is (t9, t10). The time window for sending packets at the egress port of the UE is (t11, t12), and the time window for sending packets at the egress port of the UE is (t3, t4). Figure 5 The latency segments can be unidirectional, meaning that for any given latency segment, the uplink latency and downlink latency are different. For example, for air interface forwarding latency, the uplink latency is not equal to the downlink latency. Figure 5 Each segment of delay represents the downlink delay; each segment of delay is also equivalent to the uplink delay information. For example, for the air interface forwarding delay, the uplink delay is equal to the downlink delay.

[0123] Figure 5 The system uses three methods to represent the latency information of each user plane node:

[0124] Method 1: The internal processing delay and forwarding delay of each user plane node are represented in segments. The delay between UPF and UE = UPF internal processing delay + N3 forwarding delay + access network internal processing delay + air interface forwarding delay + UE internal processing delay. Here, the UPF internal processing delay can be represented as UP_DELAY. The N3 forwarding delay refers to the forwarding delay between UPF and (R)AN, where N3 represents the interface between UPF and (R)AN, and can be represented as BH_DELAY. The access network internal processing delay can be represented as RAN_DELAY. The air interface forwarding delay refers to the forwarding delay between (R)AN and UE, and can be represented as AIR_DELAY. The UE internal processing delay can be represented as UE_DELAY. Internal processing delay refers to the time elapsed between a packet entering from one port of this user plane node and being sent from another port of the same user plane node. In other words, the delay between UPF and UE = UP_DELAY + BH_DELAY + RAN_DELAY + AIR_DELAY + UE_DELAY.

[0125] Method 2: The internal processing delay and forwarding delay of the UPF and (R)AN are represented together. The delay between the UPF and UE = UPF_N3_delay + Access Network_Air Interface_delay + UE_internal processing delay. Here, UPF_N3_delay refers to the sum of the forwarding delay between the UPF and (R)AN and the internal processing delay of the UPF, which can be represented as UP_BH_DELAY, UP_BH_DELAY = UP_DELAY + BH_DELAY. Access Network_Air Interface_delay refers to the sum of the air interface forwarding delay and the internal processing delay of (R)AN, which can be represented as RAN_AIR_DELAY, RAN_AIR_DELAY = RAN_DELAY + AIR_DELAY. The representation of the UE's internal processing delay can be found in Method 1. In other words, the delay between the UPF and UE = UP_BH_DELAY + RAN_AIR_DELAY + UE_DELAY.

[0126] Method 3: The delay between the UE and (R)AN is represented by a combined delay, where the delay between the UPF and the UE = UPF_N3_delay + Access Network_Air Interface_UE_delay. The meaning and representation of UPF_N3_delay can be found in Method 2. Access Network_Air Interface_UE_delay refers to the delay between the UE and (R)AN, which can be represented as RAN_AIR_UE_DELAY, where RAN_AIR_UE_DELAY = RAN_DELAY + AIR_DELAY + UE_DELAY. In other words, the delay between the UPF and the UE = UP_BH_DELAY + RAN_AIR_UE_DELAY.

[0127] It should be noted that the above three methods can be combined in combination. For example, the delay between UPF and (R)AN can be represented using method one, while the delay between (R)AN and UE can be represented using method three. In this case, the delay between UPF and UE = UP_DELAY + BH_DELAY + RAN_AIR_UE_DELAY. The values ​​of the above delay segments can be specific numerical values, such as a delay segment of 5ms. In this case, the maximum and minimum values ​​of this value will be the same in the following text. Alternatively, it can be a numerical range, such as a delay segment of 3ms to 6ms.

[0128] The terms or nouns used in the embodiments of this application will be introduced below.

[0129] Scheduling rules are used to limit the time information for switching nodes or user plane nodes to process packets. In this embodiment, the scheduling rules may include a time window, used to limit the sending and receiving of packets by switching nodes or user plane nodes within the time window; they may also include the timing of sending and receiving packets, used to limit user plane nodes to send and receive packets before the timing of sending and receiving packets or to limit user plane nodes to start sending and receiving packets at the timing of sending and receiving packets; and they may include delay reservation, which may be a time value range for a single user plane node, used to limit the sending and receiving of packets by that user plane node within that time value range, or it may be a time value range between two adjacent user plane nodes, where the processing time of these two user plane nodes is within that time value range.

[0130] In this embodiment of the application, scheduling capability refers to the time information that the user plane node itself can support for processing packets, such as the internal processing latency supported by the user plane node being 5ms to 7ms. Scheduling capability is related to the load and bandwidth of the user plane node; for the same user plane node, different loads will result in different scheduling capabilities.

[0131] The scheduling rule determination method provided in the embodiments of this application will be described in detail below. In the introduction of the scheduling rule determination method, the user terminal is UE, the session management network element is SMF, the user plane function network element is UPF, the application function network element is AF, and the access network device is RAN. For the sake of simplicity, the word "network element" is not shown in the corresponding figures of the embodiments, and the word "network element" is not mentioned in the specific description of the embodiments, but this does not affect the understanding of the embodiments of this application.

[0132] The introduction to the scheduling rule determination method uses downlink transmission as an example. This involves determining the scheduling rules for each user plane node on the downlink transmission path. These downlink scheduling rules can also be applied to uplink transmission; for example, the uplink delay of each segment equals the downlink delay. If the downlink scheduling rules for each user plane node are not applicable to uplink transmission (e.g., the uplink delay of each segment is not equal to the downlink delay), then the scheduling rules for each user plane node on the uplink transmission path are determined using a method similar to that used for downlink transmission.

[0133] It should be noted that the message names or parameter names between network elements in the following embodiments of this application are merely examples, and other names may be used in specific implementations. This application does not impose specific limitations on these names. In the flowcharts of this application, the AMF between the SMF and RAN is omitted. In reality, an AMF exists between the SMF and RAN, and the AMF forwards messages between the SMF and RAN.

[0134] The embodiments of this application are applied to Figure 4b Taking the network architecture diagram shown as an example, as Figure 6 The diagram shown is a flowchart illustrating the reporting delay information provided in an embodiment of this application, and may include, but is not limited to, the following steps:

[0135] In step S101, the UPF sends the first delay information to the SMF. Correspondingly, the SMF receives the first delay information from the UPF.

[0136] In Method 1, the first latency information may include the UPF's internal processing latency, i.e., UP_DELAY. The UPF can obtain UP_DELAY by measuring the QoS flow corresponding to the TSN flow, specifically the time it takes for the QoS flow to be received from the UPF's ingress port and sent from the UPF's egress port.

[0137] Method 2: The first latency information can include the internal processing latency of the UPF and the forwarding latency of N3, namely UP_DELAY and BH_DELAY. The UPF can obtain UP_DELAY by measuring the QoS flow corresponding to the TSN flow, measuring the time it takes for the QoS flow to be received from the UPF's ingress port and sent from the UPF's egress port; and obtain BH_DELAY by measuring the time it takes for the QoS flow to be sent from the UPF's egress port and received from the RAN's ingress port.

[0138] Method 3: The first delay information may include UPF_N3_delay, i.e., UP_BH_DELAY. UPF can obtain UP_BH_DELAY by measuring the QoS flow corresponding to the TSN flow and measuring the time taken for the QoS flow to be received from the ingress port of the UPF to the ingress port of the RAN.

[0139] The specific type of delay information included in the first delay information depends on the specific measurement conditions. The first delay information may also include access network_air interface_delay or access network_air interface_UE_delay, that is, it may also include RAN_AIR_DELAY or RAN_AIR_UE_DELAY. Which type it includes depends on the specific measurement conditions, and whether RAN_AIR_DELAY or RAN_AIR_UE_DELAY is included also depends on the specific measurement conditions.

[0140] The UPF can send the first delay information to the SMF via the N4 interface in either the N4 session creation response message or the N4 session modification response message. In other words, the first delay information is carried within either the N4 session creation response message or the N4 session modification response message. The N4 session creation response message or the N4 session modification response message can indicate which delay segment and the specific delay information are being carried through N4 interface information cells or QoS parameters. The N4 interface is the interface between the UPF and the SMF, and the N4 session is the session between the UPF and the SMF. The UPF can also send the first delay information directly to the SMF via the N4 interface alone; the N4 interface information cells can indicate which delay segment and the specific delay information are being carried.

[0141] In step S102, the RAN sends the second delay information to the SMF. Correspondingly, the SMF receives the second delay information from the RAN.

[0142] In Method 1, the second latency information includes the RAN's internal processing latency and the air interface forwarding latency, namely RAN_DELAY and AIR_DELAY. Similarly, the RAN can obtain RAN_DELAY and AIR_DELAY through measurement.

[0143] Method 2: The second delay information includes the access network air interface delay, specifically RAN_AIR_DELAY. Similarly, the RAN can obtain RAN_AIR_DELAY through measurement.

[0144] Method 3: The second delay information includes the access network air interface UE delay, specifically RAN_AIR_UE_DELAY. Similarly, the RAN can obtain RAN_AIR_UE_DELAY through measurement.

[0145] The second delay information may also include the forwarding delay of N3 and / or the forwarding delay of the air interface, that is, it may also include BH_DELAY and / or AIR_DELAY.

[0146] Step S102 is optional. Whether to execute step S102 and which types of delays the second delay information includes depends on the specific measurement and the first delay information reported by the UPF to the SMF. For example, if the first delay information only includes UP_DELAY, then step S102 is executed, and the second delay information must include BH_DELAY and any one of the three methods mentioned above. As another example, if the first delay information includes UP_BH_DELAY and RAN_AIR_UE_DELAY, then step S102 does not need to be executed.

[0147] When performing step S102, the RAN can send the second delay information to the SMF via the N2 interface in the N2 session creation response message or in the N2 session modification response message; that is, the second delay information is carried in the N2 session creation response message or the N2 session modification response message. The N2 session creation response message or the N2 session modification response message can indicate which delay segment and the specific delay information are carried through N2 interface information elements or QoS parameters. Messages between the RAN and the SMF are forwarded through the AMF; the N2 interface is the interface between the RAN and the AMF, and the N2 session is the session between the RAN and the SMF. The RAN can also send the second delay information to the SMF independently via the N2 interface; the N2 interface information element can indicate which delay segment and the specific delay information are carried.

[0148] In step S103, the UE sends third delay information to the SMF. Correspondingly, the SMF receives the third delay information from the UE.

[0149] The third delay information includes the UE's internal processing delay, specifically UE_DELAY. Step S103 is also optional; whether or not to execute step S103 depends on whether the content carried by the first and second delay information includes the UE's internal processing delay. For example, if the first or second delay information includes RAN_AIR_UE_DELAY, and RAN_AIR_UE_DELAY contains the UE's internal processing delay, then step S103 may not be executed.

[0150] When performing step S103, the UE can send third delay information to the SMF via a non-access stratum (NAS) message in the packet data unit (PDU) session creation request message, or in the PDU session modification request message. That is, the third delay information is carried within either the PDU session creation request message or the PDU session modification request message. The path for the UE to send the PDU session creation / modification request message to the SMF is: UE->RAN->AMF->SMF. The UE sends the PDU session creation / modification request message to the AMF via the RAN; this message is a NAS message. Then, the AMF forwards the PDU session creation / modification request message to the SMF.

[0151] Step S104: SMF determines the latency information of the virtual switching node.

[0152] The delays included in the first, second, and third delay information can be specific numerical values ​​or numerical ranges.

[0153] The Serving Module (SMM) determines the latency information of the 5G system as a virtual switching node based on at least one of the first, second, or third latency information. This latency information is the internal processing latency of the virtual switching node. For example, the first latency information includes UP_DELAY, the second latency information includes RAN_AIR_DELAY and BH_DELAY, and the third latency information includes UE_DELAY. The SMF adds these four latency segments to obtain the latency information of the virtual switching node. As another example, if the first latency information includes UP_BH_DELAY and RAN_AIR_UE_DELAY, the SMF can add these two latency segments to obtain the latency information of the virtual switching node. Similarly, if the first latency information includes UP_BH_DELAY and the second latency information includes RAN_AIR_UE_DELAY, the SMF adds these two latency segments to obtain the latency information of the virtual switching node.

[0154] SMF collects the latency of each segment and can decompose the scheduling rules of the virtual switching node based on the latency of each segment. The specific decomposition method will be described in detail in subsequent embodiments. The scheduling rules of the virtual switching node are generated by the CNC in the TSN system and distributed to the virtual switching node. The scheduling rules for the virtual switching node are used to limit the virtual switching node to receive packets within a specified time window on a specified ingress port and to send packets within a specified time window on a specified egress port.

[0155] In step S105, the SMF sends the latency information of the virtual switching node to the AF. Correspondingly, the AF receives the latency information of the virtual switching node from the SMF.

[0156] When the SMF obtains the latency information of the virtual switching node, it sends the latency information of the virtual switching node to the AF, that is, it reports the internal processing latency of the virtual switching node to the AF so that the AF can know the internal processing latency of the virtual switching node. The SMF can send the latency information of the virtual switching node directly to the AF, or it can send the latency information of the virtual switching node to the AF through the PCF or NEF.

[0157] exist Figure 6 In the illustrated embodiment, the SMF obtains the latency information reported by the user plane nodes and acquires the internal processing latency of the virtual switching nodes, then reports it to the AF. The SMF can decompose the scheduling rules of the virtual switching nodes based on the latency of each segment in order to determine the scheduling rules for each user plane node. It is understood that... Figure 6 The embodiments shown are prerequisites for implementing subsequent embodiments.

[0158] The embodiments of this application are applied to Figure 4b Taking the network architecture diagram shown as an example, as Figure 7 The diagram shown is a flowchart illustrating the scheduling rule determination method provided in Embodiment 1 of this application, which may include, but is not limited to, the following steps:

[0159] In step S201, the CNC sends the scheduling rules for the virtual switching nodes to the AF. Correspondingly, the AF receives the scheduling rules for the virtual switching nodes from the CNC.

[0160] The CNC uses the interface defined by the TSN system to send the scheduling rules of the TSN stream on the virtual switching node to the AF. The scheduling rules of the TSN stream on the virtual switching node are the scheduling rules of that virtual switching node. This virtual switching node is... Figure 7 The virtual switching node consists of UE, UPF, and AF.

[0161] The scheduling rules for a virtual switching node include at least one of the following: a port for receiving packets, a time window for receiving packets, a port for sending packets, and a time window for sending packets. The port for receiving packets refers to the port on which the virtual switching node receives TSN streams. The time window for receiving packets refers to the time window during which the virtual switching node receives TSN streams. The port for receiving packets and the time window for receiving packets instruct the virtual switching node to receive TSN streams on the receiving port within the specified time window. Similarly, the port for sending packets and the time window for sending packets instruct the virtual switching node to send TSN streams on the sending port within the specified time window.

[0162] Time windows can be represented by intervals, such as (t1, t2) for receiving messages and (t3, t4) for sending messages, where t1, t2, t3, and t4 can represent specific time values; they can also represent the offset time relative to the packet transmission period within the TSN clock domain. For example, if the packet transmission period is T, t1 is the start time of the packet transmission period T, and t3 represents the offset time relative to the start time of the packet transmission period T. Time windows can also be identified by a start time and a time length, such as (t, t+A) for receiving messages and (t+B, t+C) for sending messages, where t represents the start time, and A, B, and C represent the time lengths.

[0163] The scheduling rules for virtual switching nodes also include flow information, which is the flow information of TSN flows. This includes the destination MAC address of the TSN flow, the flow identifier (ID) of the TSN flow, the bandwidth information of the TSN flow, and the flow class of the TSN flow. The flow information of TSN flows can be used to determine the QoS flow corresponding to the TSN flow and to determine the forwarding path of the TSN flow.

[0164] In step S202, the AF sends the scheduling rules for the virtual switching nodes to the SMF. Correspondingly, the SMF receives the scheduling rules for the virtual switching nodes from the AF.

[0165] After receiving the scheduling rules of the virtual switching node, the AF (Active Front-End) sends the scheduling rules to the SMF (Signaling Function) using the interface defined by the 5G system. The AF can send the scheduling rules directly to the SMF, or it can send them through the PCF (Programmable Center-End) or NEF (New Element-End). Specifically, the AF first sends the scheduling rules to the PCF or NEF, and then the PCF or NEF sends them to the SMF. If the PCF sends the scheduling rules to the SMF, the PCF can do so through a QoS flow creation request message or a QoS flow modification request message within the PDU session.

[0166] Specifically, in step S202, the AF or PCF can merge TSN flows with the same traffic class into the same QoS flow, and use the scheduling rules of the TSN flows corresponding to the traffic class as the scheduling rules of the QoS flow.

[0167] In step S203, the SMF sends a clock domain offset request message to the UPF. Correspondingly, the UPF receives the clock domain offset request message from the SMF.

[0168] Steps S203 and S204 are optional. The time window included in the scheduling rules of the virtual switching node issued by the AF corresponds to the TSN clock domain, while the UE, RAN, and UPF are user plane nodes in the 5G system, corresponding to the 5G clock domain. When the TSN clock domain differs from the 5G clock domain, steps S203 and S204 can be executed, allowing the SMF to adjust the scheduling rules of the virtual switching node based on the clock domain offset information, or the SMF to obtain the time window corresponding to the 5G system from the UPF. The TSN clock domain differs from the 5G clock domain, meaning the two systems reference different clock synchronization systems, resulting in different representations of the TSN system and the 5G system at the same time. When the TSN clock domain is the same as the 5G clock domain, steps S203 and S204 can be omitted. Steps S203 and S204 can also be executed when the SMF cannot obtain the TSN clock domain information, for example, if the RAN does not synchronize TSN clock domain information and cannot provide it to the SMF, the SMF cannot obtain the TSN clock domain information.

[0169] In one possible implementation, a clock domain offset request message is used to request clock domain offset information between the TSN clock domain and the 5G clock domain. The clock domain offset information can be the offset of the TSN clock domain relative to the 5G clock domain, or the offset of the 5G clock domain relative to the TSN clock domain, so that the SMF can adjust the time window included in the scheduling rules of the virtual switching node issued by the AF according to the clock domain offset information, so that the adjusted time window corresponds to the 5G clock domain.

[0170] In one possible implementation, the clock domain offset request message may include the time window for receiving messages and / or sending messages issued by the AF for the virtual switching node, which is used to request the UPF to provide feedback on the time window corresponding to the 5G clock domain. That is, the UPF adjusts the time window for receiving messages and / or sending messages according to the relationship between the TSN clock domain and the 5G clock domain, so that the adjusted time window corresponds to the 5G clock domain.

[0171] SMF can send a clock domain offset request message to UPF via N4 session creation request message or N4 session modification request message.

[0172] In step S204, the UPF sends a clock domain offset response message to the SMF. Correspondingly, the SMF receives the clock domain offset response message from the UPF.

[0173] In one possible implementation, when the UPF receives a clock domain offset request message, it determines the clock domain offset information based on the TSN clock domain and the 5G clock domain, and sends a clock domain offset response message to the SMF, which includes the clock domain offset information. Upon receiving this clock domain offset information, the SMF adjusts the time window included in the scheduling rules of the virtual switching node issued by the AF, so that the adjusted time window corresponds to the 5G clock domain. For example, the SMF adjusts the clock domain offset information according to (t1,t2) and / or (t3,t4) to obtain (t1',t2') and / or (t3',t4'), where (t1,t2) and / or (t3,t4) correspond to the TSN clock domain, and (t1',t2') and / or (t3',t4') correspond to the 5G clock domain.

[0174] In one possible implementation, when the UPF receives a clock domain offset request message, which includes a time window for receiving packets and / or a time window for sending packets, it adjusts the time windows for receiving packets and / or sending packets according to the relationship between the TSN clock domain and the 5G clock domain, so that the adjusted time windows correspond to the 5G clock domain. The UPF then sends a clock domain offset response message to the SMF, which includes the adjusted time windows. For example, the clock domain offset request message includes the time window (t1, t2) for receiving packets issued by the AF, and the clock domain offset response message sent by the UPF to the SMF includes the adjusted time window (t1', t2'), where (t1', t2') corresponds to the 5G clock domain.

[0175] UPF can send clock domain offset response messages to SMF by creating or modifying response messages through the N4 session.

[0176] UPF can also proactively feed back clock domain offset information to SMF, i.e., without executing step S203. For example, UPF proactively carries clock domain offset information in the N4 session creation response message or N4 session modification response message. Another example is that UPF proactively sends clock domain offset information to SMF through an event reporting mechanism.

[0177] In step S205a, the SMF sends the virtual switching node delay information and UPF_N3_delay to the RAN. Correspondingly, the RAN receives the virtual switching node delay information and UPF_N3_delay from the SMF.

[0178] The latency information of the virtual switching node, i.e., the internal processing latency of the virtual switching node, is determined by the SMF according to the time windows included in the scheduling rules of the virtual switching node. For example, the time window for receiving packets is (t1, t2), and the time window for sending packets is (t3, t4). The latency information of the virtual switching node can be the difference between t3 and t1, Δt1; the difference between t4 and t2, Δt2; the minimum value between Δt1 and Δt2; or the average value between Δt1 and Δt2. This embodiment of the application uses the minimum value between Δt1 and Δt2 as an example for the latency information of the virtual switching node.

[0179] UPF_N3_delay is UP_BH_DELAY. Figure 6 In the illustrated embodiment, the UPF or RAN reports to the SMF.

[0180] The SMF can first send the virtual switching node's latency information and UPF_N3_latency to the AMF. Then, the AMF sends the virtual switching node's latency information and UPF_N3_latency to the RAN via the N2 interface in the N2 session creation request message or the N2 session modification request message. The N2 session creation request message or the N2 session modification request message can indicate the virtual switching node's latency information and UPF_N3_latency through N2 interface information elements or QoS parameters. The SMF can also send the virtual switching node's latency information and UPF_N3_latency to the RAN independently via the N2 interface; the N2 interface information elements can indicate the virtual switching node's latency information and UPF_N3_latency.

[0181] In step S206a, the RAN determines the first delay reservation between the RAN and the UE. For downlink transmission, the RAN determines the first delay reservation from the RAN to the UE.

[0182] The RAN determines the first delay reservation from the RAN to the UE based on the latency information of the virtual switching node, UP_BH_DELAY, and the RAN's scheduling capabilities. Specifically, assuming the latency information of the virtual switching node is represented as T_DELAY, the RAN determines the first delay reservation from the RAN to the UE based on its own load, bandwidth information, and other factors within the range of its measured RAN_AIR_UE_DELAY. The latency difference between T_DELAY and the first delay reservation is within the range of UP_BH_DELAY. In this case, the first delay reservation includes the RAN's internal processing latency reservation, the air interface forwarding latency reservation, and the UE's internal processing latency reservation.

[0183] Furthermore, after determining the first delay reservation between the RAN and the UE, the RAN determines the second delay reservation between the UPF and the RAN. For downlink transmission, the RAN determines the second delay reservation from the UPF to the RAN. Specifically, the RAN subtracts the first delay reservation from the delay information of the virtual switching node to obtain the second delay reservation. The value of the second delay reservation is within the range of UP_BH_DELAY. At this time, the second delay reservation includes the internal processing reservation of the UPF and the forwarding delay reservation of N3.

[0184] In one possible implementation, if the RAN determines the first delay reservation from the RAN to the UE based on its own load and bandwidth information within the range of its measured RAN_AIR_DELAY value, then the first delay reservation includes the RAN's internal processing delay reservation and the air interface forwarding delay reservation. The delay difference T_DELAY - the first delay reservation - UE_DELAY is within the range of UP_BH_DELAY. Further, the RAN subtracts the first delay reservation from the delay information of the virtual switching node, and then subtracts UE_DELAY to obtain the second delay reservation from the UPF to the RAN. This second delay reservation includes the UPF's internal processing reservation and the N3 forwarding delay reservation. UE_DELAY can be measured by the RAN.

[0185] In step S207a, the RAN sends a first delay reservation and / or a second delay reservation to the SMF. Correspondingly, the SMF receives the first delay reservation and / or the second delay reservation from the RAN.

[0186] The RAN can send a first delay reservation and / or a second delay reservation to the SMF via the N2 interface in an N2 session creation request message or an N2 session modification request message. The first delay reservation and / or the second delay reservation can be indicated in the N2 interface information element or QoS parameters within the N2 session creation request message or N2 session modification request message. The RAN can also send the first delay reservation and / or the second delay reservation to the SMF independently via the N2 interface; the N2 interface information element can indicate the first delay reservation and / or the second delay reservation.

[0187] If the RAN sends a first delay reservation to the SMF, the SMF can determine a second delay reservation. If the first delay reservation includes the RAN's internal processing delay reservation, the air interface forwarding delay reservation, and the UE's internal processing delay reservation, the SMF subtracts the first delay reservation from the virtual switching node's delay information to obtain the second delay reservation. The value of the second delay reservation is within the range of UP_BH_DELAY. Alternatively, if the first delay reservation includes the RAN's internal processing delay reservation and the air interface forwarding delay reservation, the SMF subtracts the first delay reservation and UE_DELAY from the virtual switching node's delay information to obtain the second delay reservation. The value of the second delay reservation is also within the range of UP_BH_DELAY.

[0188] If the RAN sends a second delay reservation to the SMF, the SMF can determine the first delay reservation. The SMF subtracts the second delay reservation from the delay information of the virtual switching node to obtain the first delay reservation. At this time, the first delay reservation includes the RAN's internal processing delay reservation, the air interface forwarding delay reservation, and the UE's internal processing delay reservation. The delay difference between the forwarding delay and the first delay reservation is within the range of UP_BH_DELAY. The SMF subtracts the second delay reservation and UE_DELAY from the delay information of the virtual switching node to obtain the first delay reservation. At this time, the first delay reservation includes the RAN's internal processing delay reservation and the air interface forwarding delay reservation. The delay difference between the forwarding delay, the first delay reservation, and UE_DELAY is within the range of UP_BH_DELAY.

[0189] In step S208a, the SMF sends the second delay reservation and the ingress port information of the virtual switching node to the UPF. Correspondingly, the UPF receives the second delay reservation and the ingress port information of the virtual switching node from the SMF.

[0190] If the RAN sends a second delay reservation to the SMF, the SMF can directly obtain the second delay reservation. If the RAN does not send a second delay reservation to the SMF, the SMF can determine the second delay reservation based on the first delay reservation and the forwarding delay, as described in step S207a, which will not be repeated here.

[0191] For downlink transmission, the ingress port of the virtual switching node is the port used by the UPF side to receive TSN streams. The ingress port information includes the ingress port identifier and the time window for receiving packets. The ingress port identifier is the identifier of the port for receiving packets specified in the scheduling rules of the virtual switching node, and the time window for receiving packets is the time window for receiving packets specified in the scheduling rules of the virtual switching node. For example, the ingress port information includes the ingress port and (t1, t2).

[0192] The SMF sends the second delay reservation and virtual switching node ingress port information to the UPF via the N4 interface in the PDU session creation request message or PDU session modification request message. The PDU session creation request message or PDU session modification request message can indicate the second delay reservation and virtual switching node ingress port information through N4 interface information cells or QoS parameters. The SMF can also send the second delay reservation and virtual switching node ingress port information to the UPF independently via the N4 interface; the N4 interface information cells can indicate the second delay reservation and virtual switching node ingress port information.

[0193] The above steps S205a-S208a are the process of first determining the first time delay reservation by the RAN, and then determining the second time delay reservation by the RAN or SMF. The following steps S205b-S208b are the process of first determining the second time delay reservation by the UPF, and then determining the first time delay reservation by the UPF or SMF.

[0194] In step S205b, the SMF sends the latency information of the virtual switching node, the access network air interface UE latency, and the ingress port information of the virtual switching node to the UPF. Correspondingly, the UPF receives the latency information of the virtual switching node, the access network air interface UE latency, and the ingress port information of the virtual switching node from the SMF.

[0195] The latency information of the virtual switching node can be found in the detailed description of the latency information of the virtual switching node in step S205a, and will not be repeated here. The ingress port information of the virtual switching node can be found in the detailed description in step S208a, and will not be repeated here.

[0196] Access network air interface UE delay, or RAN_AIR_UE_DELAY, is Figure 6 In the illustrated embodiment, the UPF or RAN reports to the SMF. If Figure 6 In the illustrated embodiment, RAN_AIR_UE_DELAY is sent from UPF to SMF, so RAN_AIR_UE_DELAY may not be included in step S205b. Figure 6 In the illustrated embodiment, RAN_AIR_UE_DELAY is sent from RAN to SMF, so step S205b needs to include RAN_AIR_UE_DELAY.

[0197] The SMF can send virtual switching node latency information, access network air interface UE latency, and virtual switching node ingress port information to the UPF via the N4 interface in PDU session creation request messages or PDU session modification request messages. The PDU session creation request message or PDU session modification request message can indicate the virtual switching node latency information, access network air interface UE latency, and virtual switching node ingress port information through interface 4 information elements or QoS parameters. The SMF can also send these information separately to the UPF via the N4 interface; the N4 interface information elements can indicate the virtual switching node latency information, access network air interface UE latency, and virtual switching node ingress port information.

[0198] In step S206b, the UPF determines the second delay reservation between the UPF and the RAN. For downlink transmission, the UPF determines the second delay reservation from the UPF to the RAN.

[0199] The UPF determines the second delay reservation from the UPF to the RAN based on the latency information of the virtual switching node, RAN_AIR_UE_DELAY, and the scheduling capability of the UPF. Specifically, assuming the latency information of the virtual switching node is represented as T_DELAY, the UPF determines the second delay reservation from the UPF to the RAN within the range of its measured UP_BH_DELAY value, based on its own load and bandwidth information. The latency difference between T_DELAY and this second delay reservation is within the range of RAN_AIR_UE_DELAY. In this case, the second delay reservation includes the UPF's internal processing reservation and the forwarding latency reservation of N3.

[0200] Furthermore, after determining the second delay reservation between the UPF and the RAN, the UPF determines the first delay reservation between the RAN and the UE. For downlink transmission, the UPF determines the first delay reservation from the RAN to the UE. Specifically, the UPF subtracts the second delay reservation from the delay information of the virtual switching node to obtain the first delay reservation. The value of the first delay reservation is within the range of RAN_AIR_UE_DELAY. At this time, the first delay reservation includes the RAN's internal processing delay reservation, the air interface forwarding delay reservation, and the UE's internal processing delay reservation.

[0201] In step S207b, the UPF sends a first delay reservation and / or a second delay reservation to the SMF. Correspondingly, the SMF receives the first delay reservation and / or the second delay reservation from the UPF.

[0202] The UPF can send a first delay reservation and / or a second delay reservation to the SMF via the N4 interface in the PDU session creation response message or the PDU session modification response message. The first delay reservation and / or the second delay reservation can be indicated in the PDU session creation response message or the PDU session modification response message via N4 interface information elements or QoS parameters. The UPF can also send the first delay reservation and / or the second delay reservation to the SMF independently via the N4 interface; the N4 interface information elements can indicate the first delay reservation and / or the second delay reservation.

[0203] If the UPF sends the second delay reservation to the SMF, the SMF can determine the first delay reservation. The SMF subtracts the second delay reservation from the delay information of the virtual switching node to obtain the first delay reservation. At this time, the first delay reservation includes the RAN's internal processing delay reservation, the air interface forwarding delay reservation, and the UE's internal processing delay reservation. The delay of the first delay reservation is within the range of RAN_AIR_UE_DELAY.

[0204] If the UPF sends the first delay reservation to the SMF, the SMF can determine the second delay reservation. The SMF subtracts the first delay reservation from the delay information of the virtual switching node to obtain the second delay reservation. The delay difference between the forwarding delay and the second delay reservation is within the range of RAN_AIR_UE_DELAY.

[0205] In step S208b, the SMF sends the first delay reservation to the RAN. Correspondingly, the RAN receives the first delay reservation from the SMF.

[0206] The SMF can send the first delay reservation to the RAN via the N2 interface in either the N2 session creation request message or the N2 session modification request message. The first delay reservation can be indicated in the N2 interface information cell or QoS parameters within the N2 session creation request message or the N2 session modification request message. The SMF can also send the first delay reservation to the RAN independently via the N2 interface; the N2 interface information cell can indicate the first delay reservation. Sending the first delay reservation to the RAN allows the RAN to perform deterministic transmission on the RAN based on the first delay reservation.

[0207] In one possible implementation, the SMF also sends a second time delay reservation to the RAN. The second time delay reservation can be sent together with the first time delay reservation or sent separately.

[0208] Steps S205b-S208b described above involve first determining the second delay reservation by the UPF, and then determining the first delay reservation by the UPF or SMF. Steps S205a-S208a and steps S205b-S208b are two parallel implementation methods.

[0209] In step S209, the SMF sends the outgoing port information of the virtual switching node to the UE. Correspondingly, the UE receives the outgoing port information of the virtual switching node from the SMF.

[0210] For downlink transmission, the egress port information of the virtual switching node (FSM) is the port used by the UE to send TSN streams. This egress port information includes the egress port identifier and the time window for sending packets. The egress port identifier is the identifier of the port for sending packets specified in the SFM's scheduling rules, and the time window for sending packets is the time window for sending packets specified in the SFM's scheduling rules. For example, the egress port information includes the egress port and (t3, t4). The SMF sends the SFM's egress port information to the UE so that the UE can send TSN streams based on this information.

[0211] In one possible implementation, the SMF also sends the virtual switching node's delay information and / or a first delay reservation to the UE to ensure deterministic delay transmission at the UE-side packet granularity. If the SMF only sends the virtual switching node's outgoing port information to the UE, the UE will forward the received packets outward within the packet transmission time window; for example, the UE will forward the received packets outward within the time window (t3, t4).

[0212] In step S210, the UPF, RAN, and UE perform deterministic transmission.

[0213] In one possible implementation, the UPF performs deterministic transmission based on a second delay reservation and a timestamp in the message. For example, for a downlink message, when the UPF receives the downlink message, it adds a timestamp indicating that the UPF received the downlink message to the downlink message. Then, based on this timestamp and the second delay reservation, it selects a transmission port from multiple transmission ports of the UPF or determines a forwarding path, and transmits the downlink message to the RAN through this transmission port or forwarding path. The difference between the timestamp of the downlink message transmitted by the transmission port determined on the UPF and the timestamp of the downlink message received is within the second delay reservation, or the time taken by the forwarding path determined by the UPF is within the second delay reservation.

[0214] Then, the RAN performs deterministic transmission based on the second delay reservation. The RAN receives the downlink message from the UPF, which carries a timestamp indicating that the UPF received the downlink message. After the second delay reservation interval, the RAN sends the downlink message to the UE. Optionally, the RAN modifies the timestamp indicating that the UPF received the downlink message carried in the downlink message to the time when the timestamp reaches the second delay reservation, that is, modifies it to the time when the RAN sends the downlink message to the UE.

[0215] Then, the UE performs deterministic transmission based on the first delay reservation. When the UE receives the downlink message from the RAN, if the downlink message carries a timestamp of the UPF receiving the downlink message, the UE forwards the downlink message after the second delay reservation and the first delay reservation, i.e., forwards it to the data terminal or switching node. The switching node may be another virtual switching node, and the specific target node to which the UE forwards the message is not limited in this embodiment. If the downlink message carries a timestamp modified by the RAN, the UE forwards the downlink message after the modified timestamp is separated by the first delay reservation.

[0216] In one possible implementation, the UPF, RAN, and UE perform deterministic transmission based on a first delay reservation, a second delay reservation, and the ingress port information of the virtual switching node, independent of the timestamp carried in the message. For example, if a TSN system is deployed between the UPF and RAN, the UPF can determine the time window for the RAN to receive the message based on the second delay reservation and the ingress port time window, thereby performing deterministic transmission.

[0217] exist Figure 7 In the illustrated embodiment, the scheduling rules include delay reservation. The RAN determines a first delay reservation between the RAN and the UE, and optionally determines a second delay reservation between the UPF and the RAN; or the UPF determines a second delay reservation between the UPF and the RAN, and optionally determines a first delay reservation between the RAN and the UE; thereby enabling deterministic transmission of the TSN stream by the UPF, RAN, and UE, achieving deterministic transmission of the 5G system.

[0218] The embodiments of this application are applied to Figure 4b Taking the network architecture diagram shown as an example, as Figure 8 The diagram shown is a flowchart illustrating the scheduling rule determination method provided in Embodiment 2 of this application, which may include, but is not limited to, the following steps:

[0219] In step S301, the CNC sends the scheduling rules for the virtual switching nodes to the AF. Correspondingly, the AF receives the scheduling rules for the virtual switching nodes from the CNC.

[0220] In step S302, the AF sends the scheduling rules for the virtual switching nodes to the SMF. Correspondingly, the SMF receives the scheduling rules for the virtual switching nodes from the AF.

[0221] In step S303, the SMF sends a clock domain offset request message to the UPF. Correspondingly, the UPF receives the clock domain offset request message from the SMF.

[0222] In step S304, the UPF sends a clock domain offset response message to the SMF. Correspondingly, the SMF receives the clock domain offset response message from the UPF.

[0223] The implementation process of steps S301-S304 can be found in [reference needed]. Figure 6 The specific descriptions of steps S201-S204 in the illustrated embodiment will not be repeated here.

[0224] In step S305a, the SMF determines the reserved scheduling interval for the RAN, that is, determines the scheduling interval reserved for the RAN.

[0225] For downlink transmission, the RAN's reserved scheduling interval may include: the start time of the RAN receiving downlink packets and the start time of the UE receiving downlink packets, i.e. Figure 5 The range of values ​​for t7 (t7_rang) and t11 (t11_rang) is specified. Optionally, the reserved scheduling interval for the RAN also includes the end time for the RAN to receive downlink packets and the end time for the UE to receive downlink packets, i.e. Figure 5 The range of values ​​for t8 (t8_rang) and t12 (t12_rang) are given.

[0226] For uplink transmission, the reserved scheduling interval of the RAN may include t7_rang and t11_rang, and optionally also t8_rang and t12_rang; or include t5_rang and t11_rang, and optionally also t6_rang and t12_rang.

[0227] The value range indicates the minimum and maximum values, and the value range is the time information in the clock domain where the RAN resides, i.e., the time information in the 5G clock domain. Assuming the 5G clock domain differs from the TSN clock domain, the SMF adjusts the time window included in the scheduling rules of the virtual switching node issued by the AF based on the clock domain offset information, so that the adjusted time window corresponds to the 5G clock domain. For example, the SMF adjusts (t1',t2') and (t3',t4') based on the clock domain offset information according to (t1,t2) and (t3,t4). (t1,t2) and (t3,t4) correspond to the TSN clock domain, and (t1',t2') and (t3',t4') correspond to the 5G clock domain.

[0228] Taking the following downlink transmission, where the RAN's reserved scheduling interval includes t7_rang and t11_rang as an example, the SMF determines that t7_rang may include:

[0229] min(t7_range)=t1'+min(UP_DELAY)+min(BH_DELAY), or min(t7_range)=t1'+min(UP_BH_DELAY);

[0230] max(t7_range)=t1'+max(UP_DELAY)+max(BH_DELAY), or max(t7_range)=t1'+max(UP_BH_DELAY).

[0231] Among them, the earliest time the RAN receives the message is no earlier than the minimum value of t7_range, i.e., no less than min(t7_range), and no later than the maximum value of t7_range, i.e., no greater than max(t7_range). These two values ​​are obtained by measuring the fastest and slowest time when the UPF forwards the downlink message to the RAN after receiving it.

[0232] SMF determination of t11_rang may include:

[0233] min(t11_range)=t3'-max(UE_DELAY); max(t11_range)=t3'-max(UE_DELAY).

[0234] Among them, the earliest time the UE receives the message is no earlier than the minimum value of t11_range, i.e., no less than min(t11_range), and no later than the maximum value of t11_range, i.e., no greater than max(t11_range). These two values ​​are obtained by measuring the fastest and slowest forwarding times after the UE receives the downlink message.

[0235] In summary, the reserved scheduling interval for a network element is determined based on the fastest and slowest transmission delays of the two network elements, combined with the time windows for sending and receiving messages between the two network elements. The method for determining the reserved scheduling interval in the SMF described above is exemplary, and the embodiments of this application do not limit the method for determining the scheduling interval.

[0236] In step S306a, the SMF sends the RAN's reserved scheduling interval to the RAN. Correspondingly, the RAN receives the RAN's reserved scheduling interval from the SMF.

[0237] The SMF can first send the reserved scheduling range of the RAN to the AMF, and then the AMF sends the reserved scheduling range of the RAN to the RAN through the N2 interface in the N2 session creation request message or the N2 session modification request message.

[0238] In step S307a, the RAN determines its scheduling rules based on the RAN's reserved scheduling interval. The RAN's scheduling rules include t7 and t11, and optionally t8 and t12 as well.

[0239] For downlink transmission, the RAN determines t7 and t11 based on its reserved scheduling interval and its own scheduling capacity. The difference between t11 and t7 lies within the range of AIR_DELAY + RAN_DELAY (the minimum values ​​of AIR_DELAY and RAN_DELAY are added together to obtain the minimum value of the range, and the maximum values ​​are added together to obtain the maximum value of the range). In other words, the RAN determines its scheduling rules from its reserved scheduling interval, and the delay corresponding to these scheduling rules meets the RAN's scheduling capacity.

[0240] Steps S305a-S307a above determine the reserved scheduling interval for the RAN and send it to the RAN, which then determines its scheduling rules. Steps S305b-S307b below determine the reserved scheduling interval for the RAN, which then determines its scheduling rules.

[0241] In step S305b, the SMF determines the scheduling intervals on both sides of the RAN, which refers to the segmented scheduling interval and the delay reservation interval for forwarding messages.

[0242] The scheduling intervals on both sides of the RAN include the scheduling interval between the RAN and the UPF, and the scheduling interval between the RAN and the UE. Taking downlink transmission as an example, it includes the scheduling interval from the UPF to the RAN and the scheduling interval from the RAN to the UE. The scheduling interval from the RAN to the UE is known to the RAN, for example, in... Figure 5 In the illustrated embodiment, the RAN obtains the second delay information between the RAN and the UE by measurement, and can use the second delay information as the scheduling interval between the RAN and the UE.

[0243] Taking the downstream transmission as an example, the minimum value of the scheduling interval from UPF to RAN is min(UP_DELAY)+min(BH_DELAY), or min(UP_BH_DELAY), and the maximum value is max(UP_DELAY)+max(BH_DELAY), or max(UP_BH_DELAY).

[0244] In one possible implementation, the SMF determines relevant information about the scheduling interval from the UPF to the RAN, which may include UP_DELAY, BH_DELAY, or UP_BH_DELAY. The SMF also determines relevant information about the scheduling interval from the RAN to the UE, which may include UE_DELAY.

[0245] In step S306b, the SMF sends a scheduling interval or related information about a scheduling interval to the RAN. Correspondingly, the RAN receives the scheduling interval or related information about a scheduling interval from the SMF.

[0246] Taking downlink transmission as an example, the SMF sends the UPF to the RAN's scheduling interval, or related information about that scheduling interval, to the RAN. If sending information about the scheduling interval, it is also necessary to send information about the RAN's scheduling interval to the UE.

[0247] In step S306b', the SMF sends the scheduling rules for the virtual switching nodes to the RAN. Correspondingly, the RAN accepts the scheduling rules for the virtual switching nodes from the SMF.

[0248] The scheduling rules for virtual switching nodes can be adjusted based on clock offset information.

[0249] The information carried in steps S306b and S306b' can be sent separately or in the same message. For example, the information carried in step S306b can be sent via an N2 session creation message during the N2 session creation process, and the information carried in step S306b' can be sent via an N2 session modification message during the N2 session modification process or the QoS flow creation process. Alternatively, both steps S306b and S306b' can be sent via an N2 session modification message during the N2 session modification process or the QoS flow creation process.

[0250] In step S307b, the RAN determines its scheduling rules.

[0251] Based on the information carried in steps S306b and S306b', and in conjunction with its own scheduling capabilities, the RAN determines its scheduling capacity. The RAN first determines its reserved scheduling interval, and then determines its scheduling capacity. The RAN determines its reserved scheduling interval according to the method used by the SMF to determine the RAN's reserved scheduling interval in step S305a, and then determines the RAN's scheduling rules according to step S307a.

[0252] Furthermore, in steps S307a and S307b, after determining its scheduling rules, the RAN can determine the latency budgets from the UPF to the RAN and from the RAN to the UE based on the scheduling rules of the virtual switching node. Specifically, after determining t7 and t11, the RAN can determine the latency budgets from the UPF to the RAN and from the RAN to the UE based on (t1', t2') and (t3', t4'). For example, subtracting t7 from t1' and t2' respectively yields the latency budget from the UPF to the RAN, and subtracting t11 from t1' and t2' and then subtracting the latency budget from the UPF to the RAN yields the latency budget from the RAN to the UE.

[0253] In step S308, the RAN sends its scheduling rules to the SMF. Correspondingly, the SMF receives the RAN scheduling rules from the RAN.

[0254] Specifically, the RAN sends t7, t11, or t5 to the SMF, which indicates the time when the RAN receives the downlink message, the time when the UE receives the downlink message, or the time when the UPF sends the downlink message. Optionally, the RAN also sends the time window of the virtual switching node's output port to the SMF. Here, t7, t11, and t5 can be the start time of the time window, the end time of the time window, or both.

[0255] Alternatively, the RAN may send at least one of its determined UPF-to-RAN delay budget or RAN-to-UE delay budget to the SMF.

[0256] In step S309, the SMF sends the ingress port information of the virtual switching node to the UPF, as well as at least one of the delay budget, t5, t6, t7, or t8 between the UPF and the RAN. Correspondingly, the UPF receives the ingress port information of the virtual switching node from the SMF, as well as at least one of the delay budget, t5, t6, t7, or t8 between the UPF and the RAN.

[0257] In step S310, the UPF determines its scheduling rules.

[0258] The UPF determines its scheduling rules based on the information carried in step S309. For example, step S309 includes (t1', t2') and t5. Subtracting t5 from t1' and t2' respectively yields a difference range. A value is determined from this difference range, and the UPF performs internal processing on downlink packets within this value range, and this value satisfies the UPF's scheduling capabilities.

[0259] In step S311, the SMF sends the outgoing port information of the virtual switching node to the UE. Correspondingly, the UE receives the outgoing port information of the virtual switching node from the SMF.

[0260] The outgoing port information of the virtual switching node includes the outgoing port time window (t3', t4'), within which the UE sends downlink messages to the data terminal or another switching node. Optional outgoing port information of the virtual switching node also includes the outgoing port identifier, i.e., the port identifier through which the UE sends downlink messages.

[0261] Optionally, the SMF also sends at least one of t11 or t12 to the UE. Since the UE's scheduling on the air interface side can be determined by the RAN's scheduling rules, the RAN can determine the UE's scheduling on the air interface side simply by determining its scheduling rules; the UE does not need to determine its own air interface scheduling. Sending at least one of t11 or t12 to the UE allows the UE to plan its internal message processing latency in advance.

[0262] In step S312, the UE determines its scheduling rules. That is, the UE sends downlink messages to the data terminal or another switching node within the time window (t3', t4').

[0263] exist Figure 8 In the illustrated embodiment, the scheduling rules include the timing of sending and receiving messages. The RAN determines its scheduling rules based on the information sent by the SMF. Then, the UPF and UE determine their respective scheduling rules. Thus, the UPF, RAN, and UE perform deterministic transmission of the TSN stream according to their respective scheduling intervals, thereby realizing deterministic transmission of the 5G system.

[0264] The embodiments of this application are applied to Figure 4b Taking the network architecture diagram shown as an example, as Figure 9 The diagram shown is a flowchart illustrating the scheduling rule determination method provided in Embodiment 3 of this application, which may include, but is not limited to, the following steps:

[0265] In step S401, the CNC sends the scheduling rules for the virtual switching nodes to the AF. Correspondingly, the AF receives the scheduling rules for the virtual switching nodes from the CNC.

[0266] In step S402, the AF sends the scheduling rules for the virtual switching nodes to the SMF. Correspondingly, the SMF receives the scheduling rules for the virtual switching nodes from the AF.

[0267] In step S403, the SMF sends a clock domain offset request message to the UPF. Correspondingly, the UPF receives the clock domain offset request message from the SMF.

[0268] In step S404, the UPF sends a clock domain offset response message to the SMF. Correspondingly, the SMF receives the clock domain offset response message from the UPF.

[0269] The implementation process of steps S401-S404 can be found in [reference needed]. Figure 6 The specific descriptions of steps S201-S204 in the illustrated embodiment will not be repeated here.

[0270] In step S405a, the SMF determines the reserved scheduling interval of the UPF, that is, the time interval reserved for the UPF to process messages internally, or the time interval reserved for the UPF to process messages internally and forward messages to the next hop (for downlink transmission, the next hop is the RAN).

[0271] Taking the downstream transmission as an example, the SMF first determines the latency information of the virtual switching node. For details, please refer to the specific description of determining the latency information of the virtual switching node in step S205a, which will not be repeated here.

[0272] Then, the SMF determines the scheduling interval for the remaining segments. For the UPF, the remaining segments can be either the UPF sending downlink packets to the UE to transmit the downlink packets out of the virtual switching node, or the RAN receiving downlink packets to the UE to transmit the downlink packets out of the virtual switching node. The difference between these two cases lies in whether the forwarding delay between the UPF and the RAN is included in the management part of the UPF. Assuming that UU_DELAY represents the scheduling interval for the remaining segments of the UPF, the values ​​of UU_DELAY for the above two cases are as follows:

[0273] A.min(UU_DELAY)=min(UE_DELAY)+min(AIR_DELAY)+min(RAN_DELAY)

[0274] +min(BH_DELAY);max(UU_DELAY)=max(UE_DELAY)+max(AIR_DELAY)

[0275] +max(RAN_DELAY)+max(BH_DELAY);

[0276] B.min(UU_DELAY)=min(UE_DELAY)+min(AIR_DELAY)+min(RAN_DELAY);

[0277] max(UU_DELAY)=max(UE_DELAY)+max(AIR_DELAY)+max(RAN_DELAY);

[0278] Then, the SMF determines the reserved scheduling interval for the UPF based on the UPF's scheduling capabilities. For both scenarios, the UPF's scheduling capability refers to the internal packet processing delay interval UP_DELAY, or the sum of the internal packet processing delay interval and the forwarding delay BH_DELAY (i.e., UP_BH_DELAY). The scheduling interval for the UPF determined by the SMF is the intersection of the difference delay interval between T_DELAY and UU_DELAY and the UPF's scheduling capability, i.e., the overlapping portion of the two delay intervals. This intersection or overlapping portion is used as the reserved scheduling interval for the UPF. For example, UU_DELAY represents the time interval from when the UPF sends a downlink message to when the UE sends the downlink message out of the virtual switching node. The scheduling capability of the UPF represents the time interval UP_DELAY for processing messages within the UPF. Then, the UPF scheduling interval determined by the SMF is the intersection of the time interval difference between T_DELAY and UU_DELAY and the time interval represented by the scheduling capability of the UPF. This intersection is taken as the reserved scheduling interval of the UPF. The method of the SMF in determining the reserved scheduling interval is only exemplary, and the embodiments of this application do not limit the method of determining the reserved scheduling interval.

[0279] In step S406a, the SMF sends the ingress port information of the virtual switching node and the UPF's reservability interval to the UPF. Correspondingly, the UPF receives the ingress port information of the virtual switching node and the UPF's reservability interval from the SMF.

[0280] The ingress port information of the virtual switching node includes the ingress port identifier for receiving uplink and downlink packets in the UPF and the time window (t1', t2') of the ingress port.

[0281] The SMF sends the ingress port information of the virtual switching node and the UPF's reservation range to the UPF via the N4 interface in the PDU session creation request message or PDU session modification request message. The ingress port information of the virtual switching node and the UPF's reservation range can be indicated in the PDU session creation request message or PDU session modification request message through N4 interface information cells or QoS parameters.

[0282] In step S407a, the UPF determines its scheduling rules.

[0283] Specifically, the UPF determines its scheduling rules based on the ingress port information of the virtual switching node, the UPF's delay reservation interval, and the UPF's scheduling capabilities. These scheduling rules include the UPF's delay reservation and at least one of t7 or t8.

[0284] For example, the UPF determines a value from its reserved scheduling interval based on the current load and the processing of packets in the data stream, and uses this value as the delay for forwarding packets. If the reserved scheduling interval is the UPF's internal packet processing delay interval, then t7 = t1' + BH_DELAY + this value; or if the reserved scheduling interval includes BH_DELAY, then t7 = t1 + this value. If the transmission between the RAN and the UPF, and the UPF itself, cannot achieve forwarding and transmission with a defined delay, then the determined information can be considered the maximum value. For example, determining the maximum processing delay of the downlink packet by the UPF and / or the maximum delay that must be guaranteed from the UPF to the RAN, the corresponding determined t7 is the latest reception time of the downlink packet by the RAN.

[0285] The above steps S405a-S407a are the process by which the SMF determines the reserved scheduling interval of the UPF, and then the UPF determines its scheduling rules. The following steps S405b-S407b are the process by which the UPF autonomously determines its scheduling rules.

[0286] In step S405b, the SMF determines the scheduling interval for the remaining segments.

[0287] For details on how SMF determines the scheduling interval for the remaining segments, please refer to step S405a for a detailed description of how SMF determines the scheduling interval for the remaining segments. These details will not be repeated here.

[0288] In step S406b, the SMF sends the remaining segment scheduling interval to the UPF. Correspondingly, the UPF receives the remaining segment scheduling interval from the SMF.

[0289] SMF sends the remaining segment scheduling range to UPF via the N4 interface in the PDU session creation request message or PDU session modification request message. The remaining segment scheduling range can be indicated in the PDU session creation request message or PDU session modification request message through the 4 interface cell or QoS parameters.

[0290] In step S406b', the SMF sends the ingress port information of the virtual switching node to the UPF. Correspondingly, the UPF receives the ingress port information of the virtual switching node from the SMF.

[0291] The SMF sends the ingress port information of the virtual switching node to the UPF via the N4 interface in the PDU session creation request message or PDU session modification request message. The ingress port information of the virtual switching node can be indicated in the PDU session creation request message or PDU session modification request message through the 4 interface cell or QoS parameters.

[0292] The information carried in steps S406b and S406b' can be sent through the same message or through different messages.

[0293] In step S407b, the UPF determines its scheduling rules.

[0294] Based on the information carried in steps S406b and S406b', and combined with its own scheduling capabilities, the UPF determines its scheduling capacity. The UPF first determines its reserved scheduling range, and then determines its scheduling capacity. The UPF determines its reserved scheduling range according to the method used by the SMF to determine the UPF's reserved scheduling range in step S405a, and then determines the UPF's scheduling rules according to step S407a.

[0295] Furthermore, after determining its scheduling rules, the UPF can determine the delay reservation for the remaining nodes. For example, the delay reservation for the remaining nodes can be obtained by subtracting the delay reservation of the UPF from the delay information of the virtual switching nodes. Alternatively, the delay reservation for the remaining nodes can be the minimum difference between the time t7 when the RAN receives the downlink message and (t1', t2').

[0296] In step S408, the UPF sends the time information for sending downlink messages to the SMF and / or the time information for the RAN to receive downlink messages. Correspondingly, the SMF receives the time information for sending downlink messages from the UPF and / or the time information for the RAN to receive downlink messages.

[0297] Specifically, the time information for the UPF to send downlink messages includes at least one of t5 or t6, and the time information for the RAN to receive downlink messages includes at least one of t7 or t8. In other words, the UPF sends at least one of t5, t6, t7, or t8 to the SMF.

[0298] Alternatively, the UPF sends its scheduling rules or the time reservation of the remaining nodes to the SMF, i.e., it sends the time reservation of the UPF or the time reservation of the remaining nodes.

[0299] In step S409, the SMF determines the reserved scheduling interval of the RAN.

[0300] In step S410, the SMF sends the RAN's adjustment reservation interval to the RAN. Correspondingly, the RAN receives the RAN's adjustment reservation interval from the SMF.

[0301] Step S411, the RAN determines its scheduling rules.

[0302] The process by which the RAN determines its scheduling rules is similar to steps S405a-S407a or steps S405b-S407b.

[0303] In one possible implementation, the SMF determines the RAN's time window or latest reception time for receiving downlink messages and sends it to the RAN. The RAN then determines its scheduling rules, which may include RAN delay reservations and optionally determine the UE's time window or latest reception time for receiving downlink messages (at least one of t11 or t12).

[0304] In one possible implementation, the SMF determines the reserved scheduling interval of the RAN and sends it to the RAN; or it sends (t3', t4') and UE_DELAY to the RAN and the RAN determines its reserved scheduling interval, and then the RAN determines its scheduling rules, which may include the RAN's delay reservation, and optionally determine the time window for the UE to receive downlink messages or the latest time to receive downlink messages (at least one of t11 or t12).

[0305] In step S412, the RAN sends its delay reservation to the SMF. Correspondingly, the SMF receives the delay reservation from the RAN.

[0306] Alternatively, the RAN can send the time window for the UE to receive downlink messages or the latest time to receive downlink messages to the SMF.

[0307] In step S413, the SMF sends the outgoing port information of the virtual switching node to the UE. Correspondingly, the UE receives the outgoing port information of the virtual switching node from the SMF.

[0308] In step S414, the UE determines its scheduling rules. That is, the UE sends downlink messages to the data terminal or another switching node within the time window (t3', t4').

[0309] For details on the implementation of steps S413 and S414, please refer to [link / reference]. Figure 8 The specific descriptions of steps S311 and S312 in the illustrated embodiment will not be repeated here.

[0310] exist Figure 9 In the illustrated embodiment, the scheduling rules include delay reservation. The UPF determines its scheduling rules based on the information sent by the SMF. Then, the UPF and UE determine their respective scheduling rules, thereby enabling the UPF, RAN, and UE to perform deterministic transmission of the TSN stream according to their respective scheduling intervals, thus achieving deterministic transmission of the 5G system.

[0311] The embodiments of this application are applied to Figure 4b Taking the network architecture diagram shown as an example, as Figure 10 The diagram shown is a flowchart illustrating the scheduling rule determination method provided in Embodiment 4 of this application, which may include, but is not limited to, the following steps:

[0312] In step S501, the CNC sends the scheduling rules for the virtual switching nodes to the AF. Correspondingly, the AF receives the scheduling rules for the virtual switching nodes from the CNC.

[0313] In step S502, the AF sends the scheduling rules for the virtual switching nodes to the SMF. Correspondingly, the SMF receives the scheduling rules for the virtual switching nodes from the AF. This message can be sent directly to the SMF by the AF, or sent to the SMF via the NEF, or it can be sent by the AF to the PCF, and then sent to the SMF by the PCF through a flow creation or modification process.

[0314] The difference between steps S201-S202 and steps S501-S502 is that the scheduling rules for the virtual switching node in steps S501-S502 include the port for sending messages and the time window for sending messages. For example, for downlink transmission, this includes the UE-side egress port and the UE-side message sending time window (t3, t4). Whether the scheduling rules for the virtual switching node include the port for receiving messages and the time window for receiving messages is not limited in steps S501-S502. In other words, the scheduling rules for the virtual switching node in steps S501-S502 may or may not include the port for receiving messages and the time window for receiving messages.

[0315] In step S503, the SMF sends a clock domain offset request message to the UPF. Correspondingly, the UPF receives the clock domain offset request message from the SMF.

[0316] In step S504, the UPF sends a clock domain offset response message to the SMF. Correspondingly, the SMF receives the clock domain offset response message from the UPF.

[0317] The implementation process of steps S503-S504 can be found in [reference needed]. Figure 7 The specific descriptions of steps S203-S204 in the illustrated embodiment will not be repeated here.

[0318] Optionally, the SMF determines the time window included in the scheduling rules of the virtual switching node within the time window corresponding to the 5G clock domain.

[0319] For downlink transmission, the UE acts as the output port for the data stream transmitted by the virtual switching node. The scheduling rules of the virtual switching node include the port on the UE side that sends messages and the time window (t3, t4) for the UE side to send messages. If the TSN clock domain information is not synchronized on the RAN, the SMF can calculate the time window (t3', t4') corresponding to the time window in the 5G clock domain through steps S503-S504.

[0320] For uplink transmission, the UPF acts as the output port for the data stream transmitted by the virtual switching node. The scheduling rules for this virtual switching node include the port on the UPF side that sends messages and the time window (t1, t2) for sending messages on the UPF side. If the scheduling rules for this virtual switching node only include the time window (t1, t2) for sending messages on the UPF side, the SMF can determine the time window (t3, t4) for receiving messages on the UE side based on (t1, t2) and the latency information of the virtual switching node. Here, the latency information of the virtual switching node = UP_BH_DELAY + RAN_AIR_UE_DELAY. Subtracting the latency information of the virtual switching node from the time window (t1, t2) for sending messages on the UPF side yields the time window (t3, t4) for receiving messages on the UE side. The determination of the time window for receiving messages on the UE side can also be performed by the RAN. In downlink transmission, the SMF determines the time window (t1, t2) for sending messages on the UPF side within the corresponding time window (t1', t2') in the 5G clock domain, and / or determines the time window (t3, t4) for receiving messages on the UE side within the corresponding time window (t3', t4') in the 5G clock domain, which can also be achieved through steps S503-S504.

[0321] In step S505, the SMF sends the time window of the virtual switching node to the RAN. Correspondingly, the RAN receives the time window of the virtual switching node from the SMF.

[0322] For downlink transmission, the SMF sends the UE-side transmission message to the RAN within a time window of (t3, t4) or (t3', t4').

[0323] For uplink transmission, in one possible implementation, the SMF sends the UPF-side message transmission time window (t1, t2) or (t1', t2') to the RAN. If the SMF has not determined the UE-side message reception time window, the SMF also sends the virtual switching node delay information to the RAN, which is used by the RAN to determine the UE-side message reception time window (t3, t4) or (t3', t4'). If the SMF sends the UPF-side message transmission time window (t1, t2) and the virtual switching node delay information to the RAN, then the SMF also sends clock domain offset information to the RAN, so that the RAN can determine the UE-side message reception time window corresponding to the 5G clock domain, i.e., determine (t3', t4'). The method by which the RAN determines the UE-side message reception time window is similar to the method by which the SMF determines the UE-side message reception time window. In another possible implementation, if the SMF determines the time window (t3,t4) or (t3',t4') for the UE to receive the message, then the SMF sends the time window (t3,t4) or (t3',t4') for the UE to receive the message to the RAN. If the SMF sends the time window (t3,t4) for the UE to receive the message to the RAN, then the SMF also sends clock domain offset information to the RAN so that the RAN can determine the time window corresponding to the time window for the UE to receive the message in the 5G clock domain, that is, determine (t3',t4').

[0324] Optionally, if the time window sent by the SMF to the RAN is the time window corresponding to the TSN clock domain, the SMF sends clock domain offset information to the RAN, which is used by the RAN to determine the time window corresponding to the TSN clock domain in the time window corresponding to the 5G clock domain, or for the RAN to synchronize the TSN clock.

[0325] Optionally, for both downlink and uplink transmissions, the SMF also sends the UE's internal processing delay, i.e., UE_DELAY, to the RAN. This delay is used by the RAN to determine the UE's scheduling rules. These scheduling rules are used to limit the time window for the UE to send and receive messages. For example, for downlink transmissions, after the RAN forwards the downlink message to the UE, the UE can receive the message within the limited time window according to the UE's scheduling rules.

[0326] Optionally, for downlink and uplink transmissions, the SMF also sends a delay reservation between the UE and the RAN to the RAN. This reservation restricts the RAN's scheduling rules, such as limiting the RAN's internal processing delay to a maximum of the delay reservation between the UE and the RAN, or limiting the RAN's internal processing delay plus the air interface forwarding delay to a maximum of the delay reservation between the UE and the RAN. The delay reservation between the UE and the RAN includes the air interface forwarding delay reservation between the UE and the RAN, or includes the RAN's internal processing delay reservation plus the air interface forwarding delay reservation between the UE and the RAN.

[0327] Step S506: The RAN determines the time window on the UE side, and determines the RAN's scheduling rules and / or the time delay between the UE and the RAN.

[0328] For downlink transmission, the RAN determines the UE-side time window by receiving the time window (t3,t4) or (t3',t4') of the UE-side message sent from the SMF.

[0329] For uplink transmission, the RAN determines the UE-side time window (t3,t4) or (t3',t4') by receiving the UE-side message reception time window from the SMF. Alternatively, the RAN determines the UE-side message reception time window (t3,t4) or (t3',t4') by receiving the UPF-side message transmission time window (t1,t2) or (t1',t2') from the SMF, along with the virtual switching node's delay information.

[0330] Once the RAN has determined the time window on the UE side, it can combine the UE-side time window with the RAN's scheduling capabilities to determine the RAN's scheduling rules and / or the delay between the UE and the RAN. The delay between the UE and the RAN includes the air interface forwarding delay between the UE and the RAN, or it includes the RAN's internal processing delay plus the air interface forwarding delay between the UE and the RAN. For example, for downlink transmission, the RAN determines the RAN's receiving and sending time windows based on the UE's packet sending time window (t3', t4'), RAN_AIR_UE_DELAY, and AIR_UE_DELAY, and then determines the RAN's scheduling rules to limit the RAN's internal processing delay. The determined RAN scheduling rules satisfy the RAN's scheduling capabilities. For example, for downlink transmission, the RAN determines the delay between the UE and the RAN (the RAN's internal processing delay + the air interface forwarding delay between the UE and the RAN) based on the time window (t3', t4') of the message sent by the UE and UE_DELAY. That is, it determines a difference from the difference range between (t11', t112') and (t3', t4'). The difference between RAN_AIR_UE_DELAY and this difference satisfies the RAN's scheduling capability.

[0331] Optionally, the RAN determines the delay reservation between the UE and the RAN. This can be used when the system has already determined the delay reservation between the UE and the UPF. Based on the delay reservations between the UE and the UPF, and between the UE and the RAN, the delay reservation between the RAN and the UPF can be determined. In this case, the forwarding delay of the virtual switching node can be considered as the delay reservation between the UE and the UPF + the UE's forwarding delay + the UPF's forwarding delay. The UE's forwarding delay is its internal processing delay, and the UPF's forwarding delay is its internal processing delay. It is understood that the delay reservation between the UE and the UPF does not include the UE's internal processing delay and the UPF's internal processing delay. The RAN's determination of the delay reservation between the UE and the RAN can also be used to restrict the RAN's scheduling rules.

[0332] If the SMF sends a delay reservation between the UE and the RAN, the RAN can directly determine the delay reservation between the UE and the RAN, and can directly restrict the RAN's scheduling rules based on the delay reservation between the UE and the RAN.

[0333] Optionally, the RAN determines the UE's scheduling rules. For example, for downlink transmission, the RAN sends the UE's determined scheduling rules to the UE to limit the time window for the UE to send and receive messages; for uplink transmission, the UE sends its scheduling rules to the RAN so that the RAN can know the UE's scheduling rules.

[0334] Optionally, in step S507, the RAN sends the time delay or time delay reservation between the UE and the RAN to the SMF. Correspondingly, the SMF receives the time delay or time delay reservation between the UE and the RAN from the RAN.

[0335] If the RAN determines the time delay or time delay reservation between the UE and the RAN, the RAN executes step S507, sending the time delay or time delay reservation between the UE and the RAN to the SMF. If the RAN does not determine the time delay or time delay reservation between the UE and the RAN, then step S507 may not be executed.

[0336] If the RAN determines the scheduling rules of the UE, then in step S507 the RAN can also send the scheduling rules of the UE to the SMF.

[0337] Optionally, in step S508, the SMF determines the time delay reservation between the UPF and the RAN, and sends the time delay reservation between the UPF and the RAN to the UPF. Correspondingly, the UPF receives the time delay reservation between the UPF and the RAN from the RAN.

[0338] Based on the time delay or time delay reservation between the UE and RAN, and the time delay reservation between the UE and UPF, as determined in step S507, the SMF determines the time delay reservation between the UPF and RAN. For example, the SMF subtracts the time delay reservation between the UE and RAN from the time delay reservation between the UE and UPF to obtain the time delay reservation between the RAN and UPF.

[0339] Upon receiving the time delay reservation between the UPF and the RAN, the UPF can determine the scheduling rules of the UPF and perform deterministic transmission on the UPF.

[0340] Optionally, in step S509, the SMF sends the UE's scheduling rules to the UE. Correspondingly, the UE receives the UE's scheduling rules from the SMF.

[0341] In step S507, if the RAN sends the UE's scheduling rules to the SMF, the SMF executes step S509. Alternatively, the RAN may not send the UE's scheduling rules to the SMF, and the SMF may not send the UE's scheduling rules to the UE. If the RAN has determined the UE's scheduling rules, it may directly send the UE's scheduling rules to the UE.

[0342] Upon receiving its scheduling rules, the UE can perform deterministic transmission on the UE according to those rules.

[0343] exist Figure 10 In the embodiment shown, the RAN determines the RAN scheduling rules and / or the time delay reservation between the UE and the RAN according to the time window on the UE side, so that deterministic transmission can be achieved on the RAN, and then the UE and UPF can achieve deterministic transmission, thus realizing deterministic transmission of the 5G system.

[0344] The methods of the embodiments of this application have been described in detail above, and the apparatus of the embodiments of this application is provided below.

[0345] Please see Figure 11 This is a schematic diagram of the logical structure of a communication device provided in an embodiment of this application. The communication device 60 may include a transceiver unit 601 and a processing unit 602. The communication device 60 is a scheduling rule determination device, which may be an access network device, a session management network element, or a user plane network element.

[0346] Regarding the case where the communication device 60 is an access network device:

[0347] The transceiver unit 501 is used to receive port information from the virtual switching node of the session management network element. The port information of the virtual switching node includes the ingress port information or the egress port information of the virtual switching node.

[0348] The processing unit 602 is configured to determine the time information of the user terminal based on the outgoing port information or the incoming port information of the virtual switching node; determine the scheduling rules of the access network device and / or the latency information between the user terminal and the access network device based on the time information of the user terminal and the scheduling capability of the access network device; and perform transmission based on the scheduling rules of the access network device and / or the latency information between the user terminal and the access device.

[0349] When the communication device 60 is an access network device, it can achieve Figures 6-10 The functions of the RAN in the illustrated embodiment, and the detailed execution process of each unit in the communication device 60, can be found in [reference needed]. Figures 6-10 The execution steps of RAN in the illustrated embodiment will not be repeated here.

[0350] For the case where the communication device has 60 session management network elements:

[0351] The transceiver unit 601 is used to receive the scheduling rules of the virtual switching node, which include the outgoing port information of the virtual switching node; and to send the port information of the virtual switching node to the access network device, which includes the outgoing port information or the incoming port information of the virtual switching node.

[0352] When the communication device 60 is a session management network element, it can achieve... Figures 6-10 The function of the SMF in the illustrated embodiment, and the detailed execution process of each unit in the communication device 60, can be found in [reference needed]. Figures 6-10 The execution steps of SMF in the illustrated embodiment will not be repeated here.

[0353] For the case where the communication device has 60 user plane network elements, it can achieve... Figures 6-10 The function of the UPF in the illustrated embodiment, and the detailed execution process of each unit in the communication device 60, can be found in [reference needed]. Figures 6-10 The execution steps of UPF in the illustrated embodiment will not be repeated here.

[0354] Please see Figure 12 This is a simplified schematic diagram of the physical structure of the communication device provided in the embodiments of this application. The communication device 70 is a scheduling rule determination device, which can be an access network device, a session management network element, or a user plane network element.

[0355] The communication device 70 includes a transceiver 701, a processor 702, and a memory 703. The transceiver 701, processor 702, and memory 703 can be interconnected via a bus 704 or in other ways. Figure 11 The functions implemented by the transceiver unit 601 shown can be implemented by the transceiver 701. Figure 11The related functions implemented by the processing unit 602 shown can be implemented by one or more processors 702.

[0356] The memory 703 includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), and is used for related instructions and data.

[0357] Transceiver 701 is used to transmit data and / or signaling, and to receive data and / or signaling.

[0358] If the communication device 70 is Figures 6-10 In the illustrated embodiment, the transceiver 701 can be used to communicate with the SMF and UE, for example, to perform... Figure 6 Step S102 in the illustrated embodiment; Execute Figure 7 Steps S205a, 207a, and S208b in the illustrated embodiment are executed. Figure 8 Steps S306a, 306b, 306b' and S308 in the illustrated embodiment are executed. Figure 9 Steps S410 and S412 in the illustrated embodiment are executed. Figure 10 Steps S505 and S507 in the illustrated embodiment.

[0359] If the communication device 70 is Figures 6-10 In the illustrated embodiment, the transceiver 701 can be used to communicate with the RAN, UPF, AF, and UE, for example, to perform... Figure 6 Steps S101, S102, and S105 in the illustrated embodiment are executed. Figure 7 Steps S202, S203, S204, S205a, S207a, S208a, S205b, S207b, S208b, and S209 in the illustrated embodiment are executed. Figure 8 Steps S302, S303, S304, S306a, S306b, S306b', S308, and S309 in the illustrated embodiment are executed. Figure 9 Steps S402, S403, S404, S406a, S406b, S406b', S408, S410, and S412 in the illustrated embodiment are executed. Figure 10 Steps S502, S503, S504, S505, S507, S508, and S509 in the illustrated embodiment.

[0360] If the communication device 70 is Figures 6-10 In the illustrated embodiment, the transceiver 701 can be used to communicate with the SMF, for example, to perform... Figure 6 Step S101 in the illustrated embodiment: Execute Figure 7 Steps S203, S204, S208a, S205b, and S207b in the illustrated embodiment are executed. Figure 8 Steps S302, S303, S304, S308, and S309 in the illustrated embodiment are executed. Figure 9 Steps S402, S403, S404, S406a, 406b, 406b', and S408 in the illustrated embodiment are executed. Figure 10 Steps S502, S503, S504, and S508 in the illustrated embodiment.

[0361] Processor 702 may include one or more processors, such as one or more central processing units (CPUs). In the case that processor 702 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.

[0362] If the communication device 70 is Figures 6-10 In the illustrated embodiment, the processor 602 can be used to perform operations that control the RAN, such as executing... Figure 7 Step S206a in the illustrated embodiment; Execute Figure 8 Steps S307a and S307b in the illustrated embodiment are executed. Figure 9 Step S411 in the illustrated embodiment; Execute Figure 10 Step S506 in the illustrated embodiment.

[0363] If the communication device 70 is Figures 6-10 In the illustrated embodiment, the processor 602 can be used to perform operations that control the SMF, such as executing... Figure 6 Step S104 in the illustrated embodiment; Execute Figure 8 Steps S305a and S305b in the illustrated embodiment are executed. Figure 9 Steps S405a, S405b, and S409 in the illustrated embodiment.

[0364] If the communication device 70 is Figures 6-10In the illustrated embodiment, the processor 602 can be used to perform operations that control the UPF, such as executing... Figure 7 Step S206b in the illustrated embodiment; Execute Figure 8 Step S310 in the illustrated embodiment; Execute Figure 9 Steps S407a and S407b in the illustrated embodiment.

[0365] The memory 703 is used to store the program code and data of the communication device 70.

[0366] For details regarding the steps performed by processor 702 and transceiver 701, please refer to [link / reference needed]. Figures 6-10 The description of the illustrated embodiments will not be repeated here.

[0367] Understandable, Figure 12 This is merely a simplified design of the communication device. In practical applications, the communication device may also include other necessary components, including, but not limited to, any number of transceivers, processors, controllers, memory, communication units, etc., and all devices that can implement this application are within the protection scope of this application.

[0368] This application also provides a scheduling rule determination communication system, which may include access network equipment and session management network elements. The access network equipment and session management network elements can be used to implement... Figures 6-10 For details on the functions of RAN and SMF in the illustrated embodiment, please refer to [link / reference needed]. Figures 6-10 The specific implementation process of RAN and SMF in China.

[0369] The scheduling rule determines that the communication system also includes a user plane network element, which can be used to implement... Figures 6-10 For details on the function of the UPF in the illustrated embodiment, please refer to [link / reference]. Figures 6-10 The specific implementation process of UPF in China.

[0370] Those skilled in the art will understand that implementing all or part of the processes in the methods of the above embodiments can be accomplished by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or RAM, magnetic disks, or optical disks. Therefore, another embodiment of this application provides a computer-readable storage medium storing instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.

[0371] Another embodiment of this application provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the methods described in the above aspects.

[0372] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art 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.

[0373] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0374] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0375] The units described as separate components may or may not be physically separate. 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 the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0376] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0377] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted through the computer-readable storage medium. The computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

Claims

1. A method for determining scheduling rules, characterized in that, include: The session management function entity acquires clock domain offset information and determines the reserved scheduling interval for the clock domain access network device based on the clock domain offset information; wherein, the clock domain offset information is the offset of the clock domain in the latency-sensitive network relative to the 5G network clock domain, or the offset of the 5G network clock domain relative to the latency-sensitive network clock domain; the reserved scheduling interval includes the start time for the access network device to receive downlink packets. The session management function entity sends the reserved scheduling interval to the access network device, and the reserved scheduling interval is used to determine the scheduling rules of the access network device; wherein, the scheduling rules of the access network device include the time when the access network device receives the downlink packet.

2. The method according to claim 1, characterized in that, The session management function entity obtains the clock domain offset information, including: The session management function entity receives clock domain offset information from the user plane function entity.

3. The method according to claim 2, characterized in that, The method further includes: The session management function entity sends a clock offset request message to the user plane function entity. The clock offset request message is used to request clock offset information between the clock domain in the latency-sensitive network and the clock domain of the 5G network.

4. The method according to any one of claims 1-3, characterized in that, The start time for the access network device to receive downlink packets includes a minimum value and / or a maximum value, where the minimum value is the earliest time the access network device receives packets, and the maximum value is the latest time the access network device receives packets.

5. The method according to claim 4, characterized in that, The minimum and maximum values ​​are the same.

6. A method for determining scheduling rules, characterized in that, include: The access network device receives a reserved scheduling interval from the session management function entity. The reserved scheduling interval is determined based on clock domain offset information. The clock domain offset information is the offset of the clock domain in the latency-sensitive network relative to the clock domain of the 5G network, or the offset of the clock domain of the 5G network relative to the clock domain of the latency-sensitive network. The reserved scheduling interval includes the start time for the access network device to receive downlink packets. The access network device determines its scheduling rules based on the reserved scheduling interval; wherein, the scheduling rules of the access network device include the time when the access network device receives the downlink message.

7. The method according to claim 6, characterized in that, The start time for the access network device to receive downlink packets includes a minimum value and / or a maximum value, where the minimum value is the earliest time the access network device receives packets, and the maximum value is the latest time the access network device receives packets.

8. The method according to claim 7, characterized in that, The minimum and maximum values ​​are the same.

9. A device, characterized in that, include: Memory is used to store instructions that are executed by one or more processors of a device; And a processor, one of the processors of the device, for executing instructions stored in the memory to implement the method of any one of claims 1 to 8.

10. A method for determining scheduling rules, characterized in that, include: The session management function entity acquires clock domain offset information and determines the reserved scheduling interval for the clock domain access network device based on the clock domain offset information; wherein, the clock domain offset information is the offset of the clock domain in the latency-sensitive network relative to the 5G network clock domain, or the offset of the 5G network clock domain relative to the latency-sensitive network clock domain; the reserved scheduling interval includes the start time for the access network device to receive downlink packets. The session management function entity sends the reserved scheduling interval to the access network device; The access network device determines its scheduling rules based on the reserved scheduling interval; wherein, the scheduling rules of the access network device include the time when the access network device receives the downlink message.

Images