Method and apparatus for determining change in timing synchronization status, and terminal

Abstract

The present application relates to the technical field of communications, and discloses a method and apparatus for determining a change in timing synchronization status, and a terminal. The method for determining a change in timing synchronization status in embodiments of the present application comprises: when a terminal obtains a first event identifier corresponding to a first event, the terminal determines, on the basis of whether a first storage event identifier corresponding to a second event is stored locally, whether the timing synchronization status of the terminal changes, wherein the first event and the second event are related to the timing synchronization status of the terminal.

Description

Method, device and terminal for determining timing synchronization state change

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the China Patent Office on December 19, 2023, with application number 202311764419.X and titled “A method, device and terminal for determining changes in timing synchronization status”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to a method, device and terminal for determining a change in a timing synchronization state. Background Art

[0004] With the continuous development of wireless communication technology, timing synchronization has become an important part of wireless communication. In related technologies, if the network and terminal clocks are out of sync, data packets may be lost or duplicated, affecting communication quality. Timing synchronization technology ensures that the network and terminal clocks are consistent, improving the accuracy and reliability of data transmission and thus enhancing communication quality.

[0005] When different timing synchronization sources are used or different interference is encountered, the timing synchronization state on the network side may change, and the timing synchronization state of the terminal will also change accordingly. However, in related technologies, when different timing synchronization sources are used or different interference is encountered, the terminal still operates based on the original timing synchronization state, making it impossible for the terminal that needs synchronization to maintain synchronization with the network side. Summary of the Invention

[0006] The embodiments of the present 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 a terminal and a network side in related technologies.

[0007] In a first aspect, a method for determining a timing synchronization state change is provided, the method comprising:

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

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

[0010] In a second aspect, a device for determining a timing synchronization state change is provided, which is applied to a terminal, and the device includes:

[0011] a determination module configured to, upon obtaining a first event identifier corresponding to a first event, determine whether a timing synchronization state of the terminal has changed based on whether a first stored event identifier corresponding to a second event is stored locally;

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

[0013] In a third aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0014] In a fourth aspect, a terminal is provided, including a processor and a communication interface, wherein the processor is configured to:

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

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

[0017] In a fifth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0018] In a sixth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to run a program or instruction to implement the steps of the method described in the first aspect.

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

[0020] In an eighth aspect, an embodiment of the present application provides a device for determining a change in a timing synchronization state, wherein the device is used to execute the steps of the method for determining a change in a timing synchronization state as described in the first aspect.

[0021] In an embodiment 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 has changed based on whether a first stored event identifier corresponding to a second event is stored locally, wherein the first event and the second event are related to the timing synchronization state of the terminal. It can be seen that in an embodiment 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 has changed based on whether a first stored event identifier corresponding to an event related to the timing synchronization state of the terminal is stored locally. Therefore, an embodiment of the present application provides a method for a terminal to determine whether its timing synchronization state has changed, so that the terminal can promptly know 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

[0022] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0023] FIG2 is a flow chart of a method for determining a timing synchronization state change in an embodiment of the present application;

[0024] FIG3 is a flow chart of a first embodiment of a method for determining a timing synchronization state change according to the present application;

[0025] FIG4 is a flow chart of a second embodiment of the method for determining a timing synchronization state change implemented in the present application;

[0026] FIG5 is a structural block diagram of an apparatus for determining a timing synchronization state change in an embodiment of the present application;

[0027] FIG6 is a structural block diagram of a communication device in an embodiment of the present application;

[0028] FIG7 is a structural block diagram of a terminal in an embodiment of the present application. Specific embodiments

[0029] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0030] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, 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 generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0031] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0032] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but 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 the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. thGeneration, 6G) communication system.

