Enabling time synchronization and time resiliency services through subscription

Abstract

A method and apparatus are provided for authorizing a time synchronization service request or a time synchronization service request with time resilience from an application function in a communication system. A time synchronization service network function supporting a time synchronization service in a communication system receives a request originating from an application function (AF) requesting a time synchronization service or alternatively a time synchronization service with time resilience for a UE or a group of UEs. The time synchronization service network function obtains subscription data for the UE or group of UEs indicating whether a request for time synchronization from the AF is authorized. If authorized, the request is allowed to commence, otherwise the request from the AF is rejected.

Description

[Technical field]

[0001] Related Applications This application claims the benefit of Provisional Patent Application Serial No. 63 / 322301, filed March 22, 2022, the disclosure of which is incorporated herein by reference in its entirety.

[0002] The present disclosure relates to time synchronization services in telecommunications systems. [Background technology]

[0003] In general, all terms used herein shall be interpreted according to their ordinary meaning in the relevant technical field unless a different meaning is expressly given and / or implied from the context in which they are used. All references to a / an / the element, apparatus, component, means, step, etc. shall be openly interpreted as referring to at least one instance of that element, apparatus, component, means, step, etc., unless expressly stated otherwise. The steps of the methods disclosed herein need not be performed in the exact order disclosed, unless a step is expressly described as following or preceding other steps, and / or unless it is implicitly described that a step must follow or precede other steps. Any feature of the embodiments disclosed herein may be applied to other embodiments, where appropriate. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the enclosed embodiments will become apparent from the following description.

[0004] The 3rd Generation Partnership Project (3GPP®) Technical Specifications (TS) 23.501 V17.3.0 and TS 23.502 V17.3.0 define aspects related to fifth generation systems (5G systems (5GS)) functionality that enable time-sensitive communications and time synchronization services. For example, to achieve time synchronization in 5G systems, 3GPP TS 23.501 V17.3.0 describes that 5GS is capable of operating with one or more Point Precision Time Protocol (PTP) instances, with each PTP instance capable of operating as follows: 1) A time-aware system as described in IEEE standard 802.1AS; 2) Boundary Clocks as described in IEEE Standard 1588, as provisioned by profiles supported by 3GPP specifications, including the SMPTE Profile for Use of IEEE Std 1588 Precision Time Protocol (PTP) in Professional Broadcast Applications ST 2059-2:2015; 3) Peer-to-peer transparent clocks as described in IEEE Standard 1588, as provisioned by profiles supported by 3GPP specifications, including the SMPTE Profile for Use of IEEE Std 1588 Precision Time Protocol in Professional Broadcast Applications ST 2059-2:2015; 4) An end-to-end transparent clock as described in IEEE Standard 1588 as provisioned by profiles supported by 3GPP specifications, including the SMPTE Profile for Use of IEEE Std 1588 Precision Time Protocol in Professional Broadcast Applications ST 2059-2:2015. According to 3GPP TS23.501 V17.3.0 clauses 5.27.1.8 and 5.27.1.9, time synchronization services can also be enabled by using an access stratum time allocation method, where an application function (AF) can influence the timing allocation between the RAN and the UE, and the UE / DS-TT can distribute timing information externally via implementation specific means.

[0005] Figure 1 shows the 3GPP Release 17 reference points for 5G systems enabling time-sensitive communication and time synchronization. The architecture includes a device-side Time-Sensitive Network (TSN) translator (DS-TT) and a network-side TSN translator (NW-TT). The TSN translator function provides interoperability between TSN and 5G systems in both the user and control planes. The architecture also includes a Time-Sensitive Communication (TSC) and Time Synchronization Function (TSCTSF) that controls the DS-TT and NW-TT for common (g)PTP-based time synchronization services based on IEEE 802.1AS. As part of 3GPP Release 18, technical report TR23.700-25 V.0.1.0 on timing resiliency, TSC and URLLC enhancements has been produced. Summary of the Invention

[0006] Currently, there is a challenge. Specifically, 3GPP Release 18 TR23.700-25 lists many key issues to be considered. Key issue #3 is about controlling time synchronization based on UE subscriptions, proposing the introduction of subscription parameters for time synchronization and its implementation in 5GS. The problem is that existing solutions do not address how to control time resiliency using time synchronization.

[0007] Certain aspects of the present disclosure and embodiments thereof may provide solutions to the aforementioned problems or other problems. Solution embodiments described herein propose to use subscription data as an enabler of time synchronization services in 5GS.

[0008] Although the embodiments described herein are described in the context of using timing synchronization architectures and services provided in 5G systems (5GS), it will be apparent that the solution may be applied to any system supporting such services, including, but not limited to, future 6G systems.

