Operating clock determination for mobile user equipment

Abstract

Systems, methods, apparatuses, and computer program products for working clock determination for mobile user equipment. A method can include receiving time domain information at a session management function during a protocol data unit (PDU) session procedure. The method can also include forwarding the time domain information to a user plane function for the PDU session procedure. The method can also include configuring the user plane function to enable determination of a correct mapping between the time domain information and a user equipment or a PDU session in accordance with the time domain information.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority to U.S. Provisional Application No. 63 / 061,502, filed August 5, 2020, which is incorporated by reference herein in its entirety. TECHNICAL FIELD

[0003] Some example embodiments can generally relate to mobile or wireless telecommunication systems, such as Long Term Evolution (LTE) or Fifth Generation (5G) wireless radio access technologies or New Radio (NR) access technologies, or can relate to other communication systems. For example, certain example embodiments can relate to apparatuses, systems, and / or methods for mobile user equipment working clock determination. BACKGROUND

[0004] Examples of mobile or wireless telecommunication systems can include the Universal Mobile Telecommunication 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) wireless radio access technologies or New Radio (NR) access technologies. The Fifth Generation (5G) wireless systems refer to the next generation (NG) of radio systems and network architecture. 5G is mainly built on the new radio (NR), but 5G (or NG) networks can also be built on E-UTRA radios. It is estimated that NR will provide bitrates of the order of 10-20 Gbit / s or higher, and will support at least enhanced mobile broadband (eMBB) and ultra-reliable low-latency Communications (URLLC) as well as massive machine type communications (mMTC). NR is expected to provide ultra-wideband and ultra-robust low-latency connectivity and massive networks to support the Internet of Things (IoT). As the IoT and machine-to-machine (M2M) communication become more widespread, the need for networks that are capable of meeting the needs of low power consumption, low data rates, and long battery life will grow. Note that in 5G, nodes that provide radio access functionalities to user equipment (i.e., similar to Node-Bs in UTRAN or eNBs in LTE) are called gNBs when built on NR radios, and NG-eNBs when built on E-UTRAN radios. BRIEF DESCRIPTION OF DRAWINGS

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

[0006] Figure 1 An example of a multi-clock domain scenario in a communication network is shown.

[0007] Figure 2A signal diagram illustrating time domain (TD) forwarding of user plane function (UPF) triggered dynamic management is shown in accordance with certain example embodiments.

[0008] Figure 3 A signal diagram for configuring a UPF is shown in accordance with certain example embodiments.

[0009] Figure 4 Another signal diagram for configuring a UPF is shown in accordance with certain example embodiments.

[0010] Figure 5 A flow diagram of a method in accordance with certain example embodiments is shown.

[0011] Figure 6 A flow diagram of another method in accordance with certain example embodiments is shown.

[0012] Figure 7 A flow diagram of another method in accordance with certain example embodiments is shown.

[0013] Figure 8 A flow diagram of another method in accordance with certain example embodiments is shown.

[0014] FIG. 9(a) illustrates an apparatus in accordance with certain example embodiments.

[0015] FIG. 9(b) illustrates another apparatus in accordance with certain example embodiments. DETAILED DESCRIPTION

[0016] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. The following detailed description is directed to certain example embodiments for systems, methods, apparatus, and computer program products for mobile user equipment (UE) operating clock determination.

[0017] The features, structures, or characteristics of the example embodiments described throughout this specification can be combined in any suitable manner in one or more example embodiments. For example, usage of the phrases “certain embodiments,” “example embodiments,” “some embodiments,” or other similar language throughout this specification refers to the possibility that a particular feature, structure, or characteristic described in connection with one embodiment can be included in at least one embodiment. Thus, appearances of these phrases, as well as appearances of the phrases “in certain embodiments,” “in example 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 can be combined in any suitable manner in one or more example embodiments.

[0018] Furthermore, different functions or processes discussed below can be performed in differing orders and / or concurrently with each other. Furthermore, if desired, one or more of the described functions or processes can be optional or can be combined. Accordingly, the following description should be taken as illustrative and in a like manner, and not limitative.

[0019] A 5G network with Time-Sensitive Networking (TSN) / time synchronization support can include integration of two types of synchronized clocks, e.g., a global time domain and a working clock domain. According to certain example embodiments, the global time domain can represent a 5G clock, and the working clock domain can represent a vertical time domain. Furthermore, a particular time domain (TD) can include devices that can cooperate in the physical world. This can include, for example, robots, automated guided vehicles (AGVs), conveyors, etc. In certain example embodiments, the TDs can be independent of each other, particularly in terms of time scale and time synchronization accuracy.

[0020] Some clock synchronization service level requirements (e.g., specified by the Third Generation Partnership Project (3GPP)) can be associated with global time domain and working clock domain support in 5G. For example, such requirements can include that a 5G system supports a network with up to 128 working clock domains (with different synchronization domain identifiers / domain numbers), including for UEs connected through the 5G network. Another requirement can include that a 5G system provides an interface at a UE to determine and configure the precision and time scale of a working clock domain. Another requirement can include that a 5G system provides suitable means to support the management of merging and splitting of working clock domains. The provided means can interoperate with corresponding mechanisms of TSN.

[0021] 3GPP specifications can also include service requirements similar to the merging and splitting management of working clock domains described above. The basic principle is the common deployment of a generic 5G network infrastructure serving industrial / energy / automation use cases, which does not map to the structure of the processes running in the use cases. In other words, a user plane function (UPF) and a serving gNB can provide services to several UEs that can work with different TDs, which can result in a situation where multiple TDs communicate through the same UPF / gNB.

