WO2021067130A1 - Methods and apparatuses for determining 5g system (5gs) delays for time sensitive communications (tsc) - Google Patents

Abstract

Systems, methods, apparatuses, and computer program products for determining 5G system (5GS) delays for time sensitive communications (TSC) are provided. One method may include obtaining at least one of mobility constraint information for a user equipment (UE) and path delay for each network node in a mobility area of the UE, and determining an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the UE. The method may further include selecting a 5G quality of service (QoS) identifier (5QI) that supports an actual PDB that accommodates the determined achievable PDB, and determining a 5G system (5GS) delay based at least on the actual PDB determined from the achievable PDB.

Description

METHODS AND APPARATUSES FOR DETERMINING 5G SYSTEM (5GS) DELAYS FOR TIME SENSITIVE COMMUNICATIONS (TSC)

CROSS-REFERENCE TO RELATED APPLICATIONS:

[0001] This application claims priority from U.S. provisional patent application no. 62/909,393 filed on October 2, 2019. The contents of this earlier filed application are hereby incorporated by reference in their entirety.

FIELD:

[0002] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or fifth generation (5G) radio access technology or new radio (NR) access technology, or other communications systems. For example, certain embodiments may relate to systems and/or methods for determining 5G system (5GS) delays for time sensitive communications (TSC). BACKGROUND:

[0003] Examples of mobile or wireless telecommunication systems may include the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), Long Term Evolution (LTE) Evolved UTRAN (E-UTRAN), LTE- Advanced (LTE- A), MulteFire, LTE-A Pro, and/or fifth generation (5G) radio access technology or new radio (NR) access technology. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G is mostly built on a new radio (NR), but a 5G (or NG) network can also build on E-UTRA radio. It is estimated that NR provides bitrates on the order of 10-20 Gbit/s or higher, and can support at least enhanced mobile broadband (eMBB) and ultra reliable low-latency-communication (URLLC) as well as massive machine type communication (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low latency connectivity and massive networking to support the Internet of Things (IoT). With IoT and machine-to-machine (M2M) communication becoming more widespread, there will be a growing need for networks that meet the needs of lower power, low data rate, and long battery life. The next generation radio access network (NG-RAN) represents the RAN for 5G, which can provide both NR and LTE radio access. It is noted that, in 5G, the nodes that can provide radio access functionality to a user equipment (i.e., similar to Node B in UTRAN or eNB in LTE) may be named gNB when built on NR radio and may be named NG-eNB when built on E-UTRA radio.

SUMMARY:

[0004] One embodiment may be directed to a method that may include obtaining at least one of mobility constraint information for a UE and path delay for each network node in a mobility area of the UE, determining an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the UE, selecting a 5G quality of service (QoS) identifier (5QI) that supports an actual PDB that accommodates the determined achievable PDB, and determining a 5G system (5GS) delay based at least on the actual PDB determined from the achievable PDB.

[0005] Another embodiment may be directed to an apparatus that may include at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to obtain at least one of mobility constraint information for a UE and path delay for each network node in a mobility area of the UE, determine an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the UE, select a 5G quality of service (QoS) identifier (5QI) that supports an actual PDB that accommodates the determined achievable PDB, and determine a 5G system (5GS) delay based at least on the actual PDB determined from the achievable PDB. [0006] Another embodiment may be directed to an apparatus that may include means for obtaining at least one of mobility constraint information for a UE and path delay for each network node in a mobility area of the UE, means for determining an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the UE, means for selecting a 5G quality of service (QoS) identifier (5QI) that supports an actual PDB that accommodates the determined achievable PDB, and means for determining a 5G system (5GS) delay based at least on the actual PDB determined from the achievable PDB.

[0007] Another embodiment may be directed to a computer readable medium comprising program instructions stored thereon for performing at least the following: obtaining at least one of mobility constraint information for a UE and path delay for each network node in a mobility area of the UE, determining an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the UE, selecting a 5G quality of service (QoS) identifier (5QI) that supports an actual PDB that accommodates the determined achievable PDB, and determining a 5G system (5GS) delay based at least on the actual PDB determined from the achievable PDB.

BRIEF DESCRIPTION OF THE DRAWINGS:

[0008] For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0009] Fig. 1 illustrates an example system architecture diagram with 5GS appearing as time sensitive networking (TSN) bridge;

[0010] Fig. 2 illustrates an example signaling diagram, according to an embodiment;

[0011] Fig. 3 illustrates an example system diagram of UEs with varying mobility, according to an embodiment; [0012] Fig. 4 illustrates an example table of PDB for UEs with high and low mobility, according to an embodiment;

[0013] Fig. 5 illustrates an example flow diagram of a method, according to an embodiment; and

[0014] Fig. 6 illustrates an example block diagram of an apparatus, according to an embodiment.

DETAILED DESCRIPTION:

[0015] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for determining 5G system (5GS) delays for time sensitive communications (TSC), is not intended to limit the scope of certain embodiments but is representative of selected example embodiments.