[0009] Embodiments of the present disclosure provide a solution that enables control of timing synchronization and more complex timing resiliency services.

[0010] According to some embodiments, a method is provided that is implemented in a time synchronization service network function (e.g., a TSCTSF in a 5G system) and for authorizing a request for a time synchronization service or a time synchronization service with time resiliency from an application function (AF).

[0011] The method includes receiving a request for time synchronization for a UE or group of UEs originating from an Application Function (AF). The request may be received via a Network Exposure Function (NEF) or directly from the AF. Alternatively, the request for time synchronization service from the AF further includes a request for time synchronization with time resiliency service. The request for time synchronization or time synchronization with time resiliency may include parameters related to the requested timing resiliency service.

[0012] The method further includes obtaining subscription data for the UE or group of UEs, the subscription data indicating whether a request for time synchronization from the AF is allowed to initiate. For example, the time synchronization service network function obtains the subscription data by sending a request to a User Data Management (UDM) node requesting subscription data related to a time synchronization service or time synchronization with time resilience service (if requested by the AF) and receiving subscription data indicating whether the time synchronization service is allowed or, alternatively, whether time synchronization with time resilience service is allowed. In one example, the subscription data may include an indication that the time synchronization service or time synchronization with time resilience service is enabled or disabled. Alternatively, if the subscription data includes time synchronization or time synchronization with time resilience that matches the request from the AF, the time synchronization network function may determine authorization of the request from the AF if the request matches the subscription.

[0013] The method further comprises determining from the obtained subscription data for the UE or UE group that a request for time synchronization or alternatively time synchronization with time resilience from the AF is not permitted, in which case the time synchronization service network function rejects the request for time synchronization service or time synchronization with time resilience received from the AF. A rejection message is sent back to the AF. In another example, if the time synchronization service network function determines that the subscription data permits a request for time synchronization service / time synchronization with time resilience from the AF, it continues activating / providing the time synchronization service or time synchronization with time resilience for the UE or UE group.

[0014] In one embodiment, the time synchronization service network function further subscribes with the user data management node to receive changes to the subscription with the time synchronization or time synchronization with time resilience service. In another example, the time synchronization service network function can subsequently receive a notification from the UDM or AF to disable the time resilience service and, upon receiving the notification, deactivate the time resilience service.

[0015] In another embodiment, the time synchronization service network function performs the step of receiving a notification from the UDM or AF to disable the time synchronization service, and upon receiving the notification, deactivates the time synchronization service and timing resiliency services if timing resiliency was previously allowed and / or activated.

[0016] In one embodiment, a node implementing a time synchronization service network function is configured to implement any of the embodiments described herein.

[0017] In another embodiment, a node is provided that comprises one or more processors and a memory for storing instructions that, when executed by the one or more processors of the node implementing a time synchronization service, perform any of the embodiments described herein.

[0018] In another embodiment, a computer-readable medium comprising program instructions that cause one or more processors of a node implementing a time synchronization service to perform any of the embodiments described herein. [Brief description of the drawings]

[0019] The accompanying drawing figures, which are incorporated in and constitute a part of this specification, illustrate several aspects of the disclosure and, together with the description, serve to explain the principles of the disclosure.

[0020] [Figure 1]FIG. 1 illustrates an exemplary embodiment in which the cellular communication system is a fifth generation (5G) system (5GS).

[0021] [Diagram 2] 1 illustrates an example of a cellular communication system in which embodiments of the present disclosure can be implemented.

[0022] [Diagram 3] FIG. 1 shows a service-based interface (SBI) architecture for a (5G) system (5GS).

[0023] [Figure 4] 1 illustrates a procedure according to one embodiment of the present disclosure.

[0024] [Figure 5A] 4 illustrates another procedure according to another embodiment of the present disclosure.

[0025] [Figure 5B] 1 illustrates a flowchart of a method in a time synchronization service network function according to some embodiments of the present disclosure.

[0026] [Figure 6] FIG. 2 is a schematic block diagram of an example embodiment of a network node; [Figure 7] FIG. 2 is a schematic block diagram of an example embodiment of a network node; [Figure 8] FIG. 2 is a schematic block diagram of an example embodiment of a network node; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which: However, other embodiments are within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments set forth herein, but rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0028] Wireless Node: As used herein, a "wireless node" is either a wireless access node or a wireless communication device.

