Primary source status reporting to user equipment

Abstract

A method, an apparatus, and a computer program product provide means for determining a user equipment affected by a network timing synchronization state and providing a timing resilient solution. An example method includes receiving, at a network entity, a network timing synchronization status request, where the network timing synchronization status request includes: an indication of one or more user equipments (UEs) to provide a time synchronization report to the one or more user equipments; determining one or more provider network entities for each UE to request a time synchronization state from the one or more provider network entities; in response to receiving the indication of the primary source event, generating a time synchronization report indicating the primary source event; and causing a time synchronization report to be provided to the one or more affected UEs.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application incorporates U.S. Provisional Application No. 63 / 362,059 filed on March 29, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] One example embodiment generally relates to techniques for determining user equipment affected by a network timing synchronization state and reporting available timing synchronization state updates to the affected user equipment. With certain embodiments described herein, synchronized timing can be maintained between network entities when a time source, such as GNSS timing, fails or is otherwise degraded. Background Art

[0004] Synchronous timing in a network is critical to the proper functioning of the network. Various aspects of network functionality rely on network time synchronization. For example, some services that utilize synchronization information (e.g., Coordinated Universal Time (UTC)) via user equipment devices and / or communication networks (whether as a primary or backup source) require that the synchronization information be up-to-date and accurate. Timing errors can lead to network connection errors as well as application functionality issues. Therefore, it is important to provide indications of timing synchronization updates to affected user equipment. Summary of the invention

[0005] Various embodiments are generally directed to techniques for determining user equipment affected by a timing synchronization status update and providing time synchronization reports to a time synchronization solution operating on the user equipment in the event of time source degradation, recovery, or failure.

[0006] According to an example embodiment, the network comprises a fifth generation technology standard (5G) network, and wherein the plurality of nodes comprises one or more of the following: a (radio) access network ((R)AN) node (e.g., a next generation radio access network (NG-RAN) node), an access and mobility management function (AMF), a time sensitive communication and time synchronization function (TSCTSF), an application function (AF).

[0007] In an example embodiment, a method is provided, the method comprising: receiving a network timing synchronization status request at a network entity, wherein the network timing synchronization status request comprises: an indication of one or more user equipment (UE) to provide a time synchronization report to the one or more user equipment. In some implementations, the method further comprises: determining one or more provider network entities for each UE to request time synchronization status from the one or more provider network entities. In some embodiments, the method further comprises: in response to receiving an indication of a primary source event, generating a time synchronization report indicating the primary source event. In some embodiments, the method further comprises: causing the time synchronization report to be provided to one or more affected UEs.

[0008] In some embodiments, the method further comprises: determining, by the network entity, one or more affected UEs affected by the primary source event.

[0009] In some embodiments, the method further comprises: receiving, by another network entity, an indication of one or more affected UEs affected by the primary source event.

[0010] In some embodiments, the method further comprises: subscribing to the access network node or the access network node timing synchronization state of each UE via a subscription request message. In some embodiments, the method further comprises: receiving a time synchronization report message in response to the subscription request message, wherein the time synchronization report message comprises a time synchronization report. In some embodiments, the subscription request message comprises: a time synchronization report type indicating the type of the requested time synchronization report.

[0011] In some embodiments, the method further comprises: subscribing to the UE location information of each UE via a location subscription request message.

[0012] In some embodiments, the method further comprises: determining a binding of each UE with respect to an access network node.

[0013] In some embodiments, the method further comprises causing a network timing synchronization report included in a port management information container (PMIC) to be provided to the UE.

