Synchronization of time sensitive communication hold-and-forward buffers with time sensitive communication assistance information

Abstract

A method and apparatus may include receiving, by a radio access network (RAN), at least one burst arrival time (BAT) parameter from at least one session management function (SMF). The method may further include determining, by the RAN, if at least one actual BAT is offset from the at least one received BAT parameter by at least one threshold. The method may further include setting, by the RAN, at least one BAT correction parameter based upon at least one offset time. The method may further include calculating, by the RAN, at least one new BAT parameter according to the one BAT correction parameter. The method may further include adjusting, by the RAN, at least one burst schedule based upon one or more of the at least one BAT correction parameter or the at least one new BAT parameter.

Claims

1. A method, comprising: receiving, by a network entity, from a network exposure function, at least one port management information container comprising at least one parameter; setting, by the network entity, at least one hold and forward transmission buffering time according to any of the at least one received parameter; receiving, by the network entity, at least one of a burst arrival time (BAT) correction parameter or at least one new BAT parameter via an information container; and adjusting, by the network entity, the at least one hold and forward transmission buffering time according to the at least one of the BAT correction parameter or the at least one new BAT parameter.

2. The method of claim 1, wherein the network entity comprises a user plane function, a device side time sensitive networking translator, or a network time sensitive networking translator.

3. The method of claim 1, wherein the at least one parameter comprises one or more of at least one BAT, at least one periodicity, or at least one offset.

4. The method of claim 2, wherein the at least one parameter comprises one or more of at least one BAT, at least one periodicity, or at least one offset.

5. An apparatus comprising: at least one processor; and at least one memory including computer program code, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to: receive from a network exposure function, at least one port management information container comprising at least one parameter; set at least one hold and forward transmission buffering time according to any of the at least one received parameter; receive at least one of a burst arrival time (BAT) correction parameter or at least one new BAT parameter via an information container; and adjust the at least one hold and forward transmission buffering time according to the at least one of the BAT correction parameter or the at least one new BAT parameter.

6. The apparatus of claim 5, wherein the apparatus comprises a user plane function, a device side time sensitive networking translator, or a network time sensitive networking translator.

7. The apparatus of claim 6, wherein the at least one parameter comprises one or more of at least one BAT, at least one periodicity, or at least one offset.

8. The apparatus of claim 5, wherein the at least one parameter comprises one or more of at least one BAT, at least one periodicity, or at least one offset.

9. A non-transitory computer-readable medium comprising instructions which when executed by at least one processor of an apparatus cause the apparatus to at least: receive from a network exposure function, at least one port management information container comprising at least one parameter; set at least one hold and forward transmission buffering time according to any of the at least one received parameter; receive at least one of a burst arrival time (BAT) correction parameter or at least one new BAT parameter via an information container; and adjust the at least one hold and forward transmission buffering time according to the at least one of the BAT correction parameter or the at least one new BAT parameter.

10. The non-transitory computer-readable medium of claim 7, wherein the apparatus comprises a user plane function, a device side time sensitive networking translator, or a network time sensitive networking translator.

11. The non-transitory computer-readable medium of claim 7, wherein the at least one parameter comprises one or more of at least one BAT, at least one periodicity, or at least one offset.

12. The non-transitory computer-readable medium of claim 11, wherein the at least one parameter comprises one or more of at least one BAT, at least one periodicity, or at least one offset.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

(1) For proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

(2) FIG. 1 illustrates an example of a 5GS timing configuration procedure for native time sensitive communications.

(3) FIG. 2 illustrates an example of a signaling diagram according to certain embodiments.

(4) FIG. 3 illustrates an example of a flow diagram of a method according to various embodiments.

(5) FIG. 4 illustrates an example of a flow diagram of a method according to some embodiments.

(6) FIG. 5 illustrates an example of a flow diagram of a method according to some embodiments.

(7) FIG. 6 illustrates an example of various network devices according to some embodiments.

(8) FIG. 7 illustrates an example of a 5G network and system architecture according to certain embodiments.

DETAILED DESCRIPTION