[0029] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a radio access network (RAN) of a cellular communications network that operates to transmit and / or receive signals wirelessly. Examples of radio access nodes include, but are not limited to, base stations (e.g., a New Radio (NR) base station (gNB) in a 3rd Generation Partnership Project (3GPP) fifth generation (5G) NR network, or an enhanced or evolved Node B (eNB) in a 3GPP long term evolution (LTE) network), high power or macro base stations, low power base stations (e.g., micro base stations, pico base stations, home eNBs, etc.), relay nodes, network nodes that perform some of the functions of a base station (e.g., a network node that performs a gNB central unit (gNB-CU), a network node that performs a gNB distributed unit (gNB-DU), etc.), or a network node that performs some of the functions of another radio access node.

[0030] Core Network Node: As used herein, a "core network node" refers to any kind of node in a core network, or a node / server / distributed server / dedicated platform that implements one or more core network functions, also referred to as network functions. Some examples of network functions include, for example, a mobility management entity (MME), a packet data network gateway (P-GW), a service capability exposure function (SCEF), a home subscriber server (HSS), etc. Some other examples of network functions include nodes that implement an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), an authentication server function (AUSF), a network slice selection function (NSSF), a network exposure function (NEF), a network function (NF) repository function (NRF), a policy control function (PCF), a unified data management (UDM), a TSCTSF, etc. In general, a network function can be implemented as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform (e.g., cloud infrastructure). Note that the UPF may include the NW-TT.

[0031] Communication Device: As used herein, a "communication device" refers to any type of device that can access an access network. Examples of communication devices include, but are not limited to, mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical appliances, media players, cameras, or any type of consumer electronics, such as televisions, radios, lighting fixtures, tablet computers, laptops, personal computers (PCs), etc. A communication device may be a portable, handheld, computer-embedded, or vehicle-mounted mobile device capable of communicating voice and / or data over a wireless or wired connection. A communication device may include or connect to a DS-TT.

[0032] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that accesses (i.e., receives service from) a wireless network (e.g., a cellular network). Examples of wireless communication devices include, but are not limited to, user equipment devices (UEs) in 3GPP networks, machine type communication (MTC) devices, Internet of Things (IoT) devices, etc. Such wireless communication devices may be, or may be integrated into, mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting fixtures, tablet computers, laptops, PCs, etc. Wireless communication devices may be portable, handheld, computer-embedded, or vehicle-mounted mobile devices that allow for communication of voice and / or data over a wireless connection. Wireless communication devices may include or connect to DS-TT.

[0033] Network Node: As used herein, a "network node" refers to a node that is part of the RAN or core network of a cellular communications network / system.

[0034] It should be noted that 3GPP terminology or terminology similar to 3GPP terminology is often used herein to focus on 3GPP cellular communication systems, however, the concepts disclosed herein are not limited to 3GPP systems.

[0035] In the description herein, reference may be made to the term "cell", however, it is important to note that, particularly with regard to 5G_NR concepts, beams may be used instead of cells, and therefore the concepts described herein are equally applicable to both cells and beams.

[0036] FIG. 2 illustrates an example of a cellular communication system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communication system 100 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC), although the present disclosure is not limited thereto. In this example, the RAN includes NR base stations (gNBs) and optionally Next Generation eNBs (ng-eNBs) (e.g., LTE RAN nodes connected to 5GC) in 5GS, and includes base stations 102-1 and 102-2 that control corresponding (macro) cells 104-1 and 104-2. The base stations 102-1 and 102-2 are generally referred to herein collectively as a plurality of base stations 102 and individually as a base station 102. Similarly, the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as a plurality of (macro) cells 104 and individually as a (macro) cell 104. The RAN may also include a number of low power nodes 106-1-106-4 that control corresponding small cells 108-1-108-4. The low power nodes 106-1-106-4 may be small base stations (such as pico or femto base stations) or RRHs, etc. Notably, although not shown, one or more of the small cells 108-1-108-4 may alternatively be provided by the base station 102. The low power nodes 106-1-106-4 are generally collectively referred to herein as a number of low power nodes 106 and individually referred to as a low power node 106. Similarly, the small cells 108-1-108-4 are generally collectively referred to herein as a number of small cells 108 and individually referred to as a small cell 108. The cellular communication system 100 also includes a core network 110, referred to as 5GC in 5G systems (5GS). The base stations 102 (and optionally the low power nodes 106 ) are connected to a core network 110 .

[0037] The base station 102 and low power node 106 serve wireless communication devices 112-1 through 112-5 in corresponding cells 104 and 108. The wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as a wireless communication device 112. In the following description, the wireless communication devices 112 are often UEs, and as such may also be referred to herein as UEs 112, although the disclosure is not limited thereto.

[0038] As shown, Figure 1 illustrates a wireless communication system represented as a 5G system architecture that enables time-sensitive communication and time synchronization, where the interaction between any two NFs is comprised of core network functions represented by point-to-point reference points / interfaces. Figure 2 can be considered one particular implementation of the system 100 of Figure 2.