[0033] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (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 (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, vehicle-mounted controller, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application.

[0034] The network-side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (RAN) device, a radio access network function, or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP), or a wireless fidelity (WiFi) node. 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 (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0035] To facilitate understanding of the method for determining a timing synchronization state change in an embodiment of the present application, the following related technologies are now introduced:

[0036] 1. Non-Public Network (NPN)

[0037] 5G NPNs are private networks built using 5G technology, independent of the public land mobile network (PLMN) serving the general public. 5G NPNs support two deployment modes: Stand-alone Non-Public Network (SNPN) and Public Network Integrated Non-Public Network (PNI-NPN). Stand-alone NPNs are independent of any PLMN network functions; PNI-NPNs rely on the public network.

[0038] In the 16th public release of the 3GPP protocol (R16), NPNs are deployed using public network integration. Currently, an NPN is understood as a slice or group of slices / Data Network Names (DNNs) of the public network. Given that 5G core network (5GC) slices cannot restrict UE access on the Radio Access Network (RAN), it is necessary to define a Closed Access Group (CAG) for the NPN to which it is allowed to access.

[0039] A CAG consists of a set of cell IDs. A UE can access the NPN RAN only within the area corresponding to the CAG. The RAN broadcasts the PLMN and CAG IDs and performs access selection and control based on the CAG. CAG information is typically pre-configured in the UE and can be updated through the User Configuration Update (UCU) process.

[0040] R17 introduces independently deployed NPNs, which are identified by a combination of PLMN ID and network identifier (NID). PLMN operators can reuse their PLMN IDs and use NIDs to distinguish between private networks, or use PLMN IDs reserved for private networks. RAN broadcasts PLMN+NID. The UE of SNPN (i.e., NPN independently deployed) is identified by the Subscription Permanent Identifier (SUPI). If the UE is set to SNPN access mode, the UE can only access and register to the SNPN through the Uu air interface. When the UE initially registers, it will bring 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 user's subscription information in the NPN includes unified access control (UAC) information. When the network is congested, the SNPN can prevent the UE from accessing.

[0041] 2. R18 Time Sensitive Communications (TSC) Enhancements

[0042] To support communication services with high-reliability synchronous communication, UEs in different Radio Resource Control (RRC) states may obtain timing synchronization status or specific clock quality information through one or both of the following methods.

[0043] Method 1: For a UE in the connected state (RRC_CONNECTED), the gNB uses proprietary RRC signaling, such as DL Information Transfer, to send an event ID indicating a time synchronization status change and clock quality information.

[0044] Method 2: For UEs not in the RRC_CONNECTED state (i.e., in RRC_INACTIVE or RRC_IDLE), the UE first establishes or restores an RRC connection and then obtains clock quality information from the gNB via proprietary RRC signaling. The gNB broadcasts an Event ID in SIB9 to notify its timing synchronization status. The gNB uses the change in Event ID as a trigger to trigger a system message change to notify the UE to read the SIB information, informing the UE that new timing synchronization status information is available (or exists).

[0045] The scope of the Event ID is the gNB. That is, a gNB ID change can be used as a condition for the UE to establish or reestablish an RRC connection, indicating a change in time synchronization status. However, the gNB itself does not broadcast the gNB ID. The UE can obtain the gNB ID corresponding to the current cell using the Cell Identity (NR Cell Identifier, NCI) and gNB-ID-Length in SIB1.

[0046] 3. RAN Cell Access Information

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

[0048] 4. Base station / cell identification distinction

[0049] The Global gNB ID is used to globally identify a gNB. The Global gNB ID consists of the PLMN identity information (Identity) to which the gNB belongs and the gNB ID.

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

[0051] The method for determining a change in a timing synchronization state provided by an embodiment of the present application is described in detail below with reference to the accompanying drawings through some embodiments and application scenarios.

[0052] An embodiment of the present application provides a method for determining a timing synchronization state change. As shown in FIG2 , the method may include the following step 201:

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

[0054] 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 terminal's timing synchronization state information.

[0055] In addition, if the base station where the terminal resides supports timing synchronization, the base station may provide the timing synchronization status by periodically broadcasting an event identifier (Event ID).

[0056] As can be seen, when a 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 resided did not support timing synchronization or did not provide timing synchronization status, but now supports timing synchronization or provides timing synchronization status. Therefore, when the terminal receives an Event ID, it can determine whether the terminal's timing synchronization status has changed based on whether the Event ID is stored locally.

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

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

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

[0060] It can be seen from the above step 201 that in an 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 state of the terminal has changed based on 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. It can be seen that in an embodiment of the present application, if the terminal obtains the 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 has changed based on whether the first stored event identifier corresponding to the event related to the timing synchronization state of the terminal is stored locally. Therefore, an embodiment of the present application provides a method for a terminal to determine whether its timing synchronization state has changed, so that the terminal can obtain and update the timing synchronization state in a timely manner, 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 determines whether the timing synchronization state of the terminal has changed based on whether the first stored event identifier corresponding to the second event is stored locally, including the following steps A-1 to A-2:

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

[0062] Step A-2: In a case where the first stored event identifier is stored locally, the terminal determines whether the timing synchronization state of the terminal changes according to the first event identifier and the first stored event identifier.

[0063] As described above, if the terminal does not locally store the Event ID when it obtains an Event ID, this indicates that the base station where the terminal previously resided 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 terminal does not locally store the first stored event identifier, it indicates that the timing synchronization status of the terminal has changed.

[0064] 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 a terminal. That is, within a time period, if the timing synchronization state corresponding to the base station where the terminal resides does not change, the base station broadcasts the same Event ID in N cycles within that time period; if the timing synchronization state corresponding to the base station changes, the base station broadcasts a different Event ID within that time period. Therefore, in step A-2, if the terminal locally stores a first stored event identifier, the terminal can determine whether the terminal's timing synchronization state has changed by comparing the first event identifier with the first stored event identifier.

[0065] 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:

[0066] 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;

[0067] 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 changes based on the identification information of the current resident base station of the terminal and the identification information of the resident base station stored locally by the terminal.

[0068] As mentioned above, if the base station where the terminal resides supports timing synchronization, then the base station can periodically broadcast an event identifier (Event ID) to notify its timing synchronization status; and if the timing synchronization status of the base station changes, the Event ID broadcast by the base station will change; and if the timing synchronization status of the base station changes, the timing synchronization status 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 locally stored by the terminal, it indicates that the timing synchronization status of the terminal has changed.

[0069] In addition, it should be noted that the scope of the Event ID is one base station. That is, when the base station where the terminal is stationed changes, and the base station where the terminal is stationed before the change and the base station where the terminal is stationed after the change both 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, the base station where the terminal is stationed has changed, and the timing synchronization status of the terminal will also change. Therefore, in step B-2, if the first event identifier currently obtained by the terminal is the same as the first stored event identifier locally stored by the terminal, the terminal needs to further compare the identification information of the current base station where the terminal is stationed with the identification information of the base station where the terminal is stationed locally stored to determine whether the timing synchronization status of the terminal has changed.

[0070] Optionally, the identification information of the current resident base station of the terminal includes a first base station identifier, the identification information of the resident base station locally stored by the terminal includes a first stored base station identifier, and both the first base station identifier and the first stored base station identifier are global base station identifiers;

[0071] In the above step B-2, the terminal determines whether the timing synchronization state of the terminal has changed based on the identification information of the current resident base station of the terminal and the identification information of the resident base station stored locally by the terminal, including the following steps C-1 to C-2:

[0072] 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;

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

[0074] When the base station a terminal is residing on changes, the terminal considers the timing synchronization status to have changed. The gNB ID is valid within a single PLMN; that is, different gNBs in different PLMNs may be assigned the same gNB ID. In this case, although the gNB ID remains unchanged, the actual gNB has changed. Therefore, the UE cannot determine whether the gNB it is residing on has changed by simply comparing the gNB ID, and thus cannot promptly determine whether the timing synchronization status has changed.

[0075] The global base station identifier (GBI) is a unique identifier for each base station. Therefore, in steps C-1 and C-2, by comparing the global base station identifier (i.e., the first base station identifier) ​​of the terminal's current resident base station with the global base station identifier (i.e., the first stored base station identifier) ​​of the terminal's locally stored resident base station, it is possible to accurately determine whether the terminal's resident base station has changed, and thus whether the terminal's timing synchronization status has changed.

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

[0077] Item D-1: When 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 and updates the storage content of the first local variable to the second storage event identifier (i.e., stores the second storage event identifier as the storage content of the first local variable, i.e., updates the storage content of the first local variable to the first event identifier), uses the first base station identifier as the second storage base station identifier, and updates the storage content of the second local variable to the second storage base station identifier (i.e., stores the second storage base station identifier as the storage content of the second local variable or replaces the storage content of the second local variable with the second storage base station identifier, i.e., updates the storage content of the second local variable to the first base station identifier);

[0078] 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 terminal's resident base station.

[0079] Moreover, as mentioned above, the terminal does not store the first storage event identifier locally, indicating that the base station where the terminal previously resided did not support timing synchronization or did not provide timing synchronization status, but now supports timing synchronization or provides timing synchronization status (that is, the timing synchronization status of the terminal has changed). Therefore, in item D-1, if no content is stored in the first local variable locally in the terminal, the first local variable and the second local variable need to be updated.

[0080] 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 and updates the storage content of the first local variable to the third stored event identifier (i.e., stores the third stored event identifier as the storage content of the first local variable, i.e., updates the storage 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 storage content of the second local variable to the third stored base station identifier (i.e., replaces the storage content of the second local variable with the third stored base station identifier, i.e., updates the storage content of the second local variable to the first base station identifier);

[0081] It should be noted that the fact that the first event identifier differs from the first stored event identifier does not directly prove whether the base station where the terminal is stationed has changed. To ensure that the stored contents of the local variable correspond to the stationed 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 differs from the first stored event identifier, both the first and second local variables need to be updated.

[0082] 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 storage content of the second local variable to the fourth stored base station identifier (i.e., replaces the storage content of the second local variable with the fourth stored base station identifier, i.e., updates the storage content of the second local variable to the first base station identifier).

[0083] It should be noted that the first base station identifier is different from the first stored base station identifier because the base station where the terminal resides changes; 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.

[0084] Optionally, the identification information of the current resident base station of the terminal includes a first local base station identifier and a first network identifier, and the identification information of the resident base station locally stored by the terminal includes a first stored local base station identifier and a first stored network identifier;

[0085] In the above step B-2, the terminal determines whether the timing synchronization state of the terminal has changed based on the identification information of the current resident base station of the terminal and the identification information of the resident base station stored locally by the terminal, including the following steps E-1 to E-2:

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

[0087] 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.

[0088] When the base station a terminal is residing on changes, the terminal considers the timing synchronization status to have changed. The gNB ID is valid within a single PLMN; that is, different gNBs in different PLMNs may be assigned the same gNB ID. In this case, although the gNB ID remains unchanged, the actual gNB has changed. Therefore, the UE cannot determine whether the gNB it is residing on has changed by simply comparing the gNB ID, and therefore cannot promptly determine whether the timing synchronization status has changed.

[0089] 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 communicated by 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 terminal's current resident base station, 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 resident base station locally stored by the terminal, it is possible to accurately determine whether the resident base station of the terminal has changed, and further, whether the timing synchronization status of the terminal has changed.

[0090] It should be noted that, in this document, 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.

[0091] 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; the method further includes one of the following items F-1 to F-4:

[0092] Item F-1: When the first stored event identifier is not stored locally (i.e., when no content is stored in the first local variable), the terminal uses the first event identifier as the second stored event identifier and 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, or updates the stored content of the first local variable to the first event identifier), uses the first local base station identifier as the second stored local base station identifier, and updates the stored content of the third local variable to the second stored local base station identifier (i.e., stores the second stored 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 stored local base station identifier, or updates the stored content of the third local variable to the first 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 (i.e., stores the second stored network identifier as the stored content of the fourth local variable or replaces the stored content of the fourth local variable with the second stored network identifier, or updates the stored content of the fourth local variable to the first network identifier);

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

[0094] Moreover, as mentioned above, the terminal does not store the first storage event identifier locally, indicating that the base station where the terminal previously resided did not support timing synchronization or did not provide timing synchronization status, but now supports timing synchronization or provides timing synchronization status (that is, the timing synchronization status of the terminal has changed). Therefore, in item F-1, if no content is stored in the first local variable of the terminal, the first local variable, the third local variable and the fourth local variable need to be updated.

[0095] 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 and 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, i.e., updates 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, 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, i.e., updates 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, i.e., updates the stored content of the fourth local variable to the first network identifier);

[0096] It should be noted that the fact that the first event identifier differs from the first stored event identifier does not directly indicate whether the base station where the terminal resides has changed. To ensure that the stored contents of the local variables correspond to the cell where the terminal resides, in addition to updating the first local variable, the terminal also needs to update the third and fourth local variables. Therefore, in item F-2, if the first event identifier differs from the first stored event identifier, the first, third, and fourth local variables must be updated.

[0097] Item F-3: If 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, i.e., updates the stored content of the third local variable to the first local base station identifier);