(9) 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 adjusting hold and forward buffers to align with deterministic flows is not intended to limit the scope of certain embodiments, but is instead representative of selected example embodiments.

(10) Third Generation Partnership Project (3GPP) seeks to enhance wireless 5GS connectivity with fixed-line IEEE, Ethernet-based networks in industrial environments to provide scalability, improve flexibility, and lower total cost of ownership (TCO). For example, 3GPP has considered enhanced support of vertical and local area network (LAN) services, as well as the ability to transparently integrate 5GS as TSN bridge into an Ethernet network. This expansion has included 5GS serving as an IEEE TSN bridge with full protocol compatibility between 3GPP and IEEE TSN-bridged Ethernet networks. However, this expansion has introduced additional complexity into 5GS by placing new constraints on both 5GS and data networks to which 5GS connects.

(11) 3GPP has also given consideration towards adjusting TSC parameters and services to improve flexibility in supporting various networking scenarios beyond TSN. For example, an application function (AF) with knowledge of an application's requirements and end-station connectivity via the 5GS may send TSC assistance information (TSCAI) to the RAN to optimize RAN scheduling. This may also configure 5GS hold and forward (HnF) buffers such that the 5GS transmits bursts with the proper timing.

(12) In general, deterministic flows require transmissions within a specific time window. TSN bridges were standardized in 3GPP using HnF buffers in the UE/DS-TT for downlink flows, and in the UPF/NW-TT for uplink flows. By using various gate schedules that use gate open times, burst release times from the HnF may be determined. As a result, jitter in 5GS may be absorbed by the HnF buffer, whereby packets may arrive at the 5GS egress within the packet data budget (PDB).

(13) Native 5GS TSC lacks support for IEEE 802.Qci PSFP information and IEEE 802.Qbv gate schedules from which to derive BAT and HnF buffer parameters. Instead, an AF that requests TSC services must determine a suitable BAT, and calculate an acceptable HnF buffer Tx time window. For example, the window may be defined by an HnF First_Open Time and HnF First_Close Time. This configuration may follow the procedure illustrated in FIG. 1, which is similar to 3GPP Rel-16 procedure. However, an AF/NEF may not have 802.1Qci PSFP information in which to base 5GS ingress time, and may calculate a HnF Tx time window. In 3GPP Rel-16, 802.1Qbv managed objects received from a CNC may be transmitted to a UE/DS-TT or a UPF/NW-TT to configure HnF buffers. However, inaccuracies of the BAT and HnF Tx time determined by the AF/NEF, such as from an estimate of the 5GS delay source Tx timing information, may result in BAT and HnF Tx times that do not reflect the actual BAT in the RAN.

(14) Some techniques have proposed the AF indicating support for burst arrival adaptation to 5GS. In this way, if the NG-RAN determines a need to adapt the burst arrival time, the NG-RAN may transmit an indication to the AF may include a burst arrival time offset value, for example of up to +/−2 ms. With respect to downlink flows, the AF may adapt the burst sending time based on the received offset. Alternatively, for uplink flows, the AF may request the source to adapt the burst sending time. However, this approach requires a source, network bridge, or UPF/NW-TT to adjust transmitting the deterministic flow according to NG-RAN timing. As a result, jitter may be introduced into the deterministic flow, and may additional delays may be added to the TSC flow such that burst arrivals in the RAN occur according to an initial erroneous calculation. This technique would also not be compatible with bridges, routers, sources, and UPF/NW-TTs which are not designed to alter the Tx time of an on-going flow according to an arbitrary external input.

(15) Certain embodiments described herein may have various benefits and/or advantages to overcome the disadvantages described above. For example, certain embodiments may enable 5GS enabled for TSC to adapt to inaccuracies in calculated burst arrival times. For example, this may be applied towards native TSC procedures where no CNC exists to provide IEEE 802.1Qbv and 802.Qci information from which to derive timing references to a RAN and egress HnF buffers. Thus, certain embodiments discussed below are directed to improvements in computer-related technology.