[0039] From the access side, the 5G system architecture shown in Figure 1 consists of multiple UEs 112 connected to either the RAN 102 or the access network (AN), as well as the AMF 200. Typically, the RAN (AN) 102 consists of a base station, such as an eNB or a gNB. From the core network side, the multiple NFs of the 5GC shown in Figure 1 include the UDM 206, the AMF 200, the SMF 208, the PCF 210, the TSCTSF (400), the application function (AF) 212, the user data record (UDR, not shown), the NSSF, and the AUSF.

[0040] Reference point representations of 5G network architecture are used to formulate detailed call flows in normative standardization. The N1 reference point is defined to carry signaling between the UE 112 and the AMF 200. Reference points connecting between the AN 102 and the AMF 200 and between the AN 102 and the UPF 214 are defined as N2 and N3, respectively. There is a reference point N11 between the AMF 200 and the SMF 208, which means that the SMF 208 is at least partially controlled by the AMF 200. N4 is used by the SMF 208 and the UPF 214 to configure the UPF 214 using control signals generated by the SMF 208, so that the UPF 214 can report its status to the SMF 208. N9 is a reference point for connections between different UPFs 214. N30 is a reference point between the PCF 210 and the NEF. N33 is a reference point between the NEF and the AF 212. N84 is a reference point between the TSCTSF and the PCF. N85 is the reference point between TSCTSF and NEF. N86 is the reference point between TSCTSF and AF (not shown).

[0041] 5GC networks aim to separate UP and CP. UP carries user traffic and CP carries signaling within the network. In Figure 1, UPF 214 is in UP, which can host NW-TT, and all other NFs, namely AMF 200, SMF 208, PCF 210, AF 212, and UDM 206, are in CP. Separating UP and CP ensures that each plane resource is scaled independently. It also allows UPF to be distributed separately from CP functions. In this architecture, UPF can be placed very close to UE to reduce round trip time (RTT) between UE and data network for some applications that require low latency.

[0042] The core 5G network architecture consists of modularized functions. For example, AMF200 and SMF208 are independent functions within the CP. The separated AMF200 and SMF208 allow independent evolution and expansion. Other CP functions, such as PCF210 and AUSF204, can also be separated as shown in Figure 2. The modularized function design allows the 5GC network to flexibly support various services.

[0043] Each NF interacts directly with other NFs. It is possible to use intermediate functions to route messages from one NF to another. In CP, a set of interactions between two NFs is defined as a service, allowing reuse. This service allows supporting modularity. UP supports interactions such as forwarding operations between different UPFs.

[0044] Figure 3 illustrates a 5G network architecture that uses service-based interfaces between NFs in a CP, rather than the point-to-point reference points / interfaces used in the 5G network architecture of Figure 1. However, the NFs described above with reference to Figure 1 correspond to the NFs illustrated in Figure 3. The services, etc. that an NF provides to other authorized NFs can be exposed to authorized NFs through service-based interfaces. In Figure 3, the service-based interfaces are indicated by the letter "N" following the name of the NF, e.g., Namf for the service-based interface of the AMF 200, Nsmf for the service-based interface of the SMF 208, etc. Although not explicitly shown in Figure 1, it should be clarified that all NFs depicted in Figure 1 can interact with the NEFs and NRFs of Figure 3 as needed.

[0045] Some characteristics of the NFs shown in Figures 1 and 3 can be explained in the following way: The AMF 200 provides UE-based authentication, authorization, mobility management, etc. The AMF 200 is independent of the access technology, so even a UE 112 using multiple access technologies is essentially connected to a single AMF 200. The SMF 208 is responsible for session management and assigns an Internet Protocol (IP) address to the UE. It also selects and controls the UPF 214 for data forwarding. If the UE 112 has multiple sessions, a different SMF 208 can be assigned to each session to manage them separately and possibly provide different features for each session. The AF 212 provides information about the packet flow to the PCF 210, which is responsible for policy control, to support QoS. The AF 212 can also interact through the NEF using a public API to request exposed services and can interact directly with the TSCTSF 400 to provide individual traffic pattern parameters, or indirectly through the NEF if the AF is a third party. The TSCTSF 400 creates a TSC assistance container based on the received individual traffic pattern parameters.

[0046] It should be noted that although the present specification describes the use of 5G systems to enable time sensitive communications and time synchronization, other supporting systems, whether 6G or other systems, may be used. Also, while the embodiments are described using 5G NFs TSCTSF and UDM, it will be apparent to one skilled in the art that the embodiments described herein also apply to equivalent functions in other systems.