[0098] It should be noted that the first local base station identifier is different from the first stored local base station identifier, which is caused by the change of the base station where the terminal resides; 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.

[0099] 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 storage content of the fourth local variable to the fourth stored network identifier (i.e., replaces the storage content of the fourth local variable with the fourth stored network identifier, i.e., updates the storage content of the fourth local variable to the first network identifier).

[0100] It should be noted that the first network identifier is different from the first stored network identifier due to a change in the network of the base station where the terminal resides; therefore, in item F-4, if the first network identifier is different from the first stored network identifier, the fourth local variable needs to be updated.

[0101] Optionally, the identification information of the base station where the terminal currently resides is determined according to the identification information of the target network, and the identification information of the target network is determined according to the support status of the network where the terminal resides for the public land mobile network PLMN and the non-public network NPN.

[0102] The target identification information is included in SIB1. That is, the target identification information may include which information in SIB1 based on the support of the PLMN and NPN by the network where the terminal resides.

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

[0104] Item G-1: When the network in which the terminal resides supports only PLMNs, the target network identification information includes the first object in the PLMN identification information list (PLMN-IdentityInfoList) in the first system information block SIB1, where the first object is the first PLMN identification information (PLMN-IdentityInfo) in the PLMN identification information list in the broadcast order;

[0105] 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 (ie, the first broadcasted PLMN-IdentityInfo).

