METHODS, APPARATUSES, AND COMPUTER PROGRAM PRODUCTS FOR SUPPORTING CHARGING FOR TIME SYNCHRONIZATION SERVICES

TECHNOLOGICAL FIELD

[0001] An example embodiment relates generally to supporting the monitoring and communication of charging information for user equipment over a network in order to facilitate charging for time synchronization services.

BACKGROUND

[0002] The 3rd Generation Partnership Project (3GPP) is a standards organization which develops protocols for mobile telephony and is known for the development and maintenance of various standards including second generation (2G), third generation (3G), fourth generation (4G), Long Term Evolution (LTE), and fifth generation (5G) standards. The 5G network has been designed as a Service Based Architecture (SBA) or, in other words, a system architecture in which the system functionality is achieved by a set of network functions providing services to other authorized network functions to access their services.

[0003] Time synchronization is required between network entities in order to provide proper resource management, network security, maintenance planning, and network function troubleshooting among other services. Time synchronization between network entities also provides a frame of reference between all devices on the network, for example, between user equipment and a radio access network node. Without synchronized timing such network entities would be unable to accurately correlate log files or communication signals between these devices and proper communication would be difficult or even impossible.

BRIEF SUMMARY

[0004] Methods, apparatuses, and computer program products are disclosed which facilitate the communication of charging information for time synchronization services provided via a network to a user equipment. The present disclosure provides procedures related to the communication and monitoring of control plane synchronization services transmitted and monitored by way of a radio access network (e.g., gNB, ng-eNB, NodeB, etc.). Moreover, the radio access network, or components thereof, may be configured to generate control plane synchronization service reports from the synchronization service information monitored for a user equipment and transmit such reports to the either the access and mobility management function or the session management function associated with a network. In some embodiments, the session management function may be configured to further receive a user plane synchronization service report from a user plane function associated with the network. In accordance with such embodiments, the user plane function may be configured to monitor synchronization service information transmitted to the user equipment via the radio access network. For example, the user plane function may cause transmission of generic precision time protocol packets to the user equipment via a gNB in order to provide time synchronization services, as such, the user plane function monitors the rendered time synchronization services and reports this information to the session management function in the form of the user plane synchronization service report.

[0005] Upon receipt of the control plane and/or user plane synchronization service report(s) the coordinating network function (e.g., access and mobility management function, session management function, the like, or combinations thereof) may further process the time synchronization service information. The coordinating network function may cause transmission of the processed time synchronization service information to a charging function. Upon receipt of the time synchronization service information, the charging function may be configured to render charges to an user account associated with the user equipment identified by the time synchronization service information. In some embodiments, the processing of the time synchronization service information and/or the charging of user account is performed in accordance with a charging profile, a services contract, a charging model, charging rates, the like, or combinations thereof. For example, a user equipment may be charged for time synchronization services rendered by the network on a volume basis (e.g., number of messages and/or packets transmitted by the network for synchronization), a timing basis (e.g., charging rates may be increased for high traffic radio access network nodes during peak service hours or the user equipment maybe charged after synchronization services are rendered for a predefined time period such as 15 minute intervals), an event basis (e.g., upon detection by the network of a particular event occurring such as the user equipment initiating a connection with the network or utilizing a particular network function or data network), the like, or combinations thereof. It will be appreciated that the information collected/monitored and transmitted by the network, or components thereof, would incorporate one or more of the time synchronization volume, timing, or event information. An example embodiment that provides event based charging may further incorporate trigger conditions as part of the charging profile and/or the like. For example, a trigger condition may indicate to the network, or a component thereof (e.g., access and mobility management function, charging function, etc.), that an event has occurred and therefore a charge should be applied to the user account associated with the event.

[0006] According to some embodiments, the architecture to support Time Sensitive Communication (TSC) relies on a network system (e.g., the 5G System (5GS)) being integrated into an associated external network as a Time Sensitive Networking (TSN) bridge. Integration of the network system with the external network provides for the TSN functionality perform time synchronization services. Additionally, in order to support the TSN time synchronization services, the entire End-To-End (E2E) architecture of the 5GS can be configured as an Institute of Electrical and Electronics Engineers (IEEE) timing and synchronization system or time-aware system. In some embodiments, only the TSN Translators (TTs) at the edges of the 5GS support the IEEE time-aware system operations. In some embodiments, the User Equipment (UE), Radio Access Network (RAN) (e.g., gNB, etc.), User Plane Function (UPF), Network-side TT (NW- TT), and Device-side TT (DS-TT) are synchronized with the 5G internal system clock (5G GM) in order to keep these network elements synchronized. Additionally, the TSN Time Synchronization may have two synchronization processes the 5GS synchronization and the TSN domain synchronization. In some embodiments, the 5GS synchronization and/or the TSN domain synchronization process may be considered independent from the other and, accordingly, the RAN (e.g., gNB, etc.) only needs to be synchronized to the 5G internal system clock.

[0007] An example embodiment provides that the 5G internal system clock distribution may be available to one or more user plane nodes in the 5G system. For example, the internal system clock distribution may be available to the UPF and/or the NW-TT by way of a Precision Time Protocol (PTP) and/or a generic Precision Time Protocol (gPTP) compatible transport network. In accordance with another example, the internal system clock distribution may be available to the UE via message signaling of time synchronization information related to absolute timing of radio frames in a Time Division Duplex (TDD) mode wherein uplink signals are separated from downlink signals by way of an allocation of different time slots in the same frequency bands. Further, the UE may then make 5G internal system clock available to the DS-TT. In accordance with the foregoing 5G internal system clock distribution examples, the time synchronization information may be transmitted and monitored by the network according to at least two example configuration embodiments. In some embodiments, the time synchronization information is monitored and collected by at least the UPF utilizing gPTP or PTP messages transferred via the user plane (U-plane) synchronization. In some embodiments, the time synchronization information is monitored and collected by at least the RAN (e.g., gNB) utilizing System Information Block (SIB) (e.g., SIB9, etc.) and/or Radio Resource Control (RRC) messages transferred via the control plane (C-plane) synchronization. It will be appreciated that the selection of U-plane and/or C-plane synchronization methods may be dependent on one or more of a type of user equipment, RAN node configurations (e.g., gNB, NodeB, etc.), a Service Level Agreement (SLA), the like, or combinations thereof.

[0008] In some embodiments, the U-plane and/or C-plane synchronization methods may provide time synchronization services, and charging services associated therewith, along with and/or as a backup to one or more Global Positioning Systems (GPSs) or similar alternative time synchronization solutions. Moreover, the U-plane and/or C-plane synchronization methods as disclosed herein may be implemented as the primary means for time synchronization services and charging services thereof. In some embodiments, as set forth by the present disclosure the network, for example, a 5G network may be configured for uplink time synchronization and, as such, the 5GS may provide support for time synchronization with the TSN and the 5G internal system clock in the TSN network attached to the user equipment. According to such embodiments, the TSN and the 5G internal system clock are configured so that they are located in the network (e.g., a server associated with the network) communi cably connected to the user equipment.

[0009] Moreover, in some embodiments, a 5GS and associated network may be configured to support exposure for time synchronization services offered by a 5GS configured with two or more clock/time sources. For example, in some such embodiments, a 5GS may be configured with a first clock/time source from a gPTP client and protocol that convey a first timing information (e.g., located in the Data Network (DN)) and further configured with a second clock/time source from a mapping protocol between the 5GS and the 5GC that convey a second timing information. In another example embodiment, a 5GS may be configured with a first time source provided via a 5G internal system clock and a second clock/time source provided by an Application Function (AF) (e.g., a GPS time source). In accordance with the preceding example the UPF and/or NW-TT create the gPTP and/or PTP message(s) for conveying the time synchronization information.

[0010] It will be appreciated that the synchronization service and thus the time synchronization information monitoring provided via the network may be configured to work in accordance with a UE’s level of network authorization (e.g., network functions with which a UE is registered to communicate). For example, in a 5GS configured as a TSN bridge the activation, authentication, and/or authorization for synchronization services are automatic (e.g., the synchronization services are hard-coded into the network) when the UE has been configured for a TSC signal flow.

[0011] The present disclosure provides for a network (e.g., 5G, etc.) that may be configured to provide authorization via a Core Network (CN), based on UE signal context, to provide a flexible synchronization service aligned with the synchronization exposure capabilities and enable service charging methods. In some embodiments, a synchronization level scalar, or the like, may be configured within the signals transmitted to a UE in order to provide a reference to a combination of parameters associated with the synchronization service, and configurations thereof, that will define the synchronization profile for the UE.

[0012] It will be appreciated that in traditional systems outside of the restricted dedicated factory network configurations, a CN is generally unable to configure the RAN in order for synchronization services to be activated for a respective UE from a plurality of UEs in communication with the RAN. Moreover, in traditional systems time synchronization as a service concept provides AFs and/or UEs with the ability to request from, for example, a 5GS specific time synchronization configurations for respective UEs, thus putting a demand on the network’s resources. In accordance with an example embodiment, however, the 5GS is configured to monetize time synchronization requirements based on level of needed engagement of the network’s resources. Additionally, the current charging framework and procedures do not generally support methods to control resource allocation and/or engagement required to provide time synchronization services via the network (e.g., charging signaling messages used for time synchronization). In an example embodiment, however, charging for 5G data connectivity, SMS, 5G connection and mobility, Network Exposure Function Northbound Application Program Interfaces, and time synchronization services is provided. In addition, an example embodiment provides support for control of network resource allocation and/or engagement with UEs. [0013] In some embodiments, a 5GS, or the like, can be configured to charge fixed and/or variable monetization rates, charging profiles, and/or charging models based on a UE’s interactions with the network. For example, rates and/or charges may be configured to reflect one or more of a roaming status, a RAN location, a UE location, a specific service, a time of day, a time period, an amount of time, a level of access used to carry a Service Data Flow (SDF), an Application Start and/or Stop event, the like or combinations thereof and accordingly the 5GS, or the like, is configured to monitor such conditions via signaling messages. In some embodiments, the network, or a portion thereof, (e.g., Access and Mobility Management Function (AMF), Session Management Function (SMF), etc.) may be configured to detect trigger events and/or trigger conditions in order to cause a charge to an account associated with a UE. In some embodiments, the AMF and/or SMF are configured to support, directly and/or with support from other network functions and/or network infrastructure, charging signal collection and reporting of charges accumulated by one or more UEs in accordance with a charging model, or the like. Furthermore, the AMF and/or SMF may report to a Charging Function (CHF) charging information based on network resource usage (e.g., processor and/or memory allocation, the like, or combinations thereof) resulting from signaling with a respective UE. In some embodiments, a UPF may be configured to monitor, collect, and report network resource usage data associated with the U-plane to an SMF.

[0014] In some embodiments, a RAN, a component thereof (e.g., gNB, etc.), the like (e.g., NG-RAN, E-UTRAN, etc.), or combinations thereof may report monitor, collect, and report network resource usage data associated with the C-plane and/or U-plane to the AMF and/or SMF. In some embodiments, a RAN, a component thereof (e.g., gNB, etc.), the like (e.g., NG- RAN, E-UTRAN, etc.), or combinations thereof may monitor, collect, and report network resource usage data associated with a secondary Radio Access Technology (RAT) to the AMF and/or SMF. In accordance with such embodiments, the AMF and/or SMF cause transmission of the network resource usage data (e.g., interactions between the UE and network functions) to a charging system (e.g., a CHF) associated with the network. In some embodiments, a Policy and Charging Control (PCC) rule supports one or more charging models for charging reported by an AMF and/or SMF to the CHF. In some embodiments, the one or more charging models comprises one or more of volume based charging, time based charging, volume and time based charging, event based charging, and no charging. In some embodiments, the one or more charging models may be associated with a respective service data flow.