[0016] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “certain embodiments,” “some embodiments,” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Thus, appearances of the phrases “in certain embodiments,” “in some embodiments,” “in other embodiments,” or other similar language, throughout this specification do not necessarily all refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments. [0017] Additionally, if desired, the different functions or procedures discussed below may be performed in a different order and/or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the following description should be considered as merely illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

[0018] Time Sensitive Communications (TSC) is a type of communication service that supports deterministic communication and/or isochronous communication with high reliability and availability. TSC may provide packet transport with QoS characteristics such as bounds on latency, loss and reliability, where end systems and relay/transmit nodes can be strictly synchronized. As such, TSC can support applications requiring the involved end devices (e.g., UEs, IoT devices, etc.) to be strictly synchronised with each other, for example in the order of 10ps or lps. Some example use cases where TSC may be applicable include, but are not limited to, factory automation, robotic arm control, smart grid controls, etc. One of the standards to support TSC is called Time Sensitive Network (TSN) and is specified in a set of standards by IEEE (e.g., IEEE 802.1Qcc, IEEE 802.1Qbv, 802. IAS). These standards are based on wired Ethernet as a transport layer; however due to ease of deployment, operation and potential cost reductions, there is a willingness from industries using those standards to move to wireless based technology. 5G is seen as a standard that can be fit to meet very stringent requirements in terms of both latency and reliability as well as highly precise synchronization accuracy of the applications running over TSN networks. As such, the 3^rd generation partnership project (3 GPP) began work on enhancements for 5G/NR system to support TSN networks. As a result, there is a need for supporting industrial networks that have unique requirements for low latency deterministic data transmission and high reliability is a current priority. [0019] To support deterministic TSN in bridged networks, IEEE has defined a suite of protocols to allow synchronization of bridges to Grand Master clocks (IEEE1588, 802. IAS), link layer discovery (LLDP / 802.1AB), provisioning of streams (802.1Qcc), frame replication and elimination for reliability (FRER - 802.1CB), and enhancements for scheduled traffic (802.1Qbv) whereby gate schedules along the path between TSN endpoints can be provisioned. These and other IEEE protocols enable very low latency transmission of periodic, deterministic traffic between connected endpoints (a talker and listeners) via Ethernet bridges. Gate schedules can be precisely synchronized at each bridge in the network between a talker and listeners so traffic bursts are transmitted without contention at bridge ports. Some example applications may include industrial automation with stringent delay requirements, such as real-time motion control where a feedback loop provides sensor information from a robot and a controller commands some action(s).

[0020] Fig. 1 illustrates an example system architecture in which a 5GS appears as a TSN bridge 101. As illustrated in the example of Fig. 1, the 5GS is integrated transparently as a bridge into the TSN network, with a TSN Translator (TT) in the UE (DS-TT) 104 and a TSN Translator (NW- TT) 105 in user plane function (UPF) 100.

[0021] The translators and the TSN-application function (AF) 111 provide interoperability between IEEE TSN network bridges (where the IEEE protocols mentioned above prevail) and the 5G core network (5GC), radio access network (RAN) and UE (where 3GPP protocols are applicable). In this manner, 3GPP procedures can be hidden from connected TSN networks. The TTs 104, 105 allow the 5GS bridge 101 to appear transparently as ports in the user plane, and the TSN AF 111 allows the 5GS bridge 101 to be configured as a bridge by the management plane/control plane, just like other TSN Bridges. [0022] The configuration of the 5GS bridge 101 may include the 5GS bridge 101 running link layer discovery protocol (LLDP) for UE 103 and UPF 100 ports so the network topology is known, and determining the bridge delay. For the 5GS bridge 101, this is the delay between the (UE/DS-TT, UPF/NW-TT) port pair. Since UE mobility is transparent to the IEEE network (the UE bridge port physically moves, but the bridged network is not affected) the reported delay must be sufficient to accommodate the maximum delay for all N3 paths between possible gNBs and the UPF 100, and within the RAN 107 on Fl-U/Xn-U paths.

[0023] The delay may be determined when the UE 103 establishes a protocol data unit (PDU) session, which occurs when the UE 103 sends a request containing a data network name (DNN) and network slice selection assistance information (NSSAI). Typically, the DNN is used by the session management function (SMF) to select the appropriate UPF, and the NSSAI (which may indicate that URLLC is required) may be used by a policy control function (PCF) to choose a 5G quality of service (QoS) identifier (5QI) with a fixed packet delay budget (PDB). The fixed PDB may be combined with a UE residence time to determine the bridge delay.

[0024] Bridge delays and network topology may be reported to a central network configuration (CNC) entity. This includes 5GS bridges and wired bridges. The CNC may determine egress gate schedules at each bridge between the talker and listener, including 5GS bridges. In 5GS Bridges, 5G QoS is used with a 5QI that supports the delay required for the Gate Schedule.

[0025] Prior to 3GPP Release- 16, a PDB, which may be associated with the QoS profile, had been defined to indicate the time that a packet may be delayed between the UE and the UPF that terminates the N6 interface. A static portion of the PDB was allocated as the Core Network PDB (CN PDB), which represents the delay between any UPF terminating N6 (that may possibly be selected for the PDU Session) and any gNB in the 5G-AN. The portion of the PDB that applied to the radio interface was determined by subtracting the static CN PDB from the PDB.

