Method, device and terminal for determining timing synchronization state change

Abstract

The invention discloses a method and device for determining timing synchronization state changes and a terminal, and belongs to the technical field of communication. The method for determining the timing synchronization state changes comprises the steps that when the terminal obtains a first event identifier corresponding to a first event, the first event identifier corresponds to the first event; the terminal determines whether the timing synchronization state of the terminal changes according to whether a first storage event identifier corresponding to a second event is locally stored; wherein the first event and the second event are related to the timing synchronization state of the terminal.

Description

Technical Field

[0001] This application belongs to the field of communication technologies, and particularly relates to a method, apparatus, and terminal for determining a change in a timing synchronization state. Background Art

[0002] With the continuous development of wireless communication technologies, timing synchronization technology has become an important part of wireless communication technologies. Among them, in related technologies, if the clocks of the network side and the terminal are not synchronized, it may lead to packet loss and duplication, thus affecting communication quality; while timing synchronization technology can ensure that the clocks of the network side and the terminal are consistent, improve the accuracy and reliability of data transmission, and thus improve communication quality.

[0003] Among them, when different timing synchronization sources are involved or different interferences are encountered, the timing synchronization state of the network side may change, and then the timing synchronization state of the terminal also changes accordingly. However, in related technologies, in the case of involving different timing synchronization sources or encountering different interferences, the terminal still operates based on the original timing synchronization state, resulting in that the terminal with a synchronization requirement cannot be synchronized with the network side. Summary of the Invention

[0004] Embodiments of this application provide a method, apparatus, and terminal for determining a change in a timing synchronization state, which can solve the problem of poor timing synchronization stability between the terminal and the network side in related technologies.

[0005] In a first aspect, a method for determining a change in a timing synchronization state is provided. The method includes:

[0006] When the terminal obtains a first event identifier corresponding to a first event, the terminal determines whether the timing synchronization state of the terminal has changed according to whether a first stored event identifier corresponding to a second event is stored locally;

[0007] wherein the first event and the second event are related to the timing synchronization state of the terminal.

[0008] In a second aspect, an apparatus for determining a change in a timing synchronization state is provided, which is applied to a terminal. The apparatus includes:

[0009] A determination module, configured to determine whether the timing synchronization state of the terminal has changed according to whether a first stored event identifier corresponding to a second event is stored locally when obtaining a first event identifier corresponding to a first event;

[0010] wherein the first event and the second event are related to the timing synchronization state of the terminal.

[0011] In a third aspect, a terminal is provided, which includes a processor and a memory. The memory stores programs or instructions that can run on the processor. When the programs or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0012] In a fourth aspect, a terminal is provided, including a processor and a communication interface. Wherein, the processor is configured to:

[0013] When obtaining a first event identifier corresponding to a first event, determine whether the timing synchronization state of the terminal changes according to whether a first stored event identifier corresponding to a second event is locally stored;

[0014] Wherein, the first event and the second event are related to the timing synchronization state of the terminal.

[0015] In a fifth aspect, a readable storage medium is provided. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the steps of the method described in the first aspect are implemented.

[0016] In a sixth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run programs or instructions to implement the steps of the method described in the first aspect.

[0017] In a seventh aspect, a computer program / program product is provided. The computer program / program product is stored in a storage medium. The program / program product is executed by at least one processor to implement the steps of the method described in the first aspect

[0018] In the embodiments of the present application, when the terminal obtains a first event identifier corresponding to a first event, the terminal can determine whether the timing synchronization state of the terminal changes according to whether a first stored event identifier corresponding to a second event is locally stored. Wherein, the first event and the second event are related to the timing synchronization state of the terminal. It can be seen that in the embodiments of the present application, if the terminal obtains a first event identifier corresponding to an event related to the timing synchronization state of the terminal, the terminal can determine whether the timing synchronization state of the terminal changes according to whether a first stored event identifier corresponding to an event related to the timing synchronization state of the terminal is locally stored. Therefore, the embodiments of the present application provide a method for the terminal to determine whether its timing synchronization state changes, enabling the terminal to timely learn and update the timing synchronization state, thereby ensuring that the terminal remains synchronized with the network side and improving the stability of timing synchronization. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0020] Figure 2 It is a flowchart of a method for determining the change of timing synchronization state in an embodiment of the present application;

[0021] Figure 3 It is a flowchart of Embodiment 1 of the method for determining the change of timing synchronization state implemented in the present application;

[0022] Figure 4 It is a flowchart of Embodiment 2 of the method for determining the change of timing synchronization state implemented in the present application;

[0023] Figure 5 It is a structural block diagram of a device for determining the change of timing synchronization state in an embodiment of the present application;

[0024] Figure 6 It is a structural block diagram of a communication device in an embodiment of the present application;

[0025] Figure 7 It is a structural block diagram of a terminal in an embodiment of the present application. Specific Embodiments

[0026] Next, the technical solutions in the embodiments of the present application will be clearly described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art belong to the scope of protection of the present application.

[0027] The terms "first", "second", etc. in the present application are used to distinguish similar objects, rather than to describe a specific order or sequence. It should be understood that such terms can be interchanged under appropriate circumstances so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are usually of the same category, and the number of objects is not limited. For example, the first object can be one or multiple. In addition, "or" in the present application means at least one of the connected objects. For example, "A or B" covers three scenarios, namely, Scenario 1: including A and not including B; Scenario 2: including B and not including A; Scenario 3: including both A and B. The character " / " generally indicates an "or" relationship between the associated objects before and after.

[0028] The term "indication" in this application can be either a direct indication (or an explicit indication) or an indirect indication (or an implicit indication). Among them, a direct indication can be understood as that the sender clearly tells the receiver specific information, operations to be performed, request results, etc. in the sent indication; an indirect indication can be understood as that the receiver determines the corresponding information according to the indication sent by the sender, or makes a judgment and determines the operations to be performed or request results, etc. according to the judgment result.

[0029] It should be noted that the technology described in the embodiments of this application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, and can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), or other systems. The terms "system" and "network" in the embodiments of this application are often used interchangeably, and the described technology can be used in the above-mentioned systems and radio technologies, as well as in other systems and radio technologies. The following description describes the New Radio (NR) system for example purposes, and the NR terms are used in most of the following descriptions, but these technologies can also be applied to systems other than the NR system, such as the 6th Generation (6G) communication system. th Generation, 6G) communication system.

[0030] Figure 1Block diagram of a wireless communication system to which embodiments of the present application can be applied. The wireless communication system includes a terminal 11 and a network-side device 12. Among them, the terminal 11 can be a mobile phone, a tablet personal computer, a laptop computer, a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device, a flight vehicle, a vehicle user equipment (VUE), a shipborne device, a pedestrian user equipment (PUE), a smart home (home devices with wireless communication functions, such as refrigerators, TVs, washing machines or furniture, etc.), a game console, a personal computer (PC), a teller machine or a self-service machine, etc. Wearable devices include: smart watches, smart bracelets, smart earphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart ankle chains, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle user equipment can also be called a vehicle terminal, a vehicle controller, a vehicle module, a vehicle component, a vehicle chip or a vehicle unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiments of the present application. The network-side device 12 can include an access network device or a core network device. Among them, the access network device can also be called a radio access network (RAN) device, a radio access network function or a radio access network unit. The access network device can include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), home Node B (HNB), home evolved Node B, Transmission Reception Point (TRP), or some other suitable term in the art. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of this application, only the base station in the NR system is taken as an example for introduction, and the specific type of the base station is not limited.

[0031] To facilitate the understanding of the method for determining the change in the timing synchronization state in the embodiments of this application, the following related technologies are introduced:

[0032] I. Non-Public Network (NPN)

[0033] 5G NPN is a private network constructed using 5G technology and independent of the Public Land Mobile Network (PLMN) that serves the public. 5G NPN supports two deployment modes, namely Stand-alone Non-Public Network (SNPN) and Public Network Integrated Non-Public Network (PNI-NPN). Among them, the stand-alone deployment of NPN does not depend on any network functions of the PLMN in implementation; the public network integrated deployment depends on the implementation of the public network.

[0034] In the 3GPP Release 16 protocol (R16), NPN is deployed using public network integration. Currently, the available method is to understand NPN as one or a group of slices / data network names (DNN) of the public network. Given that 5G Core Network (5GC) slices cannot restrict UE access on the Radio Access Network (RAN) side, it is necessary to divide a Closed Access Group (CAG) that NPN is allowed to access.

[0035] Among them, the CAG consists of a group of cell IDs. The UE can only access the NPN RAN within the area corresponding to the CAG. The RAN broadcasts PLMN + CAG ID, and access selection and control are performed based on the CAG. The CAG information is usually pre-configured in the UE and can be updated through the User Configuration Update (UCU) process.

[0036] R17 introduces stand-alone deployed NPN, which is identified by the combination of PLMN ID and Network identifier (NID). The PLMN operator can reuse its PLMN ID and use the NID to distinguish each private network, or use the PLMN ID reserved for private networks. The RAN broadcasts PLMN + NID. The UE of SNPN (i.e., stand-alone deployed NPN) is identified using the Subscription Permanent Identifier (SUPI). If the UE is set to the SNPN access mode, the UE can only access and register to the SNPN through the Uu air interface. When the UE performs initial registration, it will carry the PLMN ID and NID, and the 5G Radio Access Network (NG-RAN) will bring this information to the Access and Mobility Management Function (AMF). The subscription information of the user in the NPN includes Unified Access Control (UAC) information. In case of network congestion, the SNPN can prevent the UE from accessing.

[0037] II. R18 Enhancement of Timing Sensitive Communications (TSC)