[0047] Certain aspects of the present disclosure and embodiments thereof for controlling timing resiliency through subscriptions may provide solutions to the above-mentioned or other problems. Embodiments of the solutions described herein are based on the following principles: -Added new subscription data type for time synchronization services. The new subscription data type includes both time synchronization and timing resiliency services. both A new time synchronization subscription data type is provisioned in the UDM / UDR for a UE or UE group and the corresponding Data Network Name (DNN) / Network Slice (S-NSSAI). - Upon receiving an AF request for time synchronization from the AF212 (via the NEF if the AF is a third party), which may include parameters related to timing resiliency services, the TSCTSF400 uses the Nudm_SDM_Get service operation to obtain subscription data regarding time synchronization for a UE or UE group (based on the AF request). -When using Nudm_SDM_Get, the TSCTSF400 contains the key for its NF identifier (NF ID), time synchronization subscription data type, DNN / S-NSSAI, and subscription data type: SUPI / internal group identifier (if the AF212 is an operator domain), or GPSI / external group identifier (if a third-party AF). If the TSCTSF 400 receives subscription data (from the UDM) corresponding to the requested service, the TSCTSF 400 proceeds with activating the service as defined above. - If the subscription data does not correspond to a service requested by the AF, the TSCTSF does not activate the service.

[0048] Additionally, the TSCTSF 400 may subscribe to UDMs (using the Nudm_SDM_Subscribe service operation) to obtain changes in time synchronization and timing resiliency subscription data: -If a subscription for a time synchronization service has been added, the TSCTSF400 proceeds with activating the service; - if a timing resiliency subscription is added in addition to a time synchronization subscription, the time synchronization service is updated to support timing resiliency or timing resiliency is activated, respectively; - if a subscription to a time synchronization is removed, the corresponding service is deactivated and timing resiliency is also deactivated if it is active (unless AF212 has requested deactivation first or the time expiration has expired first); - If only timing resiliency is removed, this service is deactivated (unless AF requests deactivation first or the time expiration time expires first). -The corresponding response is provided to the AF212. -When using Nudm_SDM_subscribe, the TSCTSF400 contains a time synchronization subscription data type indicating time synchronization and / or time resiliency data, a DNN / S-NSSAI, and a key for the subscription data type: SUPI / internal group identifier (if the AF212 is an operator domain), or GPSI / external group identifier (if a third-party AF). When the time synchronization service is deactivated (either via an AF request or if the subscription to the time synchronization is removed in the UDM), the TSCTSF400 can unsubscribe to the UDM (using the Nudm_SDM_Unsubscribe service operation) if it was previously subscribed to the UDM.

[0049] UDM and TSCTSF Interaction FIG. 4 illustrates one embodiment of the present disclosure in which the TSCTSF 400 interacts with the UDM to obtain time synchronization and time resilience subscriptions and subscribe to changes thereto.

[0050] The TSCTSF requests time synchronization data and / or time resiliency synchronization data during service activation, as described in subsequent embodiments. The TSCTSF uses an application programming interface (API) with a UDM (e.g., Nudm_SDM_Get) to request a subscription to the service. The TSCTSF includes its NF ID, a (new) time synchronization subscription data type (time synchronization and / or time resiliency), a DNN / S-NSSAI, and a key for the subscription data type: SUPI / internal group identifier (if the AF is an operator domain), or GPSI / external group identifier (if a third-party AF).

[0051] If the TSCTSF receives (from the UDM) subscription data corresponding to a service requested by an AF (i.e., an AF requesting time synchronization that may include additional time resiliency), the TSCTSF proceeds with the activation of the service as described below. If the subscription data does not correspond to a service requested by the AF (requested directly or via the NEF), the TSCTSF shall not activate the service requested by the AF. In addition to obtaining subscriptions, the TSCTSF may subscribe to UDMs (using the Nudm_SDM_Subscribe service operation) to obtain changes to the time synchronization and timing resiliency subscription data: -If a subscription for a time synchronization service was added, TSCTSF proceeds with activating the service; - if a timing resiliency subscription is added in addition to a time synchronization subscription, the time synchronization service is updated to support timing resiliency or timing resiliency is activated, respectively; - if a subscription to a time synchronization is removed, the corresponding service is deactivated and timing resiliency is also deactivated if it is active (unless the AF requested deactivation first or the time expiration time expired first); - If only timing resiliency is removed, this service is deactivated (unless AF requests deactivation first or the time expiration time expires first). -The corresponding response is provided to the AF. Any changes to subscription data are indicated by the UDM to the TSCTSF via the notification API Nudm_SDM_notify. A change may be to authorize a time synchronization or time resiliency service that was not previously authorized. The API can also deauthorize, i.e., remove, a service, as described above.