[0026] For 3GPP Release- 16, it was recognized that paths between a UPF and different gNBs may have different delays, for example due to the topology of the transport network between gNBs and a UPF, which can range from a direct fiber connection to many hops through bridges or routers. To provide greater flexibility for RAN scheduling, 3GPP defined “dynamic values for” CN PDBs. This means that a CN PDB can be specified individually for each (gNB, UPF) pair. Since AN PDB = PDB - CN PDB, this gave gNBs with smaller N3 network delays additional time to transmit a delay critical guaranteed bit rate (GBR) packet to a UE.

[0027] Furthermore, in Release- 16, QoS monitoring to assist URLLC service was defined (see 3GPP TS 23.501, section 5.33.3). The monitoring provides packet delay measurements between the UE and the PDU session anchor. One of the options provides General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTP-U) path monitoring using GTP-U echo request/response messages between a UPF and the RAN. Hence, measured values of the core network delay between the UPF and RAN may be obtained from QoS monitoring results.

[0028] For delay critical deterministic applications, such as motion control, that require isochronous gate schedules at bridge egress ports, it is important that latency within the 5GS bridge be minimized so the overall latency on the path between talker and listener is also minimized. Different robots and their associated UEs can have different levels of mobility within a factory. For example, some UEs/robots will stay within the coverage of one gNB, while others may be more mobile and move about an entire factory. In the former case, a UPF may have a direct fiber connection with the gNB serving the UE, in which case the delay on N3 will be negligible. In the latter case where UEs are more mobile, a N3 network spanning the factory may be needed to connect gNBs to a UPF, in which case several bridge/router hops may be required for some gNBs and the maximum delay for all N3 paths may be significant. These delays can be significant for industrial motion control applications. The same type of path variation can occur within the RAN on Fl-U/Xn-U.

[0029] However, when the 5GS bridge delay is determined at PDU session setup (as described above), the PCF does not consider the UE mobility range. Similarly, the UE’s mobility range is not considered when determining the bridge delay sent to the CNC. Hence, the bridge delay, which is determined as discussed above, must accommodate the longest path between a gNB and the UPF, and the longest path within the RAN, even if a particular UE will never receive service via the most distant gNB because of mobility restrictions. This unnecessarily increases the 5GS bridge delay for robots/UEs with limited mobility. As one example, if 7 bridge hops in a 100 Mbps Ethernet network are needed to connect the most distant gNB to the UPF, approximately 1 millisecond of unnecessary delay will be added to the 5GS bridge delay for a UE that receives service only via a gNB directly connected by fiber to the UPF.

[0030] Example embodiments described herein are able to address and overcome at least the problem(s) outlined in the foregoing.

[0031] Certain embodiments can reduce the delay of a 5GS TSN Bridge, for example, for UEs/robots with limited mobility while engaged in TSC transactions because the delay is determined considering only the subset of N3 and/or RAN (Fl-U/Xn-U) network paths needed to serve the UE within its mobility area. Some embodiments may accomplish this by using UE mobility constraints known to the network to select a limited set of wired network path delays applicable for the UE. The limited set of delays may then be used to determine an achievable PDB and to select a 5QI for QoS. The actual PDB associated with the 5QI may then be used to calculate 5GS bridge delay. [0032] According to certain embodiments, the UE mobility constraints may be mobility restriction information, including closed access group (CAG) and service area restrictions already defined by 3GPP (e.g., see 3GPP TS 23.501, section 5.3.4.1), or it may be a restricted area defined specifically for TSC UEs. For example, a restricted area for TSC purposes may be defined by a list of gNBs provisioned in the unified data management (UDM).

[0033] In an embodiment, in order to determine the achievable PDB over the subset of N3 and/or RAN paths that will be used by a UE, the 5GC may make use of UE mobility constraints and one or both of: (1) per (UPF, NG- RAN node) dynamic values of CN PDB information, and/or (2) URLLC QoS monitoring information. The achievable PDB may be determined using the maximum delay over the subset of N3 and/or RAN paths. That achievable PDB may then be used to select the 5QI (with its associated actual PDB). Next, the actual PDB may be used to determine the 5GS bridge delay (e.g., as described in 5.27.5 of 3GPP TS23.501).

[0034] Fig. 2 illustrates an example signaling diagram, according to certain embodiments. As illustrated in the example of Fig. 2, at 1, UE mobility constraint information and path delay may be obtained for each gNB in the mobility area. In an embodiment, mobility constraint information may come from 3 GPP defined mobility restrictions or may be provisioned (e.g., in the UDM) for TSC. According to one embodiment, the path delay may comprise N3 paths and/or RAN paths. In certain embodiments, the N3 path delay may be obtained from dynamic values of CN PDB provisioned in RAN or UPF, or may be obtained from URLLC QoS monitoring information. According to some embodiments, RAN path delay (which may include Fl-U and/or Xn-U) may be obtained from URLLC QoS monitoring. It is noted that this RAN path delay may also include Uu delay. Delays and mobility constraints may alternatively be obtained from other sources. [0035] Continuing with the example of Fig. 2, at 2, it may be determined, for the selected UPF, the achievable PDB. The achievable PDB may include the maximum path delay (max(Path Delay)) over the constrained UE mobility area. In an embodiment, at 3, a 5QI with an actual PDB that accommodates the achievable PDB may be selected or determined. According to certain embodiments, the 5QI is selected so that the actual PDB >= the achievable PDB. Then, at 4, the 5GS bridge delay may be determined based on the actual PDB determined from the achievable PDB. It is noted that, in an embodiment, the 5GS bridge delay may be determined from the UE residence time and the PDB. In one example, the determined 5GS bridge delay may be transmitted to the CNC, which determines bridge schedules.