[0038] To support communication services with highly reliable synchronous communication, etc., UEs in different Radio Resource Control (RRC) states can obtain the timing synchronization status or specific clock quality information in the following manner 1 or 2.

[0039] Manner 1: For a UE in the connected state (RRC_CONNECTED), the gNB uses dedicated RRC signaling, such as Downlink Information Transfer, to send the event identifier (EventID) of the occurrence of a timing synchronization status change and the clock quality information.

[0040] Manner 2: For a UE not in the RRC_CONNECTED state (i.e., in the RRC_INACTIVE state or the RRC_IDLE state), the UE first needs to establish or resume an RRC connection, and then obtain the clock quality information from the gNB through dedicated RRC signaling. Among them, the gNB broadcasts the Event ID in SIB9 to notify its timing synchronization status, and the gNB uses the change of the Event ID as a trigger condition to trigger a system message change to notify the UE to read the SIB information: to inform the UE that there is new timing synchronization status information available (or exists).

[0041] Among them, the scope of action of the Event ID is the gNB. That is, the change of the gNB ID can also be used as one of the conditions for the UE to consider that the time synchronization status has changed and establish or resume an RRC connection. However, the gNB itself does not broadcast the gNB ID, and the UE can obtain the gNB ID corresponding to the current cell through the cell identity information (CellIdentity, that is, the NR Cell Identifier, NCI) and the gNB identifier length (gNB-ID-Length) in SIB1.

[0042] III. RAN cell access related information

[0043] The first system information block SIB1 contains information related to cell access, including different types of networks supported by the cell, which may include a list of PLMN ID information and a list of NPN ID information.

[0044] IV. Base station / cell identifier differentiation

[0045] The Global gNB ID is used to globally identify the gNB. Among them, the Global gNB ID is composed of the PLMN identity information (Identity) to which the gNB belongs and the gNB ID.

[0046] The NR Cell Global Identifier (NCGI) is used to globally identify NR cells. The NCGI is composed of the PLMN Identity to which the cell belongs and the NR cell identity information NCI of the cell. The PLMN Identity included in the NCGI is the first PLMN Identity in the list of PLMN IDs associated with the cell identity information (CellIdentity) in SIB1 (used to uniquely identify a cell within a PLMN / SNPN) that follows the broadcast order.

[0047] Next, in conjunction with the accompanying drawings, the method for determining the change in the timing synchronization state provided by the embodiments of the present application will be described in detail through some embodiments and their application scenarios.

[0048] Embodiments of the present application provide a method for determining a change in the timing synchronization state, as Figure 2 shown. The method may include the following step 201:

[0049] Step 201: When the terminal obtains the first event identifier corresponding to the first event, the terminal determines whether the timing synchronization state of the terminal has changed according to whether the first storage event identifier corresponding to the second event is stored locally.

[0050] Among them, the first event and the second event are related to the timing synchronization state of the terminal. That is, the first event and the second event are respectively used to indicate a timing synchronization state of the terminal. It can also be understood that the first event and the second event both correspond to the 5G access layer time distribution parameters in the "clock quality report control information" from the core network device, enabling the terminal to obtain the timing synchronization state information of the terminal.

[0051] In addition, if the base station where the terminal camps supports timing synchronization, then the base station can provide the timing synchronization state by periodically broadcasting the event identifier (Event ID).

[0052] It can be seen that when the terminal obtains an Event ID, if the terminal does not store the Event ID locally, it means that the base station where the terminal previously camped did not support timing synchronization or did not provide the timing synchronization state, but now supports timing synchronization or provides the timing synchronization state. Therefore, when the terminal receives an Event ID, it can determine whether the timing synchronization state of the terminal has changed according to whether the Event ID is stored locally.

[0053] Optionally, the terminal obtaining the first event identifier includes:

[0054] The terminal obtains the first event identifier from the ninth system information block SIB9.

[0055] It can be seen therefrom that if the base station where the terminal camps supports timing synchronization, then the base station can provide the timing synchronization status by periodically broadcasting an event identifier (Event ID) in SIB9; in this way, the terminal can obtain the Event ID from the received SIB9 by receiving SIB9.

[0056] As can be seen from step 201 above, in the embodiment of the present application, when the terminal obtains the first event identifier corresponding to the first event, the terminal can determine whether the timing synchronization status of the terminal has changed according to whether the first storage event identifier corresponding to the second event is stored locally, where the first event and the second event are related to the timing synchronization status of the terminal. It can be seen that in the embodiment of the present application, if the terminal obtains the first event identifier corresponding to an event related to the timing synchronization status of the terminal, the terminal can determine whether the timing synchronization status of the terminal has changed according to whether the first storage event identifier corresponding to the event related to the timing synchronization status of the terminal is stored locally. Therefore, the embodiment of the present application provides a method for the terminal to determine whether its timing synchronization status has changed, enabling the terminal to timely learn and update the timing synchronization status, thereby ensuring that the terminal remains synchronized with the network side and improving the stability of timing synchronization. Optionally, in the above step 201, the terminal determining whether the timing synchronization status of the terminal has changed according to whether the first storage event identifier corresponding to the second event is stored locally includes the following steps A-1 to A-2:

[0057] Step A-1: When the first storage event identifier is not stored locally, the terminal determines that the timing synchronization status of the terminal has changed;

[0058] Step A-2: When the first storage event identifier is stored locally, the terminal determines whether the timing synchronization status of the terminal has changed according to the first event identifier and the first storage event identifier.

[0059] As described above, if the terminal does not store the Event ID locally when obtaining an Event ID, it means that the base station where the terminal previously camped did not support timing synchronization or did not provide the timing synchronization status, but now supports timing synchronization or provides the timing synchronization status. Therefore, in step A-1, if the first storage event identifier is not stored locally at the terminal, it means that the timing synchronization status of the terminal has changed.

[0060] In addition, an Event ID is used to indicate a timing synchronization state of a terminal, that is, different Event IDs are used to indicate different timing synchronization states of the terminal. That is, within a period of time, if the timing synchronization state corresponding to the base station where the terminal camps does not change, the Event IDs broadcast by the base station in N cycles within this period of time are the same; if the timing synchronization state corresponding to the base station changes, the base station broadcasts different Event IDs during this period. Therefore, in step A-2, if the terminal locally stores a first stored event identifier, the terminal can determine whether the timing synchronization state of the terminal has changed by comparing the first event identifier with the first stored event identifier.

[0061] Optionally, in the above step A-2, the terminal determines whether the timing synchronization state of the terminal has changed according to the first event identifier and the first stored event identifier, including the following steps B-1 to B-2:

[0062] Step B-1: When the first event identifier is different from the first stored event identifier, the terminal determines that the timing synchronization state of the terminal has changed;

[0063] Step B-2: When the first event identifier is the same as the first stored event identifier, the terminal determines whether the timing synchronization state of the terminal has changed according to the identification information of the current serving base station of the terminal and the identification information of the serving base station stored locally by the terminal.

[0064] As described above, if the base station where the terminal camps supports timing synchronization, then this base station can periodically broadcast an event identifier (Event ID) to notify its timing synchronization state; and, if the timing synchronization state of the base station changes, the Event ID broadcast by the base station will change; and, if the timing synchronization state of the base station changes, the timing synchronization state of the terminal will change accordingly; therefore, in step B-1, if the first event identifier currently obtained by the terminal is different from the first stored event identifier stored locally by the terminal, it means that the timing synchronization state of the terminal has changed.

[0065] In addition, it should be noted that the scope of action of the Event ID is a base station. That is, when the base station where the terminal camps changes, and both the base station where the terminal camped before the change and the base station where the terminal camps after the change support timing synchronization, then, before and after the change, even if the Event ID received by the terminal may be the same, in this case, since the base station where the terminal camps has changed, the timing synchronization state of the terminal will also change accordingly. Therefore, in step B-2, if the first event identifier currently obtained by the terminal is the same as the first stored event identifier stored locally in the terminal, the terminal needs to further compare the identifier information of the base station where the terminal currently camps with the identifier information of the base station where the terminal camps stored locally in the terminal to determine whether the timing synchronization state of the terminal has changed.

[0066] Optionally, the identifier information of the base station where the terminal currently camps includes a first base station identifier, and the identifier information of the base station where the terminal camps stored locally in the terminal includes a first stored base station identifier, and both the first base station identifier and the first stored base station identifier belong to the global base station identifier;

[0067] In the above step B-2, the terminal determines whether the timing synchronization state of the terminal has changed according to the identifier information of the base station where the terminal currently camps and the identifier information of the base station where the terminal camps stored locally in the terminal, including the following steps C-1 to C-2:

[0068] Step C-1: When the first base station identifier is the same as the first stored base station identifier, the terminal determines that the timing synchronization state of the terminal has not changed;

[0069] Step C-2: When the first base station identifier is different from the first stored base station identifier, the terminal determines that the timing synchronization state of the terminal has changed.

[0070] Among them, when the base station where the terminal camps changes, the terminal will consider that the timing synchronization state has changed. Among them, the gNB ID is valid within a PLMN; that is, different gNBs in different PLMNs may be assigned the same gNB ID. In this case, although the gNB ID has not changed, the actual gNB has changed. Therefore, the UE cannot know whether the gNB where the terminal camps has changed by simply comparing the gNB ID, and thus cannot timely determine whether the timing synchronization state has changed.

[0071] The global base station identifier globally identifies a base station, that is, the global base station identifiers of each base station are different. Therefore, in the above steps C-1 and C-2, by comparing the global base station identifier of the base station where the terminal currently camps (i.e., the first base station identifier) with the global base station identifier of the base station where the terminal camps and is locally stored (i.e., the first stored base station identifier), it can be accurately determined whether the base station where the terminal camps has changed, and further, it can be accurately determined whether the timing synchronization state of the terminal has changed.