[0022] 3GPP specifications describe support for TSN time synchronization provided by the 5G system (5GS). For example, the 5GS can have two synchronization procedures: 1) 5GS synchronization, and 2) TSN domain synchronization. Each synchronization procedure can be considered independent of each other, and in some cases, a gNB can be synchronized to a 5G grand master (GM) clock. 5GS synchronization can be used for synchronization of nodes within the 3GPP system, including, for example, synchronization between a 5G radio access network (RAN) and a UPF. 5GS synchronization can also be used for synchronization of nodes within the 5G RAN, including, for example, synchronization between a gNB and a UE. Further, 5G RAN synchronization between a gNB and a UE can be achieved via reference time information signaling. For TSN domain synchronization, this can provide a synchronization service to a TSN network, and this procedure can follow IEEE specifications.

[0023] In some cases, when multiple working clock domains are supported, 3GPP specifications describe that a UPF / network-side TSN translator (NW-TT) can send generic precision time protocol (gPTP) messages or PTP messages for each domain to a device-side TSN translator (DS-TT) in a protocol data unit (PDU) session. If PTP is considered, a TSN application function (AF) can be applied in the case where the TSN AF is not an AF but a gPTP. Further, a UE can forward information related to all working clock domains as-is to the connected DS-TT based on the domain number supported by the end device and the domain number carried by the (g)PTP message that it can need to synchronize to. However, this can waste network and spectrum resources, as this can unnecessarily increase the size of the user plane (UP) payload. In the case of TSN traffic, time-limited transmission can be critical, and thus, the increased payload can consume unnecessary radio resources for transmission, which can lead to the risk of delayed delivery and UP congestion.

[0024] Figure 1 An example of a multi-clock domain scenario in a communication network is shown. Integration of TSN / time synchronization support and 5G wireless networks can be impacted by mobility. For example, a mobile TSN device can move around (e.g., where different factory floors using different working clock domains are used). As shown, such a device can need to be provided with a single clock domain or a subset of clock domains at certain times, even though a wide range of clock domains can be needed at different times, depending on its current location. A 3GPP assumption is that the DS-TT can know which time domain number is supported. Thus, the end station can know which clock domain to use at a particular time. Figure 1

[0025] ​According to certain example embodiments, a TD of interest can be introduced for a UE as part of PDU session management to optimize time information distribution to the UE. In certain example embodiments, by using available TDs, a 5G core (5GC) can update UP configuration to provide a UE only with synchronization messages for the TD(s) that the UE can need. That is, in certain example embodiments, a UPF can be able to dynamically determine the TD(s) for which it can need to forward its synchronization messages to a UE based on a combination of parameters including, for example, mobility events, location, and / or traffic inspection. According to certain example embodiments, a mobility event can correspond to a mobility of a UE. For example, a UE can change a serving cell when a signal in a target cell is stronger than in a source cell. Further, in certain example embodiments, in the case of traffic inspection, if a UPF detects that two UEs are talking / communicating with each other (inspecting user plane traffic), and the UPF knows the TDs with which the two UEs can work, then traffic inspection can help determine the TDs that the UEs should receive.

[0026] In certain example embodiments, a session management function (SMF) can configure a UPF to enable a correct mapping between TD(s) and UE(s). To do so, the SMF can have two sources of information. One source of information can be provided by a UE. For example, a UE can provide TD information during a PDU session management procedure (e.g., PDU session establishment or modification). Another source of information can be provided by a TSN application function (TSN AF). For example, a TSN AF can provide TD information via a policy control function (PCF).

[0027] According to certain example embodiments, TD (or working clock domain) determination at a UPF can be configured in various ways. For example, one option can include a UE / DS-TT providing a SMF with the working clock domain number that is needed during a PDU session establishment procedure. Once received, the SMF can forward this information to a UPF / NW-TT for a given PDU session, which enables the UPF / NW-T to know the domain number(s) that can be needed for a given UE / DS-TT PDU session. When a UPF / NW-TT receives a (g)PTP message containing time information related to a specific clock domain number, it can determine whether a (g)PTP message needs to be sent to a given UE / DS-TT for a given PDU session based on the information received from the SMF. If a (g)PTP message is needed for a given UE / DS-TT, the UPF can include the corresponding (g)PTP message. If a (g)PTP message is not needed for a given UE / DS-TT, the UPF will not send the message for the corresponding UE / DDS-TT.

[0028] Certain example embodiments can provide another option to configure TD determination at the UPF. For example, the TSN AF can obtain information about the mapping between the time domain in the (g)PTP messages and the UE / DS-TT subscribing to this time domain from the Best Master Clock Algorithm (BMCA) results or from external configuration. In certain example embodiments, this mapping information can be provided by the PCF to the SMF. Further, the SMF can associate the mapping information with the PDU session of the corresponding UE / DS-TT and configure the UPF accordingly. For example, in certain example embodiments, the UPF can be configured by the SMF using N4 rules. According to certain example embodiments, the N4 rules can include a Packet Detection Rule (PDR) which can contain information for classifying traffic ((multiple) PDUs) arriving at the UPF. The N4 rules can also include a Forwarding Action Rule (FAR), a Quality of Service (QoS) enforcement rule (QER), etc. Based on the associated PDU session and time domain information (e.g., mapping information), the UPF / NW-TT can deliver the (g)PTP messages to the corresponding UE PDU session.

[0029] According to certain example embodiments, a further option for configuring TD determination at the UPF can be provided. In the above solution, the BMCA results and thus the mapping information can be obtained at the NW-TT. However, in other example embodiments, the NW-TT can provide the mapping information to the SMF via the UPF or via the AF (or TSN AF). Then, the association of the mapping information with the PDU session and the configuration at the UPF can be performed as described above with respect to the SMF association of the mapping information with the PDU session and the UPF / NW-TT delivery of the (g)PTP messages to the corresponding UE / DS-TT PDU session. In other example embodiments, another option can be that the NW-TT itself uses the BMCA results / mapping information to transparently forward the (g)PTP messages to the appropriate UE / DS-TT(s) over the 5GS.