[0052] When the TSCTSF subscribes to time synchronization and time resiliency subscription changes, for example using Nudm_SDM_subscribe, the TSCTSF includes the key for the time synchronization subscription data type, the DNN / S-NSSAI, and the subscription data type: SUPI / internal group identifier (if the AF is an operator domain), or GPSI / external group identifier (if a third-party AF).

[0053] Any changes to the time synchronization and / or time resilience subscriptions are provided to the TSCTSF via notification messages from the UDM.

[0054] When the time synchronization service is deactivated (either by an AF request or if the subscription to the time synchronization is removed in the UDM), the TSCTSF unsubscribes for notifications from the UDM if it was subscribed to the UDM.

[0055] Time Synchronization Activation Procedure The time synchronization and time resiliency procedures can be activated using a similar procedure as described in 3GPP TS 23.502 section 4.15.9 Time Synchronization Activation. 3GPP TS 23.502 states that the AF uses the time synchronization activation procedure to activate, modify or deactivate a 5GS (g) Precision Time Protocol (gPTP) instance (see section 4.15.9.3). In this case, the time distribution from the RAN to the UE is influenced by the AF, and the UE / DS-TT may distribute timing information externally by implementation specific means, but not necessarily PTP (see section 4.15.9.4 of 3GPP TS 23.502).

[0056] In this embodiment shown in FIG. 5A, the AF may activate a time synchronization service or a time synchronization service with a time resilience service, such as using a Nnef_TimeSynchronization_ConfigCreate service operation.

[0057] Step 1: The AF calls the Nnef_TimeSynchronization_ConfigCreate service operation for a UE or a group of UEs to create a time synchronization service configuration for a PTP instance to request a time synchronization service. The request includes information indicating time synchronization and may include parameters related to the time resiliency service (if the request is for a time synchronization service with time resiliency service). The request may include a subscription correlation ID and a user plane node ID as references to the UE and the target of the AF session.

[0058] Step 2: The NEF (optional, only if the AF is a third party) authorizes the request. After successful authorization, the NEF calls the corresponding TSCTSF and Ntsctsf_TimeSynchronization_ConfigCreate service operations with the parameters received from the AF. AFs that are part of the operator's trust domain can directly call the service on TSCTSF.

[0059] Step 3a: The TSCTSF interacts with the UDM to obtain time synchronization and, optionally, time resilience subscription data.

[0060] Step 3b: TSCTSF receives subscription data for time synchronization. - if the subscription data indicates that the subscription to the time synchronization service is valid, the TSCTSF proceeds with activation of the service; - If the subscription data indicates a subscription for timing resiliency and timing resiliency services are enabled or authorized in addition to time synchronization, the time synchronization services are updated to support timing resiliency or timing resiliency is enabled, respectively. However, a UDM may authorize time synchronization services while not authorizing time resiliency. Time resiliency services are authorized only if time synchronization services are authorized.

[0061] Step 3: TSCTSF responds with a Ntsctsf_TimeSynchronization_ConfigCreate response, which includes the PTP instance reference.

[0062] Step 4: The remaining activation steps are as described in TS 23.502, V.17.3.0, section 4.15.9.3, with the modification that if a time resilience subscription is provided by the UDM indicating that time resilience is enabled, then the time synchronization service is updated to support time resilience or time resilience is activated.

[0063] In step 3a or a subsequent step (not shown in the figure), the TSCTSF may subscribe to the UDM for any changes in subscriptions related to time synchronization and time resiliency.

[0064] FIG. 5B shows a method implemented in a time synchronization service network function (e.g., a TSCTSF in a 5G system) according to some embodiments.

[0065] In step 500B, the time synchronization service network function performs a step of receiving a request for time synchronization for a UE or a group of UEs originating from an application function (AF). The request may be received via a network exposure function (NEF) or directly from the AF. Alternatively, the request for time synchronization service from the AF further includes a request for time synchronization with time resiliency service. The request for time synchronization or time synchronization with time resiliency may include parameters related to the requested timing resiliency service.

[0066] In step 510B, the time synchronization service network function performs a step of obtaining subscription data for a UE or UE group, which indicates whether a request for time synchronization from the AF is allowed to proceed. For example, the time synchronization service network function obtains the subscription data by sending a request to a User Data Management (UDM) node requesting subscription data related to a time synchronization service or time synchronization with time resilience service (if requested by the AF) and receiving subscription data indicating whether the time synchronization service is allowed or whether time synchronization with time resilience service is allowed. The subscription data may include an indication that the time synchronization service or time synchronization with time resilience service is enabled or disabled. Alternatively, if the subscription data includes time synchronization or time synchronization with time resilience that matches the request from the AF, the time synchronization network function may determine authorization of the request from the AF if the request matches the subscription.