[0072] Optionally, the first stored event identifier is stored in a first local variable, and the first stored base station identifier is stored in a second local variable; the method further includes one of the following D-1 to D-3:

[0073] Item D-1: When the first stored event identifier is not locally stored (i.e., when the first local variable does not store any content), the terminal uses the first event identifier as the second stored event identifier, updates the stored content of the first local variable to the second stored event identifier (i.e., stores the second stored event identifier as the stored content of the first local variable, that is, updates the stored content of the first local variable to the first event identifier), uses the first base station identifier as the second stored base station identifier, and updates the stored content of the second local variable to the second stored base station identifier (i.e., stores the second stored base station identifier as the stored content of the second local variable or replaces the stored content of the second local variable with the second stored base station identifier, that is, updates the stored content of the second local variable to the first base station identifier);

[0074] It can be understood that the first local variable is used to store an event identifier related to the timing synchronization state of the terminal, that is, the first local variable is used to store an event identifier for indicating the timing synchronization state of the terminal; the second local variable is used to store the global base station identifier of the base station where the terminal camps.

[0075] Moreover, as described above, if the first stored event identifier is not locally stored in the terminal, it means that the base station where the terminal previously camped does not support timing synchronization or does not provide a timing synchronization state, but now supports timing synchronization or provides a timing synchronization state (i.e., the timing synchronization state of the terminal has changed). Therefore, in item D-1, if the first local variable in the terminal locally does not store any content, the first local variable and the second local variable need to be updated.

[0076] Item D-2: When the first event identifier is different from the first stored event identifier, the terminal uses the first event identifier as the third stored event identifier, updates the stored content of the first local variable to the third stored event identifier (i.e., stores the third stored event identifier as the stored content of the first local variable, which is also to update the stored content of the first local variable to the first event identifier), uses the first base station identifier as the third stored base station identifier, and updates the stored content of the second local variable to the third stored base station identifier (i.e., replaces the stored content of the second local variable with the third stored base station identifier, which is also to update the stored content of the second local variable to the first base station identifier).

[0077] It should be noted that the difference between the first event identifier and the first stored event identifier does not directly prove whether the base station where the terminal camps has changed; in order to make the stored content of the local variable correspond to the camped cell, in addition to updating the first local variable, the terminal also needs to update the second local variable. Therefore, in Item D-2, if the first event identifier is different from the first stored event identifier, the first local variable and the second local variable need to be updated.

[0078] Item D-3: When the first base station identifier is different from the first stored base station identifier, the terminal uses the first base station identifier as the fourth stored base station identifier and updates the stored content of the second local variable to the fourth stored base station identifier (i.e., replaces the stored content of the second local variable with the fourth stored base station identifier, which is also to update the stored content of the second local variable to the first base station identifier).

[0079] It should be noted that the difference between the first base station identifier and the first stored base station identifier is caused by the change of the base station where the terminal camps; therefore, in Item D-3, if the first base station identifier is different from the first stored base station identifier, the second local variable needs to be updated.

[0080] Optionally, the identification information of the base station where the terminal currently camps includes a first local base station identifier and a first network identifier, and the identification information of the base station where the terminal locally stores the camped cell includes a first stored local base station identifier and a first stored network identifier;

[0081] In the above step B-2, the terminal determines whether the timing synchronization state of the terminal has changed according to the identification information of the base station where the terminal currently camps and the identification information of the base station where the terminal locally stores the camped cell, including the following steps E-1 to E-2:

[0082] Step E-1: When the first local base station identifier is the same as the first stored local base station identifier and the first network identifier is the same as the first stored network identifier, the terminal determines that the timing synchronization state of the terminal has not changed;

[0083] Step E-2: When the first local base station identifier is different from the first stored local base station identifier, or the first network identifier is different from the first stored network identifier, the terminal determines that the timing synchronization state of the terminal has changed.

[0084] Among them, when the base station where the terminal camps changes, the terminal will consider that the timing synchronization state has changed. Among them, the gNB ID is valid within a PLMN; that is, different gNBs in different PLMNs may be assigned the same gNB ID. In this case, although the gNB ID has not changed, the actual gNB has changed. Therefore, the UE cannot know whether the gNB where the terminal camps has changed by simply comparing the gNB ID, and thus cannot determine in time whether the timing synchronization state has changed.

[0085] The global base station identifier globally identifies the base station, that is, the global base station identifier of each base station is different, and the global base station identifier is composed of the network identifier and the local base station identifier. Therefore, in the above steps D-1 and D-2, by comparing the network identifier (i.e., the first network identifier) and the local base station identifier (i.e., the first local base station identifier) of the current serving base station of the terminal, and the network identifier (i.e., the first stored network identifier) and the local base station identifier (i.e., the first stored local base station identifier) of the serving base station stored locally by the terminal, it can be accurately determined whether the serving base station of the terminal has changed, and further it can be accurately determined whether the timing synchronization state of the terminal has changed.

[0086] It should be noted that in this article, the order of the process of comparing the first network identifier with the first stored network identifier and the process of comparing the first local base station identifier with the first stored local base station identifier is not specifically limited.

[0087] Optionally, the first stored local base station identifier is stored in the third local variable, and the first stored network identifier is stored in the fourth local variable; the method further includes one of the following F-1 to F-4:

[0088] Item F-1: In the case where the first storage event identifier is not stored locally (i.e., when the first local variable does not store content), the terminal uses the first event identifier as the second storage event identifier, updates the stored content of the first local variable to the second storage event identifier (i.e., stores the second storage event identifier as the stored content of the first local variable, that is, updates the stored content of the first local variable to the first event identifier), uses the first local base station identifier as the second storage local base station identifier, and updates the stored content of the third local variable to the second storage local base station identifier (i.e., stores the second storage local base station identifier as the stored content of the third local variable or replaces the stored content of the third local variable with the second storage local base station identifier, that is, updates the stored content of the third local variable to the first local base station identifier), uses the first network identifier as the second storage network identifier, and updates the stored content of the fourth local variable to the second storage network identifier (i.e., stores the second storage network identifier as the stored content of the fourth local variable or replaces the stored content of the fourth local variable with the second storage network identifier, that is, updates the stored content of the fourth local variable to the first network identifier);

[0089] It can be understood that the first local variable is used to store the event identifier related to the timing synchronization status of the terminal, that is, the first local variable is used to store the event identifier indicating the timing synchronization status of the terminal; the third local variable is used to store the local base station identifier of the resident base station of the terminal; the fourth local variable is used to store the network identifier of the resident base station of the terminal.

[0090] Moreover, as mentioned above, the fact that the first storage event identifier is not stored locally in the terminal means that the base station where the terminal previously resided does not support timing synchronization or does not provide the timing synchronization status, but now supports timing synchronization or provides the timing synchronization status (i.e., the timing synchronization status of the terminal has changed). Therefore, in Item F-1, if the first local variable in the terminal locally does not store content, it is necessary to update the first local variable, the third local variable, and the fourth local variable.

[0091] Item F-2: When the first event identifier is different from the first stored event identifier, the terminal uses the first event identifier as the third stored event identifier, updates the stored content of the first local variable to the third stored event identifier (i.e., stores the third stored event identifier as the stored content of the first local variable, which is also to update the stored content of the first local variable to the first event identifier), uses the first local base station identifier as the third stored local base station identifier, and updates the stored content of the third local variable to the third stored local base station identifier (i.e., replaces the stored content of the third local variable with the third stored local base station identifier, which is also to update the stored content of the third local variable to the first local base station identifier), uses the first network identifier as the third stored network identifier, and updates the stored content of the fourth local variable to the third stored network identifier (i.e., replaces the stored content of the fourth local variable with the third stored network identifier, which is also to update the stored content of the fourth local variable to the first network identifier).

[0092] It should be noted that the difference between the first event identifier and the first stored event identifier cannot directly prove whether the base station where the terminal camps has changed; and in order to make the stored content of the local variable correspond to the camped cell, in addition to updating the first local variable, the terminal also needs to update the third local variable and the fourth local variable. Therefore, in Item F-2, if the first event identifier is different from the first stored event identifier, the first local variable, the third local variable, and the fourth local variable need to be updated.

[0093] Item F-3: When the first local base station identifier is different from the first stored local base station identifier, the terminal uses the first local base station identifier as the fourth stored local base station identifier, and updates the stored content of the third local variable to the fourth stored local base station identifier (i.e., replaces the stored content of the third local variable with the fourth stored local base station identifier, which is also to update the stored content of the third local variable to the first local base station identifier).

[0094] It should be noted that the difference between the first local base station identifier and the first stored local base station identifier is caused by the change of the base station where the terminal camps; therefore, in Item F-3, if the first local base station identifier is different from the first stored local base station identifier, the third local variable needs to be updated.

[0095] Item F-4: When the first network identifier is different from the first stored network identifier, the terminal uses the first network identifier as the fourth stored network identifier, and updates the stored content of the fourth local variable to the fourth stored network identifier (i.e., replaces the stored content of the fourth local variable with the fourth stored network identifier, which is also to update the stored content of the fourth local variable to the first network identifier).

[0096] It should be noted that the first network identifier is different from the first storage network identifier, which is caused by the change of the network where the base station where the terminal resides is located; therefore, in item F-4, if the first network identifier is different from the first storage network identifier, the fourth local variable needs to be updated.