[0106] Item G-2: when the network in which the terminal resides supports sharing of PLMN and NPN, the target network identification information includes the first object in the PLMN identification information list in SIB1;

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

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

[0109] It can be seen from item G-3 that when the network where the terminal resides supports NPN, the target network identification information includes the first NPN-IdentityInfo in the broadcast order in the NPN-IdentityInfoList in SIB1 (ie, the first broadcasted NPN-IdentityInfo).

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

[0111] Optionally, the identification information of the current resident base station of the terminal 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 current resident base station of the terminal includes the first network identifier and the first local base station identifier;

[0112] The first network identifier and the first local base station identifier satisfy one of the following items H-1 to H-3:

[0113] Item H-1: when the network where the terminal resides 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 based on the first object;

[0114] Item H-2: When the network where the terminal resides supports sharing of a PLMN with a 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 based on the first object;

[0115] Item H-3: When the network where the terminal resides supports NPN, the first network identifier is the PLMN identifier contained in the first NPN identifier in the second object, and the first local base station identifier is determined based on the second object.

[0116] As mentioned above, the identification information of the base station where the terminal currently resides may include a first base station identifier (a global base station identifier), or may also include a first network identifier and a first local base station identifier.

[0117] Among them, when the identification information of the terminal's current resident base station includes the first base station identifier, the first base station identifier is determined based on 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.

[0118] In addition, as mentioned above, the identification information of the current base station where the terminal resides is determined according to the identification information of the target network. Therefore, the first network identification and the first local base station identification are determined according to the target network information.

[0119] Specifically, it can be seen from the above G-1 and H-1 items that, when the network where the terminal resides only supports PLMN, the first network identifier is the first PLMN identifier (PLMN-identity) in the first PLMN-IdentityInfo in the broadcast order in the PLMN-IdentityInfoList in SIB1, and the first local base station identifier is determined according to the first PLMN-IdentityInfo in the broadcast order in the PLMN-IdentityInfoList in SIB1;

[0120] It can be seen from the above G-2 and H-2 that, when the network where the terminal resides supports sharing of PLMN and NPN, the first network identifier is the first PLMN identifier (PLMN-identity) in the first PLMN-IdentityInfo in the broadcast order in the PLMN-IdentityInfoList in SIB1, and the first local base station identifier is determined according to the first PLMN-IdentityInfo in the broadcast order in the PLMN-IdentityInfoList in SIB1;

[0121] It can be seen from the above items G-3 and H-3 that when the network where the terminal resides supports NPN, the first network identifier is the PLMN identifier (PLMN-Identity) contained in the first NPN identifier (NPN-Identity) in the first NPN-IdentityInfo in the broadcast order in the NPN-IdentityInfoList in SIB1, and the first local base station identifier is determined according to the first PLMN-IdentityInfo in the broadcast order in the PLMN-IdentityInfoList in SIB1.

[0122] In addition, the target network identification information (e.g., 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). Determining the first local base station identifier based on the target network identification information may include:

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

[0124] A specific implementation manner in which the first local base station identifier is determined according to the target network identifier information may be, for example:

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

[0126] Optionally, the method further includes:

[0127] In the case of determining that the timing synchronization state of the terminal has changed, the access layer of the terminal notifies the non-access layer of the change in target information;

[0128] The target information includes at least one of clock quality information and timing synchronization status information.

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

[0130] In summary, the specific implementation of the method for determining a timing synchronization state change in the embodiment of the present application can be as described in the following implementation modes 1 or 2:

[0131] Implementation method 1: The UE maintains two local variables, one corresponding to an event identifier and a global base station identifier. That is, the first local variable is used to store an identifier of an 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 UE's resident base station. As shown in FIG3 , the specific execution process of the UE is as follows:

[0132] Step 301: Obtain a first event identifier from SIB9, and determine a first base station identifier of a base station where the terminal is currently camped based on information obtained from SIB1; wherein the first base station identifier is a global base station identifier;

[0133] It is understandable 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 resident base station based on the information obtained from SIB1 is not specifically limited here.

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

[0135] Step 302: Determine whether the first local variable stores any content; if the first local variable does not store any content (i.e., the base station coverage area where the UE was last located did not support / provide time synchronization status, but now supports / provides time synchronization status), execute step 303; if the first local variable stores a first storage event identifier, execute step 304;