[0014] In some embodiments, the network timing synchronization state request is received from one or more user equipments. In some embodiments, the network timing synchronization state request is received from another network entity. In some embodiments, one or more provider network entities are determined to request time synchronization state from one or more provider network entities, and the one or more provider network entities include one or more of the following: access network (AN) node, access and mobility management function (AMF), session management function (SMF), user plane function (UPF), or network side converter (NW-TT). In some embodiments, the network timing synchronization report is provided to the affected UE via non-access layer (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session process signaling. In some embodiments, the network timing synchronization request indicates whether each information element included in the network timing synchronization state request is optional or mandatory in the time synchronization report. In some embodiments, the information element of the network timing synchronization report includes at least one of the following: primary source type, lock state, primary source event, or primary source quality.

[0015] In an example embodiment, an apparatus is provided, the apparatus comprising: a component for receiving a network timing synchronization status request at a network entity, wherein the network timing synchronization status request comprises: an indication of one or more user equipment (UE) to provide a time synchronization report to the one or more user equipment. In some embodiments, the apparatus further comprises: a component for determining one or more provider network entities for each UE to request time synchronization status from the one or more provider network entities. In some embodiments, the apparatus further comprises: a component for generating a time synchronization report indicating a primary source event in response to receiving an indication of a primary source event. In some embodiments, the apparatus further comprises: a component for causing the time synchronization report to be provided to one or more affected UEs.

[0016] In some embodiments, the apparatus further comprises: means for determining, by the network entity, one or more affected UEs affected by the primary source event.

[0017] In some embodiments, the apparatus further comprises means for receiving, by another network entity, an indication of one or more affected UEs affected by the primary source event.

[0018] In some embodiments, the apparatus further comprises: a component for subscribing to the timing synchronization status of the access network node or the access network node of each UE via a subscription request message. In some embodiments, the apparatus further comprises: a component for receiving a time synchronization report message in response to the subscription request message, wherein the time synchronization report message comprises a time synchronization report. In some embodiments, the subscription request message comprises: a time synchronization report type indicating the type of the requested time synchronization report.

[0019] In some embodiments, the apparatus further comprises means for subscribing to UE location information of each UE via a location subscription request message.

[0020] In some embodiments, the apparatus further comprises: means for determining a binding of each UE with respect to an access network node.

[0021] In some embodiments, the apparatus further comprises means for causing a network timing synchronization report included in a port management information container (PMIC) to be provided to the UE.

[0022] In some embodiments, the network timing synchronization state request is received from one or more user equipments. In some embodiments, the network timing synchronization state request is received from another network entity. In some embodiments, one or more provider network entities are determined to request time synchronization state from one or more provider network entities, and the one or more provider network entities include one or more of the following: access network (AN) node, access and mobility management function (AMF), session management function (SMF), user plane function (UPF), or network side converter (NW-TT). In some embodiments, the network timing synchronization report is provided to the affected UE via non-access layer (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session process signaling. In some embodiments, the network timing synchronization request indicates whether each information element included in the network timing synchronization state request is optional or mandatory in the time synchronization report. In some embodiments, the information element of the network timing synchronization report includes at least one of the following: primary source type, lock state, primary source event, or primary source quality.

[0023] In another example embodiment, an apparatus may be provided, the apparatus comprising at least one processor and at least one memory, the at least one memory comprising computer program code for one or more programs, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: receive a network timing synchronization status request at a network entity, wherein the network timing synchronization status request comprises: an indication of one or more user equipments (UEs) to provide a time synchronization report to the one or more user equipments. In some embodiments, the apparatus may include computer program code, the computer program code being further configured to, with the at least one processor, cause the apparatus to at least: determine one or more provider network entities for each UE to request time synchronization status from the one or more provider network entities. In some embodiments, the apparatus may include computer program code, the computer program code being further configured to, with the at least one processor, cause the apparatus to at least: generate a time synchronization report indicating a primary source event in response to receiving an indication of a primary source event. In some embodiments, the apparatus may include computer program code, the computer program code being further configured to, with the at least one processor, cause the apparatus to at least: cause the time synchronization report to be provided to one or more affected UEs.

[0024] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: determine, by the network entity, one or more affected UEs affected by the primary source event.

[0025] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: receive, by another network entity, an indication of one or more affected UEs affected by the primary source event.

[0026] In some embodiments, the apparatus may include computer program code, the computer program code is further configured to, together with the at least one processor, enable the apparatus to at least: subscribe to the access network node or the access network node timing synchronization state of each UE via a subscription request message. In some embodiments, the apparatus may include computer program code, the computer program code is further configured to, together with the at least one processor, enable the apparatus to at least: receive a time synchronization report message in response to the subscription request message, wherein the time synchronization report message includes a time synchronization report. In some embodiments, the subscription request message includes: a time synchronization report type indicating the type of the requested time synchronization report.

[0027] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: subscribe to UE location information of each UE via a location subscription request message.

[0028] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: determine a binding of each UE with respect to an access network node.

[0029] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: cause a network timing synchronization report included in a port management information container (PMIC) to be provided to the UE.

[0030] In some embodiments, the network timing synchronization state request is received from one or more user equipments. In some embodiments, the network timing synchronization state request is received from another network entity. In some embodiments, one or more provider network entities are determined to request time synchronization state from one or more provider network entities, and the one or more provider network entities include one or more of the following: access network (AN) node, access and mobility management function (AMF), session management function (SMF), user plane function (UPF), or network side converter (NW-TT). In some embodiments, the network timing synchronization report is provided to the affected UE via non-access layer (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session process signaling. In some embodiments, the network timing synchronization request indicates whether each information element included in the network timing synchronization state request is optional or mandatory in the time synchronization report. In some embodiments, the information element of the network timing synchronization report includes at least one of the following: primary source type, lock state, primary source event, or primary source quality.

[0031] In another example embodiment, a computer program product may be provided, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising the program code instructions being configured to, when executed: receive a network timing synchronization status request at a network entity, wherein the network timing synchronization status request comprises: an indication of one or more user equipment (UE) to provide a time synchronization report to the one or more user equipment. In some embodiments, the computer-executable program code instructions comprising the program code instructions may also be configured to, when executed: determine one or more provider network entities for each UE to request time synchronization status from the one or more provider network entities. In some embodiments, the computer-executable program code instructions comprising the program code instructions may also be configured to, when executed: generate a time synchronization report indicating a primary source event in response to receiving an indication of a primary source event. In some embodiments, the computer-executable program code instructions comprising the program code instructions may also be configured to, when executed: cause the time synchronization report to be provided to one or more affected UEs.

[0032] In some embodiments, the computer executable program code instructions including the program code instructions may be further configured to, when executed: determine, by the network entity, one or more affected UEs affected by the primary source event.

[0033] In some embodiments, the computer executable program code instructions including the program code instructions may be further configured to, when executed: receive, by another network entity, an indication of one or more affected UEs affected by the primary source event.

[0034] In some embodiments, the computer executable program code instructions including the program code instructions may also be configured to, when executed: subscribe to the access network node or the access network node timing synchronization state of each UE via a subscription request message. In some embodiments, the computer executable program code instructions including the program code instructions may also be configured to, when executed: receive a time synchronization report message in response to the subscription request message, wherein the time synchronization report message includes a time synchronization report. In some embodiments, the subscription request message includes: a time synchronization report type indicating the type of the requested time synchronization report.

[0035] In some embodiments, the computer executable program code instructions including the program code instructions may also be configured to, when executed, subscribe to UE location information of each UE via a location subscription request message.

[0036] In some embodiments, the computer executable program code instructions comprising the program code instructions may also be configured to, when executed: determine a binding of each UE with respect to an access network node.

[0037] In some embodiments, the computer executable program code instructions including the program code instructions may be further configured to, when executed: cause a network timing synchronization report included in a port management information container (PMIC) to be provided to the UE.

[0038] In some embodiments, the network timing synchronization state request is received from one or more user equipments. In some embodiments, the network timing synchronization state request is received from another network entity. In some embodiments, one or more provider network entities are determined to request time synchronization state from one or more provider network entities, and the one or more provider network entities include one or more of the following: access network (AN) node, access and mobility management function (AMF), session management function (SMF), user plane function (UPF), or network side converter (NW-TT). In some embodiments, the network timing synchronization report is provided to the affected UE via non-access layer (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session process signaling. In some embodiments, the network timing synchronization request indicates whether each information element included in the network timing synchronization state request is optional or mandatory in the time synchronization report. In some embodiments, the information element of the network timing synchronization report includes at least one of the following: primary source type, lock state, primary source event, or primary source quality.

[0039] In another example embodiment, a method is provided, the method comprising: receiving a time synchronization report. The method further comprises: updating one or more configurations based at least in part on the time synchronization report.

[0040] In some embodiments, the method further comprises: storing the time synchronization report.

[0041] In some embodiments, the method further comprises causing the master advertised update to be provided to an associated precision time protocol network.

[0042] In some embodiments, the method further comprises causing a time source event report indicative of the time source event to be provided to a higher layer.

[0043] In some embodiments, the method further comprises causing a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

[0044] In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, changing a primary time source from which time information is received. In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, relying on a retention capability of time information. In some embodiments, the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

[0045] In another example embodiment, an apparatus is provided that includes means for receiving a time synchronization report. The apparatus also includes means for updating one or more configurations based at least in part on the time synchronization report.

[0046] In some embodiments, the apparatus further comprises: means for storing the time synchronization report.

[0047] In some embodiments, the apparatus further comprises means for causing the master advertise updates to be provided to an associated precision time protocol network.

[0048] In some embodiments, the apparatus further comprises: means for causing a time source event report indicative of the time source event to be provided to a higher layer.

[0049] In some embodiments, the apparatus further comprises means for causing a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

[0050] In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, changing a primary time source from which time information is received. In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, relying on a retention capability of time information. In some embodiments, the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

[0051] In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, changing a primary time source from which time information is received. In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, relying on a retention capability of time information. In some embodiments, the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

[0052] In another example embodiment, an apparatus may be provided, the apparatus comprising at least one processor and at least one memory, the at least one memory comprising computer program code for one or more programs, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: receive a time synchronization report. The apparatus may include computer program code, the computer program code being further configured to, with the at least one processor, cause the apparatus to at least: update one or more configurations based at least in part on the time synchronization report.

[0053] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: store a time synchronization report.

[0054] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: cause a master advertise update to be provided to an associated precision time protocol network.

[0055] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: cause a time source event report indicative of the time source event to be provided to a higher layer.

[0056] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: cause a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

[0057] In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, changing a primary time source from which time information is received. In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, relying on a retention capability of time information. In some embodiments, the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

[0058] In another example embodiment, a computer program product may be provided, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising the program code instructions being configured to, when executed: receive a time synchronization report. The computer-executable program code instructions comprising the program code instructions may also be configured to, when executed: update one or more configurations based at least in part on the time synchronization report.

[0059] In some embodiments, the computer executable program code instructions comprising the program code instructions may be further configured, when executed, to: store a time synchronization report.

[0060] In some embodiments, the computer executable program code instructions comprising the program code instructions may be further configured, when executed, to: cause a master advertise update to be provided to an associated precision time protocol network.

[0061] In some embodiments, the computer executable program code instructions comprising the program code instructions may be further configured to, when executed, cause a time source event report indicative of the time source event to be provided to a higher layer.

[0062] In some embodiments, the computer executable program code instructions comprising the program code instructions may be further configured to, when executed: cause a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

[0063] In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, changing a primary time source from which time information is received. In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, relying on a retention capability of time information. In some embodiments, the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

[0064] In another example embodiment, a method is provided, the method comprising: receiving, by a network entity, an indication to provide a time synchronization report to one or more user equipments (UEs). The method further comprises: providing the time synchronization report to the one or more UEs.

[0065] In some embodiments, the network entity is an access network node, an access and mobility management function, or a session management function. In some embodiments, the time synchronization report is provided via SIB9 signaling, or radio resource connection (RRC) signaling. In some embodiments, providing the time synchronization report further comprises: triggering a paging or UE information transfer process. In some embodiments, an indication to provide the time synchronization report is received via non-access stratum (NAS) signaling. In some embodiments, the time synchronization report is provided in a port management information container (PMIC).

[0066] In another example embodiment, an apparatus is provided that includes means for receiving, by a network entity, an indication to provide a time synchronization report to one or more user equipments (UEs). The apparatus also includes means for providing the time synchronization report to the one or more UEs.

[0067] In some embodiments, the network entity is an access network node, an access and mobility management function, or a session management function. In some embodiments, the time synchronization report is provided via SIB9 signaling, or radio resource connection (RRC) signaling. In some embodiments, providing the time synchronization report further comprises: triggering a paging or UE information transfer process. In some embodiments, an indication to provide the time synchronization report is received via non-access stratum (NAS) signaling. In some embodiments, the time synchronization report is provided in a port management information container (PMIC).

[0068] In another example embodiment, an apparatus may be provided, the apparatus comprising at least one processor and at least one memory, the at least one memory comprising computer program code for one or more programs, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: receive, by a network entity, an indication to provide a time synchronization report to one or more user equipments (UEs). The apparatus may include computer program code, the computer program code being further configured to, with the at least one processor, cause the apparatus to at least: provide a time synchronization report to one or more UEs.

[0069] In some embodiments, the network entity is an access network node, an access and mobility management function, or a session management function. In some embodiments, the time synchronization report is provided via SIB9 signaling, or radio resource connection (RRC) signaling. In some embodiments, providing the time synchronization report further comprises: triggering a paging or UE information transfer process. In some embodiments, an indication to provide the time synchronization report is received via non-access stratum (NAS) signaling. In some embodiments, the time synchronization report is provided in a port management information container (PMIC).

[0070] In another example embodiment, a computer program product may be provided, the computer program product including at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions including the program code instructions being configured to, when executed: receive, by a network entity, an indication to provide a time synchronization report to one or more user equipments (UEs). The computer-executable program code instructions including the program code instructions may also be configured to, when executed, cause the apparatus to at least: provide a time synchronization report to one or more UEs.

[0071] In some embodiments, the network entity is an access network node, an access and mobility management function, or a session management function. In some embodiments, the time synchronization report is provided via SIB9 signaling, or radio resource connection (RRC) signaling. In some embodiments, providing the time synchronization report further comprises: triggering a paging or UE information transfer process. In some embodiments, an indication to provide the time synchronization report is received via non-access stratum (NAS) signaling. In some embodiments, the time synchronization report is provided in a port management information container (PMIC).

[0072] The above overview is provided only to summarize some example embodiments to provide a basic understanding of certain aspects of the present invention. Therefore, it should be understood that the above embodiments are merely examples and should not be interpreted as narrowing the scope or spirit of the present invention in any way. It should be understood that in addition to those summarized here, the scope of the present invention also includes many potential embodiments, some of which will be further described below. Other features, aspects and advantages of this theme will become clear from the specification, drawings and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] Having described certain example embodiments of the present disclosure in general terms above, non-limiting and non-exhaustive embodiments of the present disclosure will now be described with reference to the accompanying drawings, which are not necessarily drawn to scale. The components shown in the drawings may or may not be present in certain embodiments described herein. Some embodiments may include fewer (or more) components than those shown in the drawings.

[0074] Figure 1 illustrates an overview of an example 5G internal clock and generalized Precision Time Protocol ((g)PTP) distribution architecture in accordance with various embodiments;

[0075] Figure 2 illustrates an overview of an example mobile network (e.g., 5GS) according to various embodiments;

[0076] Figure 3 A block diagram of an example apparatus is provided that can facilitate tolerance to temporal signal degradation through a mitigation framework in accordance with various embodiments;

[0077] Figure 4A-4B illustrates a message flow diagram in the case of TSCTSF binding timing synchronization updates from (R)AN according to various embodiments;

[0078] Figure 5 illustrates a message flow diagram in the case where the AMF binds the timing synchronization update from the (R)AN according to various embodiments;

[0079] Figure 6illustrates a message flow diagram in the case where the 5GS has been configured for network time synchronization reporting using SIB9 based notifications according to various embodiments;

[0080] Figure 7 illustrates a message flow diagram in the case where the 5GS has been configured for network time synchronization reporting using RRC-based notifications according to various embodiments;

[0081] Figure 8 illustrates a message flow diagram for a scenario where a 5GS has been configured for network time synchronization reporting using NAS-based notifications according to various embodiments;

[0082] Fig. 9 depicts example information that may be included in a time synchronization report according to various embodiments;

[0083] Fig.10 illustrates an example workflow of various components of a communication system according to an example embodiment;

[0084] Fig.11 illustrates an example workflow of various components of a communication system according to an example embodiment; and

[0085] Fig.12 An example workflow of various components of a communication system according to an example embodiment is illustrated. DETAILED DESCRIPTION

[0086] Some embodiments of the present invention will be described more fully below with reference to the accompanying drawings, in which some but not all embodiments of the present invention are shown. In fact, various embodiments of the present invention can be embodied in many different forms and should not be construed as being limited to the embodiments described herein; on the contrary, these embodiments are provided to enable the present disclosure to meet applicable legal requirements. The same reference numerals always refer to the same elements. As used herein, the terms "data", "content", "information", "electronic information", "signal", "command" and similar terms can be used interchangeably to refer to data that can be captured, sent, received, and / or stored according to various embodiments of the present disclosure. Therefore, the use of any such terms should not be regarded as limiting the spirit and scope of the embodiments of the present disclosure. In addition, when a first computing device is described herein as receiving data from a second computing device, it should be understood that the data can be received directly from the second computer device or indirectly via one or more intermediate computing devices (such as, for example, one or more servers, relays, routers, network access points, base stations, hosts, repeaters, etc., sometimes referred to as "networks" in this article). Similarly, where a first computing device is described herein as sending data to a second computing device, it should be understood that the data may be sent or transmitted directly to the second computing device, or may be sent or transmitted indirectly via one or more intermediate computing devices (such as, for example, one or more servers, remote servers, cloud-based servers (e.g., cloud utilities), relays, routers, network access points, base stations, hosts, repeaters, etc.).

[0087] The term "including" is meant to include, but is not limited to, the manner in which it is commonly used in a patent context, and should be interpreted accordingly. The use of broader terms such as "comprising," "containing," and "having" should be understood to support narrower terms such as "consisting of," "consisting essentially of," and "consisting essentially of." Furthermore, where the terms "including" and "comprising" and variations thereof are used in the detailed description or claims, these terms are intended to be inclusive in a manner similar to the term "comprising."

[0088] The phrases "in one embodiment," "according to one embodiment," "in some implementations," "in various embodiments," etc. generally mean that the particular feature, structure, or characteristic following the phrase may be included in at least one embodiment of the present disclosure, but not necessarily in all embodiments of the present disclosure. Thus, a particular feature, structure, or characteristic may be included in more than one embodiment of the present disclosure, such that these phrases do not necessarily refer to the same embodiment.

[0089] As used herein, the terms "example," "exemplary," and the like are used to mean "serving as an example, instance, or illustration." Any implementation, aspect, or design described herein as "example" or "exemplary" is not necessarily to be construed as preferred over other implementations, aspects, or designs. Rather, the use of the terms "example," "exemplary," and the like is intended to present concepts in a concrete manner.

[0090] If the specification states that a component or feature "may," "could," "should," "would," "preferably," "might," "usually," "optionally," "for example," "often," or "might" (or other such language) be included or have a characteristic, that particular component or feature is not required to be included or have that characteristic. Such a component or feature may optionally be included in some embodiments, or may be excluded.

[0091] As used herein, the term "computer-readable medium" refers to non-transitory storage hardware, non-transitory storage devices, or non-transitory computer system memory that can be accessed by a controller, a microcontroller, a computing system, or a module of a computing system to encode computer-executable instructions or software programs thereon. Non-transitory "computer-readable medium" can be accessed by a computing system or a module of a computing system to retrieve and / or execute computer-executable instructions or software programs encoded on the medium. Examples of non-transitory computer-readable media may include, but are not limited to, one or more types of hardware memory, non-transitory tangible media (e.g., one or more magnetic storage disks, one or more optical disks, one or more USB flash drives), computer system memory, or random access memory (such as DRAM, SRAM, EDO RAM), etc.

[0092] In addition, as used herein, the term "circuitry" refers to (a) a pure hardware circuit implementation (e.g., an implementation in an analog circuit system and / or a digital circuit system); (b) a combination of a circuit and (multiple) computer program products, including software and / or firmware instructions stored on one or more computer-readable memories, which work together to cause the device to perform one or more functions described herein; and (c) a circuit that requires software or firmware to operate (even if the software or firmware is not physically present), such as, for example, (multiple) microprocessors or a portion of (multiple) microprocessors. This definition of "circuitry" applies to all uses of the term herein, including in any claims. As another example, as used herein, the term "circuitry" also includes an implementation that includes one or more processors and / or (multiple) portions thereof, and accompanying software and / or firmware. As another example, for example, as used herein, the term "circuitry" also includes a baseband integrated circuit or application processor integrated circuit for a mobile phone, or a similar integrated circuit in a server, cellular network equipment, other network equipment (such as a core network device), a field programmable gate array, and / or other computing devices.

[0093] Telecommunication networks typically employ a combination of synchronization methods to ensure reliability and robustness of phase / time synchronization, such as avoiding causing (R)AN ((Radio) Access Network) timing failures and interfering with other nodes and devices. For example, a local GNSS (Global Navigation Satellite System) receiver at a (R)AN node is combined with a PTP (Precision Time Protocol) transmission network to support a more centrally located GNSS-based physical layer clock. In one example, according to the International Telecommunication Union (ITU) standard ITU-TG8271.2, network restrictions are defined for time synchronization in packet networks with partial timing support of the network. In an Assisted Partial Timing Support (APTS) configuration, PTP is used as a backup timing source for a local reference (e.g., a GNSS-based Primary Reference Clock (PRTC)) for up to 72 hours. PTP is not intended to be used as a primary timing source. However, in a PTS configuration, PTP is used as the primary time source for the end application. In this mode, a local time reference (e.g., GNSS) is not available.

[0094] Some examples of requirements that the (R)AN needs to meet include a Cell Phase Synchronization Accuracy (CPSA) of 3 microseconds between cells for TDD (Time Division Duplex), and a time alignment error of less than 260 nanoseconds (Class B) and 130 nanoseconds (Class A) between gNB (gNodeB) radio units (RU) for intra-band carrier aggregation. However, GNSS signals are susceptible to degradation, such as due to threats such as physical congestion, interference, and jamming / spoofing attacks, which can compromise network synchronization. The gNB is a network element that is well suited to monitor GNSS signals, although it can have different implementations, such as whether the gNB relies on a directly connected GNSS, or whether it is connected to its timing host through a transport network.

[0095] The use of GNSS time delivery, especially in GPS, is important in many areas, such as for positioning, and / or navigation and timing (PNT) purposes. However, GNSS may experience several vulnerabilities due to environmental phenomena, malicious or accidental interference, spoofing, adjacent band interference, etc. A TSCTSF is required to monitor and / or control timing resilience monitoring within a communication system (e.g., 5GS). However, the TSCTSF may need to extract the synchronization plane status from the network entity responsible for time distribution within the 5GS.

[0096] Figure 1 An example 5G internal clock and (g)PTP distribution architecture is illustrated. For control plane (C-plane) time distribution (i.e., 5G access stratum (AS) time distribution), an access node (AN) (such as a radio access (RAN) node) is responsible for providing 5GS timing information to the UE via the Uu interface. For example, the (R)AN may use SIB9 or dedicated radio resource control (RRC) signaling to provide 5G timing information. Alternatively, for user plane (U-plane) time distribution (i.e., using general precision time protocol ((g)PTP or PTP) messages), a (g)PTP master (GM) provides (g)PTP timing information to the UE and / or device-side time-sensitive network translator (DS-TT) via the user plane. The DS-TT on the UE side and the network-side time-sensitive network translator (NW-TT) on the network side (e.g., at the user plane function (UPF)) are responsible for supporting (g)PTP operations.

[0097] For C-plane time distribution of precise absolute time, the (R)AN sends the ReferenceTiemInfo-r16 (RTI) information element (IE) in SIB9 or dedicated RRC signaling as part of the downlink (DL) information transmission. The SIB9 information element is described in TS 38.331. It is then up to the (R)AN to determine whether the (R)AN includes the RTI in the SIB9. The (R)AN may be aware that it should send the RTI to the UE in two cases. In the first case, the (R)AN is configured from the core network (CN) side to always deliver the RTI or always deliver the RTI to a specific UE. In the other case, the UE may request to receive the RTI via the ReferenceTimeInfoPreference field in the UEAssistanceInformation IE.

[0098] As a baseline, the uncertainty field contained in the Reference Time Information (RTI) information element indicates the uncertainty of the reference time information provided by the Time field. This attribute can be used to describe the degradation of the 5G timing information propagated to the UE, but it is not sufficient if the 5GS can withstand degradation / failure of its primary time source (using another source or due to its own keepalive capabilities) but still be able to inform the UE that there is currently a problem with the primary source (e.g. for traceability reasons or for monitoring purposes).

[0099] As mentioned above, in 5GS, a single wireless timing solution will utilize multiple timing sources. In addition, 5GS communications can provide Coordinated Universal Time (UTC), GPS, and local time to the UE. For devices connected to the 5G modem, the 5G clock can be the primary time source or the backup time source. For both cases, if the UE has more than one time reference, it can use them to compare time signals and determine whether its primary time source is degrading, failing, or has recovered.

[0100] For example, in the case of GNSS, GNSS receivers may have built-in features that enable the device side to provide more resilient performance against GNSS vulnerabilities, such as multi-constellation GNSS support. If the traditional use of single or dual GNSS (GPS / GPS+GLONASS) was reserved for applications with strict power constraints or low performance requirements, or where regulations have not yet been updated to multi-constellation, the inclusion of all possible constellations is a key trend for GNSS timing receivers.

[0101] For other types of time sources, the solution may involve further processing on the device side (e.g., comparing inputs), calibration of the device, setting up monitoring tools in the network, etc. As an integral part of the E2E timing solution, the 5G UE is in a unique position to support and validate multiple sources utilizing the 5GS timing synchronization status monitoring service.

[0102] Certain embodiments described herein provide an enabler for a network, such as a fifth generation technology standard (5G) network system (5GS), to determine UEs affected by the timing synchronization state of the network. In addition, the current embodiments provide an enabler for the 5GS to report available timing synchronization state updates to the UE outside of the uncertainty field available in the current RTI. With certain embodiments described herein, synchronized timing can be maintained between network entities when a time source, such as GNSS timing, fails or is otherwise degraded.

[0103] Reference now Figure 2 , illustrates an example mobile network 100. Mobile network 100 (also referred to as a cellular network) is a network in which at least the last link is wireless and provides timing, voice, and / or data services to multiple devices. Mobile network 100 may be a third generation (3G), fourth generation (4G), and / or next generation (e.g., fifth generation or 5G) network, or any other of a variety of networks.

[0104] The mobile network 100 is illustrated as providing communication services to UE 110. UE 110 may be enabled for voice services, data services, machine-to-machine (M2M) or machine-type communication (MTC) services, Internet of Things (IoT) services, and / or other services. UE 110 may be an end-user device such as a mobile phone (e.g., a smartphone), a tablet or PDA, a computer with a mobile broadband adapter, etc.

[0105] The mobile network 100 includes one or more radio access networks ((R)AN 120) that communicate with the UE 110 over a radio interface. The (R)AN 120 of an example embodiment may support Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) access, Wireless Local Area Network (WLAN) access, fixed access, satellite radio access, new radio access technology (RAT), etc. For example, the (R)AN 120 may include an E-UT(R)AN or a Next Generation (R)AN (NG-RAN), which includes one or more base stations 124 dispersed over a geographical area. The base station 124 may include an entity that communicates with the UE over a licensed spectrum using radio communication technology and interfaces the UE with the core network 130. The base station 124 in the E-UT(R)AN may be referred to as an evolved Node B (eNodeB). The base station 124 in the NG(R)AN may be referred to as a gNodeB (NR base station), and / or an ng-eNodeB (LTE base station supporting a 5G core network). As another example, the (R)AN 120 may include a WLAN including one or more wireless access points (WAPs). A WLAN is a network in which a UE can be connected to a local area network (LAN) via a wireless (radio) connection. A WAP is a node that uses radio communication technology to communicate with a UE on an unlicensed spectrum and provides the UE with access to a core network. An example of a WAP is a Wi-Fi access point operating on a 2.4 GHz or 5 GHz radio frequency band. The term "base station" may then refer to an eNodeB, a gNodeB, an ng-eNodeB, a WAP, etc.

[0106] UE 110 is able to attach to a cell of (R)AN 120 to access core network 130. Thus, (R)AN 120 represents a radio interface between UE 110 and core network 130. Core network 130 is a central part of mobile network 100 that provides various services to customers connected through (R)AN 120. One example of core network 130 is an evolved packet core (EPC) network described by 3GPP for LTE. Another example of core network 130 is a 5G core (5GC) network described by 3GPP. Core network 130 includes network entity 132, which may include a server, device, apparatus, or equipment (including hardware) that provides services for UE 110. Network entity 132 in the EPC network may include a mobility management entity (MME), a serving gateway (S-GW), a packet data network gateway (P-GW), and the like. The network entity 132 in the 5G network may include: access and mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), unified data management (UDM), etc.

[0107] Reference now Figure 3 , an example apparatus 300 is provided. In some cases, the apparatus 300 may be an embodiment of, and / or may be embodied by, or otherwise associated with, the UE 110. Alternatively, the apparatus 300 may be an embodiment of, or may be embodied by, or otherwise associated with, the network element 132 (such as the PCF 260). In any aspect, the apparatus 300 is configured to indicate and / or evaluate the applicability of routing parameters (such as URSP parameters). In an example embodiment, the apparatus 300 is embodied by the network element 132 (such as the PCF 260), and generates a network applicability indication of a parameter in a policy rule data object (e.g., a URSP) based at least in part on determining the applicability of the parameter to the EPS network. The apparatus 300 may then cause transmission of the policy rule data object including the network applicability indication to the UE 110, and the UE 110 may then use the policy rule data object when communicating via the EPS network and evaluate the network applicability indication of the parameter of the policy rule data object. In another example embodiment, apparatus 300 is embodied by UE 110 and receives a policy rule data object including a network suitability indication associated with parameters. Apparatus 300 (eg, UE 110) evaluates the network suitability indication to decide whether to ignore or consider various parameters and / or rule descriptors when communicating via the EPS network.

[0108] The apparatus 300 may include: a processor 302, a memory 304, and a network interface 306. The apparatus 300 may be configured to perform the operations described herein. Although these components are described with respect to the performance of various functions, it should be understood that a particular implementation necessarily includes the use of specific hardware. It should also be understood that some of these components may include similar or general hardware. For example, two groups of circuit systems may use the same processor, network interface, storage medium, etc. to perform their related functions, so that no duplicate hardware is required for each group of circuit systems.

[0109] In some embodiments, the processor 302 (and / or a co-processor or auxiliary processor, or any other processing circuit system associated with the processor) can communicate with the memory 304 via a bus to deliver information between components of the device. The memory 304 is non-transitory and can include, for example, one or more volatile and / or non-volatile memories. In other words, for example, the memory 304 can be an electronic storage device (e.g., a computer-readable storage medium). The memory 304 can be configured to store information, data, content, applications, instructions, etc. for enabling the device to perform various functions according to the example embodiments disclosed herein.

[0110] The processor 302 may be embodied in a variety of different ways, and may include, for example, one or more processing devices configured to execute independently. In some non-limiting embodiments, the processor 302 may include: one or more processors configured in series via a bus to implement independent execution of instructions, pipelining, and / or multithreading. The use of the term "processor" may be understood to include a single-core processor, a multi-core processor, multiple processors within a device, and / or a remote or "cloud" processor.

[0111] In some embodiments, the processor 302 may be configured to execute instructions stored in the memory 304, and / or the processor 302, in a circuit system otherwise accessible, such as instructions for indicating and evaluating the EPS applicability of URSP parameters of a policy rule data object. In some embodiments, the processor 302 may be configured to perform hard-coded functions. Therefore, whether configured by hardware or software methods, or by a combination thereof, the processor 302 may represent an entity (e.g., physically embodied in a circuit system) that is capable of performing operations according to the embodiments disclosed herein when configured accordingly. Alternatively, as another example, when the processor 302 is embodied as an executor of software instructions, the instructions may specifically configure the processor 302 to perform the algorithms and / or operations described herein when the instructions are executed.

[0112] In some embodiments, the device 300 may include an input / output circuit system that can communicate with the processor 302 to provide output to a user and / or other entity and receive an indication of input in some implementations. The input / output circuit system may include a user interface, and may include a display, may include a network user interface, a mobile application, a query initiation computing device, an information kiosk, etc. In some embodiments, the input / output circuit system may also include: a keyboard, a mouse, a joystick, a touch screen, a touch area, a soft key, a microphone, a speaker, or other input / output mechanisms. The processor and / or the user interface circuit system including the processor may be configured to: control one or more functions of one or more user interface elements by computer program instructions (e.g., software and / or firmware) stored on a memory (e.g., memory 304, etc.) accessible to the processor.

[0113] The network interface 306 can be any component, such as a device or circuit system embodied in hardware or a combination of hardware and software, which is configured to receive and / or send data from / to a network and / or any other device, circuit system, or module that communicates with the device 300. In this regard, for example, the network interface 306 may include a network interface for enabling communication with a wired or wireless communication network. For example, the network interface 304 may include one or more network interface cards, antennas, buses, switches, routers, modems, and supporting hardware and / or software, or any other device suitable for communicating via a network. Additionally or alternatively, the network interface 306 may include a circuit system for interacting with one / multiple antennas to enable signal transmission via one / multiple antennas or processing the reception of signals received via one / multiple antennas.

[0114] It should also be noted that all or part of the information discussed herein may be based on data received, generated, and / or maintained by one or more components of the device 300. In some embodiments, one or more external systems (such as remote cloud computing and / or data storage systems) may also be utilized to provide at least some of the functionality discussed herein.

[0115] The example embodiments described herein provide a consistent, fault-tolerant timing degradation mitigation framework to enable a network, such as a 5GS network, to maintain timing when a time source fails. Certain embodiments determine the UEs affected by timing synchronization status updates and how to enable 5GS reporting of time synchronization reports to the UEs, which provides mitigation strategies to ensure that time synchronization services consumed on the device side are informed of the network timing synchronization status.

[0116] 5GC can determine the UE that needs time source status update. In particular, the determination of the UE to be updated can be determined. Figure 4A-4B Example communications between a UE and various network entities of a communication system for configuring a UE behavior policy for the UE are illustrated.

[0117] Figure 4A-4BAn example implementation of the method of the message flow described in this document is illustrated, where the TSCTSF is configured to bind node level time synchronization reports to specific UEs. The 5GS must bind the reporting updates to the UEs that may be affected. The update can be based on the UEs in the coverage area of ​​the (R)AN, and / or whether the corresponding node is currently serving the UE. In this case, the TSCTSF subscribes at the AMF at each RAN node level. The AMF forwards the status report received from the NG-RAN node to the TSCTSF. In order to determine the (multiple) affected UEs, the TSCTSF needs to subscribe to the location service of the UE at the AMF. For UPF / NW-TT reporting, the TSCTSF can be a consumer of the Nupf_EventExposure service operation and retrieve the reports directly from the UPF, or the SMF can be used to affect the N4 node level reporting between the SMF and the UPF. Alternatively, as Figure 5 As shown, the AMF can bind the node level time synchronization report to a specific UE.

[0118] At operation 1, a network synchronization status request may be received. The network synchronization status request may be received from one or more UEs or from an associated AF. In particular, the TSCTSF 404 may receive the network synchronization status request.

[0119] In a first instance, the access function (AF) 406 may request a network timing synchronization state target for a UE and / or a subset of UEs. The AF may provide the received UE identifier for a subset of UEs directly and / or by filtering the information based on spatial validity or data network name (DNN) connectivity. Alternatively, the 5GS network may notify all UEs in the coverage area and / or all UEs receiving time synchronization services via non-access stratum (NAS) signaling or RRC signaling.

[0120] Alternatively, UE 401 may explicitly request network timing synchronization status monitoring. In particular, UE 401 may provide 5GS with subscription events or information elements of which it wishes to be notified. The UE request may be forwarded to TSCTSF 404, where TSCTSF 404 may control subscriptions to notifications and configure network time synchronization reports. UE 401 may provide the request using NAS or RRC signaling. In the case where the UE uses NAS signaling, UE 401 may provide the request via NAS signaling via AMF 403. AMF 403 may process the request, identify the corresponding TSCTSF, and forward the request. In the case where the UE uses RRC signaling, the serving (R)AN node may forward the request to TSCTSF 404 via AMF 403.

[0121] As shown in operation 2, when TSCTSF 404 receives a network timing synchronization state request from AF 406, TSCTSF 404 may determine a target UE. The target UE may be determined based at least in part on a provided UE identifier and / or DNN single network slice selection assistance information (S-NSSAI).

[0122] As shown in operation 3, for each UE, the TSCTSF 404 may determine a network entity to contact and / or request a subscription from the network entity. For example, a subscription request message may be provided from the TSCTSF 404 to an AMF, an associated session management function (SMF), and / or a UPF (or NW-TT) corresponding to a UE in one or more UEs.

[0123] Operation 4-6 may allow the TSCTSF to subscribe to (R)AN timing synchronization status updates at the node level. This occurs at the node level when the 5GS collects network timing synchronization status from (R)AN nodes and / or UPF NW-TT nodes.

[0124] As shown in operation 4, TSCTSF 404 may provide a subscription request message to AMF 403. In particular, the subscription request message may be a Namf_Communication_NonUeN2Info_Subscribe message. The subscription request message may include the (R)AN node identity and / or (R)AN time synchronization report type to which TSCTSF 404 wishes to subscribe. As shown in operation 5, the time synchronization report control message may be shared between (R)AN 402 and AMF 403. As shown in operation 6, AMF 403 may provide a subscription completion message to TSCTSF 404. The subscription completion message may indicate whether TSCTSF has successfully subscribed to the requested network entity. The subscription completion message may be a Namf_communication_NonUeN2Info_Notify message.

[0125] Operations 7-9 may allow the TSCTSF to communicate UE location information. For UPF / NW-TT nodes, the TSCTSF may have been configured to determine the binding of the serving UPF / NW-T and the UE, since the UE has a (g)PTP service already controlled by the TSCTSF (operation standardized in Release 17).

[0126] For NG-RAN nodes, the Next Generation Application Protocol (NGAP) location report provided by the NG-RAN to the AMF may include the UE's Tracking Area Identity (TAI) and / or cell identifier. In addition, the UE's state (connected mode, idle, etc.) may be determined to determine the UE's location and associate the UE with the received NG-RAN time synchronization report. If the UE is in the RRC-CONNECTED state, the serving cell may be determined at the AMF by reusing the location reporting procedure already available in the NGAP. Therefore, once a report from a NG-RAN cell is received in the 5GC, the UE can be identified. If the UE is in the RRC-INACTIVE state, the NG-RAN determines the RAN Notification Area (RNA) (a list of (multiple) Tracking Areas (TAs)), and therefore, the AMF can determine the RNA in which the UE is located. When a report from a NG-RAN cell is received, the 5GC or NG-RAN will need to page the UE to check the cell in which the UE resides within the RNA. If the UE is in the RRC-IDLE state, the AMF can determine the TA in which the UE is located. When the report from the NG-RAN cell is received, the 5GC will need to page the UE to check the cell in which the UE is camped within the TA.

[0127] As shown in operation 7, TSCTSF 404 may provide a location subscription request message to AMF 403. The location subscription request message may include an event identifier in the location report. The location subscription request may be a Namf_EventExposure_Subscribe message. As shown in operation 8, the location report request message may be shared between (R)AN 402 and AMF 403. As shown in operation 9, AMF 403 may provide a location subscription completion message to TSCTSF 404. The location subscription completion message may indicate whether TSCTSF has successfully subscribed to UE location information. The subscription completion message may be a Namf_EventExposure_Notify message.

[0128] As shown in operation 10, the TSCTSF 404 may determine a UE bound to an (R)AN node. The binding of the UE to the (R)AN node may be based at least in part on a received subscription message related to (R)AP timing synchronization state subscription information and / or UE location information, as discussed above with respect to operations 4-6 and 7-9, respectively.

[0129] At operation 11, (R)AN 402 may detect a primary source event. The primary source event may be a (R)AN synchronization update. At operation 12, (R)AN 402 may provide a time synchronization report to AMF 403. At operation 13, AMF 403 may provide an indication of the primary source event to TSCTSF 404. The indication of the primary source event may be provided as a Namf_EventExposure_Notify message.

[0130] At operation 14, TSCTSF 404 may determine the UEs affected by the primary source event. At operation 15, TSCTSF 404 may cause a time synchronization report to be provided to one or more affected UEs. Figure 6-Figure 8 The provision of time synchronization reports is discussed in more detail.

[0131] The time synchronization report may provide information related to the timing information of the UE. Fig. 9 An example of information that may be included in a time synchronization report is depicted. A UE may be interested only in events, or in a more detailed description of the timing synchronization status of the 5G clock delivered to the UE via the c-plane or u-plane method by the 5GS. The information element of the time synchronization report may also have an indication of whether the information element is mandatory or optional. The time synchronization report may include information elements such as primary source type, lock status, primary source events, and / or primary source quality.

[0132] The lock status value can describe various values, including: 1) parent value, which can indicate that the signal from the source is currently used as a synchronization reference, 2) OK, which can indicate that the signal from the source can potentially be used as a synchronization reference, 3) NOK, which can indicate that the signal from the source cannot be used as a synchronization reference, and / or 4) disabled, which can indicate that the source connection is unavailable.