[0097] Optionally, the identification information of the current serving base station of the terminal is determined according to the target network identification information, and the target network identification information is determined according to the support situation of the network where the terminal resides for the Public Land Mobile Network (PLMN) and the Non-Public Network (NPN).

[0098] Among them, the target identification information is included in SIB1. That is, according to the support situation of the network where the terminal resides for PLMN and NPN, it can be determined which information in SIB1 the target identification information includes.

[0099] Optionally, the target network identification information satisfies one of the following items G-1 to G-3:

[0100] Item G-1: When the network where the terminal resides only supports PLMN, the target network identification information includes the first object in the PLMN Identity Information List (PLMN-IdentityInfoList) in the first system information block SIB1, and the first object is the first PLMN identity information (PLMN-IdentityInfo) in the PLMN Identity Information List that follows the broadcast order;

[0101] It can be seen from item G-1 that when the network where the terminal resides only supports PLMN, the target network identification information includes the first PLMN-IdentityInfo in the PLMN-IdentityInfoList in SIB1 that follows the broadcast order (i.e., the first PLMN-IdentityInfo broadcast).

[0102] Item G-2: When the network where the terminal resides supports the sharing of PLMN and NPN, the target network identification information includes the first object in the PLMN Identity Information List in SIB1;

[0103] It can be seen from item G-2 that when the network where the terminal resides supports the sharing of PLMN and NPN, the target network identification information includes the first PLMN-IdentityInfo in the PLMN-IdentityInfoList in SIB1 that follows the broadcast order (i.e., the first PLMN-IdentityInfo broadcast).

[0104] Item G-3: When the network where the terminal camps supports NPN, the target network identification information includes the second object in the NPN-IdentityInfoList in SIB1, and the second object is the first NPN-IdentityInfo in the NPN-IdentityInfoList that follows the broadcast order.

[0105] As can be seen from Item G-3, when the network where the terminal camps supports NPN, the target network identification information includes the first NPN-IdentityInfo (i.e., the first NPN-IdentityInfo to be broadcast) in the NPN-IdentityInfoList in SIB1 that follows the broadcast order.

[0106] It should be noted that SIB1 includes information related to cell access; the information related to cell access includes PLMN-IdentityInfoList and NPN-IdentityInfoList, PLMN-IdentityInfoList includes multiple PLMN-IdentityInfo, and NPN-IdentityInfoList includes multiple NPN-IdentityInfo.

[0107] Optionally, the identification information of the base station where the terminal currently camps includes a first base station identification, and the first base station identification is determined according to a first network identification and a first local base station identification; or, the identification information of the base station where the terminal currently camps includes the first network identification and the first local base station identification;

[0108] Among them, the first network identification and the first local base station identification satisfy one of the following H-1 to H-3:

[0109] Item H-1: When the network where the terminal camps only supports PLMN, the first network identification is the first PLMN identification in the first object, and the first local base station identification is determined according to the first object;

[0110] Item H-2: When the network where the terminal camps supports the sharing of PLMN and non-public network NPN, the first network identification is the first PLMN identification in the first object, and the first local base station identification is determined according to the first object;

[0111] Item H-3: When the network where the terminal camps supports NPN, the first network identification is the PLMN identification included in the first NPN identification in the second object, and the first local base station identification is determined according to the second object.

[0112] As described above, the identification information of the base station where the terminal currently camps may include a first base station identifier (which belongs to the global base station identifier), or may also include a first network identifier and a first local base station identifier.

[0113] Among them, when the identification information of the base station where the terminal currently camps includes the first base station identifier, the first base station identifier is determined according to the first network identifier and the first local base station identifier. For example, a first base station identifier is obtained by combining a first network identifier and a first local base station identifier.

[0114] In addition, as described above, the identification information of the base station where the terminal currently camps is determined according to the target network identification information. Therefore, the above-mentioned first network identifier and first local base station identifier are determined according to the target network information.

[0115] Specifically, from the above items G-1 and H-1, in the case where the network where the terminal camps only supports PLMN, the first network identifier is the first PLMN identifier (PLMN-identity) in the first PLMN-IdentityInfo in the PLMN-IdentityInfoList in SIB1 that follows the broadcast order, and the first local base station identifier is determined according to the first PLMN-IdentityInfo in the PLMN-IdentityInfoList in SIB1 that follows the broadcast order;

[0116] From the above items G-2 and H-2, in the case where the network where the terminal camps supports the sharing of PLMN and NPN, the first network identifier is the first PLMN identifier (PLMN-identity) in the first PLMN-IdentityInfo in the PLMN-IdentityInfoList in SIB1 that follows the broadcast order, and the first local base station identifier is determined according to the first PLMN-IdentityInfo in the PLMN-IdentityInfoList in SIB1 that follows the broadcast order;

[0117] From the above items G-3 and H-3, in the case where the network where the terminal camps supports NPN, the first network identifier is the PLMN identifier (PLMN-Identity) included in the first NPN identifier (NPN-Identity) in the first NPN-IdentityInfo in the NPN-IdentityInfoList in SIB1 that follows the broadcast order, and the first local base station identifier is determined according to the first PLMN-IdentityInfo in the PLMN-IdentityInfoList in SIB1 that follows the broadcast order.

[0118] In addition, if the target network identification information (such as the PLMN-IdentityInfo described in item G-1 or G-2 above, or the NPN-IdentityInfo described in item G-3) includes cell identification information (CellIdentity) and base station identification length (Gnb-ID-length), then determining the first local base station identification according to the target network identification information may include:

[0119] Determine the first local base station identification according to the CellIdentity and Gnb-ID-length in the target network identification information.

[0120] The specific implementation manner of determining the first local base station identification according to the target network identification information may be, for example:

[0121] Optionally, the high X bits of CellIdentity may be used as the first local base station identification, where X is equal to Gnb-ID-length. For example, if CellIdentity consists of 32 bits and Gnb-ID-length is 22 bits, then the high 22 bits of CellIdentity are the first local base station identification.

[0122] Optionally, the method further includes:

[0123] When it is determined that the timing synchronization state of the terminal has changed, the access stratum of the terminal notifies the non-access stratum that the target information has changed;

[0124] Wherein, the target information includes at least one of clock quality information and timing synchronization state information.

[0125] It can be seen from this that if the timing synchronization state of the terminal changes, the access stratum (AS) of the terminal can notify the non-access stratum (NAS): at least one of the clock quality information and the timing synchronization state information has changed.

[0126] In summary, the specific implementation manner of the method for determining the change of the timing synchronization state in the embodiments of the present application may be implemented as described in Embodiment 1 or Embodiment 2 below:

[0127] Embodiment 1: The UE maintains two local variables, corresponding to an event identifier and a global base station identifier respectively; that is, the first local variable is used to store the identifier of the event related to the timing synchronization state of the UE; the second local variable is used to store the global base station identifier of the base station where the UE camps; as Figure 3 shown, the specific execution process of the UE is as described below:

[0128] Step 301: Obtain a first event identifier from SIB9, and determine a first base station identifier of the terminal's current serving base station according to the information obtained from SIB1; wherein, the first base station identifier belongs to the global base station identifier.

[0129] It can be understood that the execution order of the process of obtaining the first event identifier from SIB9 and the process of determining the first base station identifier of the terminal's current serving base station according to the information obtained from SIB1 is not specifically limited here.

[0130] The AS layer of the UE performs the following steps:

[0131] Step 302: Determine whether the first local variable stores content; if the first local variable does not store content (that is, the base station coverage area where the UE was last located does not support / does not provide the time synchronization status, but now supports / provides the time synchronization status), then execute Step 303; if the first local variable stores the first stored event identifier, then execute Step 304.

[0132] Step 303: Determine that the timing synchronization status has changed, and notify the NAS layer that the target information has changed; update the first local variable and the second local variable (that is, use the first event identifier as the second stored event identifier, and store the second stored event identifier as the stored content of the first local variable; use the first base station identifier as the second stored base station identifier, and store the second stored base station identifier as the stored content of the second local variable, or replace the stored content of the second local variable with the second stored base station identifier); wherein, the target information may include at least one of the content of the clock quality details and the timing synchronization status information.

[0133] Step 304: Determine whether the values of the first event identifier and the first stored event identifier are equal; if the value of the first event identifier is not equal to the value of the first stored event identifier, then execute Step 305; if the value of the first event identifier is equal to the value of the first stored event identifier, then execute Step 306.

[0134] Step 305: Determine that the timing synchronization status has changed, and notify the NAS layer that the target information has changed; update the first local variable and the second local variable (that is, use the first event identifier as the third stored event identifier, and replace the stored content of the first local variable with the third stored event identifier; use the first base station identifier as the third stored base station identifier, and replace the stored content of the second local variable with the third stored base station identifier).

[0135] Step 306: Determine whether the value of the first base station identifier is equal to the value of the first stored base station identifier stored in the second local variable; if the value of the first base station identifier is equal to the value of the first stored base station identifier, then execute Step 307; if the value of the first base station identifier is not equal to the value of the first stored base station identifier, then execute Step 308.

[0136] Step 307: Determine that the timing synchronization status has not changed;

[0137] Step 308: Determine that the timing synchronization status has changed, notify the NAS layer that the target information has changed; update the second local variable (i.e., use the first base station identifier as the fourth stored base station identifier, and replace the stored content of the second local variable with the fourth stored base station identifier).

[0138] Wherein, the UE determines the above-mentioned first base station identifier according to the first network identifier and the first local base station identifier; for example, a first network identifier and a first local base station identifier are combined to obtain a first base station identifier; wherein, the first network identifier and the first local base station identifier are determined according to the information in SIB1;

[0139] In addition, the first network identifier satisfies one of the following:

[0140] When the network only supports PLMN or supports the sharing of PLMN and NPN, the first network identifier is: the first PLMN identifier (PLMN-identity) in the first PLMN identifier information (PLMN-IdentityInfo) that follows the broadcast order in the PLMN identifier information list (PLMN-IdentityInfoList) in SIB1;

[0141] When the network only supports NPN, the first network identifier is: the PLMN identifier (PLMN-Identity) included in the first NPN identifier (NPN-Identity) in the first NPN identifier information (NPN-IdentityInfo) that follows the broadcast order in the NPN identifier information list (NPN-IdentityInfoList) in SIB1.

[0142] Correspondingly, the first local base station identifier is determined according to the target identifier information. For example, take the high X bits of the cell identifier information (CellIdentity) in the target identifier information as the first local base station identifier, where X is the Gnb-ID-length in the target identifier information; the target identifier information satisfies one of the following:

[0143] When the network only supports PLMN or the network supports the sharing of PLMN and NPN, the target identifier information is: the first PLMN identifier information (PLMN-IdentityInfo) that follows the broadcast order in the PLMN identifier information list (PLMN-IdentityInfoList) in SIB1;

[0144] When the network only supports NPN, the target identification information is: the first NPN identification information (NPN-IdentityInfo) in the NPN identification information list (NPN-IdentityInfoList) in SIB1 that follows the broadcast order.

[0145] Embodiment 2: The UE maintains three local variables, which respectively correspond to an event identifier, a local base station identifier, and a network identifier; that is, the first local variable is used to store the identifier of an event related to the timing synchronization state of the UE; the third local variable is used to store the local base station identifier of the base station where the UE camps, and the fourth local variable is used to store the network identifier of the base station where the UE camps; as Figure 4 shown, the specific execution process of the UE is as described below:

[0146] Step 401: Obtain the first event identifier from SIB9, and determine the first local base station identifier and the first network identifier of the current base station where the terminal camps according to the information obtained from SIB1; wherein, the first base station identifier belongs to the global base station identifier.

[0147] It can be understood that the execution order of the process of obtaining the first event identifier from SIB9 and the process of determining the first local base station identifier and the first network identifier of the current base station where the terminal camps according to the information obtained from SIB1 is not specifically limited here.

[0148] It should be noted that if the base station broadcasts the event ID in SIB9, it must include the gNB-ID-Length in SIB1. That is, from the perspective of the terminal, if it receives the event identifier in SIB9, it can definitely obtain the local base station identifier through SIB1 (including the Cell identity and gNB-ID-Length).

[0149] The AS layer of the UE executes the following steps:

[0150] Step 402: Determine whether the first local variable stores content; if the first local variable does not store content (that is, the coverage area of the base station where the UE was last located does not support / does not provide the time synchronization state, and now it supports / provides the time synchronization state), then execute Step 403; if the first local variable stores the first stored event identifier, then execute Step 404;

[0151] Step 403: Determine that the timing synchronization status has changed, and notify the NAS layer that the target information has changed; update the first local variable, the third local variable, and the fourth local variable; (that is, use the first event identifier as the second stored event identifier, and store the second stored event identifier as the stored content of the first local variable; use the first local base station identifier as the second stored local base station identifier, and store the second stored local base station identifier as the stored content of the third local variable, or replace the stored content of the third local variable with the second stored local base station identifier; use the first network identifier as the second stored network identifier, and store the second stored network identifier as the stored content of the fourth local variable, or replace the stored content of the fourth local variable with the second stored network identifier); where the target information may include at least one of the content of the clock quality details and the timing synchronization status information.

[0152] Step 404: Determine whether the values of the first event identifier and the first stored event identifier are equal; if the value of the first event identifier is not equal to the value of the first stored event identifier, then execute Step 405; if the value of the first event identifier is equal to the value of the first stored event identifier, then execute Step 406:

[0153] Step 405: Determine that the timing synchronization status has changed, and notify the NAS layer that the target information has changed; update the first local variable, the third local variable, and the fourth local variable; (that is, use the first event identifier as the third stored event identifier, and replace the stored content of the first local variable with the third stored event identifier; use the first local base station identifier as the third stored local base station identifier, and replace the stored content of the third local variable with the third stored local base station identifier, use the first network identifier as the third stored network identifier, and replace the stored content of the fourth local variable with the third stored network identifier);

[0154] Step 406: Determine whether the value of the first local base station identifier is equal to the value of the first stored local base station identifier stored in the third local variable, and whether the value of the first network identifier is equal to the value of the first stored network identifier stored in the fourth local variable; if the value of the first local base station identifier is equal to the value of the first local stored base station identifier, and the value of the first network identifier is equal to the value of the first stored network identifier, then execute Step 407; if the value of the first local base station identifier is not equal to the value of the first stored local base station identifier, then execute Step 408; if the value of the first network identifier is not equal to the value of the first stored network identifier, then execute Step 409;

[0155] Step 407: Determine that the timing synchronization status has not changed;

[0156] Step 408: Determine that the timing synchronization status has changed, notify the NAS layer that the target information has changed; update the third local variable (i.e., use the first local base station identifier as the fourth stored local base station identifier, and replace the stored content of the third local variable with the fourth stored local base station identifier).

[0157] Step 409: Determine that the timing synchronization status has changed, notify the NAS layer that the target information has changed; update the fourth local variable (i.e., use the first network identifier as the fourth stored network identifier, and replace the stored content of the fourth local variable with the fourth stored network identifier).

[0158] Among them, the above first network identifier satisfies one of the following:

[0159] When the network only supports PLMN or supports the sharing of PLMN and NPN, the first network identifier is: the first PLMN identifier (PLMN-identity) in the first PLMN identifier information (PLMN-IdentityInfo) following the broadcast order in the PLMN identifier information list (PLMN-IdentityInfoList) in SIB1;

[0160] When the network only supports NPN, the first network identifier is: the PLMN identifier (PLMN-Identity) included in the first NPN identifier (NPN-Identity) in the first NPN identifier information (NPN-IdentityInfo) following the broadcast order in the NPN identifier information list (NPN-IdentityInfoList) in SIB1.

[0161] Correspondingly, the first local base station identifier is determined according to the target identifier information. For example, take the high X bits of the cell identifier information (CellIdentity) in the target identifier information as the first local base station identifier, where X is the Gnb-ID-length in the target identifier information; the target identifier information satisfies one of the following:

[0162] When the network only supports PLMN or the network supports the sharing of PLMN and NPN, the target identifier information is: the first PLMN identifier information (PLMN-IdentityInfo) following the broadcast order in the PLMN identifier information list (PLMN-IdentityInfoList) in SIB1;

[0163] When the network only supports NPN, the target identifier information is: the first NPN identifier information (NPN-IdentityInfo) following the broadcast order in the NPN identifier information list (NPN-IdentityInfoList) in SIB1.

[0164] In the method for determining the change of the timing synchronization state provided by the embodiments of the present application, the executing entity may be a device for determining the change of the timing synchronization state. In the embodiments of the present application, taking the device for determining the change of the timing synchronization state executing the method for determining the change of the timing synchronization state as an example, the device for determining the change of the timing synchronization state provided by the embodiments of the present application is described.

[0165] As Figure 5 shown, the embodiments of the present application further provide a device for determining the change of the timing synchronization state. The device 50 for determining the change of the timing synchronization state may include the following modules:

[0166] A determination module 501, configured to determine whether the timing synchronization state of the terminal changes according to whether the first storage event identifier corresponding to the second event is stored locally when the first event identifier corresponding to the first event is obtained;

[0167] wherein, the first event and the second event are related to the timing synchronization state of the terminal.

[0168] Optionally, the determination module 501 includes:

[0169] A first determination sub-module, configured to determine that the timing synchronization state of the terminal changes when the first storage event identifier is not stored locally;

[0170] A second determination sub-module, configured to determine whether the timing synchronization state of the terminal changes according to the first event identifier and the first storage event identifier when the first storage event identifier is stored locally.

[0171] Optionally, the second determination sub-module includes:

[0172] A first determination unit, configured to determine that the timing synchronization state of the terminal changes when the first event identifier is different from the first storage event identifier;

[0173] A second determination unit, configured to determine whether the timing synchronization state of the terminal changes according to the identifier information of the serving base station where the terminal is currently located and the identifier information of the serving base station stored locally by the terminal when the first event identifier is the same as the first storage event identifier.

[0174] Optionally, the identifier information of the serving base station where the terminal is currently located includes a first base station identifier, and the identifier information of the serving base station stored locally by the terminal includes a first stored base station identifier, and both the first base station identifier and the first stored base station identifier belong to the global base station identifier;

[0175] The second determination unit is specifically configured to:

[0176] When the first base station identifier is the same as the first stored base station identifier, it is determined that the timing synchronization state of the terminal has not changed;

[0177] When the first base station identifier is different from the first stored base station identifier, it is determined that the timing synchronization state of the terminal has changed.

[0178] Optionally, the first stored event identifier is stored in a first local variable, and the first stored base station identifier is stored in a second local variable;

[0179] The apparatus further includes at least one of the following modules:

[0180] A first update module, configured to, when the first stored event identifier is not stored locally, use the first event identifier as a second stored event identifier, update the stored content of the first local variable to the second stored event identifier, use the first base station identifier as a second stored base station identifier, and update the stored content of the second local variable to the second stored base station identifier;

[0181] A second update module, configured to, when the first event identifier is different from the first stored event identifier, use the first event identifier as a third stored event identifier, update the stored content of the first local variable to the third stored event identifier, use the first base station identifier as a third stored base station identifier, and update the stored content of the second local variable to the third stored base station identifier;