[0015] In some embodiments, the AMF cause transmission of network resource usage data to a charging system (e.g., a CHF) based on one or more detected events comprising one or more of a registration management event, a connection management event, or a location reporting event. The registration management event comprises one or more of a registration checked, a registration completed, or a deregistration. The connection management event comprises one or more of a start of an N2 interface connection or an end of an N2 interface connection. The location reporting event comprises one or more of a UE location change or a change of UE presence in one or more presence reporting areas. In some embodiments, a registration management event, a connection management event, and/or a location reporting event may be initiated in response to a signal received by a UE, a RAN, a network function, the like, or combinations thereof.

[0016] In an example embodiment of the present disclosure, a 5GS can provide means for one or more gNBs to monitor, collect, and/or report time synchronization information to an AMF, SMF, and/or CHF for charging an account associated with a UE based on time synchronization messages transmitted to the UE via one or more of a System Information Block (SIB) message (e.g., SIB9, etc.), a Radio Resource Control (RRC) message, a Precision Time Protocol (PTP) message, or a generic Precision Time Protocol (gPTP) message. In some embodiments, the AMF and/or SMF receive a time synchronization service report from the gNB and compile the time synchronization service report from the gNB with one or more other time synchronization service reports before causing transmission of the compiled time synchronization service report to the CHF for charging of an account. In some embodiments, a time synchronization service report may comprise time synchronization messages associated with a plurality of UEs wherein each UE is associated with one or more accounts to be charged by the CHF.

[0017] In another example embodiment of the present disclosure, a 5GS can provide means for one or more UPFs to monitor, collect, and/or report time synchronization information to an SMF and/or CHF for charging an account associated with a UE based on time synchronization messages transmitted to the UE via one or more of a PTP message or a gPTP message. In some embodiments, the UPF may report a respective PTP and/or gPTP message based on a granularity associated with the message. In some embodiments, a 5GS can provide means for one or more CHFs to charge an account based on a plurality of charging models. The plurality of charging models comprise one or more of a one-time charge, a continuous set of charges per each synchronization service rendered to a UE, a charge based on synchronization accuracy (e.g., a charge may not be applied to an account if the synchronization is below a predefined accuracy threshold, a charge may be increased if it is above a predefined accuracy threshold, a charge may be decreased if it is below a predefined accuracy threshold, etc.) or a charge based on a number of time synchronization messages (e.g., gPTP, RRC, PTP, SIB, SIB9, etc.) transmitted to the UE. In some embodiments, a charging model, or the like (e.g., a charging profile) may be configured to apply a charge to an account in accordance with a message number threshold. For example, a minimum number of time synchronization messages may be required to be transmitted to a UE before the UE’s account is charged by the CHF. Additionally, multiple message number thresholds may be implemented by a CHF via a charging model such that the charge amount to the UE’s account increases at predetermined thresholds (e.g., a charge is increased after 5 messages, then increased again after 15 messages, etc.).

[0018] In accordance with some embodiments, a CHF, based on a charging model, or the like (e.g., a charging profile, etc.), may be configured to apply a charge to an account in accordance with the type of clock source used to render time synchronization services to a UE. For example, a CHF may charge an account associated with a UE according to a first rate for each time synchronization message transmitted to the UE wherein time synchronization information is provided via a first clock/time source such as a 5G internal system clock. Additionally, the CHF may charge the account associated with the UE according to a second rate for each time synchronization message transmitted to the UE wherein time synchronization information is provided via a second clock/time source such as an Application Function (AF) (e.g., a GPS time source). In some embodiments, a network via at least a network function (e.g., AMF, SMF, UPF, CHF, etc.) may switch a time synchronization source used for time synchronization services between a first clock/time source and one or more second clock/time sources. In such embodiments, the time synchronization source may be switched from a first clock/time source to one or more second clock/time sources in order to provide predefined time synchronization services (e.g., to transmit time synchronization information with a minimum granularity and/or accuracy level). Additionally, or alternatively, the time synchronization source may be switched from a first clock/time source to one or more second clock/time sources in order to minimize charging costs incurred by a UE’s account to conform to the term of a service level agreement.

[0019] An example embodiment of the present disclosure provides for the selection of rates and/or charging models based on a vertical application’s level of engagement with the 5GS. For example, a time synchronization service may be configured on the 5GS as part of the CN. In an instance that the CN (e.g., AMF, SMF, etc.) selects only C-plane time synchronization information delivery for charging of time synchronization services then the charging model may have alternative means for implementing time synchronization services for the vertical application. For example, in an instance the vertical application requests a particular level of time synchronization service accuracy (e.g., ps accuracy) then the rate may be approximated based on a determination by the network according to network resource usage required to achieve the particular level of time synchronization service accuracy. In some embodiments, the approximated rate may be based on the requesting UE’s connectivity (e.g., mobility, cell size, etc.). For another example, in an instance the vertical application requests a particular level of time synchronization service accuracy (e.g., ps accuracy) and time synchronization information messaging type (e.g., RRC, SIB9, etc.) then the rate may be negotiated between the UE, the AF, and the CN (e.g., AMF, SMF, etc.). In some embodiments, the rate may be approximated based on a number of time synchronization information messages.

[0020] In some embodiments, a gNB may be configured with one or more additional interfaces to the CN. For example, the gNB may be configured with one or more of another N2 interface, Ni l interface, the like, or combinations thereof in order to receive and/transmit time synchronization information to the CN and/or UE. In some embodiments, a RAN (e.g., one or more gNBs, etc.) may be configured with one or more onboard network functions to monitor, collect, and report network resource usage data to the CN. For example, the RAN may be configured with one or more Policy and Charging Control (PCC) rules (e.g., volume, time, or event based charging rules, etc.) in order to monitor, collect, and report network resource usage data associated with transmitted time synchronization messages or other types of signaling messages. In some embodiments, the RAN may be configured to communicate with one or more network functions in the CN, U-plane, and/or C-plane in order to monitor, collect, and report network resource usage data to the CN. In some embodiments, the network resource usage data is determine based on the transmitted time synchronization messages or other types of signaling messages.

[0021] In some embodiments, a UPF, configured to monitor, collect, and report U-plane time synchronization information, may utilize network communication channels to an SMF and/or a PCC configured for charging services other than time synchronization information. For example, the UPF may utilize network communication channels to the SMF, that are configured for charging internet data usage, in order to also charge for time synchronization services. In some embodiments, the UPF may utilize such communication channels to transmit network resource usage data, for example a number of transmitted gPTP and/or PTP messages transmitted with particular granularities. For additional example, the UPF may utilize such communication channels to transmit network resource usage data for a given application (e.g., IEEE TSN, an AF, etc.), targeted UE and/or DS-TT, a Data Network Name (DNN) and Network Slice Selection Assistance Information (NS SAI) combination, the like, or combinations thereof.

[0022] In some embodiments, the time synchronization service, time synchronization messaging, charging model, UE charging profile, the like, or combinations thereof may be authorized for a UE based on one or more of a factory default UE hardware and/or software configuration, a default configuration received via an established Time Sensitive Communication (TSC) flow, a software and/or firmware update provided via a network, the like, or combinations thereof. In some embodiments, a 5G network may comprise Next Generation Application Protocols (NGAP) and a service based architecture in which a set of network functions may offer different functionalities. The NGAP may be used, for example, in the N2 interface, between the gNB and the AMF, in order to configure the gNB, or the like, to monitor, collect, and report to the AMF time synchronization information transmitted to a UE. In some embodiments, the time synchronization information monitored and/or collected, by the gNB, for a respective UE is at least transmitted in part over a RAN associated with the gNB. In some embodiments, the NGAP may be configured to provide means for communications between the AMF and SMF to support the transmission and receipt of time synchronization information. Moreover, the Service Based Architecture (SBA) may be configured as part of other network interfaces (e.g., N4, Nsmf, Namf, the like, or combinations thereof) to allow for the transmission and receipt of time synchronization information between the AMF and/or SMF and other network entities. In some embodiments, the NGAP enable the AMF and/or SMF of the CN to transmit charging models, charging profiles, rate information, the like, or combinations thereof to the gNB. Moreover, the NGAP and the SBA may be configured to enable communication between the AMF and SMF in order to coordinate C-plane and U-plane resource usage monitoring, collecting, and/or reporting from the gNB and one or more network (e.g., UPF). In some embodiments, the NGAP or the network function service framework may distribute trigger conditions, for reporting resource usage, to the AMF and/or SMF. For example, the network function service framework may distribute minimum thresholds for charging based on a number of messages, a quality of service (e.g., time synchronization accuracy, message granularity, etc.), the like, or combinations thereof. Moreover, the NGAP may define the trigger conditions for use by the gNB, UPF, the like, or combinations thereof. In some embodiments, the SMF may provide charging requirements and time synchronization information to the CHF for stand-alone time synchronization services without resource usage reporting from the AMF. In some embodiments, the SMF and a Policy Charging Function (PCF) of a 5G network may define additional extensions to the previous version of the PCC charging model in order to include time synchronization services associated with a Protocol Data Unit (PDU) session. Moreover, the N4 Session signaling may define UPF Usage Reporting Rule (URR) extensions to enable gPTP and/or PTP message identification based on particular charging model and/or charging profile criteria. In some embodiments, the PCF defines the charging model and/or charging profile criteria.

[0023] According to one aspect of the present disclosure, there is provided a method that comprises receiving, from a network, charging profile information comprising one or more of a charging rate, a charging model, or a synchronization delivery method. The method may further comprise causing transmission, to a user equipment, of at least a time synchronization information message. The method may further comprise generating, based on the charging profile information and the time synchronization information message, a control plane synchronization service report for the user equipment. The method may further comprise causing transmission, to the network, of the control plane synchronization service report.

[0024] In some embodiments of the method, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message. In some embodiments of the method, the control plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least the time synchronization information message. In some embodiments of the method, the charging model is configured for one or more of one-time charging, continuous charging per synchronization service, charging based on synchronization accuracy, or charging based on a number of messages associated with the time synchronization information message. In some embodiments of the method, the network comprises one or more of an access and mobility management function, a session management function, a charging function, a user plane function, or a data network.

[0025] According to another aspect of the present disclosure, there is provided an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to receive, from a network, charging profile information comprising one or more of a charging rate, a charging model, or a synchronization delivery method. The apparatus may be further caused to at least cause transmission, to a user equipment, of at least a time synchronization information message. The apparatus may be further caused to at least generate, based on the charging profile information and the time synchronization information message, a control plane synchronization service report for the user equipment. The apparatus may be further caused to at least cause transmission, to the network, of the control plane synchronization service report.

[0026] In some embodiments of the apparatus, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message. In some embodiments of the apparatus, the control plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least the time synchronization information message. In some embodiments of the apparatus, the charging model is configured for one or more of one-time charging, continuous charging per synchronization service, charging based on synchronization accuracy, or charging based on a number of messages associated with the time synchronization information message. In some embodiments of the apparatus, the network comprises one or more of an access and mobility management function, a session management function, a charging function, a user plane function, or a data network.

[0027] According to another aspect of the present disclosure, there is provided a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution, to receive, from a network, charging profile information comprising one or more of a charging rate, a charging model, or a synchronization delivery method. The computer program product may be further configured, upon execution, to at least cause transmission, to a user equipment, of at least a time synchronization information message. The computer program product may be further configured, upon execution, to at least generate, based on the charging profile information and the time synchronization information message, a control plane synchronization service report for the user equipment. The computer program product may be further configured, upon execution, to at least cause transmission, to the network, of the control plane synchronization service report.

