Patent Application
20240414665
An example embodiment relates generally to techniques for conditional event reporting and, more particularly, to techniques for conditional event reporting of timing synchronization status.
Within next generation radio access network architecture, F1 application protocol reporting can be configured between a central network entity and a distributed network entity in several ways. One time reporting can be configured in a request/response format. Event-triggered reporting can be configured upon a change of serving cell, change in a user equipment presence in an area of interest, or other significant events. Event-triggered reporting can also occur periodically, such as A2event-triggered periodic reporting in an MI reporting configuration. Continuous periodic reporting can also be configured based on a periodicity configured for providing reports to a consumer. An example of such reports is an inter-system resource status request. Next generation application protocol reporting between a network entity and an access and mobility management function (AMF) have similar report types.
Timing resilience can be enabled with 5GS network timing synchronization status and reporting. Timing synchronization status monitoring can be triggered by a user equipment subscription that includes clock quality information. Timing synchronization status monitoring can also be triggered by a request from an application function (AF) to subscribe to time synchronization service status for a target user equipment including clock quality information within the request. A service configuration for a network timing synchronization status subscription includes clock quality detail level and clock quality acceptance criteria. Clock quality detail level indicates whether and which clock quality information to provide to a user equipment. The values for clock quality detail level include “clock quality metrics” or “acceptable/not acceptable indication”. Clock quality acceptance criteria indicates acceptable criteria for a user equipment. Clock quality acceptance criteria is included if the “clock quality detail level” is equal to “acceptable/not acceptable.” The application function may provide clock quality detail level and clock quality acceptance criteria. Alternatively, clock quality detail level and clock quality acceptance criteria can be part of the user equipment's subscription. If an application function provides these values, the same reporting configured to the user equipment (e.g., clock quality metrics or acceptable/not acceptable timing synchronization service) is notified to the application function requesting the service.
To determine timing synchronization status in a core, a time sensitive communication and time synchronization function (TSCTSF) subscribes to a radio access network (RAN) timing synchronizations status (TSS). The subscription can be through an access and mobility management function or through operations, administration, and maintenance. A radio access network timing synchronization status can be reported from a next generation radio access network node to the time sensitive communication and time synchronization function through the access and mobility management function. The radio access network timing synchronization status can be reported from the next generation radio access node to the subscribed user equipment to the service if the user equipment context stored at the next generation radio access network node indicates it.
Timing synchronization information may contain different attributes in the form of information elements. A synchronization state information element indicates the state of a node synchronization represented by values “Locked”, “Holdover”, or “Freerun”. A clock quality information element may be used. A traceable to global navigation satellite system information element indicates whether the current time source is traceable to the global navigation satellite system and is represented by values “Yes” or “No”. A traceable to coordinated universal time information element indicates whether the current time source is traceable to the coordinated universal time and is represented by values “Yes” or “No”. A frequency stability information element describes an estimate of the variation of a local clock when it is not synchronized to another source. A precision time protocol (PTP) clockClass information element is available under nodes are synchronized using (g) PTP. A clock accuracy information element describes a mean in nanoseconds over an ensemble of time measurements between a clock under test and a reference clock. A parent time source information element describes the primary source the node is currently using and can be represented by values “PTP”, “GNSS”, “atomic clock”, “terrestrial radio”, “serial time code”, “NTP”, “hand_set”, and “other”.
A next generation radio access network can be pre-configured with thresholds for each of the attributes listed above. When a radio access network timing synchronization status exceeds a threshold (status degradation) or when the radio access network timing synchronization status meets the thresholds again (status improvement), a radio access network node generates a radio access network timing synchronization report. The radio access network node notifies the time sensitive communication and time synchronization function using either N2 node level signaling via an access and mobility management function or via operations, administration, and maintenance. The radio access network node notifies the user equipment devices via broadcast notification using SIB 9 and dedicated radio resource control signaling of the user equipment is in RRC_CONNECTED.
Reporting towards a user equipment can indicate a clock quality acceptance criteria, which describes a condition for acceptable or not acceptable service operation for a user equipment. Evaluation of clock quality acceptance criteria may be performed by a distributed network entity if clock quality acceptance criteria is received from a central network entity. Evaluation of clock quality acceptance criteria can also be performed by a central network entity if clock quality metrics are received from a distributed network entity.
Information flow is used to control timing synchronization status reporting towards a user equipment and a time sensitive communication and time synchronization function. For non-user equipment associated signaling, a procedure can be used for signaling radio access node timing synchronization status or core network timing synchronization status to an application function which subscribed to a time sensitive communication and time synchronization function for network timing synchronization status. Information flow between an application function and a time sensitive communication and time synchronization function can be used to signal target user equipment identifiers and subscription to network status (e.g., providing a list of timing synchronization status attributes). Information flow between a time sensitive communication and time synchronization function and an access and mobility management function, between an access and mobility management function and a central unit of gNB (gNB-CU), and between a central unit of gNB and a distributed unit of gNB (gNB-DU) can be used to signal a timing synchronization status attributes list. For user equipment associated signaling, a procedure can be used for signaling time synchronization service for clock quality reporting to user equipment and application functions. Information flow between an application function and a time sensitive communication and time synchronization function, between a time sensitive communication and time synchronization function and an access and mobility management function, and between an access and mobility management function and a central unit of gNB can be used to signal target user equipment identifier, clock quality detail level, and clock quality acceptance criteria.
Timing synchronization status thresholds for the gNB are pre-configured by an operator and are the same in different radio access network nodes. The thresholds are relevant for service requirements at operator configuration and are assumed to be the smallest values of any potential timing synchronization service later requested for a user equipment. A central unit of gNB needs to know the timing synchronization status to report to a subscribed time sensitive communication and time synchronization function via an access and mobility management function. The central unit also reports the timing synchronization status to user equipment devices following the acceptance criteria. However, a distributed unit does not require the user equipment specific acceptance criteria. The distributed unit of gNB requires the thresholds to report the radio access network timing synchronization status (node level information) to the central unit gNB. In a case of continuous degradation or improvement, a gNB's thresholds can start or stop node level reporting between a central unit of gNB and a distributed unit of gNB. For enumerated attributes such as synchronization state, event based reporting in F1 application protocol and next generation application protocol may be used in which a report is generated and sent when there is a change in value. However, for non-enumerated attributes, there is no way to ensure that a central unit of gNB is aware of a timing synchronization status at the distributed unit of gNB to determine if the service is acceptable or unacceptable for a user equipment or to keep a time sensitive communication and time synchronization function updated with latest status degradations or improvements via an access and mobility management function using next generation application protocol reporting between a central unit of gNB and an access and mobility management function, unless a report is generated upon every change in value which creates an unnecessary large volume of reports. Event triggered reporting when the timing synchronization status is met can't capture a user equipment's clock quality acceptance criteria.
A method, apparatus, and computer program product are provided for conditional event reporting.
In an example embodiment, a network node is provided that includes at least one processor and at least one memory including computer program code with the at least one memory and the computer program code configured to, with the at least one processor, cause the network node to determine at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute. The at least one memory and the computer program code are further configured to, with the at least one processor, cause the network node to transmit, to a second network node, the radio access network timing synchronization status reporting range.
In an example embodiment, a core network node is provided that includes at least one processor and at least one memory including computer program code with the at least one memory and the computer program code configured to, with the at least one processor, cause the core network node to determine at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute.
In an example embodiment, a user equipment is provided that includes at least one processor and at least one memory including computer program code with the at least one memory and the computer program code configured to, with the at least one processor, cause the user equipment to determine a clock quality acceptance criteria. The at least one memory and the computer program code are further configured to, with the at least one processor, cause the user equipment to transmit the clock quality acceptance criteria.
In an example embodiment, a method is provided that includes determining, by a network node, at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute. The method further includes transmitting, to a second network node, the radio access network timing synchronization status reporting range.
In an example embodiment, a method is provided that includes determining, by a core network node, at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute.
In an example embodiment, a method is provided that includes determining, by a user equipment, a clock quality acceptance criteria. The method further includes transmitting the clock quality acceptance criteria.
In an example embodiment, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a network node, cause the network node to at least determine at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute. The non-transitory computer readable storage medium further includes computer instructions configured, upon execution, to transmit, to a second network node, the radio access network timing synchronization status reporting range.
In an example embodiment, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a core network node, cause the core network node to at least determine at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute.
In an example embodiment, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a user equipment, cause the user equipment to at least determine a clock quality acceptance criteria The non-transitory computer readable storage medium further includes computer instructions configured, upon execution, to transmit the clock quality acceptance criteria.
In an example embodiment, a network node is provided that includes means for determining at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute. The network node further includes means for transmitting, to a second network node, the radio access network timing synchronization status reporting range.
In an example embodiment, a core network node is provided that includes means for determining at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute.
In an example embodiment, a user equipment is provided that includes means for determining a clock quality acceptance criteria. The user equipment further includes means for transmitting the clock quality acceptance criteria.
Having thus described certain example embodiments of the present disclosure in general terms, reference will hereinafter be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
Some embodiments of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments are shown. Indeed, various embodiments may be embodied in many different forms and not to be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. As used herein, the terms “data,” “content,” “information,” and similar terms may be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present disclosure. Thus, use of any such terms not to be taken to limit the spirit and scope of embodiments of the present disclosure.
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) including 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 including 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 (such as a core network apparatus), field programmable gate array, and/or other computing device.
As used herein, the term “computer-readable medium” refers to non-transitory storage hardware, non-transitory storage device or non-transitory computer system memory that may be accessed by a controller, a microcontroller, a computational system or a module of a computational system to encored thereon computer-executable instructions or software programs. A non-transitory “computer readable medium” may be accessed by a computational system or a module of a computational system to retrieve and/or execute the computer-executable instructions or software programs encoded on the medium. Examples of non-transitory computer-readable media may include, but are not limited to, one or more types of hardware memory, non-transitory tangible media (for example, one or more magnetic storage disks, one or more optical disks, one or more universal synchronous bus (USB) flash drives), computer system memory or random-access memory (such as dynamic random access memory (DRAM), static random access memory (SRAM), extended data out random access memory (EDO RAM), and the like.
As illustrated in
The data that is transmitted between the user equipment 110, distributed network entity 120, central network entity 130, and the core network entity 140 can be any of a wide variety of data including, but not limited to digital imagery data including video data, audio data as well as data provided by sensors, radars, telescopes and radio receivers. In at least some instances, the data is encoded prior to communication of the data via the uplink and downlink beams and decoded upon reception. The resulting data received may be utilized for a variety of purposes including presentation to a user, storage of the data for subsequent use and/or provision of the data to one or more applications, such as applications that perform statistical inference on the data for various purposes including object recognition, image classification, spectrum sensing, speech transcription and/or prediction or detection of events.
The user equipment 110 of
The distributed network entity 120 and the central network entity 130 of
The core network entity 140 may comprise any of an access and mobility management function (AMF), a time sensitive communication and time synchronization function (TSCTSF), an application function (AF), or the like. Core network entity 140 may be configured to communicate with any of user equipment 110, distributed network entity 120, and central network entity 130.
The apparatus 200 may, in some embodiments, be embodied in various computing devices described as above. However, in some embodiments, the apparatus may be embodied as a chip or chip set. In other words, the apparatus may include 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 may provide physical strength, conservation of size, and/or limitation of electrical interaction for component circuitry included thereon. The apparatus may therefore, in some cases, be configured to implement an embodiment on a single chip or as a single “system on a chip.” As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.
The processing circuitry 220, also referenced as a processor, may be embodied in a number of different ways. For example, the processing circuitry may 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 ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processing circuitry may include one or more processing cores configured to perform independently. A multi-core processing circuitry may enable multiprocessing within a single physical package. Additionally or alternatively, the processing circuitry may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining, and/or multithreading.
In an example embodiment, the processing circuitry 220 may be configured to execute instructions stored in the memory device 240 or otherwise accessible to the processing circuitry. Alternatively or additionally, the processing circuitry may be configured to execute hardcoded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processing circuitry may 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 processing circuitry is embodied as an ASIC, FPGA or the like, the processing circuitry may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processing circuitry is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and/or operations described herein when the instructions are executed. However, in some cases, the processing circuitry may be a processor of a specific device (e.g., an image or video processing system) configured to employ an embodiment by further configuration of the processing circuitry by instructions for performing the algorithms and/or operations described herein. The processing circuitry may include, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processing circuitry.
The communication interface 260 may 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 including media content in the form of video or image files, one or more audio tracks or the like. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and/or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). In some environments, the communications interface may alternatively or also support wired communication. As such, for example, the communication interface may include a communication modem and/or other hardware/software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.
Turning now to
Turning now to
Turning now to
Turning now to
In one or more embodiments, for enumerated attributes in the RAN time synchronization status (e.g., synchronization state, traceable to coordinated universal time, traceable to global navigation satellite system, parent time source), the distributed unit of gNB 610 reports to the central unit of gNB 620 when there is a change in the enumerated value of the list, as shown in
In one or more embodiments, for integer attributes in the radio access network timing synchronization status (e.g., clock accuracy, frequency stability) the distributed unit of gNB reports to the central unit of gNB when the integer value is above a threshold and there is a change beyond an additional enumerated report range value, as shown in report 520 of
Turning now to
In one or more embodiments, at operation 640, the central unit of gNB 620 transmits a clock quality reporting control request to the distributed unit of gNB 610. In one or more embodiments, the request is transmitted in F1 application protocol. In one or more embodiments, the clock quality reporting control request comprises a list of clock quality attributes. In one or more embodiments, the event-based reporting available in the F1 application protocol and next generation application protocol is extended to add a condition for reporting while the event is active.
In one or more embodiments, the central unit the gNB 620 requests clock quality information from the distributed unit the gNB 610. In one or more embodiments, the request includes conditional event reporting provided by a reporting range for one or more clock quality attributes to the distributed unit the gNB 610.
In one or more embodiments, the clock quality reporting control request requires an additional reporting range information element. In one or more embodiments, the reporting range information element was provisioned per synchronization status attribute when an access and mobility management function sent a clock quality information subscription at a central unit the gNB 620 via next generation application protocol signaling. In one or more embodiments, the application function determined the reporting range based on knowledge of the time synchronization service requirements. In one or more embodiments, the application function included in its request for time synchronization with clock quality information a range for reporting the set of attributes of interest. In one or more embodiments, the reporting rang per attribute is sent from the time sensitive communication and time synchronization function to the central unit gNB 620 via an access and mobility management function to control the radio access node timing synchronization status reporting. In one or more embodiments, the application function determines what is interesting from a service perspective to be reported.
In one or more embodiments, the reporting range transmitted at operation 640 is adjusted to align with the attribute magnitude. In one or more embodiments, the reporting range may be defined depending on the acceptance criteria of user equipment 710 connected to distributed unit of gNB 610. In one or more embodiments, the reporting range for the radio access network timing synchronization status attribute comprises a quantization of the attribute. In one or more embodiments, linear quantization is used to determine the reporting range with the same quantization interval. In one or more embodiments, non-linear quantization is used to determine the reporting range. In one or more embodiments when non-linear quantization is used, quantization error changes with the clock accuracy range. In one or more embodiments, the central unit of gNB 620 configures the distributed unit of gNB 610 to report with quantization steps (e.g., the reporting range) of 50 nanoseconds in the range between 200 and 400 nanoseconds. In one or more embodiments, the central unit of gNB 620 configures the distributed unit gNB 610 to report with quantization steps (e.g., the reporting range) of 100 nanoseconds in the range is above 400 nanoseconds. In one or more embodiments, quantization is performed by defining a list of thresholds (e.g., intermediate thresholds for reporting). In one or more embodiments, a CHOICE structure for the report type is used. In one or more embodiments, a reporting event is defined for each threshold independently. In one or more embodiments, one F1 application protocol reporting configuration comprises one threshold. In one or more embodiments, where a reporting event is defined for each threshold independently, the central unit of gNB 620 provides multiple reporting at the distributed unit of gNB 610. In one or more embodiments, each reporting threshold comprises an identifier for management when the central unit of gNB 620 terminates the reporting. In one or more embodiments, each threshold requires a subscription between the nodes for managing the subscription independently.
In one or more embodiments, at operation 650, the distributed unit of gNB 610 determines whether a request can be supported. In one or more embodiments, the distributed unit of gNB 610 determines whether the received request is supported.
In one or more embodiments, the distributed unit of gNB 610 uses pre-configured thresholds to determine when to transmit a clock quality metrics to the central unit of the gNB 620. In one or more embodiments, the pre-configured thresholds are configured in the distributed unit of disaggregated gNB 610 in a situation when the reporting request is transmitted from central unit gNB 620. In other embodiments, the pre-configured thresholds are configured in the central unit of gNB 620 and the central unit provides the pre-configured threshold is a reporting configuration request message to the distributed unit of gNB.
In one or more embodiments, at operation 660, the distributed unit of gNB 610 transmits a clock quality reporting control response to the central unit of gNB 620. In one or more embodiments, the response is transmitted in F1 application protocol. In one or more embodiments, the response includes a request result. In one or more embodiments, the distributed unit of gNB indicates success or failure of the request. In one or more embodiments, the request is successful when the distributed unit of gNB 610 is capable of providing at least one of the attributes with one of the received conditional reporting thresholds or ranges. In one or more embodiments, the request is successful when the distributed unit gNB 610 is capable of providing at least one of the attributes based on a pre-configured threshold. In one or more embodiments, the response includes a failure list. In one or more embodiments, the failure list includes a list of attributes or conditions that the distributed unit gNB is unable to support.
Turning now to
In one or more embodiments where clock quality information is provided by the application function 725, the process 700 includes operations 735-750. In one or more embodiments, the time sensitive communication and time synchronization function 720 is responsible for determining the reporting range.
In one or more embodiments, at operation 735, an access and mobility management function 715, a time sensitive communication and time synchronization function 720, and an application function 725 are configured with clock quality information reporting. In one or more embodiment, the core network comprises a time synchronization service. In one or more embodiments, the clock quality information reporting is to the user equipment 710 and the application function 725.
In one or more embodiments, application function 725, time sensitive communication and time synchronization function 720, or access and mobility management function 715 are interested in receiving the timing synchronization status when the change in timing synchronization impacts the timing synchronization service for a user equipment 710 in a way that the service is provided in an acceptable or unacceptable level based on the user equipment's 710 clock quality acceptance criteria. In one or more embodiments, in this scenario, the time sensitive communication and time synchronization function 720 and the access and mobility management function 715 do not provide the timing synchronization status reporting ranges. In one or more embodiments, in this scenario, the central unit the gNB determines the timing synchronization status reporting ranges based on the clock quality acceptance criteria of all user equipment devices for which a clock quality acceptance criteria is configured (e.g., user equipment 710). In one or more embodiments, a radio access network timing synchronization status report towards the access and mobility management function 715 and the time sensitive communication and time synchronization function 720 may then be initiated when a clock quality changes from acceptable to unacceptable in a user equipment.
In one or more embodiments, at operation 740, clock quality acceptance criteria are transmitted from the access and mobility management function 715 to the central unit of gNB 620. In one or more embodiments, the clock quality acceptance criteria are transmitted with a user equipment context modification in next generation application protocol. In one or more embodiments, the clock quality acceptance criteria are transmitted with a user equipment context setup in next generation application protocol.
In one or more embodiments, at operation 745, the time sensitive communication and time synchronization function 720 determines the radio access network reporting ranges. In one or more embodiments, the time sensitive communication and time synchronization function 720 determines the radio access network reporting ranges based the application function's 725 requests for time synchronization service including clock quality reporting information.
In one or more embodiments, at operation 750, the time sensitive communication and time synchronization function 720 subscribes to radio access network timing synchronization status including reporting ranges. In one or more embodiments, the time sensitive communication and time synchronization function 720 provisions the reporting range to the access and mobility management function 715. In one or more embodiments, the time sensitive communication and time synchronization function 720 sends additional thresholds.
In one or more embodiments where clock quality information is available at the user equipment's 710 subscription data, the process 700 includes operation 755. In or more embodiments, the access and mobility management function 715 is responsible for determining the reporting ranges. In one or more embodiments, this is advantageous in that the application and mobility management function 715 has a wider view than the central unit of gNB 620 to consider the time synchronization service continuation across gNBs. In one or more embodiments, the access and mobility management function has an understanding of application request ranging from minimal acceptance threshold values for clock quality to the best possible values for clock quality. In one or more embodiments, it is useful for the access and mobility management function 715 to determine the radio access node time synchronization service ranges when mobility to a target cell can be conditioned to the synchronization status if multiple candidates are available.
In one or more embodiments, at operation 755, the access and mobility management function determines the radio access network reporting ranges. In one or more embodiments, the access and mobility management function determines the reporting ranges based on based on the time sensitive communication and time synchronization function 720 requests for time synchronization service including clock quality reporting information and user equipment 710 subscriptions.
In one or more embodiments, at operation 760, the access and mobility management function transmits the radio access network timing synchronization status reporting ranges to the central unit of gNB 620. In one or more embodiments, the radio access network timing synchronization service reporting ranges are transmitted to a central unit of gNB 620 with a next generation application protocol radio access network timing synchronization service subscription request. In one or more embodiments, the access and mobility management function 715 forwards the reporting ranges from the time sensitive communication and time synchronization function 720 to the central unit of gNB 620. In one or more embodiments, the access and mobility management function 715 modifies or complements thresholds received from the time sensitive communication and time synchronization function 720 when subscribing for receiving timing synchronization status with the information to the central unit of gNB 620. In one or more embodiments, the access and mobility management function 715 requests the central unit of gNB 620 conditional event reporting. In one or more embodiments, the central unit of gNB later requests the distributed unit of gNB reporting via F1 application protocol.
In one or more embodiments at operation 765, the central unit of gNB 620 stores pre-configured thresholds as well as clock quality acceptance criteria. In one or more embodiments, the clock quality acceptance criteria is associated with user equipment 710. In one or more embodiments, the central unit of gNB stores reporting ranges received from access and mobility management function 715.
In one or more embodiments, at operation 770, in a scenario where radio access network reporting ranges are not received from the access and mobility management function, the central unit of gNB determines radio access network timing synchronization service reporting ranges. In one or more embodiments, the central unit of gNB determines the radio access network timing synchronization status based on an access and mobility management function request for timing synchronization status and based on user equipment contexts (e.g., clock quality reporting information or clock quality acceptance criteria).
In one or more embodiments, at operation 775, the central unit of gNB 620 subscribes to clock quality metrics at the distributed unit of gNB 610. In one or more embodiments, operation 775 comprises node level signaling. In one or more embodiments, at operation 775, the central unit of gNB transmits the radio access network timing synchronization status attribute reporting ranges to the distributed unit of gNB. In one or more embodiments, the reporting ranges are transmitted with clock quality reporting control.
In one or more embodiments, at operation 780, time source degradation occurs at distributed of gNB 610.
In one or more embodiments, at operation 785, a radio access network timing synchronization status exceeds the distributed unit's threshold. In one or more embodiments, upon the timing synchronization status exceeding the threshold, the reporting range is monitored.
In one or more embodiments, at operation 790, the distributed unit of gNB 610 transmits a clock quality report to the central unit of gNB 620. In one or more embodiments, the clock quality report is transmitted in response to a radio access network timing synchronization status value being exceeded. In one or more embodiments, the clock quality report indicates the radio access network timing synchronization service attribute value for which the threshold was exceeded.
In one or more embodiments, at operation 792, the central unit of gNB 620 evaluates the time synchronization service status for the user equipment 710.
In one or more embodiments, at operation 794, the central unit of gNB 620 performs radio resource dedicated signaling to the user equipment 710. In one or more embodiments, the dedicated signaling indicates a radio access network timing synchronization status. In one or more embodiments, the central unit of gNB 620 signals the user equipment 710 through the distributed unit of gNB 610.
In one or more embodiments, at operation 796, the radio access network timing synchronization service reporting range is exceeded. In one or more embodiments, the radio access network reporting range is exceeded on top of the radio access network timing synchronization service threshold exceeded at operation 785.
In one or more embodiments, at operation 798, a clock quality report is transmitted to the central unit of gNB 610 from the distributed unit of gNB 610. In one or more embodiments, the clock quality report indicates that the radio access network timing synchronization service reporting range has been exceeded. In one or more embodiments, the clock quality report indicates the attribute value that was transmitted by the distributed unit of gNB 610.
In one or more embodiments, at operation 799, the central unit of gNB 620 performs radio resource dedicated signaling to the user equipment 710. In one or more embodiments, the dedicated signaling indicates a radio access network timing synchronization status. In one or more embodiments, the central unit of gNB 620 signals the user equipment 710 through the distributed unit of gNB 610.
Turning now to
In one or more embodiments, at operation 810, user equipment 710 provides a clock quality acceptance criteria to access and mobility management function 715. In one or more embodiments, the clock quality acceptance criteria is later forwarded to the central unit of gNB 620 at operation 760. In one or more embodiments, the clock quality control acceptance criteria is transmitted in a non access stratum message. In one or more embodiments, the non access stratum message comprises a non access stratum registration request. In one or more embodiments, the non access stratum message comprises an uplink non access stratum transport.
In one or more embodiments, at operation 820, the user equipment 710 provides a clock quality acceptance criteria to central unit of gNB 620. In one or more embodiments, the clock quality acceptance criteria is provided over radio resource control. In one or more embodiments, the message is a UEAssistanceInformation message.
Turning now to
Some operations performed in both
In one or more embodiments, a central unit of gNB 620 influences a distributed unit's 610 pre-configured threshold based on clock quality acceptance criteria. In one or more embodiments, central and distributed unit of gNB 620 and 610 have thresholds configured for radio access network timing synchronization status reporting (e.g., clock accuracy of 200 nanoseconds). In one or more embodiments, the central unit of gNB 620 receives user equipment context from access and mobility management function 715 with a clock quality acceptance criteria (e.g., clock accuracy of 300 nanoseconds). In one or more embodiments, the central unit of gNB 620 determines that there is no user equipment context that uses a value as low as the preconfigured threshold (e.g., all user equipment devices have clock quality acceptance criteria above 300 nanoseconds). In one or more embodiments, the central unit of gNB 620 sends a command to the distributed unit of gNB 610 to monitor an additional threshold comprising a reporting range for clock accuracy (e.g., update to 300 nanoseconds). In one or more embodiments, the additional threshold is sent when the central unit of gNB requests the subscription for radio access network timing synchronization service at operation 775. In one or more embodiments, the additional threshold is part of a new F1 application protocol procedure. In one or more embodiments, there is a different signaling in F1 application protocol than next generation application protocol in that the access and mobility management function 715 does not provide thresholds to the central unit of gNB. In one or more embodiments, adding a threshold will impact reporting towards user equipment devices and the time sensitive communication and time synchronization function 720. In one or more embodiments, the central unit of gNB sends a reporting range when it can ensure active subscriptions to status updates won't be neglected.
Turning now to
Turning now to
As shown in block 1110 of
As shown in block 1120 of
Turning now to
As shown in block 1210 of
As shown in block 1220 of
Turning now to
As shown in block 1310 of
As shown in block 1320 of
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.
In one or more embodiments, a network node (620) is provided, including at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the network node (620) to determine at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute and transmit, to a second network node (610), the radio access network timing synchronization status reporting range.
In one or more embodiments, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the network node (620) to receive, from the second network node (610), a radio access network timing synchronization status report when a timing synchronization status threshold and the radio access network timing synchronization status reporting range are satisfied.
In one or more embodiments, the at least one radio access network timing synchronization status reporting range is determined based on the timing synchronization status threshold.
In one or more embodiments, the at least one radio access network timing synchronization status reporting range is determined based on at least one user equipment clock quality acceptance criteria.
In one or more embodiments, the at least one radio access network timing synchronization status reporting range comprises a step value, wherein the network node (130) receives the radio access network timing synchronization status report when the timing synchronization status threshold is exceeded by an integer multiple of the step value.
In one or more embodiments, the at least one user equipment clock quality acceptance criteria is received from a user equipment (710).
In one or more embodiments, the at least one user equipment clock quality acceptance criteria is received over radio resource control.
In one or more embodiments, the at least one user equipment clock quality acceptance criteria is received from a core network node.
In one or more embodiments, the at least one radio access network timing synchronization reporting range is determined based on a plurality of user equipment clock quality acceptance criteria.
In one or more embodiments, the at least one radio access network timing synchronization status reporting range is received from a core network node (715/720).
In one or more embodiments, the core network node (715/720) includes at least one or both of: an access and mobility management function (AMF) and a time sensitive communication and time synchronization function (TSCTSF).
In one or more embodiments, the time sensitive communication and time synchronization function determines the radio access network timing synchronization status reporting range and subscribes to the access and mobility management function for at least one radio access network timing synchronization status (RAN TSS). [745/750]
In one or more embodiments, the access and mobility management function is configured to pass the at least one radio access network timing synchronization status reporting range provided by the time sensitive communication and time synchronization function when the at least one user equipment clock quality acceptance criteria is not present. [750/760]
In one or more embodiments, the at least one radio access network timing synchronization status reporting range includes a plurality of radio access network timing synchronization status reporting ranges associated with a plurality of radio access network timing synchronization status attributes.
In one or more embodiments, a core network node (715/720) is provided, including at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the core network node (715/720) to determine at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute. [745/755]
In one or more embodiments, the at least one memory and the computer program code are further configured to, with the at least one processor, cause the core network node (715/720) to transmit the at least one radio access network timing synchronization status reporting range to a network node (620).
In one or more embodiments, the core network node (720) includes at least one or both of: an access and mobility management function (AMF) (715) and a time sensitive communication and time synchronization function (TSCTSF) (720).
In one or more embodiments, the at least one radio access network timing synchronization status reporting range is determined based on at least one user equipment clock quality acceptance criteria.
In one or more embodiments, the at least one clock quality acceptance criteria includes a plurality of clock quality acceptance criteria.
In one or more embodiments, the at least one clock quality acceptance criteria is received from at least one user equipment.
In one or more embodiments, the time sensitive communication and time synchronization function (720) determines the radio access network timing synchronization status reporting range and subscribes to the access and mobility management function (715) for at least one radio access network timing synchronization (RAN TSS).
In one or more embodiments, the access and mobility management function (715) is configured to pass the at least one radio access network timing synchronization status reporting range provided by the time sensitive communication and time synchronization function (720) when the at least one user equipment clock quality acceptance criteria is not present.
In one or more embodiments, the at least one clock quality acceptance criteria is received through a non access stratum message.
In one or more embodiments, the non access stratum message includes a non access stratum registration request.
In one or more embodiments, the non access stratum message includes an uplink non access stratum transport.
In one or more embodiments, a user equipment (710) is provided, including at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the user equipment (710) to determine a clock quality acceptance criteria and transmit the clock quality acceptance criteria. [810/820]
In one or more embodiments, the clock quality acceptance criteria is transmitted to a core network node (715).
In one or more embodiments, the clock quality acceptance criteria is transmitted through a non access stratum message.
In one or more embodiments, the non access stratum message includes a non access stratum registration request.
In one or more embodiments, the non access stratum message includes an uplink non access stratum transport.
In one or more embodiments, the clock quality acceptance criteria is transmitted to a network node (620).
In one or more embodiments, the clock quality acceptance criteria is transmitted over radio resource control.
In one or more embodiments, a network node is provided, including means for determining at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute and means for transmitting, to a second network node, the radio access network timing synchronization status reporting range.
In one or more embodiments, the network node further includes means for receiving, from the second network node, a radio access network timing synchronization status report when a timing synchronization status threshold and the radio access network timing synchronization status reporting range are satisfied.
In one or more embodiments, the at least one radio access network timing synchronization status reporting range is determined based on the timing synchronization status threshold.
In one or more embodiments, the at least one radio access network timing synchronization status reporting range is determined based on at least one user equipment clock quality acceptance criteria.
In one or more embodiments, the at least one radio access network timing synchronization status reporting range comprises a step value, wherein the network node receives the radio access network timing synchronization status report when the timing synchronization status threshold is exceeded by an integer multiple of the step value.
In one or more embodiments, the at least one user equipment clock quality acceptance criteria is received from a user equipment.
In one or more embodiments, the at least one user equipment clock quality acceptance criteria is received over radio resource control.
In one or more embodiments, the at least one user equipment clock quality acceptance criteria is received from a core network node.
In one or more embodiments, the at least one radio access network timing synchronization reporting range is determined based on a plurality of user equipment clock quality acceptance criteria.
In one or more embodiments, the at least one radio access network timing synchronization status reporting range is received from a core network node.
In one or more embodiments, the core network node includes at least one or both of: an access and mobility management function (AMF) and a time sensitive communication and time synchronization function (TSCTSF).
In one or more embodiments, the time sensitive communication and time synchronization function determines the radio access network timing synchronization status reporting range and subscribes to the access and mobility management function for at least one radio access network timing synchronization status (RAN TSS).
In one or more embodiments, the access and mobility management function is configured to pass the at least one radio access network timing synchronization status reporting range provided by the time sensitive communication and time synchronization function when the at least one user equipment clock quality acceptance criteria is not present.
In one or more embodiments, the at least one radio access network timing synchronization status reporting range includes a plurality of radio access network timing synchronization status reporting ranges associated with a plurality of radio access network timing synchronization status attributes.
In one or more embodiments, a core network node is provided, including means for determining at least one radio access network timing synchronization status reporting range associated with at least one radio access network timing synchronization status attribute.
In one or more embodiments, the core network node further includes means for transmitting the at least one radio access network timing synchronization status reporting range to a network node.
In one or more embodiments, the core network node includes at least one or both of: an access and mobility management function (AMF) and a time sensitive communication and time synchronization function (TSCTSF).
In one or more embodiments, the at least one radio access network timing synchronization status reporting range is determined based on at least one user equipment clock quality acceptance criteria.
In one or more embodiments, the at least one clock quality acceptance criteria includes a plurality of clock quality acceptance criteria.
In one or more embodiments, the at least one clock quality acceptance criteria is received from at least one user equipment.
In one or more embodiments, the time sensitive communication and time synchronization function determines the radio access network timing synchronization status reporting range and subscribes to the access and mobility management function for at least one radio access network timing synchronization (RAN TSS).
In one or more embodiments, the access and mobility management function is configured to pass the at least one radio access network timing synchronization status reporting range provided by the time sensitive communication and time synchronization function when the at least one user equipment clock quality acceptance criteria is not present.
In one or more embodiments, the at least one clock quality acceptance criteria is received through a non access stratum message.
In one or more embodiments, the non access stratum message includes a non access stratum registration request.
In one or more embodiments, the non access stratum message includes an uplink non access stratum transport.
In one or more embodiments, a user equipment is provided, including means for determining, a clock quality acceptance criteria and means for transmitting the clock quality acceptance criteria.
In one or more embodiments, the clock quality acceptance criteria is transmitted to a core network node.
In one or more embodiments, the clock quality acceptance criteria is transmitted through a non access stratum message.
In one or more embodiments, the non access stratum message includes a non access stratum registration request.
In one or more embodiments, the non access stratum message includes an uplink non access stratum transport.
In one or more embodiments, the clock quality acceptance criteria is transmitted to a network node.
In one or more embodiments, the clock quality acceptance criteria is transmitted over radio resource control.
Many modifications and other embodiments 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 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 may 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 may 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.
| Number | Date | Country | |
|---|---|---|---|
| 63501859 | May 2023 | US |