[0182] A third update module, configured to, when the first base station identifier is different from the first stored base station identifier, use the first base station identifier as a fourth stored base station identifier, and update the stored content of the second local variable to the fourth stored base station identifier.

[0183] Optionally, the identification information of the base station where the terminal currently camps includes a first local base station identifier and a first network identifier, and the identification information of the base station where the terminal stores locally includes a first stored local base station identifier and a first stored network identifier;

[0184] The second determination unit is specifically configured to:

[0185] When the first local base station identifier is the same as the first stored local base station identifier and the first network identifier is the same as the first stored network identifier, it is determined that the timing synchronization state of the terminal has not changed;

[0186] In the case where the first local base station identifier is different from the first stored local base station identifier, or the first network identifier is different from the first stored network identifier, it is determined that the timing synchronization state of the terminal has changed.

[0187] Optionally, the first stored local base station identifier is stored in a third local variable, and the first stored network identifier is stored in a fourth local variable;

[0188] The apparatus further includes at least one of the following modules:

[0189] A fourth update module, configured to, when the first stored event identifier is not stored locally, use the first event identifier as a second stored event identifier, update the stored content of the first local variable to the second stored event identifier, use the first local base station identifier as a second stored local base station identifier, update the stored content of the third local variable to the second stored local base station identifier, use the first network identifier as a second stored network identifier, and update the stored content of the fourth local variable to the second stored network identifier;

[0190] A fifth update module, configured to, when the first event identifier is different from the first stored event identifier, use the first event identifier as a third stored event identifier, update the stored content of the first local variable to the third stored event identifier, use the first local base station identifier as a third stored local base station identifier, update the stored content of the third local variable to the third stored local base station identifier, use the first network identifier as a third stored network identifier, and update the stored content of the fourth local variable to the third stored network identifier;

[0191] A sixth update module, configured to, when the first local base station identifier is different from the first stored local base station identifier, use the first local base station identifier as a fourth stored local base station identifier, and update the stored content of the third local variable to the fourth stored local base station identifier;

[0192] A seventh update module, configured to, when the first network identifier is different from the first stored network identifier, use the first network identifier as a fourth stored network identifier, and update the stored content of the fourth local variable to the fourth stored network identifier.

[0193] Optionally, the identification information of the base station where the terminal currently camps is determined according to target network identification information, and the target network identification information is determined according to the support situation of the network where the terminal camps for a public land mobile network (PLMN) and a non-public network (NPN).

[0194] Optionally, the target network identification information satisfies one of the following:

[0195] When the network where the terminal camps only supports PLMN, the target network identification information includes the first object in the PLMN identification information list in the first system information block SIB1, and the first object is the first PLMN identification information following the broadcast order in the PLMN identification information list;

[0196] When the network where the terminal camps supports the sharing of PLMN and NPN, the target network identification information includes the first object in the PLMN identification information list in SIB1;

[0197] When the network where the terminal camps supports NPN, the target network identification information includes the second object in the NPN identification information list in SIB1, and the second object is the first NPN identification information following the broadcast order in the NPN identification information list.

[0198] Optionally, the identification information of the base station where the terminal currently camps includes a first base station identification, and the first base station identification is determined according to a first network identification and a first local base station identification; or, the identification information of the base station where the terminal currently camps includes the first network identification and the first local base station identification;

[0199] Wherein, when the network where the terminal camps only supports PLMN, the first network identification is the first PLMN identification in the first object, and the first local base station identification is determined according to the first object;

[0200] When the network where the terminal camps supports the sharing of PLMN and a non-public network NPN, the first network identification is the first PLMN identification in the first object, and the first local base station identification is determined according to the first object;

[0201] When the network where the terminal camps supports NPN, the first network identification is the PLMN identification included in the first NPN identification in the second object, and the first local base station identification is determined according to the second object.

[0202] Optionally, the device further includes:

[0203] A notification module, configured to notify that the non-access stratum target information of the terminal has changed when it is determined that the timing synchronization state of the terminal has changed;

[0204] Wherein, the target information includes at least one of clock quality information and timing synchronization state information.

[0205] Optionally, the device further includes:

[0206] An acquisition module, configured to acquire the first event identifier from the ninth system information block SIB9.

[0207] The device for determining the change of the timing synchronization state in the embodiments of the present application may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device may be a terminal or other devices other than the terminal. Exemplarily, the terminal may include, but is not limited to, the types of the terminal 11 listed above, and other devices may be a server, a Network Attached Storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0208] The device for determining the change of the timing synchronization state provided in the embodiments of the present application can implement Figures 2 to 4 each process implemented by the method embodiments and achieve the same technical effects. To avoid repetition, details are not described here again.

[0209] As Figure 6 shown, the embodiments of the present application further provide a communication device 600, including a processor 601 and a memory 602. A program or instruction that can run on the processor 601 is stored on the memory 602. For example, when the communication device 600 is a terminal, when the program or instruction is executed by the processor 601, each step of the method embodiment for determining the change of the timing synchronization state described above is implemented, and the same technical effects can be achieved. To avoid repetition, details are not described here again.

[0210] The embodiments of the present application further provide a terminal, including a processor and a communication interface. The communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the steps in the method embodiment as Figure 2 shown. This terminal embodiment corresponds to the method embodiment on the terminal side. Each implementation process and implementation manner of the above method embodiment can be applied to this terminal embodiment, and the same technical effects can be achieved. Specifically, Figure 7 FIG. is a schematic diagram of the hardware structure of a terminal for implementing the embodiments of the present application.

[0211] The terminal 700 includes, but is not limited to, at least some components such as a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, and a processor 710.

[0212] Those skilled in the art can understand that the terminal 700 may further include a power source (such as a battery) for powering each component. The power source can be logically connected to the processor 710 through a power management system, so as to implement functions such as management of charging, discharging, and power consumption management through the power management system. Figure 7 The terminal structure shown in Figure 7 does not limit the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0213] It should be understood that in the embodiments of the present application, the input unit 704 may include a Graphics Processing Unit (GPU) 7041 and a microphone 7042. The graphics processor 7041 processes the image data of static pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light-emitting diode, etc. The user input unit 707 includes at least one of a touch panel 7071 and other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include two parts: a touch detection device and a touch controller. The other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, which will not be elaborated here.

[0214] In the embodiments of the present application, after the radio frequency unit 701 receives downlink data from the network-side device, it can be transmitted to the processor 710 for processing; in addition, the radio frequency unit 701 can send uplink data to the network-side device. Generally, the radio frequency unit 701 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, etc.

[0215] The memory 709 can be used to store software programs or instructions as well as various data. The memory 709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. Among them, the first storage area may store an operating system, application programs or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 709 may include volatile memory or non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDR SDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct rambus random access memory (DRRAM). The memory 709 in the embodiments of the present application includes but is not limited to these and any other suitable types of memory.

[0216] The processor 710 may include one or more processing units; optionally, the processor 710 integrates an application processor and a modem processor. Among them, the application processor mainly processes operations related to the operating system, user interface, and application programs, etc., and the modem processor mainly processes wireless communication signals, such as a baseband processor. It can be understood that the above-mentioned modem processor may not be integrated into the processor 710 either.

[0217] Among them, the processor 710 is used for: when obtaining a first event identifier corresponding to a first event, determining whether the timing synchronization state of the terminal has changed according to whether a first stored event identifier corresponding to a second event is stored locally;

[0218] Among them, the first event and the second event are related to the timing synchronization state of the terminal.

[0219] Optionally, the processor 710 determines whether the timing synchronization status of the terminal has changed based on whether the first storage event identifier corresponding to the second event is stored locally, including:

[0220] When the first storage event identifier is not stored locally, it is determined that the timing synchronization status of the terminal has changed;

[0221] When the first storage event identifier is stored locally, it is determined whether the timing synchronization status of the terminal has changed based on the first event identifier and the first storage event identifier.

[0222] Optionally, the processor 710 determines whether the timing synchronization status of the terminal has changed based on the first event identifier and the first storage event identifier, including:

[0223] When the first event identifier is different from the first storage event identifier, it is determined that the timing synchronization status of the terminal has changed;

[0224] When the first event identifier is the same as the first storage event identifier, it is determined whether the timing synchronization status of the terminal has changed based on the identification information of the serving base station where the terminal is currently resident and the identification information of the serving base station stored locally in the terminal.

[0225] Optionally, the identification information of the serving base station where the terminal is currently resident includes a first base station identifier, and the identification information of the serving base station stored locally in the terminal includes a first stored base station identifier, and both the first base station identifier and the first stored base station identifier belong to the global base station identifier;

[0226] The processor 710 determines whether the timing synchronization status of the terminal has changed based on the identification information of the serving base station where the terminal is currently resident and the identification information of the serving base station stored locally in the terminal, including:

[0227] When the first base station identifier is the same as the first stored base station identifier, it is determined that the timing synchronization status of the terminal has not changed;

[0228] When the first base station identifier is different from the first stored base station identifier, it is determined that the timing synchronization status of the terminal has changed.

[0229] Optionally, the first storage event identifier is stored in a first local variable, and the first stored base station identifier is stored in a second local variable;

[0230] The processor 710 is further configured to perform one of the following:

[0231] In the case where the first storage event identifier is not stored locally, use the first event identifier as the second storage event identifier, update the stored content of the first local variable to the second storage event identifier, use the first base station identifier as the second storage base station identifier, and update the stored content of the second local variable to the second storage base station identifier;

[0232] In the case where the first event identifier is different from the first storage event identifier, use the first event identifier as the third storage event identifier, update the stored content of the first local variable to the third storage event identifier, use the first base station identifier as the third storage base station identifier, and update the stored content of the second local variable to the third storage base station identifier;