[0136] Step 303: Determine that the timing synchronization state has changed, and notify the NAS layer of the change in target information; update the first local variable and the second local variable (i.e., use the first event identifier as the second stored event identifier, and store the second stored event identifier as the storage 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 storage content of the second local variable, or replace the storage 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 clock quality details and timing synchronization state information;

[0137] Step 304: Determine whether the values ​​of the first event identifier and the first stored event identifier are equal; if the values ​​of the first event identifier and the first stored event identifier are not equal, execute step 305; if the values ​​of the first event identifier and the first stored event identifier are equal, execute step 306:

[0138] Step 305: Determine that the timing synchronization state has changed, and notify the NAS layer of the change in the target information; update the first local variable and the second local variable (i.e., use the first event identifier as the third stored event identifier, 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);

[0139] Step 306: Determine whether 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 first base station identifier is equal to the value of the first stored base station identifier, execute step 307; if the first base station identifier is not equal to the value of the first stored base station identifier, execute step 308;

[0140] Step 307: Determine that the timing synchronization state has not changed;

[0141] Step 308: Determine that the timing synchronization state has changed, notify the NAS layer of the change in the target information; update the second local variable (ie, use the first base station identifier as the fourth stored base station identifier, and replace the storage content of the second local variable with the fourth stored base station identifier).

[0142] The UE determines the first base station identifier based on 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 based on the information in SIB1;

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

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

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

[0146] Accordingly, the first local base station identifier is determined based on the target identification information. For example, the high X bits of the cell identification information (CellIdentity) in the target identification information are taken as the first local base station identifier, where X is the Gnb-ID-length in the target identification information; the target identification information satisfies one of the following:

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

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

[0149] Implementation method 2: The UE maintains three local variables, corresponding to an event identifier, a local base station identifier, and a network identifier, respectively; that is, the first local variable is used to store an 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 UE's resident base station, and the fourth local variable is used to store the network identifier of the resident base station of the UE; as shown in FIG4 , the specific execution process of the UE is as follows:

[0150] Step 401: Obtain a first event identifier from SIB9, and determine a first local base station identifier and a first network identifier of the base station where the terminal is currently camped based on the information obtained from SIB1; wherein the first base station identifier is a global base station identifier;

[0151] It is understandable 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 terminal's current resident base station based on the information obtained from SIB1 are not specifically limited here.

[0152] It should be noted that if the eNB broadcasts the event ID in SIB9, it must include the gNB-ID-Length in SIB1. This means that from the terminal's perspective, if it receives the event ID in SIB9, it can obtain the local eNB identity from SIB1 (including the Cell Identity and gNB-ID-Length).

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

[0154] Step 402: Determine whether the first local variable stores any content. If the first local variable does not store any content (i.e., the base station coverage area where the UE was last located did not support / provide time synchronization status, but now supports / provides time synchronization status), execute step 403. If the first local variable stores a first storage event identifier, execute step 404.

[0155] Step 403: Determine that the timing synchronization state has changed, and notify the NAS layer of the change in target information; update the first local variable, the third local variable, and the fourth local variable; (i.e., use the first event identifier as the second stored event identifier, and store the second stored event identifier as the storage 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 storage content of the third local variable, or replace the storage 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 storage content of the fourth local variable, or replace the storage content of the fourth local variable with the second stored network identifier;) wherein the target information may include at least one of the content of clock quality details and timing synchronization state information;

[0156] Step 404: Determine whether the values ​​of the first event identifier and the first stored event identifier are equal; if the values ​​of the first event identifier and the first stored event identifier are not equal, execute step 405; if the values ​​of the first event identifier and the first stored event identifier are equal, execute step 406:

[0157] Step 405: Determine that the timing synchronization state has changed, and notify the NAS layer of the change in the target information; update the first local variable, the third local variable, and the fourth local variable; (i.e., 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;)

[0158] Step 406: Determine whether 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 first network identifier is equal to the value of the first stored network identifier stored in the fourth local variable; if the first local base station identifier is equal to the value of the first local stored base station identifier, and the first network identifier is equal to the value of the first stored network identifier, execute step 407; if the first local base station identifier is not equal to the value of the first stored local base station identifier, execute step 408; if the first network identifier is not equal to the value of the first stored network identifier, execute step 409;

[0159] Step 407: Determine that the timing synchronization state has not changed;

[0160] Step 408: Determine that the timing synchronization state has changed, notify the NAS layer of the change in the target information, and 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).

[0161] Step 409: Determine that the timing synchronization state has changed, notify the NAS layer of the change in the target information; update the fourth local variable (ie, use the first network identifier as the fourth storage network identifier, and replace the storage content of the fourth local variable with the fourth storage network identifier).

[0162] The first network identifier satisfies one of the following conditions:

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

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

[0165] Accordingly, the first local base station identifier is determined based on the target identification information. For example, the high X bits of the cell identification information (CellIdentity) in the target identification information are taken as the first local base station identifier, where X is the Gnb-ID-length in the target identification information; the target identification information satisfies one of the following:

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

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

[0168] The method for determining a timed synchronization state change provided in an embodiment of the present application can be performed by a device for determining a timed synchronization state change. In the embodiment of the present application, the method for determining a timed synchronization state change performed by the device for determining a timed synchronization state change is used as an example to illustrate the device for determining a timed synchronization state change provided in an embodiment of the present application.

[0169] As shown in FIG5 , an embodiment of the present application further provides an apparatus for determining a timing synchronization state change. The apparatus 50 for determining a timing synchronization state change may include the following modules:

[0170] The determining module 501 is configured to determine whether the timing synchronization state of the terminal has changed based on whether a first stored event identifier corresponding to a second event is stored locally when a first event identifier corresponding to a first event is obtained;

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

[0172] Optionally, the determining module 501 includes:

[0173] a first determining submodule, configured to determine, when the first storage event identifier is not stored locally, whether the timing synchronization state of the terminal has changed;

[0174] The second determining submodule is 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 stored locally.

[0175] Optionally, the second determining submodule includes:

[0176] a first determining unit, configured to determine that a timing synchronization state of the terminal has changed when the first event identifier is different from the first stored event identifier;

[0177] The second determination unit is used to determine whether the timing synchronization state of the terminal changes according to the identification information of the current resident base station of the terminal and the identification information of the resident base station locally stored by the terminal when the first event identifier is the same as the first stored event identifier.

[0178] Optionally, the identification information of the current resident base station of the terminal includes a first base station identifier, the identification information of the resident base station locally stored by the terminal includes a first stored base station identifier, and both the first base station identifier and the first stored base station identifier are global base station identifiers;

[0179] The second determining unit is specifically configured to:

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

[0181] 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.

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

[0183] The device further comprises at least one of the following modules:

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

[0185] a second updating 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, and update the storage 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 storage content of the second local variable to the third stored base station identifier;