[0036] Fig. 3 illustrates an example system including UEs with local and factory wide mobility, according to an example embodiment. More specifically, the example of Fig. 3 depicts a factory network with four gNBs (gNB-1, gNB-2, gNB-3, gNB-4) connected to a UPF (UPF1) via an N3 network, and two UEs/robots (UE-1 and UE-2). In this example, UE-1 has limited mobility and therefore is served only by gNB-1, which has a fiber connection to UPF1. UE-2 is mobile throughout the factory and therefore as many as four bridge hops may be required to connect the serving gNB to the UPF1. According to an embodiment, the 5GS bridge delay reported to the CNC for UE-1 reflects the N3 delay between only gNB-1 and UPF1, while the 5GS bridge delay reported for UE-2 reflects the worst case N3 path (via gNB-4 and the three bridges having four bridge hops). In each case, the 5GC may calculate the achievable PDB based on the maximum N3 path delay over the UE mobility range. The achievable PDB may then be used in selecting a 5QI with an appropriate actual PDB, and the actual PDB can be used to determine the 5GS bridge delay.

[0037] It is noted that Fig. 3 depicts one example for purposes of illustration and embodiments are not just limited to this example. For instance, example embodiments are not merely limited to the number of gNBs, UEs, and/or bridges depicted in Fig. 3; indeed, any number of network nodes may be included according to certain embodiments. It should therefore be understood that other examples are possible, according to further embodiments.

[0038] Fig. 4 illustrates an example table depicting PDB for UEs with high and low mobility, such as UE-1 and UE-2 depicted in Fig. 3. In an embodiment, according to the example shown in Fig. 4, UE-1 and UE-2 may use identical QoS, except the UE-1 5QI has a PDB of 7 while the UE-2 5QI has a PDB of 10. It is noted that the PDB units used here are arbitrary - one unit, which corresponds to one bridge hop may be approximately -0.14 msec @100 Mbps. Different 5GS bridge delays are possible because different achievable PDBs were used to determine the 5GS bridge delays for UE-1 and UE-2, as illustrated in Fig. 4.

[0039] Fig. 5 illustrates an example flow diagram of a method for determining 5GS delays for TSC, according to one example embodiment. In certain example embodiments, the flow diagram of Fig. 5 may be performed by a network entity or network node in a 3GPP system, such as a 5G-AN or 5GC in the 5GS. For instance, in some example embodiments, the method of Fig. 5 may be performed by a core network node in a 5GS, such as a PCF or UPF, and/or TSN bridge.

[0040] As illustrated in the example of Fig. 5, the method may include, at 500, obtaining or receiving mobility constraint information for a UE and/or path delay for each network node (e.g., gNB) in a mobility area of the UE. According to certain embodiments, the UE mobility constraints may include mobility restriction information including CAG and/or service area restrictions and/or may include a restricted area defined for TSC UEs.

[0041] In an embodiment, the obtaining 500 may include obtaining the mobility constraint information from pre-defined mobility restrictions, or the mobility constraint information may be provisioned (e.g., in the UDM) for TSC. According to one embodiment, the path delay may comprise N3 path delay and/or RAN path delay. In certain embodiments, the N3 path delay may be obtained from dynamic values of CN PDB provisioned in RAN or UPF, or may be obtained from URLLC QoS monitoring information. According to some embodiments, RAN path delay (which may include Fl-U and/or Xn-U) may be obtained from URLLC QoS monitoring information. The RAN path delay may also include Uu delay.

[0042] As further illustrated in the example of Fig. 5, the method may also include, at 510, determining the achievable PDB, which may include the maximum path delay over the mobility area of the UE. In an embodiment, the method may then include, at 520, selecting a 5QI having an actual PDB that accommodates the determined achievable PDB. According to certain embodiments, the 5QI is selected so that the actual PDB >= the achievable PDB. In other words, a 5QI having an actual PDB accommodating the achievable PDB is one where the actual PDB >= the achievable PDB. In an embodiment, the method may further include, at 530, determining a 5GS delay based at least on the actual PDB determined from the achievable PDB. In some embodiments, the determining 530 may include determining the 5GS delay from a residence time of the UE, as well as the actual PDB. In one example, the method may also include, at 540, transmitting the determined 5GS delay to a CNC, which determines bridge schedules.

[0043] In certain embodiments, the 5GS may be integrated with the external network as a TSN bridge, and the 5GS delay may be a 5GS TSN bridge delay.