[0030] Figure 2 A signal diagram illustrating dynamic management of user plane function (UPF) triggered time domain (TD) forwarding is shown in accordance with certain example embodiments. As Figure 2As shown, certain example embodiments can provide dynamic management of TD(s) of interest for a UE at the UPF. At 200, a UE can establish a PDU session with gNB1 and the UPF. At 205, the UE’s TDs and related triggers can already be configured for the UE at the UPF, and at 210, the NW-TT can receive various (g)PTP packets associated with respective TDs (e.g., TD#1, TD#2, and TD#3). According to certain example embodiments, the (g)PTP packets can include a domainNumber identifying the TD. Further, the contents of the (g)PTP messages can include a message type, a timestamp, a domainNumber, a correctionField, a sequence ID, a flag, etc. At 215, the UPF / NW-TT can inspect the (g)PTP packets and forward the (g)PTP packets with the TDs that the UE can need (e.g., (g)PTP packet (TD#2)) to gNB1. At 220, gNB1 can forward the (g)PTP packet (TD#2) to the UE.

[0031] As Figure 2 Further shown, at 225, a movement of the UE can trigger a handover from gNB1 to gNB2. At 230, the UPF can determine that the UE needs another TD, and at 235, the NW-TT can receive various (g)PTP packets with respective TDs (e.g., TD#1, TD#2, and TD#3). At 240, the UPF / NW-TT can inspect the (g)PTP packets and forward the (g)PTP packets with the TDs that the UE needs (e.g., (g)P packet (TD#3)) to gNB2. At 245, gNB2 can forward the (g)PTP packet (TD#3) to the UE.

[0032] As Figure 2 shown, in certain example embodiments, the mapping between the UE and the TDs can be updated if the UE is moving. For example, the UE can move around different factory floors, or can interact with the UE / device using different TDs. According to certain example embodiments, the update of the mapping between the UE and the TDs can be triggered by the UE / AGV based on its location in the network. For example, the UE / AGV can enter a new cell, enter a predefined area, which is determined based on a location determined based on a 3GPP positioning system or knowledge of the clock domain being used by other UEs in the vicinity (e.g., signaled by the gNB, or advertised by the UE over sidelink).

[0033] According to other example embodiments, the update can be triggered by the UPF itself. For example, the update can be triggered by the UPF based on certain mobility events (such as handover indications from the gNB / SMF), based on the UE changing its serving UPF, or when a frame is received from the AGV for a nearby UE / when a frame is received from the AGV for a nearby UE. In this case, the UPF may need to know the overall list of TDs subscribed to by the UE and the TDs used in a particular network location. According to another example embodiment, updates to the mapping between the UE and TDs can be signaled from the TSN controller via NW-TT. For example, this can be based on the TSN controller's knowledge of the AGV's location.

[0034] Figure 3 Signal diagrams for configuring a UPF are shown according to certain example embodiments. For example... Figure 3 As shown, at 300, a PDU session can be established with the UPF, and Non-Access Stratum (NAS) signaling can be used to indicate the UE's TD. Specifically, at 300, the UE can trigger a session management procedure (i.e., modify or establish) to provide TD information to the network. In some example embodiments, the TD information can be encapsulated in a NAS information element, and it can be transparently forwarded to the SMF by the gNB and AMF. At 305, during PDU session establishment, the SMF can configure the TD that the UPF will forward for each PDU session or UE. For example, in some example embodiments, the SMF can reconfigure the UPF user plane processing (i.e., N4 rules) to ensure that the UE is receiving the TD (e.g., via packet detection rules). Furthermore, the TD configuration can be directed to send TD information to the UPF so that the UPF knows the domain number that a given UE / PDU session may require.

[0035] In certain example embodiments, the SMF can forward TD information related to a specific UE and / or PDU session to the UPF during configuration. For example, according to certain example embodiments, the SMF can manage the TDs that the UPF needs to forward to each UE. Further, the UPF can learn what TDs should be used based on the traffic flows that the UE is exchanging. Further, in the SMF-managed and UPF-learned SMF, the SMF can provide some initial configuration and the UPF can update this information and inform the SMF. In certain example embodiments, the TD information can include a trigger to switch the TDs to forward to the UE, a forwarding rule, or an update of the association between the TD(s), the UE, and the PDU session. For example, in certain example embodiments, the trigger can include detected traffic that the UPF forwards for each UE, or it can be on-demand traffic requested by the SMF due to a location change of the UE reported by the AMF. Alternatively, there can be a time window in which the UE should be synchronized to a specific TD, or there can be a time window due to a new request by a TSN AF or AF. According to certain example embodiments, the exchanged information can impact the packet forwarding control protocol (PFCP) between the SMF and the UPF to include extensions for a new set of information (e.g., a new set of TD information and possible triggers or policies for switching between TDs). Further, the SMF can subscribe to mobility events to get updates from the access and mobility management function (AMF) and report to the UPF when needed.

[0036] At 310, using the information obtained at 305, the UPF can update local information that associates the TD(s) and the UE. According to certain example embodiments, the local information can include a mapping between the TDs and the UE, a policy for switching between the TDs, a trigger for reporting to the SMF, etc. In particular, the UPF / NW-TT can determine (e.g., based on mobility events, location, etc.) the TDs to forward to the PDU session. According to certain example embodiments, at 310, the UPF can maintain a local table with an association between the TD number and the PDU session. At 315, the NW-TT can receive a (g)PTP packet with TD#1, TD#2, and TD#3. Further, at 320, the UPF / NW-TT can inspect the (g)PTP packet and forward the TD (e.g., TD#3) that the UE needs. In particular, when a (g)PTP packet is received in the UPF / NW-TT, the TD number can be read and the packet can be forwarded to the matching PDU session that the UPF has configured.

[0037] Figure 4Another signal diagram for configuring a UPF is shown in accordance with certain example embodiments. At 400, a TSN AF can obtain information about the mapping between a UE / (multiple) DS-TT and a TD for which the UE is subscribed. Further, the TSN AF can prepare the mapping between the UE / DS-TT port and the TD. At 405, the TSN AF can forward the TD information to a PCF, which can then forward the TD information to a SMF. In particular, the TSN AF can provide the mapping information to the 5G network to the PCF via an exposure framework. The PCF can then forward the mapping information to the SMF, and the SMF can store this information. According to certain example embodiments, this exchange can extend the time synchronization exposure framework to allow the AF to forward information about the TD. As Figure 4 Further shown, at 410, a PDU session can be established between network elements.

[0038] At 415, the SMF can correlate the information received from the TSN AF with the port binding information to track the association of the TD, UE, and PDU session. Further, as Figure 4 shown, steps 420, 425, 430, and 435 can be similar to steps 305, 310, 315, and 320 in Figure 3 . In particular, at 420, during PDU session establishment, the SMF can configure the TDs that the UPF can forward per PDU session or UE. According to certain example embodiments, the SMF can send a TD information indication to the UPF during the configuration of the UPF. In other words, the SMF can send the TD information to the UPF. Finally, the SMF can configure the routing at the UPF, and thus, every piece of information useful for packet classification can be taken into account. Further, the SMF can forward the TD information related to a specific UE and / or PDU session to the UPF. In certain example embodiments, the TD information can include a trigger to switch the TD used to forward to the UE, a forwarding rule, or an update of the association between the TD(s), UE, and PDU session. According to certain example embodiments, the information exchanged can impact the PFCP between the SMF and the UPF to include extensions for a new set of information. Further, the SMF can subscribe to mobility events to obtain updates from an access and mobility management function (AMF) and report to the UPF when needed.

[0039] At 425, using the information obtained at 420, the UPF can update its local information associating the TD(s) and the UE. In particular, the UPF / NW-TT can determine (e.g., based on mobility events, location, etc.) the TDs to be forwarded to the PDU session. According to certain example embodiments, in this step, the UPF can maintain a local table with the association between the TD number and the PDU session. At 430, the NW-TT can receive the (g)PTP packets associated with TD#1, TD#2 and TD#3. Moreover, at 435, the UPF / NW-TT can inspect the (g)PTP packets and forward the (g)PTP packets associated with the corresponding TD (e.g., TD#3) that the UE needs. In particular, when a (g)PTP packet is received in the UPF / NW-TT, the TD number can be read and the packet can be forwarded to the matching PDU session that the UPF has configured.

[0040] Certain example embodiments can provide additional solutions to configure the TD (or working clock domain) determination at the UPF. For example, this solution can have a similar signaling flow as shown in Figure 4 However, the mapping information can be obtained at the NW-TT, which provides the mapping information to the SMF via the UPF or via the AF. The steps after 405 can be the same. Moreover, in certain example embodiments, the SMF can eventually configure the UPF with this information. Moreover, based on the configuration from the SMF, the UPF can be able to determine which Ethernet frames are to be mapped to which PDU session based on its Ethernet multicast destination address and / or time domain number (e.g., time domain information (TD)). According to certain example embodiments, when the SMF sends N4 rules to the UPF (e.g., PDR, FAR, QER), the classification of the traffic can include a specific filter for the (g)PTP packets or the use of the multicast address as a filter for the PDR. Thus, if the SMF is in charge of managing the process completely in the UPF, the SMF can send to the UPF specific dedicated forwarding rules for each UE and update the information when the information is determined due to an event triggered by the AMF or due to a notification from the UPF.

[0041] Figure 5 A flow diagram of a method according to certain example embodiments is shown. In certain example embodiments, the flow diagram of Figure 5 may be performed by a telecommunication network entity or network node in a 3GPP system, such as LTE or 5G-NR. For example, in certain example embodiments, the method of Figure 5 may be performed by a session management function, e.g., an apparatus 20 similar to the one shown in Fig. 9(b).

[0042] According to certain example embodiments, Figure 5The method of FIG. 9(a) can include, at 500, receiving time domain information at a session management function during a protocol data unit (PDU) procedure. The method can further include, at 505, forwarding the time domain information to a user plane function for the PDU procedure. The method can further include, at 510, configuring the user plane function to enable determination of a correct mapping between the time domain information and a user equipment or PDU session according to the time domain information.

[0043] According to certain example embodiments, the forwarding can include forwarding a configuration including one or more extensions for a new set of time domain information. According to other example embodiments, the time domain information can include an associated working clock domain number, a trigger for switching a time domain to forward to the user equipment or PDU session, a forwarding rule, a packet filter, or an update of an association between the time domain, the user equipment, and the PDU session. In certain example embodiments, the method can further include subscribing to a mobility event of the user equipment for updates of the mobility event. In other example embodiments, the method can further include reporting the mobility event to the user plane function.

[0044] Figure 6 A flow diagram illustrating another method according to certain example embodiments is shown. In certain example embodiments, Figure 6 The flow diagram of FIG. 9(a) can be performed by a telecommunication network entity or network node in a 3GPP system, such as LTE or 5G-NR. For example, in certain example embodiments, Figure 6 The method of FIG. 9(a) can be performed by a session management function, e.g., similar to the apparatus 20 shown in FIG. 9(b).

[0045] According to certain example embodiments, Figure 6 The method of FIG. 9(a) can include, at 600, receiving time domain information and mapping information. The method can further include, at 605, relating the time domain information and the mapping information to a protocol data unit (PDU) session procedure. Further, at 610, the method can include configuring a user plane function to enable determination of a correct mapping between the time domain information and a user equipment or PDU session according to the time domain information or the mapping information.

[0046] According to certain example embodiments, the mapping information can include a mapping between time domain information and user equipment subscribing to the time domain information. In certain example embodiments, the mapping information can be received from the user equipment via non-access stratum signaling, or from a time sensitive networking application function or application function via an exposure framework, or derived from a result of a best master clock algorithm. In other example embodiments, the configuration can be performed during a PDU session procedure. In some example embodiments, the time domain information can include an associated working clock domain number, a trigger for switching a time domain to forward to the user equipment or PDU session, a forwarding rule, a packet filter, or an update of an association between the time domain, the user equipment, and the PDU session. According to certain example embodiments, the method can further include subscribing to a mobility event of the user equipment for updates of the mobility event. According to further example embodiments, the method can include reporting the mobility event to a user plane function.

[0047] Figure 7 A flow diagram illustrating another method according to certain example embodiments is shown. In example embodiments, Figure 7 The method of FIG. 10 can be performed by a telecommunication network entity or network node in a 3GPP system, such as LTE or 5G-NR. For example, in certain example embodiments, Figure 7 The method of FIG. 10 can be performed by a UPF similar to the apparatus 20 shown in FIG. 9(b).

[0048] According to certain example embodiments, the method can include, at 700, receiving time domain information for a protocol data unit (PDU) session. The method can further include, at 705, updating local information associating the time domain information with a user equipment or the PDU session based on one or more parameters related to the user equipment. The method can further include, at 710, receiving a time protocol packet. Further, at 715, the method can include determining whether to send the time protocol packet to the user equipment for the given PDU session based on the received time domain information. Further, at 720, the method can include sending the time protocol packet to the user equipment for the given PDU session or performing other forwarding actions on the time protocol packet based on the determination. For example, in certain example embodiments, the UPF can retain the packet, discard the packet, or replace the packet.

[0049] According to certain example embodiments, the one or more parameters can include information related to one or more of a mobility event, a location, or a traffic check. According to other example embodiments, the time protocol packet can be a grand master time protocol packet or a precision time protocol packet. According to further example embodiments, the time protocol packet can include time information related to a clock domain number. In certain example embodiments, the updating can include maintaining a local table with an association between the time domain information and the PDU session.

[0050] Figure 8 A flow diagram illustrating another method according to certain example embodiments is shown. In example embodiments, Figure 8 The method of can be performed by a telecommunication network entity or network node in a 3GPP system, such as LTE or 5G-NR. For example, in certain example embodiments, Figure 8 The method of can be performed by a UPF similar to the apparatus 20 shown in Figure 9(b).

[0051] According to certain example embodiments, the method can include, at 800, receiving time domain information or mapping information for a protocol data unit (PDU) session. The method can further include, at 805, updating local information that associates the time domain information or mapping information with a user equipment based on one or more parameters related to the user equipment. The method can further include, at 810, receiving a time protocol packet. At 815, the method can include determining whether to send the time protocol packet to the user equipment for a given PDU session based on the received time domain information or mapping information. Further, at 820, the method can include sending the time protocol packet to the user equipment for the given PDU session or performing other forwarding actions on the time protocol packet based on the determination. For example, in certain example embodiments, the UPF can retain the packet, discard the packet, or replace the packet.

[0052] According to certain example embodiments, the mapping information can include a mapping between the time domain information and user equipment that subscribes to the time domain information. In certain example embodiments, the mapping information can be received from the user equipment or received from a time sensitive networking application function or application function via an exposure framework or derived from results of a best master clock algorithm. In some example embodiments, the updating can include maintaining a local table with associations between the time domain information and PDU sessions. In other example embodiments, the one or more parameters can include one or more of a mobility event, a location, or a traffic check. According to certain example embodiments, the time protocol packet can be a grandmaster time protocol packet or a precision time protocol packet.

[0053] Figure 9(a) illustrates an apparatus 10 according to certain example embodiments. In certain example embodiments, the apparatus 10 can be a node or element in a communication network or associated with such a network. For example, in certain example embodiments, the apparatus 10 can be a UE, a mobile equipment (ME), a mobile station, a mobile equipment, a fixed device, an IoT device, or other device. As described herein, a UE can alternatively be referred to as, for example, a mobile station, a mobile device, a mobile unit, a mobile equipment, a user device, a subscriber station, a wireless terminal, a tablet, a smartphone, an IoT device, a sensor, or a NB-IoT device, among other examples. In other example embodiments, the apparatus 10 can be implemented, for example, in a wireless handset, a wireless plug-in accessory, or the like.

[0054] In some example embodiments, apparatus 10 can include one or more processors, one or more computer-readable storage medium (e.g., memory, storage, etc.), one or more radio access components (e.g., modems, transceivers, etc.), and / or a user interface. In some example embodiments, apparatus 10 can be configured to operate using one or more radio access technologies, such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology. It should be noted that one of ordinary skill in the art will understand that apparatus 10 can include components or features not shown in FIG. 9(a).

[0055] As shown in the example of FIG. 9(a), apparatus 10 can include or be coupled to a processor 12 for processing information and executing instructions or operations. Processor 12 can be any type of general or specific purpose processor. Indeed, processor 12 can 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. 9(a), multiple processors can be employed according to other example embodiments. For example, it should be understood that, in certain example embodiments, apparatus 10 can include two or more processors that can form a multiprocessor system that can support multiprocessing (e.g., in which case processor 12 can represent a multiprocessor). According to certain example embodiments, the multiprocessor system can be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0056] Processor 12 can perform functions associated with the operation of apparatus 10, including, as some examples, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming a communication message, formatting of information, and overall control of apparatus 10, including Figures 1 to 4 the processes shown.

[0057] The apparatus 10 can also include or be coupled to a memory 14 (internal or external) that can be coupled to the processor 12, the memory 14 for storing information and instructions that can be executed by the processor 12. The memory 14 can be one or more memories of any type suitable to the local application environment, and can be implemented using any suitable volatile or non-volatile data storage technology such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory, and / or removable memory. For example, the memory 14 can include 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 can include program instructions or computer program code that, when executed by the processor 12, enable the apparatus 10 to perform the tasks described herein.

[0058] In certain example embodiments, the apparatus 10 can also include or be coupled to (internal or external) a drive or port that is configured to accept and read external computer readable storage media, such as an optical disc, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium can store instructions for execution by the processor 12 and / or the apparatus 10 to perform any of the methods illustrated. Figures 1 to 4

[0059] In some example embodiments, the apparatus 10 can also include or be coupled to one or more antennas 15 for receiving downlink signals and for transmitting from the apparatus 10 via an uplink. The apparatus 10 can also include a transceiver 18 configured to transmit and receive information. The transceiver 18 can also include a radio interface (e.g., a modem) coupled to the antenna 15. The radio interface can correspond to one or more of a variety of radio access technologies, including one or more of GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface can include other components, such as filters, converters (e.g., digital-to-analog converters, etc.), symbol demappers, signal shaping components, an inverse fast Fourier transform (IFFT) module, etc., for processing symbols, such as OFDMA symbols, carried by a downlink or uplink.

[0060] ​For example, the transceiver 18 can be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 15 and to demodulate information received via the antenna(s) 15 for further processing by other elements of the apparatus 10. In other example embodiments, the transceiver 18 can be capable of directly transmitting and receiving signals or data. Additionally or alternatively, in some example embodiments, the apparatus 10 can comprise an input and / or output device (I / O device). In certain example embodiments, the apparatus 10 can also comprise a user interface, such as a graphical user interface or a touchscreen.

[0061] In certain example embodiments, the memory 14 stores software modules that provide functionality when executed by the processor 12. The modules can include, for example, an operating system that provides operating system functionality for the apparatus 10. The memory can also store one or more functional modules, such as an application or program, to provide additional functionality for the apparatus 10. The components of the apparatus 10 can be implemented in hardware, or as any suitable combination of hardware and software. According to certain example embodiments, the apparatus 10 can optionally be configured to communicate with the apparatus 20 via a wireless or wired communication link 70 in accordance with any radio access technology, such as NR.

[0062] According to certain example embodiments, the processor 12 and the memory 14 can be included or form part of processing circuitry or controller circuitry. Furthermore, in some example embodiments, the transceiver 18 can be included or form part of transceiver circuitry.

[0063] Figure 9(b) illustrates an apparatus 20 according to certain example embodiments. In certain example embodiments, the apparatus 20 can be a network element, node, host or server in a communication network or serving such a network. For example, the apparatus 20 can be a network element including an AMF, UPF or SMF of a 5GC, for example. In other example embodiments, the apparatus 20 can be a base station, node B, evolved node B (eNB), 5G node B or access point, next generation node B (NG-NB or gNB) and / or WLAN access point associated with a radio access network (RAN) such as a LTE network, 5G or NR. It should be noted that one of ordinary skill in the art would understand that the apparatus 20 can include components or features not shown in Figure 9(b).

[0064] As shown in the example of FIG. 9(b), the apparatus 20 can include a processor 22 for processing information and executing instructions or operations. The processor 22 can be any type of general or specific purpose processor. For example, as examples, the processor 22 can include one or more of a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor based on a multi-core processor architecture. Although a single processor 22 is shown in FIG. 9(b), multiple processors can be used according to other example embodiments. For example, it will be appreciated that, in certain example embodiments, the apparatus 20 can include two or more processors that can form a multi-processor system that can support multiprocessing (e.g., in which case the processor 22 can represent a multi-processor). In certain example embodiments, the multi-processor system can be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0065] According to certain example embodiments, the processor 22 can perform functions associated with operations of the apparatus 20, which can 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 20, including Figures 1 to 8 the processes shown.