[0186] The third updating module is used to use the first base station identifier as the fourth stored base station identifier when the first base station identifier is different from the first stored base station identifier, and update the storage content of the second local variable to the fourth stored base station identifier.

[0187] Optionally, the identification information of the current resident base station of the terminal includes a first local base station identifier and a first network identifier, and the identification information of the resident base station locally stored by the terminal includes a first stored local base station identifier and a first stored network identifier;

[0188] The second determining unit is specifically configured to:

[0189] 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, determining that the timing synchronization state of the terminal has not changed;

[0190] 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, it is determined that the timing synchronization state of the terminal has changed.

[0191] 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;

[0192] The device further comprises at least one of the following modules:

[0193] a fourth updating module, configured to, when the first stored event identifier is not stored locally, use the first event identifier as the second stored event identifier, update the storage 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 storage 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 storage content of the fourth local variable to the second stored network identifier;

[0194] a fifth updating 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, and update the storage 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, and update the storage 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 storage content of the fourth local variable to the third stored network identifier;

[0195] a sixth updating 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 storage content of the third local variable to the fourth stored local base station identifier;

[0196] The seventh updating module is configured to use the first network identifier as a fourth storage network identifier and update the storage content of the fourth local variable to the fourth storage network identifier when the first network identifier is different from the first storage network identifier.

[0197] Optionally, the identification information of the base station where the terminal currently resides is determined according to the identification information of the target network, and the identification information of the target network is determined according to the support status of the network where the terminal resides for the public land mobile network PLMN and the non-public network NPN.

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

[0199] In a case where the network where the terminal resides only supports PLMN, the target network identification information includes a first object in a PLMN identification information list in a first system information block SIB1, where the first object is the first PLMN identification information in the PLMN identification information list following a broadcast order;

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

[0201] In the case that the network where the terminal resides 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 in the NPN identification information list following the broadcast order.

[0202] Optionally, the identification information of the current resident base station of the terminal 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 current resident base station of the terminal includes the first network identifier and the first local base station identifier;

[0203] Wherein, in the case where the network where the terminal resides 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;

[0204] In a case where the network where the terminal resides supports sharing of PLMN and 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;

[0205] In the case that the network where the terminal resides 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.

[0206] Optionally, the device further comprises:

[0207] a notification module, configured to notify the terminal of a change in non-access stratum target information when determining that the timing synchronization state of the terminal has changed;

[0208] The target information includes at least one of clock quality information and timing synchronization status information.

[0209] Optionally, the device further comprises:

[0210] The acquisition module is configured to acquire the first event identifier from a ninth system information block SIB9.

[0211] The apparatus for determining a change in the timing synchronization state in the embodiments of the present application may be an electronic device, such as an electronic device having an operating system, or a component in the electronic device, such as an integrated circuit or chip. The electronic device may be a terminal, or may be another device other than a terminal. For example, the terminal may include, but is not limited to, the types of terminal 11 listed above, and the other device may be a server, a network attached storage (NAS), etc., which is not specifically limited in the embodiments of the present application.

[0212] The device for determining the change of the timing synchronization state provided in the embodiment of the present application can implement the various processes implemented in the method embodiments of Figures 2 to 4 and achieve the same technical effects. To avoid repetition, they will not be described here.

[0213] As shown in Figure 6, an embodiment of the present application also provides a communication device 600, including a processor 601 and a memory 602, and the memory 602 stores programs or instructions that can be run on the processor 601. For example, when the communication device 600 is a terminal, the program or instruction is executed by the processor 601 to implement the various steps of the above-mentioned method embodiment for determining the change of the timing synchronization state, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0214] The present application also provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG2 . This terminal embodiment corresponds to the aforementioned terminal-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG7 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0215] The terminal 700 includes but is not limited to: 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 at least some of the components of the processor 710.

[0216] Those skilled in the art will appreciate that the terminal 700 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 710 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG7 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0217] It should be understood that in an embodiment of the present application, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042, and the graphics processor 7041 processes the image data of a static picture or video 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 a touch panel 7071 and at least one of 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. 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, and an operating stick, which will not be repeated here.

[0218] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 701 may transmit the data to the processor 710 for processing. Furthermore, the RF unit 701 may send uplink data to the network-side device. Typically, the RF unit 701 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0219] The memory 709 can be used to store software programs or instructions and 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, wherein the first storage area may store an operating system, applications 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 a volatile memory or a 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 (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0220] Processor 710 may include one or more processing units. Optionally, processor 710 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 710.

[0221] The processor 710 is configured to: upon obtaining a first event identifier corresponding to a first event, determine whether a timing synchronization state of the terminal has changed according to whether a first stored event identifier corresponding to a second event is stored locally;

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

[0223] Optionally, the processor 710 determines whether the timing synchronization state of the terminal changes according to whether a first stored event identifier corresponding to the second event is stored locally, including:

[0224] In a case where the first storage event identifier is not stored locally, determining that a timing synchronization state of the terminal has changed;

[0225] In a case where the first stored event identifier is stored locally, it is determined whether the timing synchronization state of the terminal changes according to the first event identifier and the first stored event identifier.

[0226] Optionally, the processor 710 determines whether the timing synchronization state of the terminal changes according to the first event identifier and the first stored event identifier, including:

[0227] When the first event identifier is different from the first stored event identifier, determining that a timing synchronization state of the terminal has changed;

[0228] When the first event identifier is the same as the first stored event identifier, it is determined whether the timing synchronization state of the terminal changes according to the identifier information of the current resident base station of the terminal and the identifier information of the resident base station stored locally by the terminal.

[0229] Optionally, the identification information of the current resident base station of the terminal includes a first base station identifier, the identification information of the resident base station locally stored by the terminal includes a first stored base station identifier, and both the first base station identifier and the first stored base station identifier are global base station identifiers;