[0133] In case the UE has configured (g)PTP distribution, the DS-TT may already know the quality of the primary source, since the considered attributes are part of the PTP signaling. That is, if the UPF is the GM of a (g)PTP time domain, the DS-TT connected to the same (g)PTP time domain is aware of its performance.

[0134] Figure 5 An example implementation of the method of the message flow described herein is illustrated, where the AMF is configured to bind a node level time synchronization report to a specific UE. The TSCTSF may subscribe to receive the (R)AN time synchronization status at the AMF at a per UE level. The AMF is then responsible for determining the affected UE(s) based on the UE(s) served by the AMF. For each affected UE, the AMF forwards the NG-RAN time synchronization status report to the TSCTSF subscribed for the affected UE(s) served by the AMF.

[0135] Operations 1-3 can be similar to Figure 4A-4B Operations 4-7 may allow the TSCTSF to subscribe to the (R)AN timing synchronization state at the UE level instead of Figure 4A-4B Node level. At operation 4, TSCTSF 404 may provide a subscription request message to AMF 403. The subscription request message may include the (R)AN node identity and / or (R)AN time synchronization report type that TSCTSF 404 wishes to subscribe to. As shown in operation 5, the location report request message may be shared between (R)AN402 and AMF 403. As shown in operation 6, the time synchronization report control message may be shared between (R)AN402 and AMF 403. As shown in operation 7+, AMF 403 may provide a subscription completion message to TSCTSF 404. The subscription completion message may indicate whether TSCTSF has successfully subscribed to the requested network entity and / or may include a UE identifier. The subscription completion message may be a Namf_Communication_N1N2MessageNotify message.