(16) FIG. 2 illustrates an example of a signaling diagram depicting how to adjust hold and forward buffers to align with deterministic flows. UE/DS-TT 230 may be similar to UE/DS-TT 620, while RAN 240, SMF 250, NEF 260, AF 270, and UPF/NW-TT 280 may be similar to NE 610, as illustrated in FIG. 6, according to certain embodiments.

(17) At 201, AF 270 may determine at least one BAT at the ingress of a 5GS system. For example, AF 270 may determine the at least one BAT based upon a transit time of a source/talker, which may be adjusted for intermediate bridges/routers. At 203, AF 270 may transmit the at least one determined BAT, as well as information associated with other TSCAI parameters, to NEF 260.

(18) At 205, NEF 260 may transmit the at least one determined BAT to SMF 250. In various embodiments, NEF 260 may also transmit at least one indication that NEF 260 supports transmitting BAT adaptation information in a PMIC. At 207, SMF 250 may adjust the at least one BAT from the ingress of the 5GS to the arrival time in RAN 240. For example, SMF 250 may perform this adjustment based on at least one PDB of the 5GS and/or a residence time of UE/DS-TT 230. At 209, SMF 270 may transmit to RAN 260 the at least one adjusted BAT, at least one other TSCAI parameter, at least one “support BAT Adaptation” parameter, and/or at least one “threshold BAT offset reporting” parameter.

(19) At 211, NEF 260 may determine at least one HnF time based upon the at least one BAT, a periodicity for the 5GS, and/or the 5GS delay for UL/DL at UE/DS-TT 230 and/or UPF/NW-TT 280, which may be based upon a 5GS PDB and/or UE/DS-TT residence time. Alternatively, NEF 260 may forward any of the BATs, periodicities, burst ingress times, offsets to UE/DS-TT 230, and offsets to UPF/NW-TT 280 via at least one PMIC container. At 213, NEF 260 may transmit the PMIC containers to UE/DS-TT 230 and/or UPF/NW-TT 280. It is noted that the procedures performed at 211 and 213 may be performed before any of the procedures performed at 205-209.

(20) At 215, based on whether UE/DS-TT 230 and/or UPF/NW-TT 280 received the PMIC at 213, UE/DS-TT 230 and/or UPF/NW-TT 280 may compute and set HnF Tx buffering times according to any of the parameters received at 211. At 217, RAN 240 may detect burst arrival times and/or may determine if the actual burst arrival times are offset from the BAT+n*Periodicity. In various embodiments, periodicity may be a TSCAI parameter indicating a period of the TSC stream, while “n” may be an integer. At 219, RAN 240 may set BAT correction parameters to equal an offset time, and may adjust its burst scheduling time in accordance with this adjustment.

(21) At 221, if at least one report threshold is exceeded, RAN 240 may transmit the BAT correction parameters to SMF 250, which, at 223, may then be transmitted by SMF 250 to NEF 260/AF 270. At 223, NEF 260 may transmit the BAT correction parameters to UE/DS-TT 230 and/or UPF/NW-TT 280 via an information container, such as a port management information container. Additionally or alternatively, the BAT correction parameters may be sent to AF 270 to enable AF 270 to determine whether the 5GS delay requirement is satisfied. At 225, UE/DS-TT 230 and/or UPF/NW-TT 280 may adjust its HnF time according to the BAT correction parameters received at 223.

(22) FIG. 3 illustrates an example of a flow diagram of a method that may be performed by a RAN, according to various embodiments. At 301, the RAN may receive from an SMF at least one adjusted BAT, at least one other TSCAI parameter, at least one “support BAT Adaptation” parameter, and/or at least one “threshold BAT offset reporting” parameter. The at least one adjusted BAT may be adjusted from an ingress of a 5GS to an arrival time in the RAN. For example, the SMF may have performed this adjustment based on at least one PDB of the 5GS and/or a residence time of a UE/DS-TT.

(23) At 303, the RAN may detect burst arrival times and/or may determine if the actual burst arrival times are offset from the at least one received BAT parameter, such from BAT+n*Periodicity. In various embodiments, periodicity may be a TSCAI parameter indicating a period of the TSC stream, while “n” may be an integer. At 305, the RAN may set BAT correction parameters to equal an offset time, and may adjust its burst scheduling time in accordance with this adjustment. At 307, if at least one report threshold is exceeded, the RAN may transmit the BAT correction parameters to the SMF.