[0028] In some embodiments of the computer program product, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message. In some embodiments of the computer program product, the control plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least the time synchronization information message. In some embodiments of the computer program product, the charging model is configured for one or more of one-time charging, continuous charging per synchronization service, charging based on synchronization accuracy, or charging based on a number of messages associated with the time synchronization information message. In some embodiments of the computer program product, the network comprises one or more of an access and mobility management function, a session management function, a charging function, a user plane function, or a data network.

[0029] According to another aspect of the present disclosure, there is provided an apparatus that comprises means for receiving, from a network, charging profile information comprising one or more of a charging rate, a charging model, or a synchronization delivery method. The apparatus may further comprise means for causing transmission, to a user equipment, of at least a time synchronization information message. The apparatus may further comprise means for generating, based on the charging profile information and the time synchronization information message, a control plane synchronization service report for the user equipment. The apparatus may further comprise means for causing transmission, to the network, of the control plane synchronization service report.

[0030] In some embodiments of the apparatus, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message. In some embodiments of the apparatus, the control plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least the time synchronization information message. In some embodiments of the apparatus, the charging model is configured for one or more of one-time charging, continuous charging per synchronization service, charging based on synchronization accuracy, or charging based on a number of messages associated with the time synchronization information message. In some embodiments of the apparatus, the network comprises one or more of an access and mobility management function, a session management function, a charging function, a user plane function, or a data network.

[0031] According to one aspect of the present disclosure, there is provided a method that comprises receiving, from a radio access network, a control plane synchronization service report associated with at least a user equipment. The method may further comprise receiving, from a user plane function, a user plane synchronization service report associated with at least the user equipment. The method may further comprise generating, based on the control plane synchronization service report or the user plane synchronization service report, synchronization usage monitoring data. The method may further comprise causing transmission, to a charging function, of the synchronization usage monitoring data.

[0032] In some embodiments of the method, the synchronization usage monitoring data is generated based on a synchronization service comprising one or more of a synchronization service coupled or independent to a protocol data unit monitoring. In some embodiments of the method, the user equipment has established a protocol data unit session with a configured time synchronization service or the user equipment has not established the protocol data unit session. In some embodiments of the method, the control plane synchronization service report and the user plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least a time synchronization information message. In some embodiments of the method, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message.

[0033] According to another aspect of the present disclosure, there is provided an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to receive, from a radio access network, a control plane synchronization service report associated with at least a user equipment. The apparatus may be further caused at least to receive, from a user plane function, a user plane synchronization service report associated with at least the user equipment. The apparatus may be further caused at least to generate, based on the control plane synchronization service report or the user plane synchronization service report, synchronization usage monitoring data. The apparatus may be further caused at least to cause transmission, to a charging function, of the synchronization usage monitoring data.

[0034] In some embodiments of the apparatus, the synchronization usage monitoring data is generated based on a synchronization service comprising one or more of a synchronization service coupled or independent to a protocol data unit monitoring. In some embodiments of the apparatus, the user equipment has established a protocol data unit session with a configured time synchronization service or the user equipment has not established the protocol data unit session. In some embodiments of the apparatus, the control plane synchronization service report and the user plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least a time synchronization information message. In some embodiments of the apparatus, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message.

[0035] According to another aspect of the present disclosure, there is provided a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution, to receive, from a radio access network, a control plane synchronization service report associated with at least a user equipment. The computer program product may be further configured, upon execution, to at least receive, from a user plane function, a user plane synchronization service report associated with at least the user equipment. The computer program product may be further configured, upon execution, to at least generate, based on the control plane synchronization service report or the user plane synchronization service report, synchronization usage monitoring data. The computer program product may be further configured, upon execution, to at least cause transmission, to a charging function, of the synchronization usage monitoring data.

[0036] In some embodiments of the computer program product, the synchronization usage monitoring data is generated based on a synchronization service comprising one or more of a synchronization service coupled or independent to a protocol data unit monitoring. In some embodiments of the computer program product, the user equipment has established a protocol data unit session with a configured time synchronization service or the user equipment has not established the protocol data unit session. In some embodiments of the computer program product, the control plane synchronization service report and the user plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least a time synchronization information message. In some embodiments of the computer program product, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message.

[0037] According to another aspect of the present disclosure, there is provided an apparatus that comprises means for receiving, from a radio access network, a control plane synchronization service report associated with at least a user equipment. The apparatus may further comprise means for receiving, from a user plane function, a user plane synchronization service report associated with at least the user equipment. The apparatus may further comprise means for generating, based on the control plane synchronization service report or the user plane synchronization service report, synchronization usage monitoring data. The apparatus may further comprise means for causing transmission, to a charging function, of the synchronization usage monitoring data.

[0038] In some embodiments of the apparatus, the synchronization usage monitoring data is generated based on a synchronization service comprising one or more of a synchronization service coupled or independent to a protocol data unit monitoring. In some embodiments of the apparatus, the user equipment has established a protocol data unit session with a configured time synchronization service or the user equipment has not established the protocol data unit session. In some embodiments of the apparatus, the control plane synchronization service report and the user plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least a time synchronization information message. In some embodiments of the apparatus, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message.

[0039] According to one aspect of the present disclosure, there is provided a method that comprises receiving, from a network entity, one or more of a charging profile associated with at least a user equipment. The method may further comprise causing transmission, based on the charging profile, of a configuration signal to a radio access network, wherein the configuration signal at least defines parameters for generating a control plane synchronization service report associated with at least the user equipment. The method may further comprise receiving, from the radio access network, the control plane synchronization service report associated with at least the user equipment. The method may further comprise generating, based on the control plane synchronization service report, synchronization usage monitoring data. The method may further comprise causing transmission, to a charging function, of the synchronization usage monitoring data. In some embodiments, the parameters for generating the control plane synchronization service report may comprise one or more of a rate, a charging model, or a time synchronization message type (e g., SIB, RRC, PTP, etc ).

[0040] In some embodiments of the method, the synchronization usage monitoring data is generated based on a synchronization service comprising one or more of a synchronization service coupled or independent to a protocol data unit monitoring. In some embodiments of the method, the user equipment does not have a protocol data unit session established. In some embodiments of the method, the control plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least a time synchronization information message. In some embodiments of the method, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message. [0041] According to another aspect of the present disclosure, there is provided an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to receive, from a network entity, one or more of a charging profile associated with at least a user equipment. The apparatus may be further caused at least to cause transmission, based on the charging profile, of a configuration signal to a radio access network, wherein the configuration signal at least defines parameters for generating a control plane synchronization service report associated with at least the user equipment. The apparatus may be further caused at least to receive, from the radio access network, the control plane synchronization service report associated with at least the user equipment. The apparatus may be further caused at least to generate, based on the control plane synchronization service report, synchronization usage monitoring data. The apparatus may be further caused at least to cause transmission, to a charging function, of the synchronization usage monitoring data. In some embodiments, the parameters for generating the control plane synchronization service report may comprise one or more of a rate, a charging model, or a time synchronization message type (e.g., SIB, RRC, PTP, etc ).

[0042] In some embodiments of the apparatus, the synchronization usage monitoring data is generated based on a synchronization service comprising one or more of a synchronization service coupled or independent to a protocol data unit monitoring. In some embodiments of the apparatus, the user equipment does not have a protocol data unit session established. In some embodiments of the apparatus, the control plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least a time synchronization information message. In some embodiments of the apparatus, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message.

[0043] According to another aspect of the present disclosure, there is provided a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution, to receive, from a network entity, one or more of a charging profile associated with at least a user equipment. The computer program product may be further configured, upon execution, to at least cause transmission, based on the charging profile, of a configuration signal to a radio access network, wherein the configuration signal at least defines parameters for generating a control plane synchronization service report associated with at least the user equipment. The computer program product may be further configured, upon execution, to at least receive, from the radio access network, the control plane synchronization service report associated with at least the user equipment. The computer program product may be further configured, upon execution, to at least generate, based on the control plane synchronization service report, synchronization usage monitoring data. The computer program product may be further configured, upon execution, to at least cause transmission, to a charging function, of the synchronization usage monitoring data. In some embodiments, the parameters for generating the control plane synchronization service report may comprise one or more of a rate, a charging model, or a time synchronization message type (e.g., SIB, RRC, PTP, etc.).

[0044] In some embodiments of the computer program product, the synchronization usage monitoring data is generated based on a synchronization service comprising one or more of a synchronization service coupled or independent to a protocol data unit monitoring. In some embodiments of the computer program product, the user equipment does not have a protocol data unit session established. In some embodiments of the computer program product, the control plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least a time synchronization information message. In some embodiments of the computer program product, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message.

[0045] According to another aspect of the present disclosure, there is provided an apparatus that comprises means for receiving, from a network entity, one or more of a charging profile associated with at least a user equipment. The apparatus may further comprise means for causing transmission, based on the charging profile, of a configuration signal to a radio access network, wherein the configuration signal at least defines parameters for generating a control plane synchronization service report associated with at least the user equipment. The apparatus may further comprise means for receiving, from the radio access network, the control plane synchronization service report associated with at least the user equipment. The apparatus may further comprise means for generating, based on the control plane synchronization service report, synchronization usage monitoring data. The apparatus may further comprise means for causing transmission, to a charging function, of the synchronization usage monitoring data. In some embodiments, the parameters for generating the control plane synchronization service report may comprise one or more of a rate, a charging model, or a time synchronization message type (e.g., SIB, RRC, PTP, etc ).

[0046] In some embodiments of the apparatus, the synchronization usage monitoring data is generated based on a synchronization service comprising one or more of a synchronization service coupled or independent to a protocol data unit monitoring. In some embodiments of the apparatus, the user equipment does not have a protocol data unit session established. In some embodiments of the apparatus, the control plane synchronization service report comprises one or more of a volume, a granularity, a time, or an event associated with at least a time synchronization information message. In some embodiments of the apparatus, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message.

[0047] According to one aspect of the present disclosure, there is provided a method that comprises receiving, from at least a user equipment or a network, one or more interaction signals, wherein the one or more interaction signals comprises an identification of one or more of a time synchronization service delivery method, a time synchronization requirement, a network capability, or an operator policy. The method may further comprise at least determining, based on the one or more interaction signals, one or more of a charging profile for the user equipment. The method may further comprise at least dynamically updating a network function to include the charging profile for the user equipment.

[0048] In some embodiments of the method, the time synchronization service delivery method identifies a selection of a time synchronization information message. In some embodiments of the method, the time synchronization information message comprises one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message. In some embodiments of the method, the charging profile comprises at least a rate to be charged for at least a service provided by the network. In some embodiments of the method, the charging profile is a charging model comprising at least a rate that is increased or decreased relative to a threshold that is associated with a quality of service. In some embodiments of the method, the quality of service comprises one or more of a number of time synchronization messages, a time period that one or more synchronization messages were transmitted, a length of time for communications between the user equipment and the network, an accuracy of time synchronization services, or a granularity of time synchronization service. In some embodiments of the method, the network function comprises one or more of an access and mobility management function or a session management function. In some embodiments of the method, dynamically updating the network function comprises transmitting to the network function the charging profile, and wherein the updated network function is authorized based on the received charging profile to request, at a radio access network or a radio access network node, control plane charging control regarding time synchronization services.

[0049] According to another aspect of the present disclosure, there is provided an apparatus that comprises at least one processor and at least one memory with the at least one memory including computer program code, that is configured to, with the at least one processor, cause the apparatus at least to receive, from at least a user equipment or a network, one or more interaction signals, wherein the one or more interaction signals comprises an identification of one or more of a time synchronization service delivery method, a time synchronization requirement, a network capability, or an operator policy. The apparatus may be further caused at least to determine, based on the one or more interaction signals, one or more of a charging profile for the user equipment. The apparatus may be further caused at least to dynamically update a network function to include the charging profile for the user equipment.