[0044] Fig. 6 illustrates an example of an apparatus 10 according to an embodiment. In an embodiment, apparatus 10 may be a node, host, or server in a communications network or serving such a network. For example, apparatus 10 may be or may include a core network node in 5 G or NR, such as a UPF and/or TSN bridge. [0045] As illustrated in the example of Fig. 6, apparatus 10 may include a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general or specific purpose processor. In fact, processor 12 may include one or more of general-purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application- specific integrated circuits (ASICs), and processors based on a multi-core processor architecture, as examples. While a single processor 12 is shown in Fig. 6, multiple processors may be utilized according to other embodiments. For example, it should be understood that, in certain embodiments, apparatus 10 may include two or more processors that may form a multiprocessor system (e.g., in this case processor 12 may represent a multiprocessor) that may support multiprocessing. In certain embodiments, the multiprocessor system may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0046] Processor 12 may perform functions associated with the operation of apparatus 10, which may include, for example, precoding of antenna gain/phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of the apparatus 10, including processes related to management of communication resources. Additionally, Processor 12 may perform functions associated with the operation of apparatus 10, which may include signaling amongst core network functions, computations and other processing in a core network, including that associated with a 5GC PCF, SMF, AMF and UPF. The functions may be further associated with network control plane elements such as those of a CNC.

[0047] Apparatus 10 may further include or be coupled to a memory 14 (internal or external), which may be coupled to processor 12, for storing information and instructions that may be executed by processor 12. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor- based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and/or removable memory. For example, memory 14 can be comprised of any combination of random access memory (RAM), read only memory (ROM), static storage such as a magnetic or optical disk, hard disk drive (HDD), or any other type of non- transitory machine or computer readable media. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable the apparatus 10 to perform tasks as described herein.

[0048] In an embodiment, apparatus 10 may further include or be coupled to (internal or external) a drive or port that is configured to accept and read an external computer readable storage medium, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium may store a computer program or software for execution by processor 12 and/or apparatus 10.

[0049] In some embodiments, apparatus 10 may also include or be coupled to one or more antennas 15 for transmitting and receiving signals and/or data to and from apparatus 10. Apparatus 10 may further include or be coupled to a transceiver 18 configured to transmit and receive information. The transceiver 18 may include, for example, a plurality of radio interfaces that may be coupled to the antenna(s) 15. The radio interfaces may correspond to a plurality of radio access technologies including one or more of GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT- LE, NFC, radio frequency identifier (RFID), ultrawideband (UWB), MulteFire, and the like. The radio interface may include components, such as filters, converters (for example, digital-to-analog converters and the like), mappers, a Fast Fourier Transform (FFT) module, and the like, to generate symbols for a transmission via one or more downlinks and to receive symbols (for example, via an uplink).

[0050] As such, transceiver 18 may be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and demodulate information received via the antenna(s) 15 for further processing by other elements of apparatus 10. In other embodiments, transceiver 18 may be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some embodiments, apparatus 10 may include an input and/or output device (I/O device).

[0051] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. The modules may include, for example, an operating system that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0052] According to some embodiments, processor 12 and memory 14 may be included in or may form a part of processing circuitry or control circuitry. In addition, in some embodiments, transceiver 18 may be included in or may form a part of transceiving circuitry.

[0053] As used herein, the term “circuitry” may refer to hardware-only circuitry implementations (e.g., analog and/or digital circuitry), combinations of hardware circuits and software, combinations of analog and/or digital hardware circuits with software/firmware, any portions of hardware processor(s) with software (including digital signal processors) that work together to case an apparatus (e.g., apparatus 10) to perform various functions, and/or hardware circuit(s) and/or processor(s), or portions thereof, that use software for operation but where the software may not be present when it is not needed for operation. As a further example, as used herein, the term “circuitry” may also cover an implementation of merely a hardware circuit or processor (or multiple processors), or portion of a hardware circuit or processor, and its accompanying software and/or firmware. The term circuitry may also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0054] As introduced above, in certain embodiments, apparatus 10 may be a network node, RAN node, such as a 5GS core network node, or the like. In one example embodiment, apparatus 10 may be a PCF, UPF or TSN bridge, for example. In some embodiments, apparatus 10 may be a CNC. According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to perform the functions associated with any of the embodiments described herein. For example, in some embodiments, apparatus 10 may be configured to perform one or more of the processes depicted in any of the flow charts or signaling diagrams described herein, such as the signaling diagram illustrated in Fig. 2 or the flow diagram of Fig. 5. In some embodiments, apparatus 10 may correspond to the 5GC depicted in Fig. 2 or UPF1 depicted in Fig. 3. For instance, in certain embodiments, apparatus 10 may be configured to perform a procedure for determining 5GS delays for TSC.

[0055] In one embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to obtain or receive mobility constraint information for a UE and/or path delay for each network node (e.g., gNB) in a mobility area of the UE. According to certain embodiments, the UE mobility constraints may include mobility restriction information including CAG and/or service area restrictions and/or may include a restricted area defined for TSC UEs.