[0230] The processor 710 determines whether the timing synchronization state of the terminal changes according to the identification information of the current resident base station of the terminal and the identification information of the resident base station stored locally by the terminal, including:

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

[0232] 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.

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

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

[0235] In a case where the first storage event identifier is not stored locally, the first event identifier is used as the second storage event identifier, and the storage content of the first local variable is updated to the second storage event identifier, the first base station identifier is used as the second storage base station identifier, and the storage content of the second local variable is updated to the second storage base station identifier;

[0236] In a case where the first event identifier is different from the first stored event identifier, the first event identifier is used as a third stored event identifier, and the storage content of the first local variable is updated to the third stored event identifier, the first base station identifier is used as a third stored base station identifier, and the storage content of the second local variable is updated to the third stored base station identifier;

[0237] In a case where the first base station identifier is different from the first stored base station identifier, the first base station identifier is used as the fourth stored base station identifier, and the storage content of the second local variable is updated to the fourth stored base station identifier.

[0238] Optionally, the identification information of the current resident base station of the terminal includes a first local base station identifier and a first network identifier, and the identification information of the resident base station locally stored by the terminal includes a first stored local base station identifier and a first stored network identifier;

[0239] The processor 710 determines whether the timing synchronization state of the terminal changes according to the identification information of the current resident base station of the terminal and the identification information of the resident base station stored locally by the terminal, including:

[0240] 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, determining that the timing synchronization state of the terminal has not changed;

[0241] 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, it is determined that the timing synchronization state of the terminal has changed.

[0242] 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;

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

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

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

[0246] In a case where the first local base station identifier is different from the first stored local base station identifier, using the first local base station identifier as a fourth stored local base station identifier, and updating the storage content of the third local variable to the fourth stored local base station identifier;

[0247] In a case where the first network identifier is different from the first storage network identifier, the first network identifier is used as the fourth storage network identifier, and the storage content of the fourth local variable is updated to the fourth storage network identifier.

[0248] Optionally, the identification information of the base station where the terminal currently resides is determined according to the identification information of the target network, and the identification information of the target network is determined according to the support status of the network where the terminal resides for the public land mobile network PLMN and the non-public network NPN.

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

[0250] In a case where the network where the terminal resides only supports PLMN, the target network identification information includes a first object in a PLMN identification information list in a first system information block SIB1, where the first object is the first PLMN identification information in the PLMN identification information list following a broadcast order;

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

[0252] In the case that the network where the terminal resides 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 in the NPN identification information list following the broadcast order.

[0253] Optionally, the identification information of the current resident base station of the terminal 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 current resident base station of the terminal includes the first network identifier and the first local base station identifier;

[0254] Wherein, in the case where the network where the terminal resides 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;

[0255] In a case where the network where the terminal resides supports sharing of PLMN and 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;

[0256] In the case that the network where the terminal resides 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.

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

[0258] When determining that the timing synchronization state of the terminal has changed, controlling the access layer of the terminal to notify the non-access layer of the target information change;

[0259] The target information includes at least one of clock quality information and timing synchronization status information.

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

[0261] The first event identifier is obtained from a ninth system information block SIB9.

[0262] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned method embodiment for determining the change of timing synchronization state, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0263] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned method embodiment for determining the change in the timing synchronization state are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0264] 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 disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0265] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method embodiment for determining the change of the timing synchronization state, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0266] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0267] An embodiment of the present application further 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 the various processes of the above-mentioned method embodiment for determining changes in timing synchronization status, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0268] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments 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 the opposite 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 also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

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

[0270] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for determining a timing synchronization state change, wherein: The method comprises: When the terminal obtains the first event identifier corresponding to the first event, the terminal determines whether the timing synchronization state of the terminal changes according to whether the first stored event identifier corresponding to the second event is stored locally; The first event and the second event are related to a timing synchronization state of the terminal.

2. The method according to claim 1, wherein: The terminal determines, according to whether a first stored event identifier corresponding to a second event is stored locally, whether a timing synchronization state of the terminal changes, including: In a case where the first storage event identifier is not stored locally, the terminal determines that a timing synchronization state of the terminal changes; In a case where the first stored event identifier is stored locally, the terminal determines whether a timing synchronization state of the terminal changes according to the first event identifier and the first stored event identifier.

3. The method according to claim 2, wherein: The terminal determines, according to the first event identifier and the first stored event identifier, whether a timing synchronization state of the terminal changes, including: When the first event identifier is different from the first stored event identifier, the terminal determines that a 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 changes according to the identifier information of the current resident base station of the terminal and the identifier information of the resident base station stored locally by the terminal.

4. The method according to claim 3, wherein: The identification information of the current resident base station of the terminal includes a first base station identification, and the identification information of the resident base station stored locally by the terminal includes a first stored base station identification, and both the first base station identification and the first stored base station identification are global base station identifications; The terminal determines, according to identification information of a base station where the terminal currently resides and identification information of a base station where the terminal resides stored locally, whether a timing synchronization state of the terminal changes, 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 a timing synchronization state of the terminal has changed.

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

6. The method according to claim 3, wherein: The identification information of the current resident base station of the terminal includes a first local base station identification and a first network identification, and the identification information of the resident base station stored locally by the terminal includes a first stored local base station identification and a first stored network identification; The terminal determines, according to identification information of a base station where the terminal currently resides and identification information of a base station where the terminal resides stored locally, whether a timing synchronization state of the terminal changes, 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; In a 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, the terminal determines that a timing synchronization state of the terminal has changed.

7. The method according to claim 6, wherein: 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: In the case where the first stored event identifier is not stored locally, the terminal uses the first event identifier as the second stored event identifier, updates the storage 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 storage 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 storage content of the fourth local variable to the second stored network identifier; In the case where 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 storage 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 storage 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 storage 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 a fourth stored local base station identifier, and updates the storage content of the third local variable to the fourth stored local base station identifier; In the case that the first network identifier is different from the first stored network identifier, the terminal uses the first network identifier as a fourth stored network identifier, and updates the storage content of the fourth local variable to the fourth stored network identifier.