[0050] In some embodiments of the apparatus, the time synchronization service delivery method identifies a selection of a time synchronization information message. In some embodiments of the apparatus, the time synchronization information message comprises one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message. In some embodiments of the apparatus, the charging profile comprises at least a rate to be charged for at least a service provided by the network. In some embodiments of the apparatus, the charging profile is a charging model comprising at least a rate that is increased or decreased relative to a threshold that is associated with a quality of service. In some embodiments of the apparatus, the quality of service comprises one or more of a number of time synchronization messages, a time period that one or more synchronization messages were transmitted, a length of time for communications between the user equipment and the network, an accuracy of time synchronization services, or a granularity of time synchronization service. In some embodiments of the apparatus, the network function comprises one or more of an access and mobility management function or a session management function. In some embodiments of the apparatus, dynamically updating the network function comprises transmitting to the network function the charging profile, and wherein the updated network function is authorized based on the received charging profile to request, at a radio access network or a radio access network node, control plane charging control regarding time synchronization services.

[0051] According to another aspect of the present disclosure, there is provided a computer program product that comprises at least a non-transitory computer readable storage medium having program code portions stored thereon with the program code portions being configured, upon execution, to receive, from at least a user equipment or a network, one or more interaction signals, wherein the one or more interaction signals comprises an identification of one or more of a time synchronization service delivery method, a time synchronization requirement, a network capability, or an operator policy. The computer program product may be further configured, upon execution, to at least determine, based on the one or more interaction signals, one or more of a charging profile for the user equipment. The computer program product may be further configured, upon execution, to at least dynamically update a network function to include the charging profile for the user equipment.

[0052] In some embodiments of the computer program product, the time synchronization service delivery method identifies a selection of a time synchronization information message. In some embodiments of the computer program product, the time synchronization information message comprises one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message. In some embodiments of the computer program product, the charging profile comprises at least a rate to be charged for at least a service provided by the network. In some embodiments of the computer program product, the charging profile is a charging model comprising at least a rate that is increased or decreased relative to a threshold that is associated with a quality of service. In some embodiments of the computer program product, the quality of service comprises one or more of a number of time synchronization messages, a time period that one or more synchronization messages were transmitted, a length of time for communications between the user equipment and the network, an accuracy of time synchronization services, or a granularity of time synchronization service. In some embodiments of the computer program product, the network function comprises one or more of an access and mobility management function or a session management function. In some embodiments of the computer program product, dynamically updating the network function comprises transmitting to the network function the charging profile, and wherein the updated network function is authorized based on the received charging profile to request, at a radio access network or a radio access network node, control plane charging control regarding time synchronization services.

[0053] According to another aspect of the present disclosure, there is provided an apparatus that comprises means for receiving, from at least a user equipment or a network, one or more interaction signals, wherein the one or more interaction signals comprises an identification of one or more of a time synchronization service delivery method, a time synchronization requirement, a network capability, or an operator policy. The apparatus may further comprise means for determining, based on the one or more interaction signals, one or more of a charging profile for the user equipment. The apparatus may further comprise means for dynamically updating a network function to include the charging profile for the user equipment.

[0054] In some embodiments of the apparatus, the time synchronization service delivery method identifies a selection of a time synchronization information message. In some embodiments of the apparatus, the time synchronization information message comprises one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message. In some embodiments of the apparatus, the charging profile comprises at least a rate to be charged for at least a service provided by the network. In some embodiments of the apparatus, the charging profile is a charging model comprising at least a rate that is increased or decreased relative to a threshold that is associated with a quality of service. In some embodiments of the apparatus, the quality of service comprises one or more of a number of time synchronization messages, a time period that one or more synchronization messages were transmitted, a length of time for communications between the user equipment and the network, an accuracy of time synchronization services, or a granularity of time synchronization service. In some embodiments of the apparatus, the network function comprises one or more of an access and mobility management function or a session management function. In some embodiments of the apparatus, dynamically updating the network function comprises transmitting to the network function the charging profile, and wherein the updated network function is authorized based on the received charging profile to request, at a radio access network or a radio access network node, control plane charging control regarding time synchronization services.

[0055] Various other aspects are also described in the following detailed description and in the attached claims.

BRIEF DESCRIPTION OF THE DRAWINGS

[0056] Having thus described embodiments of the disclosure in general terms, reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

[0057] FIG. 1 illustrates an example architecture for a communications network, according to some embodiments;

[0058] FIG. 2 illustrates an example architecture for a communications network, according to some embodiments;

[0059] FIG. 3 illustrates an example architecture for a communications network, according to some embodiments;

[0060] FIG. 4 illustrates an example computing device for communicating over communication networks with other network entities, according to some embodiments;

[0061] FIG. 5 a flow diagram illustrating the signaling between communication devices via a network infrastructure, according to some embodiments;

[0062] FIG. 6 is a flow diagram illustrating communication transmissions, according to some embodiments, between communication devices via a network infrastructure;

[0063] FIG. 7 is a table that shows combinations of example network and user equipment configurations, according to some embodiments;

[0064] FIG. 8 is a flow chart illustrating the operations performed, such as by a communication device or other client device, in accordance with some example embodiments;

[0065] FIG. 9 is a flow chart illustrating the operations performed, such as by a communication device or other client device, in accordance with some example embodiments; [0066] FIG. 10 is a flow chart illustrating the operations performed, such as by a communication device or other client device, in accordance with some example embodiments; and

[0067] FIG. 11 is a flow chart illustrating the operations performed, such as by a communication device or other client device, in accordance with some example embodiments.

DETAILED DESCRIPTION

[0068] Some embodiments of the present invention will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments of the invention are shown. Indeed, various embodiments of the invention can be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. The term “or” is used herein in both the alternative and conjunctive sense, unless otherwise indicated. The terms “illustrative” and “exemplary” are used to be examples with no indication of quality level. Like reference numerals refer to like elements throughout. As used herein, the terms “data,” “content,” “information,” and similar terms can be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.

[0069] Additionally, as used herein, the term ‘circuitry’ refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present. This definition of ‘circuitry’ applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term ‘circuitry’ also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware. As another example, the term ‘circuitry’ as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device, and/or other computing device.

[0070] Additionally, as used herein, the terms “node,” “entity,” “intermediary,” “intermediate entity,” “go-between,” and similar terms can be used interchangeably to refer to computers connected via, or programs running on, a network or plurality of networks capable of data creation, modification, deletion, transmission, receipt, and/or storage in accordance with certain embodiments of the present disclosure. Thus, use of any such terms should not be taken to limit the spirit and scope of the present disclosure.

[0071] Additionally, as used herein, the terms “user equipment,” “user device,” “device,” “apparatus,” “mobile device,” “personal computer,” “laptop computer,” “laptop,” “desktop computer,” “desktop,” “mobile phone,” “tablet,” “smartphone,” “smart device,” “cellphone,” “computing device,” “communication device,” “user communication device,” “terminal,” and similar terms can be used interchangeably to refer to an apparatus, such as may be embodied by a computing device, configured to access a network or plurality of networks for at least the purpose of wired and/or wireless transmission of communication signals in accordance with certain embodiments of the present disclosure. Thus, use of any such terms should not be taken to limit the spirit and scope of certain embodiments of the present disclosure.

[0072] As defined herein, a “computer-readable storage medium,” which refers to a non- transitory physical storage medium (e.g., volatile or non-volatile memory device), can be differentiated from a “computer-readable transmission medium,” which refers to an electromagnetic signal. Such a medium can take many forms, including, but not limited to a non- transitory computer-readable storage medium (e.g., non-volatile media, volatile media), and transmission media. Transmission media include, for example, coaxial cables, copper wire, fiber optic cables, and carrier waves that travel through space without wires or cables, such as acoustic waves and electromagnetic waves, including radio, optical and infrared waves. Signals include man-made transient variations in amplitude, frequency, phase, polarization or other physical properties transmitted through the transmission media. Examples of non-transitory computer- readable media include a magnetic computer readable medium (e.g., a floppy disk, hard disk, magnetic tape, any other magnetic medium), an optical computer readable medium (e.g., a compact disc read only memory (CD-ROM), a digital versatile disc (DVD), a Blu-Ray disc (BD), the like, or combinations thereof), a random access memory (RAM), a programmable read only memory (PROM), an erasable programmable read only memory (EPROM), a FLASH- EPROM, or any other non-transitory medium from which a computer can read. The term computer-readable storage medium is used herein to refer to any computer-readable medium except transmission media. However, it will be appreciated that where embodiments are described to use a computer-readable storage medium, other types of computer-readable mediums can be substituted for or used in addition to the computer-readable storage medium in alternative embodiments.

[0073] In the following, certain embodiments are explained with reference to communication devices capable of communication via a wired and/or wireless network and communication systems serving such communication devices. Before explaining in detail these example embodiments, certain general principles of a wired and/or wireless communication system, access systems thereof, and communication devices are briefly explained with reference to FIGS. 1-3 to assist in understanding the technology underlying the described examples.

[0074] According to some embodiments, a communication device or terminal can be provided for wireless access via cells, base stations, access points, the like (e.g., wireless transmitter and/or receiver nodes providing access points for a radio access communication system and/or other forms of wired and/or wireless networks), or combinations thereof. Such wired and/or wireless networks include, but are not limited to, networks configured to conform to 2G, 3G, 4G, LTE, 5G, and/or any other similar or yet to be developed future communication network standards. The present disclosure contemplates that any methods, apparatuses, computer program codes, and any portions or combination thereof can also be implemented with yet undeveloped communication networks and associated standards as would be developed in the future and understood by one skilled in the art in light of the present disclosure.

[0075] Access points and hence communications there through are typically controlled by at least one appropriate control apparatus so as to enable operation thereof and management of mobile communication devices in communication therewith. In some embodiments, a control apparatus for a node can be integrated with, coupled to, and/or otherwise provided for controlling the access points. In some embodiments, the control apparatus can be arranged to allow communications between a user equipment and a core network or a network entity of the core network. For this purpose, the control apparatus can comprise at least one memory, at least one data processing unit such as a processor or the like, and an input/output interface (e.g., global positioning system receiver/transmitter, keyboard, mouse, touchpad, display, universal serial bus (USB), Bluetooth, ethernet, wired/wireless connections, the like, or combinations thereof). Via the interface, the control apparatus can be coupled to relevant other components of the access point. The control apparatus can be configured to execute an appropriate software code to provide the control functions. It shall be appreciated that similar components can be provided in a control apparatus provided elsewhere in the network system, for example in a core network entity. The control apparatus can be interconnected with other control entities. The control apparatus and functions can be distributed between several control units. In some embodiments, each base station can comprise a control apparatus. In alternative embodiments, two or more base stations can share a control apparatus.

[0076] Access points and associated controllers can communicate with each other via a fixed line connection and/or via a radio interface. The logical connection between the base station nodes can be provided for example by an X2, an SI, a similar interface, or combinations thereof. This interface can be used for example for coordination of operation of the stations and performing reselection or handover operations. The logical communication connection between the initial communication node and the final communication node of the network can comprise a plurality of intermediary nodes. Additionally, any of the nodes can be added to and removed from the logical communication connection as required to establish and maintain a network function communication.