[0066] The apparatus 20 can also include or be coupled to (internally or externally) a memory 24, which can be coupled to the processor 22, for storing information and instructions that can be executed by the processor 22. The memory 24 can be one or more memories of any type suitable to the local application environment, and can be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and / or removable memory. For example, the memory 24 can include 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 24 can include program instructions or computer program code that, when executed by the processor 22, enable the apparatus 20 to perform the tasks described herein.

[0067] In certain example embodiments, the apparatus 20 can also include or be coupled to (internally or externally) a drive or port that is configured to accept and read external computer readable storage media, such as an optical disk, USB drive, flash drive, or any other storage medium. For example, the external computer readable storage medium can store instructions for execution by the processor 22 and / or the apparatus 20 to perform Figures 1 to 8A computer program or software of the method shown.

[0068] In certain example embodiments, the apparatus 20 can also include or be coupled to one or more antennas 25 for transmitting and receiving signals and / or data to and from the apparatus 20. The apparatus 20 can also include or be coupled to a transceiver 28 configured to transmit and receive information. The transceiver 28 can include, for example, a plurality of radio interfaces that can be coupled to the antenna(s) 25. The radio interfaces can correspond to one or more of a variety of radio access technologies, including GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, Radio Frequency Identification (RFID), Ultra-Wide Band (UWB), MulteFire, etc. The radio interfaces can include components such as filters, converters (for example, digital-to-analog converters, etc.), mappers, Fast Fourier Transform (FFT) modules, etc., to generate symbols for transmission via one or more downlinks and to receive symbols (for example, via an uplink).