(24) FIG. 4 illustrates an example of a flow diagram of a method that may be performed by a UE/DS-TT, such as UE/DS-TT 620 in FIG. 6, according to various embodiments. At 401, the UE/DS-TT may receive, from a NEF such as the NEF illustrated in FIG. 9, at least one PMIC container, which may include any number of BATs, periodicities, burst ingress times, and offsets.

(25) At 403, the UE/DS-TT may compute and set HnF Tx buffering times according to any of the parameters received at 401. At 405, the UE/DS-TT may receive at least one or more of a BAT correction parameter or the at least one new BAT parameter via an information container, such as a port management information container. At 407, the UE/DS-TT may adjust its HnF time according to the BAT correction parameters received at 405 or the at least one new BAT parameter.

(26) FIG. 5 illustrates an example of a flow diagram of a method that may be performed by a UPF/NW-TT, such as the UPF/NW-TT illustrated in FIG. 7, according to various embodiments. At 501, the UPF/NW-TT may receive, from a NEF, such as the NEF illustrated in FIG. 6, at least one PMIC container, which may include any number of BATs, periodicities, burst ingress times, and offsets.

(27) At 503, the UPF/NW-TT may compute and set HnF Tx buffering times according to any of the parameters received at 501. At 505, the UPF/NW-TT may receive BAT correction parameters via an information container, such as a port management information container. At 507, the UPF/NW-TT may adjust its HnF time according to the BAT correction parameters received at 505.

(28) FIG. 6 illustrates an example of a system according to certain example embodiments. In one example embodiment, a system may include multiple devices, such as, for example, NE 610 and/or UE/DS-TT 620.

(29) NE 610 may be one or more of a base station, such as an eNB or gNB, a serving gateway, a server, and/or any other access node or combination thereof. Furthermore, NE 610 and/or UE/DS-TT 620 may be one or more of a citizens broadband radio service device (CBSD).

(30) NE 610 may further comprise at least one gNB-CU, which may be associated with at least one gNB-DU. The at least one gNB-CU and the at least one gNB-DU may be in communication via at least one F1 interface, at least one X.sub.n-C interface, and/or at least one NG interface via a 5GC.

(31) UE 620 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof.

(32) NE 610 and/or UE/DS-TT 620 may include at least one processor, respectively indicated as 611 and 621. Processors 611 and 621 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.

(33) At least one memory may be provided in one or more of the devices, as indicated at 612 and 622. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. Memories 612 and 622 may independently be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory, and which may be processed by the processors, may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

(34) Processors 611 and 621, memories 612 and 622, and any subset thereof, may be configured to provide means corresponding to the various blocks of FIGS. 2-5. Although not shown, the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors are also permitted, and may be configured to determine location, elevation, velocity, orientation, and so forth, such as barometers, compasses, and the like.

(35) As shown in FIG. 6, transceivers 613 and 623 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 614 and 624. The device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple RATs. Other configurations of these devices, for example, may be provided. Transceivers 613 and 623 may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.

(36) The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE/DS-TT, to perform any of the processes described above (i.e., FIGS. 2-5). Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments may be performed entirely in hardware.

(37) In certain embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIGS. 2-5. For example, circuitry may be hardware-only circuit implementations, such as analog and/or digital circuitry. In another example, circuitry may be a combination of hardware circuits and software, such as a combination of analog and/or digital hardware circuitry with software or firmware, and/or any portions of hardware processors with software (including digital signal processors), software, and at least one memory that work together to cause an apparatus to perform various processes or functions. In yet another example, circuitry may be hardware circuitry and or processors, such as a microprocessor or a portion of a microprocessor, that includes software, such as firmware, for operation. Software in circuitry may not be present when it is not needed for the operation of the hardware.

