Embodiments of this application relate to the wireless communication field, and in particular, to a communication method and apparatus.
In a data packet forwarding process of a conventional Ethernet, in response to a large quantity of data packets arriving at a forwarding port within short time, a forwarding latency is high or a packet loss problem is caused. Therefore, the conventional Ethernet cannot provide services with high reliability and a guaranteed transmission latency, and cannot meet conditions of fields such as vehicle control and industrial internet.
The institute of electrical and electronics engineers (institute of electrical and electronics engineers, IEEE) defines a time sensitive networking (time sensitive networking, TSN) standard to meet a condition on reliable latency transmission. The standard can provide reliable latency transmission services based on layer 2 switching, ensure data transmission reliability of latency-sensitive services, and ensure predictable end-to-end transmission latencies.
As shown in
An entire 5G system (5G System, 5GS) may be used as a switching node. The CNC network element may configure each switching node based on information reported by the 5GS and another switching node, to ensure an end-to-end (from the TSN talker to the TSN listener) deterministic latency. As shown in
For a data packet with a deterministic latency condition, the 5GS is to determine a corresponding packet delay budget (packet delay budget, PDB) based on the latency condition of the data packet, and ensure that transmission time of the data packet between the UE and the UPF network element is not greater than the PDB. How to meet the deterministic latency condition and improve overall network performance is an urgent problem to be resolved.
According to a first aspect, at least one embodiment provides a communication method. The method includes:
A first device determines information about service flow arrival time, where the information about the service flow arrival time includes the service flow arrival time or an offset of the service flow arrival time relative to reference time, the service flow arrival time is time at which a first service flow arrives at a second device, and the first service flow is a periodic service flow to be transmitted between an access network device and a user plane network element. The first device determines information about service flow sending time based on the information about the service flow arrival time. The first device indicates the second device to wait, after receiving the first service flow, until the service flow sending time to send the first service flow. In response to the first service flow being an uplink service flow, the second device is the access network device or a translator corresponding to the access network device; or in response to the first service flow being a downlink service flow, the second device is the user plane network element.
According to the foregoing method, the first device first determines the information about the service flow arrival time, and determines the information about the service flow sending time based on the information about the service flow arrival time, so that after receiving the first service flow, the second device may wait until the service flow sending time to send the first service flow. In other words, the first device configures time at which the second device sends the first service flow, and the second device waits, according to configuration and indication of the first device, until the specified service flow sending time to send the first service flow. Through coordinated configuration of the first device, even in response to the second device receiving a plurality of service flows simultaneously or within a time period, congestion does not occur, so that a deterministic latency condition of each flow can be met, and therefore overall network performance can be improved.
In at least one embodiment, in response to indicating the second device to wait, after receiving the first service flow, until the service flow sending time to send the first service flow, the first device sends the information about the service flow sending time to the second device.
In at least one embodiment, the information about the service flow sending time includes the service flow sending time or an offset of the service flow sending time relative to the reference time. The service flow sending time is not later than latest sending time, and the latest sending time is determined based on the information about the service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the latest sending time is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time does not exceed a maximum offset, and the maximum offset is determined based on the information about the service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the maximum offset is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device.
In the foregoing design, the service flow sending time is not later than the latest sending time, or the offset of the service flow sending time relative to the reference time does not exceed the maximum offset, so that a latency condition of the first service flow can be met in response to the second device sending the first service flow.
In at least one embodiment, the service flow sending time is not earlier than earliest sending time, and the earliest sending time is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time is greater than or equal to a minimum offset, and the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device.
In at least one embodiment, parameters for determining the latest sending time, the maximum offset, the earliest sending time, or the minimum offset further include a jitter latency associated with the first service flow.
In at least one embodiment, service flow sending time that is determined by the first device and at which the second device sends a second service flow is different from the service flow sending time that is determined by the first device and at which the second device sends the first service flow, the second service flow is a periodic service flow to be transmitted between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device at the same time, or a difference between time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold.
In the foregoing design, the first device determines different service flow sending time for the first service flow and the second service flow, so that congestion between the first service flow and the second service flow can be avoided, and deterministic latency conditions separately of the first service flow and the second service flow can be ensured.
In at least one embodiment, in response to determining the information about the service flow sending time based on the information about the service flow arrival time, the first device obtains an offset selection value, where the offset selection value is greater than or equal to the minimum offset and less than or equal to the maximum offset, or the offset selection value is greater than or equal to an offset of the earliest sending time relative to the reference time and less than or equal to an offset of the latest sending time relative to the reference time; and the first device determines the information about the service flow sending time based on the offset selection value.
In the foregoing design, the first device first determines the minimum offset and the maximum offset, or the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time, then obtains the offset selection value, and determines the information about the service flow sending time based on the offset selection value.
In at least one embodiment, in response to obtaining the offset selection value, the first device sends, to a fourth device, the minimum offset and the maximum offset, or the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time; and the first device receives the offset selection value from the fourth device.
In at least one embodiment, in response to obtaining the offset selection value, the first device determines, based on a packet delay budget for transmitting the first service flow between the second device and a third device, the processing time of the first service flow in the second device, and processing time of the first service flow in the third device, a latency condition for transmitting the first service flow between the second device and the third device; and the first device sends the latency condition to the fourth device. The third device is a device that is to receive the first service flow, and in response to the first service flow being an uplink service flow, the third device is the user plane network element, or in response to the first service flow being a downlink service flow, the third device is the access network device or the translator corresponding to the access network device.
In the foregoing design, the fourth device may determine the offset selection value with reference to the latency condition. In addition, the first device further sends a priority of the first service flow to the fourth device. The fourth device may refer to a plurality of parameters in response to determining the offset selection value. How the fourth device determines the offset selection value is not limited in at least one embodiment.
In at least one embodiment, in response to determining the information about the service flow sending time based on the offset selection value, the first device determines the information about the service flow sending time based on the offset selection value and the jitter latency associated with the first service flow.
In at least one embodiment, the information about the service flow sending time includes a gate control scheduling parameter. The first device may determine the gate control scheduling parameter according to the following method: The first device obtains the cycle of the first service flow and the maximum burst size of the first service flow. The first device determines a size of a maximum frame of the first service flow based on the maximum burst size of the first service flow. The first device determines the gate control scheduling parameter based on the cycle of the first service flow, the size of the maximum frame of the first service flow, and the offset selection value.
In the foregoing design, the first device may determine the gate control scheduling parameter based on the cycle of the first service flow, the maximum burst size of the first service flow, and the offset selection value. The gate control scheduling parameter herein is a gate control scheduling parameter for the second device.
In at least one embodiment, in response to the first service flow being an uplink service flow, the first service flow arrives at the second device through a terminal device. In response to determining the information about the service flow arrival time, the first device obtains information about time at which the first service flow arrives at a translator on a terminal device side, residence time of the first service flow in the terminal device and in the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device; and the first device determines the information about the service flow arrival time based on the information about the time at which the first service flow arrives at the translator on the terminal device side, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device.
In the foregoing design, the first device may determine the information about the service flow arrival time in a scenario in which the first service flow is an uplink service flow.
In at least one embodiment, the first device is a time sensitive networking TSN application function network element. In response to obtaining the information about the time at which the first service flow arrives at the translator on the terminal device side, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device, the first device determines the information about the time at which the first service flow arrives at the translator on the terminal device side; and the first device receives, from a session management network element, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device.
In at least one embodiment, the first device is a session management network element. In response to obtaining the information about the time at which the first service flow arrives at the translator on the terminal device side, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device, the first device receives, from a policy control network element, the information about the time at which the first service flow arrives at the translator on the terminal device side; the first device receives, from the terminal device, the residence time of the first service flow in the terminal device and in the translator on the terminal device side; and the first device determines the packet delay budget for transmitting the first service flow between the terminal device and the second device.
According to a second aspect, at least one embodiment provides a communication method. The method includes: A second device receives a first service flow, where the first service flow is a periodic service flow to be transmitted between an access network device and a user plane network element. The second device receives, from a first device, information about service flow sending time. The second device waits until the service flow sending time indicated by the information about the service flow sending time to send the first service flow. In response to the first service flow being an uplink service flow, the second device is the access network device or a translator corresponding to the access network device; or in response to the first service flow being a downlink service flow, the second device is the user plane network element.
According to the foregoing method, after receiving the first service flow at service flow arrival time, the second device waits until the service flow sending time indicated by the first device to send the first service flow. Therefore, the second device may send the first service flow based on the service flow sending time indicated by the first device. In other words, the first device configures time at which the second device sends the first service flow, and the second device waits, according to configuration and indication of the first device, until the specified service flow sending time to send the first service flow. Through coordinated configuration of the first device, even in response to the second device receiving a plurality of service flows simultaneously or within a time period, congestion does not occur, so that a deterministic latency condition of each flow can be met, and therefore overall network performance can be improved.
In at least one embodiment, service flow sending time at which the second device sends a second service flow is different from the service flow sending time at which the second device sends the first service flow, the second service flow is a periodic service flow to be transmitted between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device at the same time, or a difference between time at which the second service flow arrives at the second device and time at which the first service flow arrives at the second device is less than or equal to a threshold.
In at least one embodiment, the information about the service flow sending time includes the service flow sending time or an offset of the service flow sending time relative to reference time. The service flow sending time is not later than latest sending time, and the latest sending time is determined based on information about service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the latest sending time is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time does not exceed a maximum offset, and the maximum offset is determined based on information about service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the maximum offset is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device.
In at least one embodiment, the service flow sending time is not earlier than earliest sending time, and the earliest sending time is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time is greater than or equal to a minimum offset, and the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device.
In at least one embodiment, parameters for determining the latest sending time, the maximum offset, the earliest sending time, or the minimum offset further include a jitter latency associated with the first service flow.
In at least one embodiment, the information about the service flow sending time includes a gate control scheduling parameter.
In at least one embodiment, the first device is a TSN application function network element, or the first device is a session management network element.
According to a third aspect, at least one embodiment provides a communication apparatus. The apparatus is a first device or an apparatus having a function of the first device, and the apparatus includes:
In at least one embodiment, in response to indicating the second device to wait, after receiving the first service flow, until the service flow sending time to send the first service flow, the transceiver unit is configured to send the information about the service flow sending time to the second device.
In at least one embodiment, the information about the service flow sending time includes the service flow sending time or an offset of the service flow sending time relative to the reference time. The service flow sending time is not later than latest sending time, and the latest sending time is determined based on the information about the service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the latest sending time is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time does not exceed a maximum offset, and the maximum offset is determined based on the information about the service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the maximum offset is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device.
In at least one embodiment, the service flow sending time is not earlier than earliest sending time, and the earliest sending time is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time is greater than or equal to a minimum offset, and the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device.
In at least one embodiment, parameters for determining the latest sending time, the maximum offset, the earliest sending time, or the minimum offset further include a jitter latency associated with the first service flow.
In at least one embodiment, service flow sending time that is determined by the first device and at which the second device sends a second service flow is different from the service flow sending time that is determined by the first device and at which the second device sends the first service flow, the second service flow is a periodic service flow to be transmitted between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device at the same time, or a difference between time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold.
In at least one embodiment, in response to determining the information about the service flow sending time based on the information about the service flow arrival time, the processing unit is configured to: obtain an offset selection value, where the offset selection value is greater than or equal to the minimum offset and less than or equal to the maximum offset, or the offset selection value is greater than or equal to an offset of the earliest sending time relative to the reference time and less than or equal to an offset of the latest sending time relative to the reference time; and determine the information about the service flow sending time based on the offset selection value.
In at least one embodiment, the transceiver unit is configured to: send, to a fourth device, the minimum offset and the maximum offset, or the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time; and receive the offset selection value from the fourth device.
In at least one embodiment, the processing unit is further configured to determine, based on a packet delay budget for transmitting the first service flow between the second device and a third device, the processing time of the first service flow in the second device, and processing time of the first service flow in the third device, a latency condition for transmitting the first service flow between the second device and the third device; and the transceiver unit is further configured to send the latency condition to the fourth device. The third device is a device that is to receive the first service flow, and in response to the first service flow being an uplink service flow, the third device is the user plane network element, or in response to the first service flow being a downlink service flow, the third device is the access network device or the translator corresponding to the access network device.
In at least one embodiment, in response to determining the information about the service flow sending time based on the offset selection value, the processing unit is configured to determine the information about the service flow sending time based on the offset selection value and the jitter latency associated with the first service flow.
In at least one embodiment, the information about the service flow sending time includes a gate control scheduling parameter. The processing unit is configured to: obtain the cycle of the first service flow and the maximum burst size of the first service flow; determine a size of a maximum frame of the first service flow based on the maximum burst size of the first service flow; and determine the gate control scheduling parameter based on the cycle of the first service flow, the size of the maximum frame of the first service flow, and the offset selection value.
In at least one embodiment, in response to the first service flow being an uplink service flow, the first service flow arrives at the second device through a terminal device. In response to determining the information about the service flow arrival time, the processing unit is configured to: obtain information about time at which the first service flow arrives at a translator on a terminal device side, residence time of the first service flow in the terminal device and in the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device; and determine the information about the service flow arrival time based on the information about the time at which the first service flow arrives at the translator on the terminal device side, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device.
In at least one embodiment, the first device is a time sensitive networking TSN application function network element. In response to obtaining the information about the time at which the first service flow arrives at the translator on the terminal device side, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device, the processing unit is configured to determine the information about the time at which the first service flow arrives at the translator on the terminal device side. The transceiver unit is configured to receive, from a session management network element, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device.
In at least one embodiment, the first device is a session management network element. In response to the information about the time at which the first service flow arriving at the translator on the terminal device side, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device are obtained, the transceiver unit is configured to: receive, from a policy control network element, the information about the time at which the first service flow arrives at the translator on the terminal device side; and receive, from the terminal device, the residence time of the first service flow in the terminal device and in the translator on the terminal device side. The processing unit is configured to determine the packet delay budget for transmitting the first service flow between the terminal device and the second device.
According to a fourth aspect, at least one embodiment provides a communication apparatus. The apparatus is a second device or an apparatus having a function of the second device, and the apparatus includes: a transceiver unit, configured to: receive a first service flow, where the first service flow is a periodic service flow to be transmitted between an access network device and a user plane network element; and receive, from a first device, information about service flow sending time; and a processing unit, configured to wait until the service flow sending time indicated by the information about the service flow sending time to send the first service flow to a third device. In response to the first service flow being an uplink service flow, the second device is the access network device or a translator corresponding to the access network device; or in response to the first service flow being a downlink service flow, the second device is the user plane network element.
In at least one embodiment, the information about the service flow sending time includes the service flow sending time or an offset of the service flow sending time relative to reference time. The service flow sending time is not later than latest sending time, and the latest sending time is determined based on information about service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the latest sending time is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time does not exceed a maximum offset, and the maximum offset is determined based on information about service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the maximum offset is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device.
In at least one embodiment, the service flow sending time is not earlier than earliest sending time, and the earliest sending time is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time is greater than or equal to a minimum offset, and the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device.
In at least one embodiment, parameters for determining the latest sending time, the maximum offset, the earliest sending time, or the minimum offset further include a jitter latency associated with the first service flow.
In at least one embodiment, service flow sending time at which the second device sends a second service flow is different from the service flow sending time at which the second device sends the first service flow, the second service flow is a periodic service flow to be transmitted by the second device between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device at the same time, or a difference between time at which the second service flow arrives at the second device and time at which the first service flow arrives at the second device is less than or equal to a threshold.
In at least one embodiment, the information about the service flow sending time includes a gate control scheduling parameter.
In at least one embodiment, the first device is a TSN application function network element, or the first device is a session management network element.
According to a fifth aspect, at least one embodiment further provides an apparatus. The apparatus may perform the foregoing method design. The apparatus may be a chip or a circuit that can perform the functions corresponding to the foregoing method, or a device including the chip or the circuit.
In at least one embodiment, the apparatus includes: a memory, configured to store computer-executable program code; and a processor, where the processor is coupled to the memory. The program code stored in the memory includes instructions. In response to the processor executing the instructions, the apparatus or a device on which the apparatus is installed is enabled to perform the method in at least one embodiment.
The apparatus may further include a communication interface. The communication interface may be a transceiver. Alternatively, in response to the apparatus being a chip or a circuit, the communication interface may be an input/output interface of the chip, for example, an input/output pin.
In at least one embodiment, the apparatus includes corresponding functional units, separately configured to implement the steps in the foregoing method. The functions may be implemented by hardware, or may be implemented by hardware by executing corresponding software. The hardware or the software includes one or more units that correspond to the foregoing functions.
According to a sixth aspect, at least one embodiment provides a computer-readable storage medium. The computer-readable storage medium stores a computer program. In response to the computer program being run on an apparatus, the method in at least one embodiment is performed.
According to a seventh aspect, at least one embodiment provides a computer program product. The computer program product includes a computer program. In response to the computer program being run on an apparatus, the method in at least one embodiment is performed.
According to an eighth aspect, at least one embodiment provides a communication system. The system includes a first device and a second device. The first device is configured to perform the method in the first aspect, and the second device is configured to perform the method in the second aspect.
In at least one embodiment, the first device is a TSN application function network element, or the first device is a session management network element.
In at least one embodiment, in response to a first service flow being an uplink service flow, the second device is an access network device or a translator corresponding to the access network device; or in response to a first service flow being a downlink service flow, the second device is a user plane network element.
In at least one embodiment, the system further includes a third device, and the third device is a device that is to receive the first service flow. In response to the first service flow being an uplink service flow, the third device is a user plane network element. In response to the first service flow being a downlink service flow, the third device is an access network device or a translator corresponding to the access network device.
According to a ninth aspect, at least one embodiment provides a communication system. The system includes a second device and a third device. The second device is configured to perform the method in the second aspect. The third device is a device that is to receive a first service flow.
For example, in response to the first service flow being an uplink service flow, the second device is an access network device or a translator corresponding to the access network device, and the third device is a user plane network element.
In response to the first service flow being a downlink service flow, the second device is a user plane network element, and the third device is an access network device or a translator corresponding to the access network device.
The following clearly and completely describes technical solutions in embodiments described herein with reference to accompanying drawings in at least one embodiment. Clearly, the described embodiments are merely some but not all of embodiments described herein. In at least one embodiment, claims, and accompanying drawings, terms such as “first” and “second” and corresponding numerals of the terms are intended to distinguish between similar objects, but do not necessarily indicate a specific order or sequence. The terms used in such a way are interchangeable in proper circumstances, which is merely a discrimination manner that is used in response to objects having a same attribute are described in at least one embodiment. In addition, terms “include”, “have” and any other variants thereof are intended to cover the non-exclusive inclusion, so that a process, method, system, product, or device that includes a series of units is not necessarily limited to those units, but may include other units not expressly listed or inherent to the process, method, product, or device.
In descriptions of at least one embodiment, “/” means “or” unless otherwise specified. For example, A/B may represent A or B. In at least one embodiment, “and/or” describes only an association relationship for describing associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. In addition, in the descriptions of at least one embodiment, “at least one item” means one or more items, and “a plurality of items” means two or more items. “At least one of the following items (pieces)” or a similar expression thereof refers to any combination of these items, including any combination of singular items (pieces) or plural items (pieces). For example, at least one of a, b, or c may indicate a, b, c, a and b, a and c, b and c, or a, b, and c, where a, b, and c may be singular or plural.
The technical solutions provided in at least one embodiment may be applied to various communication systems. For example, the technical solutions are applicable to a long term evolution (long term evolution, LTE) system or a 5G system, or are applicable to another future-oriented new system, for example, a programmable user plane system. This is not specifically limited in at least one embodiment. In addition, terms “system” and “network” are interchangeable.
The following briefly describes devices in at least one embodiment with reference to
A terminal device may be connected to an access network device, to access a communication system. The terminal device may also be referred to as a terminal, UE, a mobile station, a mobile terminal, or the like. The terminal device may be a mobile phone, a tablet computer, a computer having a wireless transceiver function, a virtual reality terminal device, an augmented reality terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, or the like. A specific technology and a specific device form that are used for the terminal device are not limited in at least one embodiment. As shown in
An access network device may be a base station (base station), an evolved base station (evolved NodeB, eNodeB), a transmission reception point (transmission reception point, TRP), a gNB, a base station in a future mobile communication system, an access node in a Wi-Fi system, or the like. Alternatively, the access network device may be a module or unit that completes some functions of a base station, for example, may be a central unit (central unit, CU) or a distributed unit (distributed unit, DU). A specific technology and a specific device form that are used for the access network device are not limited in at least one embodiment. As shown in
An access management network element is used for mobility management, access management, and the like, for example, location update of a terminal device, registration of a terminal device with a network, and terminal device handover. The access management network element may be a mobility management entity (mobility management entity, MME) function in a 4G mobile communication system or an AMF network element in a 5G mobile communication system. In a future mobile communication system, for example, a 6G mobile communication system, the access management network element may still be the AMF network element, or may have another name. This is not limited in at least one embodiment. Namf is a service-based interface provided by the AMF. The AMF may communicate with another network function through the Namf. As shown in
A session management network element is used for session management, for example, session establishment, modification, and release. The session management network element is further configured to: allocate an internet protocol (Internet Protocol, IP) address to a terminal device, select a UPF that provides a data packet forwarding function, and so on. In a 5G mobile communication system, the session management network element may be an SMF network element. In a future mobile communication system, for example, a 6G mobile communication system, the session management function network element may still be the SMF network element, or may have another name. This is not limited in at least one embodiment. Nsmf is a service-based interface provided by the SMF. The SMF may communicate with another network function through the Nsmf. As shown in
A policy control network element is configured to provide, for an access management network element or a session management network element, policy rule information and the like, for example, a quality of service (Quality of Service, QoS) policy and a slice selection policy. In a 5G mobile communication system, the policy control network element may be a PCF network element. In a future mobile communication system, for example, a 6G mobile communication system, the policy control function network element may still be the PCF network element, or may have another name. This is not limited in at least one embodiment. As shown in
A data management network element is configured to store data of a terminal device, for example, subscription information and authentication/authorization information. In a 5G mobile communication system, the data management network element may be a UDM network element. In a future mobile communication system, for example, a 6G mobile communication system, the data management network element may still be the UDM network element, or may have another name. This is not limited in at least one embodiment. As shown in
A data repository network element is responsible for storing structured data, and stored content includes subscription data, policy data, externally exposed structured data, and application-related data. In a 5G mobile communication system, the data repository network element may be a UDR network element. In a future communication system, for example, a 6G mobile communication system, the data repository network element may still be the UDR network element, or may have another name. This is not limited in at least one embodiment.
An authentication server function network element is mainly responsible for providing an authentication function and supporting authentication of 3GPP access and non-3GPP (Non-3GPP) access. In a 5G mobile communication system, the authentication server function network element may be an authentication server function AUSF network element. In a future communication system, for example, a 6G mobile communication system, the authentication server function network element may still be the AUSF network element, or may have another name. This is not limited in at least one embodiment.
A network exposure function network element mainly provides a service, so that a 3GPP network can securely provide a network service capability to a third-party service provider, namely, an application function network element. In a 5G communication system, the network exposure function network element may be an NEF network element. In a future communication system, for example, a 6G mobile communication system, the network exposure function network element may still be the NEF network element, or may have another name. This is not limited in at least one embodiment.
An application function network element is configured to provide a service for a 3GPP network, for example, affect service routing, and interact with a policy control network element for policy control. In 5G communication, the application function network element may be an AF network element. In future communication, for example, 6G communication, the application function network element may still be the AF network element, or may have another name. This is not limited in at least one embodiment. As shown in
A user plane network element is configured to process a data packet of a terminal device, for example, perform forwarding and charging. In 5G communication, the user plane network element may be a UPF network element. In future communication, for example, 6G communication, the user plane network element may still be the UPF network element, or may have another name. This is not limited in at least one embodiment. As shown in
A data network (data network, DN) is a network that provides a data transmission service for a terminal device. The data network may be a private network, for example, a local area network, or an external network that is not managed and controlled by an operator, for example, the internet (Internet), or a dedicated network deployed by an operator, for example, a network that provides an IP multimedia core network subsystem (IP multimedia core network subsystem, IMS) service. The terminal device may access the data network by establishing a connection from the terminal device to the data network through an access network device and a user plane network element.
Currently, a fully centralized configuration model is defined for a TSN system.
A TSN terminal includes a talker and a listener. The talker and the listener are respectively a sender and a receiver of a service flow.
A CUC network element is responsible for discovering and managing the TSN terminal, obtaining capability information and a user condition of the TSN terminal, sending a condition of the service flow to a CNC network element, and configuring the TSN terminal according to indication of the CNC network element.
The CNC network element is configured to: determine an end-to-end (end-to-end, E2E) forwarding path of the service flow based on a topology of a user plane of the TSN system (including a topology between the TSN terminal and each switching node), capability information of each switching node, and the condition of the service flow that is sent by the CUC network element, and configure a switching node on the forwarding path.
The switching node is configured to: send capability information of the switching node to the CNC network element, determine a gate control scheduling parameter based on configuration information of the CNC network element, and schedule and forward the service flow based on the gate control scheduling parameter.
A DS-TT may be located inside UE or may be located outside the UE, and an NW-TT may be located inside a UPF. A downlink data packet is used as an example. The DS-TT may determine a gate control scheduling parameter based on configuration information sent by a CNC network element, and send the data packet based on the gate control scheduling parameter. To ensure that the data packet can be sent in time, time at which the data packet arrives at the DS-TT cannot be later than a specific moment, to ensure that the data packet can be sent in a gate opening process. The gate opening process refers to a range of duration in which a gate state is Open. In response to the data packet arriving at the DS-TT before start time, indicated by the gate control scheduling parameter, from which the gate state is Open, the data packet is to be buffered at the DS-TT until time at which the gate state is Open for sending. In response to the data packet arriving at the DS-TT after the start time, indicated by the gate control scheduling parameter, from which the gate state is Open, the DS-TT is to complete sending of the data packet before the gate state is switched to a closed state. Similarly, the NW-TT may also determine a gate control scheduling parameter based on configuration information sent by the CNC network element, and send a data packet based on the gate control scheduling parameter. For example, the NW-TT may send, to a next-hop switching node adjacent to the 5GS on a forwarding path, an uplink service flow received through the 5GS; or the NW-TT may be configured to receive a downlink service flow from a previous-hop switching node adjacent to the 5GS on a forwarding path, and send the downlink service flow to the 5GS.
As shown in
As shown in
In at least one embodiment, the data packet may also be referred to as a packet, a data packet, a data frame, a frame, or the like. The following uses only the data packet as an example for description.
At least one embodiment may be applied to network architectures shown in
For example, as shown in
In the domain 2, a translator corresponding to an access network device is added on a gNB side. The translator corresponding to the access network device may be denoted as an AN-TT (as shown in
In addition, another translator corresponding to the UPF network element is added on a UPF network element side, and the translator is located inside the UPF network element. In other words, functional modules of two translators are integrated inside the UPF. One translator is the foregoing described NW-TT, and the other translator may be denoted as an N3 interface translator, namely, an N3-TT (as shown in
In addition, the two newly added translators may alternatively have other names. This is not limited in at least one embodiment.
Based on a layout of the network architecture in
The network architecture shown in
In the network architectures shown in
At least one embodiment may be applied to domains 2 shown in
For example, as shown in
For example, as shown in
For
At least one embodiment provides a communication method, to implement a low transmission latency between a gNB and a UPF, and improve overall network performance. In the method, deterministic transmission is supported between the gNB and the UPF, so that a data packet can arrive at the gNB or the UPF (or an NW-TT) within a predetermined time window, in other words, the long tail effect shown in
The communication method relates to a first device, a second device, and a third device. For example, the first device may be a session management network element, for example, the SMF network element in
Optionally, the method may further relate to a fourth device. For example, the fourth device may be the CNC-transport network (transport network, TN) in
In a scenario in which a first service flow is an uplink service flow (corresponding to the following scenario 1), a packet delay budget (PDB 3) for transmitting the first service flow between a terminal device and the user plane network element indicates an upper limit of a latency from time at which the terminal device receives a data packet of the first service flow to time at which the user plane network element or the NW-TT completes processing of the data packet and sends the data packet to a next-hop node.
In response to the second device being the access network device and the third device being the user plane network element, the translator (namely, the AN-TT) corresponding to the access network device is used as a functional module inside the access network device. A packet delay budget (PDB 1) for transmitting the first service flow between the terminal device and the access network device indicates an upper limit of a latency from the time at which the terminal device receives the data packet of the first service flow to time at which the data packet of the first service flow arrives at a PDCP layer or an SDAP layer of the access network device. A packet delay budget (PDB 2) for transmitting the first service flow between the access network device and the user plane network element indicates an upper limit of a latency from time at which the data packet of the first service flow is sent from the PDCP layer or the SDAP layer of the access network device to the time at which the user plane network element or the NW-TT completes processing of the data packet and sends the data packet to the next-hop node. The PDB 3 is equal to a sum of the PDB 1 and the PDB 2.
In this case, a packet delay budget for transmitting the first service flow between the second device and the third device corresponds to the PDB 2.
In response to the second device being the translator (namely, the AN-TT) corresponding to the access network device and the third device being the user plane network element, the AN-TT is a device that is independently deployed outside the access network device. A packet delay budget (PDB 1′) for transmitting the first service flow between the terminal device and the translator (namely, the AN-TT) corresponding to the access network device indicates an upper limit of a latency from the time at which the terminal device receives the data packet of the first service flow to time at which the data packet of the first service flow arrives at the AN-TT. A packet delay budget (PDB 2′) for transmitting the first service flow between the translator corresponding to the access network device and the user plane network element indicates an upper limit of a latency from time at which the AN-TT receives the data packet of the first service flow to the time at which the user plane network element or the NW-TT completes processing of the data packet and sends the data packet to the next-hop node. The PDB 3 is equal to a sum of the PDB 1′ and the PDB 2′.
In this case, a packet delay budget for transmitting the first service flow between the second device and the third device corresponds to the PDB 2′.
For example, in a scenario in which a first service flow is a downlink service flow (corresponding to the following scenario 2), a packet delay budget (PDB 6) for transmitting the first service flow between the user plane network element and a terminal device indicates an upper limit of a latency from time at which a packet of the first service flow is received by the user plane network element or the NW-TT from a previous-hop switching node to time at which the packet arrives at the terminal device (for example, an application layer of the terminal device).
In response to the second device being the user plane network element and the third device being the access network device, the translator (namely, the AN-TT) corresponding to the access network device is used as a functional module inside the access network device. A packet delay budget (PDB 4) for transmitting the first service flow between the user plane network element and the access network device indicates an upper limit of a latency from the time at which the packet of the first service flow is received by the user plane network element or the NW-TT from the previous-hop switching node to time at which a general packet radio service (general packet radio service, GPRS) tunnel protocol for the user plane (GPRS Tunnel Protocol for the user plane, GTP-U) layer of the access network device completes processing of the packet. A packet delay budget (PDB 5) for transmitting the first service flow between the access network device and the terminal device indicates an upper limit of a latency from time at which the packet of the first service flow is sent from a PDCP layer or an SDAP layer of the access network device to the time at which the packet of the first service flow arrives at the terminal device (for example, the application layer of the terminal device). The PDB 6 is equal to a sum of the PDB 4 and the PDB 5.
In this case, a packet delay budget for transmitting the first service flow between the second device and the third device corresponds to the PDB 4.
In response to the second device being the user plane network element and the third device being the translator (namely, the AN-TT) corresponding to the access network device, the AN-TT is a device that is independently deployed outside the access network device. A packet delay budget (PDB 4′) for transmitting the first service flow between the user plane network element and the translator (namely, the AN-TT) corresponding to the access network device indicates an upper limit of a latency from time at which the user plane network element or the NW-TT receives the packet of the first service flow to time at which the AN-TT completes processing of the packet. A packet delay budget (PDB 5′) for transmitting the first service flow between the translator (namely, the AN-TT) corresponding to the access network device and the terminal device indicates an upper limit of a latency from time at which the packet of the first service flow is sent from the AN-TT to the time at which the packet of the first service flow arrives at the terminal device (for example, the application layer of the terminal device). The PDB 6 is equal to a sum of the PDB 4′ and the PDB 5′.
In this case, a packet delay budget for transmitting the first service flow between the second device and the third device corresponds to the PDB 4′.
The following describes the communication method with reference to
Step 800: A first device determines information about service flow arrival time, where the service flow arrival time is time at which a first service flow arrives at a second device, and the first service flow is a periodic service flow to be sent between an access network device and a user plane network element.
The information about the service flow arrival time may be the service flow arrival time, or may be an offset of the service flow arrival time relative to reference time.
The first service flow may be a TSN service flow that is referred to as a TSN flow for short. For example, the first service flow may be a TSN flow sent from a talker to a listener in
The first device may determine at least one of the service flow arrival time or the offset of the service flow arrival time relative to the reference time. In at least one embodiment, the first device may first determine the offset of the service flow arrival time relative to the reference time, and then determine the service flow arrival time based on the offset of the service flow arrival time relative to the reference time. Alternatively, after determining the offset of the service flow arrival time relative to the reference time, the first device does not further determine the service flow arrival time. In at least one embodiment, the first device may first determine the service flow arrival time, and then determine, based on the service flow arrival time, the offset of the service flow arrival time relative to the reference time. Alternatively, after determining the service flow arrival time, the first device does not further determine the offset of the service flow arrival time relative to the reference time.
A specific process in which the first device determines the information about the service flow arrival time is described below with reference to two scenarios by using examples.
Scenario 1: In response to the first service flow being an uplink service flow, the second device is the access network device or a translator corresponding to the access network device. In other words, the first service flow is an uplink service flow to be sent by the access network device to the user plane network element.
For example, that the second device is the access network device or a translator corresponding to the access network device may be understood as follows: In response to the translator corresponding to the access network device and the access network device being separately deployed, the second device may be the translator corresponding to the access network device. For example, the service flow arrival time may be time at which the first service flow arrives at the translator (for example, the foregoing AN-TT) corresponding to the access network device. In response to the translator corresponding to the access network device being used as a functional module inside the access network device, the second device may be an access network device that includes a translator function, in other words, the second device may be the access network device. Correspondingly, the service flow arrival time may be time at which the first service flow arrives at the access network device. For example, the service flow arrival time is time at which the first service flow arrives at a packet data convergence protocol (packet data convergence protocol, PDCP) layer or a service data adaptation protocol (Service Data Adaptation Protocol, SDAP) layer of the access network device.
In this case, a forwarding path of the first service flow in the mobile communication system includes at least a terminal device, the access network device, and the user plane network element. Optionally, on the forwarding path, at least one switch or router may be further included between the access network device and the user plane network element.
For example, as shown in
In an implementation, the first device may obtain information about time at which the first service flow arrives at a translator (for example, a DS-TT) on a terminal device side, residence time of the first service flow in the terminal device and in the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device.
For example, the information about the time at which the first service flow arrives at the translator (for example, the DS-TT) on the terminal device side specifically refers to information about time at which a data packet of the first service flow in a specific cycle arrives at the translator on the terminal device side, and may be determined based on burst arrival time (burst arrival time) at which the first service flow arrives at the DS-TT and a cycle of the first service flow. The information about the time at which the first service flow arrives at the translator on the terminal device side may be the time at which the first service flow arrives at the translator on the terminal device side or an offset of the time at which the first service flow arrives at the translator on the terminal device side relative to the reference time. The reference time refers to start time of a time domain (for example, 00:00:00 on Jan. 1, 1970).
The residence time of the first service flow in the terminal device and in the translator on the terminal device side may be residence time of the first service flow between the DS-TT and the UE in
Further, the first device may determine the service flow arrival time or the offset of the service flow arrival time relative to the reference time based on the information about the time at which the first service flow arrives at the translator on the terminal device side, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device. An example is provided below:
T1 (uplink) indicates service flow arrival time in an uplink scenario, and T1-offset (uplink) indicates an offset of the service flow arrival time relative to the reference time in the uplink scenario. Burst Arrival Time 1 indicates time at which the first service flow arrives at the DS-TT, and Burst Arrival Time 1* indicates an offset of the time at which the first service flow arrives at the DS-TT relative to the reference time. UE-DS-TT Residence Time indicates residence time of the first service flow in the terminal device and in the DS-TT. PDB indicates the packet delay budget for transmitting the first service flow between the terminal device and the second device, and may be the foregoing PDB 1 or PDB 1′. For example, residence time of service flows in the terminal device and in the translator on the terminal device side may be the same or may be different.
In response to the first device being implemented by using different devices, manners in which the first device obtains the three parameters are also different. The following uses a manner 1 and a manner 2 as examples to describe a specific process in which the first device obtains the three parameters.
Manner 1: In response to the first device being a session management network element (for example, the SMF network element in
For the information about the time at which the first service flow arrives at the translator on the terminal device side, the session management network element may determine, based on information obtained from a policy control network element, the information about the time at which the first service flow arrives at the translator on the terminal device side.
For example, the information about the time at which the first service flow arrives at the translator on the terminal device side specifically refers to information about time at which a data packet of the first service flow in a specific cycle arrives at the translator on the terminal device side.
For example, the policy control network element sends, to the session management network element, parameters such as information about burst arrival time of the first service flow, a cycle of the first service flow, and a direction of the first service flow.
The information about the burst arrival time of the first service flow may be time at which the 1st data packet in a data burst of the first service flow arrives at an ingress port of a 5G system, duration from the reference time to the time at which the 1st data packet in the data burst of the first service flow arrives at the ingress port of the 5G system, or an offset of the time at which the 1st data packet in the data burst of the first service flow arrives at the ingress port of the 5G system relative to the reference time. The reference time is start time of a time domain (for example, 00:00:00 on Jan. 1, 1970). In response to the direction of the first service flow indicating that the first service flow is an uplink service flow, the ingress port of the 5G system herein refers to a port of the translator (for example, the DS-TT) on the terminal device side. In this case, the information about the burst arrival time of the first service flow is information about time at which the 1st data packet of the data burst of the first service flow arrives at the translator on the terminal device side.
In addition, the cycle of the first service flow may also be described as a time length of an interval between two adjacent points of burst start time of the first service flow.
In at least one embodiment, the policy control network element may obtain, from a TSN application function network element (for example, the TSN AF network element shown in
For example, for the network architecture shown in
For another example, for the network architecture shown in
For example, the policy control network element sends a policy control and charging (Policy Control and Charging, PCC) rule to the session management network element. The PCC rule includes the information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow. For example, the PCC rule includes a TSC assistance container (assistance container). The TSC assistance container carries the information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow.
In addition, the PCC rule may further include a service condition description parameter. The service condition description parameter is obtained by the policy control network element from the TSN application function network element or the time sensitive communication and time synchronization function network element. The service condition description parameter may include at least one of a maximum burst size (maximum burst Size), a priority of the first service flow, a latency condition of the first service flow, a maximum flow bit rate (maximum flow bit rate), and the like.
After receiving several parameters, to be specific, the information about the burst arrival time of the first service flow, the cycle of the first service flow, and the direction of the first service flow from the policy control network element, the session management network element may determine, based on these parameters, the information about the time at which the data packet of the first service flow in the specific cycle arrives at the translator on the terminal device side, namely, the information about the time at which the first service flow arrives at the translator on the terminal device side.
In other words, Burst Arrival Time 1 in the formula (1) or Burst Arrival Time 1* in the formula (2) may be determined in the foregoing manner.
For the residence time of the first service flow in the terminal device and in the translator on the terminal device side, the session management network element may obtain, from the terminal device, the residence time of the first service flow in the terminal device and in the translator on the terminal device side.
For example, in a protocol data unit (protocol data unit, PDU) session establishment process, the session management network element may receive a PDU session establishment request message from the terminal device, where the PDU session establishment request message carries the residence time of the first service flow in the terminal device and in the translator on the terminal device side. Optionally, the PDU session establishment request message may further carry a media access control address (media access control Address, MAC) address of a DS-TT port.
In other words, UE-DS-TT Residence Time in the formula (1) or the formula (2) may be determined in the foregoing manner.
For the packet delay budget for transmitting the first service flow between the terminal device and the second device, the session management network element may determine the packet delay budget for transmitting the first service flow between the terminal device and the second device.
For example, the session management network element may determine a PDB 1 or a PDB 1′ based on a 5G QoS identifier (5G QoS Identifier, 5QI) in the PCC rule. For example, the session management network element has configured a PDB 2 or a PDB 2′, and may further determine a PDB 3 based on the 5QI. Further, a difference between the PDB 3 and the PDB 2 may be calculated, to obtain the PDB 1. Alternatively, a difference between the PDB 3 and the PDB 2′ may be calculated, to obtain the PDB 1′. For details, refer to the foregoing related content.
In other words, the PDB 1 and the PDB 1′ may be determined in the foregoing manner. An example in which the PDB is the PDB 1 is only used below for description.
Manner 2: In response to the first device being a TSN application function network element (for example, the TSN AF network element shown in
For the information about the time at which the first service flow arrives at the translator on the terminal device side, the first device may determine the information about the time at which the first service flow arrives at the translator on the terminal device side.
For example, the information about the time at which the first service flow arrives at the translator on the terminal device side specifically refers to information about time at which a data packet of the first service flow in a specific cycle arrives at the translator on the terminal device side.
For example, in response to the first device being the TSN application function network element, the TSN application function network element is further used as a control plane of a 5GS switching node, and determines, based on information obtained from the CNC network element, parameters such as information about burst arrival time of the first service flow, a cycle of the first service flow, and a direction of the first service flow. For another example, in response to the first device being the time sensitive communication and time synchronization function network element, the time sensitive communication and time synchronization function network element is further used as a control plane of a 5GS switching node, and determines, based on information obtained from an application function network element, parameters such as information about burst arrival time of the first service flow, a cycle of the first service flow, and a direction of the first service flow.
The information about the burst arrival time of the first service flow may be time at which the 1st data packet in a data burst of the first service flow arrives at an ingress port of a 5G system, duration from the reference time to the time at which the 1st data packet in the data burst of the first service flow arrives at the ingress port of the 5G system, or an offset of the time at which the 1st data packet in the data burst of the first service flow arrives at the ingress port of the 5G system relative to the reference time. The reference time is start time of a time domain (for example, 00:00:00 on Jan. 1, 1970). In response to the direction of the first service flow indicating that the first service flow is an uplink service flow, the ingress port of the 5G system herein refers to a port of the translator (for example, the DS-TT) on the terminal device side. In this case, the information about the burst arrival time of the first service flow is information about time at which the 1st data packet of the data burst of the first service flow arrives at the translator on the terminal device side.
For the residence time of the first service flow in the terminal device and in the translator on the terminal device side and the packet delay budget for transmitting the first service flow between the terminal device and the second device, with reference to the manner 1, a session management network element may obtain the residence time of the first service flow in the terminal device and in the translator on the terminal device side from the terminal device, and the session management network element may further determine the packet delay budget (namely, a PDB 1 or a PDB 1′) for transmitting the first service flow between the terminal device and the second device. For example, the first device may directly receive the foregoing information from the session management network element, or receive the foregoing information from the session management network element through another network element (for example, a policy control network element). Alternatively, the session management network element stores the foregoing information in a data repository network element (for example, a UDR network element) through a data management network element (for example, a UDM network element), and the first device may obtain the foregoing information from the data repository network element.
Scenario 2: In response to the first service flow being a downlink service flow, the second device is the user plane network element. In other words, the first service flow is a downlink service flow to be sent by the user plane network element to the access network device.
In this case, a forwarding path of the first service flow in the mobile communication system is: the user plane network element, the access network device, and a terminal device. Optionally, at least one switch or router may be further included between the user plane network element and the access network device.
For example, as shown in
In an implementation, the information about the service flow arrival time is information about time at which the first service flow arrives at the user plane network element, or may be understood as information about time at which the first service flow arrives at an NW-TT. The NW-TT is located inside the user plane network element, and the time at which the first service flow arrives at the NW-TT is equal to the time at which the first service flow arrives at the user plane network element. The information about the service flow arrival time may include the time at which the first service flow arrives at the user plane network element, or an offset of the time at which the first service flow arrives at the user plane network element relative to the reference time. An example is provided below:
T1 (downlink) indicates service flow arrival time in a downlink scenario, and T1-offset (downlink) indicates an offset of the service flow arrival time relative to the reference time in the downlink scenario. Burst Arrival Time 2 indicates the time at which the first service flow arrives at the NW-TT, and Burst Arrival Time 2* indicates an offset of the time at which the first service flow arrives at the NW-TT relative to the reference time.
Similarly, in response to the first device being implemented by using different devices, manners in which the first device obtains the information about the service flow arrival time are also different. The following uses a manner 3 and a manner 4 as examples to describe a specific process in which the first device obtains the information about the service flow arrival time.
Manner 3: In response to the first device being a session management network element (for example, the SMF network element in
The manner 3 is similar to the manner 1 in which the session management network element may obtain, from the policy control network element, the information about the time at which the first service flow arrives at the translator on the terminal device side. A difference lies in: Because information about burst arrival time of the first service flow may be time at which the 1st data packet in a data burst of the first service flow arrives at an ingress port of a 5G system, duration from the reference time to the time at which the 1st data packet in the data burst of the first service flow arrives at the ingress port of the 5G system, or an offset of the time at which the 1st data packet in the data burst of the first service flow arrives at the ingress port of the 5G system relative to the reference time, in response to a direction of the first service flow indicating that the first service flow is a downlink service flow, the ingress port of the 5G system herein refers to a port of the NW-TT. In this case, the information about the burst arrival time of the first service flow is information about time at which the 1st data packet of the data burst of the first service flow arrives at the NW-TT.
Manner 4: In response to the first device being a TSN application function network element or a time sensitive communication and time synchronization function network element, the first device may determine the information about the service flow arrival time.
The manner 4 is similar to the manner 2 in which the first device may determine the information about the time at which the first service flow arrives at the translator on the terminal device side. A difference lies in: Because information about burst arrival time of the first service flow may be time at which the 1st data packet in a data burst of the first service flow arrives at an ingress port of a 5G system, duration from the reference time to the time at which the 1st data packet in the data burst of the first service flow arrives at the ingress port of the 5G system, or an offset of the time at which the 1st data packet in the data burst of the first service flow arrives at the ingress port of the 5G system relative to the reference time, in response to a direction of the first service flow indicating that the first service flow is a downlink service flow, the ingress port of the 5G system herein refers to a port of the NW-TT. In this case, the information about the burst arrival time of the first service flow is information about time at which the 1st data packet of the data burst of the first service flow arrives at the NW-TT.
Step 810: The first device determines information about service flow sending time based on the information about the service flow arrival time.
In a first implementation, the first device determines earliest sending time and latest sending time based on the information about the service flow arrival time. The earliest sending time may be understood as earliest time at which the second device sends the first service flow, and the latest sending time may be understood as latest time at which the second device sends the first service flow. The service flow sending time is not earlier than the earliest sending time, and the service flow sending time is not later than the latest sending time. The first device may determine, as the service flow sending time, time that is not earlier than the earliest sending time and not later than the latest sending time. The service flow sending time may be understood as time recommended for the second device to send the service flow.
The earliest sending time is a sum of the service flow arrival time and processing time of the first service flow in the second device.
For example, in a scenario in which a jitter is not considered:
T2 indicates the earliest sending time. T1 indicates the service flow arrival time, and may be T1 (uplink) obtained according to the formula (1) or T1 (downlink) obtained according to the formula (3).
For example, in response to the first service flow being an uplink service flow:
TAN is processing time of the first service flow in the access network device or the AN-TT.
In addition, the first device may further skip a process of calculating T1 (uplink), and directly calculate T2 (uplink):
For example, in response to the first service flow being a downlink service flow:
TUPF is processing time of the first service flow in the user plane network element.
In addition, the first device may further skip a process of calculating T1 (downlink), and directly calculate T2 (downlink):
In a scenario in which a jitter is considered:
For example, in response to the first service flow being an uplink service flow:
For example, in response to the first service flow being a downlink service flow:
In addition, in the scenario in which the jitter is considered, the first device may further skip a process of calculating T1, and directly calculate T2. Details are not described herein again.
Jitter (Jitter) indicates a jitter latency associated with the first service flow, is a sending latency caused by existence of a service flow having a same priority as the first service flow, and may be determined based on a size of a maximum frame of the service flow having the same priority as the first service flow.
For example, for a flow, in response to no flow having a same priority as the flow exists, a jitter value of the flow is 0. For a flow, in response to a flow having a same priority as the flow exists, a jitter value of the flow is affected by [MaxFrameSize] of all other flows having the same priority. [MaxFrameSize] refers to time used for sending a maximum data packet of the service flow, or longest time for sending a frame of the service flow.
For example, a flow J and a flow K have a same priority. Based on [MaxFrameSize] of the flow J, the longest time for sending a frame of the flow J is 120 μs, and based on [MaxFrameSize] of the flow K, the longest time for sending a frame of the flow K is 80 μs. A jitter of the flow K depends on the longest time for sending a frame of flow J. For example, the jitter of the flow K is determined based on half of the longest time for sending a frame of the flow J, that is, 60 μs. Because the flow J and the flow K have the same priority, the flow J and the flow K enter a same send queue. In response to the flow J and the flow K simultaneously waiting to be sent in the same send queue, in response to the flow J being sent first, the flow K is to wait for maximum duration, where the maximum duration is the longest time for sending a frame of the flow J; in response to the flow K being sent first, the flow K is to wait for minimum duration, where the minimum duration is 0. Therefore, herein, the jitter of the flow K is defined, based on a probability, as half of the longest time (120 μs) for sending a frame of the flow J, that is, 60 μs. Similarly, a jitter of the flow J is 40 μs.
For another example, a flow J, a flow K, and a flow G have a same priority. Based on [MaxFrameSize] of the flow J, the longest time for sending a frame of the flow J is 120 μs, based on [MaxFrameSize] of the flow K, the longest time for sending a frame of the flow K is 80 μs, and based on [MaxFrameSize] of the flow G, the longest time for sending a frame of the flow G is 100 μs. Similarly, a jitter of the flow J depends on the longest time for sending a frame of the flow K and the longest time for sending a frame of the flow G. For example, the jitter of the flow J is determined based on a sum of half of the longest time for sending a frame of the flow K and half of the longest time for sending a frame of the flow K, that is, the jitter of the flow J is 90 μs. Similarly, a jitter of the flow K is 110 μs, and a jitter of the flow G is 100 μs.
In addition, the processing time of the first service flow in the second device in the foregoing formula may be understood as time used by the second device to decapsulate a data packet of the first service flow, process the data packet of the first service flow, encapsulate the data packet of the first service flow, and send the encapsulated data packet to an egress port of the second device after the data packet of the first service flow arrives at the second device. The egress port is an egress port used by the second device to send the first service flow. In other words, the processing time of the first service flow in the second device may be understood as duration from time at which the second device receives the data packet of the first service flow to time at which the data packet arrives at the egress port of the second device and is ready for sending. For example, the second device receives the data packet of the first service flow from an upstream node at a moment t1, and the data packet arrives at the egress port of the second device at a moment t2 after being processed by the second device, and waits to be sent to a next device. In this case, t2−t1 is the processing time of the first service flow in the second device. The moment t1 corresponds to the service flow arrival time, and the moment t2 corresponds to the earliest sending time in response to the jitter not being considered.
In an implementation, in response to the second device being the user plane network element, t1 is time at which the data packet of the first service flow arrives at an ingress port of the NW-TT corresponding to the user plane network element, and t2 is time at which the data packet of the first service flow arrives at an egress port of the user plane network element or the NW-TT. For example, in response to a forwarding path from the second device to the access network device not including an I-UPF, t2 is time at which the data packet of the first service flow arrives at an egress port of an N3-TT. The egress port herein is an egress port used for sending to the access network device or the AN-TT. For example, in response to a forwarding path from the second device to the access network device including an I-UPF, t2 is time at which the data packet of the first service flow arrives at an egress port of an N9-TT. The egress port herein is an egress port used for sending to the I-UPF.
In another implementation, in response to the second device being the access network device, t1 is time at which the data packet of the first service flow arrives at the access network device after being transmitted over an air interface, for example, may be time at which the data packet of the first service flow arrives at the PDCP layer or the SDAP layer of the access network device, and t2 is time at which the data packet of the first service flow arrives at an egress port after being processed by the access network device.
In still another implementation, in response to the second device being the translator corresponding to the access network device, t1 is time at which the data packet of the first service flow arrives at the AN-TT outside the access network device after being transmitted over an air interface, and t2 is time at which the data packet of the first service flow arrives at an egress port after being processed by the AN-TT.
For example, the first device may obtain processing time information of the second device from the second device, and determine, based on the processing time information of the second device, the processing time of the first service flow in the second device.
The processing time information of the second device may include a 5QI and processing time of a service flow corresponding to the 5QI in the second device. Further, the first device may determine, based on a 5QI of the first service flow and the processing time information of the second device, the processing time of the first service flow in the second device.
Alternatively, the processing time information of the second device includes a data packet size range and processing time of a service flow that meets the data packet size range in the second device. Further, the first device may determine, based on a size of the data packet of the first service flow, a data packet size range within which the data packet of the first service flow falls, and determine, based on the processing time information of the second device, the processing time of the first service flow in the second device.
Alternatively, the processing time information of the second device includes processing time of a service flow in the second device, in other words, processing time of all service flows in the second device is of a same time length. Further, the second device determines the processing time of the service flow in the second device in the processing time information of the second device as the processing time of the first service flow in the second device.
With reference to the scenario 1 and the scenario 2, the following uses examples to describe an implementation in which the first device obtains the processing time information of the second device from the second device.
In correspondence to the scenario 1, in response to the translator corresponding to the access network device being used as a functional module inside the access network device, the first device may obtain the processing time information of the second device from the access network device. In this case, the processing time information of the second device is also referred to as processing time information of the access network device.
In response to the translator corresponding to the access network device being a device that is independently deployed outside the access network device, the translator corresponding to the access network device may send the processing time information of the second device to the access network device, and the first device may obtain the processing time information of the second device from the access network device; or the processing time information of the second device is configured on the access network device; or the first device may obtain the processing time information of the second device from the translator corresponding to the access network device. In this case, the processing time information of the second device is also referred to as processing time information of the translator corresponding to the access network device.
For example, in response to the first device being the session management network element, the access network device may send a setup request (NG Setup Request) message to an access and mobility management function network element in response to establishing a connection to the access and mobility management function network element, where the NG setup request message carries the processing time information of the second device. Alternatively, the access network device may send a configuration update (RAN Configuration Update) message to an access and mobility management function network element, where the RAN configuration update message carries the processing time information of the second device. Alternatively, in a registration process of a terminal device (for example, the 1st terminal device), the access network device may send the processing time information of the second device to an access and mobility management function network element. Further, the access and mobility management function network element sends the processing time information of the second device to the session management network element in a PDU session establishment process. Alternatively, the processing time information of the second device may be configured on the session management network element. Alternatively, in a session establishment process of a terminal device (for example, a session establishment request carries specific single network slice selection assistance information (single network slice selection assistance information, S-NSSAI) and a data network name (data network name, DNN)), the access network device may send the processing time information of the second device to the session management network element through an access and mobility management network element.
In correspondence to the scenario 2, the first device may obtain processing time information of the user plane network element from the user plane network element. For example, in response to the first device being the session management network element, the session management network element sends a request message to the user plane network element, where the request message is used to request the processing time information of the user plane network element. For example, the request message may be an N4 session establishment message or an N4 session modification request message. The user plane network element may send a response message for the request message to the first device, where the response message for the request message carries the processing time information of the user plane network element. For example, in response to the request message being the N4 session establishment message, the response message for the request message is a response message for the N4 session establishment message. In response to the request message being the N4 session modification request message, the response message for the request message is a response message for the N4 session modification message. Alternatively, the user plane network element may directly report the processing time information of the user plane network element to the session management network element, and the session management network element does not request, from the user plane network element, the processing time of the first service flow in the user plane network element. Alternatively, the processing time information of the user plane network element may be configured on the session management network element.
In addition, in response to the first device being a device other than the session management network element, the session management network element may send the processing time of the first service flow in the second device and the processing time information of the second device to the first device, and the first device may directly receive the foregoing information from the session management network element, or receive the foregoing information from the session management network element through another network element (for example, the policy control network element). Alternatively, the session management network element stores the foregoing information in the data repository network element (for example, the UDR network element) through the data management network element (for example, the UDM network element), and the first device may obtain the foregoing information from the data repository network element. Alternatively, the processing time information of the second device may be configured on the first device.
In the foregoing manner, the earliest sending time may be determined. In addition, the service flow sending time is not later than the latest sending time. The latest sending time may be determined in, but not limited to, the following manner A, manner B, or manner C:
Manner A: Because the first service flow is a periodic service flow, a data packet of the first service flow that currently arrives at the second device is to be sent before a data packet of the first service flow in a next cycle arrives at the second device, in other words, the second device is to send the data packet of the first service flow within duration corresponding to a cycle of the first service flow after the service flow arrival time. Therefore, latest time (namely, the latest sending time) at which the second device sends the data packet of the first service flow is to be earlier than a sum of the service flow arrival time and the cycle of the first service flow. Further, to implement that before the data packet of the first service flow in the next cycle arrives at the second device, the data packet of the first service flow that currently arrives at the second device has been sent instead of being sent, based on the foregoing discussion, the latest time (namely, the latest sending time) at which the second device sends the first service flow may be equal to a difference between the sum of the service flow arrival time and the cycle of the first service flow and duration corresponding to sending of a maximum data packet of the first service flow.
For example, the latest sending time is determined based on the service flow arrival time, the cycle of the first service flow, and a size of a maximum frame of the first service flow.
In the scenario in which the jitter is not considered:
T3A indicates latest sending time determined in the manner A. T1 indicates the service flow arrival time, and may be T1 (uplink) obtained according to the formula (1) or T1 (downlink) obtained according to the formula (3). Interval indicates the cycle of the first service flow, and [MaxFrameSize] indicates duration corresponding to sending of a data packet with a size of MaxFrameSize through the egress port of the second device, that is, the duration corresponding to sending of the maximum data packet of the first service flow.
For the cycle of the first service flow, refer to related content in the manner 1 to the manner 4. MaxFrameSize may be determined based on information obtained from the service condition description parameter, and MaxFrameSize is a difference between the maximum burst size in the service condition description parameter and a size of a media framing field. The media framing field may include at least one of a preamble, an IEEE 802.3 header, a priority or a virtual local area network identifier (VLAN Identifier, VID), a cyclic redundancy check (cyclic redundancy check, CRC), an interframe gap, and the like.
In addition, the first device may further skip a process of calculating T1 (uplink), and directly calculate T3A (uplink):
Similarly, the first device may further skip a process of calculating T1 (downlink), and directly calculate T3A (downlink):
Optionally, in the scenario in which the jitter is considered:
In the scenario in which the jitter is considered, the second device sends the data packet of the first service flow earlier than T1+Interval-[MaxFrameSize]-Jitter, so that in response to the data packet of the first service flow in the next cycle arriving at the second device, the data packet of the first service flow in a current cycle has been sent by the second device instead of being sent. Therefore, Jitter is subtracted herein.
Similarly, the first device may also skip a process of calculating T1. Details are not described herein again.
Manner B: After the first service flow arrives at the second device, the second device is to process the first service flow, which is limited by maximum buffer duration of the first service flow in the second device. Therefore, latest time (namely, the latest sending time) at which the second device sends the first service flow may be equal to a sum of the service flow arrival time, the processing time of the first service flow in the second device, and the maximum buffer duration of the first service flow in the second device.
For example, the latest sending time is determined based on the service flow arrival time, the processing time of the first service flow in the second device, and the maximum buffer duration of the first service flow in the second device. The maximum buffer duration of the first service flow in the second device is maximum duration in which the first service flow can be buffered in the second device.
In the scenario in which the jitter is not considered:
T3B indicates latest sending time determined in the manner B. T1 indicates the service flow arrival time, and may be T1 (uplink) obtained according to the formula (1) or T1 (downlink) obtained according to the formula (3). T′ indicates the processing time of the first service flow in the second device. T* indicates the maximum buffer duration of the first service flow in the second device.
In addition, the first device may further skip a process of calculating T1 (uplink), and directly calculate T3B (uplink):
The first device may further skip a process of calculating T1 (downlink), and directly calculate T3B (downlink):
In the scenario in which the jitter is considered:
In the scenario in which the jitter is considered, the second device is to send the data packet of the first service flow earlier than T1+T′+T*-Jitter, so that buffer time of the data packet of the first service flow in the second device does not exceed the maximum buffer duration.
Similarly, the first device may also skip a process of calculating T1. Details are not described herein again.
For the processing time T′ of the first service flow in the second device that is to be used to calculate the latest sending time in the manner B, refer to the descriptions of how to determine the processing time of the first service flow in the second device in determining the earliest sending time. Details are not described herein again.
In at least one embodiment, the maximum buffer duration T* of the first service flow in the second device that is to be used to calculate the latest sending time in the manner B is related to a buffer capability of the second device, or the maximum buffer duration of the first service flow in the second device is related to the 5QI corresponding to the first service flow, or the maximum buffer duration of the first service flow in the second device is related to the data packet size range. For example, the first device obtains maximum buffer duration information of the second device, and determines, based on the maximum buffer duration information of the second device, the maximum duration in which the first service flow can be buffered in the second device. For example, in response to the first device being the session management network element, the maximum buffer duration information includes at least one 5QI and maximum duration in which a service flow corresponding to each 5QI can be buffered in the second device. The session management network element may further determine the maximum buffer duration of the first service flow in the second device with reference to the 5QI of the first service flow. Alternatively, the maximum buffer duration information includes a data packet size range and maximum buffer duration of a service flow that meets the data packet size range in the second device. The session management network element may further determine the maximum buffer duration of the first service flow in the second device with reference to the size of the data packet of the first service flow. Alternatively, the maximum buffer duration information includes maximum buffer duration of a service flow in the second device, in other words, maximum buffer duration of all service flows in the second device is the same. An implementation in which the session management network element obtains the maximum buffer duration information of the second device may be the same as the implementation in which the first device obtains the processing time information of the second device from the second device. For details, refer to the descriptions in step 810. Details are not described herein again.
In at least one embodiment, the first device determines the maximum buffer duration of the first service flow in the second device based on the processing time information of the second device, processing time information of the third device, a packet delay budget for transmitting the first service flow between the second device and the third device, and a maximum transmission latency of the first service flow between the second device and the third device. The maximum buffer duration T* of the first service flow in the second device=the packet delay budget for transmitting the first service flow between the second device and the third device-processing time of the first service flow in the third device—the processing time of the first service flow in the second device-maximum transmission latency of the first service flow between the second device and the third device.
For example, in response to the first device being the session management network element, the session management network element may determine, based on the 5QI corresponding to the first service flow, the packet delay budget for transmitting the first service flow between the second device and the third device, and determine the processing time of the first service flow in the second device based on the processing time information of the second device. The session management network element may further determine the maximum transmission latency of the first service flow between the second device and the third device, and further calculate the maximum buffer duration of the first service flow in the second device based on the foregoing parameters.
For example, for the packet delay budget for transmitting the first service flow between the second device and the third device, refer to related descriptions of the PDB 2 (or the PDB 2′) and the PDB 4 (or the PDB 4′) in the scenario 1 and the scenario 2. For example, the first service flow is an uplink service flow. In response to a latency condition for transmitting the first service flow between the terminal device and the user plane network element being 2 ms, the session management network element may determine that a packet delay budget (the PDB 3) for transmission between the terminal device and the user plane network element is 2 ms, and the packet delay budget (the PDB 2) for transmission between the second device and the third device is 1 ms.
For the processing time of the first service flow in the second device, refer to the foregoing related descriptions.
The maximum transmission latency of the first service flow between the second device and the third device depends on a capability of each transmission node between the second device and the third device, and indicates a latency used for transmitting the first service flow between the second device and the third device. The maximum transmission latency of the first service flow between the second device and the third device is duration from time at which the second device (the access network device or the AN-TT) sends the data packet of the first service flow to time at which the third device (the user plane network element, the N3-TT, or the N9-TT) receives the data packet of the first service flow in response to the second device, the third device, and another transmission node between the second device and the third device forwarding the data packet of the first service flow based on a gate control scheduling parameter under control of a CNC-TN.
The maximum transmission latency of the first service flow between the second device and the third device may be preconfigured on the session management network element. For example, maximum transmission latencies between different access network devices (or translators corresponding to the access network devices) and different user plane network elements may be configured on the session management network element. Alternatively, the maximum transmission latencies may be configured based on different 5QIs. To be specific, for a specific access network device (or a translator corresponding to the access network device) and a specific user plane network element, corresponding maximum transmission latencies are separately preconfigured for different 5QIs, or a uniform value of a maximum transmission latency may be configured, in other words, 5QIs separately corresponding to different services are not distinguished.
The processing time of the first service flow in the third device may be understood as time used by the third device to decapsulate and process the data packet of the first service flow, encapsulate the first service flow, and send the encapsulated first service flow to an egress port of the third device after the data packet of the first service flow arrives at the third device. The egress port is an egress port used by the third device to send the first service flow to a next-hop device. In other words, the processing time of the first service flow in the third device may be understood as duration from the time at which the third device receives the data packet of the first service flow to time at which the data packet arrives at the egress port of the third device and is ready for sending. For example, the third device receives the data packet of the first service flow from an upstream node at a moment t3, and the data packet arrives at the egress port of the third device at a moment t4 after being processed by the third device, and waits to be sent to the next-hop device. In this case, t4−t3 is the processing time of the first service flow in the third device.
In an implementation, in response to the third device being the user plane network element, t3 is time at which the data packet of the first service flow arrives at an ingress port of the N3-TT or the N9-TT corresponding to the user plane network element, and t4 is time at which the data packet of the first service flow arrives at an egress port of the user plane network element or the NW-TT of the user plane network element. For example, in response to a forwarding path determined from the second device to the third device not including an I-UPF, t3 is time at which the data packet of the first service flow arrives at an ingress port of the N3-TT. For example, in response to a forwarding path determined from the second device to the third device including an I-UPF, t3 is time at which the data packet of the first service flow arrives at an ingress port of the N9-TT.
In another implementation, in response to the third device being the access network device, t3 is time at which the data packet of the first service flow arrives at the access network device after being transmitted over an N3 link, for example, may be time at which the data packet of the first service flow arrives at an ingress port of the access network device, and t4 is time at which the data packet of the first service flow arrives at the PDCP layer or the SDAP layer after being processed by the access network device.
In still another implementation, in response to the third device being the translator corresponding to the access network device, t3 is time at which the data packet of the first service flow arrives at an ingress port of the AN-TT outside the access network device after being transmitted over an N3 link, and t4 is time at which the data packet of the first service flow is processed by the AN-TT.
For example, the first device may obtain the processing time information of the third device from the third device, and determine, based on the processing time information of the third device, the processing time of the first service flow in the third device.
The processing time information of the third device may include a 5QI and processing time of a service flow corresponding to the 5QI in the third device. Further, the first device may determine, based on the 5QI of the first service flow and the processing time information of the third device, the processing time of the first service flow in the third device.
Alternatively, the processing time information of the third device includes a data packet size range and processing time of a service flow that meets the data packet size range in the third device. Further, the first device may determine, based on the size of the data packet of the first service flow, a data packet size range within which the data packet of the first service flow falls, and determine, based on the processing time information of the third device, the processing time of the first service flow in the third device.
Alternatively, the processing time information of the third device includes processing time of a service flow in the third device, in other words, processing time of all service flows in the third device is of a same time length, so that the third device determines the processing time of the service flow in the third device in the processing time information of the third device as the processing time of the first service flow in the third device.
In addition, in response to the first device being a device other than the session management network element, the session management network element may send the processing time of the first service flow in the third device or the processing time information of the third device to the first device.
With reference to the scenario 1 and the scenario 2, the following uses examples to describe an implementation in which the first device obtains the processing time information of the third device from the third device.
In correspondence to the scenario 1, the first device may obtain processing time information of the user plane network element from the user plane network element. For details, refer to the foregoing related content. Repeated parts are not described.
In correspondence to the scenario 2, the first device may obtain processing time information of the access network device or processing time information of the translator corresponding to the access network device. For details, refer to the foregoing related content. Repeated parts are not described.
In addition, in response to the first device being a device other than the session management network element, the session management network element may send the processing time of the first service flow in the third device and the processing time information of the third device to the first device, and the first device may directly receive the foregoing information from the session management network element, or receive the foregoing information from the session management network element through another network element (for example, the policy control network element). Alternatively, the session management network element stores the foregoing information in the data repository network element (for example, the UDR network element) through the data management network element (for example, the UDM network element), and the first device may obtain the foregoing information from the data repository network element. Alternatively, the processing time information of the third device may be configured on the first device.
In addition, in response to the first device being a device other than the session management network element, the session management network element may send the maximum buffer duration information of the second device or the maximum buffer duration of the first service flow in the second device to the first device, or the maximum buffer duration information of the second device may be configured on the first device.
In the foregoing manner, the first device may determine the maximum buffer duration of the first service flow in the second device, and then determine the latest sending time according to the formula (9-1), formula (9-2), formula (9-3), or formula (10-1).
In addition, the maximum buffer duration T* of the first service flow in the second device may not be first determined, and the latest sending time is directly determined in the foregoing manner of determining the maximum buffer duration T* of the first service flow in the second device with reference to the formula (9-1), formula (9-2), formula (9-3), or formula (10-1).
For example, in the scenario in which the jitter is not considered, with reference to the formula (9-1):
In the scenario in which the jitter is considered, with reference to the formula (10-1):
Manner C: Based on the manner A and the manner B, a smaller value of the latest sending time determined in the manner A and the latest sending time determined in the manner B is selected as the latest sending time. For example, a smaller value of T3A and T3B is selected.
The foregoing three manners of determining the latest sending time are merely examples.
Therefore, the first device may determine the earliest sending time and the latest sending time with reference to the foregoing manners, and then the first device may determine, as the service flow sending time, time that is not earlier than the earliest sending time and not later than the latest sending time. Alternatively, the first device may further determine, based on the determined service flow sending time, an offset of the service flow sending time relative to the reference time, and uses the offset as the information of the service flow sending time.
In a second implementation, the first device may directly determine an offset of the service flow sending time relative to the reference time.
For the second implementation, the first device may determine a minimum offset and a maximum offset based on the information about the service flow arrival time. The minimum offset is a minimum offset of time at which the second device sends the first service flow relative to the reference time, and is equal to an offset of the earliest sending time in the first implementation relative to the reference time. The maximum offset is a maximum offset of the time at which the second device sends the first service flow relative to the reference time, and is equal to an offset of the latest sending time in the first implementation relative to the reference time. Further, the first device may obtain an offset selection value, where the offset selection value is greater than or equal to the minimum offset and is less than or equal to the maximum offset. Further, the first device determines the information about the service flow sending time based on the offset selection value. The offset selection value may be used as the offset of the service flow sending time relative to the reference time, or a difference between the offset selection value and a jitter latency associated with the first service flow may be used as the offset of the service flow sending time relative to the reference time.
For example, the minimum offset may be an earliest transmission offset (EarliestTransmitOffset) in TSpecTimeAware, and the earliest transmission offset is used to define an earliest time offset, relative to the reference time, of time at which the second device can start to send a data packet in the cycle (Interval) of the first service flow.
For the minimum offset, the first device may determine the minimum offset based on the information about the service flow arrival time and processing time of the first service flow in the second device. For example, the minimum offset is a sum of the offset of the service flow arrival time relative to the reference time and the processing time of the first service flow in the second device, or the minimum offset is a sum of the offset of the service flow arrival time relative to the reference time, the processing time of the first service flow in the second device, and the jitter latency associated with the first service flow.
For example, in a scenario in which a jitter is not considered:
T1-offset indicates the offset of the service flow arrival time relative to the reference time, and may be T1-offset (uplink) obtained according to the formula (2) or T1-offset (downlink) obtained according to the formula (4).
For example, in response to the first service flow being an uplink service flow:
In addition, the first device may further skip a process of calculating T1-offset (uplink), and directly calculate EarliestTransmitOffset (uplink):
For example, in response to the first service flow being a downlink service flow:
In addition, the first device may further skip a process of calculating T1-offset (downlink), and directly calculate EarliestTransmitOffset (downlink):
In a scenario in which a jitter is considered:
For example, in response to the first service flow being an uplink service flow:
For example, in response to the first service flow being a downlink service flow:
Similarly, the first device may also skip a process of calculating T1-offset. Details are not described herein again.
For a specific manner in which the first device determines the processing time of the first service flow in the second device, refer to the foregoing related descriptions. Details are not described again.
For example, the maximum offset may be a latest transmission offset (LatestTransmitOffset) in TSpecTimeAware, and the latest transmission offset is used to define a latest time offset, relative to the reference time, of time at which the second device can start to send a frame in the cycle (Interval) of the first service flow.
For the maximum offset, the maximum offset corresponds to the latest sending time. Therefore, for a manner in which the first device determines the maximum offset, refer to the foregoing manner of determining the latest sending time.
Manner A*: In the scenario in which the jitter is not considered:
In addition, the first device may further skip a process of calculating T1-offset (uplink), and directly calculate LatestTransmitOffset (uplink):
The first device may further skip a process of calculating T1-offset (downlink), and directly calculate LatestTransmitOffset (downlink):
In the scenario in which the jitter is considered: LatestTransmitOffset=T1−offset+Interval−[MaxFrameSize]−Jitter Formula (14)
Similarly, the first device may also skip a process of calculating T1-offset. Details are not described herein again.
For the manner A*, refer to related descriptions of the manner A corresponding to the latest sending time in the first implementation.
Manner B*: In the scenario in which the jitter is not considered:
In addition, the first device may further skip a process of calculating T1-offset (uplink), and directly calculate LatestTransmitOffset (uplink):
The first device may further skip a process of calculating T1-offset (downlink), and directly calculate LatestTransmitOffset (downlink):
In the scenario in which the jitter is considered: LatestTransmitOffset=T1−offset+T′+T*−Jitter Formula (16)
Similarly, the first device may also skip a process of calculating T1-offset. Details are not described herein again.
For the manner B*, refer to related descriptions of the manner B corresponding to the latest sending time in the first implementation.
Manner C*: Based on the manner A* and the manner B*, a smaller value of the maximum offset determined in the manner A* and the maximum offset determined in the manner B* is selected as the maximum offset.
For the manner C*, refer to related descriptions of the manner C corresponding to the latest sending time in the first implementation.
For example, after the minimum offset and the maximum offset are determined in the foregoing manners, the first device may obtain the offset selection value in, but not limited to, the following manner.
In at least one embodiment, the first device sends the minimum offset and the maximum offset to a fourth device. The fourth device may determine the offset selection value based on the minimum offset and the maximum offset, and send the offset selection value to the first device.
In addition, the foregoing method is also applicable to the first implementation. For example, the first device sends the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time to the fourth device. The fourth device may determine the offset selection value based on the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time, and send the offset selection value to the first device. The offset selection value of the first service flow is greater than or equal to the minimum offset of the first service flow, and is less than or equal to the maximum offset of the first service flow.
The offset of the earliest sending time relative to the reference time is equal to the minimum offset, and the offset of the latest sending time relative to the reference time is equal to the maximum offset. The following only uses the maximum offset and the minimum offset as an example for description.
In at least one embodiment, in addition to the minimum offset and the maximum offset of the first service flow, the fourth device may further obtain a minimum offset and a maximum offset of a second service flow. The second service flow and the first service flow arrive at the second device at the same time, or a difference between time at which the second service flow arrives at the second device and time at which the first service flow arrives at the second device is less than or equal to a threshold.
The fourth device may determine the offset selection value of the first service flow and an offset selection value of the second service flow based on the minimum offset and the maximum offset of the first service flow and the minimum offset and the maximum offset of the second service flow.
The offset selection value of the first service flow is greater than or equal to the minimum offset of the first service flow and is less than or equal to the maximum offset of the first service flow, and the offset selection value of the second service flow is greater than or equal to the minimum offset of the second service flow and is less than or equal to the maximum offset of the second service flow, so that a deterministic latency condition of the first service flow and a deterministic latency condition of the second service flow can be ensured. In addition, a difference between the offset selection value of the first service flow and the offset selection value of the second service flow is greater than or equal to duration corresponding to a data packet of MaxFrameSize of the first service flow (when the fourth device determines that the offset selection value of the first service flow is less than the offset selection value of the second service flow) or duration corresponding to a data packet of MaxFrameSize of the second service flow (when the fourth device determines that the offset selection value of the first service flow is greater than the offset selection value of the second service flow), to avoid congestion between the first service flow and the second service flow.
Optionally, the first device may further send the priority of the first service flow to the fourth device. The fourth device may determine the offset selection value based on the obtained maximum offset and minimum offset of the first service flow and the priority of the first service flow. For example, for a service flow with a high priority, a small offset selection value is set. A smaller offset selection value indicates shorter time for caching a data packet of a service flow in the second device, and a larger offset selection value indicates longer time for caching a data packet of a service flow in the second device. A small offset selection value is set for a service flow with a high priority, to ensure that a data packet of the service flow is preferentially sent, and therefore ensure a low transmission latency of the service flow.
Optionally, the first device may further send a priority of the second service flow to the fourth device, and the fourth device may comprehensively consider priorities of service flows to determine an offset selection value for each service flow.
Optionally, the first device further sends, to the fourth device, a maximum latency condition for transmitting the first service flow between the second device and the third device. The fourth device may determine the offset selection value with reference to the maximum latency condition for transmitting the first service flow between the second device and the third device, the minimum offset, and the maximum offset, and send the offset selection value to the first device. The maximum latency condition for transmitting the first service flow between the second device and the third device is a maximum allowable value of duration from time at which the second device sends the first service flow to time at which the third device receives the first service flow or duration from time at which the third device sends the first service flow to time at which the second device receives the first service flow.
For example, the first device may determine, based on the packet delay budget for transmitting the first service flow between the second device and the third device and the processing time of the first service flow in the second device, the maximum latency condition for transmitting the first service flow between the second device and the third device. For the packet delay budget for transmitting the first service flow between the second device and the third device and the processing time of the first service flow in the second device, refer to the foregoing descriptions. Details are not described herein again. For example, the maximum latency condition for transmitting the first service flow between the second device and the third device=the packet delay budget for transmitting the first service flow between the second device and the third device—the processing time of the first service flow in the second device.
For another example, the first device may determine, based on the packet delay budget for transmitting the first service flow between the second device and the third device, the processing time of the first service flow in the second device, and the processing time of the first service flow in the third device, the maximum latency condition for transmitting the first service flow between the second device and the third device. For the processing time of the first service flow in the third device, refer to the foregoing descriptions. Details are not described herein again. For example, the maximum latency condition for transmitting the first service flow between the second device and the third device=the packet delay budget for transmitting the first service flow between the second device and the third device—the processing time of the first service flow in the second device—the processing time of the first service flow in the third device.
A smaller value of the maximum latency condition indicates a higher latency condition of the service flow, and the service flow is to be sent as soon as possible. A larger value of the maximum latency condition indicates a lower latency condition of the service flow, and the service flow is able to not be sent.
For example, in response to the first service flow being an uplink service flow, the SMF network element may determine the maximum latency condition MaxLatency between the second device and the third device based on the packet delay budget (the PDB 2) (or the PDB 2′) for transmitting the first service flow between the second device and the third device, the processing time (TAN) of the first service flow in the access network device or the AN-TT, and the processing time (TUPF) of the first service flow in the user plane network element. The following uses the PDB 2 as an example:
In response to the first service flow being a downlink service flow, the SMF network element may determine the maximum latency condition MaxLatency between the second device and the third device based on the packet delay budget (the PDB 4) (or the PDB 4′) for transmitting the first service flow between the second device and the third device, the processing time (TUPF) of the first service flow in the user plane network element, and the processing time (TAN) of the first service flow in the access network device or the AN-TT. The following uses the PDB 4 as an example:
For example, the fourth device may determine the offset selection value in, but not limited to, the following manner:
In an implementation, the fourth device may determine the offset selection value based on the obtained maximum offset and minimum offset of the first service flow and the maximum latency condition of the service flow. For example, a small offset selection value is set for a service flow with a small value of a maximum latency condition for transmitting the service flow between the second device and the third device. A smaller offset selection value indicates shorter time for caching a data packet of a service flow in the second device, and a larger offset selection value indicates longer time for caching a data packet of a service flow in the second device. A small offset selection value is set for a service flow with a high latency condition, to ensure that a data packet of the service flow is preferentially sent, and therefore ensure a low transmission latency of the service flow.
Optionally, the first device may further send maximum latency conditions of a plurality of service flows to the fourth device, and the fourth device may comprehensively consider maximum latency conditions of service flows to determine an offset selection value for each service flow. For example, in response to a maximum latency condition of a service flow between the second device and the third device being small, the fourth device may determine a value close to a minimum offset corresponding to the service flow as an offset selection value corresponding to the service flow; in response to a maximum latency condition of a service flow between the second device and the third device being large, the fourth device may determine a value close to a maximum offset as an offset selection value corresponding to the service flow.
A specific method for determining the offset selection value by the fourth device is not limited in at least one embodiment. The foregoing content is merely an example and is not intended to limit embodiments described herein. In addition, the foregoing manners may be combined.
In at least one embodiment, the first device may autonomously determine the offset selection value based on the minimum offset and the maximum offset.
The first device and the fourth device are integrated, or the first device integrates a function of the fourth device.
According to the foregoing method, the first device may obtain the offset selection value, and use the offset selection value as the offset of the service flow sending time relative to the reference time, or use the difference between the offset selection value and the jitter latency associated with the first service flow as the offset of the service flow sending time relative to the reference time, to obtain the offset of the service flow sending time relative to the reference time.
Step 820: The first device indicates the second device to wait, after receiving the first service flow, until the service flow sending time to send the first service flow.
For example, in response to the first service flow being an uplink service flow, and the second device is the access network device, the first device may send the information about the service flow sending time to the access network device. In response to the second device being the AN-TT, the first device may directly send the information about the service flow sending time to the AN-TT. Alternatively, the first device may first send the information about the service flow sending time to the access network device, and then the access network device notifies the AN-TT of the information. In response to the first service flow being a downlink service flow, the first device may send, to the user plane network element (the N3-TT), information indicating the service flow sending time.
In at least one embodiment, the information about the service flow sending time includes the offset of the service flow sending time relative to the reference time or the service flow sending time.
In some special cases, the offset selection value may also be equal to the minimum offset, in other words, the service flow sending time may be equal to the earliest sending time. The following uses the offset selection value as an example for description. For example, at a specific moment, no service flow other than the first service flow arrives at the second device, and the second device may send the first service flow based on the minimum offset. For another example, three service flows arrive at the second device at the same time, where the service flows are separately a service flow a, a service flow b, and a service flow c. For the service flow a, an offset selection value corresponding to the service flow a may be equal to a minimum offset corresponding to the service flow a. In this case, after the service flow a arrives at the second device and is processed by the second device, the second device immediately sends the service flow a to the third device. For the service flow b, an offset selection value corresponding to the service flow b may be greater than a minimum offset corresponding to the service flow b and less than or equal to a maximum offset corresponding to the service flow b (where the offset selection value corresponding to the service flow b is denoted as a first value). In this case, after the service flow b arrives at the second device and is processed by the second device, the second device is to wait for a period of time corresponding to a difference between the first value and the minimum offset corresponding to the service flow b before sending the service flow b to the third device. For the service flow c, an offset selection value corresponding to the service flow c may be greater than a minimum offset corresponding to the service flow c and less than or equal to a maximum offset corresponding to the service flow c (where the offset selection value corresponding to the service flow c is denoted as a second value), and the second value is greater than the first value. After the service flow c arrives at the second device and is processed by the second device, the second device is to wait for a period of time corresponding to a difference between the second value and the minimum offset corresponding to the service flow c before sending the service flow c to the third device. Therefore, different service flow sending time is configured for service flows according to the foregoing method, so that congestion does not occur among data packets of the three service flows, and latency conditions of the three service flows can be separately met.
Optionally, the difference between the first value and the minimum offset is duration corresponding to a data packet of MaxFrameSize of the service flow a, and a difference between the second value and the first value is duration corresponding to a data packet of MaxFrameSize of the service flow b. Based on the foregoing setting, the service flow b may be sent after sending of the service flow a is completed, and the service flow c may be sent after sending of the service flow b is completed. In this way, sending congestion among the service flow a, the service flow b, and the service flow c can be better avoided, and network resources can be fully used, so that overall network performance can be improved.
For example, the fourth device sends interface configuration information for the second device to the first device. The first device sends the interface configuration information for the second device to the second device. For example, the interface configuration information for the second device includes an interface identifier (InterfaceID) of the second device and the information about the service flow sending time. The interface identifier of the second device is used to identify an interface of the second device, and may include a MAC address and an interface name (InterfaceName). The interface corresponding to the interface identifier of the second device is an egress port used to send the first service flow. In other words, the second device may learn, based on the interface identifier (InterfaceID) of the second device, which interface is used as the egress port for sending the first service flow, and with reference to the information about the service flow sending time, the second device may wait, based on the information about the service flow sending time, at the egress port until the service flow sending time to send the first service flow.
In addition, the fourth device may further send interface configuration information for the third device to the first device, and the first device sends the interface configuration information for the third device to the third device. For example, the interface configuration information for the third device includes an interface identifier of the third device. Optionally, the interface configuration information for the third device may further include the information about the service flow sending time. The interface identifier of the third device is used to identify an interface of the third device, and may include a MAC address and an interface name. The interface corresponding to the interface identifier of the third device is a receiving port used to receive the first service flow. In other words, the third device may learn, based on the interface identifier of the third device, which interface is used as the receiving port for receiving the first service flow.
In addition, the interface configuration information for the second device and the interface configuration information for the third device may further include a QoS flow identifier (QoS flow identifier, QFI) and a corresponding priority. In response to encapsulating the data packet of the first service flow, the second device may include, in an outer MAC, the priority corresponding to the QFI, so that a switching node on a path between the second device and the third device determines, based on the included priority of the QFI, a transmission queue corresponding to the data packet.
For example, as shown in
In at least one embodiment, the information about the service flow sending time includes a gate control scheduling parameter.
For example, the first device may further determine the gate control scheduling parameter based on the cycle of the first service flow, the maximum burst size of the first service flow, and the service flow sending time. The gate control scheduling parameter herein is a first gate control scheduling parameter, in other words, the first gate control scheduling parameter is a gate control scheduling parameter determined by the first device. The first gate control scheduling parameter may include an administration value (AdminCycleTime) of a port gate control cycle, an administration value (AdminBaseTime) of base time, and an administration value (AdminControlList) of a port gate control list.
The second device determines a second gate control scheduling parameter based on the first gate control scheduling parameter. In other words, the second gate control scheduling parameter is a gate control scheduling parameter determined by the second device. The second gate control scheduling parameter may include an operation value (OperCycleTime) of the port gate control cycle, an operation value (OperBaseTime) of the base time, start time (CycleStartTime) of the gate control cycle, and an operation value (OperControlList) of the gate control list run at a port.
The following describes a relationship between the first gate control scheduling parameter and the second gate control scheduling parameter.
AdminCycleTime is used to configure a gate control cycle of each port. The second device uses the parameter to set OperCycleTime. AdminCycleTime and OperCycleTime may be the same, or may be different.
AdminBaseTime is used to configure start time of the gate control cycle of each port. Usually, AdminBaseTime indicates duration relative to start time of a time domain (for example, 00:00:00 on Jan. 1, 1970). The second device uses the parameter to set OperBaseTime. AdminBaseTime and AdminBaseTime may be the same, or may be different. The second device may determine CycleStartTime based on OperBaseTime and OperCycleTime, where CycleStartTime=OperBaseTime+N*OperCycleTime, and N indicates an Nth cycle and N is a positive integer.
AdminControlList is used to configure a transmission queue gate control action of each port, including a gate control state (gateState) and a time interval (TimeInterval), where gateState is a gate control state (Open or Closed) of each transmission queue of the port. In response to the gate control state being Open, the switching node may transmit the service flow; in response to the gate control state being Closed, the switching node cannot transmit the service flow. TimeInterval indicates duration of the gate control state. The switching node uses the parameter to set the operation value of OperControlList. AdminControlList and OperControlList may be the same, or may be different.
The second device may be configured to transmit a plurality of service flows, the plurality of service flows may arrive at the second device at the same time or may not arrive at the second device at the same time, and priorities of the plurality of service flows may be the same or different. Currently, in response to the priorities of the plurality of service flows being different, the second device may place each service flow into a different transmission queue based on a priority of the service flow. A plurality of service flows with a same priority are placed into a same transmission queue. For each transmission queue, the first device may determine a corresponding first gate control scheduling parameter based on a service flow that is to be transmitted in the transmission queue, and the second device may determine, based on the first gate control scheduling parameter corresponding to the transmission queue, a second gate control scheduling parameter corresponding to the transmission queue. In other words, a gate control scheduling parameter corresponding to a transmission queue is used to schedule one or more service flows that have a same priority and that are transmitted by using the transmission queue.
Specifically, for a method for configuring the first gate control scheduling parameter by the first device, refer to the following examples:
Example 1: In response to a plurality of service flows with a same priority arriving at the same time, the first device places the plurality of service flows into one transmission queue, and sends a minimum offset and a maximum offset (and optionally, a priority) of each of the plurality of service flows to the fourth device. The fourth device may configure a different offset selection value for each service flow. For example, an interval, determined by the fourth device, between offset selection values of any two adjacently sent service flows in offset selection values separately corresponding to the plurality of service flows is not less than duration corresponding to a maximum data packet of a service flow that is first sent in the two service flows, so that no congestion occurs during sending of the plurality of service flows. In addition, an offset selection value corresponding to each service flow is greater than or equal to a minimum offset corresponding to the service flow, and is less than or equal to a maximum offset corresponding to the service flow, to meet deterministic latency conditions separately corresponding to the plurality of service flows. Further, the first device may determine, based on the offset selection values separately corresponding to the plurality of service flows, information about service flow sending time of each service flow, and send the information to the second device.
In addition, the first device may further determine AdminBaseTime based on a minimum value in the offset selection values separately corresponding to the plurality of service flows, determine AdminCycleTime based on a least common multiple of cycles separately corresponding to the plurality of service flows, and determine, based on duration corresponding to a maximum data packet of each service flow, duration in which a gate state is Open.
In other words, in this example, the first device sends the offset selection values of the service flows and a first gate control scheduling parameter to the second device.
For example, a periodic service flow J and a periodic service flow K have a same priority. Both the periodic service flow J and the periodic service flow K are downlink service flows. EarliestTransmitOffset corresponds to a minimum offset, LatestTransmitOffset corresponds to a maximum offset, and TimeAwareOffset corresponds to an offset selection value. In the following example, LatestTransmitOffset is calculated in the manner A* of determining the maximum offset. LatestTransmitOffset may alternatively be calculated in the manner B* or the manner C*. This is merely an example and is not limited in at least one embodiment.
Parameters of the periodic service flow J are as follows:
Parameters of the periodic service flow K are as follows:
In the scenario in which the latency jitter is not considered, EarliestTransmitOffset (corresponding to a minimum offset) and LatestTransmitOffset (corresponding to a maximum offset) of the flow J may be calculated according to the formula (11-4) and formula (13-1):
In the scenario in which the latency jitter is not considered, EarliestTransmitOffset (corresponding to a minimum offset) and LatestTransmitOffset (corresponding to a maximum offset) of the flow K may be calculated according to the formula (11-4) and formula (13-1):
TimeAwareOffset (corresponding to offset selection values) returned by the fourth device is as follows:
The fourth device may learn of <Maximum Burst Size in time> of the flow J and the flow K to obtain jitters through calculation. In response to determining TimeAwareOffset of each service flow, the fourth device may refer to <Maximum Burst Size in time>, so that a difference between TimeAwareOffset corresponding to the flow J and TimeAwareOffset corresponding to the flow K that are determined by the fourth device is equal to <Maximum Burst Size in time> of the flow J. Therefore, deterministic transmission of the flow J is ensured.
Further, the first device determines based on the foregoing result:
The first device sends the foregoing determined parameters to the second device, and the second device determines based on these parameters:
The second device may send the periodic service flow J to the third device based on the offset of the sending time of the periodic service flow J relative to the reference time and a second gate control scheduling parameter, and send the periodic service flow K to the third device based on the offset of the sending time of the periodic service flow K relative to the reference time and the second gate control scheduling parameter. This can meet deterministic latency conditions of the periodic service flow J and the periodic service flow K, and can also avoid congestion between the periodic service flow J and the periodic service flow K.
Descriptions are provided herein with reference to
In the foregoing manner, different service flow sending time of the periodic service flow J and the periodic service flow K and the gate control scheduling parameters corresponding to the periodic service flow J and the periodic service flow K are configured, so that congestion between service flows that have a same priority and arrive at the second device at the same time can be avoided, and deterministic latency conditions of the service flows can be ensured.
Example 2: In response to a plurality of service flows with a same priority arriving at the same time, the first device places the plurality of service flows into one transmission queue, and sends a minimum offset, a maximum offset, and a priority of each of the plurality of service flows to the fourth device. The fourth device may configure an offset selection value for each service flow. An offset selection value corresponding to each service flow is greater than or equal to a minimum offset corresponding to the service flow, and is less than or equal to a maximum offset corresponding to the service flow, to meet deterministic latency conditions separately corresponding to the plurality of service flows. The first device may determine AdminBaseTime based on a minimum value in differences between offset selection values separately corresponding to the plurality of service flows and corresponding jitters, determine AdminCycleTime based on a least common multiple of cycles separately corresponding to the plurality of service flows, and determine, based on duration corresponding to a maximum data packet of each service flow, duration in which a gate state is Open.
In this case, the first device may not directly configure service flow sending time separately corresponding to the plurality of service flows, but implicitly indicate service flow sending time for the plurality of service flows by using AdminBaseTime. The service flow sending time may be service flow sending time of any service flow in the plurality of service flows, and another service flow is randomly sent after the service flow, in other words, a sending sequence of each service flow is not specified. Sufficient duration in which the gate state is Open is reserved, to ensure that the plurality of service flows can be all sent from the second device in response to the gate state being Open.
For example, a periodic service flow J and a periodic service flow K have a same priority. For specific parameters of the periodic service flow J and the periodic service flow K, refer to the descriptions in the example 1.
Similarly, jitters (jitter) of the periodic service flow J and the periodic service flow K may be calculated based on the foregoing related descriptions of the latency jitter:
Therefore, EarliestTransmitOffset (corresponding to a minimum offset) and LatestTransmitOffset (corresponding to a maximum offset) of the flow J may be calculated according to the formula (12-3) and formula (14):
EarliestTransmitOffset (corresponding to a minimum offset) and LatestTransmitOffset (corresponding to a maximum offset) of the flow K may be calculated according to the formula (12-3) and formula (14):
TimeAwareOffset (corresponding to offset selection values) returned by the fourth device is as follows:
The first device subtracts a corresponding jitter from each TimeAwareOffset, to obtain: a difference between TimeAwareOffset corresponding to the flow J and the corresponding jitter is 1600,000,000,000,320−40=1600,000,000,000,280 μs, and a difference between TimeAwareOffset corresponding to the flow K and the corresponding jitter is 1600,000,000,000,340-60=1600,000,000,000,280 μs. Further, the first device may determine, based on the foregoing result, that AdminBaseTime is 1600,000,000,000 280 μs. The first device further determines that AdminCycleTime is 500 μs, and configures AdminControlList based on AdminCycleTime and <Maximum Burst Size in time>, where for GateState=Open, TimeInterval=200 μs; and for GateState=Closed, TimeInterval=300 μs.
The fourth device may determine, based on priorities of service flows sent by the first device, that the flow J and the flow K are service flows of a same priority, and obtain the jitters through calculation based on <Maximum Burst Size in time> of the flow J and the flow K. In response to determining TimeAwareOffset of each service flow, the fourth device may refer to a jitter, so that the difference between TimeAwareOffset corresponding to the flow J and the corresponding jitter and the difference between TimeAwareOffset corresponding to the flow K and the corresponding jitter that are determined by the first device correspond to a same time offset, namely, AdminBaseTime.
Descriptions are provided herein with reference to
After receiving AdminBaseTime, AdminCycleTime, and AdminControlList of the periodic service flow J and the periodic service flow K, the second device may determine OperBaseTime, OperCycleTime, and OperControlList of the periodic service flow J and the periodic service flow K based on these parameters. For example,
As shown in
In the example 2, each time in response to the gate control state corresponding to the periodic service flow J and the periodic service flow K being Open, although the first device does not indicate a sequence of sending the periodic service flow J and the periodic service flow K, in other words, the sequence of sending the periodic service flow J and the periodic service flow K is not determined, for example, the second device may first send the periodic service flow J or may first send the periodic service flow K, micro-bursts and micro-congestion of the second device and the transmission node between the second device and the third device are still not caused. A cause is that the first device may configure the second device to reserve sufficient sending time for the periodic service flow J and the periodic service flow K, in other words, duration in which the gate control state is Open is sufficient. For the second device, regardless of whether the periodic service flow J or the periodic service flow K is first sent, sending of the periodic service flow J and the periodic service flow K can be completed within the duration in which the gate control state is Open. Similarly, for the transmission node between the second device and the third device, regardless of whether the periodic service flow J or the periodic service flow K is first received, the fourth device may configure the transmission node to reserve, for transmitting the two periodic service flows, fixed and sufficient duration in which the gate control state is Open, so that sending of the periodic service flow J and the periodic service flow K can be completed within the duration in which the gate control state is Open. According to the solution provided in this embodiment of at least one embodiment, the second device and the transmission node between the second device and the third device reserve sufficient resources for transmitting the periodic service flow J and the periodic service flow K, so that determinacy of transmission time of the periodic service flow J and determinacy of transmission time of the periodic service flow K can be implemented.
In other words, in the example 2, a gate control scheduling parameter is used to implicitly indicate service flow sending time for service flows with a same priority, the service flow sending time transferred by using the gate control scheduling parameter may be used to sequentially send a plurality of service flows in a transmission queue, and time in which a gate control state is Open is sufficient to ensure completion of transmission of the plurality of service flows, so that deterministic transmission is implemented, and overall network performance is improved.
Example 3: In response to a plurality of service flows with different priorities not arriving at the same time, the first device places the plurality of service flows into different transmission queues. The first device may send a minimum offset, a maximum offset, and a priority of each of the plurality of service flows to the fourth device. The fourth device may configure a different offset selection value for each service flow. For example, an interval, determined by the fourth device, between offset selection values of any two adjacently sent service flows in offset selection values separately corresponding to the plurality of service flows is not less than duration corresponding to a maximum data packet of a service flow with a higher priority in the two service flows, so that a service flow with a high priority is sent before a service flow with a low priority, and no congestion occurs during sending of the plurality of service flows. In addition, an offset selection value corresponding to each service flow is greater than or equal to a minimum offset corresponding to the service flow, and is less than or equal to a maximum offset corresponding to the service flow, to meet deterministic latency conditions separately corresponding to the plurality of service flows. Further, the first device may determine, based on the offset selection values separately corresponding to the plurality of service flows, service flow sending time of each service flow, and send the service flow sending time to the second device.
In addition, the first device determines AdminBaseTime based on a minimum value in the offset selection values separately corresponding to the plurality of service flows, and determine AdminCycleTime based on a least common multiple of cycles separately corresponding to the plurality of service flows.
For example, a periodic service flow J and a periodic service flow K have different priorities, and a priority of the periodic service flow J is higher than a priority of the periodic service flow K, in other words, the periodic service flow J is preferentially sent relative to the periodic service flow K. Both the periodic service flow J and the periodic service flow K are downlink service flows. EarliestTransmitOffset corresponds to a minimum offset, LatestTransmitOffset corresponds to a maximum offset, and TimeAwareOffset corresponds to an offset selection value. In the following example, LatestTransmitOffset is calculated in the manner A* of determining the maximum offset. LatestTransmitOffset may alternatively be calculated in the manner B* or the manner C*. This is merely an example and is not limited in at least one embodiment.
Parameters of the periodic service flow J are as follows:
Therefore, EarliestTransmitOffset (corresponding to a minimum offset) and LatestTransmitOffset (corresponding to a maximum offset) of the periodic service flow J may be calculated according to the formula (11-4) and formula (13-1):
Parameters of the periodic service flow K are as follows:
Similarly, EarliestTransmitOffset (corresponding to a minimum offset) and LatestTransmitOffset (corresponding to a maximum offset) of the periodic service flow K may be calculated according to the formula (11-4) and formula (13-1):
The first device sends EarliestTransmitOffset and LatestTransmitOffset of the periodic service flow J and the priority of the periodic service flow J to the fourth device, and sends EarliestTransmitOffset and LatestTransmitOffset of the periodic service flow K and the priority of the periodic service flow K to the fourth device. The fourth device determines, for each of the periodic service flow J and the periodic service flow K, a value in a range from EarliestTransmitOffset to LatestTransmitOffset as TimeAwareOffset (corresponding to an offset selection value). TimeAwareOffset (corresponding to offset selection values), of the periodic service flow J and the periodic service flow K, returned by the fourth device is as follows:
A difference between TimeAwareOffset of the periodic service flow K and TimeAwareOffset of the periodic service flow J is <Maximum Burst Size in time> of the flow K. In this way, the periodic service flow K and the periodic service flow J may be sent in a staggered manner, and congestion does not occur. Certainly, at least one embodiment is not limited thereto. The difference between TimeAwareOffset of the periodic service flow K and TimeAwareOffset of the periodic service flow J may alternatively be greater than <Maximum Burst Size in time> of the flow K.
The first device may determine, based on TimeAwareOffset of different flows, that AdminBaseTime is 1600,000,000,000,260 μs (for example, is a minimum value in TimeAwareOffset of the different flows). The first device further determines that AdminCycleTime is 800 μs (namely, a least common multiple of Interval corresponding to the periodic service flow J and Interval corresponding to the periodic service flow K), and configures AdminControlList based on AdminCycleTime, Interval corresponding to the periodic service flow J and the periodic service flow K, and <Maximum Burst Size in time> corresponding to the periodic service flow J and the periodic service flow K.
Descriptions are provided herein with reference to
For a queue in which the periodic service flow K is located, a gate state of the periodic service flow K is Closed at the beginning, and is switched to Open until the gate state of the periodic service flow J is Closed. Other principles are similar to those of the periodic service flow J. Therefore, AdminControlList of the periodic service flow K includes: for GateState=Closed, TimeInterval=120 μs; for GateState=Open, TimeInterval=80 μs; for GateState=Closed, TimeInterval=720 μs; for GateState=Open, TimeInterval=80 μs; and for GateState=Closed, TimeInterval=720 μs.
In addition to determining AdminBaseTime, AdminCycleTime, AdminControlList of the periodic service flow J, and AdminControlList of the periodic service flow K, the first device also determines service flow sending time of the periodic service flow J, that is, AdminBaseTime, and determines service flow sending time of the periodic service flow K, to be specific, determines, as the service flow sending time of the periodic service flow K based on AdminBaseTime, AdminControlList of the periodic service flow J, and AdminControlList of the periodic service flow K, time in which the gate state of the periodic service flow K is Open.
After receiving AdminBaseTime, AdminCycleTime, and AdminControlList of the periodic service flow J and the periodic service flow K, the second device may determine, based on these parameters, OperBaseTime, OperCycleTime, and OperControlList of the periodic service flow J and the periodic service flow K, the service flow sending time of the periodic service flow K, and the service flow sending time of the periodic service flow J. For example:
Descriptions are provided herein with reference to
For example, for the periodic service flow J, at a time offset corresponding to 1600,000,000,000,260 μs, the gate state of the transmission queue of the periodic service flow J is Open. Duration in which the gate state is Open is 120 μs. At a time offset corresponding to 1600,000,000,000,380 μs, the gate state of the transmission queue of the periodic service flow J is Closed. Duration in which the gate state is Closed is 280 μs. At a time offset corresponding to 1600,000,000,000,660 μs, the gate state of the transmission queue of the periodic service flow J is Open again, and a next cycle is entered. The rest may be deduced by analogy.
For the periodic service flow K, at the time offset corresponding to 1600,000,000,000,260 μs, the gate state of the transmission queue of the periodic service flow K is Closed. Duration in which the gate state is Closed is 120 μs. At the time offset corresponding to 1600,000,000,000,380 μs, the gate state of the transmission queue of the periodic service flow K is Open. Duration in which the gate state is Open is 80 μs. At a time offset corresponding to 1600,000,000,000,460 μs, the gate state of the transmission queue of the periodic service flow K is Closed again, and a next cycle is entered. The rest may be deduced by analogy.
As shown in
In the example 1, although the periodic service flow J and the periodic service flow K have different priorities and arrive at the second device at different time, the method provided in at least one embodiment can ensure that a high-priority service flow is preferentially sent. Specifically, the priority of the periodic service flow J is higher than the priority of the periodic service flow K. According to the method provided in this embodiment of at least one embodiment, gate control states and duration corresponding to different transmission queues in which the periodic service flow J and the periodic service flow K are located are controlled. In response to the periodic service flow K arriving at the second device earlier than the periodic service flow J, the periodic service flow J with a higher priority can still be preferentially sent. This avoids a case in which the periodic service flow J is to wait to be sent until completion of sending of the periodic service flow K because the periodic service flow K is being sent.
In some embodiments, the first device may further send, to the second device, information used to determine the gate control scheduling parameter, and the second device determines the gate control scheduling parameter. The information used to determine the gate control scheduling parameter herein may include a cycle of each service flow, an offset selection value of each service flow, duration corresponding to a maximum data packet corresponding to each service flow, and the like.
In addition, in at least one embodiment, the fourth device is further configured to: determine the forwarding path (to be specific, the forwarding path from the second device to the third device) of the first service flow based on a user plane topology (including the access network device, the user plane network element, and a transmission node between the access network device and the user plane network element), capability information of each transmission node, and information that is about the first service flow and that is sent by the first device, for example, the minimum offset and the maximum offset in the foregoing embodiment; and configure a transmission node on the forwarding path, to be specific, send a corresponding gate control scheduling parameter to each transmission node. The gate control scheduling parameter herein is a gate control scheduling parameter for the transmission node. For example, AdminBaseTime in a gate control scheduling parameter of a next-hop transmission node of the second device may be AdminBaseTime in the gate control scheduling parameter of the second device plus a maximum transmission latency used from the second device to the next-hop transmission node of the second device. Content of other parameters is the same. The transmission node may further send capability information (used by the fourth device to configure the forwarding path for the service flow and determine a corresponding gate control scheduling parameter) of the transmission node to the fourth device, and the transmission node that receives the gate control scheduling parameter forwards the first service flow based on the received gate control scheduling parameter. How the fourth device determines the forwarding path of the first service flow and configures the transmission node on the forwarding path is not limited in at least one embodiment. Therefore, through configuration of the second device and the transmission node on the forwarding path determined from the second device to the third device, a deterministic transmission latency condition between the second device and the third device can be ensured.
The following
S1301: The SMF network element obtains, from UE, residence time (UE-DS-TT-Residence Time) of the first service flow in a DS-TT and the UE.
In addition, the SMF network element may further obtain a parameter, for example, a MAC address of a DS-TT port. This is not limited in at least one embodiment. The residence time (UE-DS-TT-Residence Time) of the first service flow in the DS-TT and the UE may be carried in a PDU session establishment request message, and is sent by the UE to the SMF network element through the gNB and an AMF network element.
For details, refer to related descriptions in the manner 1. Repeated parts are not described again.
S1302: The SMF network element obtains processing time information of the AN-TT and port information of the AN-TT.
For example, in response to the AN-TT being a device that is independently deployed outside the gNB, the SMF network element may obtain the processing time information of the AN-TT and the port information of the AN-TT from the AN-TT, or obtain the processing time information of the AN-TT and the port information of the AN-TT from the gNB. In this case, the processing time information of the AN-TT and the port information of the AN-TT are sent by the AN-TT to the gNB, or configured on the gNB.
For example, in response to the AN-TT being used as a functional module inside the gNB, the SMF network element may obtain the processing time information of the AN-TT and the port information of the AN-TT from the gNB. In this case, the processing time information of the AN-TT is also referred to as processing time information of the gNB.
The port information of the AN-TT specifically includes an identifier of each port, where the identifier of each port includes a MAC address and an interface name of each port. In addition, the port information of the AN-TT may further include another parameter. This is not limited in at least one embodiment.
For example, the SMF network element may determine, based on the processing time information of the AN-TT, processing time of the first service flow in the AN-TT. For specific content of the processing time information of the AN-TT, refer to related descriptions of the processing time information of the second device in step 810.
S1303: A PCF network element sends a PCC rule to the SMF network element.
The PCC rule includes a TSC assistance container, and the TSC assistance container includes information about burst arrival time of the first service flow, a cycle of the first service flow, and a direction of the first service flow. The PCC rule may further include a service condition description parameter, and the service condition description parameter may include a maximum burst size. In addition, the TSC assistance container and the service condition parameter may further include other parameters. For specific content, refer to related content in the manner 1. The information about the burst arrival time of the first service flow herein is information about time at which the first service flow arrives at the DS-TT.
In correspondence to
In correspondence to
For example, the PCF network element may generate the PCC rule based on the information about the burst arrival time of the first service flow, the cycle of the first service flow, the direction of the first service flow, and the service condition description parameter that are obtained from the TSN AF network element or the TSCTSF network element, and send the PCC rule to the SMF network element. The SMF network element associates the PCC rule with a QoS flow, and the QoS flow is a QoS flow corresponding to the first service flow.
In a 5GS system, the first service flow may be a service flow obtained through aggregation by the TSN AF or the TSCTSF. In other words, the TSN AF or the TSCTSF aggregates a plurality of service flows with same or similar features, to obtain the first service flow.
S1304: The SMF network element determines a minimum offset and a maximum offset.
The minimum offset may also be referred to as an earliest offset, and the maximum offset may also be referred to as a latest offset. For example, the SMF network element determines TSpecTimeAware. The minimum offset corresponds to EarliestTransmitOffset in TSpecTimeAware, and the maximum offset corresponds to LatestTransmitOffset in TSpecTimeAware. An example in which the minimum offset is EarliestTransmitOffset and the maximum offset is LatestTransmitOffset is only used below for description.
(1) The SMF network element determines EarliestTransmitOffset.
For example, the SMF network element may determine, according to the formula (11-3) or formula (12-2), EarliestTransmitOffset based on UE-DS-TT-Residence Time in S1301, the processing time information of the gNB in S1302, the information about the burst arrival time of the first service flow in the PCC rule in S1303, and a PDB 1 determined based on the PCC rule.
(2) The SMF network element determines LatestTransmitOffset.
For example, the SMF network element may determine, according to the formula (13-2) or formula (14), LatestTransmitOffset based on UE-DS-TT-Residence Time in S1301, the information about the burst arrival time of the first service flow in the PCC rule in S1303, the cycle of the first service flow, the maximum burst size included in the service condition description parameter, and the PDB 1 determined based on the PCC rule.
Alternatively, in response to the SMF network element obtaining maximum buffer duration of the first service flow in the AN-TT, the SMF network element may determine, according to the formula (15-2) or formula (16), LatestTransmitOffset based on the processing time information of the AN-TT in S1302, the maximum buffer duration of the first service flow in the AN-TT, UE-DS-TT-Residence Time in S1301, the information about the burst arrival time of the first service flow in the PCC rule in S1303, and the PDB 1 determined based on the PCC rule. For obtaining, by the SMF network element, the maximum buffer duration of the first service flow in the AN-TT, refer to the descriptions in the foregoing related paragraphs. Details are not described herein again. For example, in this case, the SMF network element further is to obtain processing time information of a UPF network element from the UPF network element.
Alternatively, after determining the two values of LatestTransmitOffset, the SMF network element may select a smaller value as LatestTransmitOffset.
In response to the AN-TT being used as a functional module inside the gNB, the SMF network element determines the PDB 1 based on the PCC rule. In response to the AN-TT being a device that is independently deployed outside the gNB, the SMF network element determines a PDB 1′ based on the PCC rule, in other words, the PDB 1 is replaced with the PDB 1′.
S1305: The SMF network element sends an identifier (StreamID) of the first service flow, the minimum offset, and the maximum offset to a CNC-TN network element.
In addition, the SMF network element may further send, to the CNC-TN network element, at least one parameter in a priority (StreamRank) of the first service flow, the cycle of the first service flow, a size of a maximum frame, a maximum latency condition between the AN-TT and an N3-TT network element, and the port information of the AN-TT.
The size of the maximum frame is determined based on the maximum burst size. For a manner of determining the maximum latency condition between the AN-TT and the N3-TT network element, refer to related descriptions in the embodiment of
S1306: The CNC-TN network element determines an offset selection value based on the received minimum offset and maximum offset, and sends the identifier of the first service flow and interface configuration information to the SMF network element.
The interface configuration information may include InterfaceID and the offset selection value, and InterfaceID is used to identify a port indicated by the port information of the AN-TT in S1302.
The offset selection value is TimeAwareOffset. TimeAwareOffset≥EarliestTransmitOffset, and TimeAwareOffset≤LatestTransmitOffset.
S1307: The SMF network element determines a gate control scheduling parameter based on the offset selection value returned by the CNC-TN network element. The gate control scheduling parameter includes AdminBaseTime, AdminCycleTime, and AdminControlList.
For example, the SMF network element determines the gate control scheduling parameter based on the offset selection value, the cycle of the first service flow, and the maximum burst size. For details, refer to the example 1, example 2, and example 3 shown by using the periodic service flow J and the periodic service flow K. Details are not described herein again.
S1308: The SMF network element sends the gate control scheduling parameter.
In response to the AN-TT being a device that is independently deployed outside the gNB, the SMF network element sends the gate control scheduling parameter to the AN-TT; or the SMF sends the gate control scheduling parameter to the gNB, and the gNB sends the gate control scheduling parameter to the AN-TT.
In response to the AN-TT being used as a functional module inside the gNB, the SMF network element sends the gate control scheduling parameter to the gNB. The gNB notifies the AN-TT of the gate control scheduling parameter through an internal interface.
In addition, the SMF network element further sends InterfaceID.
According to the foregoing method, the SMF network element configures, for the AN-TT, the gate control scheduling parameter associated with the first service flow, and the AN-TT transmits the service flow according to configuration of the SMF network element, so that a problem of congestion between the first service flow and another service flow can be avoided. Therefore, a deterministic latency condition of the first service flow is met, low-latency transmission between the AN-TT and the N3-TT can be implemented, and overall network performance can be improved.
In
S1401: The SMF network element obtains processing time information of a UPF network element and port information of an N3-TT from the UPF network element.
The port information of the N3-TT specifically includes an identifier of each port, where the identifier of each port includes a MAC address and an interface name of each port. In addition, the port information of the N3-TT may further include another parameter. This is not limited in at least one embodiment.
For example, the SMF network element may obtain the processing time information of the UPF network element from the UPF network element, and determine processing time of the first service flow in the UPF network element based on the processing time information of the UPF network element. For specific content of the processing time information of the UPF network element, refer to related descriptions of the processing time information of the second device in step 810. In addition, a manner of obtaining the processing time information of the UPF network element is similar to a manner of obtaining the port information of the N3-TT. For details, refer to related descriptions of obtaining, by the first device, the processing time information of the user plane network element from the user plane network element in step 810. Repeated parts are not described again.
S1402: A PCF network element sends a PCC rule to the SMF network element.
For example, the PCC rule includes a TSC assistance container, and the TSC assistance container includes information about burst arrival time of the first service flow, a cycle of the first service flow, and a direction of the first service flow. The PCC rule further includes a service condition description parameter, and the service condition description parameter includes a maximum burst size. In addition, the TSC assistance container and the service condition parameter may further include other parameters. For specific content, refer to related content in the manner 1. A difference from S1303 lies in that the information about the burst arrival time of the first service flow herein is information about time at which the first service flow arrives at an NW-TT.
S1403: The SMF network element determines a minimum offset and a maximum offset.
The minimum offset may also be referred to as an earliest offset, and the maximum offset may also be referred to as a latest offset. For example, the SMF network element determines TSpecTimeAware. The minimum offset corresponds to EarliestTransmitOffset in TSpecTimeAware, and the maximum offset corresponds to LatestTransmitOffset in TSpecTimeAware. An example in which the minimum offset is EarliestTransmitOffset and the maximum offset is LatestTransmitOffset is only used below for description.
(1) The SMF network element determines EarliestTransmitOffset. For example, the SMF network element may determine, according to the formula (11-5) or formula (12-3), EarliestTransmitOffset based on the processing time information of the UPF network element in S1401 and the information about the burst arrival time of the first service flow in the PCC rule in S1402.
(2) The SMF network element determines LatestTransmitOffset. For example, the SMF network element may determine, according to the formula (13-3) or formula (14), LatestTransmitOffset based on the information about the burst arrival time of the first service flow, the cycle of the first service flow, and the maximum burst size included in the service condition description parameter that are in the PCC rule in S1402.
Alternatively, in response to the SMF network element determining maximum buffer duration of the first service flow in the UPF network element, the SMF network element may determine, according to the formula (15-3) or formula (16), LatestTransmitOffset based on the processing time information of the UPF network element in S1401, the maximum buffer duration of the first service flow in the UPF, and the information about the burst arrival time of the first service flow in the PCC rule in S1402. For obtaining, by the SMF network element, the maximum buffer duration of the first service flow in the UPF network element, refer to the descriptions in the foregoing related paragraphs. Details are not described herein again. For example, in this case, the SMF network element further is to obtain processing time information of an AN-TT.
Alternatively, after determining the two values of LatestTransmitOffset, the SMF network element may select a smaller value as LatestTransmitOffset.
S1404: The SMF network element sends an identifier of the first service flow, the minimum offset, and the maximum offset to a CNC-TN network element.
In addition, the SMF network element may further send, to the CNC-TN network element, at least one parameter in a priority of the first service flow, the cycle of the first service flow, a size of a maximum frame, a maximum latency condition between the AN-TT and the N3-TT network element, and the port information of the N3-TT.
The size of the maximum frame is determined based on the maximum burst size. For a manner of determining the maximum latency condition between the AN-TT and the N3-TT network element, refer to related descriptions in the embodiment of
S1405: The CNC-TN network element determines an offset selection value based on the received minimum offset and maximum offset, and sends the identifier of the first service flow and interface configuration information to the SMF network element.
The interface configuration information may include InterfaceID and the offset selection value, and InterfaceID is used to identify a port of the N3-TT that is indicated by the port information of the N3-TT in S1401.
The offset selection value is TimeAwareOffset. TimeAwareOffset≥EarliestTransmitOffset, and TimeAwareOffset≤LatestTransmitOffset.
S1406: The SMF network element determines a gate control scheduling parameter based on the offset selection value returned by the CNC-TN network element. The gate control scheduling parameter includes AdminBaseTime, AdminCycleTime, and AdminControlList.
For example, the SMF network element determines the gate control scheduling parameter based on the offset selection value, the cycle of the first service flow, and the maximum burst size. For details, refer to the example 1, example 2, and example 3 shown by using the periodic service flow J and the periodic service flow K. Details are not described herein again.
S1407: The SMF network element sends the gate control scheduling parameter to the UPF network element.
The UPF network element may notify the N3-TT of the gate control scheduling parameter through an internal interface.
In addition, the SMF network element further sends InterfaceID to the UPF network element, and the UPF network element notifies the N3-TT of InterfaceID through the internal interface.
In the embodiments shown in
According to the foregoing method, the SMF network element configures, for the N3-TT, the gate control scheduling parameter associated with the first service flow, and the N3-TT transmits the service flow according to configuration of the SMF, so that a problem of congestion between the first service flow and another service flow can be avoided. Therefore, a deterministic latency condition of the first service flow is met, low-latency transmission between the AN-TT and the N3-TT can be implemented, and overall network performance can be improved.
With reference to
For S1501 and S1502, refer to S1301 and S1302. Repeated parts are not described again.
S1503: An SMF network element sends, to the TSN AF network element through a PCF network element, information obtained in S1501 and S1502.
For example, processing time information of an AN-TT and port information of the AN-TT may be encapsulated in a container (Container), in other words, invisible to the SMF network element; or may not be encapsulated in a container, and in this case, the SMF network element may read the information.
S1504: The PCF network element sends a PCC rule to the SMF network element.
For details, refer to S1303.
S1505: The SMF network element determines, based on the PCC rule, any one or both of a packet delay budget (PDB 1) for transmitting the first service flow between UE and a gNB and a packet delay budget (PDB 2) for transmitting the first service flow between the gNB and the UPF network element.
S1506: The SMF network element sends, to the TSN AF network element through the PCF network element, any one or both of the packet delay budget (PDB 1) for transmitting the first service flow between the UE and the gNB and the packet delay budget (PDB 2) for transmitting the first service flow between the gNB and the UPF network element. In response to the SMF sending only the PDB 2, the TSN AF network element further determines the PDB 1 based on the PDB 2.
In addition, the SMF network element may send, to the TSN AF network element through the PCF network element, the information obtained in S1501 and S1502, and any one or both of the packet delay budget (PDB 1) for transmitting the first service flow between the UE and the gNB and the packet delay budget (PDB 2) for transmitting the first service flow between the gNB and the UPF network element, that is, S1503 and S1506 may be combined into one step.
In addition, in response to the AN-TT being a device that is independently deployed outside the gNB, the PDB 1 and the PDB 2 are replaced with a PDB 1′ and a PDB 2′.
S1507: The TSN AF network element determines a minimum offset and a maximum offset.
A method for determining the minimum offset and the maximum offset by the TSN AF network element may be the same as the method for determining the minimum offset and the maximum offset by the SMF network element. For details, refer to related descriptions in S1304.
S1508: The TSN AF network element sends an identifier of the first service flow, the minimum offset, and the maximum offset to a CNC-TN network element.
S1509: The TSN AF network element obtains the identifier of the first service flow and interface configuration information from the CNC-TN network element.
The interface configuration information may include InterfaceID and an offset selection value, and InterfaceID is used to identify a port in the port information of the AN-TT.
The offset selection value may be TimeAwareOffset. TimeAwareOffset≥EarliestTransmitOffset, and TimeAwareOffset≤LatestTransmitOffset.
S1510: The TSN AF network element determines a gate control scheduling parameter based on the offset selection value returned by the CNC-TN network element. The gate control scheduling parameter includes AdminBaseTime, AdminCycleTime, and AdminControlList.
S1511: The TSN AF network element sends the gate control scheduling parameter to the SMF network element through the PCF network element. In addition, the TSN AF network element may further send InterfaceID to the SMF network element through the PCF network element.
S1512: The SMF network element sends the gate control scheduling parameter.
In response to the AN-TT being a device that is independently deployed outside the gNB, the SMF network element sends the gate control scheduling parameter to the AN-TT; or the SMF sends the gate control scheduling parameter to the gNB, and the gNB sends the gate control scheduling parameter to the AN-TT.
In response to the AN-TT being used as a functional module inside the gNB, the SMF network element sends the gate control scheduling parameter to the gNB.
In addition, the SMF network element further sends InterfaceID.
According to the foregoing method, the TSN AF network element configures, for the AN-TT through the SMF network element, a first gate control scheduling parameter associated with the first service flow, and the AN-TT transmits the service flow according to configuration of the TSN AF, so that a problem of congestion between the first service flow and another service flow can be avoided. Therefore, a deterministic latency condition of the first service flow is met, low-latency transmission between the AN-TT and an N3-TT can be implemented, and overall network performance can be improved.
In
For S1601, refer to S1401. Repeated parts are not described again.
S1602: An SMF network element sends, to the TSN AF network element through a PCF network element, information obtained in S1601.
For example, processing time information of a UPF network element and port information of an N3-TT that are obtained from the UPF network element may be encapsulated in a container (Container), in other words, invisible to the SMF network element; or may not be encapsulated in a container, and in this case, the SMF network element may read the information.
S1603: The TSN AF network element determines a minimum offset and a maximum offset.
For details, refer to related descriptions of S1403.
S1604: The TSN AF network element sends an identifier of the first service flow, the minimum offset, and the maximum offset to a CNC-TN network element.
S1605: The TSN AF network element obtains the identifier of the first service flow and interface configuration information from the CNC-TN network element.
The interface configuration information may include InterfaceID and an offset selection value, and InterfaceID is used to identify an interface of the UPF network element or a port in the port information of the N3-TT.
The offset selection value may be TimeAwareOffset. TimeAwareOffset≥EarliestTransmitOffset, and TimeAwareOffset≤LatestTransmitOffset.
S1606: The TSN AF network element determines a gate control scheduling parameter based on the offset selection value returned by the CNC-TN network element. The gate control scheduling parameter includes AdminBaseTime, AdminCycleTime, and AdminControlList.
S1607: The TSN AF network element sends the gate control scheduling parameter to the SMF network element through the PCF network element.
In addition, the TSN AF network element further sends InterfaceID to the SMF network element through the PCF network element.
S1608: The SMF network element sends the gate control scheduling parameter to the UPF network element.
The UPF network element notifies the N3-TT of the gate control scheduling parameter.
In addition, the SMF network element sends InterfaceID to the UPF network element, and the UPF network element notifies the N3-TT of InterfaceID.
In the embodiments shown in
According to the foregoing method, the TSN AF network element configures, for the N3-TT through the SMF network element, a first gate control scheduling parameter associated with the first service flow, and the N3-TT transmits the service flow according to configuration of the TSN AF, so that a problem of congestion between the first service flow and another service flow can be avoided. Therefore, a deterministic latency condition of the first service flow is met, low-latency transmission between the AN-TT and the N3-TT can be implemented, and overall network performance can be improved.
In response to the TSN AF network element in the embodiments shown in
In another embodiment, in addition to the network architectures in
The EM network element provides a network element management function, and manages one or more network elements.
The NM network element provides a network management function, and manages a network between network elements managed by EMs.
With reference to
S1801: An NM network element determines, according to network planning and service planning, a latency condition of a transmission link between an AN-TT and an N3-TT and a feature of a flow obtained after flow aggregation.
For example, the feature of the flow obtained after flow aggregation includes a cycle of the flow, a maximum quantity of data packets transmitted in the cycle, maximum duration of the data packet, and the like.
The network planning means that the NM network element plans data packet processing capabilities and data packet transmission capabilities of the AN-TT, the N3-TT, and a transmission node between the AN-TT and the N3-TT network element, a network topology between the AN-TT and the N3-TT, and the like. The service planning means that the NM network element pre-obtains, in a phase before a network runs a service, a plurality of types of service flows that is to be transmitted between the AN-TT and the N3-TT network element, a latency condition of each type of service flow, a feature (for example, a cycle or sending time) of each type of service flow, and the like, and determines one or more aggregation flows based on the feature of each type of service flow, to subsequently determine a gate control scheduling parameter of a queue corresponding to each aggregation flow.
S1802: The NM network element further obtains processing time information of the AN-TT, port information of the AN-TT, processing time information of a UPF network element, and port information of the N3-TT.
The foregoing information may be configured on the NM network element. Alternatively, in response to a gNB (where the AN-TT is deployed inside the gNB) or the AN-TT (independently deployed) being powered on, the processing time information of the AN-TT and the port information of the AN-TT are reported to the NM network element. Alternatively, in response to the UPF network element being powered on, the processing time information of the UPF network element and the port information of the N3-TT are reported to the NM network element.
S1803: The NM network element determines a minimum offset and a maximum offset based on information obtained in S1801 and S1802. The NM network element may determine the minimum offset and the maximum offset based on the obtained information in a processing manner the same as that of the SMF network element in
S1804: The NM network element sends an identifier of the first service flow, the minimum offset, and the maximum offset to a CNC-TN network element.
S1805: The CNC-TN network element sends the identifier of the first service flow and an offset selection value to the NM network element.
In response to the first service flow being an uplink service flow, interface configuration information includes InterfaceID and the offset selection value. InterfaceID is used to identify a port in the port information of the AN-TT.
In response to the first service flow being a downlink service flow, interface configuration information includes InterfaceID and the offset selection value. InterfaceID is used to identify an interface of the UPF network element or a port in the port information of the N3-TT.
S1806: The NM network element determines a gate control scheduling parameter based on the offset selection value returned by the CNC-TN network element.
S1807A: In response to the first service flow being an uplink service flow, the NM network element sends the gate control scheduling parameter through an EM network element.
S1807B: In response to the first service flow being a downlink service flow, the NM network element sends the gate control scheduling parameter through an EM network element.
According to the foregoing method, the NM network element may first determine the gate control scheduling parameter in advance according to the network planning and service planning, and send the gate control scheduling parameter to the AN-TT or the N3-TT network element, so that a deterministic latency condition of the first service flow can be met, and low-latency transmission between the AN-TT and the N3-TT network element can be implemented.
Optionally, each module in the apparatus 1900 may be implemented by using software.
Optionally, the processing module 1920 may be a processor or a controller, for example, may be a general-purpose central processing unit (central processing unit, CPU), a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or another programmable logic device, a transistor logic device, a hardware component, or any combination thereof. The processing module may implement or execute various example logical blocks, modules, and circuits described with reference to content disclosed in at least one embodiment. The processor may alternatively be a combination of processors implementing a computing function, for example, a combination of one or more microprocessors, or a combination of a DSP and a microprocessor. The transceiver module 1910 may be a communication interface, a transceiver, a transceiver circuit, or the like. The communication interface is a general term. During specific implementation, the communication interface may include a plurality of interfaces, and the storage unit may be a memory.
In response to the apparatus 1900 being a first device or a chip in the first device, the processing module 1920 in the apparatus 1900 may support the apparatus 1900 in performing actions of the first device in the foregoing method examples, for example, may support the apparatus 1900 in performing step 800 and step 810 in
The transceiver module 1910 may support communication between the apparatus 1900 and a second device or a third device. For example, the transceiver module 1910 may support the apparatus 1900 in performing step 820 in
An example is provided below:
In an implementation, the processing module 1920 is configured to determine information about service flow arrival time, where the information about the service flow arrival time includes the service flow arrival time or an offset of the service flow arrival time relative to reference time, the service flow arrival time is time at which a first service flow arrives at the second device, and the first service flow is a periodic service flow to be transmitted by the second device between an access network device and a user plane network element; the processing module 1920 is configured to determine information about service flow sending time based on the information about the service flow arrival time; and the transceiver module 1910 is configured to indicate the second device to wait, after receiving the first service flow, until the service flow sending time to send the first service flow. In response to the first service flow being an uplink service flow, the second device is the access network device or a translator corresponding to the access network device; or in response to the first service flow being a downlink service flow, the second device is the user plane network element.
In at least one embodiment, in response to indicating the second device to wait, after receiving the first service flow, until the service flow sending time to send the first service flow, the transceiver module 1910 is configured to send the information about the service flow sending time to the second device.
In at least one embodiment, the information about the service flow sending time includes the service flow sending time or an offset of the service flow sending time relative to the reference time. The service flow sending time is not later than latest sending time, and the latest sending time is determined based on the information about the service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the latest sending time is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time does not exceed a maximum offset, and the maximum offset is determined based on information about the offset of the service flow arrival time relative to the reference time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the maximum offset is determined based on the information about the offset of the service flow arrival time relative to the reference time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device.
In at least one embodiment, the service flow sending time is not earlier than earliest sending time, and the earliest sending time is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time is greater than or equal to a minimum offset, and the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device.
In at least one embodiment, parameters for determining the latest sending time, the maximum offset, the earliest sending time, or the minimum offset further include a jitter latency associated with the first service flow.
In at least one embodiment, service flow sending time that is determined by the first device and at which the second device sends a second service flow is different from the service flow sending time that is determined by the first device and at which the second device sends the first service flow, the second service flow is a periodic service flow to be transmitted by the second device between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device at the same time, or a difference between time at which the second service flow arrives at the second device and the time at which the first service flow arrives at the second device is less than or equal to a threshold.
In at least one embodiment, in response to determining the information about the service flow sending time based on the information about the service flow arrival time, the processing module 1920 is configured to: obtain an offset selection value, where the offset selection value is greater than or equal to the minimum offset and less than or equal to the maximum offset, or the offset selection value is greater than or equal to an offset of the earliest sending time relative to the reference time and less than or equal to an offset of the latest sending time relative to the reference time; and determine the information about the service flow sending time based on the offset selection value.
In at least one embodiment, the transceiver module 1910 is configured to: send, to a fourth device, the minimum offset and the maximum offset, or the offset of the earliest sending time relative to the reference time and the offset of the latest sending time relative to the reference time; and receive the offset selection value from the fourth device.
In at least one embodiment, the processing module 1920 is further configured to determine, based on a packet delay budget for transmitting the first service flow between the second device and the third device, the processing time of the first service flow in the second device, and processing time of the first service flow in the third device, a latency condition for transmitting the first service flow between the second device and the third device; and the transceiver module 1910 is further configured to send the latency condition to the fourth device. The third device is a device that is to receive the first service flow, and in response to the first service flow being an uplink service flow, the third device is the user plane network element, or in response to the first service flow being a downlink service flow, the third device is the access network device or the translator corresponding to the access network device.
In at least one embodiment, in response to determining the information about the service flow sending time based on the offset selection value, the processing module 1920 is configured to determine the information about the service flow sending time based on the offset selection value and the jitter latency associated with the first service flow.
In at least one embodiment, the information about the service flow sending time includes a gate control scheduling parameter. The processing module 1920 is configured to: obtain the cycle of the first service flow and the maximum burst size of the first service flow; determine a size of a maximum frame of the first service flow based on the maximum burst size of the first service flow; and determine the gate control scheduling parameter based on the cycle of the first service flow, the size of the maximum frame of the first service flow, and the offset selection value.
In at least one embodiment, in response to the second device being the access network device and the third device is the user plane network element, the first service flow arrives at the second device through a terminal device. In response to determining the information about the service flow arrival time, the processing module 1920 is configured to: obtain information about time at which the first service flow arrives at a translator on a terminal device side, residence time of the first service flow in the terminal device and in the translator on the terminal device side, and a packet delay budget for transmitting the first service flow between the terminal device and the second device; and determine the information about the service flow arrival time based on the information about the time at which the first service flow arrives at the translator on the terminal device side, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device.
In at least one embodiment, the first device is a time sensitive networking TSN application function network element. In response to obtaining the information about the time at which the first service flow arrives at the translator on the terminal device side, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device, the processing module 1920 is configured to determine the information about the time at which the first service flow arrives at the translator on the terminal device side. The transceiver unit is configured to receive, from a session management network element, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device.
In at least one embodiment, the first device is a session management network element. In response to the information about the time at which the first service flow arriving at the translator on the terminal device side, the residence time of the first service flow in the terminal device and in the translator on the terminal device side, and the packet delay budget for transmitting the first service flow between the terminal device and the second device are obtained, the transceiver module 1910 is configured to: receive, from a policy control network element, the information about the time at which the first service flow arrives at the translator on the terminal device side; and receive, from the terminal device, the residence time of the first service flow in the terminal device and in the translator on the terminal device side. The processing module 1920 is configured to determine the packet delay budget for transmitting the first service flow between the terminal device and the second device.
The apparatus 1900 in at least one embodiment may correspond to the first device in the foregoing method embodiments, and operations and/or functions of modules in the apparatus 1900 are separately used to implement corresponding steps of the method of the first device in the foregoing method embodiments. Therefore, beneficial effects in the foregoing method embodiments can also be implemented. For brevity, details are not described herein again.
In response to the apparatus 1900 is a second device or a chip in the second device, the processing module 1920 in the apparatus 1900 may support the apparatus 1900 in performing actions of the second device in the foregoing method examples.
The transceiver module 1910 may support communication between the apparatus 1900 and a first device or a third device. For example, the transceiver module 1910 may support the apparatus 1900 in performing step 820 in
For example, in an implementation, the transceiver module 1910 is configured to: receive a first service flow, where the first service flow is a periodic service flow to be transmitted by the second device between an access network device and a user plane network element; and receive, from the first device, information about service flow sending time; and the processing module 1920 is configured to wait until the service flow sending time indicated by the information about the service flow sending time to send the first service flow to the third device. In response to the first service flow being an uplink service flow, the second device is the access network device or a translator corresponding to the access network device; or in response to the first service flow being a downlink service flow, the second device is the user plane network element.
In at least one embodiment, the information about the service flow sending time includes the service flow sending time or an offset of the service flow sending time relative to reference time. The service flow sending time is not later than latest sending time, and the latest sending time is determined based on information about service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the latest sending time is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time does not exceed a maximum offset, and the maximum offset is determined based on information about service flow arrival time, a cycle of the first service flow, and a maximum burst size of the first service flow, and/or the maximum offset is determined based on the information about the service flow arrival time, processing time of the first service flow in the second device, and maximum buffer duration of the first service flow in the second device.
In at least one embodiment, the service flow sending time is not earlier than earliest sending time, and the earliest sending time is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device. Alternatively, the offset of the service flow sending time relative to the reference time is greater than or equal to a minimum offset, and the minimum offset is determined based on the information about the service flow arrival time and the processing time of the first service flow in the second device.
In at least one embodiment, parameters for determining the latest sending time, the maximum offset, the earliest sending time, or the minimum offset further include a jitter latency associated with the first service flow.
In at least one embodiment, service flow sending time at which the second device sends a second service flow is different from the service flow sending time at which the second device sends the first service flow, the second service flow is a periodic service flow to be transmitted by the second device between the access network device and the user plane network element, and the second service flow and the first service flow arrive at the second device at the same time, or a difference between time at which the second service flow arrives at the second device and time at which the first service flow arrives at the second device is less than or equal to a threshold.
In at least one embodiment, the information about the service flow sending time includes a gate control scheduling parameter.
In at least one embodiment, the first device is a TSN application function network element, or the first device is a session management network element.
The apparatus 1900 in at least one embodiment may correspond to the second device in the foregoing method embodiments, and operations and/or functions of modules in the apparatus 1900 are separately used to implement corresponding steps of the method of the second device in the foregoing method embodiments. Therefore, beneficial effects in the foregoing method embodiments can also be implemented. For brevity, details are not described herein again.
In response to the apparatus 2000 being a first device or a chip in the first device, in at least one embodiment, the processor 2001 is configured to invoke an interface to perform the following actions:
The apparatus 2000 may be further configured to perform other steps and/or operations on a first device side in the foregoing embodiments. For brevity, details are not described herein.
In response to the apparatus 2000 being a second device or a chip in the second device, in at least one embodiment, the processor 2001 is configured to invoke an interface to perform the following actions:
The apparatus 2000 may be further configured to perform other steps and/or operations on a second device side in the foregoing embodiments. For brevity, details are not described herein.
The processor 2001 may invoke the interface to perform the foregoing receiving and sending actions. The invoked interface may be a logical interface or a physical interface. This is not limited. Optionally, the physical interface may be implemented by using a transceiver. Optionally, the apparatus 2000 further includes a transceiver 2003.
Optionally, the apparatus 2000 further includes a memory 2002, and the memory 2002 may store program code in the foregoing method embodiments, so that the processor 2001 invokes the program code.
Specifically, in response to the apparatus 2000 including the processor 2001, the memory 2002, and the transceiver 2003, the processor 2001, the memory 2002, and the transceiver 2003 communicate with each other through internal connection paths, to transfer a control signal and/or a data signal. In at least one embodiment, the processor 2001, the memory 2002, and the transceiver 2003 may be implemented by using a chip. The processor 2001, the memory 2002, and the transceiver 2003 may be implemented in a same chip, or may be implemented in different chips, or any two functions of the processor 2001, the memory 2002, and the transceiver 2003 are combined and implemented in one chip. The memory 2002 may store program code, and the processor 2001 invokes the program code stored in the memory 2002, to implement a corresponding function of the apparatus 2000.
The methods disclosed in at least one embodiment may be applied to a processor or may be implemented by a processor. The processor may be an integrated circuit chip with a signal processing capability. In an implementation process, steps in the foregoing method embodiments can be implemented by using a hardware integrated logical circuit in the processor, or by using instructions in a form of software. The processor may be a general-purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (application-specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, or may be a system on chip (system on chip, SoC), or may be a central processing unit (central processing unit, CPU), or may be a network processor (network processor, NP), or may be a digital signal processing circuit (digital signal processor, DSP), or may be a micro controller (micro controller unit, MCU), or may be a programmable controller (programmable logic device, PLD) or another integrated chip. The processor may implement or perform the methods, steps, and logical block diagrams that are disclosed in at least one embodiment. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the methods disclosed with reference to at least one embodiment may be directly performed and completed by a hardware decoding processor, or may be performed and completed by using a combination of hardware in the decoding processor and a software module. The software module may be located in a mature storage medium in the art, for example, a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in a memory, and the processor reads information in the memory and completes the steps of the methods in combination with hardware of the processor.
The memory in at least one embodiment may be a volatile memory or a nonvolatile memory, or may include a volatile memory and a nonvolatile memory. The nonvolatile memory may be a read-only memory (read-only memory, ROM), a programmable read-only memory (programmable ROM, PROM), an erasable programmable read-only memory (erasable PROM, EPROM), an electrically erasable programmable read-only memory (electrically EPROM, EEPROM), or a flash memory. The volatile memory may be a random access memory (random access memory, RAM) and is used as an external cache. By way of example, and not limitation, RAMs in many forms may be used, for example, a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), a synchronous dynamic random access memory (synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (synchlink DRAM, SLDRAM), and a direct rambus random access memory (direct rambus RAM, DR RAM). The memory of the systems and methods described in at least one embodiment includes but is not limited to these and any memory of another proper type.
In at least one embodiment, numbers “first”, “second”, and the like are merely intended to distinguish between different objects, for example, to distinguish between different parameter information or messages, and do not constitute a limitation on the scope of at least one embodiment. At least one embodiment is not limited thereto.
Sequence numbers of the foregoing processes do not mean execution sequences in at least one embodiment. The execution sequences of the processes should be determined based on functions and internal logic of the processes. Numbers or sequence numbers in the foregoing processes are merely for differentiation for ease of description, and should not constitute any limitation on an implementation process of at least one embodiment.
The term “and/or” in at least one embodiment describes only an association relationship between associated objects and represents that three relationships may exist. For example, A and/or B may represent the following three cases: Only A exists, both A and B exist, and only B exists. In addition, the character “/” in at least one embodiment generally indicates an “or” relationship between the associated objects.
Unless otherwise specified, an expression used in embodiments described herein similar to an expression that “an item includes one or more of the following: A, B, and C” usually means that the item may be any one of the following: A; B; C; A and B; A and C; B and C; A, B, and C; A and A; A, A, and A; A, A, and B; A, A, and C; A, B, and B; A, C, and C; B and B; B, B, and B; B, B, and C; C and C; C, C, and C; and another combination of A, B, and C. In the foregoing descriptions, three elements A, B, and C are used as an example to describe an optional case of the item. In response to an expression being “an item includes at least one of the following: A, B, . . . , and X”, in other words, more elements are included in the expression, a case to which the item is applicable may also be obtained according to the foregoing rule.
A person of ordinary skill in the art may be aware that, in combination with the examples described in at least one embodiment, units and algorithm steps can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether the functions are performed by hardware or software depends on particular applications and design constraints of the technical solutions. A person skilled in the art may use different methods to implement the described functions for each particular application, but the implementation is not considered to go beyond the scope of at least one embodiment.
A person skilled in the art understands that, for the purpose of convenient and brief description, for a detailed working process of the foregoing system, apparatus, and unit, refer to a corresponding process in the foregoing method embodiments. Details are not described herein again.
In embodiments described herein, the disclosed system, apparatus, and method may be implemented in other manners. For example, the described apparatus embodiments are merely examples. For example, division into the units is merely logical function division and may be other division during actual implementation. For example, a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed. In addition, the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented through some interfaces. The indirect couplings or communication connections between the apparatuses or units may be implemented in electrical, mechanical, or other forms.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, that is, may be located at one position, or may be distributed on a plurality of network units. Some or all of the units may be selected based on actual conditions to achieve the objectives of the solutions of embodiments.
In addition, functional units in at least one embodiment may be integrated into one processing unit, each of the units may exist alone physically, or two or more units may be integrated into one unit.
In response to the functions being implemented in a form of a software functional unit and sold or used as an independent product, the functions may be stored in a computer-readable storage medium. Based on such an understanding, the technical solutions of at least one embodiment essentially, or the part contributing to the current technology, or some of the technical solutions may be implemented in a form of a software product. The computer software product is stored in a storage medium, and includes several instructions for instructing a computer device (which may be a personal computer, a server, a network device, or the like) to perform all or some of the steps of the methods described in at least one embodiment. The foregoing storage medium includes any medium that can store program code, for example, a USB flash drive, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or a compact disc.
Number | Date | Country | Kind |
---|---|---|---|
202111468102.2 | Dec 2021 | CN | national |
This application is a continuation of International Application No. PCT/CN2022/134027, filed on Nov. 24, 2022, which claims priority to Chinese Patent Application No. 202111468102.2, filed on Dec. 3, 2021. The disclosures of the aforementioned applications are hereby incorporated by reference in their entireties.
Number | Date | Country | |
---|---|---|---|
Parent | PCT/CN2022/134027 | Nov 2022 | WO |
Child | 18679723 | US |