[0069] Accordingly, the transceiver 28 can be configured to modulate information on to a carrier waveform for transmission by the antenna(s) 25 and to demodulate information received via the antenna(s) 25 for further processing by other elements of the apparatus 20. In other example embodiments, the transceiver 28 can be capable of transmitting and receiving signals or data directly. Additionally or alternatively, in some example embodiments, the apparatus 20 can include input and / or output devices (I / O devices).

[0070] In certain example embodiments, the memory 24 can store software modules that provide functionality when executed by the processor 22. The modules can include, for example, an operating system that provides operating system functionality for the apparatus 20. The memory can also store one or more functional modules, such as an application or an app, to provide additional functionality for the apparatus 20. The components of the apparatus 20 can be implemented in hardware, or as any suitable combination of hardware and software.

[0071] According to some example embodiments, the processor 22 and the memory 24 can be included in, or can form part of, processing circuitry or control circuitry. Furthermore, in some example embodiments, the transceiver 28 can be included in, or can form part of, transceiver circuitry.

[0072] As used herein, the term "circuitry" can refer to hardware-only circuitry (e.g., analog and / or digital circuitry), combinations of hardware circuits and software, combinations of analog and / or digital hardware circuits with software / firmware, hardware processor(s) (including digital signal processors) working together to cause an apparatus (e.g., apparatuses 10 and 20) to perform various functions described herein, and / or a hardware circuit and / or processor or portion thereof that uses software during operation, but does not require software to be present during operation. As another example, as used herein, the term "circuitry" can also cover an implementation that has solely hardware circuit or processor (or multiple processors), or solely a portion of hardware circuit or processor, and its accompanying software and / or firmware. The term circuitry can also cover, for example, a baseband integrated circuit in a server, cellular network node or device, or other computing or network device.