[0077] The communication device or user equipment can comprise any suitable device capable of at least receiving a communication signal comprising data. The communication signal can be transmitted via a wired connection, a wireless connection, or combinations thereof. For example, the device can be a handheld data processing device equipped with radio receiver, data processing and user interface apparatus. Non-limiting examples include a mobile station (MS) such as a mobile phone or what is known as a ‘smart phone,’ a portable computer such as a laptop or a tablet computer provided with a wireless interface card or other wireless interface facility, personal data assistant (PDA) provided with wireless communication capabilities, or any combinations of these or the like. Further examples include wearable wireless devices such as those integrated with watches or smart watches, eyewear, helmets, hats, clothing, earpieces with wireless connectivity jewelry and so on, Universal Serial Bus (USB) sticks with wireless capabilities, modem data cards, machine type devices or any combinations of these or the like. [0078] In some embodiments, a communication device, e.g., configured for communication with the wireless network or a core network entity, can be exemplified by a handheld or otherwise mobile communication device or user equipment. A mobile communication device can be provided with wireless communication capabilities and appropriate electronic control apparatus for enabling operation thereof. Thus, the communication device can be provided with at least one data processing entity, for example a central processing unit and/or a core processor, at least one memory and other possible components such as additional processors and memories for use in software and hardware aided execution of tasks it is designed to perform. The data processing, storage, and other relevant control apparatus can be provided on an appropriate circuit board and/or in chipsets. Data processing and memory functions provided by the control apparatus of the communication device are configured to cause control and signaling operations in accordance with certain embodiments as described later in this description. A user can control the operation of the communication device by means of a suitable user interface such as touch sensitive display screen or pad and/or a keypad, one of more actuator buttons, voice commands, combinations of these, or the like. A speaker and a microphone are also typically provided. Furthermore, a mobile communication device can comprise appropriate connectors (either wired or wireless) to other devices and/or for connecting external accessories, for example hands-free equipment, thereto.

[0079] In some embodiments, a communication device can communicate wirelessly via one or more appropriate apparatuses for receiving and transmitting signals (e.g., global positioning system receiver/transmitter, remote touchpad interface with remote display, Wi-Fi interface, etc.). In some embodiments, a radio unit can be connected to the control apparatus of the device. The radio unit can comprise a radio part and associated antenna arrangement. The antenna arrangement can be arranged internally or externally to the communication device.

[0080] FIGS. 1-3 illustrate various example architectures for a communications network 100 in which the various methods, apparatuses, and computer program products can be carried out and/or used. In some embodiments, the communications network 100 can comprise any suitable configuration, number, orientation, positioning, and/or dimensions of components and specialized equipment configured to provide an air interface (e.g., New Radio (NR)) for communication or connection between a User Equipment 102 (UE 102) and a Data Network 116 (DN 116) via a Core Network 101 (CN 101) of the communications network 100. The UE 102 can be associated with one or more devices associated with one or more network function (NF) service consumers. As illustrated in FIG. 1, a communications network 100 can be provided in which the UE 102 is in operable communication with the Radio Access Network 104 (RAN 104), such as by way of a transmission tower, a base station, an access point, a network node, and/or the like. In some embodiments, the RAN 104 can communicate with the CN 101 or a component or entity thereof. In some embodiments, the CN 101 can facilitate communication between the UE 102 and the DN 116, such as for sending data, messages, requests, the like, or combinations thereof. In some embodiments, the DN 116 or the CN 101 can be in communication with an Application Server or Application Function 112 (AS/AF 112). The RAN 104, CN 101, DN 116, and/or AS/AF 112 can be associated with a Network Repository Function (NRF), NF service producer, Service Communication Proxy (SCP), Security Edge Protection Proxy (SEPP), Policy Charging Function (PCF), the like, or combinations thereof.

[0081] In the context of a 5G network, such as illustrated in FIGS. 2 and 3, the communications network 100 can comprise a series of connected network devices and specialized hardware that is distributed throughout a service region, state, province, city, or country, and one or more network entities, which can be stored at and/or hosted by one or more of the connected network devices or specialized hardware. In some embodiments, the UE 102 can connect to the RAN 104, which can then relay the communications between the UE 102 and the CN 101, the CN 101 being connected to the DN 116, which can be in communication with one or more AS/AF 112. In some embodiments, the UE 102 can be in communication with a RAN 104, which can act as a relay between the UE 102 and other components or services of the CN 101. For instance, in some embodiments, the UE 102 can communicate with the RAN 104, which can in turn communicate with an Access and Mobility Management Function 108 (AMF 108). In other instance or embodiments, the UE 102 can communicate directly with the AMF 108. In some embodiments, the AMF 108 can be in communication with one or more network functions (NFs), such as an Authentication Server Function 120 (AUSF 120), a Network Slice Selection Function 122 (NSSF 122), a Network Repository Function 124 (NRF 124), a Policy Charging Function 114 (PCF 114), a Network Data Analytics Function 126 (NWDAF 126), a Unified Data Management function 118 (UDM 118), the AS/AF 112, a Session Management Function 110 (SMF 110), a Charging Function 128 (CHF 128), the like, or combinations thereof. [0082] In some embodiments, CHF 128 may be configured for charging of services not covered by PCF 114, such as, charging for time synchronization services provide by the network to UE 102. In some embodiments, CHF 128 may at least partially comprise one or more of PCF 114, AMF 108, SMF 110, RAN 104, another network function, the like, or combinations thereof. In some embodiments, CHF 128 may be at least partially included as a portion of one or more of PCF 114, AMF 108, SMF 110, RAN 104, another network function, the like, or combinations thereof. In some embodiments, CHF 128 may be configured to dynamically updated one or more of PCF 114, AMF 108, SMF 110, RAN 104, another network function, the like, or combinations thereof with time synchronization charging information (e.g., a charging policy, an authorization to collect, monitor, and/or report time synchronization information over the network, etc.). In some embodiments, PCF 114 may incorporate at least partially any functionality described by the present disclosure with respect to CHF 128.

[0083] In some embodiments, the SMF 110 can be in communication with one or more User Plane Functions 106 (UPF 106, UPF 106a, UPF 106b, collectively “UPF 106”). By way of example only, in some embodiments, the UPF 106 can be in communication with the RAN 104 and the DN 116. In other embodiments, the DN 116 can be in communication with a first UPF 106a and the RAN 104 can be in communication with a second UPF 106b, while the SMF 110 is in communication with both the first and second UPFs 106a, b and the first and second UPFs 106a, b are in communication each with the other. In some embodiments, the SMF 110 can be in communication with CHF 128 to provide for charging of services not covered by PCF 114, such as, charging for time synchronization services provide by the network to UE 102.

[0084] In some embodiments, the UE 102 can comprise a single-mode or a dual-mode device such that the UE 102 can be connected to one or more RANs 104. In some embodiments, the RAN 104 can be configured to implement one or more Radio Access Technologies (RATs), such as Bluetooth, Wi-Fi, and Global System for Mobile Communication (GSM), Universal Mobile Telecommunications System (UMTS), LTE or 5GNR, among others, that can be used to connect the UE 102 to the CN 101. In some embodiments, the RAN 104 can comprise or be implemented using a chip, such as a silicon chip, in the UE 102 that can be paired with or otherwise recognized by a similar chip in the CN 101, such that the RAN 104 can establish a connection or line of communication between the UE 102 and the CN 101 by identifying and pairing the chip within the UE 102 with the chip within the CN 101. In some embodiments, the RAN 104 can implement one or more base stations, towers or the like to communicate between the UE 102 and the AMF 108 of the CN 101. In some embodiments, RAN 104 can comprise one or more of a gNB, ng-eNB, NodeB, NG-RAN, radio tower, cell, en-gNB, eNB, E-UTRAN, communication interface, the like, or combinations thereof.

[0085] In some embodiments, the communications network 100 or components thereof (e.g., base stations, towers, etc.) can be configured to communicate with a communication device (e.g., the UE 102) such as a cell phone or the like over multiple different frequency bands, e.g., FR1 (below 6 GHz), FR2 (mm Wave), other suitable frequency bands, sub-bands thereof, and/or the like. In some embodiments, the communications network 100 can comprise or employ massive Multiple Input and Multiple Output (MIMO) antennas. In some embodiments, the communications network 100 can comprise Multi-User MIMO (MU-MIMO) antennas. In some embodiments, the communications network 100 can employ edge computing whereby the computing servers are communicatively, physically, computationally, and/or temporally closer to the communications device (e.g., UE 102) in order to reduce latency and data traffic congestion. In some embodiments, the communications network 100 can employ other technologies, devices, or techniques, such as small cell, low-powered RAN, beamforming of radio waves, Wi-Fi cellular convergence, Non-Orthogonal Multiple Access (NOMA), channel coding, the like, or combinations thereof.

[0086] As illustrated in FIG. 3, the UE 102 can be configured to communicate with the RAN 104 in a N1 interface, e.g., according to a Non-Access Stratum (NAS) protocol. In some embodiments, RAN 104 can be configured to communicate with the CN 101 or a component thereof (e.g., the AMF 108) in a N2 interface, e.g., in a control plane between a base station of the RAN 104 and the AMF 108. In some embodiments, the RAN 104 can be configured to communicate with the UPF 106 in a N3 interface, e.g., in a user plane. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with other services or network entities within the CN 101 in various different interfaces and/or according to various different protocols. For instance, in some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the AUSF 120 in a Nausf interface or an N12 interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the NSSF 122 in a Nnssf interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the NRF 124 in a Nnrf interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the PCF 114 in a Npcf interface or an N7 interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the NWDAF 126 in a Nnwdaf interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the UDM 118 in a Nudm interface, an N8 interface, or an N10 interface. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the AS/AF 112 in a Naf interface. In some embodiments, the SMF 110 can be configured to communicate with the UPF 106 in a N4 interface, which can act as a bridge between the control plane and the user plane, such as acting as a conduit for a Protocol Data Unit (PDU) session during which information is transmitted between, e.g., the UE 102 and the CN 101 or components/services thereof. In some embodiments, the AMF 108 and/or the SMF 110 can be configured to communicate with the CHF 128 in a Nchf interface.

[0087] It will be appreciated that certain example embodiments described herein arise in the context of a telecommunications network, including but not limited to a telecommunications network that conforms to and/or otherwise incorporates aspects of a fifth-generation (5G) architecture. While FIGS. 1-3 illustrate various configurations and/or components of an example architecture of the communications network 100, many other systems, system configurations, networks, network entities, and pathways/protocols for communication therein are contemplated and considered within the scope of this present disclosure.

[0088] While the methods, devices/apparatuses, and computer program products/codes described herein are described within the context of a fifth-generation core network (5GC) and system, such as illustrated in FIGS. 1-3 and described hereinabove, the described methods, devices, and computer program products can nevertheless be applied in a broader context within any suitable telecommunications system, network, standard, and/or protocol. It will be appreciated that the described methods, devices, and computer program products can further be applied to yet undeveloped future networks and systems as would be apparent to one skilled in the art in light of the present disclosure.

[0089] Turning now to FIG. 4, examples of an apparatus that may be embodied by the user equipment or by a network entity, such as server or other computing device are depicted in accordance with an example embodiment of the present disclosure. As described below in conjunction with the flowcharts and block diagrams presented herein, the apparatus 200 of an example embodiment can be configured to perform the functions described herein. In any instance, the apparatus 200 can more generally be embodied by a computing device, such as a server, a personal computer, a computer workstation or other type of computing device including those functioning as a user equipment and/or a component of a wireless network or a wireless local area network. Regardless of the manner in which the apparatus 200 is embodied, the apparatus of an example embodiment can be configured as shown in FIG. 4 so as to include, be associated with or otherwise be in communication with a processor 202 and a memory device 204 and, in some embodiments, and/or a communication interface 206.