[0067] In step 520B, if the time synchronization service network function determines from the subscription data of the UE or UE group obtained in step 510B that the request for time synchronization or time synchronization with time resilience from the AF should not be allowed, the time synchronization service network function rejects the request for time synchronization received from the AF. A rejection message may be sent back to the AF. On the other hand, if the time synchronization service network function determines that the subscription data approves the request for time synchronization service / time synchronization service with time resilience from the AF, it proceeds to activate / provide the time synchronization service or time synchronization service with time resilience for the UE or UE group (step 530B).

[0068] In one embodiment, the time synchronization service network function further subscribes with the user data management node to receive changes to the subscription for the time synchronization or the time synchronization and time resilience services. In another example, the time synchronization service network function can subsequently receive a notification from the UDM or AF to disable the time resilience service and, upon receiving the notification, deactivate the time resilience service.

[0069] In another embodiment, the time synchronization service network function performs the step of receiving a notification from the UDM or AF to disable the time synchronization service, and upon receiving the notification, deactivates the time synchronization service and, if timing resiliency was previously allowed and / or enabled (if time synchronization with timing resiliency was previously enabled), also deactivates the timing resiliency service.

[0070] FIG. 6 is a schematic block diagram of a network node 800 according to some embodiments of the present disclosure. Optional functions are represented by dashed boxes. The network node 800 may be, for example, a core network node implementing an NF (e.g., AMF 200, SMF 206, TSCTSF 400, UDM, UDR, AF, UPF, etc.). As shown, the network node 800 includes one or more processors 804 (e.g., a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), and / or the like), a memory 806, and a network interface 808. The one or more processors 804 are also referred to herein as processing circuits. The one or more processors 804 operate to provide one or more functions of the network node 800 described herein (e.g., one or more functions of the AMF 200, SMF 206, TSCTSF 400, UDM, UDR, AF, UPF, etc. described herein). In some embodiments, the functionality(s) is implemented in software that is stored in memory 806 and executed by one or more processors 804, for example.

[0071] 7 is a schematic block diagram illustrating a virtualized embodiment of a network node 800 according to some embodiments of the present disclosure. Again, optional features are represented by dashed boxes. As used herein, a "virtualized" network node is an embodiment of a network node 800 in which at least a portion of the functionality of the network node 800 is implemented as virtual component(s) (e.g., via virtual machine(s) running on physical processing node(s) in the network). As shown, in this example, the network node 800 includes one or more processing nodes 900 coupled to or included as part of a network 902. Each processing node 900 includes one or more processors 904 (e.g., CPU, ASIC, FPGA, etc.), memory 906, and a network interface 908. In this example, the functions 910 of network node 800 described herein (e.g., one or more functions such as AMF 200, SMF 206, TSCTSF 400, UDM, UDR, AF, UPF, etc. described herein) are implemented on one or more processing nodes 900 or distributed in any desired manner across two or more processing nodes 900. In some particular embodiments, some or all of the functions 910 of network node 800 described herein are implemented as virtual components executed by one or more virtual machines implemented in virtual environment(s) hosted by processing node 900.

[0072] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform functions of a network node 800 or a node that implements one or more of the functions 910 of the network node 800 in a virtual environment (e.g., processing node 900) in accordance with any of the embodiments described herein. In some embodiments, a carrier is provided that includes the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a wireless signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0073] 8 is a schematic block diagram of a network node 800 according to some other embodiments of the present disclosure. The network node 800 includes one or more modules 1000, each implemented in software. The modules 1000 provide the functionality of the network node 800 described herein. This discussion is equally applicable to the processing node 900 of FIG. 7, where the modules 1000 may be implemented in one of the processing nodes 900 or distributed across multiple processing nodes 900.

[0074] The relevant steps, methods, features, functions, or advantages disclosed herein may be performed through one or more functional units or modules of one or more virtual devices. Each virtual device may be composed of a number of these functional units. These functional units may be implemented through processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware including digital signal processors (DSPs), special purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as ROM (read only memory), RAM (random access memory), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for executing one or more telecommunications and / or data communication protocols, as well as instructions for executing one or more techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional units to perform functions corresponding to the respective functional units according to one or more embodiments of the present disclosure.

[0075] Although the steps in the figures may indicate a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such orders are exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, or duplicate certain operations).

