Method and device for supporting time service continuity, equipment and storage medium
By determining and switching to a target service node that meets the timed service needs in the communication system, the problem of difficult to guarantee the timed service continuity during the base station or UPF handover is solved, and service stability is achieved when the UE moves or timed service needs change.
Patent Information
- Application Number
- CN202310533009.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-11
- Publication Date
- 2024-11-12
AI Technical Summary
When the existing communication system switches the base station or UPF, it is difficult to ensure the continuity of the timing service, especially when the UE's mobile or timing service needs change, the difference in timing capabilities of the base station and UPF leads to service interruption.
By determining the target service node that meets the timing service needs and switching, the terminal ensures that the terminal continues to provide stable timing services when the UE moves or timing service needs change. The specific method includes receiving and analyzing timing capability information, time synchronization status and handover indication information based on the current service node type and target conditions, and selecting a suitable target node for handover.
It realizes that when the UE's mobile or timed service needs change, maintains the continuity of the timed service, avoids service interruptions, and ensures the stability of the timed service by the terminal.
Smart Images

Figure CN118944794A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a method, apparatus, device and storage medium for supporting timing service continuity. Background Art
[0002] Currently, the communication system supports opening the clock synchronization service to AF and UE. AF can request (g)PTP synchronization service, use the TSN domain clock as GM (master clock), and synchronize UE to TSN domain clock. In addition, AF can request 5G accessstratum time distribution synchronization service, use 5G clock as GM, and synchronize UE to 5G clock. In addition, the communication system supports flexible timing service, and can open the network timing synchronization status (such as clock source signal attenuation or recovery) to UE and AF.
[0003] When the base station or UPF switches due to reasons such as UE mobility or the inability to meet the timing service requirements requested by the AF, it is considered that different base stations or UPFs are synchronized to the same clock source (e.g., all synchronized to GNSS), that is, the base stations or UPFs have the same timing capabilities. Therefore, the timing service will not change due to the switching of the base station or UPF.
[0004] However, the timing capabilities of base stations and UPF / NW-TT are different. Therefore, how to ensure the continuity of timing services is an urgent problem to be solved. Summary of the invention
[0005] The present application provides a method, apparatus, device and storage medium for supporting the continuity of timing service, so as to ensure the continuity of timing service for a terminal.
[0006] In a first aspect, the present application provides a method for supporting the continuity of timing services, which is applied to a first node. The method includes: determining a target service node that meets the timing service requirements as the service node after switching based on the service node type and target conditions currently serving the terminal; and indicating information of the target service node.
[0007] In some embodiments, when the source service node is a source RAN node, the target condition includes receiving at least one of the following switching information: timing capability information of the target RAN node, a node identification list of the target RAN node, a signal measurement report of the source RAN node and / or the target RAN node, a time synchronization error budget parameter and / or a clock quality acceptance standard parameter to be met by the target RAN node, and the time synchronization status of the source RAN node; when the source service node is a source UPF node, the target condition includes receiving at least one of the following switching information: timing capability information of the target UPF node, a data network access identifier DNAI or a candidate DNAI of the target UPF node, a time synchronization error budget parameter and a clock quality acceptance standard parameter to be met by the target UPF node, and the time synchronization status of the source UPF node.
[0008] In some embodiments, the target condition further includes: determining that the source service node does not meet the timing service requirements, the timing service requirements including time synchronization error budget and / or clock quality acceptance criteria.
[0009] In some embodiments, when the source service node is a source RAN node, the switching information is received in the following manner: in response to detecting a change in the timing capability information of the source RAN node, requesting the source RAN node to obtain switching indication information and / or a list of identifiers of a target RAN node; receiving switching indication information or a list of identifiers of a target RAN node from the source RAN node, the switching information including the switching indication information and / or the list of identifiers of the target RAN node, the switching indication information including the identifier information and / or signal measurement data of the target RAN node, and the list of identifiers of the target RAN node including a list of target RAN node identifiers or a list of cell identifiers.
[0010] In some embodiments, based on the service node type and target conditions currently serving the terminal, a target service node that meets the timing service requirements is determined as the service node after switching, including: determining the target RAN node based on the changed timing capability information of the source RAN node, as well as the switching indication information and / or the target RAN node identification list.
[0011] In some embodiments, when the source service node is a source RAN node, the switching information is received in the following manner: obtaining the timing service requirement and the time synchronization status of the source RAN node, the switching information includes the timing service requirement and the time synchronization status of the source RAN node; the timing service requirement includes at least one of the following: time synchronization error budget, clock quality detail level, clock quality acceptance criteria; the time synchronization status of the source RAN node includes at least one of the following: synchronization status, synchronization performance, clock quality and master time source of the source RAN node.
[0012] In some embodiments, whether the source service node meets the timing service requirement is determined in the following manner: whether the source RAN node meets the timing service requirement is determined based on the timing capability information of the source RAN node and the time synchronization status of the source RAN node.
[0013] In some embodiments, it also includes: receiving timing capability information from the source RAN node and the target RAN node, the timing capability information including at least one of the following: primary time source, clock quality, synchronization performance, punctuality performance, node identification, and cell identification list.
[0014] In some embodiments, when the source service node is a source UPF node, the switching information is received in the following manner: in response to a DNAI change of the source UPF node, a DNAI or a candidate DNAI of a target UPF node is received from a second node, and the switching information includes the DNAI or the candidate DNAI of the target UPF node.
[0015] In some embodiments, based on the service node type and target conditions currently serving the terminal, a target service node that meets the timing service requirements is determined as the service node after switching, including: determining the target UPF node based on the changed timing capability information of the source UPF node and the DNAI or candidate DNAI of the target UPF node.
[0016] In some embodiments, when the source service node is a source UPF node, the switching information is received in the following manner: obtaining the timing service requirements and the time synchronization status of the source UPF node, the switching information includes the timing service requirements and the time synchronization status of the source UPF node; the timing service requirements include at least one of the following: time synchronization error budget, clock quality detail level and clock quality acceptance criteria; the time synchronization status of the source UPF node includes at least one of the following: synchronization status, synchronization performance, clock quality and master time source of the source UPF node.
[0017] In some embodiments, whether the source service node meets the timing service requirements is determined in the following manner: based on the timing capability information of the source UPF node and the time synchronization status of the source UPF node, whether the source UPF node meets the timing service requirements is determined.
[0018] In some embodiments, it also includes: receiving timing capability information from the source UPF node and the target UPF node, the timing capability information including at least one of the following: main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
[0019] In some embodiments, after indicating the information of the target service node, it also includes: receiving the time synchronization status and / or timing capability information of the target service node; determining the time synchronization error budget of the target service node based on the time synchronization status and / or timing capability information of the target service node; and sending the time synchronization error budget to the target service node.
[0020] In a second aspect, the present application provides a method for supporting continuity of timing services, which is applied to a source service node. The method includes: sending timing capability information to a first node, so that the first node determines a target service node that meets the timing service requirements based on the timing capability information, as the service node after switching; or, determining a target service node that meets the timing service requirements as the service node after switching based on the timing capability information of the source service node and / or the timing capability information of the target service node.
[0021] In some embodiments, the source service node is a source RAN node, further comprising: in response to receiving a request from the first node for obtaining switching indication information and / or a target RAN node identification list, determining whether to switch the source RAN node to the target RAN node, or determining whether a signal value of the target RAN node is greater than a preset value, the target RAN node identification list including a node identification list or a cell identification list of the target RAN node; in response to switching the source RAN node to the target RAN node, or the signal value of the target RAN node being greater than a preset value, sending the switching indication information and / or the target RAN node identification list to the first node.
[0022] In some embodiments, it also includes: in response to receiving clock quality report control information from the first node, or the time synchronization status of the source RAN node changes, sending time synchronization assistance information to the target RAN node, the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node, and the target service node is the target RAN node.
[0023] In some embodiments, the source service node is a source RAN node, and the timing capability information includes at least one of the following: the main time source of the source RAN node, clock quality, synchronization performance, punctuality performance, node identification, cell identification list, and signal measurement report of the source RAN node and / or the target RAN node; the source service node is a source UPF node, and the timing capability information includes at least one of the following: the main time source of the source UPF node, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list, and supported DNAI list.
[0024] In a third aspect, the present application provides a method for supporting continuity of timing services, which is applied to a target service node. The method includes: sending timing capability information to a first node, so that the first node determines a target service node that meets the timing service requirements based on the timing capability information, as the service node after switching; or, the source service node determines the target service node that meets the timing service requirements as the service node after switching based on the timing capability information of the source service node and / or the timing capability information of the target service node.
[0025] In some embodiments, the target service node is a target RAN node, and further includes: sending a time synchronization status in response to receiving time synchronization assistance information, the source service node is a source RAN node, and the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node.
[0026] In some embodiments, the method further includes: receiving a time synchronization error budget from the first node, where the time synchronization error budget is determined by the first node based on the received time synchronization status and / or timing capability information of the target service node.
[0027] In some embodiments, the target service node is a target RAN node, and the timing capability information includes at least one of the following: the main time source of the target RAN node, clock quality, synchronization performance, punctuality performance, node identification, cell identification list, signal measurement report of the source RAN node and / or the target RAN node; the target service node is a target UPF node, and the timing capability information includes at least one of the following: the main time source of the target UPF node, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
[0028] In a fourth aspect, the present application provides a method for supporting continuity of timing services, which is applied to a second node, and the method includes: in response to a change in the DNAI or candidate DNAI of a source UPF node, sending the DNAI or candidate DNAI of a target UPF node to a first node, so that the first node determines to switch the terminal to a target UPF node that meets the timing service requirements based on the DNAI or candidate DNAI of the target UPF node.
[0029] In the fifth aspect, the present application provides a device that supports the continuity of timing services, which is applied to a first node. The device includes: a determination module, which is used to determine a target service node that meets the timing service requirements based on the service node type and target conditions currently serving the terminal, as the service node after switching; an indication module, which is used to indicate the information of the target service node.
[0030] In a sixth aspect, the present application provides a device for supporting the continuity of timing services, which is applied to a source service node. The device includes: a processing module for sending timing capability information to a first node, so that the first node determines a target service node that meets the timing service requirements based on the timing capability information, as the service node after switching; or, determines a target service node that meets the timing service requirements as the service node after switching based on the timing capability information of the source service node and / or the timing capability information of the target service node.
[0031] In the seventh aspect, the present application provides a device that supports the continuity of timing services, which is applied to a target service node. The device includes: a sending module, which is used to send timing capability information to a first node, so that the first node determines a target service node that meets the timing service requirements based on the timing capability information, as the service node after switching; or, the source service node determines the target service node that meets the timing service requirements as the service node after switching based on the timing capability information of the source service node and / or the timing capability information of the target service node.
[0032] In the eighth aspect, the present application provides a device for supporting the continuity of timing services, which is applied to a second node, and the device includes: a sending module, which is used to send the DNAI or candidate DNAI of the target UPF node to the first node in response to the change of the DNAI or candidate DNAI of the source UPF node, so that the first node determines to switch the terminal to the target UPF node that meets the timing service requirements according to the DNAI or candidate DNAI of the target UPF node.
[0033] In the ninth aspect, the present application provides a device supporting the continuity of timing services, including: a memory, a transceiver, and a processor; the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: based on the service node type and target conditions currently serving the terminal, determine the target service node that meets the timing service requirements as the service node after switching; indicate information about the target service node.
[0034] In some embodiments, when the source service node is a source RAN node, the target condition includes receiving at least one of the following switching information: timing capability information of the target RAN node, a node identification list of the target RAN node, a signal measurement report of the source RAN node and / or the target RAN node, a time synchronization error budget parameter and / or a clock quality acceptance standard parameter to be met by the target RAN node, and the time synchronization status of the source RAN node; when the source service node is a source UPF node, the target condition includes receiving at least one of the following switching information: timing capability information of the target UPF node, a data network access identifier DNAI or a candidate DNAI of the target UPF node, a time synchronization error budget parameter and a clock quality acceptance standard parameter to be met by the target UPF node, and the time synchronization status of the source UPF node.
[0035] In some embodiments, the target condition further includes: determining that the source service node does not meet the timing service requirements, the timing service requirements including time synchronization error budget and / or clock quality acceptance criteria.
[0036] In some embodiments, when the source service node is a source RAN node, the switching information is received in the following manner: in response to detecting a change in the timing capability information of the source RAN node, requesting the source RAN node to obtain switching indication information and / or a list of identifiers of a target RAN node; receiving switching indication information or a list of identifiers of a target RAN node from the source RAN node, the switching information including the switching indication information and / or the list of identifiers of the target RAN node, the switching indication information including the identifier information and / or signal measurement data of the target RAN node, and the list of identifiers of the target RAN node including a list of target RAN node identifiers or a list of cell identifiers.
[0037] In some embodiments, based on the service node type and target conditions currently serving the terminal, a target service node that meets the timing service requirements is determined as the service node after switching, including: determining the target RAN node based on the changed timing capability information of the source RAN node, as well as the switching indication information and / or the target RAN node identification list.
[0038] In some embodiments, when the source service node is a source RAN node and the target service node is a target RAN node, the switching information is received in the following manner: obtaining the timing service requirement and the time synchronization status of the source RAN node, the switching information includes the timing service requirement and the time synchronization status of the source RAN node; the timing service requirement includes at least one of the following: time synchronization error budget, clock quality detail level, clock quality acceptance criteria; the time synchronization status of the source RAN node includes at least one of the following: synchronization status, synchronization performance, clock quality and master time source of the source RAN node.
[0039] In some embodiments, whether the source service node meets the timing service requirement is determined in the following manner: whether the source RAN node meets the timing service requirement is determined based on the timing capability information of the source RAN node and the time synchronization status of the source RAN node.
[0040] In some embodiments, it also includes: receiving timing capability information from the source RAN node and the target RAN node, the timing capability information including at least one of the following: primary time source, clock quality, synchronization performance, punctuality performance, node identification, and cell identification list.
[0041] In some embodiments, when the source service node is a source UPF node and the target service node is a target UPF node, the switching information is received in the following manner: in response to a DNAI change of the source UPF node, a DNAI or a candidate DNAI of the target UPF node is received from a second node, and the switching information includes the DNAI or the candidate DNAI of the target UPF node.
[0042] In some embodiments, based on the service node type and target conditions currently serving the terminal, a target service node that meets the timing service requirements is determined as the service node after switching, including: determining the target UPF node based on the changed timing capability information of the source UPF node and the DNAI or candidate DNAI of the target UPF node.
[0043] In some embodiments, when the source service node is a source UPF node and the target service node is a target UPF node, the switching information is received in the following manner: obtaining the timing service requirements and the time synchronization status of the source UPF node, the switching information includes the timing service requirements and the time synchronization status of the source UPF node; the timing service requirements include at least one of the following: time synchronization error budget, clock quality detail level and clock quality acceptance criteria; the time synchronization status of the source UPF node includes at least one of the following: synchronization status, synchronization performance, clock quality and master time source of the source UPF node.
[0044] In some embodiments, whether the source service node meets the timing service requirements is determined in the following manner: based on the timing capability information of the source UPF node and the time synchronization status of the source UPF node, whether the source UPF node meets the timing service requirements is determined.
[0045] In some embodiments, it also includes: receiving timing capability information from the source UPF node and the target UPF node, the timing capability information including at least one of the following: main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
[0046] In some embodiments, after indicating the information of the target service node, it also includes: receiving the time synchronization status and / or timing capability information of the target service node; determining the time synchronization error budget of the target service node based on the time synchronization status and / or timing capability information of the target service node; and sending the time synchronization error budget to the target service node.
[0047] In the tenth aspect, the present application provides a device supporting the continuity of timing services, including: a memory, a transceiver, and a processor; the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: sending timing capability information to a first node, so that the first node determines a target service node that meets the timing service requirements based on the timing capability information as the service node after switching; or, based on the timing capability information of the source service node and / or the timing capability information of the target service node, determining the target service node that meets the timing service requirements as the service node after switching.
[0048] In some embodiments, the source service node is a source RAN node, further comprising: in response to receiving a request from the first node for obtaining switching indication information and / or a target RAN node identification list, determining whether to switch the source RAN node to the target RAN node, or determining whether a signal value of the target RAN node is greater than a preset value, the target RAN node identification list including a node identification list or a cell identification list of the target RAN node; in response to switching the source RAN node to the target RAN node, or the signal value of the target RAN node being greater than a preset value, sending the switching indication information and / or the target RAN node identification list to the first node.
[0049] In some embodiments, it also includes: in response to receiving clock quality report control information from the first node, or the time synchronization status of the source RAN node changes, sending time synchronization assistance information to the target RAN node, the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node, and the target service node is the target RAN node.
[0050] In some embodiments, the source service node is a source RAN node, and the timing capability information includes at least one of the following: the main time source of the source RAN node, clock quality, synchronization performance, punctuality performance, node identification, cell identification list, and signal measurement report of the source RAN node and / or the target RAN node; the source service node is a source UPF node, and the timing capability information includes at least one of the following: the main time source of the source UPF node, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list, and supported DNAI list.
[0051] In an eleventh aspect, the present application provides a device supporting continuity of timing services, comprising: a memory, a transceiver, and a processor; the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: sending timing capability information to a first node, so that the first node determines a target service node that meets the timing service requirements based on the timing capability information as the service node after switching; or, the source service node determines the target service node that meets the timing service requirements as the service node after switching based on the timing capability information of the source service node and / or the timing capability information of the target service node.
[0052] In some embodiments, the target service node is a target RAN node, and further includes: sending a time synchronization status in response to receiving time synchronization assistance information, the source service node is a source RAN node, and the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node.
[0053] In some embodiments, the method further includes: receiving a time synchronization error budget from the first node, where the time synchronization error budget is determined by the first node based on the received time synchronization status and / or timing capability information of the target service node.
[0054] In some embodiments, the target service node is a target RAN node, and the timing capability information includes at least one of the following: the main time source of the target RAN node, clock quality, synchronization performance, punctuality performance, node identification, cell identification list, signal measurement report of the source RAN node and / or the target RAN node; the target service node is a target UPF node, and the timing capability information includes at least one of the following: the main time source of the target UPF node, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
[0055] In the twelfth aspect, the present application provides a device supporting the continuity of timing services, including: a memory, a transceiver, and a processor; the memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: in response to a change in the DNAI or candidate DNAI of the source UPF node, sending the DNAI or candidate DNAI of the target UPF node to the first node, so that the first node determines to switch the terminal to the target UPF node that meets the timing service requirements based on the DNAI or candidate DNAI of the target UPF node.
[0056] In a thirteenth aspect, the present application provides a processor-readable storage medium, which stores a computer program, and the computer program is used to enable the processor to execute the above-mentioned method of supporting timing service continuity.
[0057] The present application provides a method, apparatus, device and storage medium for supporting the continuity of timing services, and the method includes: determining a target service node that meets the timing service requirements as the service node after switching based on the type and target conditions of the service node currently serving the terminal; indicating the information of the target service node. In the present application, in order to ensure the continuity of the timing service provided to the terminal, the first node can determine the target service node that meets the timing service requirements through the type and target conditions of the service node currently serving the terminal, and instruct the terminal to switch from the service node to the target service node, so that the continuity of the timing service for the terminal can be ensured. BRIEF DESCRIPTION OF THE DRAWINGS
[0058] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0059] Figure 1 A communication system based on the 3GPP Rel-17 standard provided in an embodiment of the present application supports a network architecture for time-sensitive communication and time synchronization services;
[0060] Figure 2 A flowchart of a method for supporting timing service continuity provided in an embodiment of the present application;
[0061] Figure 3 A flowchart of another method for supporting timing service continuity provided in an embodiment of the present application;
[0062] Figure 4 A flowchart of another method for supporting timing service continuity provided in an embodiment of the present application;
[0063] Figure 5 A flowchart of another method for supporting timing service continuity provided in an embodiment of the present application;
[0064] Figure 6 A schematic diagram of the structure of a device for supporting timing service continuity provided in an embodiment of the present application;
[0065] Figure 7 A schematic diagram of the structure of another device for supporting timing service continuity provided in an embodiment of the present application;
[0066] Figure 8 A schematic diagram of the structure of another device for supporting timing service continuity provided in an embodiment of the present application;
[0067] Fig. 9 A schematic diagram of the structure of another device for supporting timing service continuity provided in an embodiment of the present application;
[0068] Fig.10 A schematic diagram of the structure of a device supporting timing service continuity provided in an embodiment of the present application;
[0069] Fig.11 A schematic diagram of the structure of another device supporting timing service continuity provided in an embodiment of the present application;
[0070] Fig.12 A schematic diagram of the structure of another device supporting timing service continuity provided in an embodiment of the present application;
[0071] Fig.13 A schematic diagram of the structure of another device supporting timing service continuity provided in an embodiment of the present application.
[0072] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application for those skilled in the art by referring to specific embodiments. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative labor. DETAILED DESCRIPTION
[0073] In the embodiments of the present invention, the term "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent three situations: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.
[0074] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.
[0075] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0076] In the process of studying the timing service of the terminal, the inventors found that there are differences in the timing capabilities of the base station and UPF. Regarding the mobility of the UE, the 5G timing service does not support how to ensure the continuity of the timing service when the base station or UPF switches, resulting in clock switching; when the timing service demand requested by the AF cannot be met, there is no consideration of how to switch the base station or UPF and select a suitable clock to meet the timing service demand requested by the AF to ensure the continuity of the timing service. Therefore, the embodiments of the present application provide methods, devices, equipment and storage media that support the continuity of timing services, which can be used to ensure the continuity of timing services.
[0077] In this application, based on the 3GPP Rel-17 standard, the communication system supports TSC (Time Sensitive Communication) and time synchronization services when TSN (including TSN CUC, TSN CNC) is not deployed, and the network architecture can be as follows: Figure 1 shown.
[0078] Figure 1 A network architecture for supporting time-sensitive communication and time synchronization services for a communication system based on the 3GPP Rel-17 standard provided in an embodiment of the present application. The network architecture may include UE, (radio) access network ((R)AN), user plane function (User Plan Function, referred to as UPF) node, access and mobility management function (Access and Mobility Management Function, referred to as AMF) node, session management function (Session Management Function, referred to as SMF) node, unified data management (Unified Data Management, referred to as UDM) node, policy control function (Policy Control Function, referred to as PCF) node, time-sensitive communication and time synchronization function (Time Sensitive Communication and Time Synchronization function, referred to as TSCTSF) node, network exposure function (Network Exposure Function, referred to as NEF) node, application function (Application Function, referred to as AF) node, data network (Data Network, referred to as DN) node.
[0079] Among them, on the terminal side, UE supports terminal TSN converter (DS-TT) and UPF supports network TSN converter (NW-TT).
[0080] Among them, UE is connected with (R)AN and AMF, and UE exchanges information with AMF through N1; (R)AN is connected with AMF and UPF, and (R)AN exchanges information with AMF through N2, and (R)AN exchanges information with UPF through N3; AMF is connected with UDM and SMF, and AMF exchanges information with UDM through N8, and AMF exchanges information with SMF through N11; UPF is connected with SMF and DN, and UPF exchanges information with SMF through N4, and UPF exchanges information with DN through U-plane, and UPF exchanges internal information through N9; UDM exchanges information with SMF, T SCTSF is connected to NEF, UDM exchanges information with SMF through N10, UDM exchanges information with TSCTSF through N87, and UDM exchanges information with NEF through N52; SMF is also connected to PCF, and SMF exchanges information with PCF through N7; TSCTSF is also connected to PCF and NEF, TSCTSF exchanges information with PCF through N84, and TSCTSF exchanges information with NEF through N85; PCF is also connected to NEF, and PCF exchanges information with NEF through N30; NEF is also connected to AF, and NEF exchanges information with AF through N33.
[0081] Among them, the AMF node is used for registration, connection management, etc.
[0082] UPF nodes are used for external protocol data unit (PDU) session nodes interconnected with data networks, message routing and forwarding. PDU session nodes are information exchanged between peer layers of the protocol layer.
[0083] SMF nodes are used for session establishment and deletion, user plane selection and control, UE IP allocation, etc.
[0084] AF nodes are used to interact with the 3GPP core network to provide services. Based on the operator's deployment, trusted AFs can interact directly with related network functions (NFs), while untrusted AFs cannot interact directly with NFs, but should use an open framework through NEFs. TSN AFs are AFs that interact with the control plane of the communication system on behalf of the TSN domain (including CUC / CNC).
[0085] The PCF node is used to support a unified policy framework to manage network behavior and provide policy rules for the control plane NF to execute.
[0086] The UDM node is used to store UE information, such as subscription information and information about established PDU sessions.
[0087] The NEF node is used to provide functions related to securely exposing the services and capabilities provided by the 3GPP network to external networks.
[0088] The UDR node is used for storage of contract data and retrieval of contract data by UDM FE, storage of policy information and retrieval of policy information by PCF.
[0089] The TSCTSF node contains TSC and time synchronization service logic, and can control DS-TT(s) and NW-TT to form (g)PTPinstance.
[0090] Therefore, a new core network element TSCTSF can be introduced in this application. TSCTSF contains TSC and time synchronization service logic, and can control DS-TT(s) and NW-TT to form (g)PTP instance, and UPF can support one or more NW-TT. When the timing service requirements requested by UE or AF cannot be met, TSCTSF can select suitable base stations and UPFs based on the timing service capabilities of the base stations and UPFs, the timing service requirements requested by AF, UE mobility and other conditions, and enhance the switching process of the base stations and UPFs to ensure the continuity of the timing service.
[0091] Among them, the method and the device are based on the same application concept. Since the method and the device solve the problem in a similar principle, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.
[0092] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) system, a general packet radio service (GPRS) system, a long term evolution (LTE) system, a frequency division duplex (FDD) system, a time division duplex (TDD) system, a long term evolution advanced (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new radio (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include core network parts, such as the Evolved Packet System (EPS), 5G System (5GS), etc.
[0093] The terminal device involved in the embodiment of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with a wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (User Equipment, referred to as UE). The wireless terminal device can communicate with one or more core networks (Core Network, referred to as CN) via a radio access network (Radio Access Network, referred to as RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it can be a portable, pocket, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a wireless access network. For example, Personal Communication Service (PCS) phone, cordless phone, Session Initiated Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA) and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, and a user device, but is not limited in the embodiments of the present application.
[0094] The network device involved in the embodiments of the present application may be a base station, which may include multiple cells providing services for terminal devices. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or other names. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, and serve as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (eNB or e-NodeB) in the long-term evolution (LTE) system, or a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., which is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be arranged geographically separately.
[0095] Network devices and terminal devices can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the form and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO or massive-MIMO, or it can be diversity transmission, precoding transmission or beamforming transmission, etc.
[0096] The technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below in conjunction with the accompanying drawings.
[0097] In some embodiments, a method for supporting timing service continuity is provided, which is applied to a first node, and the first node may be a TSCTSF node.
[0098] Figure 2 A flow chart of a method for supporting timing service continuity provided in an embodiment of the present application is shown as follows: Figure 2 As shown, the method mainly includes the following steps:
[0099] S201: Based on the type of the service node currently serving the terminal and the target condition, determine a target service node that meets the timing service requirement as the service node after switching.
[0100] In this step, the terminal may be a user equipment, and the service node currently serving the terminal may be a source service node. Types of source service nodes may include source RAN nodes and source UPF nodes, and types of target service nodes may include target RAN nodes and target UPF nodes.
[0101] Specifically, in order to ensure the continuity of the timing service provided to the terminal, the first node can determine the target service node that meets the timing service requirements based on the service node type and target conditions currently serving the terminal. The target service node can be the service node that provides timing service to the terminal at the next moment.
[0102] S202: Indicate the information of the target service node.
[0103] In this step, after determining the target service node, the first node can indicate the information of the target service node to the source service node or the second node, so that the source service node or the second node can determine the target service node, thereby ensuring that the timing service continues to be provided to the terminal through the target service node at the next moment, thereby achieving the continuity of the terminal's timing service.
[0104] Optionally, the 5G clock can be used as the master clock. Due to the mobility of the UE or the inability of the source RAN node to meet the timing service requirements, it is necessary to switch the source RAN node to the target RAN node, thereby switching the terminal's clock from the source RAN node's clock to the target RAN node's clock.
[0105] Optionally, 5Gclock or (g)PTP GM can be used as the master clock. Due to the mobility of the UE or the inability of the source UPF node to meet the timing service requirements, it is necessary to switch the source UP node to the target UPF node, thereby switching the terminal's clock from the source UPF node's clock to the target UPF node's clock.
[0106] The method for supporting the continuity of timing services provided by the embodiment of the present application, in order to ensure the continuity of the timing services provided to the terminal, the first node can determine the target service node that meets the timing service requirements as the switched service node through the service node type and target conditions currently serving the terminal, and indicate the information of the target service node so that the source service node can determine the target service node, thereby ensuring the continuity of the timing services for the terminal.
[0107] In some embodiments, when the source service node is a source RAN node, the target condition includes receiving at least one of the following switching information: timing capability information of the target RAN node, a node identification list of the target RAN node, a signal measurement report of the source RAN node and / or the target RAN node, a time synchronization error budget parameter and / or a clock quality acceptance standard parameter to be met by the target RAN node, and the time synchronization status of the source RAN node; when the source service node is a source UPF node, the target condition includes receiving at least one of the following switching information: timing capability information of the target UPF node, a data network access identifier DNAI or a candidate DNAI of the target UPF node, a time synchronization error budget parameter and a clock quality acceptance standard parameter to be met by the target UPF node, and the time synchronization status of the source UPF node.
[0108] Specifically, the source service node can be a source RAN node or a source UPF node. When determining the target service node, different types of source service nodes require different target conditions. Therefore, when determining the target service node, it can be determined first whether to switch the RAN node or the UPF node.
[0109] Optionally, when performing RAN node switching, if the source RAN node needs to be switched to the target RAN node due to UE mobility, the target condition includes receiving at least one of the following switching information: timing capability information of the target RAN node, a node identification list of the target RAN node, and a signal measurement report of the source RAN node and / or the target RAN node; if the source RAN node needs to be switched to the target RAN node because the source RAN node cannot meet the timing service requirements, the target condition includes receiving at least one of the following switching information: timing capability information of the target RAN node, a time synchronization error budget and / or clock quality acceptance criteria to be met by the target RAN node, and the time synchronization status of the source RAN node.
[0110] Optionally, when performing UPF node switching, if the source UPF node needs to be switched to the target UPF node due to UE mobility, the target condition includes receiving at least one of the following switching information: the timing capability information of the target UPF node, the data network access identifier DNAI or candidate DNAI of the target UPF node; if the source UPF node needs to be switched to the target UPF node because the source UPF node cannot meet the timing service requirements, the target condition includes receiving at least one of the following switching information: the timing capability information of the target UPF node, the time synchronization error budget and / or clock quality acceptance criteria to be met by the target UPF node, and the time synchronization status of the source UPF node.
[0111] Optionally, the timing service requirement may include a time synchronization error budget and / or clock quality acceptance criteria, and may also include a clock quality detail level. The timing service requirement may be used to request activation or update of a 5G access stratum time distribution service.
[0112] Optionally, by selecting a suitable target service node, the source service node can be switched to a suitable target service node, so that when the UE moves or the timing service demand requested by the AF cannot be met, the continuity of the timing service to the terminal can still be guaranteed.
[0113] In some embodiments, the target condition further includes: determining that the source service node does not meet the timing service requirements, the timing service requirements including time synchronization error budget and / or clock quality acceptance criteria.
[0114] Specifically, in addition to determining the target service node upon receiving the switching information, the first node can also determine whether the source service node meets the timing service requirements. If the source service node meets the timing service requirements, it can be determined that the source service node can continue to provide timing services for the terminal, so there is no need to switch the source service node to the target service node. If the source service node does not meet the timing service requirements, it can be determined that the source service node cannot continue to provide timing services for the terminal. Therefore, it is necessary to switch the source service node to the target service node, so that when the UE moves or the timing service requirements requested by the AF cannot be met, the continuity of the timing service for the terminal can still be guaranteed.
[0115] In some embodiments, when the source service node is a source RAN node, the switching information is received in the following manner: in response to detecting a change in the timing capability information of the source RAN node, requesting the source RAN node to obtain switching indication information and / or a list of identifiers of a target RAN node; receiving switching indication information or a list of identifiers of a target RAN node from the source RAN node, the switching information including the switching indication information and / or the list of identifiers of the target RAN node, the switching indication information including the identifier information and / or signal measurement data of the target RAN node, and the list of identifiers of the target RAN node including a list of target RAN node identifiers or a list of cell identifiers.
[0116] Specifically, the first node may subscribe to the notification of the change of the timing capability information of the source RAN node. If the timing capability information of the source RAN node changes, the first node may request the source RAN node or UE to obtain the switching indication information and / or the identification list of the target RAN node. When the source RAN node or UE determines that the RAN node switching is required or the signal value of the target RAN node exceeds the preset value, the switching indication information and / or the identification list of the target RAN node may be sent to the first node. The switching information received by the first node may include the switching indication information and / or the identification list of the target RAN node, that is, the switching information may include the identification information and / or the signal measurement report of the target RAN node to be switched to, and the node identifier list (node identifier list) or cell identifier list (Cell ID list) of the target RAN node. Among them, the switching indication information may include the identification information and / or the signal measurement report of the target RAN node to be switched to, and the identification list of the target RAN node may include the node identifier list or the cell identifier list of the target RAN node.
[0117] Optionally, when determining the handover indication information and / or the identifier list of the target RAN node, the source RAN node or the UE may select an optional target RAN node or cell according to the signal strength of the target RAN node.
[0118] In an optional implementation, if the switching indication information includes a signal measurement report, the first node may periodically report a notification of subscribing to the signal measurement report to the source RAN node, or actively send a request message to the source RAN node to request a real-time signal measurement report.
[0119] Optionally, by receiving the switching information, the first node can determine the service node of the terminal that needs to be switched, thereby selecting a suitable target service node, thereby switching the source service node to the selected suitable target service node, so that when the UE moves, the continuity of the timing service to the terminal can still be guaranteed.
[0120] In some embodiments, based on the service node type and target conditions currently serving the terminal, a target service node that meets the timing service requirements is determined as the service node after switching, including: determining the target RAN node based on the changed timing capability information of the source RAN node, as well as the switching indication information and / or the target RAN node identification list.
[0121] Specifically, the first node may receive timing capability information from the source RAN node, and the first node may subscribe to whether the timing capability information of the source RAN node has changed. If the changed timing capability information of the source RAN node is received, it may be determined that the timing capability information of the source RAN node has changed, and thus the most suitable target RAN node is determined from a plurality of selectable target RAN nodes according to the switching indication information and / or the identification list of the target RAN node received from the source RAN node, or the switching indication information and / or the identification list of the target RAN node received from the UE, to implement RAN node switching. In this way, when the UE moves, the continuity of the timing service for the terminal can still be guaranteed.
[0122] Optionally, when determining the target RAN node, the first node may determine a node identifier (node identifier) of the target RAN node, or determine a target cell identifier (Cell-ID) corresponding to the target RAN node.
[0123] Optionally, the first node may send the node identifier of the target RAN node to the source RAN node, or send the target cell identifier corresponding to the target RAN node to the source RAN node. Optionally, the first node may send the node identifier or target cell identifier of the target RAN node to the AMF node through the Namf_Communication_NonUeN2MessageTransfer service operation, and then the AMF node sends the node identifier or target cell identifier of the target RAN node to the source RAN node through the N2 message, so that the source RAN node can determine the target RAN node according to the node identifier or target cell identifier of the target RAN node.
[0124] In some embodiments, when the source service node is a source RAN node, the switching information is received in the following manner: obtaining the timing service requirement and the time synchronization status of the source RAN node, the switching information includes the timing service requirement and the time synchronization status of the source RAN node; the timing service requirement includes at least one of the following: time synchronization error budget, clock quality detail level, clock quality acceptance criteria; the time synchronization status of the source RAN node includes at least one of the following: synchronization status, synchronization performance, clock quality and master time source of the source RAN node.
[0125] Specifically, the timing service requirement can be sent by the AF node by calling the Nnef_ASTI_Create service or the Nnef_ASTI_Update request service. The timing service requirement can be used to request activation or update of the 5G accessstratum time distribution service. The timing service requirement can include at least one of the time synchronization error budget, the clock quality acceptance criteria, and the clock quality detail level.
[0126] Optionally, the first node may also subscribe to the notification of the change of the time synchronization status from the source RAN node. When the source RAN node detects a change in the time synchronization status (e.g., degradation, failure, promotion, etc.), the time synchronization status may be sent to the first node, and the time synchronization status may include at least one of the synchronization status, synchronization performance, clock quality and primary time source of the source RAN node. The first node may subscribe to the notification of the change of the time synchronization status from the source RAN node through an AMF node or an Operation Administration and Maintenance (OAM) node.
[0127] Optionally, by receiving the switching information, the first node can determine the service node of the terminal that needs to be switched, and thus select a suitable target service node to switch the source service node to the selected suitable target service node. In this way, when the timing service demand requested by the AF cannot be met, the continuity of the timing service to the terminal can still be guaranteed.
[0128] In some embodiments, whether the source service node meets the timing service requirement is determined in the following manner: whether the source RAN node meets the timing service requirement is determined based on the timing capability information of the source RAN node and the time synchronization status of the source RAN node.
[0129] Specifically, the first node can receive the timing capability information from the source RAN node, and after receiving the timing service requirement, determine whether the current source RAN node meets the timing service requirement based on the timing capability information of the source RAN node and the time synchronization status of the source RAN node, that is, determine whether the current source RAN node meets the time synchronization error budget or clock quality acceptance standard in the timing service requirement. If the source RAN node cannot meet the timing service requirement, the first node determines the most suitable target RAN node from multiple selectable target RAN nodes to implement RAN node switching. In this way, when the timing service requirement requested by the AF cannot be met, the continuity of the timing service to the terminal can still be guaranteed.
[0130] Optionally, when determining the target RAN node, the first node may determine a node identifier of the target RAN node, or determine a target cell identifier corresponding to the target RAN node.
[0131] Optionally, the first node may send the node identifier of the target RAN node to the source RAN node, or send the target cell identifier corresponding to the target RAN node to the source RAN node. The first node may send the node identifier or target cell identifier of the target RAN node to the AMF node through the Namf_Communication_NonUeN2MessageTransfer service operation, and then the AMF node sends the node identifier or target cell identifier of the target RAN node to the source RAN node through the N2 message, so that the source RAN node can determine the target RAN node according to the node identifier or target cell identifier of the target RAN node.
[0132] In some embodiments, it also includes: receiving timing capability information from the source RAN node and the target RAN node, the timing capability information including at least one of the following: primary time source, clock quality, synchronization performance, punctuality performance, node identification, and cell identification list.
[0133] Specifically, during the PDU session establishment process, the first node may receive timing capability information from the source RAN node and the target RAN node, and the timing capability information may include at least one of a parent time source (for example, "Synchronous Ethernet SyncE", "Precision Time Protocol PTP", "Global Navigation Satellite System GNSS", "atomic clock", "terrestrial radio", "serial time code", "Network Time Protocol NTP", "hand set", etc.), clock quality (for example, clock accuracy), synchronization performance (Synchronization performance) (for example, Traceable to GNSS), holdover performance (holdover), node identifier (node identifier), and cell ID list (Cell ID list).
[0134] Optionally, the source RAN node and the target RAN node can send their timing capability information to the AMF node through the N2 message, and then the AMF node sends the timing capability information to the first node through the Namf_Communication_NonUeN2MessageTransfer service operation, or the source RAN node can send its timing capability information to the first node through the OAM node. Through the timing capability information of the source RAN node and the target RAN node, the first node can determine the service node to which the terminal needs to be switched, and thus determine the target RAN node that meets the timing service requirements based on the timing capability information of the source RAN node and the target RAN node. In this way, when the timing service requirements of the UE mobile or AF request cannot be met, the continuity of the timing service for the terminal can still be guaranteed.
[0135] In some embodiments, when the source service node is a source UPF node, the switching information is received in the following manner: in response to a DNAI change of the source UPF node, a DNAI or a candidate DNAI of a target UPF node is received from a second node, and the switching information includes the DNAI or the candidate DNAI of the target UPF node.
[0136] Specifically, the second node may be an SMF node. The first node may subscribe to the second node for notification of events of DNAI changes of the source UPF node or candidate DNAI(s) changes through the Nsmf_EventExposure_Suscribe service operation. When the event subscribed by the first node to the second node occurs, the second node may send the DNAI or candidate DNAI(s) of the target UPF node (Candidate DNAI(s) for the PDU Session) to the first node through the Nsmf_EventExposure_Notify service operation, that is, the switching information may include the DNAI or candidate DNAI of the target UPF node.
[0137] Optionally, by receiving the switching information, the first node can determine the service node of the terminal that needs to be switched, thereby selecting a suitable target service node to switch the source service node to the selected suitable target service node, so that when the UE moves, the continuity of the timing service to the terminal can still be guaranteed.
[0138] In some embodiments, based on the service node type and target conditions currently serving the terminal, a target service node that meets the timing service requirements is determined as the service node after switching, including: determining the target UPF node based on the changed timing capability information of the source UPF node and the DNAI or candidate DNAI of the target UPF node.
[0139] Specifically, the first node can receive the timing capability information from the source UPF node, and the first node can subscribe to the second node whether the timing capability information of the source UPF node has changed. If the changed timing capability information of the source UPF node is received, it can be determined that the timing capability information of the source UPF node has changed, and then the most suitable target UPF node is determined among multiple selectable target UPF nodes according to the DNAI or candidate DNAI of the target UPF node received from the second node, so as to realize UPF node switching. In this way, when the UE moves, the continuity of the timing service for the terminal can still be guaranteed.
[0140] Optionally, when determining the target UPF node, the first node may determine the identification information (identifier) of the target UPF node.
[0141] Optionally, the first node may send a switching request message including identification information of the target UPF node to the second node, so that the second node may select the most suitable target UPF node (PSA UPF) from a plurality of selectable target UPF nodes according to the received switching request message.
[0142] Optionally, the second node may perform the switching of the UPF node. When performing the switching of the UPF node, the second node may simultaneously send the DNAI or candidate DNAI of the target UPF node to the AF node (eg, TSN AF) so that the AF node may subsequently configure PTP instances to the target UPF node.
[0143] In some embodiments, when the source service node is a source UPF node, the switching information is received in the following manner: obtaining the timing service requirements and the time synchronization status of the source UPF node, the switching information includes the timing service requirements and the time synchronization status of the source UPF node; the timing service requirements include at least one of the following: time synchronization error budget, clock quality detail level and clock quality acceptance criteria; the time synchronization status of the source UPF node includes at least one of the following: synchronization status, synchronization performance, clock quality and master time source of the source UPF node.
[0144] Specifically, the timing service requirement can be sent by the AF node. For (g)PTP, the AF node can send the timing service requirement by calling Nnef_TimeSynchronization_ConfigCreate or Nnef_TimeSynchronization_ConfigUpdate request service; for 5G access stratum time distribution, the AF node can call Nnef_ASTI_Create or Nnef_ASTI_Update request service to send the timing service requirement. The timing service requirement may include at least one of the time synchronization error budget, clock quality acceptance criteria, and clock quality detail level.
[0145] Optionally, the first node may also subscribe to notifications of changes in time synchronization status from the source UPF node. When the source UPF node detects a change in the time synchronization status (e.g., degradation, failure, promotion, etc.), it may send a time synchronization status to the first node, and the time synchronization status may include at least one of the synchronization status, synchronization performance, clock quality, and primary time source. The first node may subscribe to notifications of changes in time synchronization status from the source UPF node through a user plane node management information container (Userplane node Management Information Container, referred to as UMIC) or an OAM node.
[0146] Optionally, by receiving the switching information, the first node can determine the service node of the terminal that needs to be switched, and thus select a suitable target service node to switch the source service node to the selected suitable target service node. In this way, when the timing service demand requested by the AF cannot be met, the continuity of the timing service to the terminal can still be guaranteed.
[0147] In some embodiments, whether the source service node meets the timing service requirements is determined in the following manner: based on the timing capability information of the source UPF node and the time synchronization status of the source UPF node, whether the source UPF node meets the timing service requirements is determined.
[0148] Specifically, the first node can receive the timing capability information from the source UPF node, and after receiving the timing service demand, determine whether the current source UPF node meets the timing service demand based on the timing capability information of the source UPF node and the time synchronization status of the source UPF node, that is, determine whether the current source UPF node meets the time synchronization error budget or clock quality acceptance criteria in the timing service demand. If the source UPF node cannot meet the timing service demand, the first node determines the most suitable target UPF node from a plurality of selectable target UPF nodes to implement UPF node switching. In this way, when the timing service demand requested by the AF cannot be met, the continuity of the timing service to the terminal can still be guaranteed.
[0149] Optionally, when determining the target UPF node, the first node may determine identification information of the target UPF node.
[0150] Optionally, the first node may send a switching request message including identification information of the target UPF node to the second node, so that the second node may select the most suitable target UPF node (PSA UPF) from a plurality of selectable target UPF nodes according to the received switching request message.
[0151] In some embodiments, it also includes: receiving timing capability information from the source UPF node and the target UPF node, the timing capability information including at least one of the following: main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
[0152] Specifically, during the PDU session establishment process, the first node can receive timing capability information from the source UPF node and the target UPF node. The timing capability information may include the main time source (for example, "Synchronous Ethernet", "Precision Time Protocol", "Global Navigation Satellite System", "Atomic Clock", "Ground Radio", "Serial Time Code", "Network Time Protocol", "Handheld Device", etc.), clock quality (for example, clock accuracy), synchronization performance (for example, Traceable to GNSS), timekeeping performance, UPF node identification, NW-TT port number list, supported time domain list, and at least one item in the supported DNAI list.
[0153] Optionally, the source UPF node and the target UPF node can send their timing capability information to the first node through the UMIC or OAM node. Through the timing capability information of the source UPF node and the target UPF node, the first node can determine the service node of the terminal to be switched, thereby determining the target UPF node that meets the timing service requirements based on the timing capability information of the source UPF node and the target UPF node, so that when the timing service requirements of the UE mobile or AF request cannot be met, the continuity of the timing service for the terminal can still be guaranteed.
[0154] In some embodiments, after indicating the information of the target service node, it also includes: receiving the time synchronization status and / or timing capability information of the target service node; determining the time synchronization error budget of the target service node based on the time synchronization status and / or timing capability information of the target service node; and sending the time synchronization error budget to the target service node.
[0155] Specifically, after determining the information of the target service node, the first node can also redetermine the time synchronization error budget of the Uu interface according to the time synchronization status and / or timing capability information of the target service node when the time synchronization status or timing capability information of the target service node changes, and optionally send a new time synchronization error budget of the Uu interface to the target service node to enhance the switching process from the source service node to the target service node, thereby ensuring the continuity of the timing service to the terminal.
[0156] Optionally, if the service node is a source RAN node and the target service node is a target RAN node, the first node may provide clock quality reporting control information to the source RAN node through the AMF node, or subscribe to event notifications of time synchronization state changes to the source RAN node. After receiving the clock quality reporting control information or detecting a change in the time synchronization state, the source RAN node may include the clock quality reporting control information and / or subscription information of the time synchronization state change in the time synchronization assistance information (Time Synchronisation Assistance Information) and send it to the target RAN node. The target RAN node sends the current time synchronization state of the target RAN node to the AMF node based on the subscription information of the time synchronization state change received from the source RAN node, and the AMF node sends the current time synchronization state of the target RAN node to the first node. The first node can recalculate the Uu time synchronization error budget based on the time synchronization state and / or timing capability information of the target RAN node.
[0157] The clock quality report control information may include clock quality acceptance criteria and clock quality detail level. The time synchronization assistance information may also include the 5G access stratum time distribution indication and Uu time synchronization error budget.
[0158] Optionally, for NG-based handover (UE switches from a source NG-RAN node to a target NG-RAN node), the AMF node may send time synchronization assistance information (including clock quality report control information and subscription information of time synchronization status changes, etc.) to the target RAN node via the Next Generation Application Protocol (NGAP, used to send a HANDOVER REQUEST message).
[0159] Optionally, for Xn-based handover (UE switching from a source gNB node to a target gNB node via Xn), the source RAN node may send time synchronization assistance information (including clock quality report control information and subscription information of time synchronization status changes, etc.) to the target RAN node via the Xn Application Protocol (XnAP, used to send a handover request message).
[0160] Among them, the AMF node can also actively request the current time synchronization status of the target RAN node from the target RAN node. If the AMF node also needs to be switched during the RAN node switching process, the source AMF node can send the current time synchronization status of the target RAN node to the target AMF node, and the target AMF node sends the current time synchronization status of the target RAN node to the first node.
[0161] Optionally, if the source service node is a source UPF node and the target service node is a target UPF node, the first node may subscribe to notifications of time synchronization status changes (e.g., degradation / failure / promotion) of the target UPF node through the UMIC or OAM node. When the target UPF node detects changes in the time synchronization status, it sends the current time synchronization status to the first node.
[0162] Optionally, the TSN AF node or the first node may configure PTP instances to the target UPF node via UMIC.
[0163] In some embodiments, a method for supporting timing service continuity is provided, which is applied to a source service node, which may be a source RAN node or a source UPF node.
[0164] Figure 3 A flowchart of another method for supporting timing service continuity provided in an embodiment of the present application is shown as follows: Figure 3 As shown, the method mainly includes the following steps:
[0165] S301: Send timing capability information to the first node, so that the first node determines a target service node that meets the timing service requirements as the service node after switching according to the timing capability information; or, determines a target service node that meets the timing service requirements as the service node after switching according to the timing capability information of the source service node and / or the timing capability information of the target service node.
[0166] Specifically, during the PDU session establishment process, the source service node may send the timing capability information to the first node.
[0167] Optionally, the source RAN node may send its timing capability information to the AMF node through the N2 message, and the AMF node then sends the timing capability information to the first node through the Namf_Communication_NonUeN2MessageTransfer service operation, or the source RAN node may send its timing capability information to the first node through the OAM node, and the source UPF node may send its timing capability information to the first node through the UMIC or OAM node. Through the timing capability information of the source RAN node, the first node can determine the service node of the terminal to be switched, thereby determining the target RAN node that meets the timing service requirements based on the timing capability information of the source RAN node, and through the timing capability information of the source UPF node, the first node can determine the service node of the terminal to be switched, thereby determining the target UPF node that meets the timing service requirements based on the timing capability information of the source UPF node, so that when the timing service requirements of the UE mobile or AF request cannot be met, the continuity of the timing service for the terminal can still be guaranteed.
[0168] Optionally, the source service node may also determine the target service node through the timing capability information of the target service node when its own timing capability information changes.
[0169] Optionally, when the source service node is a source RAN node, the timing capability information of the source service node may further include a signal measurement report of the source RAN node, and the timing capability information of the target service node may further include a signal measurement report of the target RAN node. In this way, the source RAN node can determine the target RAN node when its signal value is less than a certain value and cannot provide timing service to the terminal, and the signal value of the target RAN node is greater than a preset value, so as to ensure that the timing service can continue to be provided to the terminal through the target RAN node, thereby ensuring the continuity of the timing service to the terminal.
[0170] In some embodiments, the source service node is a source RAN node, further comprising: in response to receiving a request from the first node for obtaining switching indication information and / or a target RAN node identification list, determining whether to switch the source RAN node to the target RAN node, or determining whether a signal value of the target RAN node is greater than a preset value, the target RAN node identification list including a node identification list or a cell identification list of the target RAN node; in response to switching the source RAN node to the target RAN node, or the signal value of the target RAN node being greater than a preset value, sending the switching indication information and / or the target RAN node identification list to the first node.
[0171] Specifically, the first node may subscribe to the notification of the change of the timing capability information of the source RAN node. If the timing capability information of the source RAN node changes, the first node may request the source RAN node or UE to obtain the switching indication information and / or the identification list of the target RAN node. After receiving the request for obtaining the switching indication information and / or the identification list of the target RAN node from the first node, the source RAN node or UE may send the switching indication information and / or the identification list of the target RAN node to the first node if it is determined that the RAN node switching is required or the signal value of the target RAN node exceeds the preset value. The switching information received by the first node may include the switching indication information and / or the identification list of the target RAN node, that is, the switching information may include the identification information and / or the signal measurement report of the target RAN node to be switched to, and the node identifier list (node identifier list) or cell identifier list (Cell ID list) of the target RAN node. Among them, the switching indication information may include the identification information and / or the signal measurement report of the target RAN node to be switched to, and the identification list of the target RAN node may include the node identifier list or the cell identifier list of the target RAN node.
[0172] Optionally, when determining the handover indication information and / or the identifier list of the target RAN node, the source RAN node or the UE may select an optional target RAN node or cell according to the signal strength of the target RAN node.
[0173] In an optional implementation, if the switching indication information includes a signal measurement report, the first node may periodically report a notification of subscribing to the signal measurement report to the source RAN node, or actively send a request message to the source RAN node to request a real-time signal measurement report.
[0174] Optionally, by receiving the switching information, the first node can determine the service node of the terminal that needs to be switched, thereby selecting a suitable target service node, thereby switching the source service node to the selected suitable target service node, so that when the UE moves, the continuity of the timing service to the terminal can still be guaranteed.
[0175] In some embodiments, it also includes: in response to receiving clock quality report control information from the first node, or the time synchronization status of the source RAN node changes, sending time synchronization assistance information to the target RAN node, the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node, and the target service node is the target RAN node.
[0176] Specifically, after determining the target service node, the first node can also redetermine the time synchronization error budget of the Uu interface according to the time synchronization status and / or timing capability information of the target service node when the time synchronization status of the target service node changes or the timing capability information changes, and optionally send a new time synchronization error budget of the Uu interface to the target service node to enhance the switching process from the source service node to the target service node, thereby ensuring the continuity of the timing service to the terminal.
[0177] Optionally, the first node may provide clock quality report control information to the source RAN node through the AMF node, or subscribe to event notifications of time synchronization state changes to the source RAN node. After receiving the clock quality report control information, or detecting a change in the time synchronization state, the source RAN node may include the clock quality report control information and / or subscription information of the time synchronization state change in the time synchronization auxiliary information and send it to the target RAN node. The target RAN node sends the current time synchronization state of the target RAN node to the AMF node based on the subscription information of the time synchronization state change received from the source RAN node, and the AMF node sends the current time synchronization state of the target RAN node to the first node. The first node can recalculate the Uu time synchronization error budget based on the time synchronization state and / or timing capability information of the target RAN node.
[0178] Among them, the time synchronization assistance information may also include the 5G access stratum time distribution indication and the Uu time synchronization error budget.
[0179] Optionally, for NG-based handover (UE switches from a source NG-RAN node to a target NG-RAN node), the AMF node may send time synchronization assistance information (including clock quality report control information and subscription information of time synchronization status changes, etc.) to the target RAN node via the Next Generation Application Protocol (NGAP, used to send a HANDOVER REQUEST message).
[0180] Optionally, for Xn-based handover (UE switching from a source gNB node to a target gNB node via Xn), the source RAN node may send time synchronization assistance information (including clock quality report control information and subscription information of time synchronization status changes, etc.) to the target RAN node via the Xn Application Protocol (XnAP, used to send a handover request message).
[0181] Among them, the AMF node can also actively request the current time synchronization status of the target RAN node from the target RAN node. If the AMF node also needs to be switched during the RAN node switching process, the source AMF node can send the current time synchronization status of the target RAN node to the target AMF node, and the target AMF node sends the current time synchronization status of the target RAN node to the first node.
[0182] In some embodiments, the source service node is a source RAN node, and the timing capability information includes at least one of the following: the main time source of the source RAN node, clock quality, synchronization performance, punctuality performance, node identification, cell identification list, and signal measurement report of the source RAN node and / or the target RAN node; the source service node is a source UPF node, and the timing capability information includes at least one of the following: the main time source of the source UPF node, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list, and supported DNAI list.
[0183] Specifically, the timing capability information of the source RAN node may include at least one of the primary time source of the source RAN node (e.g., "Synchronous Ethernet", "Precision Time Protocol", "Global Navigation Satellite System", "Atomic Clock", "Terrestrial Radio", "Serial Time Code", "Network Time Protocol", "Handheld Device", etc.), clock quality (e.g., clock accuracy), synchronization performance (e.g., Traceable to GNSS), timekeeping performance, node identification, cell identification list, and signal measurement reports of the source RAN node and / or the target RAN node. The timing capability information of the source UPF node may include at least one of the primary time source of the source UPF node (e.g., "Synchronous Ethernet", "Precision Time Protocol", "Global Navigation Satellite System", "Atomic Clock", "Terrestrial Radio", "Serial Time Code", "Network Time Protocol", "Handheld Device", etc.), clock quality (e.g., clock accuracy), synchronization performance (e.g., Traceable to GNSS), timekeeping performance, UPF node identification, NW-TT port number list, supported time domain list, and supported DNAI list.
[0184] Optionally, through the timing capability information of the source RAN node, the first node can determine the service node of the terminal to be switched, thereby determining the target RAN node that meets the timing service requirements according to the timing capability information of the source RAN node; and through the timing capability information of the source UPF node, the first node can determine the service node of the terminal to be switched, thereby determining the target UPF node that meets the timing service requirements according to the timing capability information of the source UPF node. In this way, when the timing service requirements of the UE move or the AF request cannot be met, the continuity of the timing service to the terminal can still be guaranteed.
[0185] In some embodiments, a method for supporting timing service continuity is provided, which is applied to a target service node, which may be a target RAN node or a target UPF node.
[0186] Figure 4 A flowchart of another method for supporting timing service continuity provided in an embodiment of the present application is shown as follows: Figure 4 As shown, the method mainly includes the following steps:
[0187] S401: Send timing capability information to the first node, so that the first node determines a target service node that meets the timing service requirements as the service node after switching according to the timing capability information; or, the source service node determines a target service node that meets the timing service requirements as the service node after switching according to the timing capability information of the source service node and / or the timing capability information of the target service node.
[0188] Specifically, during the PDU session establishment process, the target service node may send the timing capability information to the first node.
[0189] Optionally, the target RAN node may send its timing capability information to the AMF node through the N2 message, and the AMF node then sends the timing capability information to the first node through the Namf_Communication_NonUeN2MessageTransfer service operation, or the target RAN node may send its timing capability information to the first node through the OAM node, and the target UPF node may send its timing capability information to the first node through the UMIC or OAM node. Through the timing capability information of the target RAN node, the first node can determine the service node of the terminal to be switched, thereby determining the target RAN node that meets the timing service requirements based on the timing capability information of the target RAN node, and through the timing capability information of the target UPF node, the first node can determine the service node of the terminal to be switched, thereby determining the target UPF node that meets the timing service requirements based on the timing capability information of the target UPF node. In this way, when the timing service requirements requested by the UE or AF cannot be met, the continuity of the timing service for the terminal can still be guaranteed.
[0190] Optionally, the source service node may determine the target service node through the timing capability information of the target service node when its own timing capability information changes.
[0191] Optionally, when the source service node is a source RAN node, the timing capability information of the source service node may further include a signal measurement report of the source RAN node, and the timing capability information of the target service node may further include a signal measurement report of the target RAN node. In this way, the source RAN node can determine the target RAN node when its signal value is less than a certain value and cannot provide timing service to the terminal, and the signal value of the target RAN node is greater than a preset value, so as to ensure that the timing service can continue to be provided to the terminal through the target RAN node, thereby ensuring the continuity of the timing service to the terminal.
[0192] In some embodiments, the target service node is a target RAN node, and further includes: sending a time synchronization status in response to receiving time synchronization assistance information, the source service node is a source RAN node, and the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node.
[0193] Specifically, the time synchronization assistance information may be sent by the source RAN node to the target RAN node, or may be sent by the AMF node to the target RAN node. After receiving the time synchronization assistance information, the target service node may provide its current time synchronization status to the first node, so that the first node can recalculate the time synchronization error budget of the Uu interface according to the time synchronization status and / or timing capability information of the target RAN node.
[0194] Optionally, the first node may provide clock quality reporting control information to the source RAN node through the AMF node, or subscribe to the event notification of the time synchronization state change to the source RAN node. The clock quality reporting control information may include clock quality acceptance criteria and may also include clock quality detail level. After receiving the clock quality reporting control information or monitoring the time synchronization state change, the source RAN node may include the clock quality reporting control information and / or the subscription information of the time synchronization state change in the time synchronization assistance information and send it to the target RAN node. The target RAN node sends the current time synchronization state of the target RAN node to the AMF node based on the subscription information of the time synchronization state change received from the source RAN node, and the AMF node sends the current time synchronization state of the target RAN node to the first node, so that the first node can recalculate the time synchronization error budget of the Uu interface based on the time synchronization state and / or timing capability information of the target RAN node.
[0195] Optionally, for Xn-based handover (UE switching from a source gNB node to a target gNB node via Xn), the source RAN node may send time synchronization assistance information (including clock quality report control information and subscription information of time synchronization status changes, etc.) to the target RAN node via the Xn Application Protocol (XnAP, used to send a handover request message).
[0196] Optionally, for NG-based handover (UE switches from a source NG-RAN node to a target NG-RAN node), the AMF node may send time synchronization assistance information (including clock quality report control information and subscription information of time synchronization status changes, etc.) to the target RAN node via the Next Generation Application Protocol (NGAP, used to send a HANDOVER REQUEST message).
[0197] Among them, the time synchronization assistance information may also include the 5G access stratum time distribution indication and the Uu time synchronization error budget.
[0198] Optionally, the AMF node may also actively request the current time synchronization status of the target RAN node from the target RAN node. If the AMF node also needs to be switched during the RAN node switching process, the source AMF node may send the current time synchronization status of the target RAN node to the target AMF node, and the target AMF node sends the current time synchronization status of the target RAN node to the first node.
[0199] Optionally, the first node can subscribe to notifications of time synchronization status changes (e.g., degradation / failure / promotion) of the target UPF node through UMIC or OAM node. When the target UPF node detects changes in the time synchronization status, it sends the current time synchronization status to the first node so that the first node can configure PTP instances to the target UPF node through UMIC.
[0200] In some embodiments, the method further includes: receiving a time synchronization error budget from the first node, where the time synchronization error budget is determined by the first node based on the received time synchronization status and / or timing capability information of the target service node.
[0201] Specifically, after determining the target service node, the first node can also redetermine the time synchronization error budget of the Uu interface according to the time synchronization status and / or timing capability information of the target service node when the time synchronization status of the target service node changes or the timing capability information changes, and optionally send a new time synchronization error budget of the Uu interface to the target service node to enhance the switching process from the source service node to the target service node, thereby ensuring the continuity of the timing service to the terminal.
[0202] In some embodiments, the target service node is a target RAN node, and the timing capability information includes at least one of the following: the main time source of the target RAN node, clock quality, synchronization performance, punctuality performance, node identification, and a cell identification list; the target service node is a target UPF node, and the timing capability information includes at least one of the following: the main time source of the target UPF node, clock quality, synchronization performance, punctuality performance, node identification, a port number list of the network side TSN converter NW-TT, a supported time domain list, and a supported DNAI list.
[0203] Specifically, the timing capability information of the target RAN node may include at least one of the primary time source of the target RAN node (e.g., "Synchronous Ethernet", "Precision Time Protocol", "Global Navigation Satellite System", "Atomic Clock", "Terrestrial Radio", "Sequential Time Code", "Network Time Protocol", "Handheld Device", etc.), clock quality (e.g., clock accuracy), synchronization performance (e.g., Traceable to GNSS), timekeeping performance, node identification, cell identification list, and signal measurement reports of the source RAN node and / or the target RAN node. The timing capability information of the target UPF node may include at least one of the primary time source of the target UPF node (e.g., "Synchronous Ethernet", "Precision Time Protocol", "Global Navigation Satellite System", "Atomic Clock", "Terrestrial Radio", "Sequential Time Code", "Network Time Protocol", "Handheld Device", etc.), clock quality (e.g., clock accuracy), synchronization performance (e.g., Traceable to GNSS), timekeeping performance, UPF node identification, NW-TT port number list, supported time domain list, and supported DNAI list.
[0204] Optionally, through the timing capability information of the source RAN node, the first node can determine the service node of the terminal to be switched, thereby determining the target RAN node that meets the timing service requirements according to the timing capability information of the source RAN node; and through the timing capability information of the source UPF node, the first node can determine the service node of the terminal to be switched, thereby determining the target UPF node that meets the timing service requirements according to the timing capability information of the source UPF node. In this way, when the timing service requirements of the UE move or the AF request cannot be met, the continuity of the timing service to the terminal can still be guaranteed.
[0205] In some embodiments, a method for supporting timing service continuity is provided, which is applied to a second node, which may be an SMF node.
[0206] Figure 5 A flowchart of another method for supporting timing service continuity provided in an embodiment of the present application is shown as follows: Figure 5 As shown, the method mainly includes the following steps:
[0207] S501: In response to the change of the DNAI or candidate DNAI of the source UPF node, the DNAI or candidate DNAI of the target UPF node is sent to the first node, so that the first node determines to switch the terminal to the target UPF node that meets the timing service requirements based on the DNAI or candidate DNAI of the target UPF node.
[0208] Specifically, the first node can subscribe to the second node for notification of the event of DNAI change of the source UPF node or candidate DNAI(s) change through the Nsmf_EventExposure_Suscribe service operation. When the event subscribed by the first node to the second node occurs, the second node can send the DNAI of the target UPF node or candidate DNAI(s) (Candidate DNAI(s) for the PDU Session) to the first node through the Nsmf_EventExposure_Notify service operation, so that the first node can determine the source UPF node of the terminal that needs to be switched, and thus select a suitable target UPF node to switch the source UPF node of the terminal to the selected suitable target UPF node, so that when the UE moves, the continuity of the timing service for the terminal can still be guaranteed.
[0209] In some embodiments, a device for supporting timing service continuity is provided, which is applied to a first node.
[0210] Figure 6 A schematic diagram of a structure of a device for supporting timing service continuity provided in an embodiment of the present application, such as Figure 6 As shown, the device comprises:
[0211] A determination module 601 is used to determine a target service node that meets the timing service requirements based on the type of service node currently serving the terminal and the target condition, as the service node after switching;
[0212] The indication module 602 is used to indicate the information of the target service node.
[0213] In some embodiments, when the source service node is a source RAN node, the target condition includes receiving at least one of the following switching information: timing capability information of the target RAN node, a node identification list of the target RAN node, a signal measurement report of the source RAN node and / or the target RAN node, a time synchronization error budget parameter and / or a clock quality acceptance standard parameter to be met by the target RAN node, and the time synchronization status of the source RAN node; when the source service node is a source UPF node, the target condition includes receiving at least one of the following switching information: timing capability information of the target UPF node, a data network access identifier DNAI or a candidate DNAI of the target UPF node, a time synchronization error budget parameter and a clock quality acceptance standard parameter to be met by the target UPF node, and the time synchronization status of the source UPF node.
[0214] In some embodiments, the target condition further includes: determining that the source service node does not meet the timing service requirements, the timing service requirements including time synchronization error budget and / or clock quality acceptance criteria.
[0215] In some embodiments, when the source service node is a source RAN node, the switching information is received in the following manner: in response to detecting a change in the timing capability information of the source RAN node, requesting the source RAN node to obtain switching indication information and / or a list of identifiers of a target RAN node; receiving switching indication information or a list of identifiers of a target RAN node from the source RAN node, the switching information including the switching indication information and / or the list of identifiers of the target RAN node, the switching indication information including the identifier information and / or signal measurement data of the target RAN node, and the list of identifiers of the target RAN node including a list of target RAN node identifiers or a list of cell identifiers.
[0216] In some embodiments, when the determination module 601 determines the target service node that meets the timing service requirements as the service node after switching based on the service node type and target conditions currently serving the terminal, it is specifically used to: determine the target RAN node according to the changed timing capability information of the source RAN node, and the switching indication information and / or the identification list of the target RAN node.
[0217] In some embodiments, when the source service node is a source RAN node, the switching information is received in the following manner: obtaining the timing service requirement and the time synchronization status of the source RAN node, the switching information includes the timing service requirement and the time synchronization status of the source RAN node; the timing service requirement includes at least one of the following: time synchronization error budget, clock quality detail level, clock quality acceptance criteria; the time synchronization status of the source RAN node includes at least one of the following: synchronization status, synchronization performance, clock quality and master time source of the source RAN node.
[0218] In some embodiments, whether the source service node meets the timing service requirement is determined in the following manner: whether the source RAN node meets the timing service requirement is determined based on the timing capability information of the source RAN node and the time synchronization status of the source RAN node.
[0219] In some embodiments, it also includes: a receiving module (not shown) for receiving timing capability information from a source RAN node and a target RAN node, the timing capability information including at least one of the following: a primary time source, clock quality, synchronization performance, punctuality performance, node identification, and a cell identification list.
[0220] In some embodiments, when the source service node is a source UPF node, the switching information is received in the following manner: in response to a DNAI change of the source UPF node, a DNAI or a candidate DNAI of a target UPF node is received from a second node, and the switching information includes the DNAI or the candidate DNAI of the target UPF node.
[0221] In some embodiments, when the determination module 601 determines the target service node that meets the timing service requirements based on the service node type and target conditions currently serving the terminal, as the service node after switching, it is specifically used to: determine the target UPF node according to the changed timing capability information of the source UPF node and the DNAI or candidate DNAI of the target UPF node.
[0222] In some embodiments, when the source service node is a source UPF node, the switching information is received in the following manner: obtaining the timing service requirements and the time synchronization status of the source UPF node, the switching information includes the timing service requirements and the time synchronization status of the source UPF node; the timing service requirements include at least one of the following: time synchronization error budget, clock quality detail level and clock quality acceptance criteria; the time synchronization status of the source UPF node includes at least one of the following: synchronization status, synchronization performance, clock quality and master time source of the source UPF node.
[0223] In some embodiments, whether the source service node meets the timing service requirements is determined in the following manner: based on the timing capability information of the source UPF node and the time synchronization status of the source UPF node, whether the source UPF node meets the timing service requirements is determined.
[0224] In some embodiments, the receiving module is also used to receive timing capability information from the source UPF node and the target UPF node, and the timing capability information includes at least one of the following: main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
[0225] In some embodiments, it also includes: a processing module (not shown), which is used to receive the time synchronization status and / or timing capability information of the target service node after indicating the information of the target service node; determine the time synchronization error budget of the target service node based on the time synchronization status and / or timing capability information of the target service node; and send the time synchronization error budget to the target service node.
[0226] In some embodiments, an apparatus for supporting timing service continuity is provided, which is applied to a source service node.
[0227] Figure 7A schematic diagram of the structure of another device for supporting timing service continuity provided in an embodiment of the present application, such as Figure 7 As shown, the device comprises:
[0228] Processing module 701 is used to send timing capability information to the first node, so that the first node determines the target service node that meets the timing service requirements as the service node after switching according to the timing capability information; or, determines the target service node that meets the timing service requirements as the service node after switching according to the timing capability information of the source service node and / or the timing capability information of the target service node.
[0229] In some embodiments, the source service node is a source RAN node, and the processing module is further used to determine whether to switch the source RAN node to the target RAN node, or determine whether a signal value of the target RAN node is greater than a preset value in response to receiving a request from the first node for obtaining switching indication information and / or a target RAN node identification list, and the target RAN node identification list includes a node identification list or a cell identification list of the target RAN node; in response to switching the source RAN node to the target RAN node, or the signal value of the target RAN node being greater than a preset value, send the switching indication information and / or the target RAN node identification list to the first node.
[0230] In some embodiments, the processing module is also used to send time synchronization assistance information to the target RAN node in response to receiving clock quality report control information from the first node, or a change in the time synchronization status of the source RAN node, the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node, and the target service node is the target RAN node.
[0231] In some embodiments, the source service node is a source RAN node, and the timing capability information includes at least one of the following: the main time source of the source RAN node, clock quality, synchronization performance, punctuality performance, node identification, cell identification list, and signal measurement report of the source RAN node and / or the target RAN node; the source service node is a source UPF node, and the timing capability information includes at least one of the following: the main time source of the source UPF node, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list, and supported DNAI list.
[0232] In some embodiments, a device for supporting timing service continuity is provided, which is applied to a target service node.
[0233] Figure 8 A schematic diagram of the structure of another device for supporting timing service continuity provided in an embodiment of the present application is shown in FIG. Figure 8 As shown, the device comprises:
[0234] The sending module 801 is used to send timing capability information to the first node, so that the first node determines the target service node that meets the timing service requirements as the service node after switching according to the timing capability information; or the source service node determines the target service node that meets the timing service requirements as the service node after switching according to the timing capability information of the source service node and / or the timing capability information of the target service node.
[0235] In some embodiments, the target service node is a target RAN node and further includes: a processing module (not shown) for sending a time synchronization status in response to receiving time synchronization assistance information, the source service node is a source RAN node, and the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node.
[0236] In some embodiments, the processing module is further used to receive a time synchronization error budget from the first node, where the time synchronization error budget is determined by the first node based on the received time synchronization state and / or timing capability information of the target service node.
[0237] In some embodiments, the target service node is a target RAN node, and the timing capability information includes at least one of the following: the main time source of the target RAN node, clock quality, synchronization performance, punctuality performance, node identification, cell identification list, signal measurement report of the source RAN node and / or the target RAN node; the target service node is a target UPF node, and the timing capability information includes at least one of the following: the main time source of the target UPF node, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
[0238] In some embodiments, a device for supporting timing service continuity is provided, which is applied to a second node.
[0239] Fig. 9 A schematic diagram of the structure of another device for supporting timing service continuity provided in an embodiment of the present application is shown in FIG. Fig. 9 As shown, the device comprises:
[0240] The sending module 901 is used to send the DNAI or candidate DNAI of the target UPF node to the first node in response to the change of the DNAI or candidate DNAI of the source UPF node, so that the first node determines to switch the terminal to the target UPF node that meets the timing service requirements according to the DNAI or candidate DNAI of the target UPF node.
[0241] It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module in each embodiment of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into one module. The above-mentioned integrated modules may be implemented in the form of hardware or in the form of software functional modules.
[0242] If the above-mentioned integrated module is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method of each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.
[0243] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.
[0244] In some embodiments, a device for supporting timing service continuity is also provided.
[0245] Fig.10 A schematic diagram of a structure of a device supporting timing service continuity provided in an embodiment of the present application, such as Fig.10 As shown, the device supporting timing service continuity includes: a memory 1011, a transceiver 1012, and a processor 1013;
[0246] The memory 1011 is used to store computer programs.
[0247] The transceiver 1012 is used to send and receive data under the control of the processor.
[0248] The processor 1013 is used to read the computer program in the memory and perform the following operations:
[0249] Based on the type of service node currently serving the terminal and the target condition, determine the target service node that meets the timing service requirements as the service node after switching;
[0250] Indicates the information of the target service node.
[0251] Among them, Fig.10 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1013 and various circuits of memory represented by memory 1011 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1012 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include wireless channels, wired channels, optical cables, and other transmission media. The processor 1013 is responsible for managing the bus architecture and general processing, and the memory 1011 may store data used by the processor 1013 when performing operations.
[0252] The processor 1013 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0253] In some embodiments, when the source service node is a source RAN node, the target condition includes receiving at least one of the following switching information: timing capability information of the target RAN node, a node identification list of the target RAN node, a signal measurement report of the source RAN node and / or the target RAN node, a time synchronization error budget parameter and / or a clock quality acceptance standard parameter to be met by the target RAN node, and the time synchronization status of the source RAN node; when the source service node is a source UPF node, the target condition includes receiving at least one of the following switching information: timing capability information of the target UPF node, a data network access identifier DNAI or a candidate DNAI of the target UPF node, a time synchronization error budget parameter and a clock quality acceptance standard parameter to be met by the target UPF node, and the time synchronization status of the source UPF node.
[0254] In some embodiments, the target condition further includes: determining that the source service node does not meet the timing service requirements, the timing service requirements including time synchronization error budget and / or clock quality acceptance criteria.
[0255] In some embodiments, when the source service node is a source RAN node, the switching information is received in the following manner: in response to detecting a change in the timing capability information of the source RAN node, requesting the source RAN node to obtain switching indication information and / or a list of identifiers of a target RAN node; receiving switching indication information or a list of identifiers of a target RAN node from the source RAN node, the switching information including the switching indication information and / or the list of identifiers of the target RAN node, the switching indication information including the identifier information and / or signal measurement data of the target RAN node, and the list of identifiers of the target RAN node including a list of target RAN node identifiers or a list of cell identifiers.
[0256] In some embodiments, based on the service node type and target conditions currently serving the terminal, a target service node that meets the timing service requirements is determined as the service node after switching, including: determining the target RAN node based on the changed timing capability information of the source RAN node, as well as the switching indication information and / or the target RAN node identification list.
[0257] In some embodiments, when the source service node is a source RAN node and the target service node is a target RAN node, the switching information is received in the following manner: obtaining the timing service requirement and the time synchronization status of the source RAN node, the switching information includes the timing service requirement and the time synchronization status of the source RAN node; the timing service requirement includes at least one of the following: time synchronization error budget, clock quality detail level, clock quality acceptance criteria; the time synchronization status of the source RAN node includes at least one of the following: synchronization status, synchronization performance, clock quality and master time source of the source RAN node.
[0258] In some embodiments, whether the source service node meets the timing service requirement is determined in the following manner: whether the source RAN node meets the timing service requirement is determined based on the timing capability information of the source RAN node and the time synchronization status of the source RAN node.
[0259] In some embodiments, it also includes: receiving timing capability information from the source RAN node and the target RAN node, the timing capability information including at least one of the following: primary time source, clock quality, synchronization performance, punctuality performance, node identification, and cell identification list.
[0260] In some embodiments, when the source service node is a source UPF node and the target service node is a target UPF node, the switching information is received in the following manner: in response to a DNAI change of the source UPF node, a DNAI or a candidate DNAI of the target UPF node is received from a second node, and the switching information includes the DNAI or the candidate DNAI of the target UPF node.
[0261] In some embodiments, based on the service node type and target conditions currently serving the terminal, a target service node that meets the timing service requirements is determined as the service node after switching, including: determining the target UPF node based on the changed timing capability information of the source UPF node and the DNAI or candidate DNAI of the target UPF node.
[0262] In some embodiments, when the source service node is a source UPF node and the target service node is a target UPF node, the switching information is received in the following manner: obtaining the timing service requirements and the time synchronization status of the source UPF node, the switching information includes the timing service requirements and the time synchronization status of the source UPF node; the timing service requirements include at least one of the following: time synchronization error budget, clock quality detail level and clock quality acceptance criteria; the time synchronization status of the source UPF node includes at least one of the following: synchronization status, synchronization performance, clock quality and master time source of the source UPF node.
[0263] In some embodiments, whether the source service node meets the timing service requirements is determined in the following manner: based on the timing capability information of the source UPF node and the time synchronization status of the source UPF node, whether the source UPF node meets the timing service requirements is determined.
[0264] In some embodiments, it also includes: receiving timing capability information from the source UPF node and the target UPF node, the timing capability information including at least one of the following: main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
[0265] In some embodiments, after indicating the information of the target service node, it also includes: receiving the time synchronization status and / or timing capability information of the target service node; determining the time synchronization error budget of the target service node based on the time synchronization status and / or timing capability information of the target service node; and sending the time synchronization error budget to the target service node.
[0266] In some embodiments, a device for supporting timing service continuity is also provided.
[0267] Fig.11 A schematic diagram of the structure of another device supporting timing service continuity provided in an embodiment of the present application, such as Fig.11 As shown, the device supporting timing service continuity includes: a memory 1111, a transceiver 1112, and a processor 1113;
[0268] The memory 1111 is used to store computer programs.
[0269] The transceiver 1112 is used to send and receive data under the control of the processor.
[0270] The processor 1113 is used to read the computer program in the memory and perform the following operations:
[0271] Send timing capability information to the first node so that the first node determines a target service node that meets the timing service requirements as the service node after switching based on the timing capability information; or, determine a target service node that meets the timing service requirements as the service node after switching based on the timing capability information of the source service node and / or the timing capability information of the target service node.
[0272] Among them, Fig.11 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1113 and various circuits of memory represented by memory 1111 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1112 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include wireless channels, wired channels, optical cables, and other transmission media. The processor 1113 is responsible for managing the bus architecture and general processing, and the memory 1111 may store data used by the processor 1113 when performing operations.
[0273] The processor 1113 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0274] In some embodiments, the source service node is a source RAN node, further comprising: in response to receiving a request from the first node for obtaining switching indication information and / or a target RAN node identification list, determining whether to switch the source RAN node to the target RAN node, or determining whether a signal value of the target RAN node is greater than a preset value, the target RAN node identification list including a node identification list or a cell identification list of the target RAN node; in response to switching the source RAN node to the target RAN node, or the signal value of the target RAN node being greater than a preset value, sending the switching indication information and / or the target RAN node identification list to the first node.
[0275] In some embodiments, it also includes: in response to receiving clock quality report control information from the first node, or the time synchronization status of the source RAN node changes, sending time synchronization assistance information to the target RAN node, the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node, and the target service node is the target RAN node.
[0276] In some embodiments, the source service node is a source RAN node, and the timing capability information includes at least one of the following: the main time source of the source RAN node, clock quality, synchronization performance, punctuality performance, node identification, cell identification list, and signal measurement report of the source RAN node and / or the target RAN node; the source service node is a source UPF node, and the timing capability information includes at least one of the following: the main time source of the source UPF node, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list, and supported DNAI list.
[0277] In some embodiments, a device for supporting timing service continuity is also provided.
[0278] Fig.12 A structural diagram of another device supporting timing service continuity provided in an embodiment of the present application is as follows: Fig.12 As shown, the device supporting timing service continuity includes: a memory 1211, a transceiver 1212, and a processor 1213;
[0279] The memory 1211 is used to store computer programs.
[0280] The transceiver 1212 is used to send and receive data under the control of the processor.
[0281] The processor 1213 is used to read the computer program in the memory and perform the following operations:
[0282] Send timing capability information to the first node so that the first node determines a target service node that meets the timing service requirements as the service node after switching based on the timing capability information; or, the source service node determines a target service node that meets the timing service requirements as the service node after switching based on the timing capability information of the source service node and / or the timing capability information of the target service node.
[0283] Among them, Fig.12 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1213 and various circuits of memory represented by memory 1211 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1212 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include wireless channels, wired channels, optical cables, and other transmission media. The processor 1213 is responsible for managing the bus architecture and general processing, and the memory 1211 may store data used by the processor 1213 when performing operations.
[0284] The processor 1213 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0285] In some embodiments, the target service node is a target RAN node, and further includes: sending a time synchronization status in response to receiving time synchronization assistance information, the source service node is a source RAN node, and the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node.
[0286] In some embodiments, the method further includes: receiving a time synchronization error budget from the first node, where the time synchronization error budget is determined by the first node based on the received time synchronization status and / or timing capability information of the target service node.
[0287] In some embodiments, the target service node is a target RAN node, and the timing capability information includes at least one of the following: the main time source of the target RAN node, clock quality, synchronization performance, punctuality performance, node identification, cell identification list, signal measurement report of the source RAN node and / or the target RAN node; the target service node is a target UPF node, and the timing capability information includes at least one of the following: the main time source of the target UPF node, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
[0288] In some embodiments, a device for supporting timing service continuity is also provided.
[0289] Fig.13 A structural diagram of another device supporting timing service continuity provided in an embodiment of the present application is shown in FIG. Fig.13 As shown, the device supporting timing service continuity includes: a memory 1311, a transceiver 1312, and a processor 1313;
[0290] The memory 1311 is used to store computer programs.
[0291] The transceiver 1312 is used to send and receive data under the control of the processor.
[0292] The processor 1313 is used to read the computer program in the memory and perform the following operations:
[0293] In response to a change in the DNAI or candidate DNAI of the source UPF node, the DNAI or candidate DNAI of the target UPF node is sent to the first node, so that the first node determines to switch the terminal to the target UPF node that meets the timing service requirements based on the DNAI or candidate DNAI of the target UPF node.
[0294] Among them, Fig.13 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1313 and various circuits of memory represented by memory 1311 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1312 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include wireless channels, wired channels, optical cables, and other transmission media. The processor 1313 is responsible for managing the bus architecture and general processing, and the memory 1311 may store data used by the processor 1313 when performing operations.
[0295] The processor 1313 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.
[0296] It should be noted that the division of units in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
[0297] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.
[0298] It should be noted here that the above-mentioned device provided in the embodiment of the present invention can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.
[0299] In some embodiments, a processor-readable storage medium is also provided, the processor-readable storage medium storing a computer program, and the computer program is used to enable a processor to execute any one of the methods in the method embodiments.
[0300] The processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NAND FLASH), solid-state drives (SSDs)), etc.
[0301] In some embodiments, a computer program product is provided, comprising a computer program for causing a processor to execute any one of the method embodiments.
[0302] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.
[0303] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0304] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0305] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0306] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.
Claims
1. A method for supporting timing service continuity, characterized in that: Applied to the first node, the method comprises: Based on the type of service node currently serving the terminal and the target condition, determine the target service node that meets the timing service requirements as the service node after switching; Indicates information about the target service node.
2. The method according to claim 1, characterized in that: In the case where the source service node is a source RAN node, the target condition includes receiving at least one of the following handover information: Timing capability information of the target RAN node, a list of node identifiers of the target RAN node, signal measurement reports of the source RAN node and / or the target RAN node, time synchronization error budget parameters and / or clock quality acceptance criteria parameters to be met by the target RAN node, and time synchronization status of the source RAN node; In the case where the source service node is a source UPF node, the target condition includes receiving at least one of the following switching information: The timing capability information of the target UPF node, the data network access identifier DNAI or candidate DNAI of the target UPF node, the time synchronization error budget parameters and clock quality acceptance standard parameters to be met by the target UPF node, and the time synchronization status of the source UPF node.
3. The method according to claim 2, characterized in that The target conditions also include: It is determined that the source service node does not meet a timing service requirement, wherein the timing service requirement includes a time synchronization error budget and / or a clock quality acceptance criterion.
4. The method according to claim 2, characterized in that: In the case where the source service node is a source RAN node, the handover information is received in the following manner: In response to detecting a change in the timing capability information of the source RAN node, requesting the source RAN node to obtain switching indication information and / or an identification list of the target RAN node; receiving the handover indication information or the identifier list of the target RAN node from the source RAN node, the handover information including the handover indication information and / or the identifier list of the target RAN node, the handover indication information including the identifier information and / or signal measurement data of the target RAN node, and the identifier list of the target RAN node including the target RAN node identifier list or the cell identifier list.
5. The method according to claim 4, characterized in that The step of determining a target service node that meets the timing service requirement based on the type of service node currently serving the terminal and the target condition as the service node after switching includes: The target RAN node is determined according to the changed timing capability information of the source RAN node, the switching indication information and / or the identifier list of the target RAN node.
6. The method according to claim 3, characterized in that In the case where the source service node is a source RAN node, the handover information is received in the following manner: Acquire a timing service requirement and a time synchronization status of the source RAN node, wherein the switching information includes the timing service requirement and the time synchronization status of the source RAN node; The timing service requirements include at least one of the following: time synchronization error budget, clock quality detail level, clock quality acceptance criteria; The time synchronization status of the source RAN node includes at least one of the following: synchronization status, synchronization performance, clock quality and primary time source of the source RAN node.
7. The method according to claim 6, characterized in that Determine whether the source service node meets the timing service requirement by: Determine whether the source RAN node meets the timing service requirement according to the timing capability information of the source RAN node and the time synchronization state of the source RAN node.
8. The method according to any one of claims 4 to 7, characterized in that Also includes: Receive timing capability information from the source RAN node and the target RAN node, wherein the timing capability information includes at least one of the following: a primary time source, clock quality, synchronization performance, punctuality performance, node identification, and a cell identification list.
9. The method according to claim 2, characterized in that: In the case where the source service node is a source UPF node, the switching information is received in the following manner: In response to the DNAI of the source UPF node changing, receiving the DNAI or candidate DNAI of the target UPF node from the second node, the switching information includes the DNAI or candidate DNAI of the target UPF node.
10. The method according to claim 9, characterized in that The step of determining a target service node that meets the timing service requirement based on the type of service node currently serving the terminal and the target condition as the service node after switching includes: The target UPF node is determined according to the changed timing capability information of the source UPF node and the DNAI or candidate DNAI of the target UPF node.
11. The method according to claim 3, characterized in that In the case where the source service node is a source UPF node, the switching information is received in the following manner: Obtaining the timing service requirement and the time synchronization status of the source UPF node, wherein the switching information includes the timing service requirement and the time synchronization status of the source UPF node; The timing service requirements include at least one of the following: time synchronization error budget, clock quality detail level, and clock quality acceptance criteria; The time synchronization status of the source UPF node includes at least one of the following: the synchronization status, synchronization performance, clock quality and master time source of the source UPF node.
12. The method according to claim 11, characterized in that Determine whether the source service node meets the timing service requirement by: According to the timing capability information of the source UPF node and the time synchronization status of the source UPF node, determine whether the source UPF node meets the timing service requirements.
13. The method according to any one of claims 9 to 12, characterized in that Also includes: Receive timing capability information from the source UPF node and the target UPF node, the timing capability information including at least one of the following: main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
14. The method according to any one of claims 1 to 3, characterized in that After the information indicating the target service node, the method further includes: Receiving time synchronization status and / or timing capability information of the target service node; Determining a time synchronization error budget of the target service node based on the time synchronization state of the target service node and / or the timing capability information; The time synchronization error budget is sent to the target service node.
15. A method for supporting timing service continuity, characterized in that: Applied to a source service node, the method comprises: Sending timing capability information to the first node, so that the first node determines a target service node that meets the timing service requirement according to the timing capability information as a service node after switching; or, According to the timing capability information of the source service node and / or the timing capability information of the target service node, a target service node that meets the timing service requirement is determined as a service node after switching.
16. The method according to claim 15, characterized in that The source service node is a source RAN node, and further includes: determining, in response to receiving a request for obtaining handover indication information and / or a target RAN node identifier list from the first node, whether to handover the source RAN node to the target RAN node, or determining whether a signal value of the target RAN node is greater than a preset value, wherein the target RAN node identifier list includes a node identifier list or a cell identifier list of the target RAN node; In response to switching the source RAN node to the target RAN node, or the signal value of the target RAN node being greater than the preset value, sending the switching indication information and / or the identifier list of the target RAN node to the first node.
17. The method according to claim 15, characterized in that Also includes: In response to receiving clock quality report control information from the first node, or a change in the time synchronization status of the source RAN node, time synchronization assistance information is sent to the target RAN node, the time synchronization assistance information including the clock quality report control information and / or the time synchronization status of the source RAN node, and the target service node is the target RAN node.
18. The method according to any one of claims 15 to 17, characterized in that The source service node is a source RAN node, and the timing capability information includes at least one of the following: a primary time source, clock quality, synchronization performance, punctuality performance, node identifier, cell identifier list, and a signal measurement report of the source RAN node and / or the target RAN node; The source service node is a source UPF node, and the timing capability information includes at least one of the following: the main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list of the source UPF node.
19. A method for supporting timing service continuity, characterized in that: Applied to a target service node, the method comprises: Sending timing capability information to the first node, so that the first node determines a target service node that meets the timing service requirement according to the timing capability information as a service node after switching; or, The source service node determines the target service node that meets the timing service requirement as the switched service node according to the timing capability information of the source service node and / or the timing capability information of the target service node.
20. The method according to claim 19, characterized in that The target service node is a target RAN node, and further includes: In response to receiving the time synchronization assistance information, a time synchronization status is sent, the time synchronization assistance information including clock quality report control information and / or the time synchronization status of the source RAN node.
21. The method according to claim 19 or 20, characterized in that Also includes: A time synchronization error budget is received from the first node, where the time synchronization error budget is determined by the first node based on the received time synchronization state and / or timing capability information of the target service node.
22. The method according to claim 19 or 20, characterized in that The target service node is a target RAN node, and the timing capability information includes at least one of the following: a primary time source, clock quality, synchronization performance, punctuality performance, node identifier, cell identifier list, and a signal measurement report of a source RAN node and / or a target RAN node of the target RAN node; The target service node is a target UPF node, and the timing capability information includes at least one of the following: the main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list of the target UPF node.
23. A method for supporting timing service continuity, characterized in that: Applied to the second node, the method comprises: In response to a change in the DNAI or candidate DNAI of the source UPF node, the DNAI or candidate DNAI of the target UPF node is sent to the first node, so that the first node determines to switch the terminal to the target UPF node that meets the timing service requirements based on the DNAI or candidate DNAI of the target UPF node.
24. A device for supporting timing service continuity, characterized in that: Applied to a first node, the device comprises: A determination module, used to determine a target service node that meets the timing service requirements based on the type of service node currently serving the terminal and the target condition, as the service node after switching; The indication module is used to indicate the information of the target service node.
25. A device for supporting timing service continuity, characterized in that: Applied to a source service node, the device comprises: a processing module, configured to send timing capability information to the first node, so that the first node determines a target service node that meets the timing service requirement according to the timing capability information as a switched service node; or According to the timing capability information of the source service node and / or the timing capability information of the target service node, a target service node that meets the timing service requirement is determined as a service node after switching.
26. A device for supporting timing service continuity, characterized in that: Applied to a target service node, the device comprises: a sending module, configured to send timing capability information to the first node, so that the first node determines a target service node that meets the timing service requirement according to the timing capability information as the service node after switching; or The source service node determines the target service node that meets the timing service requirement as the switched service node according to the timing capability information of the source service node and / or the timing capability information of the target service node.
27. A device for supporting timing service continuity, characterized in that: Applied to a second node, the device comprises: A sending module is used to send the DNAI or candidate DNAI of the target UPF node to the first node in response to the change of the DNAI or candidate DNAI of the source UPF node, so that the first node determines to switch the terminal to the target UPF node that meets the timing service requirements according to the DNAI or candidate DNAI of the target UPF node.
28. A device supporting timing service continuity, characterized in that: include: Memory, transceiver, processor; The memory is used to store computer programs; The transceiver is used to send and receive data under the control of the processor; The processor is configured to read the computer program in the memory and perform the following operations: Based on the type of service node currently serving the terminal and the target condition, determine the target service node that meets the timing service requirements as the service node after switching; Indicates information about the target service node.
29. The device according to claim 28, characterized in that In the case where the source service node is a source RAN node, the target condition includes receiving at least one of the following handover information: Timing capability information of the target RAN node, a list of node identifiers of the target RAN node, signal measurement reports of the source RAN node and / or the target RAN node, time synchronization error budget parameters and / or clock quality acceptance criteria parameters to be met by the target RAN node, and time synchronization status of the source RAN node; In the case where the source service node is a source UPF node, the target condition includes receiving at least one of the following switching information: The timing capability information of the target UPF node, the data network access identifier DNAI or candidate DNAI of the target UPF node, the time synchronization error budget parameters and clock quality acceptance standard parameters to be met by the target UPF node, and the time synchronization status of the source UPF node.
30. The device according to claim 29, characterized in that The target conditions also include: It is determined that the source service node does not meet a timing service requirement, wherein the timing service requirement includes a time synchronization error budget and / or a clock quality acceptance criterion.
31. The device according to claim 29, characterized in that In the case where the source service node is a source RAN node, the handover information is received in the following manner: In response to detecting a change in the timing capability information of the source RAN node, requesting the source RAN node to obtain switching indication information and / or an identification list of the target RAN node; receiving the handover indication information or the identifier list of the target RAN node from the source RAN node, the handover information including the handover indication information and / or the identifier list of the target RAN node, the handover indication information including the identifier information and / or signal measurement data of the target RAN node, and the identifier list of the target RAN node including the target RAN node identifier list or the cell identifier list.
32. The device according to claim 31, characterized in that The step of determining a target service node that meets the timing service requirement based on the type of service node currently serving the terminal and the target condition as the service node after switching includes: The target RAN node is determined according to the changed timing capability information of the source RAN node, the switching indication information and / or the identifier list of the target RAN node.
33. The device according to claim 30, characterized in that When the source service node is a source RAN node and the target service node is a target RAN node, the handover information is received in the following manner: Acquire a timing service requirement and a time synchronization status of the source RAN node, wherein the switching information includes the timing service requirement and the time synchronization status of the source RAN node; The timing service requirements include at least one of the following: time synchronization error budget, clock quality detail level, clock quality acceptance criteria; The time synchronization status of the source RAN node includes at least one of the following: synchronization status, synchronization performance, clock quality and primary time source of the source RAN node.
34. The device according to claim 33, characterized in that Determine whether the source service node meets the timing service requirement by: Determine whether the source RAN node meets the timing service requirement according to the timing capability information of the source RAN node and the time synchronization state of the source RAN node.
35. Apparatus according to any one of claims 31 to 34, characterised in that Also includes: Receive timing capability information from the source RAN node and the target RAN node, wherein the timing capability information includes at least one of the following: a primary time source, clock quality, synchronization performance, punctuality performance, node identification, and a cell identification list.
36. The apparatus according to claim 29, characterized in that When the source service node is a source UPF node and the target service node is a target UPF node, the switching information is received in the following manner: In response to the DNAI of the source UPF node changing, receiving the DNAI or candidate DNAI of the target UPF node from the second node, the switching information includes the DNAI or candidate DNAI of the target UPF node.
37. The device according to claim 36, characterized in that The step of determining a target service node that meets the timing service requirement based on the type of service node currently serving the terminal and the target condition as the service node after switching includes: The target UPF node is determined according to the changed timing capability information of the source UPF node and the DNAI or candidate DNAI of the target UPF node.
38. The apparatus according to claim 30, characterized in that When the source service node is a source UPF node and the target service node is a target UPF node, the switching information is received in the following manner: Obtaining the timing service requirement and the time synchronization status of the source UPF node, wherein the switching information includes the timing service requirement and the time synchronization status of the source UPF node; The timing service requirements include at least one of the following: time synchronization error budget, clock quality detail level, and clock quality acceptance criteria; The time synchronization status of the source UPF node includes at least one of the following: the synchronization status, synchronization performance, clock quality and master time source of the source UPF node.
39. The device according to claim 38, characterized in that Determine whether the source service node meets the timing service requirement by: According to the timing capability information of the source UPF node and the time synchronization status of the source UPF node, determine whether the source UPF node meets the timing service requirements.
40. Apparatus according to any one of claims 36 to 39, characterised in that Also includes: Receive timing capability information from the source UPF node and the target UPF node, the timing capability information including at least one of the following: main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list.
41. Apparatus according to any one of claims 28 to 30, characterised in that After the information indicating the target service node, the method further includes: Receiving time synchronization status and / or timing capability information of the target service node; Determining a time synchronization error budget of the target service node based on the time synchronization state of the target service node and / or the timing capability information; The time synchronization error budget is sent to the target service node.
42. A device supporting timing service continuity, characterized in that: include: Memory, transceiver, processor; The memory is used to store computer programs; The transceiver is used to send and receive data under the control of the processor; The processor is configured to read the computer program in the memory and perform the following operations: Sending timing capability information to the first node, so that the first node determines a target service node that meets the timing service requirement according to the timing capability information as a switched service node; or According to the timing capability information of the source service node and / or the timing capability information of the target service node, a target service node that meets the timing service requirement is determined as the service node after the switch.
43. The device according to claim 42, characterized in that The source service node is a source RAN node, and further includes: determining, in response to receiving a request for obtaining handover indication information and / or a target RAN node identifier list from the first node, whether to handover the source RAN node to the target RAN node, or determining whether a signal value of the target RAN node is greater than a preset value, wherein the target RAN node identifier list includes a node identifier list or a cell identifier list of the target RAN node; In response to switching the source RAN node to the target RAN node, or the signal value of the target RAN node being greater than the preset value, sending the switching indication information and / or the identifier list of the target RAN node to the first node.
44. The device according to claim 42, characterized in that Also includes: In response to receiving clock quality report control information from the first node, or a change in the time synchronization status of the source RAN node, time synchronization assistance information is sent to the target RAN node, the time synchronization assistance information including the clock quality report control information and / or the time synchronization status of the source RAN node, and the target service node is the target RAN node.
45. Apparatus according to any one of claims 42 to 44, characterised in that The source service node is a source RAN node, and the timing capability information includes at least one of the following: a primary time source, clock quality, synchronization performance, punctuality performance, node identifier, cell identifier list, and a signal measurement report of the source RAN node and / or the target RAN node; The source service node is a source UPF node, and the timing capability information includes at least one of the following: the main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list of the source UPF node.
46. A device supporting timing service continuity, characterized in that: include: Memory, transceiver, processor; The memory is used to store computer programs; The transceiver is used to send and receive data under the control of the processor; The processor is configured to read the computer program in the memory and perform the following operations: Sending timing capability information to the first node, so that the first node determines a target service node that meets the timing service requirement according to the timing capability information as a switched service node; or, The source service node determines the target service node that meets the timing service requirement as the switched service node according to the timing capability information of the source service node and / or the timing capability information of the target service node.
47. The device according to claim 46, characterized in that The target service node is a target RAN node, and further includes: In response to receiving time synchronization assistance information, a time synchronization status is sent, the source service node is a source RAN node, and the time synchronization assistance information includes clock quality report control information and / or the time synchronization status of the source RAN node.
48. Apparatus according to claim 46 or 47, characterised in that Also includes: A time synchronization error budget is received from the first node, where the time synchronization error budget is determined by the first node based on the received time synchronization state and / or timing capability information of the target service node.
49. The apparatus according to claim 46 or 47, characterized in that The target service node is a target RAN node, and the timing capability information includes at least one of the following: a primary time source, clock quality, synchronization performance, punctuality performance, node identifier, cell identifier list, and a signal measurement report of a source RAN node and / or a target RAN node of the target RAN node; The target service node is a target UPF node, and the timing capability information includes at least one of the following: the main time source, clock quality, synchronization performance, punctuality performance, node identification, port number list of the network side TSN converter NW-TT, supported time domain list and supported DNAI list of the target UPF node.
50. A device supporting timing service continuity, characterized in that: include: Memory, transceiver, processor; The memory is used to store computer programs; The transceiver is used to send and receive data under the control of the processor; The processor is configured to read the computer program in the memory and perform the following operations: In response to a change in the DNAI or candidate DNAI of the source UPF node, the DNAI or candidate DNAI of the target UPF node is sent to the first node, so that the first node determines to switch the terminal to the target UPF node that meets the timing service requirements based on the DNAI or candidate DNAI of the target UPF node.
51. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the method according to any one of claims 1 to 23.