[0073] As described above, in certain example embodiments, apparatus 20 can be a network element, node, host or server in a communication network or serving such a network. For example, apparatus 20 can be an AMF, SMF, satellite, base station, Node B, evolved Node B (eNB), 5G Node B or access point, next generation Node B (NG-NB or gNB), and / or WLAN access point associated with a radio access network (RAN) such as an LTE network, 5G or NR. According to certain example embodiments, apparatus 20 can be controlled by memory 24 and processor 22 to perform functions associated with any of the embodiments described herein.

[0074] For example, in certain example embodiments, apparatus 20 can be controlled by memory 24 and processor 22 to receive time domain information at a session management function during a protocol data unit (PDU) session procedure. Apparatus 20 can also be controlled by memory 24 and processor 22 to forward the time domain information to a user plane function for the PDU session procedure. Apparatus 20 can also be controlled by memory 24 and processor 22 to configure the user plane function according to the time domain information to enable determination of a correct mapping between the time domain information and a user equipment or PDU session.

[0075] In other example embodiments, apparatus 20 can be controlled by memory 24 and processor 22 to receive time domain information and mapping information. Apparatus 20 can also be controlled by memory 24 and processor 22 to relate the time domain information and the mapping information to a protocol data unit (PDU) session procedure. Further, apparatus 20 can be controlled by memory 24 and processor 22 to configure a user plane function according to the time domain information or the mapping information to enable determination of a correct mapping between the time domain information and a user equipment or PDU session.