[0233] In the case where the first base station identifier is different from the first storage base station identifier, use the first base station identifier as the fourth storage base station identifier, and update the stored content of the second local variable to the fourth storage base station identifier.

[0234] Optionally, the identification information of the serving base station where the terminal is currently resident includes a first local base station identifier and a first network identifier, and the identification information of the serving base station stored locally by the terminal includes a first stored local base station identifier and a first stored network identifier;

[0235] The processor 710 determines whether the timing synchronization state of the terminal has changed according to the identification information of the serving base station where the terminal is currently resident and the identification information of the serving base station stored locally by the terminal, including:

[0236] In the case where the first local base station identifier is the same as the first stored local base station identifier and the first network identifier is the same as the first stored network identifier, determine that the timing synchronization state of the terminal has not changed;

[0237] In the case where the first local base station identifier is different from the first stored local base station identifier or the first network identifier is different from the first stored network identifier, determine that the timing synchronization state of the terminal has changed.

[0238] Optionally, the first stored local base station identifier is stored in a third local variable, and the first stored network identifier is stored in a fourth local variable;

[0239] The processor 710 is further configured to perform one of the following:

[0240] In the case where the first storage event identifier is not stored locally, use the first event identifier as the second storage event identifier, update the stored content of the first local variable to the second storage event identifier, use the first local base station identifier as the second storage local base station identifier, update the stored content of the third local variable to the second storage local base station identifier, use the first network identifier as the second storage network identifier, and update the stored content of the fourth local variable to the second storage network identifier;

[0241] In the case where the first event identifier is different from the first storage event identifier, use the first event identifier as the third storage event identifier, update the stored content of the first local variable to the third storage event identifier, use the first local base station identifier as the third storage local base station identifier, update the stored content of the third local variable to the third storage local base station identifier, use the first network identifier as the third storage network identifier, and update the stored content of the fourth local variable to the third storage network identifier;

[0242] In the case where the first local base station identifier is different from the first storage local base station identifier, use the first local base station identifier as the fourth storage local base station identifier, and update the stored content of the third local variable to the fourth storage local base station identifier;

[0243] In the case where the first network identifier is different from the first storage network identifier, use the first network identifier as the fourth storage network identifier, and update the stored content of the fourth local variable to the fourth storage network identifier.

[0244] Optionally, the identification information of the base station where the terminal is currently camped is determined according to the target network identification information, and the target network identification information is determined according to the support situation of the network where the terminal is camped for the Public Land Mobile Network (PLMN) and the Non-Public Network (NPN).

[0245] Optionally, the target network identification information satisfies one of the following:

[0246] In the case where the network where the terminal is camped only supports PLMN, the target network identification information includes the first object in the list of PLMN identification information in the first System Information Block (SIB1), and the first object is the first PLMN identification information in the list of PLMN identification information that follows the broadcast order;

[0247] In the case where the network where the terminal is camped supports the sharing of PLMN and NPN, the target network identification information includes the first object in the list of PLMN identification information in SIB1;

[0248] When the network where the terminal camps supports NPN, the target network identification information includes a second object in the NPN identification information list in SIB1, and the second object is the first NPN identification information following the broadcast order in the NPN identification information list.

[0249] Optionally, the identification information of the base station where the terminal currently camps includes a first base station identification, and the first base station identification is determined according to a first network identification and a first local base station identification; or, the identification information of the base station where the terminal currently camps includes the first network identification and the first local base station identification;

[0250] Wherein, when the network where the terminal camps only supports PLMN, the first network identification is the first PLMN identification in the first object, and the first local base station identification is determined according to the first object;

[0251] When the network where the terminal camps supports the sharing of PLMN and non-public network NPN, the first network identification is the first PLMN identification in the first object, and the first local base station identification is determined according to the first object;

[0252] When the network where the terminal camps supports NPN, the first network identification is the PLMN identification included in the first NPN identification in the second object, and the first local base station identification is determined according to the second object.

[0253] Optionally, the processor 710 is further configured to:

[0254] When it is determined that the timing synchronization state of the terminal changes, control the access stratum of the terminal to notify the non-access stratum that the target information changes;

[0255] Wherein, the target information includes at least one of clock quality information and timing synchronization state information.

[0256] Optionally, the processor 710 obtains the first event identifier, including:

[0257] Obtaining the first event identifier from the ninth system information block SIB9.

[0258] It can be understood that the implementation processes of the implementation manners mentioned in this embodiment can refer to the relevant descriptions of the method embodiments for determining the change of the timing synchronization state above, and achieve the same or corresponding technical effects. To avoid repetition, they will not be elaborated here.

[0259] An embodiment of the present application further provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, it implements each process of the method embodiment for determining the change of the timing synchronization state described above, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0260] Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disc, etc. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0261] Another embodiment of the present application provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement each process of the method embodiment for determining the change of the timing synchronization state described above, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0262] It should be understood that the chip mentioned in the embodiment of the present application may also be referred to as a system-on-chip, a system chip, a chip system, or a system-on-chip.

[0263] Another embodiment of the present application provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement each process of the method embodiment for determining the change of the timing synchronization state described above, and can achieve the same technical effect. To avoid repetition, it will not be elaborated here.

[0264] It should be noted that in this article, the term "comprising", "including" or any other variant thereof is intended to cover a non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including a..." does not exclude the existence of additional identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0265] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-described example methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, they can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes several instructions for causing a terminal or a network-side device to execute the methods described in various embodiments of the present application.

[0266] The embodiments of the present application have been described above in conjunction with the accompanying drawings. However, the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not restrictive. Under the inspiration of the present application, those of ordinary skill in the art can also make many forms of embodiments without departing from the purpose of the present application and the scope protected by the claims. These embodiments are all within the protection scope of the present application.

Claims

1. A method for determining a change in timing synchronization status, characterized in that, The method includes: When the terminal obtains the first event identifier corresponding to the first event, the terminal determines whether the timing synchronization state of the terminal has changed according to whether the first stored event identifier corresponding to the second event is stored locally; Wherein, the first event and the second event are related to the timing synchronization state of the terminal.

2. The method according to claim 1, characterized in that, The terminal determines whether the timing synchronization state of the terminal has changed according to whether the first stored event identifier corresponding to the second event is stored locally, including: When the first stored event identifier is not stored locally, the terminal determines that the timing synchronization state of the terminal has changed; When the first stored event identifier is stored locally, the terminal determines whether the timing synchronization state of the terminal has changed according to the first event identifier and the first stored event identifier.

3. The method according to claim 2, characterized in that, The terminal determines whether the timing synchronization state of the terminal has changed according to the first event identifier and the first stored event identifier, including: When the first event identifier is different from the first stored event identifier, the terminal determines that the timing synchronization state of the terminal has changed; When the first event identifier is the same as the first stored event identifier, the terminal determines whether the timing synchronization state of the terminal has changed according to the identifier information of the serving base station where the terminal is currently located and the identifier information of the serving base station stored locally in the terminal.

4. The method according to claim 3, characterized in that, The identifier information of the serving base station where the terminal is currently located includes a first base station identifier, and the identifier information of the serving base station stored locally in the terminal includes a first stored base station identifier. Both the first base station identifier and the first stored base station identifier belong to the global base station identifier; The terminal determines whether the timing synchronization state of the terminal has changed according to the identifier information of the serving base station where the terminal is currently located and the identifier information of the serving base station stored locally in the terminal, including: When the first base station identifier is the same as the first stored base station identifier, the terminal determines that the timing synchronization state of the terminal has not changed; When the first base station identifier is different from the first stored base station identifier, the terminal determines that the timing synchronization state of the terminal has changed.

5. The method according to claim 4, characterized in that, The first stored event identifier is stored in a first local variable, and the first stored base station identifier is stored in a second local variable; The method further includes one of the following: When the first stored event identifier is not stored locally, the terminal uses the first event identifier as the second stored event identifier, updates the stored content of the first local variable to the second stored event identifier, uses the first base station identifier as the second stored base station identifier, and updates the stored content of the second local variable to the second stored base station identifier; When the first event identifier is different from the first stored event identifier, the terminal uses the first event identifier as the third stored event identifier, updates the stored content of the first local variable to the third stored event identifier, uses the first base station identifier as the third stored base station identifier, and updates the stored content of the second local variable to the third stored base station identifier; When the first base station identifier is different from the first stored base station identifier, the terminal uses the first base station identifier as the fourth stored base station identifier, and updates the stored content of the second local variable to the fourth stored base station identifier.

6. The method according to claim 3, characterized in that, The identification information of the base station where the terminal currently camps includes a first local base station identifier and a first network identifier, and the identification information of the base station where the terminal stores locally includes a first stored local base station identifier and a first stored network identifier; The terminal determines whether the timing synchronization state of the terminal has changed according to the identification information of the base station where the terminal currently camps and the identification information of the base station where the terminal stores locally, including: When the first local base station identifier is the same as the first stored local base station identifier, and the first network identifier is the same as the first stored network identifier, the terminal determines that the timing synchronization state of the terminal has not changed; When the first local base station identifier is different from the first stored local base station identifier, or the first network identifier is different from the first stored network identifier, the terminal determines that the timing synchronization state of the terminal has changed.