[0090] Although not illustrated, the apparatus of an example embodiment may also optionally include a user interface, such as a touch screen, a display, a keypad, the like, or combinations thereof. Moreover, the apparatus according to example embodiments can be configured with a global positioning circuit that comprises a global positioning receiver and/or global positioning transmitter configured for communication with one or more global navigation satellite systems (e.g., GPS, GLONASS, Galileo, the like, or combinations thereof). The global positioning circuit may be configured for the transmission and/or receipt of direct/indirect satellite and/or cell signals in order to determine geolocation data (e.g., latitude, longitude, elevation, altitude, geographic coordinates, the like, or combinations thereof.) for the apparatus and/or another communication device associated with the apparatus or the one or more global navigation satellite systems. In some embodiments, the global positioning circuit may be configured to provide time synchronization services (e.g., transmit and/or receive time synchronization messages, etc.).

[0091] The processor 202 (and/or co-processors or any other circuitry assisting or otherwise associated with the processor) can be in communication with the memory device 204 via a bus for passing information among components of the apparatus 200. The memory device can include, for example, one or more volatile and/or non-volatile memories, such as a non-transitory memory device. In other words, for example, the memory device can be an electronic storage device (e.g., a computer readable storage medium) comprising gates configured to store data (e.g., bits) that can be retrievable by a machine (e.g., a computing device like the processor). The memory device can be configured to store information, data, content, applications, instructions, the like, or combinations thereof for enabling the apparatus to carry out various functions in accordance with an example embodiment. For example, the memory device could be configured to buffer input data for processing by the processor. Additionally or alternatively, the memory device could be configured to store instructions for execution by the processor.

[0092] The apparatus 200 can, in some embodiments, be embodied in various computing devices as described above. However, in some embodiments, the apparatus can be embodied as a chip or chip set. In other words, the apparatus can comprise one or more physical packages (e.g., chips) including materials, components and/or wires on a structural assembly (e.g., a baseboard). The structural assembly can provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus can therefore, in some cases, be configured to implement an example embodiment on a single chip or as a single “system on a chip.” As such, in some cases, a chip or chipset can constitute means for performing one or more operations for providing the functionalities described herein.

[0093] The processor 202 can be embodied in a number of different ways. For example, the processor can be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a Digital Signal Processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, for example, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Micro-Controller Unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processor can include one or more processing cores configured to perform independently. A multi-core processor can enable multiprocessing within a single physical package. Additionally or alternatively, the processor can include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining and/or multithreading.

[0094] In an example embodiment, the processor 202 can be configured to execute instructions stored in the memory device 204 or otherwise accessible to the processor. Alternatively or additionally, the processor can be configured to execute hard coded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processor can represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure while configured accordingly. Thus, for example, when the processor is embodied as an ASIC, FPGA, the like, or combinations thereof the processor can be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processor is embodied as an executor of instructions, the instructions can specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processor can be a processor of a specific device (e.g., an encoder and/or a decoder) configured to employ an example embodiment by further configuration of the processor by instructions for performing the algorithms and/or operations described herein. The processor can include, among other things, a clock, an Arithmetic Logic Unit (ALU) and logic gates configured to support operation of the processor.

[0095] In embodiments that include a communication interface 206, the communication interface can be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and/or transmit data from/to a network and/or any other device or module in communication with the apparatus 200, such as NF, NRF, a base station, an access point, SCP, UE 102, RAN 104, core network services, AS/AF 112, a database or other storage device, the like, or combinations thereof. In this regard, the communication interface can include, for example, one or more antennas and supporting hardware and/or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface can include the circuitry for interacting with the one or more antennas to cause transmission of signals via the one or more antennas or to handle receipt of signals received via the one or more antennas. In some embodiments, the one or more antennas may comprise one or more of a dipole antenna, monopole antenna, helix antenna, loop antenna, waveguide, horn antenna, parabolic reflectors, corner reflectors, dishes, micro strip patch array, convex-plane, concave-plane, convex-convex, concave-concave lenses, the like or combinations thereof. In some environments, the communication interface can alternatively or also support wired communication. As such, for example, the communication interface can include a communication modem and/or other hardware/software for supporting communication via cable, Digital Subscriber Line (DSL), USB, the like or combinations thereof. In some embodiments, a session management function (e.g., SMF 110) can comprise a 5GC session management function for any suitable Control and User Plane Separation (CUPS) architecture, such as for the General Packet Radio Service (GPRS), Gateway GPRS Support Node Control plane function (GGSN-C), Trusted Wireless Access Gateway Control plane function (TWAG-C), Broadband Network Gateway Control and User Plane Separation (BNG-CUPS), N4 interface, Sxa interface, Sxb interface, Sxc interface, Evolved Packet Core (EPC) Serving Gateway Control plane function (SGW-C), EPC Packet Data Network Gateway Control plane function (PGW-C), EPC Traffic Detection Control plane function (TDF-C), the like, or combinations thereof.

[0096] As illustrated, the apparatus 200 can include a processor 202 in communication with a memory 204 and configured to provide signals to and receive signals from a communication interface 206. In some embodiments, the communication interface 206 can include a transmitter and a receiver. In some embodiments, the processor 202 can be configured to control the functioning of the apparatus 200, at least in part. In some embodiments, the processor 202 can be configured to control the functioning of the transmitter and receiver by effecting control signaling via electrical leads to the transmitter and receiver. Likewise, the processor 202 can be configured to control other elements of apparatus 200 by effecting control signaling via electrical leads connecting the processor 202 to the other elements, such as a display or the memory 204. [0097] The apparatus 200 can be capable of operating with one or more air interface standards, communication protocols, modulation types, access types, and/or the like. Signals sent and received by the processor 202 can include signaling information in accordance with an air interface standard of an applicable cellular system, and/or any number of different wireline or wireless networking techniques, comprising but not limited to Wi-Fi, Wireless Local Access Network (WLAN) techniques, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, 802.16, 802.3, Asymmetric Digital Subscriber Line (ADSL), Data Over Cable Service Interface Specification (DOCSIS), the like, or combinations thereof. In addition, these signals can include speech data, user generated data, user requested data, the like, or combinations thereof.

[0098] For example, the apparatus 200 and/or a cellular modem therein can be capable of operating in accordance with various first generation (1G) communication protocols, second generation (2G or 2.5G) communication protocols, third-generation (3G) communication protocols, fourth-generation (4G) communication protocols, fifth-generation (5G) communication protocols, Internet Protocol Multimedia Subsystem (IMS) communication protocols (for example, Session Initiation Protocol (SIP)), the like, or combinations thereof. For example, the apparatus 200 can be capable of operating in accordance with 2G wireless communication protocols Interim Standard (IS) 136 (IS-136), Time Division Multiple Access (TDMA), GSM, IS-95, Code Division Multiple Access, Code Division Multiple Access (CDMA), the like, or combinations thereof. In addition, for example, the apparatus 200 can be capable of operating in accordance with 2.5G wireless communication protocols GPRS, Enhanced Data GSM Environment (EDGE), the like, or combinations thereof. Further, for example, the apparatus 200 can be capable of operating in accordance with 3G wireless communication protocols, such as UMTS, Code Division Multiple Access 2000 (CDMA2000), Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TD-SCDMA), the like, or combinations thereof. The NA 200 can be additionally capable of operating in accordance with 3.9G wireless communication protocols, such as Long Term Evolution (LTE), Evolved Universal Terrestrial Radio Access Network (E- UTRAN), the like, or combinations thereof. Additionally, for example, the apparatus 200 can be capable of operating in accordance with 4G wireless communication protocols, such as LTE Advanced, 5G, and/or the like as well as similar wireless communication protocols that can be subsequently developed. In some embodiments, the apparatus 200 can be capable of operating according to or within the framework of any suitable CUPS architecture, such as for the gateway GGSN-C, TWAG-C, Broadband Network Gateways (BNGs), N4 interface, Sxa interface, Sxb interface, Sxc interface, EPC SGW-C, EPC PGW-C, EPC TDF-C, the like, or combinations thereof. Indeed, although described herein in conjunction with operation with a 5G system, the apparatus and method may be configured to operate in conjunction with a number of other types of systems including systems hereinafter developed and implemented.

[0099] Some of the embodiments disclosed herein can be implemented in software, hardware, application logic, or a combination of software, hardware, and application logic. The software, application logic, and/or hardware can reside on memory 204, the processor 202, or electronic components, for example. In some example embodiments, the application logic, software or an instruction set is maintained on any one of various conventional computer- readable media. In the context of this document, a “computer-readable medium” can be any non- transitory media that can contain, store, communicate, propagate or transport the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer or data processor circuitry, with examples depicted at FIG. 4. The computer-readable medium can comprise a non-transitory computer-readable storage medium that can be any media that can contain or store the instructions for use by or in connection with an instruction execution system, apparatus, or device, such as a computer. [00100] FIG. 5 illustrates a flow chart that depicts an example signal sequence 500, for the provision of time synchronization services messaging, between communication devices (e.g., apparatus 200, one or more servers, etc.) by way of at least a network infrastructure (e.g., communications network 100, 600, etc.), and the collection, monitoring, and/or reporting of time synchronization information by one or more network entities. As shown, the example network infrastructure utilized for signal sequence 500 comprises at least UE 102, RAN 104, AMF 108, SMF 110, UPF 106, CHF 128, and DN 116. In some embodiments, the network infrastructure may be configured in accordance with 5G system standards, or the like (e.g., 4G, LTE, etc.), and RAN 104 can comprise one or more 5G radio nodes, such as one or more gNBs or equivalent. In some embodiments, the example signal sequence 500 may be implemented utilizing one or more network infrastructures associated with one or more networks comprising one or more network slices.

[00101] During signal sequence 500, UE 102 is in communication with the network via at least an established PDU session and the network is operating in accordance with pre-configured time synchronization service protocols. In accordance with the example signal sequence presented by FIG. 5, the network and/or UE 102 have selected a combined U-plane and C-plane delivery distribution for the time synchronization information, see block 502. As shown by block 504, the communications network, by way of at least RAN 104, transmits time synchronization information to UE 102. The time synchronization information may be transmitted to UE 102 via one or more time synchronization messages as shown in blocks 504, 506, and 512. As shown, time synchronization messages may comprise one or more of a System Information Block (SIB) message (e.g., SIB9, etc.), a Radio Resource Control (RRC) message, a Precision Time Protocol (PTP) message, or a generic Precision Time Protocol (gPTP) message, see blocks 504, 506, and 512 respectively. In an instance that gPTP and/or PTP messaging packets are transmitted to UE 102 the gPTP and/or PTP messaging packets may comprise time synchronization information provided by DN 116, see block 508, and transmitted via UPF 106 to RAN 104, see block 510, before being received by UE 102, see block 512.

[00102] In accordance with some embodiments, RAN 104 may provide means for monitoring, collecting, and/reporting time synchronization information transmitted thereby to UE 102. For example, RAN 104 may include an onboard network function which monitors the number and/or accuracy of time synchronization SIB9 messages transmitted to UE 102. RAN 104 may compile such time synchronization information into a C-plane time synchronization service report and cause transmission of the C-plane time synchronization service report to AMF 108, see block 514. Additionally, or alternatively, RAN 104 may directly, or by way of AMF 108, cause transmission of the C-plane time synchronization service report to SMF 110, see block 516. In some embodiments, UPF 106 may provide means for monitoring, collecting, and/reporting time synchronization information transmitted thereby to UE 102. For example, UPF 106 may include functionality that monitors the number and/or granularity of time synchronization PTP messages transmitted to UE 102. As illustrated by block 518, UPF 106 may compile such time synchronization information into a U-plane time synchronization service report and cause transmission of the U-plane time synchronization service report to SMF 110.