[0076] In other example embodiments, the apparatus 20 can be controlled by the memory 24 and the processor 22 to receive time domain information for a protocol data unit (PDU) session. The apparatus 20 can also be controlled by the memory 24 and the processor 22 to update local information associating the time domain information with a user equipment or a PDU session based on a combination of parameters related to the user equipment. The apparatus 20 can also be controlled by the memory 24 and the processor 22 to receive a time protocol packet. In addition, the apparatus 20 can be controlled by the memory 24 and the processor 22 to determine whether to send the time protocol packet to the user equipment for a given PDU session based on the received time domain information. Moreover, the apparatus 20 can be controlled by the memory 24 and the processor 22 to send the time protocol packet to the user equipment for the given PDU session or perform other forwarding actions on the time protocol packet based on the determination.

[0077] In other example embodiments, the apparatus 20 can be controlled by the memory 24 and the processor 22 to receive time domain information or mapping information for a protocol data unit (PDU) session. The apparatus 20 can also be controlled by the memory 24 and the processor 22 to update local information associating the time domain information or mapping information with a user equipment based on one or more parameters related to the user equipment. The apparatus 20 can also be controlled by the memory 24 and the processor 22 to receive a time protocol packet. In addition, the apparatus 20 can be controlled by the memory 24 and the processor 22 to determine whether to send the time protocol packet to the user equipment for a given PDU session based on the received time domain information or mapping information. Moreover, the apparatus 20 can be controlled by the memory 24 and the processor 22 to send the time protocol packet to the user equipment for the given PDU session or perform other forwarding actions on the time protocol packet based on the determination.

[0078] Further example embodiments can provide a means for performing any of the functions, steps, or procedures described herein. For example, one example embodiment can relate to an apparatus comprising means for receiving time domain information at a session management function during a protocol data unit (PDU) session procedure. The apparatus can also comprise means for forwarding the time domain information to a user plane function for the PDU session procedure. The apparatus can also comprise means for configuring the user plane function according to the time domain information to enable a correct mapping between the time domain information and a user equipment.

[0079] Other example embodiments can relate to an apparatus comprising means for receiving time domain information and mapping information. The apparatus can also comprise means for storing the time domain information and the mapping information. The apparatus can also comprise means for correlating the time domain information and the mapping information. In addition, the apparatus can comprise means for configuring a user plane function according to the time domain information or the mapping information to enable a correct mapping between the time domain information and a user equipment.

[0080] Other example embodiments can relate to a further apparatus comprising means for receiving time domain information for a protocol data unit (PDU) session. The apparatus can further comprise means for updating local information associating the time domain information with a user equipment based on a combination of parameters related to the user equipment. The apparatus can further comprise means for receiving a time protocol packet. Moreover, the apparatus can comprise means for determining whether to send the time protocol packet to the user equipment for a given PDU session based on the received time domain information. The apparatus can further comprise means for sending the time protocol packet to the user equipment for the given PDU session or performing other forwarding actions on the time protocol packet based on the determination.

[0081] Other example embodiments can relate to a further apparatus comprising means for receiving time domain information or mapping information for a protocol data unit (PDU) session. The apparatus can further comprise means for updating local information associating the time domain information or mapping information with a user equipment based on a combination of parameters related to the user equipment. The apparatus can further comprise means for receiving a time protocol packet. Moreover, the apparatus can comprise means for determining whether to send the time protocol packet to the user equipment for a given PDU session based on the received time domain information or mapping information. The apparatus can further comprise means for sending the time protocol packet to the user equipment for the given PDU session or performing other forwarding actions on the time protocol packet based on the determination.