8. The method according to any one of claims 3 to 7, wherein: The identification information of the base station where the terminal currently resides is determined according to the identification information of the target network, and the identification information of the target network is determined according to the support status of the network where the terminal resides for the public land mobile network PLMN and the non-public network NPN.

9. The method according to claim 8, wherein: The target network identification information satisfies one of the following: In the case where the network where the terminal resides only supports PLMN, the target network identification information includes a first object in a PLMN identification information list in a first system information block SIB1, where the first object is the first PLMN identification information in the PLMN identification information list that follows a broadcast order; In the case where the network where the terminal resides supports sharing of PLMN and NPN, the target network identification information includes the first object in the PLMN identification information list in SIB1; In the case that the network where the terminal resides 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 in the NPN identification information list following the broadcast order.

10. The method according to claim 9, wherein: The identification information of the base station where the terminal currently resides includes a first base station identifier, and the first base station identifier is determined according to a first network identifier and a first local base station identifier; or, the identification information of the base station where the terminal currently resides includes the first network identifier and the first local base station identifier; The first network identifier and the first local base station identifier satisfy one of the following conditions: In a case where the network where the terminal resides 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; In the case where the network where the terminal resides supports sharing of PLMN and 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; In the case that the network where the terminal resides 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 comprises: In the case of determining that the timing synchronization state of the terminal has changed, the access layer of the terminal notifies the non-access layer of the change in target information; The target information includes at least one of clock quality information and timing synchronization status 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 a ninth system information block SIB9.

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

14. The device according to claim 13, wherein: The determination module comprises: A first determining submodule, configured to determine that a timing synchronization state of the terminal has changed when the first storage event identifier is not stored locally; The second determining submodule is 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 stored locally.

15. The device according to claim 14, wherein: The second determining submodule includes: A first determining unit, configured to determine that a timing synchronization state of the terminal has changed when the first event identifier is different from the first stored event identifier; The second determination unit is used to determine whether the timing synchronization state of the terminal changes according to the identification information of the current resident base station of the terminal and the identification information of the resident base station locally stored by 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 identification information of the current resident base station of the terminal includes a first base station identification, and the identification information of the resident base station stored locally by the terminal includes a first stored base station identification, and both the first base station identification and the first stored base station identification are global base station identifications; The second determining unit is specifically configured to: When the first base station identifier is the same as the first stored base station identifier, determining 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, it is determined that the timing synchronization state of the terminal has changed.

17. The device according to claim 16, wherein: The first storage event identifier is stored in a first local variable, and the first storage base station identifier is stored in a second local variable; The device also includes at least one of the following modules: a first updating module, configured to, when the first storage event identifier is not stored locally, use the first event identifier as a second storage event identifier, and update the storage content of the first local variable to the second storage event identifier, use the first base station identifier as a second storage base station identifier, and update the storage content of the second local variable to the second storage base station identifier; a second updating 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, and update the storage 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 storage content of the second local variable to the third stored base station identifier; The third updating module is used to use the first base station identifier as a fourth storage base station identifier when the first base station identifier is different from the first storage base station identifier, and update the storage content of the second local variable to the fourth storage base station identifier.

18. The device according to claim 15, wherein: The identification information of the current resident base station of the terminal includes a first local base station identification and a first network identification, and the identification information of the resident base station stored locally by the terminal includes a first stored local base station identification and a first stored network identification; The second determining 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, determining 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, it is determined that the timing synchronization state of the terminal has changed.

19. The device according to claim 18, wherein: 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 also includes at least one of the following modules: a fourth updating module, configured to, when the first stored event identifier is not stored locally, use the first event identifier as the second stored event identifier, and update the storage 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, and update the storage 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 storage content of the fourth local variable to the second stored network identifier; a fifth updating 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, and update the storage 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, and update the storage 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 storage content of the fourth local variable to the third stored network identifier; a sixth updating 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 storage content of the third local variable to the fourth stored local base station identifier; The seventh updating module is used to use the first network identifier as a fourth storage network identifier and update the storage content of the fourth local variable to the fourth storage network identifier when the first network identifier is different from the first storage network identifier.

20. The device according to any one of claims 15 to 19, wherein: The identification information of the base station where the terminal currently resides is determined according to the identification information of the target network, and the identification information of the target network is determined according to the support status of the network where the terminal resides for the public land mobile network PLMN and the non-public network NPN.

21. The device according to claim 20, wherein: The target network identification information satisfies one of the following: In the case where the network where the terminal resides only supports PLMN, the target network identification information includes a first object in a PLMN identification information list in a first system information block SIB1, where the first object is the first PLMN identification information in the PLMN identification information list that follows a broadcast order; In the case where the network where the terminal resides supports sharing of PLMN and NPN, the target network identification information includes the first object in the PLMN identification information list in SIB1; In the case that the network where the terminal resides 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 in the NPN identification information list following the broadcast order.

22. The device according to claim 21, wherein The identification information of the base station where the terminal currently resides includes a first base station identifier, and the first base station identifier is determined according to a first network identifier and a first local base station identifier; or, the identification information of the base station where the terminal currently resides includes the first network identifier and the first local base station identifier; Wherein, in the case where the network where the terminal resides 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; In the case where the network where the terminal resides supports sharing of PLMN and 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; In the case that the network where the terminal resides 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.

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

24. A terminal, wherein: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method for determining a timing synchronization state change according to any one of claims 1 to 12 are implemented.

25. A readable storage medium, wherein: The readable storage medium stores a program or an instruction, and when the program or the instruction is executed by the processor, the steps of the method for determining a timing synchronization state change according to any one of claims 1 to 12 are implemented.

26. A chip, wherein: The chip 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 the steps of the method for determining a change in a timing synchronization state as described in any one of claims 1 to 12.

Images