[0076] Some exemplary embodiments of the present disclosure are as follows: 1. A method in a first network node implementing a first network function for supporting a time synchronization service in a communication system, the method comprising: receiving a request for time synchronization for a UE or a group of UEs originating from an application function (AF), the request may include time resiliency service related parameters; · Sending requests to a User Data Management (UDM) node to request subscription data related to time synchronization and / or time resiliency services; receiving subscription data indicating whether a time synchronization service or a time synchronization with a time resiliency service is permitted; Activating a time synchronization service or a time synchronization service with time resiliency service in accordance with the subscription data.

[0077] The method according to embodiment 1, further comprising subscribing at the user data management node to receive any changes to a subscription to a time synchronization and / or time resiliency service.

[0078] The method according to embodiment 1 or 2, further comprising: receiving a notification from the UDM or the AF to disable the time resilient service; and deactivating the time resilient service when the notification is received.

[0079] The method according to embodiment 1 or 2, further comprising: receiving a notification from the UDM or the AF to disable a time synchronization service; and, when the notification is received, deactivating the time synchronization service and the time resiliency service if time resiliency was previously allowed and / or activated.

[0080] A node implementing a first network function configured to implement any one of embodiments 1 to 4.

[0081] A node comprising one or more processors and a memory for storing instructions that, when executed by the one or more processors, perform any of embodiments 1 to 4.

[0082] A computer-readable medium comprising program instructions for causing a computer to carry out the method of any one of embodiments 1 to 4.

[0083] 1. A method in a second network node implementing a second network function for supporting a subscription to a time synchronization service in a communication system, the method comprising: receiving a request to provide subscription data related to time synchronization with a time synchronization service or a time resilience service for a UE or a group of UEs to a first network node; Sending subscription data indicating whether a time synchronization service or a time synchronization with time resiliency service is allowed.

[0084] The method according to embodiment 8, further comprising receiving a subscription for reporting any changes to a time synchronization or time synchronization subscription with a time resiliency service.

[0085] The method according to embodiment 8 or 9, further comprising sending a notification to disable the time resilience service or the time synchronization service, or both.

[0086] A node implementing a second network function configured to implement any of embodiments 8 to 10.

[0087] A node comprising one or more processors and a memory for storing instructions that, when executed by the one or more processors, perform any of embodiments 8 to 10.

[0088] A computer-readable medium comprising program instructions for causing a computer to carry out the method of any one of embodiments 8 to 10.

[0089] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure, and all such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

1. 1. A method for supporting time synchronization services in a communication system provided by a first network node implementing a time synchronization service network function, comprising: Receiving a request for time synchronization for a UE or a group of UEs originating from an Application Function (AF); obtaining subscription data for the UE or the group of UEs, the subscription data indicating whether the request for time synchronization from the AF is allowed to commence; rejecting the request for time synchronization from the AF if it is determined that the subscription data for the UE or the UE group does not allow the request for time synchronization from the AF; initiating the time synchronization service if it is determined that the subscription data authorizes the request for time synchronization service from the AF; A method comprising:

2. The request for time synchronization service from the AF further includes a request for time synchronization with time resilience service, and the subscription data indicates whether the request for time synchronization with time resilience is permitted. The method of claim 1.

3. The request for time synchronization or time synchronization with time resilience includes parameters related to the requested time resilience service. The method according to claim 1 or 2.

4. The step of acquiring subscription data includes: sending a request to a User Data Management (UDM) node to request the subscription data related to a time synchronization service or a time synchronization with time resilience service; receiving the subscription data indicating whether a time synchronization service or a time synchronization with a time resilience service is permitted; Also includes The method according to claim 1 or 2.

5. The subscription data includes an indication that the time synchronization service or the time synchronization with time resiliency service is enabled or disabled.

5. The method according to any one of claims 1 to 4.

6. The method further includes subscribing at the user data management node to receive any changes to a subscription to a time synchronization or time synchronization with time resiliency service.

5. The method according to any one of claims 1 to 4.

7. receiving a notification from the UDM or the AF to disable time resilient services; deactivating said time resilient service upon receipt of said notification; Also includes 7. The method according to any one of claims 2 to 6.

8. receiving a notification from the UDM or the AF to disable a time synchronization service; deactivating the time synchronization service when said notification is received and, if time synchronization with time resilience was previously permitted and / or activated, deactivating the time resilience service; Also includes 7. The method according to any one of claims 1 to 6.

9. A node implementing a time synchronization service network function configured to implement the method according to any one of claims 1 to 8.

10. A node comprising one or more processors and a memory for storing instructions which, when executed by the one or more processors of the node implementing a time synchronization service, perform the method according to any one of claims 1 to 8.

11. A computer readable medium comprising program instructions for causing one or more processors of a node implementing a time synchronization service to perform the method of any one of claims 1 to 8.

Images