[0082] Certain example embodiments described herein provide several technical improvements, enhancements, and / or advantages. In some example embodiments, TD of interest to a UE can be introduced as part of PDU session management to optimize time information distribution to the UE. Using the available TD, the 5GC can update the user plane configuration to provide only the synchronization message of the TD(s) needed by the UE to the UE. According to certain example embodiments, the UPF can dynamically determine the TD(s) to forward its synchronization message to the UE based on a combination of parameters related to the UE, including, for example, mobility events, location, and traffic inspection.

[0083] A computer program product can include one or more computer- executable components such as those described herein. The computer-executable components can be configured to perform operations when the program is run on a computer. The one or more computer-executable components may, in some example embodiments, be at least one software code or portions thereof. Modifications and configurations needed to implement the functions of the example embodiments can be performed as routines, which can be implemented as added or updated software routines. The software routines can be downloaded to the apparatus.

[0084] As an example, software or computer program code or portions thereof can be in source code form, object code form, or in some intermediate form, and it can be stored in some sort of carrier, distribution medium, or computer readable medium, which can be any entity or device containing or storing the program. Such carriers can include a record medium, computer memory, read-only memory, optical and / or magnetic disc, electrical and / or optical signal, and the like. The computer program can be executed in a single electronic digital computer, or it can be distributed amongst a number of computers. The computer readable medium or computer readable storage medium can be a non-transitory medium.

[0085] In other example embodiments, the functions can be performed by hardware or circuitry included in an apparatus, such as apparatus 10 or apparatus 20, for example by using 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 functions can be implemented as a signal, i.e. an intangible means that can be carried by a electromagnetic signal downloaded from an internet or other network.

[0086] According to certain example embodiments, an apparatus such as a node, device, or corresponding component can be configured as a circuitry, computer, or microprocessor, such as a single-chip computer element, or as a chipset, comprising at least a memory for providing storage capacity to the arithmetic operations and an operation processor for performing the arithmetic operations.

[0087] Those of ordinary skill in the art will readily understand that the present application as discussed above can be practiced with the different orders of process and / or hardware elements than those disclosed. Since embodiments of the application can be implemented in various ways, the application should not be limited to the particular examples set forth in the above descriptions. While the above examples have been described with respect to 5G NR and LTE technologies, the above examples can also be applied to any other current or future 3GPP technologies, such as LTE-Advanced and / or fourth generation (4G) technologies.

[0088] Partial Glossary

[0089] 5GC 5G core

[0090] 5GS 5G system

[0091] AF application function

[0092] AMF access and mobility management function

[0093] CN core network

[0094] DN data network

[0095] DS-TT device-side TSN translator

[0096] eNB enhanced NodeB

[0097] GM grand master

[0098] gNB 5G or next generation NodeB

[0099] gPTP generic precise time protocol

[0100] LTE long term evolution

[0101] NAS non-access stratum

[0102] NR new radio

[0103] NW-TT network-side TSN translator

[0104] PCF policy control function

[0105] RAN radio access network

[0106] RRC radio resource control

[0107] SIB system information block

[0108] SMF session management function

[0109] TD time domain

[0110] TSC time sensitive communication

[0111] TSN time sensitive networking

[0112] UE user equipment

[0113] UL uplink

[0114] UPF user plane function

Claims

1. A method of communication, comprising: Receive time-domain information for Protocol Data Unit (PDU) sessions; Local information is updated based on one or more parameters related to the user equipment, the local information associating the time-domain information with the user equipment or the PDU session; Receive multiple time protocol packets, where the corresponding time protocol packets are General Precision Time Protocol (gPTP) messages; Based on the received time-domain information, the User Plane Function (UPF) determines whether to send the corresponding time protocol packets of the plurality of time protocol packets to the User Equipment for a given PDU session according to the updated local information. When the signal is stronger in the target cell than in the source cell, the UPF dynamically determines whether to send the corresponding time protocol packets of the plurality of time protocol packets to the User Equipment based on the User Equipment changing its serving cell. The UPF checks the plurality of time protocol packets based on the time-domain TD number and forwards the corresponding time protocol packets to the matching PDU session configured by the UPF. as well as Based on the determination, the corresponding time protocol packets of the plurality of time protocol packets are forwarded to the user equipment for the matching PDU session.

2. The method of claim 1, wherein the one or more parameters include information relating to one or more of the location or business checks.

3. The method of claim 1, wherein the time protocol group includes time information related to the clock domain number.

4. The method of claim 1, wherein the update includes maintaining a local table having an association between the time-domain information and the PDU session.

5. A device for communication, comprising: At least one processor; as well as At least one memory, including computer program code, The at least one memory and the computer program code are configured, together with the at least one processor, to make the device at least: Receive time-domain information for Protocol Data Unit (PDU) sessions; Local information is updated based on one or more parameters related to the user equipment, the local information associating the time-domain information with the user equipment or the PDU session; Receive multiple time protocol packets, where the corresponding time protocol packets are General Precision Time Protocol (gPTP) messages; Based on the received time-domain information, the User Plane Function (UPF) determines whether to send the corresponding time protocol packets of the plurality of time protocol packets to the User Equipment for a given PDU session according to the updated local information. When the signal is stronger in the target cell than in the source cell, the UPF dynamically determines whether to send the corresponding time protocol packets of the plurality of time protocol packets to the User Equipment based on the change of the serving cell of the User Equipment. The UPF checks the plurality of time protocol packets based on the time-domain TD number for forwarding the corresponding time protocol packets to the matching PDU session configured by the UPF. as well as Based on the determination, the corresponding time protocol packets of the plurality of time protocol packets are forwarded to the user equipment for the matching PDU session.

6. The apparatus of claim 5, wherein the one or more parameters include information relating to one or more of the location or business checks.

7. The apparatus of claim 5, wherein the time protocol group includes time information related to the clock domain number.

8. The apparatus of claim 5, wherein the update includes maintaining a local table having an association between the time-domain information and the PDU session.

Images