[0056] In an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to obtain the mobility constraint information from pre defined mobility restrictions, or the mobility constraint information may be provisioned (e.g., in the UDM) for TSC. According to one embodiment, the path delay may comprise N3 path delay and/or RAN path delay. In certain embodiments, the N3 path delay may be obtained from dynamic values of CN PDB provisioned in RAN or UPF, or may be obtained from URLLC QoS monitoring information. According to some embodiments, RAN path delay (which may include Fl-U and/or Xn-U) may be obtained from URLLC QoS monitoring information. The RAN path delay may also include Uu delay.

[0057] In certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to determine the achievable PDB, which may include the maximum path delay over the mobility area of the UE. In an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to select a 5QI having an actual PDB that accommodates the determined achievable PDB. According to certain embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to select the 5QI such that the actual PDB >= the achievable PDB. In an embodiment, apparatus 10 may be controlled by memory 14 and processor 12 to determine a 5GS delay based at least on the actual PDB determined from the achievable PDB. In some embodiments, apparatus 10 may be controlled by memory 14 and processor 12 to determine the 5GS delay from a residence time of the UE, as well as the actual PDB. In one example, apparatus 10 may be further controlled by memory 14 and processor 12 to transmit the determined 5GS bridge delay to the CNC, which determines bridge schedules. According to certain embodiments, the 5GS may be integrated with the external network as a TSN bridge, and the 5GS delay determined by apparatus 10 may be a 5GS TSN bridge delay.

[0058] Therefore, certain example embodiments provide several technological improvements, enhancements, and/or advantages over existing technological processes and constitute an improvement at least to the technological field of wireless network control and management. For example, certain embodiments provide methods to support deterministic QoS in a 5GS TSN bridge. In particular, some embodiments reduce the delay of a 5GS TSN bridge for UEs, such as UEs/robots with limited mobility. Accordingly, the use of certain example embodiments results in improved functioning of communications networks and their nodes, such as base stations, NG-RAN nodes, eNBs, gNBs, and/or UEs or mobile stations.

[0059] In some example embodiments, the functionality of any of the methods, processes, signaling diagrams, algorithms or flow charts described herein may be implemented by software and/or computer program code or portions of code stored in memory or other computer readable or tangible media, and executed by a processor.

[0060] In some example embodiments, an apparatus may be included or be associated with at least one software application, module, unit or entity configured as arithmetic operation(s), or as a program or portions of it (including an added or updated software routine), executed by at least one operation processor. Programs, also called program products or computer programs, including software routines, applets and macros, may be stored in any apparatus-readable data storage medium and may include program instructions to perform particular tasks.

[0061] A computer program product may include one or more computer- executable components which, when the program is run, are configured to carry out some example embodiments. The one or more computer-executable components may be at least one software code or portions of code. Modifications and configurations required for implementing functionality of an example embodiment may be performed as routine(s), which may be implemented as added or updated software routine(s). In one example, software routine(s) may be downloaded into the apparatus.

[0062] As an example, software or computer program code or portions of code may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers may include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and/or software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers. The computer readable medium or computer readable storage medium may be a non-transitory medium. [0063] In other example embodiments, the functionality may be performed by hardware or circuitry included in an apparatus (e.g., apparatus 10), for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software. In yet another example embodiment, the functionality may be implemented as a signal, such as a non-tangible means, that can be carried by an electromagnetic signal downloaded from the Internet or other network.

[0064] According to an example embodiment, an apparatus, such as a node, device, or a corresponding component, may be configured as circuitry, a computer or a microprocessor, such as single-chip computer element, or as a chipset, which may include at least a memory for providing storage capacity used for arithmetic operation(s) and/or an operation processor for executing the arithmetic operation(s).

[0065] A first embodiment is directed to a method, which may include obtaining at least one of mobility constraint information for a user equipment (UE) and path delay for each network node in a mobility area of the user equipment (UE), determining an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the user equipment (UE), selecting a 5G quality of service (QoS) identifier (5QI) having an actual packet delay budget (PDB) that accommodates the determined achievable packet delay budget (PDB), and determining a 5G system (5GS) delay based at least on the actual packet delay budget (PDB) determined from the achievable packet delay budget (PDB).

[0066] According to a variant, the mobility constraints may include at least one of: mobility restriction information including closed access group (CAG) or service area restrictions, or a restricted area defined for time sensitive communications (TSC) user equipment (UEs).

[0067] In some variants, the obtaining may comprise obtaining the mobility constraint information from pre-defined mobility restrictions, or the mobility constraint information may be provisioned for time sensitive communications (TSC).

[0068] According to a variant, the path delay may comprise at least one of N3 path delay or radio access network (RAN) path delay.

[0069] In some variants, the N3 path delay may be obtained from dynamic values of core network (CN) packet delay budget (PDB) provisioned in radio access network (RAN) or user plane function (UPF), or the N3 path delay may be obtained from ultra-reliable low-latency-communication (URLLC) quality of service (QoS) monitoring information.

[0070] According to a variant, the radio access network (RAN) path delay may be obtained from ultra-reliable low-latency-communication (URLLC) quality of service (QoS) monitoring information.