[00103] Moreover, upon receipt of one or more of a C-plane time synchronization service report and/or a U-plane time synchronization service report SMF 110 may provide means for processing the time synchronization service report information into chargeable monitoring data for transmission to CHF 128, see block 520. For example, SMF 110 may compare the number of time synchronization messages (e.g., SIB9, RRC, gPTP, PTP, etc.) transmitted to UE 102 against a minimum number threshold in order to signal to CHF 128 that an account associated with UE 102 should be charged at a particular rate. As shown by block 522, SMF 110 causes transmission of the chargeable monitoring data, compiled from the time synchronization service report(s), to CHF 128. In some embodiments, CHF 128 may be integrated at least partially into one or more other network functions (e.g., AMF 108, SMF 110, etc.).

[00104] As shown by FIG. 5, the time synchronization service charging framework and procedures may incorporate U-plane and/or C-plane resource usage reporting to SMF 110 or AMF 108. This is provided by the coordinated monitoring, collection, and reporting of time synchronization messaging carried out by RAN 104, for example by a gNB, and/or UPF 106. In accordance with example embodiments of C-plane resource usage reporting and charging services, a gNB may support C-plane resource usage reporting (e.g., SIB9, RRC messages, etc.) based on a NG_RAN charging profile received from the SMF 110 and/or AMF 108. Since both SMF 110 and AMF 108 may be configured to receive and/or cause transmission of charging information (e.g., time synchronization charging information, etc.) the gNB may be configured to report such information to either of the network functions. In an instance, only C-plane information is utilized for time synchronization charging the gNB may be configured to report to only SMF 110 or AMF 108. In an instance, both C-plane and U-plane information is utilized for time synchronization charging the gNB may be configured to report the C-plane information only to SMF 110 because the U-plane information reported by the UPF would also be reported to SMF 110. In some embodiments, the gNB may be configured to report time synchronization information according to Secondary RAT Usage Data Reporting Procedures, wherein the NG_RAN node sends an NGAP to AMF 108 that then may be processed by AMF 108 and/or transmitted onto SMF 110 to be processed. Further, either AMF 108 and/or SMF 110 may report the resource usage data onto CHF 128.

[00105] In some embodiments, UPF 106 may be configured with rules and/or trigger conditions to identify a chargeable criteria based on gPTP and/or PTP messages transmitted to UE 102. In some embodiments, new applicable trigger conditions may be configured with UPF 106 to include charging profiles for UEs utilizing the network time synchronization services via gPTP and/or PTP messaging, wherein the rules and/or trigger conditions may be added to UPF 106 by way of software and/or firmware updates. Moreover, the rules and/or trigger conditions applied to UPF 106 for detection of charges may comprise one or more of a measurement metric and/or threshold value associated with gPTP and/or PTP messages with URR definitions. For example, UPF 106 may be configured to identify a chargeable condition based on a number or granularity associated with one or more gPTP and/or PTP packets. In some embodiment, the UPF 106 may utilize one or more PCC rules to monitor for charges related to gPTP and/or PTP packets. In some embodiments, the PCC rules may be provided by PCF 114, via the network, to one or more other network functions, for example, UPF 106.

[00106] In some embodiments, a synchronization service may be configured as part of the PDU Session wherein the synchronization charging is associated with the PDU session charging which is carried out in accordance with the PCC charging rules, and/or a PCC charging model, in order to include indicators of C-plane resource usage monitoring in addition to the U-plane resource usage monitoring. In some embodiments, the time synchronization service and charging processes associated therewith may be configured as a stand-alone service. In other words, the time synchronization service and charging processes associated therewith may be configured only based on C-plane information delivery and not relying on any PDU session information for the provision of U-plane information delivery. In some embodiments, a stand-alone synchronization service may include synchronization charging independent of other charging service (e.g., mobile data usage, etc.). Such embodiments of a stand-alone time synchronization service and charging service will now be described in further detail with regards to FIG. 6. It will be appreciated that while FIG. 6 illustrates a stand-alone time synchronization service and charging service implemented using AMF 108 the same operations may be implemented by SMF 110.

[00107] FIG. 6 illustrates a flow diagram that depicts an example signal sequence 600, for the provision of time synchronization services messaging, between communication devices (e.g., apparatus 200, one or more servers, etc.) by way of at least a network infrastructure (e.g., communications network 100, 600, etc.), and the collection, monitoring, and/or reporting of time synchronization information by RAN 104. As shown, the example network infrastructure utilized for signal sequence 600 comprises at least UE 102, RAN 104, AMF 108, and CHF 128. In some embodiments, the network infrastructure may be configured in accordance with 5G system standards, or the like (e.g., 4G, LTE, etc.), and RAN 104 can comprise one or more 5G radio nodes, such as one or more gNBs or equivalent. In some embodiments, the example signal sequence 600 may be implemented utilizing one or more network infrastructures associated with one or more networks comprising one or more network slices.

[00108] In accordance with example signal sequence 600, UE 102 is registered with the network and the synchronization service is already configured. Additionally, UE 102 and/or the network has selected for time synchronization information to be reported by way of C-plane delivery, see block 602. As shown the communications network, by way of at least RAN 104, transmits time synchronization information to UE 102 via SIB9 and/or RRC messages, see blocks 604 and 606 respectively. In accordance with some embodiments, RAN 104 may provide means for monitoring, collecting, and/reporting time synchronization information transmitted thereby to UE 102. For example, RAN 104 may include an onboard network function which monitors the number and/or accuracy of time synchronization SIB9 and/or RRC messages transmitted to UE 102. Moreover, RAN 104 may compile such time synchronization information into a C-plane time synchronization service report and cause transmission of the C-plane time synchronization service report to AMF 108, see block 608.

[00109] Upon receipt of one or more C-plane time synchronization service reports AMF 108 may provide means for processing the time synchronization service report information into chargeable monitoring data for transmission to CHF 128, see block 610. For example, AMF 108 may compare the number and/or accuracy of time synchronization messages (e.g., SIB9, etc.) transmitted to UE 102 against a minimum number threshold and/or a minimum accuracy threshold in order to signal to CHF 128 that an account associated with UE 102 should be charged at a particular rate. In some embodiments if either the number and/or accuracy of time synchronization messages is below a comparable threshold value then AMF 108 may be configured to report no charging or charging at a lower rate than if one or more threshold value was met or exceeded. As shown by block 612, AMF 108 causes transmission of the chargeable monitoring data, compiled from the one or more time synchronization service reports, to CHF 128. In some embodiments, CHF 128 may be integrated at least partially into one or more other network functions (e.g., AMF 108, SMF 110, etc.). In some embodiments, AMF 108 may be configured with rules and/or trigger conditions which if met by the one or more time synchronization service reports or information therein will cause the AMF 108 to identify a charge to CHF 128. In some embodiments, new applicable trigger conditions may be configured with AMF 108 to include charging profiles for UEs utilizing the network time synchronization services, wherein new applicable trigger conditions may be added to AMF 108, or other network functions, by way of software and/or firmware updates.

[00110] As shown by FIG. 6, UE 102 is connected to and register with a particular network. The connection between UE 102 and the network is facilitated at least in part by RAN 104. Additionally, UE 102, RAN 104, and/or the network have agreed to authorize C-plane reporting for time synchronization services rendered by the network to UE 102. For example, a service level agreement between UE 102 and a network provider may dictate that C-plane reporting for time synchronization services is a default configured for UE 102. Therefore, as RAN 104 provides for the transmission of time synchronization messages to UE 102 a gNB associated with RAN 104 may be configured to record information related to these time synchronization message. For example, the gNB may record the number of messages, the time period over which the messages were sent, a clock/time source associated with the generation of the messages, a function of UE 102 and/or the network that requested the messages, the like, or combinations thereof.

[00111] Upon collection of this time synchronization messaging information the gNB may compare the collected information against a charging profile associated with UE 102 to generate a time synchronization service report. The charging profile 102 may be further defined by the service level agreement. Alternatively, the gNB may only format or compile the time synchronization messaging information into a C-plane time synchronization service report. The gNB generated time synchronization service report is then transmitted by the gNB, and/or another component of RAN 104, to AMF 108. Upon receipt of the C-plane time synchronization service report from RAN 104, AMF 108 may process the time synchronization service report according to one or more of a charging profile, charging model, and/or the like. AMF 108 generates time synchronization usage monitoring data from the one or more time synchronization service reports received from RAN 104 and causes transmission of the time synchronization usage monitoring data to CHF 128. Upon receipt of the time synchronization usage monitoring data CHF 128 causes charging of an account associated with UE 102 based on the monitoring data.

[00112] FIG. 7 illustrates a table 700 that shows combinations of example network and user equipment configurations, according to some example embodiments. As shown by table 700, in some embodiments, UE 102 may be configured with Device-side Time Sensitive Networking Translators (DS-TT) in accordance with an example network architecture that supports Time Sensitive Communication (TSC) which utilizes the network system (e.g., the 5G System (5GS)) that is integrated into an associated external network as a Time Sensitive Networking (TSN) bridge. Example embodiments of this type of configuration may be deployed as part of the TSN bridge in order to handle bridge traffic. In an instance, such an embodiment is configured with gate schedule mechanisms, for example a Qbv mechanism, then the U-plane and C-plane delivery methods may both be employed. In an instance, no gate schedule mechanisms are configured, but a Time Synchronization Charge Advice Information (TSCAI) mechanism is configured with a gNB scheduler that needs to know time synchronization information in order to adjust to the TSC flow in accordance with the TSCAI, then either the U-plane delivery method and/or the C-plane delivery methods may be employed.

[00113] Alternatively, another example embodiment, as aforementioned, may be deployed as a stand-alone system which is not part of the TSN bridge. In an instance, no specific user plane Quality of Service (QoS) measures are defined but the UE needs time synchronization information from a time/clock source outside of the 5GS then the U-plane and C-plane delivery methods may both be employed. In an instance, no specific U-plane QoS measures are defined and the UE needs time synchronization information from a time/clock source outside of 5GS then the U-plane delivery method may be optional employed (e.g., dependent on whether transparent gPTP and/or PTP messaging and/or native 5G synchronization can be used) and the C-plane delivery method may be employed.

[00114] In accordance with other embodiments, as shown by table 700 in FIG. 7, UE 102 may be configured without DS-TT but rather uses time synchronization capabilities, as described by the present disclosure, to read SIB9 and/or RRC messages and set a real-time clock which is provided by the SIB9 and/or RRC messages. In such embodiments, the time synchronization deployment may be configured as a stand-alone system. In an instance, the stand-alone system is configured to receive native 3 GPP time synchronization service via an over the air interface from a 5G internal system clock then the C-plane delivery method may be employed. In an instance, the UE does not subscribe to and/or does not need synchronization service from the network then the C-plane delivery method is disabled and charging is determined according to the network operator policies.

[00115] FIG. 8 illustrates a flowchart of the operations of an example method 800 performed by an example apparatus 200 which, in one embodiment, may be embodied by a computing device, such as the user equipment, which may, in turn, include a computer program product comprising a non-transitory computer-readable medium storing computer program code to be executed by processor 202. As shown in block 802, apparatus 200 of this example embodiment incudes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for receiving, from a network, charging profile information comprising one or more of a charging rate, a charging model, or a synchronization delivery method. As shown in block 804, apparatus 200 is further configured with means, such as the processor 202, the communication interface 206 or the like, for causing transmission, to a user equipment, of at least a time synchronization information message. In some embodiments, apparatus 200 may be configured to cause transmission of the time synchronization information message in response to a request for time synchronization services received from at least a user equipment, wherein the user equipment caused the transmission of the request to apparatus 200. In response to causing the transmission of the time synchronization information message, apparatus 200 of this example embodiment may further include means, such as the processor 202, the memory 204, the communication interface 206 or the like, for generating, based on the charging profile information and the time synchronization information message, a control plane synchronization service report for the user equipment, see block 806. In some embodiments, the time synchronization information message is one or more of a radio resource control message, a system information block message, a generic precision time protocol message, or a precision time protocol message. Moreover, apparatus 200 of this example embodiment may further include means, such as the processor 202, the memory 204, the communication interface 206 or the like, for causing transmission, to the network, of the control plane synchronization service report, see block 808.