7. The method according to claim 6, characterized in that, The first stored local base station identifier is stored in a third local variable, and the first stored network identifier is stored in a fourth local variable; The method further includes one of the following: When the first stored event identifier is not stored locally, the terminal uses the first event identifier as the second stored event identifier, updates the stored content of the first local variable to the second stored event identifier, uses the first local base station identifier as the second stored local base station identifier, updates the stored content of the third local variable to the second stored local base station identifier, uses the first network identifier as the second stored network identifier, and updates the stored content of the fourth local variable to the second stored network identifier; When the first event identifier is different from the first stored event identifier, the terminal uses the first event identifier as the third stored event identifier, updates the stored content of the first local variable to the third stored event identifier, uses the first local base station identifier as the third stored local base station identifier, updates the stored content of the third local variable to the third stored local base station identifier, uses the first network identifier as the third stored network identifier, and updates the stored content of the fourth local variable to the third stored network identifier; When the first local base station identifier is different from the first stored local base station identifier, the terminal uses the first local base station identifier as the fourth stored local base station identifier and updates the stored content of the third local variable to the fourth stored local base station identifier; When the first network identifier is different from the first stored network identifier, the terminal uses the first network identifier as the fourth stored network identifier and updates the stored content of the fourth local variable to the fourth stored network identifier.

8. The method according to any one of claims 3 to 7, characterized in that, The identification information of the base station where the terminal currently camps is determined according to the target network identification information, and the target network identification information is determined according to the support situation of the network where the terminal camps for the public land mobile network (PLMN) and the non-public network (NPN).

9. The method according to claim 8, characterized in that, The target network identification information satisfies one of the following: When the network where the terminal camps only supports PLMN, the target network identification information includes the first object in the PLMN identification information list in the first system information block (SIB1), and the first object is the first PLMN identification information following the broadcast order in the PLMN identification information list; When the network where the terminal camps supports the sharing of PLMN and NPN, the target network identification information includes the first object in the PLMN identification information list in SIB1; When the network where the terminal camps supports NPN, the target network identification information includes the second object in the NPN identification information list in SIB1, and the second object is the first NPN identification information following the broadcast order in the NPN identification information list.

10. The method according to claim 9, wherein The identification information of the base station where the terminal currently camps includes a first base station identifier, and the first base station identifier is determined according to the first network identifier and the first local base station identifier; or, the identification information of the base station where the terminal currently camps includes the first network identifier and the first local base station identifier; Among them, the first network identifier and the first local base station identifier satisfy one of the following: When the network where the terminal camps only supports PLMN, the first network identifier is the first PLMN identifier in the first object, and the first local base station identifier is determined according to the first object; When the network where the terminal camps supports the sharing of PLMN and the non-public network NPN, the first network identifier is the first PLMN identifier in the first object, and the first local base station identifier is determined according to the first object; When the network where the terminal camps supports NPN, the first network identifier is the PLMN identifier included in the first NPN identifier in the second object, and the first local base station identifier is determined according to the second object.

11. The method according to any one of claims 2 to 10, wherein The method further includes: When it is determined that the timing synchronization state of the terminal changes, the access stratum of the terminal notifies the non-access stratum that the target information changes; Among them, the target information includes at least one of clock quality information and timing synchronization state information.

12. The method according to any one of claims 2 to 11, wherein The terminal obtains the first event identifier, including: The terminal obtains the first event identifier from the ninth system information block SIB9.

13. A device for determining a change in timing synchronization state, wherein Applied to a terminal, the device includes: A determination module, configured to determine whether the timing synchronization state of the terminal changes according to whether a first stored event identifier corresponding to a second event is locally stored when the first event identifier corresponding to the first event is obtained; Wherein, the first event and the second event are related to the timing synchronization state of the terminal.

14. The device according to claim 13, wherein The determination module includes: A first determination sub-module, configured to determine that the timing synchronization state of the terminal changes when the first stored event identifier is not locally stored; A second determination sub-module, configured to determine whether the timing synchronization state of the terminal changes according to the first event identifier and the first stored event identifier when the first stored event identifier is locally stored.

15. The device according to claim 14, wherein The second determination sub-module includes: A first determination unit, configured to determine that the timing synchronization state of the terminal changes when the first event identifier is different from the first stored event identifier; A second determination unit, configured to determine whether the timing synchronization state of the terminal changes according to the identifier information of the serving base station of the terminal currently and the identifier information of the serving base station stored locally in the terminal when the first event identifier is the same as the first stored event identifier.

16. The device according to claim 15, wherein The identifier information of the serving base station of the terminal currently includes a first base station identifier, and the identifier information of the serving base station stored locally in the terminal includes a first stored base station identifier, and both the first base station identifier and the first stored base station identifier belong to the global base station identifier; The second determination unit is specifically configured to: Determine that the timing synchronization state of the terminal does not change when the first base station identifier is the same as the first stored base station identifier; Determine that the timing synchronization state of the terminal changes when the first base station identifier is different from the first stored base station identifier.

17. The device according to claim 16, wherein The first stored event identifier is stored in a first local variable, and the first stored base station identifier is stored in a second local variable; The device further includes at least one of the following modules: A first update module, configured to use the first event identifier as a second stored event identifier and update the stored content of the first local variable to the second stored event identifier, use the first base station identifier as a second stored base station identifier, and update the stored content of the second local variable to the second stored base station identifier when the first stored event identifier is not locally stored; A second update module, configured to use the first event identifier as a third stored event identifier and update the stored content of the first local variable to the third stored event identifier, use the first base station identifier as a third stored base station identifier, and update the stored content of the second local variable to the third stored base station identifier when the first event identifier is different from the first stored event identifier; A third update module, configured to, when the first base station identifier is different from the first stored base station identifier, use the first base station identifier as the fourth stored base station identifier, and update the stored content of the second local variable to the fourth stored base station identifier.

18. The device according to claim 15, characterized in that, The identification information of the base station where the terminal currently camps includes a first local base station identifier and a first network identifier, and the identification information of the base station where the terminal locally stores includes a first stored local base station identifier and a first stored network identifier; The second determination unit is specifically configured to: When the first local base station identifier is the same as the first stored local base station identifier and the first network identifier is the same as the first stored network identifier, determine that the timing synchronization state of the terminal has not changed; When the first local base station identifier is different from the first stored local base station identifier or the first network identifier is different from the first stored network identifier, determine that the timing synchronization state of the terminal has changed.

19. The device according to claim 18, characterized in that, The first stored local base station identifier is stored in a third local variable, and the first stored network identifier is stored in a fourth local variable; The device further includes at least one of the following modules: A fourth update module, configured to, when the first stored event identifier is not locally stored, use the first event identifier as the second stored event identifier, update the stored content of the first local variable to the second stored event identifier, use the first local base station identifier as the second stored local base station identifier, update the stored content of the third local variable to the second stored local base station identifier, use the first network identifier as the second stored network identifier, and update the stored content of the fourth local variable to the second stored network identifier; A fifth update module, configured to, when the first event identifier is different from the first stored event identifier, use the first event identifier as the third stored event identifier, update the stored content of the first local variable to the third stored event identifier, use the first local base station identifier as the third stored local base station identifier, update the stored content of the third local variable to the third stored local base station identifier, use the first network identifier as the third stored network identifier, and update the stored content of the fourth local variable to the third stored network identifier; A sixth update module, configured to, when the first local base station identifier is different from the first stored local base station identifier, use the first local base station identifier as the fourth stored local base station identifier, and update the stored content of the third local variable to the fourth stored local base station identifier; A seventh update module, configured to, when the first network identifier is different from the first stored network identifier, use the first network identifier as the fourth stored network identifier, and update the stored content of the fourth local variable to the fourth stored network identifier.

20. The device according to any one of claims 15 to 19, characterized in that, The identification information of the current serving base station of the terminal is determined according to the target network identification information, and the target network identification information is determined according to the support situation of the network where the terminal camps for the public land mobile network (PLMN) and the non-public network (NPN).

21. The device according to claim 20, characterized in that, The target network identification information satisfies one of the following: When the network where the terminal camps only supports the PLMN, the target network identification information includes the first object in the PLMN identification information list in the first system information block (SIB1), and the first object is the first PLMN identification information in the PLMN identification information list that follows the broadcast order; When the network where the terminal camps supports the sharing of the PLMN and the NPN, the target network identification information includes the first object in the PLMN identification information list in the SIB1; When the network where the terminal camps supports the NPN, the target network identification information includes the second object in the NPN identification information list in the SIB1, and the second object is the first NPN identification information in the NPN identification information list that follows the broadcast order.

22. The device according to claim 21, characterized in that, The identification information of the current serving base station of the terminal includes a first base station identification, and the first base station identification is determined according to a first network identification and a first local base station identification; or, the identification information of the current serving base station of the terminal includes the first network identification and the first local base station identification; Wherein, when the network where the terminal camps only supports the PLMN, the first network identification is the first PLMN identification in the first object, and the first local base station identification is determined according to the first object; When the network where the terminal camps supports the sharing of the PLMN and the non-public network (NPN), the first network identification is the first PLMN identification in the first object, and the first local base station identification is determined according to the first object; When the network where the terminal camps supports the NPN, the first network identification is the PLMN identification included in the first NPN identification in the second object, and the first local base station identification is determined according to the second object.

23. The device according to any one of claims 14 to 22, characterized in that, The device further includes: A notification module, configured to notify that the non-access stratum target information of the terminal has changed when it is determined that the timing synchronization state of the terminal has changed; Wherein, the target information includes at least one of clock quality information and timing synchronization state information.

24. A terminal, characterized in that, It includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the steps of the method for determining the change of the timing synchronization state as described in any one of claims 1 to 12 are implemented.

25. A readable storage medium, characterized in that, A program or instruction is stored on the readable storage medium. When the program or instruction is executed by the processor, the steps of the method for determining the change of the timing synchronization state as described in any one of claims 1 to 12 are implemented.

Images