[0071] In a variant, the selecting may include selecting the 5G quality of service (QoS) identifier (5QI) so that the actual packet delay budget (PDB) is greater than or equal to the achievable packet delay budget (PDB).

[0072] According to a variant, the determining of the 5G system (5GS) delay may further comprise determining the 5GS delay from a residence time of the user equipment (UE).

[0073] In a variant, the 5G system (5GS) may be integrated with the external network as a TSN bridge, and the 5G system (5GS) delay may comprise a 5GS TSN bridge delay. [0074] According to a variant, the method may further comprise transmitting the determined 5G system (5GS) bridge delay to a central network configuration (CNC) entity that determines bridge schedules.

[0075] A second embodiment is directed to an apparatus that may comprise at least one processor and at least one memory comprising computer program code. The at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to obtain at least one of mobility constraint information for a user equipment (UE) and path delay for each network node in a mobility area of the user equipment (UE), determine an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the user equipment (UE), select a 5G quality of service (QoS) identifier (5QI) having an actual packet delay budget (PDB) that accommodates the determined achievable packet delay budget (PDB), and determine a 5G system (5GS) delay based at least on the actual packet delay budget (PDB) determined from the achievable packet delay budget (PDB).

[0076] In a variant, the mobility constraints may comprise at least one of: mobility restriction information including closed access group (CAG) or service area restrictions, or a restricted area defined for time sensitive communications (TSC) user equipment (UEs).

[0077] According to a variant, the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to: obtain the mobility constraint information from pre defined mobility restrictions, or the mobility constraint information may be provisioned for time sensitive communications (TSC).

[0078] In a variant, the path delay may comprise at least one of N3 path delay or radio access network (RAN) path delay.

[0079] According to some variants, the N3 path delay may be obtained from dynamic values of core network (CN) packet delay budget (PDB) provisioned in radio access network (RAN) or user plane function (UPF), or the N3 path delay may be obtained from ultra-reliable low-latency- communication (URLLC) quality of service (QoS) monitoring information. [0080] In a variant, the radio access network (RAN) path delay may be obtained from ultra-reliable low-latency-communication (URLLC) quality of service (QoS) monitoring information.

[0081] According to a variant, the at least one memory and computer program code may be further configured, with the at least one processor, to cause the apparatus at least to: select the 5G quality of service (QoS) identifier (5QI) so that the actual packet delay budget (PDB) is greater than or equal to the achievable packet delay budget (PDB).

[0082] In a variant, the at least one memory and computer program code may be further configured, with the at least one processor, to cause the apparatus at least to: determine the 5GS delay from a residence time of the user equipment (UE).

[0083] According to a variant, the 5G system (5GS) may be integrated with the external network as a TSN bridge, and the 5G system (5GS) delay may be a 5GS TSN Bridge delay.

[0084] In a variant, the at least one memory and computer program code may be further configured, with the at least one processor, to cause the apparatus at least to: transmit the determined 5G system (5GS) bridge delay to a central network configuration (CNC) entity that determines bridge schedules.

[0085] A third embodiment is directed to an apparatus that may comprise means for obtaining at least one of mobility constraint information for a user equipment (UE) and path delay for each network node in a mobility area of the user equipment (UE), means for determining an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the user equipment (UE), means for selecting a 5G quality of service (QoS) identifier (5QI) having an actual packet delay budget (PDB) that accommodates the determined achievable packet delay budget (PDB), and means for determining a 5G system (5GS) delay based at least on the actual packet delay budget (PDB) determined from the achievable packet delay budget (PDB).

[0086] A fourth embodiment may be directed to a computer readable medium comprising program instructions stored thereon for performing at least the following: obtaining at least one of mobility constraint information for a user equipment (UE) and path delay for each network node in a mobility area of the user equipment (UE), determining an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the user equipment (UE), selecting a 5G quality of service (QoS) identifier (5QI) having an actual packet delay budget (PDB) that accommodates the determined achievable packet delay budget (PDB), and determining a 5G system (5GS) delay based at least on the actual packet delay budget (PDB) determined from the achievable packet delay budget (PDB).

[0087] Another embodiment may be directed to an apparatus including circuitry configured to perform any of the embodiments discussed above or any of their variants.

[0088] One having ordinary skill in the art will readily understand that the example embodiments as discussed above may be practiced with procedures in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although some embodiments have been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of example embodiments.

Claims

We Claim:

1. A method, comprising: obtaining at least one of mobility constraint information for a user equipment (UE) and path delay for each network node in a mobility area of the user equipment (UE); determining an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the user equipment (UE); selecting a 5G quality of service (QoS) identifier (5QI) that supports an actual packet delay budget (PDB) that accommodates the determined achievable packet delay budget (PDB); and determining a 5G system (5GS) delay based at least on the actual packet delay budget (PDB) determined from the achievable packet delay budget (PDB).

2. The method according to claim 1, wherein the mobility constraints comprise at least one of: mobility restriction information including closed access group (CAG) or service area restrictions, or a restricted area defined for time sensitive communications (TSC) user equipment (UEs).