[0136] At operation 8, (R)AN 402 may detect a primary source event. The primary source event may be a (R)AN synchronization update. At operation 9, (R)AN 402 may provide a time synchronization report to AMF 403.

[0137] At operation 10, AMF 403 may determine the UEs affected by the primary source event. At operation 11, AMF 403 may provide an indication of one or more affected UEs affected by the primary source event to TSCTSF 404. AMF 403 may provide an indication of one or more affected UEs affected by the primary source event using a Namf_CommunicationN1N2MessageNotify message. The Namf_CommunicationN1N2MessageNotify message may include one or more UE identifiers and / or a time synchronization report of the affected UEs.

[0138] At operation 12, TSCTSF 404 may cause a time synchronization report to be provided to one or more affected UEs. Figure 6-Figure 8 The provision of time synchronization reports is discussed in more detail.

[0139] Figure 6-Figure 8An example implementation of the method of the message flow described herein is illustrated, wherein a time synchronization report is provided to one or more affected UEs. In some embodiments, the TSCTSF may generate the time synchronization report, as described above. Alternatively, the (R)AN node may generate the time synchronization report. Regardless of the entity that generates the time synchronization report, the TSCTSF needs to be aware of the UE's subscription to this type of time synchronization report, and the TSCTSF will configure the (R)AN node with appropriate configuration to allow appropriate time synchronization reporting on a cell level or UE level basis. The (R)AN node may be configured to always report time synchronization information to the TSCTSF when a time synchronization status update is detected, and may additionally notify the UE directly.