(38) FIG. 7 illustrates an example of a 5G network and system architecture according to certain embodiments. Shown are multiple network functions that may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware. The NE and UE/DS-TT illustrated in FIG. 7 may be similar to NE 610 and UE/DS-TT 620, respectively. The UPF/NW-TT may provide services such as intra-RAT and inter-RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of downlink packets, and/or triggering of downlink data notifications. The application function (AF) may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.

(39) 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 “various embodiments,” “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 example embodiment may be included in at least one example embodiment. Thus, appearances of the phrases “in various embodiments,” “in certain embodiments,” “in some embodiments,” or other similar language throughout this specification does not necessarily all refer to the same group of example embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

(40) Additionally, if desired, the different functions or procedures discussed above 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 description above should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

(41) One having ordinary skill in the art will readily understand that the example embodiments 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 the example embodiments.

PARTIAL GLOSSARY

(42) 3GPP Third Generation Partnership Project

(43) 5G Fifth Generation

(44) 5GC Fifth Generation Core

(45) 5GS Fifth Generation System

(46) AF Application Function

(47) AMF Access and Mobility Management Function

(48) ASIC Application Specific Integrated Circuit

(49) BAT Burst Arrival Time

(50) BS Base Station

(51) CBSD Citizens Broadband Radio Service Device

(52) CE Control Elements

(53) CG Configured Grant

(54) CN Core Network

(55) CPU Central Processing Unit

(56) DL Downlink

(57) DN Data Network

(58) DS-TT Device Side Time Sensitive Networking Translator

(59) E2E End-to-End

(60) eMBB Enhanced Mobile Broadband

(61) eMTC Enhanced Machine Type Communication

(62) eNB Evolved Node B

(63) eOLLA Enhanced Outer Loop Link Adaptation

(64) EPS Evolved Packet System

(65) gNB Next Generation Node B

(66) GPS Global Positioning System

(67) GTP General Packet Radio Service Tunneling Protocol

(68) HDD Hard Disk Drive

(69) HnF Hold and Forward

(70) IEEE Institute of Electrical and Electronics Engineers

(71) LTE Long-Term Evolution

(72) LTE-A Long-Term Evolution Advanced

(73) MAC Medium Access Control

(74) MBS Multicast and Broadcast Systems

(75) MC Multicast

(76) MCS Modulation and Coding Scheme

(77) MEMS Micro Electrical Mechanical System

(78) MIB Master Information Block

(79) MIMO Multiple Input Multiple Output

(80) MME Mobility Management Entity

(81) mMTC Massive Machine Type Communication

(82) MPDCCH Machine Type Communication Physical Downlink Control Channel

(83) MTC Machine Type Communication

(84) NAS Non-Access Stratum

(85) NB-IoT Narrowband Internet of Things

(86) NE Network Entity

(87) NEF Network Exposure Function

(88) NG Next Generation

(89) NG-eNB Next Generation Evolved Node B

(90) NG-RAN Next Generation Radio Access Network

(91) NR New Radio

(92) NR-U New Radio Unlicensed

(93) NW-TT Network Time Sensitive Networking Translator

(94) OLLA Outer Loop Link Adaptation

(95) PCF Policy Control Function

(96) PDA Personal Digital Assistance

(97) PMIC Port Management Information Container

(98) PSFP Per-Stream Filtering and Policing

(99) RAM Random Access Memory

(100) RAN Radio Access Network

(101) RAT Radio Access Technology

(102) RE Resource Element

(103) RLC Radio Link Control

(104) RRC Radio Resource Control

(105) RS Reference Signal

(106) SDU Service Data Unit

(107) SMF Session Management Function

(108) SPS Semi Persistent Scheduling

(109) TR Technical Report

(110) TS Technical Specification

(111) TSC Time Sensitive Communication

(112) TSCAI Time Sensitive Communication Assistance Information

(113) Tx Transmission

(114) UE User Equipment

(115) UL Uplink

(116) UMTS Universal Mobile Telecommunications System

(117) UPF User Plane Function

(118) URLLC Ultra-Reliable and Low-Latency Communication

(119) UTRAN Universal Mobile Telecommunications System Terrestrial Radio Access Network

(120) VN Virtual Network

(121) WLAN Wireless Local Area Network