3. The method according to claims 1 or 2, wherein the obtaining comprises obtaining the mobility constraint information from pre-defined mobility restrictions, or wherein the mobility constraint information may be provisioned for time sensitive communications (TSC).

4. The method according to any of claims 1-3, wherein the path delay comprises at least one of N3 path delay or radio access network (RAN) path delay.

5. The method according to claim 4, wherein the N3 path delay is obtained from dynamic values of core network (CN) packet delay budget (PDB) provisioned in radio access network (RAN) or user plane function (UPF), or wherein the N3 path delay is obtained from ultra-reliable low-latency- communication (URLLC) quality of service (QoS) monitoring information.

6. The method according to claim 4, wherein the radio access network (RAN) path delay is obtained from ultra-reliable low-latency-communication (URLLC) quality of service (QoS) monitoring information.

7. The method according to any of claims 1-6, wherein the selecting comprises selecting the 5G quality of service (QoS) identifier (5QI) so that the actual packet delay budget (PDB) is greater than or equal to the achievable packet delay budget (PDB).

8. The method according to any of claims 1-7, wherein the determining of the 5G system (5GS) delay further comprises determining the 5GS delay from a residence time of the user equipment (UE).

9. The method according to any of claims 1-8, wherein the 5G system (5GS) is integrated with the external network as a time sensitive networking (TSN) bridge, and the 5G system (5GS) delay is a 5GS TSN Bridge delay.

10. The method according to any of claims 1-9, further comprising: transmitting the determined 5G system (5GS) bridge delay to a central network configuration (CNC) entity that determines bridge schedules or to an application function (AF).

11. An apparatus, comprising: at least one processor; and at least one memory comprising computer program code, the at least one memory and computer program code configured, with the at least one processor, to cause the apparatus at least to obtain at least one of mobility constraint information for a user equipment (UE) and path delay for each network node in a mobility area of the user equipment (UE); determine an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the user equipment (UE); select a 5G quality of service (QoS) identifier (5QI) that supports an actual packet delay budget (PDB) that accommodates the determined achievable packet delay budget (PDB); and determine a 5G system (5GS) delay based at least on the actual packet delay budget (PDB) determined from the achievable packet delay budget (PDB).

12. The apparatus according to claim 11, wherein the mobility constraints comprise at least one of: mobility restriction information including closed access group (CAG) or service area restrictions, or a restricted area defined for time sensitive communications (TSC) user equipment (UEs).

13. The apparatus according to claims 11 or 12, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to: obtain the mobility constraint information from pre-defined mobility restrictions, or wherein the mobility constraint information may be provisioned for time sensitive communications (TSC).

14. The apparatus according to any of claims 11-13, wherein the path delay comprises at least one of N3 path delay or radio access network (RAN) path delay.

15. The apparatus according to claim 14, wherein the N3 path delay is obtained from dynamic values of core network (CN) packet delay budget (PDB) provisioned in radio access network (RAN) or user plane function (UPF), or wherein the N3 path delay is obtained from ultra-reliable low- latency-communication (URLLC) quality of service (QoS) monitoring information.

16. The apparatus according to claim 14, wherein the radio access network (RAN) path delay is obtained from ultra-reliable low-latency-communication (URLLC) quality of service (QoS) monitoring information.

17. The apparatus according to any of claims 11-16, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to: select the 5G quality of service (QoS) identifier (5QI) so that the actual packet delay budget (PDB) is greater than or equal to the achievable packet delay budget (PDB).

18. The apparatus according to any of claims 11-17, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to: determine the 5GS delay from a residence time of the user equipment

(UE).

19. The apparatus according to any of claims 11-18, wherein the 5G system (5GS) is integrated with the external network as a time sensitive networking (TSN) bridge, and the 5G system (5GS) delay is a 5GS TSN Bridge delay.

20. The apparatus according to any of claims 11-19, wherein the at least one memory and computer program code are further configured, with the at least one processor, to cause the apparatus at least to: transmit the determined 5G system (5GS) bridge delay to a central network configuration (CNC) entity that determines bridge schedules or to an application function (AF).

21. An apparatus, comprising: means for obtaining at least one of mobility constraint information for a user equipment (UE) and path delay for each network node in a mobility area of the user equipment (UE); means for determining an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the user equipment (UE); means for selecting a 5G quality of service (QoS) identifier (5QI) that supports an actual packet delay budget (PDB) that accommodates the determined achievable packet delay budget (PDB); and means for determining a 5G system (5GS) delay based at least on the actual packet delay budget (PDB) determined from the achievable packet delay budget (PDB).

22. A computer readable medium comprising program instructions stored thereon for performing at least the following: obtaining at least one of mobility constraint information for a user equipment (UE) and path delay for each network node in a mobility area of the user equipment (UE); determining an achievable packet delay budget (PDB) that comprises a maximum path delay over the mobility area of the user equipment (UE); selecting a 5G quality of service (QoS) identifier (5QI) that supports an actual packet delay budget (PDB) that accommodates the determined achievable packet delay budget (PDB); and determining a 5G system (5GS) delay based at least on the actual packet delay budget (PDB) determined from the achievable packet delay budget (PDB).