[0140] When generating a report to the UE, depending on whether the UPF / NW-TT participates in the time synchronization distribution process (the c-plane using access layer signaling, or the u-plane using the (g)PTP message time distribution method is used to distribute the 5G clock to the UE), the TSCTSF may need to write the time synchronization report considering only the (R)AN node report (if the c-plane time distribution method is used) and the UPF / NW / TT node report (if the u-plane time distribution method is used).

[0141] Figure 6 An example message flow is illustrated when the (R)AN node 402 notifies the UE using SIB9 signaling. At operation 1, the 5GS may have been configured for network time synchronization reporting to the UE. At operation 2, using the (R)AN node, the (R)AN 402 may provide a time synchronization report to the UE 401 using SIB9 signaling. The SIB9 may include only: a flag for notifying a UE in RRC_IDLE mode or RRC_INACTIVE mode that there is a network timing synchronization report. The SIB9 signaling may include a limited update report, which may include only mandatory information elements for the time synchronization report. A UE in the RRC_IDLE / INACTIVE state may only need this type of report without re-establishing a connection with the 5GS. If the UE determines that it needs more details, it may re-establish a connection with the 5GS and receive a complete report via RRC or NAS signaling.

[0142] At operation 3, the interested UE 401 may wake up (if not already in RRC_CONNECTED mode) and re-establish connection with the 5GS and receive a complete report via RRC or NAS signaling.

[0143] Figure 7An example message flow is illustrated when the (R)AN node 402 notifies the UE using RRC signaling. At operation 1, the 5GS may have been configured for network time synchronization reporting to the UE. At operation 2, the TSCTSF 404 may generate a time synchronization report for the UE. At operation 3, the TSCTSF 404 may notify the AMF 403 of the time synchronization report.

[0144] At operation 4, the AMF 403 may determine the reachability of each UE and / or the notification configuration of each UE.

[0145] In the case where the UE is in IDLE mode and a timing synchronization status report is required, at operation 5, the AMF 403 may include the timing synchronization status notification as part of the "Paging Assistance Data" in the NGAP signaling and forward it to the (R)AP node of the (R)AN 402. The paging procedure or system information block (SIB) message may be extended to include an optional network time synchronization report to directly update the UE. Alternatively, the time synchronization report from the TSC TSF is used by the AMF 403 as a trigger for paging the UE in IDLE mode. In this case, the UE will only initiate a service request, and the network provides the UE with the timing synchronization status using a service acceptance or using an RRC reconfiguration procedure, which may include a timing synchronization status report.

[0146] In the case that UE 401 is in INACTIVE mode and a time synchronization report is required, AMF 403 may include a time synchronization status report as part of the "RRC Inactive Assistance Data" in the NGAP signaling and forward it to the (R)AP node of (R)AN 402. The paging procedure may be extended to include an optional network time synchronization report to directly update the UE. Alternatively, the time synchronization report from TSCTSF 404 is used as a trigger to update the RRC Inactive Assistance Data, and the network may update the UE with only the timing synchronization status.

[0147] In case the UE is in CONNECTED mode, RRC reconfiguration or DL ​​information transmission can be used for UE in RRC-CONNECTED mode. The corresponding message needs to be extended to include time synchronization status report.

[0148] Figure 8An example message flow is illustrated when the TSCTSF 404 notifies the UE using a NAS report. The NAS report may send a complete network time synchronization report to the UE (i.e., via the NG-RAN and UPF / NW-TT, if applicable). At operation 1, the 5GS may have been configured for a network time synchronization report to the UE. At operation 2, the TSCTSF 404 may generate a time synchronization report for the UE. At operation 3, the TSCTSF 404 may notify the AMF 403 of the time synchronization report. At operation 4, the AMF 403 may use the NAS report to notify the UE 401 of the time synchronization report. If a downlink NAS transmission procedure is used, the AMF is responsible for triggering the downlink NAS transmission procedure towards the UE 401. The downlink NAS transmission procedure is used to send network timing synchronization information to the UE as an optional field.

[0149] Alternatively, if the Port Management Information Container (PMIC) forwarding method is used, the TSCTSF 404 contacts the SMF (not shown) to send the PMIC to the affected UE / DS-TT.NAS PDU session procedures are required, so the forwarding of the network time synchronization report will be coupled to the PDU session signaling.

[0150] Reference now Fig.10 , illustrates an example workflow of various components of a communication system, such as UE, R(AN), AMF, SMF, TSCTSF, NEF, AF, or other components previously described, for example, in conjunction with other figures, according to an example embodiment. Now refer to Fig.10 , illustrates a method 1000, which may be performed by one or more of the entities, the entity comprising: means for receiving a network timing synchronization status request at a network entity at 1001, such as a processor 302 and a network interface 306. The network timing synchronization status request may include: an indication of one or more UEs to be provided with a time synchronization report. In some embodiments, the network timing synchronization status request is received from one or more user equipments. Alternatively, in some embodiments, the network timing synchronization status request is received from another network entity (e.g., AF).

[0151] The method 1000 may include: a component, such as the processor 302, for determining one or more provider network entities for each UE at 1002 to request a time synchronization status from the one or more provider network entities. The one or more provider network entities are determined to request a time synchronization status from the one or more provider network entities, and the one or more provider network entities include one or more of the following: an access network (AN) node, an AMF, an SMF, and / or a UPF.

[0152] In some embodiments, the method further includes: a component for subscribing to the access network node timing synchronization status of each UE via a subscription request message, such as the processor 302, the network interface 306, etc. The subscription request message may include: a time synchronization report type indicating the type of the requested time synchronization report. In some embodiments, the method further includes: a component for receiving a time synchronization report message in response to the subscription request message, such as the processor 302, the network interface 306, etc., wherein the time synchronization report message includes the time synchronization report. In some embodiments, the method further includes: a component for subscribing to the UE location information of each UE via a location subscription request message, such as the processor 302, the network interface 306, etc. In some embodiments, the method further includes: a component for determining the binding of each UE with respect to the access network node, such as the processor 302, etc.

[0153] The method 100 may also include: a component for generating a time synchronization report indicating a primary source event in response to receiving an indication of the primary source event at 1003, such as the processor 302, the network interface 306, etc. In some embodiments, the method also includes: determining, by the network entity, one or more affected UEs affected by the primary source event. Alternatively, in some embodiments, the method also includes: a component for receiving, by another network entity (e.g., AMF), an indication of one or more affected UEs affected by the primary source event, such as the processor 302, the network interface 306, etc. The time synchronization report may indicate whether different elements are optional or mandatory.