[00116] As outlined by FIG. 8, a gNB, for example, and/or another portion of an example RAN, is configured to receive instructions from a network, or network function such as the AMF or SMF to monitor, collect, and report back to the network any time synchronization information transmitted to a UE. The instructions received by the gNB from the network may include charging profile details for the UE based on a service level agreement between the UE and the network operator. For example, the charging profile may comprise conditions, such as a minimum level of service (e.g., a minimum number of time synchronization message transmitted to the UE), for charging an account associated with the UE based on time synchronization services rendered to the UE. Moreover, the charging profile may contain a fee schedule, rate information, and/or the like to inform the gNB which time synchronization services relate to the charging procedures. The gNB may then transmit time synchronization information in the form of SIB9, RRC, gPTP, and/or PTP messages to the UE and in response the gNB may then generate a time synchronization service report based on the services rendered to the UE. In some embodiments, time synchronization services may be provided by the gNB over a course of one or more time periods to the UE and as a result the gNB may compile the time synchronization service report over the course of the one or more time periods before causing transmission of the time synchronization service report to the network (e.g., the AMF, SMF, etc.). In some embodiments, the gNB may be dynamically updated by a network function of the network (e.g., AMF, SMF, CHF, PCF, etc.) over the course of the one or more time periods to include one or more other charging profiles for the UE or one or more other UEs. In some embodiments, if the gNB receives other charging profile information from the network that the previously compiled time synchronization service report information may be updated to reflect the other charging profile information. Moreover, in other embodiments, the previously compiled time synchronization service report information may remain the same and only time synchronization information collected after the receipt of the other charging profile information will reflect the other charging profile information.

[00117] FIG. 9 illustrates a flowchart of the operations of an example method 900 performed by an example apparatus 200 which, in one embodiment, may be embodied by a computing device, such as the user equipment, which may, in turn, include a computer program product comprising a non-transitory computer-readable medium storing computer program code to be executed by processor 202. As shown in block 902, apparatus 200 of this example embodiment incudes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for receiving, from a radio access network, a control plane synchronization service report associated with at least a user equipment. Additionally, apparatus 200 may be configured for receiving, from a user plane function, a user plane synchronization service report associated with at least the user equipment, see block 904. In response to the receipt of the control plane synchronization service report and/or the user plane synchronization service report, as shown in block 906, apparatus 200 may be configured to generate, based on the control plane synchronization service report or the user plane synchronization service report, synchronization usage monitoring data. Moreover, apparatus 200 may provide means for causing transmission, to a charging function, of the generated synchronization usage monitoring data, see block 908. [00118] As outlined by FIG. 9, a server comprising an SMF associated with a network, for example, is configured to receive C-plane time synchronization data and U-plane time synchronization data for a UE. The C-plane time synchronization data is provide, for example, by a gNB and the U-plane time synchronization data is provided by a UPF associated with the network. The gNB and UPF are configured to monitor and collect their respective time synchronization interactions with the UE and report the time synchronization services rendered back to the SMF. The gNB and UPF may be configured to monitor, collect, and report the information base on a charging profile or other time synchronization charging information received from the SMF or another network function associated therewith (e.g., a PCF, AMF, CHF, etc.). Upon receipt of the C-plane and U-plane time synchronization service reports the SMF uses this data to generate time synchronization usage monitoring data which can be used to charge an account associated with the UE being monitored. In some embodiments, the SMF may comprise at least partially a charging function (e.g., CHF, PCF, etc.) which is configured to charge the UE’s account. In some embodiments, the SMF causes transmission of the generated time synchronization usage monitoring data to the charging function (e.g., CHF, PCF, etc.) which then provides charging services.

[00119] FIG. 10 illustrates a flowchart of the operations of an example method 1000 performed by an example apparatus 200 which, in one embodiment, may be embodied by a computing device, such as the user equipment, which may, in turn, include a computer program product comprising a non-transitory computer-readable medium storing computer program code to be executed by processor 202. As shown in block 1002, apparatus 200 of this example embodiment incudes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for receiving, from a network entity (e.g., a PCF, SMF, etc.), one or more of a charging profile associated with at least a user equipment. Apparatus 200 further provides means for causing transmission, based on the charging profile, of a configuration signal to a radio access network, or radio access node thereof (e.g., gNB, NodeB, etc.), wherein the configuration signal at least defines parameters for generating a control plane synchronization service report associated with at least the user equipment, see block 1004. In some embodiments, the parameters for generating the control plane synchronization service report may comprise one or more of a rate, a charging model, or a time synchronization message type (e.g., SIB, RRC, PTP, etc.). Additionally, as shown in block 1006, apparatus 200 of this example embodiment incudes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for receiving, from a radio access network, a control plane synchronization service report associated with at least a user equipment. In response to the received control plane report, as shown in block 1008, the apparatus 200 may comprise means for generating, based on the control plane synchronization service report, synchronization usage monitoring data. Moreover, apparatus 200 of this example embodiment incudes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for causing transmission, to a charging function, of the synchronization usage monitoring data, see block 1010.

[00120] As outlined by FIG. 10, a server comprising an AMF associated with a network, for example, is configured to receive from a network entity (e.g., a PCF, SMF, etc.) a charging profile for a UE. The AMF may then configure another network entity, such as a gNB, to collect time synchronization information, based on the charging profile, for the UE and report that information back to the AMF. The AMF can then receive the time synchronization information from, for example, the gNB that is in communication with the UE. Moreover, the gNB may be further dynamically updated by the AMF to monitor, collect, and report additional C-plane time synchronization data to the AMF based on updated time synchronization charging information. For example, an updated charging profile may be provided by the PCF to the AMF and in turn the AMF may update the configuration at the gNB.

[00121] In some embodiments, a PCF may determine the charging profile information for the time synchronization service and provide this via the network to the AMF and/or gNB. In such embodiments, the PCF may determine the charging profile information based on one or more of a distribution delivery method (e.g., C-plane distribution, etc.), a time synchronization requirement, a network capability or configuration (e.g., TSN, TSC, etc.), or a network operator policy. In some embodiments, the PCF may be able to have dynamic control over the charging behavior at the AMF and/or the gNB. For example, the PCF may be configured to change charging profile information at the AMF and/or the gNB at any time or in response to a detect condition associated with the UE. Moreover, the AMF may be configured to request C-plane charging control regarding time synchronization services at the gNB. For example, the AMF may be configured to cause transmission of a signal to the gNB at any time to cause the gNB to monitor, collect, and/or report the time synchronization information associated with a respective UE. Upon receipt of the time synchronization information, from the gNB, the AMF may generate synchronization usage monitoring data that is then transmitted to a charging function (e.g., CHF, PCF, etc.) that provides further charging services (e.g., charge the UE’s account). In some embodiments, the AMF may comprise at least partially a charging function (e.g., CHF, PCF, etc.) which is configured to charge the UE’s account.

[00122] FIG. 11 illustrates a flowchart of the operations of an example method 1100 performed by an example apparatus 200 which, in one embodiment, may be embodied by a computing device, such as the user equipment, which may, in turn, include a computer program product comprising a non-transitory computer-readable medium storing computer program code to be executed by processor 202. As shown in block 1102, apparatus 200 of this example embodiment incudes means, such as the processor 202, the memory 204, the communication interface 206 or the like, for receiving, from at least a user equipment or a network, one or more interaction signals, wherein the one or more interaction signals comprises an identification of one or more of a time synchronization service delivery method, a time synchronization requirement, a network capability, or an operator policy. Additionally, as shown in block 1104, apparatus 200 of this example embodiment incudes means for determining, based on the one or more interaction signals, one or more of a charging profile for the user equipment. Moreover, apparatus 200 may be further configured to dynamically update a network function, such as the AMF and/or SMF, to include the charging profile for a respective user equipment, see block 1106.

[00123] As outlined by FIG. 11, a server comprising a PCF associated with a network, for example, is configured to receive input signals in order to identify information for determining how to monitor time synchronization services rendered to a UE. Additionally, the PCF may further identify how to charge the UE based on the identification information. For example, the input signals may be received from a server, or other client device, which includes at least a charging contract between the UE and the network operator. This information may be utilized by the PCF to generate a charging profile, or the like, and provide this information to a network function (e.g., AMF, SMF, CHF, gNB onboard function, etc.) configured to monitor, collect, and report time synchronization services utilized by the UE. The PCF may be further configured to dynamically update this information with the aforementioned network function in response to, for example, a time period change or newly received input signals identifying an new or updated charging contract between the UE and the network operator. For example, if the charging contract between the UE and the network operator included a promotional time period (e.g., the first six months of the contract period) then the UE may be charged at a lower rate or time synchronization services may be no charge for the promotional period. In such an example, the PCF may update the monitoring, collection, and reporting policies at the AMF, SMF, or gNB once the promotional period has ended. In some embodiments, the AMF and/or SMF may use the charging profile received from the PCF to configure other network entities to monitor, collect, and/or report time synchronization information. For example, an AMF may receive a charging profile from a PCF then the AMF can configure a RAN (e.g., a gNB, etc.) to report back time synchronization information in the form of a C-plane synchronization service report associated with at least a UE.

[00124] As described above, the referenced flowcharts of methods that can be carried out by an apparatus according to related computer program products comprising computer program code. It will be understood that each block of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by various means, such as hardware, firmware, processor, circuitry, and/or other devices associated with execution of software including one or more computer program instructions. For example, one or more of the procedures described above can be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above can be stored by a memory device, e.g., 204, of an apparatus, e.g., 200, employing an example embodiment of the present disclosure and executed by processor, e.g., 202, of the apparatus. As will be appreciated, any such computer program instructions can be loaded onto a computer or other programmable apparatus (e.g., hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks. These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture, the execution of which implements the function specified in the flowchart blocks. The computer program instructions can 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 which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.

[00125] A computer program product is therefore defined in those instances in which the computer program instructions, such as computer-readable program code portions, are stored by at least one non-transitory computer-readable storage medium with the computer program instructions, such as the computer-readable program code portions, being configured, upon execution, to perform the functions described above. In other embodiments, the computer program instructions, such as the computer-readable program code portions, need not be stored or otherwise embodied by a non-transitory computer-readable storage medium, but can, instead, be embodied by a transitory medium with the computer program instructions, such as the computer-readable program code portions, still being configured, upon execution, to perform the functions described above.

[00126] Accordingly, blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, can be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.

[00127] In some embodiments, certain ones of the operations, methods, steps, processes, or the like, above can be modified or further amplified. Furthermore, in some embodiments, additional optional operations, methods, steps, processes, or the like, can be included. Modifications, additions, subtractions, inversions, correlations, proportional relationships, disproportional relationships, attenuation and/or amplifications to the operations above can be performed in any order and in any combination. It will also be appreciated that in instances where particular operations, methods, processes, or the like, required particular hardware such hardware may be considered as part of apparatus 200 for any such embodiment.

[00128] Many modifications and other embodiments of the present disclosure set forth herein will come to mind to one skilled in the art to which this disclosure pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the present disclosure is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and/or functions, it should be appreciated that different combinations of elements and/or functions can be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and/or functions than those explicitly described above are also contemplated as can be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.