[0154] The method 1000 may also include a component for causing a time synchronization status report to be provided to one or more affected UEs, such as the processor 302, the network interface 306, etc. In some embodiments, causing the time synchronization report to be provided includes: i) causing the (R)AN to provide a time synchronization report, or ii) causing the AMF to trigger a paging or UE information transfer procedure. The time synchronization report may be provided via non-access stratum (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session process signaling.

[0155] Reference now Fig.11 , illustrates an example workflow of various components of a communication system, such as UE, R(AN), AMF, SMF, TSCTSF, NEF, AF, or other components previously described, for example, in conjunction with other figures, according to an example embodiment. Now refer to Fig.11, illustrates a method 1100, which may be performed by one or more of the entities, the entity comprising: a component for receiving a time synchronization report at 1101, such as a processor 302 and a network interface 306. In some embodiments, the method 1100 further comprises: a component for storing the time synchronization report, such as a processor 302, a memory 304, a network interface 306, etc.

[0156] The method also includes: components for updating one or more configurations based at least in part on the time synchronization report, such as the processor 302, the network interface 306, etc. If the device has multiple time sources available, updating the time synchronization report may include: changing the primary time source from which the time information is received in response to receiving the network timing synchronization status request. Additionally or alternatively, updating the time synchronization report may include: relying on the retention capability of the time information in response to receiving the network timing synchronization status request.

[0157] In some embodiments, the method further comprises means, such as the processor 302, the network interface 306, etc., for causing the master announcement updates to be provided to the associated general packet transport protocol network if the apparatus is a GM of (g)PTP.

[0158] In some embodiments, the method 1100 further includes means for causing a time source event report indicating a time source event (e.g., degradation, recovery, failure) to be provided if the device relies on the timestamp for application-level actions, such as the processor 302, the network interface 306, etc. The time source event report can be used for higher layers where there may be problems with application layer operations.

[0159] Reference now Fig.12 , illustrates an example workflow of various components of a communication system, such as UE, R(AN), AMF, SMF, TSCTSF, NEF, AF, or other components previously described, for example, in conjunction with other figures, according to an example embodiment. Now refer to Fig.12 , illustrates a method 1200, which may be performed by one or more of the entities, the entity comprising: a component for receiving an indication to provide a time synchronization report to one or more UEs, such as a processor 302 and a network interface 306. In some embodiments, the indication to provide the time synchronization report is received from the TSCTSF. In some embodiments, the indication to provide the time synchronization report is received via NAS signaling.

[0160] In some embodiments, the method further comprises: a component for providing a time synchronization report to one or more UEs, such as a processor 302, a network interface 306, etc. In some embodiments, the time synchronization report is provided via SIB9 signaling or RRC signaling. In some embodiments, providing the time synchronization report includes triggering a paging or UE information transmission process. In some embodiments, the time synchronization report is provided at the PMIC.

[0161] Figure 10-12 A flowchart depicting the operation according to an example embodiment of the present disclosure is illustrated. It should be understood that each block of the flowchart and the combination of blocks in the flowchart can be implemented in various ways, such as hardware, firmware, processor, circuit system, and / or other communication devices associated with the execution of software including one or more computer program instructions. For example, one or more of the above-mentioned processes or operations can be embodied by computer program instructions. In this regard, the computer program instructions embodying the above-mentioned processes or operations can be stored by the memory 304 of the device (e.g., device 300, UE 401, TSCTSF 404) using an embodiment of the present invention, and executed by the processor 302. As will be understood, any such computer program instructions can be loaded onto a computer or other programmable device (e.g., hardware) to produce a machine so that the resulting computer or other programmable device implements the functions specified in the flowchart blocks. These computer program instructions can also be stored in a computer-readable memory, which can instruct a computer or other programmable device to operate in a specific manner so that the instructions stored in the computer programmable memory produce a product, and the execution of the product implements the functions specified in the flowchart blocks. Computer program instructions may also be loaded onto a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions executed in the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.

[0162] Therefore, the blocks of the flow chart support the combination of components for performing the specified functions and the combination of operations for performing specific functions. It will also be understood that one or more blocks of the flow chart and the combination of blocks in the flow chart can be implemented by a computer system based on special-purpose hardware that performs the specified functions, or a combination of special-purpose hardware and computer instructions.

[0163] In an example embodiment, a method is provided, the method comprising: receiving a network timing synchronization status request at a network entity, wherein the network timing synchronization status request comprises: an indication of one or more user equipment (UE) to provide a time synchronization report to the one or more user equipment. In some implementations, the method further comprises: determining one or more provider network entities for each UE to request time synchronization status from the one or more provider network entities. In some embodiments, the method further comprises: in response to receiving an indication of a primary source event, generating a time synchronization report indicating the primary source event. In some embodiments, the method further comprises: causing the time synchronization report to be provided to one or more affected UEs.

[0164] In some embodiments, the method further comprises: determining, by the network entity, one or more affected UEs affected by the primary source event.

[0165] In some embodiments, the method further comprises: receiving, by another network entity, an indication of one or more affected UEs affected by the primary source event.

[0166] In some embodiments, the method further comprises: subscribing to the access network node or the access network node timing synchronization state of each UE via a subscription request message. In some embodiments, the method further comprises: receiving a time synchronization report message in response to the subscription request message, wherein the time synchronization report message comprises a time synchronization report. In some embodiments, the subscription request message comprises: a time synchronization report type indicating the type of the requested time synchronization report.

[0167] In some embodiments, the method further comprises: subscribing to the UE location information of each UE via a location subscription request message.

[0168] In some embodiments, the method further comprises: determining a binding of each UE with respect to an access network node.

[0169] In some embodiments, the method further comprises causing a network timing synchronization report included in a port management information container (PMIC) to be provided to the UE.

[0170] In some embodiments, the network timing synchronization state request is received from one or more user equipments. In some embodiments, the network timing synchronization state request is received from another network entity. In some embodiments, one or more provider network entities are determined to request time synchronization state from one or more provider network entities, and the one or more provider network entities include one or more of the following: access network (AN) node, access and mobility management function (AMF), session management function (SMF), user plane function (UPF), or network side converter (NW-TT). In some embodiments, the network timing synchronization report is provided to the affected UE via non-access layer (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session process signaling. In some embodiments, the network timing synchronization request indicates whether each information element included in the network timing synchronization state request is optional or mandatory in the time synchronization report. In some embodiments, the information element of the network timing synchronization report includes at least one of the following: primary source type, lock state, primary source event, or primary source quality.

[0171] In an example embodiment, an apparatus is provided, the apparatus comprising: a component for receiving a network timing synchronization status request at a network entity, wherein the network timing synchronization status request comprises: an indication of one or more user equipment (UE) to provide a time synchronization report to the one or more user equipment. In some embodiments, the apparatus further comprises: a component for determining one or more provider network entities for each UE to request time synchronization status from the one or more provider network entities. In some embodiments, the apparatus further comprises: a component for generating a time synchronization report indicating a primary source event in response to receiving an indication of a primary source event. In some embodiments, the apparatus further comprises: a component for causing the time synchronization report to be provided to one or more affected UEs.

[0172] In some embodiments, the apparatus further comprises: means for determining, by the network entity, one or more affected UEs affected by the primary source event.

[0173] In some embodiments, the apparatus further comprises means for receiving, by another network entity, an indication of one or more affected UEs affected by the primary source event.

[0174] In some embodiments, the apparatus further comprises: a component for subscribing to the timing synchronization status of the access network node or the access network node of each UE via a subscription request message. In some embodiments, the apparatus further comprises: a component for receiving a time synchronization report message in response to the subscription request message, wherein the time synchronization report message comprises a time synchronization report. In some embodiments, the subscription request message comprises: a time synchronization report type indicating the type of the requested time synchronization report.

[0175] In some embodiments, the apparatus further comprises means for subscribing to UE location information of each UE via a location subscription request message.

[0176] In some embodiments, the apparatus further comprises: means for determining a binding of each UE with respect to an access network node.

[0177] In some embodiments, the apparatus further comprises means for causing a network timing synchronization report included in a port management information container (PMIC) to be provided to the UE.

[0178] In some embodiments, the network timing synchronization state request is received from one or more user equipments. In some embodiments, the network timing synchronization state request is received from another network entity. In some embodiments, one or more provider network entities are determined to request time synchronization state from one or more provider network entities, and the one or more provider network entities include one or more of the following: access network (AN) node, access and mobility management function (AMF), session management function (SMF), user plane function (UPF), or network side converter (NW-TT). In some embodiments, the network timing synchronization report is provided to the affected UE via non-access layer (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session process signaling. In some embodiments, the network timing synchronization request indicates whether each information element included in the network timing synchronization state request is optional or mandatory in the time synchronization report. In some embodiments, the information element of the network timing synchronization report includes at least one of the following: primary source type, lock state, primary source event, or primary source quality.

[0179] In another example embodiment, an apparatus may be provided, the apparatus comprising at least one processor and at least one memory, the at least one memory comprising computer program code for one or more programs, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: receive a network timing synchronization status request at a network entity, wherein the network timing synchronization status request comprises: an indication of one or more user equipments (UEs) to provide a time synchronization report to the one or more user equipments. In some embodiments, the apparatus may include computer program code, the computer program code being further configured to, with the at least one processor, cause the apparatus to at least: determine one or more provider network entities for each UE to request time synchronization status from the one or more provider network entities. In some embodiments, the apparatus may include computer program code, the computer program code being further configured to, with the at least one processor, cause the apparatus to at least: generate a time synchronization report indicating a primary source event in response to receiving an indication of a primary source event. In some embodiments, the apparatus may include computer program code, the computer program code being further configured to, with the at least one processor, cause the apparatus to at least: cause the time synchronization report to be provided to one or more affected UEs.

[0180] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: determine, by the network entity, one or more affected UEs affected by the primary source event.

[0181] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: receive, by another network entity, an indication of one or more affected UEs affected by the primary source event.

[0182] In some embodiments, the apparatus may include computer program code, the computer program code is further configured to, together with the at least one processor, enable the apparatus to at least: subscribe to the access network node or the access network node timing synchronization state of each UE via a subscription request message. In some embodiments, the apparatus may include computer program code, the computer program code is further configured to, together with the at least one processor, enable the apparatus to at least: receive a time synchronization report message in response to the subscription request message, wherein the time synchronization report message includes a time synchronization report. In some embodiments, the subscription request message includes: a time synchronization report type indicating the type of the requested time synchronization report.

[0183] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: subscribe to UE location information of each UE via a location subscription request message.

[0184] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: determine a binding of each UE with respect to an access network node.

[0185] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: cause a network timing synchronization report included in a port management information container (PMIC) to be provided to the UE.

[0186] In some embodiments, the network timing synchronization state request is received from one or more user equipments. In some embodiments, the network timing synchronization state request is received from another network entity. In some embodiments, one or more provider network entities are determined to request time synchronization state from one or more provider network entities, and the one or more provider network entities include one or more of the following: access network (AN) node, access and mobility management function (AMF), session management function (SMF), user plane function (UPF), or network side converter (NW-TT). In some embodiments, the network timing synchronization report is provided to the affected UE via non-access layer (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session process signaling. In some embodiments, the network timing synchronization request indicates whether each information element included in the network timing synchronization state request is optional or mandatory in the time synchronization report. In some embodiments, the information element of the network timing synchronization report includes at least one of the following: primary source type, lock state, primary source event, or primary source quality.

[0187] In another example embodiment, a computer program product may be provided, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising the program code instructions being configured to, when executed: receive a network timing synchronization status request at a network entity, wherein the network timing synchronization status request comprises: an indication of one or more user equipment (UE) to provide a time synchronization report to the one or more user equipment. In some embodiments, the computer-executable program code instructions comprising the program code instructions may also be configured to, when executed: determine one or more provider network entities for each UE to request time synchronization status from the one or more provider network entities. In some embodiments, the computer-executable program code instructions comprising the program code instructions may also be configured to, when executed: generate a time synchronization report indicating a primary source event in response to receiving an indication of a primary source event. In some embodiments, the computer-executable program code instructions comprising the program code instructions may also be configured to, when executed: cause the time synchronization report to be provided to one or more affected UEs.

[0188] In some embodiments, the computer executable program code instructions including the program code instructions may be further configured to, when executed: determine, by the network entity, one or more affected UEs affected by the primary source event.

[0189] In some embodiments, the computer executable program code instructions including the program code instructions may be further configured to, when executed: receive, by another network entity, an indication of one or more affected UEs affected by the primary source event.

[0190] In some embodiments, the computer executable program code instructions including the program code instructions may also be configured to, when executed: subscribe to the access network node or the access network node timing synchronization state of each UE via a subscription request message. In some embodiments, the computer executable program code instructions including the program code instructions may also be configured to, when executed: receive a time synchronization report message in response to the subscription request message, wherein the time synchronization report message includes a time synchronization report. In some embodiments, the subscription request message includes: a time synchronization report type indicating the type of the requested time synchronization report.

[0191] In some embodiments, the computer executable program code instructions including the program code instructions may also be configured to, when executed, subscribe to UE location information of each UE via a location subscription request message.

[0192] In some embodiments, the computer executable program code instructions comprising the program code instructions may also be configured to, when executed: determine a binding of each UE with respect to an access network node.

[0193] In some embodiments, the computer executable program code instructions including the program code instructions may be further configured to, when executed, cause: a network timing synchronization report included in a port management information container (PMIC) to be provided to the UE.

[0194] In some embodiments, the network timing synchronization state request is received from one or more user equipments. In some embodiments, the network timing synchronization state request is received from another network entity. In some embodiments, one or more provider network entities are determined to request time synchronization state from one or more provider network entities, and the one or more provider network entities include one or more of the following: access network (AN) node, access and mobility management function (AMF), session management function (SMF), user plane function (UPF), or network side converter (NW-TT). In some embodiments, the network timing synchronization report is provided to the affected UE via non-access layer (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session process signaling. In some embodiments, the network timing synchronization request indicates whether each information element included in the network timing synchronization state request is optional or mandatory in the time synchronization report. In some embodiments, the information element of the network timing synchronization report includes at least one of the following: primary source type, lock state, primary source event, or primary source quality.

[0195] In another example embodiment, a method is provided, the method comprising: receiving a time synchronization report. The method further comprises: updating one or more configurations based at least in part on the time synchronization report.

[0196] In some embodiments, the method further comprises: storing the time synchronization report.

[0197] In some embodiments, the method further comprises causing the master advertised update to be provided to an associated precision time protocol network.

[0198] In some embodiments, the method further comprises causing a time source event report indicative of the time source event to be provided to a higher layer.

[0199] In some embodiments, the method further comprises causing a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

[0200] In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, changing a primary time source from which time information is received. In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, relying on a retention capability of time information. In some embodiments, the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

[0201] In another example embodiment, an apparatus is provided that includes means for receiving a time synchronization report. The apparatus also includes means for updating one or more configurations based at least in part on the time synchronization report.

[0202] In some embodiments, the apparatus further comprises: means for storing the time synchronization report.

[0203] In some embodiments, the apparatus further comprises means for causing the master advertise updates to be provided to an associated precision time protocol network.

[0204] In some embodiments, the apparatus further comprises: means for causing a time source event report indicative of the time source event to be provided to a higher layer.

[0205] In some embodiments, the apparatus further comprises means for causing a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

[0206] In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, changing a primary time source from which time information is received. In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, relying on a retention capability of time information. In some embodiments, the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

[0207] In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, changing a primary time source from which time information is received. In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, relying on a retention capability of time information. In some embodiments, the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

[0208] In another example embodiment, an apparatus may be provided, the apparatus comprising at least one processor and at least one memory, the at least one memory comprising computer program code for one or more programs, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: receive a time synchronization report. The apparatus may include computer program code, the computer program code being further configured to, with the at least one processor, cause the apparatus to at least: update one or more configurations based at least in part on the time synchronization report.

[0209] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: store a time synchronization report.

[0210] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: cause a master advertise update to be provided to an associated precision time protocol network.

[0211] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: cause a time source event report indicative of the time source event to be provided to a higher layer.

[0212] In some embodiments, the apparatus may include computer program code further configured to, with the at least one processor, cause the apparatus to at least: cause a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

[0213] In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, changing a primary time source from which time information is received. In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, relying on a retention capability of time information. In some embodiments, the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

[0214] In another example embodiment, a computer program product may be provided, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising the program code instructions being configured to, when executed: receive a time synchronization report. The computer-executable program code instructions comprising the program code instructions may also be configured to, when executed: update one or more configurations based at least in part on the time synchronization report.

[0215] In some embodiments, the computer executable program code instructions comprising the program code instructions may be further configured, when executed, to: store a time synchronization report.

[0216] In some embodiments, the computer executable program code instructions comprising the program code instructions may be further configured, when executed, to: cause a master advertise update to be provided to an associated precision time protocol network.

[0217] In some embodiments, the computer executable program code instructions comprising the program code instructions may be further configured to, when executed, cause a time source event report indicative of the time source event to be provided to a higher layer.

[0218] In some embodiments, the computer executable program code instructions comprising the program code instructions may be further configured to, when executed: cause a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

[0219] In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, changing a primary time source from which time information is received. In some embodiments, updating one or more configurations includes: in response to receiving a network timing synchronization status request, relying on a retention capability of time information. In some embodiments, the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

[0220] In another example embodiment, a method is provided, the method comprising: receiving, by a network entity, an indication to provide a time synchronization report to one or more user equipments (UEs). The method further comprises: providing the time synchronization report to the one or more UEs.

[0221] In some embodiments, the network entity is an access network node, an access and mobility management function, or a session management function. In some embodiments, the time synchronization report is provided via SIB9 signaling or radio resource connection (RRC) signaling. In some embodiments, providing the time synchronization report further comprises: triggering a paging or UE information transfer process. In some embodiments, an indication to provide the time synchronization report is received via non-access stratum (NAS) signaling. In some embodiments, the time synchronization report is provided in a port management information container (PMIC).

[0222] In another example embodiment, an apparatus is provided that includes means for receiving, by a network entity, an indication to provide a time synchronization report to one or more user equipments (UEs). The apparatus also includes means for providing the time synchronization report to the one or more UEs.

[0223] In some embodiments, the network entity is an access network node, an access and mobility management function, or a session management function. In some embodiments, the time synchronization report is provided via SIB9 signaling, or radio resource connection (RRC) signaling. In some embodiments, providing the time synchronization report further comprises: triggering a paging or UE information transfer process. In some embodiments, an indication to provide the time synchronization report is received via non-access stratum (NAS) signaling. In some embodiments, the time synchronization report is provided in a port management information container (PMIC).

[0224] In another example embodiment, an apparatus may be provided, the apparatus comprising at least one processor and at least one memory, the at least one memory comprising computer program code for one or more programs, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: receive, by a network entity, an indication to provide a time synchronization report to one or more user equipments (UEs). The apparatus may include computer program code, the computer program code being further configured to, with the at least one processor, cause the apparatus to at least: provide a time synchronization report to one or more UEs.

[0225] In some embodiments, the network entity is an access network node, an access and mobility management function, or a session management function. In some embodiments, the time synchronization report is provided via SIB9 signaling, or radio resource connection (RRC) signaling. In some embodiments, providing the time synchronization report further comprises: triggering a paging or UE information transfer process. In some embodiments, an indication to provide the time synchronization report is received via non-access stratum (NAS) signaling. In some embodiments, the time synchronization report is provided in a port management information container (PMIC).

[0226] In another example embodiment, a computer program product may be provided, the computer program product including at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions including the program code instructions being configured to, when executed: receive, by a network entity, an indication to provide a time synchronization report to one or more user equipments (UEs). The computer-executable program code instructions including the program code instructions may also be configured to, when executed, cause the apparatus to at least: provide a time synchronization report to one or more UEs.

[0227] In some embodiments, the network entity is an access network node, an access and mobility management function, or a session management function. In some embodiments, the time synchronization report is provided via SIB9 signaling, or radio resource connection (RRC) signaling. In some embodiments, providing the time synchronization report further comprises: triggering a paging or UE information transfer process. In some embodiments, an indication to provide the time synchronization report is received via non-access stratum (NAS) signaling. In some embodiments, the time synchronization report is provided in a port management information container (PMIC).

[0228] The above overview is provided only for summarizing some example embodiments to provide a basic understanding of some aspects of the present invention. Therefore, it should be understood that the above-described embodiments are merely examples and should not be interpreted as narrowing the scope or spirit of the present invention in any way. It should be understood that, in addition to those summarized here, the scope of the present invention also includes many potential embodiments, some of which will be further described below. From the specification, drawings, and claims, other features, aspects, and advantages of this theme will become clear.

[0229] Many modifications and other embodiments of the invention described herein will come to mind to those skilled in the art with the benefit of the teachings given in the above description and the associated drawings. Therefore, it should be understood that the invention is not limited to the specific embodiments disclosed, and modifications and other embodiments are intended to be included within the scope of the appended claims.

[0230] Furthermore, although the foregoing description and the associated drawings describe example embodiments in the context of certain example combinations of elements and / or functions, it should be understood that alternative embodiments may provide different combinations of elements and / or functions without departing from the scope of the appended claims. In this regard, different combinations of elements and functions than those explicitly described above are also contemplated, for example, as described in some of the appended claims. Although specific terms are used herein, they are used only in a general and descriptive sense and not for purposes of limitation.

Claims

1. A method, include: Receiving, at a network entity, a network timing synchronization status request, wherein the network timing synchronization status request includes: an indication of one or more user equipments (UEs) to provide a time synchronization report to the one or more user equipments; determining one or more provider network entities for each UE to request a time synchronization status from the one or more provider network entities; In response to receiving an indication of a primary source event, generating a time synchronization report indicating the primary source event; and Such that the time synchronization report will be provided to one or more affected UEs.

2. The method according to claim 1, further comprising: include: One or more affected UEs affected by the primary source event are determined by the network entity.

3. The method according to claim 1, further comprising: include: An indication of one or more affected UEs affected by the primary source event is received by another network entity. 4 . The method of claim 1 , wherein the network timing synchronization status request is received from one or more user devices. The method of claim 1 , wherein the network timing synchronization status request is received from another network entity.

6. The method according to claim 1, further comprising: include: The access network node or the access network node timing synchronization status of each UE is subscribed to via a subscription request message.

7. The method according to claim 6, wherein the subscription request message include: A time synchronization report type indicating the type of time synchronization report requested.

8. The method according to claim 6, further comprising: include: A time synchronization report message is received in response to the subscription request message, wherein the time synchronization report message includes a time synchronization report.

9. The method according to claim 1, further comprising: include: The UE location information of each UE is subscribed to via the location subscription request message.

10. The method of claim 1, wherein the one or more provider network entities are determined to request a time synchronization status from the one or more provider network entities, the one or more provider network entities comprising one or more of: an access network (AN) node, an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), or a network side translator (NW-TT).

11. The method according to claim 1, further comprising: include: Determine the binding of each UE with respect to the access network node.

12. The method of claim 1, wherein the network timing synchronization report is provided to the affected UE via non-access stratum (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session procedure signaling.

13. The method of claim 1 , wherein causing the time synchronization report to be provided to one or more affected UEs further comprises: include: Such that a network timing synchronization report included in a port management information container (PMIC) will be provided to the UE.

14. The method of claim 1, wherein the network timing synchronization request indicates whether each information element included in the network timing synchronization status request is optional or mandatory in the time synchronization report.

15. The method of claim 1, wherein the information element of the network timing synchronization report comprises at least one of the following: primary source type, lock status, primary source event, or primary source quality.

16. A method, include: Receive time synchronization report; as well as Based at least in part on the time synchronization report, one or more configurations are updated.

17. The method of claim 16, wherein updating one or more configuration include: In response to receiving the network timing synchronization state request, a primary time source from which time information is received is changed.

18. The method of claim 16, wherein updating one or more configuration include: In response to receiving the network timing synchronization status request, relying on the ability to maintain time information 19. The method according to claim 16, further comprising: include: The time synchronization report is stored.

20. The method according to claim 16, further comprising: include: Enables high-level notification updates to be provided to the associated Precision Time Protocol network.

21. The method according to claim 16, further comprising: include: A time source event report indicating a time source event is provided to a higher layer.

22. The method according to claim 16, further comprising: include: Causes a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

23. The method of claim 16, wherein the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

24. A method, include: Receiving, by a network entity, an indication to provide time synchronization reporting to one or more user equipments (UEs); as well as Provide time synchronization reports to one or more UEs.

25. The method of claim 24, wherein the network entity is an access network node, an access and mobility management function, or a session management function.

26. The method of claim 24, wherein the time synchronization report is provided via SIB9 signaling, or Radio Resource Connection (RRC) signaling.

27. The method of claim 24, wherein providing the time synchronization report further comprises: include: Trigger paging or UE information delivery process.

28. The method of claim 24, wherein the indication to provide a time synchronization report is received via non-access stratum (NAS) signaling.

29. The method of claim 24, wherein the time synchronization report is provided in a port management information container (PMIC).

30. An apparatus comprising at least one processor and at least one memory, the at least one memory comprising computer program code for one or more programs, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: A network timing synchronization status request is received at a network entity, wherein the network timing synchronization status request include: an indication of one or more user equipments (UEs) to provide a time synchronization report to the one or more user equipments; determining one or more provider network entities for each UE to request a time synchronization status from the one or more provider network entities; In response to receiving an indication of a primary source event, generating a time synchronization report indicating the primary source event; as well as Such that the time synchronization report will be provided to one or more affected UEs.

31. The apparatus of claim 30, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: One or more affected UEs affected by the primary source event are determined by the network entity.

32. The apparatus of claim 30, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: An indication of one or more affected UEs affected by the primary source event is received by another network entity.

33. The apparatus of claim 30, wherein the network timing synchronization status request is received from one or more user equipment.

34. The apparatus of claim 30, wherein the network timing synchronization status request is received from another network entity.

35. The apparatus of claim 30, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: The access network node or the access network node timing synchronization status of each UE is subscribed to via a subscription request message.

36. The apparatus of claim 35, wherein the subscription request message include: A time synchronization report type indicating the type of time synchronization report requested.

37. The apparatus of claim 35, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: A time synchronization report message is received in response to the subscription request message, wherein the time synchronization report message includes a time synchronization report.

38. The apparatus of claim 30, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: The UE location information of each UE is subscribed to via the location subscription request message.

39. An apparatus according to claim 30, wherein the one or more provider network entities are determined to request a time synchronization status from the one or more provider network entities, and the one or more provider network entities include one or more of the following: an access network (AN) node, an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), or a network side translator (NW-TT).

40. The apparatus of claim 30, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: Determine the binding of each UE with respect to the access network node.

41. The apparatus of claim 30, wherein the network timing synchronization report is provided to the affected UE via non-access stratum (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session procedure signaling.

42. The apparatus of claim 30, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: Such that a network timing synchronization report included in a port management information container (PMIC) will be provided to the UE.

43. The apparatus of claim 30, wherein the network timing synchronization request indicates whether each information element included in the network timing synchronization status request is optional or mandatory in the time synchronization report.

44. The apparatus of claim 30, wherein the information element of the network timing synchronization report comprises at least one of the following: primary source type, lock status, primary source event, or primary source quality.

45. A computer program product comprising at least one non-transitory computer readable storage medium having computer executable program code instructions stored therein, the computer executable program code instructions comprising program code instructions being configured to, when executed: A network timing synchronization status request is received at a network entity, wherein the network timing synchronization status request include: an indication of one or more user equipments (UEs) to provide a time synchronization report to the one or more user equipments; determining one or more provider network entities for each UE to request a time synchronization status from the one or more provider network entities; In response to receiving an indication of a primary source event, generating a time synchronization report indicating the primary source event; as well as Such that the time synchronization report will be provided to one or more affected UEs.

46. ​​The computer program product of claim 45, wherein the computer executable program code instructions comprising program code instructions are further configured to, when executed: One or more affected UEs affected by the primary source event are determined by the network entity.

47. The computer program product of claim 45, wherein the computer executable program code instructions comprising program code instructions are further configured to, when executed: An indication of one or more affected UEs affected by the primary source event is received by another network entity.

48. The computer program product of claim 45, wherein the network timing synchronization status request is received from one or more user devices.

49. The computer program product of claim 45, wherein the network timing synchronization status request is received from another network entity.

50. The computer program product of claim 45, wherein the computer executable program code instructions comprising program code instructions are further configured to, when executed: The access network node or the access network node timing synchronization status of each UE is subscribed to via a subscription request message.

51. The computer program product of claim 50, wherein the subscription request message include: A time synchronization report type indicating the type of time synchronization report requested.

52. The computer program product of claim 50, wherein the computer executable program code instructions comprising program code instructions are further configured to, when executed: A time synchronization report message is received in response to the subscription request message, wherein the time synchronization report message includes a time synchronization report.

53. The computer program product of claim 45, wherein the computer executable program code instructions comprising program code instructions are further configured to, when executed: The UE location information of each UE is subscribed to via the location subscription request message.

54. The computer program product of claim 45, wherein the one or more provider network entities are determined to request a time synchronization status from the one or more provider network entities, the one or more provider network entities comprising one or more of: an access network (AN) node, an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), or a network side translator (NW-TT).

55. The computer program product of claim 45, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: Determine the binding of each UE with respect to the access network node.

56. The computer program product of claim 45, wherein the network timing synchronization report is provided to the affected UE via non-access stratum (NAS) signaling, SIB9 signaling, RRC signaling, or PDU session procedure signaling.

57. The computer program product of claim 45, wherein the computer executable program code instructions comprising program code instructions are further configured to, when executed: Such that a network timing synchronization report included in a port management information container (PMIC) will be provided to the UE.

58. The computer program product of claim 45, wherein the network timing synchronization request indicates whether each information element included in the network timing synchronization status request is optional or mandatory in the time synchronization report.

59. The computer program product of claim 45, wherein the information elements of the network timing synchronization report include at least one of: primary source type, lock status, primary source events, or primary source quality.

60. An apparatus comprising at least one processor and at least one memory, the at least one memory comprising computer program code for one or more programs, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: receiving a time synchronization report; and Based at least in part on the time synchronization report, one or more configurations are updated.

61. The apparatus of claim 60, wherein when updating one or more configurations, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: In response to receiving the network timing synchronization state request, a primary time source from which time information is received is changed.

62. The apparatus of claim 60, wherein when updating one or more configurations, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: In response to receiving the network timing synchronization status request, relying on the ability to maintain time information.

63. The apparatus of claim 60, wherein when updating one or more configurations, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: The time synchronization report is stored.

64. The apparatus of claim 60, wherein when updating one or more configurations, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: Enables high-level notification updates to be provided to the associated Precision Time Protocol network.

65. The apparatus of claim 60, wherein when updating one or more configurations, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: A time source event report indicating a time source event is provided to a higher layer.

66. The apparatus of claim 60, wherein when updating one or more configurations, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to at least: Causes a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

67. The apparatus of claim 60, wherein the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

68. A computer program product comprising at least one non-transitory computer readable storage medium having computer executable program code instructions stored therein, the computer executable program code instructions comprising program code instructions being configured to, when executed: receiving a time synchronization report; and Based at least in part on the time synchronization report, one or more configurations are updated.

69. The computer program product of claim 68, wherein when updating one or more configurations, the computer executable program code instructions comprising program code instructions are further configured to, when executed: In response to receiving the network timing synchronization state request, a primary time source from which time information is received is changed.

70. The computer program product of claim 68, wherein when updating one or more configurations, the computer executable program code instructions comprising program code instructions are further configured to, when executed: In response to receiving the network timing synchronization status request, relying on the ability to maintain time information.

71. The computer program product of claim 68, wherein when updating one or more configurations, the computer executable program code instructions comprising program code instructions are further configured to, when executed: The time synchronization report is stored.

72. The computer program product of claim 68, wherein when updating one or more configurations, the computer executable program code instructions comprising program code instructions are further configured to, when executed: Enables high-level notification updates to be provided to the associated Precision Time Protocol network.

73. The computer program product of claim 68, wherein when updating one or more configurations, the computer executable program code instructions comprising program code instructions are further configured to, when executed: A time source event report indicating a time source event is provided to a higher layer.

74. The computer program product of claim 68, wherein when updating one or more configurations, the computer executable program code instructions comprising program code instructions are further configured to, when executed: Causes a network timing synchronization status request to be sent, wherein the time synchronization report is received in response to the network timing synchronization status request.

75. The computer program product of claim 68, wherein the network timing synchronization request indicates whether different information elements are optional or mandatory in the time synchronization report.

76. An apparatus comprising at least one processor and at least one memory, the at least one memory comprising computer program code for one or more programs, the at least one memory and the computer program code being configured to, with the at least one processor, cause the apparatus to at least: Receiving, by a network entity, an indication to provide time synchronization reporting to one or more user equipments (UEs); and Provide time synchronization reports to one or more UEs.

77. The apparatus of claim 76, wherein the network entity is an access network node, an access and mobility management function, or a session management function.

78. The apparatus of claim 76, wherein the time synchronization report is provided via SIB9 signaling, or Radio Resource Connection (RRC) signaling.

79. The apparatus of claim 76, wherein providing the time synchronization report further comprises: include: Trigger paging or UE information delivery process.

80. The apparatus of claim 76, wherein the indication to provide a time synchronization report is received via non-access stratum (NAS) signaling.

81. The apparatus of claim 76, wherein the time synchronization report is provided in a port management information container (PMIC).

82. A computer program product comprising at least one non-transitory computer readable storage medium having computer executable program code instructions stored therein, the computer executable program code instructions comprising program code instructions being configured to, when executed: Receiving, by a network entity, an indication to provide time synchronization reporting to one or more user equipments (UEs); and Provide time synchronization reports to one or more UEs.

83. The computer program product of claim 82, wherein the network entity is an access network node, an access and mobility management function, or a session management function.

84. The computer program product of claim 82, wherein the time synchronization report is provided via SIB9 signaling, or Radio Resource Connection (RRC) signaling.

85. The computer program product of claim 82, wherein providing the time synchronization report further comprises: include: Trigger paging or UE information delivery process.

86. The computer program product of claim 82, wherein the indication to provide a time synchronization report is received via non-access stratum (NAS) signaling.

87. The computer program product of claim 82, wherein the time synchronization report is provided in a port management information container (PMIC).

Images