WO2022156332A1 - 网络状态同步方法、装置、存储介质及电子设备 - Google Patents

网络状态同步方法、装置、存储介质及电子设备 Download PDF

Info

Publication number
WO2022156332A1
WO2022156332A1 PCT/CN2021/130910 CN2021130910W WO2022156332A1 WO 2022156332 A1 WO2022156332 A1 WO 2022156332A1 CN 2021130910 W CN2021130910 W CN 2021130910W WO 2022156332 A1 WO2022156332 A1 WO 2022156332A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
synchronization
state
service
storage
Prior art date
Application number
PCT/CN2021/130910
Other languages
English (en)
French (fr)
Inventor
谢朝阳
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Publication of WO2022156332A1 publication Critical patent/WO2022156332A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/30—Reselection being triggered by specific parameters by measured or perceived connection quality data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of computer technologies, and in particular, to a network state synchronization method, device, storage medium and electronic device.
  • Embodiments of the present application provide a network state synchronization method, apparatus, storage medium, and electronic device, which can allocate service threads to appropriate processor clusters.
  • the technical solutions of the embodiments of the present application are as follows:
  • an embodiment of the present application provides a network state synchronization method, the method includes:
  • tracking area identifier exists in the tracking area identifier list before disconnection, perform network state synchronization to the network end.
  • an embodiment of the present application provides a network state synchronization device, the device comprising:
  • an identification acquisition module configured to acquire the current tracking area identification of the network when the first device goes offline and restores the network
  • a state synchronization module configured to synchronize the network state to the network end if the tracking area identifier exists in the tracking area identifier list before going offline.
  • an embodiment of the present application provides a computer storage medium, where the computer storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the above method steps.
  • an embodiment of the present application provides an electronic device, which may include: a processor and a memory; wherein, the memory stores a computer program, and the computer program is adapted to be loaded by the processor and execute the above method steps .
  • the first device acquires the current tracking area identifier of the network when the first device disconnects from the network and restores the network; if the tracking area identifier exists in the tracking before disconnection In the area identification list, the first device can synchronize the network state to the network, thereby avoiding the problem of waiting for the network to perform paging when the tracking area identification exists in the tracking area identification list before going offline in the related art.
  • the problem of high latency of network status synchronization greatly reduces the latency of network status synchronization, ensures the normal business services of subsequent devices, and ensures that the first device synchronizes with the network status in real time after recovery from the network. sex.
  • FIG. 1 is a schematic flowchart of a network state synchronization method provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of a device movement scenario involved in a network state synchronization method provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of another device movement scenario involved in the network state synchronization method provided by the embodiment of the present application.
  • FIG. 4 is a schematic flowchart of another network state synchronization method provided by an embodiment of the present application.
  • FIG. 5 is a schematic flowchart of another network state synchronization method provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of an off-network recovery scenario involved in a network state synchronization method provided by an embodiment of the present application
  • FIG. 7 is a schematic diagram of another off-network recovery scenario involved in the network state synchronization method provided by the embodiment of the present application.
  • FIG. 8 is a schematic flowchart of another network state synchronization method provided by an embodiment of the present application.
  • FIG. 9 is a schematic diagram of a scenario of device state synchronization in a local area network involved in a method for network state synchronization provided by an embodiment of the present application;
  • FIG. 10 is a schematic diagram of a scenario architecture for network state synchronization provided by an embodiment of the present application.
  • FIG. 11 is a schematic structural diagram of a network state synchronization apparatus provided by an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a state synchronization module provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • FIG. 14 is a schematic structural diagram of an operating system and a user space provided by an embodiment of the present application.
  • Figure 15 is an architecture diagram of the Android operating system in Figure 13;
  • FIG. 16 is an architectural diagram of the IOS operating system in FIG. 13 .
  • a plurality means two or more.
  • “And/or”, which describes the association relationship of the associated objects means that there can be three kinds of relationships, for example, A and/or B, which can mean that A exists alone, A and B exist at the same time, and B exists alone.
  • the character “/” generally indicates that the associated objects are an "or" relationship.
  • This specification provides a network state synchronization method, which is applied to a first device, and the method includes:
  • tracking area identifier exists in the tracking area identifier list before disconnection, perform network state synchronization to the network end.
  • the performing network state synchronization to the network includes:
  • the performing network state synchronization to the network based on the synchronization decision information includes:
  • the synchronization judgment information is the off-network duration, and if the off-network duration is greater than the preset duration threshold, network state synchronization is performed to the network; or,
  • the synchronization judgment information is the network interaction information before the first device is disconnected from the network. If the network interaction information matches the reference interaction information, the network state synchronization is performed to the network terminal; the network interaction information includes the network interaction frequency. , at least one of network interaction data volume, and network interaction scenarios.
  • the performing network state synchronization to the network includes:
  • the verification result sent by the network terminal is received, and it is determined based on the verification result that the network state synchronization is successful.
  • the sending a network synchronization request to the network includes:
  • the acquiring a data transmission state and generating a network synchronization request based on the data transmission state includes:
  • the data transmission state is the calling service state, generating a service service request
  • the data transmission state is the called service state or the idle service state, a tracking area update request is generated.
  • the sending a network synchronization request to the network so that the network performs network recovery verification on the network synchronization request includes:
  • a network synchronization request carrying a temporary identity identifier is sent to the network terminal, so that the network terminal performs network recovery verification on the network synchronization request based on the temporary identity identifier.
  • the receiving the verification result sent by the network terminal, and determining that the network state synchronization is successful based on the verification result includes:
  • a network identity registration process is initiated to the network end, and after the network identity registration process is successful, it is determined that the network state synchronization is successful.
  • the receiving the verification result sent by the network terminal, and determining that the network state synchronization is successful based on the verification result includes:
  • the verification success information sent by the network terminal is received, and it is determined that the synchronization of the network state is successful.
  • the performing network state synchronization to the network based on the synchronization decision information includes:
  • a monitoring timer for the network calling service is started, and a network service instruction for the network calling service is monitored based on the monitoring timer.
  • the performing network state synchronization to the network includes:
  • the network state is synchronized to the network terminal based on the first storage state.
  • the judging the storage state of the first temporary identity of the first device on the network includes:
  • the second storage state is the storage state of the second temporary identity corresponding to the second device on the network end; the second device and the first The devices are under the same local area network;
  • the second storage state is a storage loss state
  • the first storage state on the network for the first temporary identity of the first device is the storage loss state
  • the second storage state is the storage normal state, it is determined that the storage state of the first temporary identity identifier for the first device on the network end is the storage normal state.
  • the method further includes:
  • the performing network state synchronization to the network terminal based on the first storage state includes:
  • the first storage state is a storage loss state
  • a network identity registration process is initiated to the network terminal, and after the network identity registration process is successful, it is determined that the network state synchronization is successful;
  • the first storage state is a normal storage state
  • a network synchronization request is sent to the network end, so that the network end performs network recovery verification on the first device; it is determined that the network state synchronization is successful.
  • a network state synchronization method is proposed, which can be implemented by relying on a computer program, and can run on a network state synchronization device based on the von Neumann system.
  • the computer program can be integrated into an application or run as a stand-alone utility application.
  • the network state synchronization method includes:
  • Step S101 when the first device goes offline and restores the network, obtain the current tracking area identifier of the network;
  • the first device usually obtains the corresponding communication network service based on the serving cell corresponding to the network side.
  • the serving cell refers to the current resident network cell that currently provides network data services for the first device (such as a terminal UE), and the network serving cell is also referred to as the area where the first device can currently obtain network services (such as LTE network services, NR network services) , is a cell divided from the entire communication service area (such as LTE communication service area, NR network service area) provided by the network.
  • eNB base station
  • Establish a wireless connection, such as the first device the electronic device that supports the communication service corresponding to the communication standard (such as LTE communication standard) can communicate in any cell in the communication service area, such as using the serving cell to carry the voice call uplink/downlink business data.
  • FIG. 2 which is a schematic diagram of a device movement scenario involved in the present application
  • the first device is at time point t1 in FIG. 2 .
  • Position A belongs to the signal coverage of the base station in cell A. If the first device moves from the current serving cell to an area with weaker signal quality in the serving cell, it is in position B in Figure 2 at time t2.
  • the network signal quality will be weak.
  • the network will be disconnected due to poor signal quality.
  • the first device re-enters the coverage area of a serving cell with better signal quality (such as another serving cell B)
  • the first device can re-register in serving cell B.
  • the first device recovers from off-network to on-network, that is, restores the network.
  • the first device may be in a normal service idle state (ie, no uplink and downlink transmission services are performed at this time).
  • the base station corresponding to the serving cell will broadcast a synchronization frame, such as a synchronization wake-up packet, and the first device may receive the network interface of the current serving cell from the network of the current serving cell.
  • the identification information of the TA to which the current serving cell belongs is obtained from the synchronization frame broadcast and sent by the device (such as a base station), and then the TAI of the TA to which the target serving cell belongs is determined according to the identification information of the TA to which the current serving cell belongs, that is, the tracking area synchronization identification.
  • all cells in the tracking area registered by the UE are usually represented in the form of tracking area identifiers, and the tracking area identifiers corresponding to all cells in the tracking area registered by the UE (such as the first device) belong to the network
  • the terminal is in the tracking area identification list issued by the UE (such as the first device) before it is on the network.
  • TA is a cell-level configuration
  • multiple cells can be configured with the same TA, and a cell can only belong to one TA. That is, each cell corresponds to a unique tracking area identifier, and there may be multiple cells under the same tracking area identifier.
  • Step S102 If the tracking area identifier exists in the tracking area identifier list before going offline, perform network state synchronization to the network end.
  • the tracking area identifier (TrackingAreaIdentity, TAI) list is allocated to the first device by the network when it initiates the network, and the tracking area identifier (TrackingAreaIdentity, TAI) list contains multiple tracking area identifiers, and the first device obtains the The current tracking area identifier of the network.
  • the tracking area identifier does not exist in the tracking area identifier list before going offline, each network device corresponding to the network end (such as the network device corresponding to the corresponding tracking area identifier in the tracking area identifier list, such as base station) can find the UE by sending a paging message.
  • the first device When the tracking area identifier does not exist in the tracking area identifier list before disconnection, when the first device moves out of the tracking area, that is, when the cell reselected by the first device is not in the tracking area, in order to When there is a downlink data service, the first device can also be paged. Usually, the first device will actively initiate network state synchronization.
  • the first device In the related art, if the tracking area identifier exists in the tracking area identifier list before going offline, usually each network device corresponding to the network end can page the first device when the corresponding data service is generated. Therefore, the first device In this case, the first device will be in an idle state after the network is restored, waiting for paging from the network side to synchronize the network status with the network side. During the period of disconnection, the network side may have some processes (such as downlink data) to interact with the first device, and the first device cannot know the information in time because it is offline at that time.
  • some processes such as downlink data
  • FIG. 3 is a paging sequence diagram of an off-network network terminal involved in the present application.
  • the current serving cell and other Cell reference signals of neighboring serving cells are measured, and based on the measurement results, it is determined to start a cell reselection process. If the first device re-enters the coverage area of a serving cell with better signal quality, the first device determines a target serving cell B with good signal quality from other adjacent serving cells, and the first device can re-register in serving cell B. At this time Serving cell B is relocated to the network, that is, time point t3;
  • the first device obtains the tracking area identifier of the re-registered serving cell B, and if the tracking area identifier exists in the list of tracking area identifiers before going offline, it usually waits for the network to perform paging.
  • the network side needs to interact with the first device (such as the following data scenario)
  • the network side needs to interact with the first device at a certain point in the time period from t3 to t2
  • a paging process (that is, a paging process) for the first device will be initiated.
  • the network usually corresponds to the paging processing strategy of paging failure. For example, when there is no response to the paging, it will cache the relevant service data, and then re-initiate the paging process after a period of time. Before the network re-initiates the paging process. , the first device will have the above-mentioned situation of network recovery within t3.
  • the first device Since the tracking area identifier of the cell that has relocated to the network exists in the tracking area identifier list before the network is disconnected, at this time, the first device is in an idle state again, and the first device is in an idle state again. The device usually does not initiate network synchronization. In this scenario, the first device can only wait for the network to re-initiate the paging process. It is assumed that the network re-initiates the paging process at time t5, because the first device is already on the network at this time. Recovery, the retry paging is successful at this time, and then the network side will transmit the service data;
  • the delay time is (t5-t4)
  • the paging response delay is also high
  • the network state synchronization is not timely.
  • the first device can execute the network state synchronization method of the present application, and if the tracking area identifier exists in the tracking area identifier list before the network is disconnected, the first device can send the network state to the network after the network is restored. Synchronize. So that the network can synchronize the network state based on the process initiated by the first device, so that the network can determine the network state of the first device in time, thereby ensuring accurate real-time synchronization of service information between the first device and the network.
  • a network synchronization method may be: the first device and the network end pre-determine a network synchronization strategy, and when the network of the first device recovers, synchronization information may be sent to the network end based on the network synchronization strategy, for example, a heartbeat packet (in the heartbeat packet) can be sent.
  • the data is empty) to reduce the transmission overhead, so as to facilitate the network to determine the terminal network status recovery.
  • a network synchronization method the first device can actively send a service service request to the network, wherein the service service request mainly involves the calling scene, that is, the service of the uplink service will only be generated when the first device has the scene of the uplink service data Service request, in this application, the first device firstly determines whether there is a calling service currently, and needs to send uplink service data based on the network side,
  • the first device If there is a calling service, the first device generates a service service request accordingly, and sends the service service request to the network end, so that the network end can determine that the current network state of the first device is restored;
  • the first device If there is no calling service, the first device is usually in an idle state at this time. At this time, it usually does not actively initiate a service request.
  • the first device can perform calling simulation, that is, actively act as the master.
  • the calling party simulates the calling scene, generates a service service request, and sends the service service request to the network end, so that the network end can determine that the current network state of the first device is restored;
  • the calling party simulation may be based on a preset calling simulation strategy , initiate a calling scenario to the specified device, and then a business service request can be generated according to the normal process.
  • the designated device may be preset, or may be an electronic device randomly determined based on a historical interaction scene of the first device.
  • the purpose of simulating a caller is to generate a service service request, so as to conform to the service process of the network side and avoid being shielded by the service response strategy of the network side.
  • a network synchronization method the first device can actively generate a tracking area update request in the current scenario, and send the tracking area update request to the network, so that the network can determine that the current network state of the first device is restored.
  • the first device acquires the current tracking area identifier of the network when the first device goes offline and restores the network; if the tracking area identifier exists in the tracking area identifier list before the network disconnection , the first device can synchronize the network state to the network, so as to avoid the network state synchronization caused by waiting for the network to perform paging when the tracking area identifier exists in the tracking area identifier list before going offline in the related art
  • the problem of high delay in the case of the network greatly reduces the synchronization delay of the network state, and ensures the normal business services of the subsequent equipment. And, the real-time synchronization of the first device with the network state is ensured after recovery from the off-line.
  • FIG. 4 is a schematic flowchart of another embodiment of a network state synchronization method proposed by the present application. specific:
  • Step S201 when the first device goes offline and restores the network, obtain the current tracking area identifier of the network;
  • Step S202 If the tracking area identifier exists in the tracking area identifier list before going offline, acquire synchronization decision information.
  • the tracking area identifier exists in the list of tracking area identifiers before going offline, it is not necessary to measure the requirement of network synchronization based on the current actual application environment, and determine whether to perform network state synchronization immediately. It is initiated only when the network status is synchronized, so as to avoid signaling conformity and reduce the probability of signaling storm.
  • the first device may preset a synchronization decision rule, and measure and quantify the urgency and timeliness of the current network synchronization based on the synchronization decision rule.
  • Different synchronization decision rules correspond to different types of synchronization decision information, and specific synchronization decision rules may be determined based on the actual application environment.
  • An optional synchronization judgment rule may be to judge the off-network duration, determine a duration threshold by acquiring a large number of sample data in an actual application environment, and measure whether to perform network synchronization based on the duration threshold.
  • the synchronization decision rule may be to decide on network interaction information, where the network interaction information includes at least one of network interaction frequency, network interaction data volume, and network interaction scenarios.
  • the network interaction frequency is a measurement value of the interaction frequency of uplink data and downlink data, for example, the interaction time interval parameter is used as the network interaction frequency.
  • the network interaction data volume is the total data volume of network uplink and downlink data in a certain period of time.
  • the network interaction scenario is the interactive application scenario of the first device, such as instant messaging scenario, e-commerce scenario, email sending and receiving scenario, video data scenario, etc.
  • the network interaction scenario is usually associated with the background application service on the first device, and can be based on the background application Service OK.
  • Step S203 Perform network state synchronization to the network based on the synchronization decision information.
  • the synchronization judgment information is the offline duration, then it can be judged whether the offline duration satisfies the network synchronization condition, and the network synchronization condition may be that the offline duration is greater than the preset duration threshold;
  • the network synchronization wait can be performed first, and the network status synchronization to the network end is not immediately initiated, but when there is a calling service, the network status synchronization is initiated. .
  • the network state synchronization to the network can be triggered immediately.
  • the first device can perform synchronization judgment on the off-network duration in real time when off-network, and when a certain moment in off-network is greater than the preset duration threshold, the first device can perform synchronization marking during network recovery.
  • the first device directly initiates network state synchronization to the network end based on the identified synchronization flag when the network is restored.
  • the synchronization decision information is the network interaction information before the first device goes offline, and if the network interaction information matches the reference interaction information, the network state synchronization is performed to the network end;
  • the network interaction information includes, but is not limited to, at least one of network interaction frequency, network interaction data volume, and network interaction scenarios.
  • the interaction frequency threshold can be set based on the network interaction frequency. If the network interaction frequency is greater than the interaction frequency threshold, the network state synchronization can be immediately triggered to the network end; otherwise, network synchronization waits.
  • a data volume threshold can be set based on the network interaction data volume. If the network interaction data volume is greater than the data volume threshold, network status synchronization to the network can be triggered immediately; otherwise, network synchronization waits.
  • At least one reference interaction scene can be preset based on the network interaction scene. If the network interaction scene belongs to the reference interaction scene, the network state synchronization to the network can be triggered immediately; otherwise, the network synchronization waits.
  • Step S204 performing network synchronization waiting, and monitoring the network service instruction for the network calling service
  • a corresponding execution strategy can be set based on the actual application environment, that is, even when the synchronization judgment information meets the network synchronization conditions, such as when the off-network duration is greater than the duration threshold, the network terminal will not be notified immediately.
  • the first device may wait for network synchronization when the synchronization decision information satisfies the network synchronization condition, that is, not to perform network synchronization immediately, because generally speaking, the first device is in an idle state at this time, and there is no need to initiate network synchronization earlier.
  • the network service instructions for the network calling service that is, detect whether the current first device is in the calling service scenario, and whether there is uplink data to send, which is used to determine whether there is uplink data to be sent soon before synchronization is performed. send. If so, it is completed through the calling service process of the 3GPP protocol, and there is no need to perform the synchronization process (eg, tracking area list synchronization) in some embodiments.
  • the monitoring network service instruction for the network calling service in the implementation: the monitoring timer T data for the network calling service may be started, and the network service for the network calling service is monitored based on the monitoring timer. instruction.
  • Step S205 It is determined that the network service instruction is monitored, and the network state is synchronized to the network end.
  • the monitoring timer T data can be set with a countdown, and the countdown can be determined based on the actual application environment, or can be set when the first device leaves the factory, and then the first device can provide a human-computer interaction interface and be determined by the user.
  • a service request process is initiated by initiating a service request process (Service Request), that is, a service service request is generated, and a service request process is initiated based on the service service request. If the Tdata timer also times out, that is, the countdown ends, the first device performs a network state synchronization process to the network, such as initiating a tracking area list synchronization process.
  • Service Request service request process
  • the first device performs a network state synchronization process to the network, such as initiating a tracking area list synchronization process.
  • the above-mentioned detection of the network service instruction may be: after the synchronization judgment information satisfies the network synchronization condition, the first device creates a service process for detecting the network service instruction, and invokes the service process in the resource pool included in the first device.
  • Resources such as thread volume, I/O ports, and memory
  • the service process can set the service running duration, if the network service instruction is monitored within the running duration, the network state synchronization is performed to the network terminal; The network side performs network status synchronization.
  • the first device acquires the current tracking area identifier of the network when the first device goes offline and restores the network; if the tracking area identifier exists in the list of tracking area identifiers before the network is disconnected , the first device can synchronize the network state to the network, thereby avoiding network state synchronization caused by waiting for the network to perform paging when the tracking area identifier exists in the tracking area identifier list before offline in the related art
  • the problem of high delay in the case of the network greatly reduces the synchronization delay of the network state, and ensures the normal business services of the subsequent equipment.
  • FIG. 5 is a schematic flowchart of another embodiment of a network state synchronization method proposed by the present application. specific:
  • Step S301 when the first device goes offline and restores the network, obtain the current tracking area identifier of the network;
  • step S101 For details, refer to step S101, which will not be repeated here.
  • Step S302 Determine that the tracking area identifier exists in the list of tracking area identifiers before going offline.
  • step S102 For details, refer to step S102, which is not repeated here.
  • Step S303 acquiring a data transmission state, and generating a network synchronization request based on the data transmission state;
  • data transmission status includes but is not limited to calling service status, called service status and idle service status;
  • the first device in the calling service state usually the first device is in a business scenario of uplink data (such as call data, network application data) transmission, such as the application on the first device has uplink data that needs to be sent to the destination through the network.
  • uplink data such as call data, network application data
  • Another device indicated by the address is another device indicated by the address.
  • the first device in the called service state usually the first device is in a business scenario of downlink data (such as call data, network application data) transmission. equipment.
  • downlink data such as call data, network application data
  • the first device In the idle service state, generally, the first device has no downlink data or uplink data to transmit, and at this time, the first device is also in idle network service.
  • the first device can detect the data transmission status at the current time point, and in the specific implementation, it can traverse all business processes in the background to see if there is data to be transmitted (such as downloading downlink data, uploading uplink data), based on the business process
  • the business scenario of data transmission can detect the data transmission scenario at the current time point, and then determine the data transmission status based on the data transmission scenario.
  • the first device acquires the data transmission state, and if the data transmission state is the calling service state, generates a service service request.
  • the business service request is that in the calling business state, the first device can generate a business service request when there is uplink data that needs to be sent to another device indicated by the destination address through the network end due to the needs of the business scenario.
  • the first device initiates a service service request to request an uplink data transmission service from the network side, and the network side will perform service authentication based on the service service request. After reaching the first device, the first device can transmit the uplink data in the subsequent calling service.
  • the service service request may typically only be generated when the first device is in a calling service state.
  • the first device obtains the data transmission state, and if the data transmission state is the called service state or the idle service state, a tracking area update request may be generated.
  • the first device usually waits for the network end to arrive at the next paging interval, and then the network end initiates a paging process for the first device. At this time, based on paging In the process, the network end will synchronize the network status with the first device.
  • the first device can be actively sent to the network when the first device is in the called service state or the idle service state Initiate network state synchronization; further, in order to avoid the occurrence of any synchronization message, the synchronization message will be blocked by the relevant policy (such as the load policy) of the network side. Therefore, the first device can generate a tracking area update request at this time, and the tracking area update The request usually has a higher priority on the network side, and usually the network side can respond to the tracking area update request in time.
  • the first device after the first device generates a network synchronization request based on the data transmission state, such as a tracking area update request and a service service request, the first device can send a network synchronization request to the network.
  • a network synchronization request based on the data transmission state, such as a tracking area update request and a service service request
  • Step S304 Send a network synchronization request to the network, so that the network performs network recovery verification on the network synchronization request.
  • the communication request process between the network end and the corresponding device usually involves network verification, and the smooth progress of the network verification is based on the identity of the corresponding device, such as a temporary identity.
  • the network synchronization request when the first device generates a network synchronization request, such as a tracking area update request and a service service request; the network synchronization request will carry an identification, and the identification can facilitate the network to perform network recovery verification on the network synchronization request.
  • the network synchronization request Before the network synchronization request is received, since the paging process for the first device fails, it will be determined that the first device is disconnected or offline due to network failure. After receiving the network recovery verification, it can be synchronized based on the network The identity identifier carried in the request is verified for network recovery, that is, it is detected whether the first device recovers the network.
  • the network side will be involved in the verification process of the identity of the first device, based on matching the identity with the reference identity saved before the first device goes off the network, if it matches, the identity verification is passed, and it is not. If it matches, the network synchronization request is rejected, and the network synchronization fails at this time.
  • the identity identifier can be an International Mobile Subscriber Identification Number (IMSI), and IMSI is a sign that distinguishes mobile users, which is stored in the SIM card and can be used to distinguish valid information of mobile users. Or an International Mobile Station Equipment Identity (IMEI) to identify a mobile user (such as a first device) in a certain mobile communication network corresponding to the network end.
  • IMSI International Mobile Subscriber Identification Number
  • IMEI International Mobile Station Equipment Identity
  • an identity such as an IMSI is usually security data involving device privacy.
  • the UE ie, the first device
  • the MME mobility management entity
  • IP Internet Protocol
  • S-Temporary Mobile Subscriber Identity S-TMSI allocated by the network
  • the allocation process of the S-TMSI may be: when the first device is attached to the MME included in the network , the network terminal will allocate a temporary mobile user identity (the same concept as the following temporary identity) based on the identity of the first device (IMSI and/or IMEI information), and also establish a temporary mobile user identity with the first device.
  • the mapping relationship of the identity identifiers, then in subsequent air interface signaling, the network can uniquely identify the first device based on the carried temporary identity.
  • the air interface signaling does not respond or the response fails.
  • the air interface signaling is a network synchronization request
  • network verification fails.
  • the first device sends a network synchronization request carrying a temporary identity to the network, such as sending a tracking area update request carrying a temporary identity, such as sending a business service request carrying a temporary identity, and the network receives the request.
  • the temporary identity identifier S-TMSI carried in the network synchronization request can be obtained, and based on the temporary identity identifier S-TMSI, the identity verification for the first device and other network recovery verification processes (for example, after the identity verification, initiate a verification process for the first device) A paging process of a device) and then perform network recovery verification on the network synchronization request.
  • Step S305 Receive the verification result sent by the network terminal, and determine that the network state synchronization is successful based on the verification result.
  • the verification result is a post-verification result during the network recovery verification process performed by the network, including but not limited to verification success information and verification failure information.
  • FIG. 6 is a schematic diagram of an offline recovery scenario involved in the present application.
  • the network side if there is a network service on the network side that needs to interact with the first device (such as the following data scenario), if the network side needs to interact with the first device at a certain point in the time period from t3 to t2, then the network side needs to interact with the first device.
  • the S-TMSI paging process (that is, the paging process) for the first device will be initiated.
  • the network usually corresponds to the paging processing strategy of paging failure. For example, when there is no response to the paging, the relevant service data will be cached, and then the paging process will be re-initiated after a period of time, and the paging process will be re-initiated on the network.
  • the first device Before the call process, the first device will have the above-mentioned network recovery within the time t3.
  • the tracking area identifier of the cell that has relocated to the network exists in the tracking area identifier list before disconnection, and the first device will report to the
  • the network end sends a network synchronization request, and the network synchronization request carries the S-TMSI, so that the network end performs network recovery verification on the network synchronization request based on the S-TMSI; the network end receives the network synchronization request and obtains the carried S-TMSI, Based on the mapping relationship between the pre-stored S-TMSI temporary mobile user identity and the identity of the first device, it is determined whether the S-TMSI in the network synchronization request is correct.
  • the network can initiate the S-TMSI paging process for the first device again as shown in Figure 6.
  • the network A verification success message can be generated to the first device.
  • the first device can receive the verification success message sent by the network terminal to determine that the network state is synchronized successfully.
  • the key to network synchronization usually lies in whether the mapping relationship between the S-TMSI temporary mobile user identity and the identity identity of the first device stored on the network side is stored normally.
  • the network synchronization corresponding to the recovery verification will usually be successful, otherwise, it will fail.
  • FIG. 7 is a schematic diagram of another off-network recovery scenario involved in the present application.
  • S-TMSI of the network side for the first device is lost will be described with reference to FIG. 7 .
  • the abnormality of the network data causes the loss of the mapping relationship between the pre-stored S-TMSI temporary mobile subscriber identity and the identity of the first equipment, and the network is in the S-TMSI paging for the first equipment.
  • the process (that is, the paging process) will inevitably fail to paging due to lack of data.
  • the network usually corresponds to the paging processing strategy of the paging failure, such as caching the information about the first device when there is no response to the paging. Relevant service data, and then the subsequent S-TMSI paging process will not be re-initiated due to the loss of S-TMSI, and the first device will have the above-mentioned network recovery after t3 time.
  • the tracking area identifier of the cell exists in the tracking area identifier list before disconnection, and the first device will continue to send the network synchronization request carrying the temporary identifier to the network, so that the network can
  • the network synchronization request performs network recovery verification; the network end receives the network synchronization request to obtain the S-TMSI carried, and because the mapping relationship between the pre-stored S-TMSI temporary mobile user identity and the identity of the first device is abnormally stored, it cannot target the first device. If it is determined whether the S-TMSI in the network synchronization request is correct, the synchronization request will be rejected, and usually the network end will send the verification failure information generated therewith to the first device. When the first device receives the verification failure information sent by the network, it can be determined that the first temporary identity of the network is lost;
  • the first temporary identity is a temporary identity S-TMSI about the first device stored by the network, which is used for device identity verification in the air interface command.
  • the first device initiates a network identity registration process (ie, the re-registration process in FIG. 7 ) to the network, and after the network identity registration process is successful, the first device may determine that the network state synchronization is successful.
  • a network identity registration process ie, the re-registration process in FIG. 7
  • a network identity registration process may be: the first device initiates a network attach (Attach) process to the network, and in the network attach process, the first device will send an Attach Request message carrying an identity identifier (IMSI and/or IMEI information) to the network
  • the network device such as MME included in the terminal, the network terminal will allocate the temporary identity based on the identity of the first device (IMSI and/or IMEI information), and also establish a relationship between the temporary identity and the identity of the first device. mapping relationship, then the first device in the subsequent air interface signaling can perform based on the carried temporary identity identifier.
  • the first device has a calling service, then the first device generates a network service request carrying the temporary identity identifier.
  • the network service request is sent to the network end, and the network end can uniquely identify the first device based on the carried temporary identity identifier, and then perform the service service acceptance process.
  • the first device acquires the current tracking area identifier of the network when the first device goes offline and restores the network; if the tracking area identifier exists in the list of tracking area identifiers before disconnection, the first device A device can synchronize the network state to the network, thereby avoiding the time of network state synchronization caused by waiting for the network to perform paging when the tracking area identifier exists in the tracking area identifier list before offline in the related art.
  • the problem of high delay greatly reduces the synchronization delay of the network status and ensures the normal business services of subsequent devices.
  • the intelligent judgment of network state synchronization can be realized. It is initiated when network status synchronization is required, thereby avoiding signaling compliance and reducing the probability of signaling storms; and based on the corresponding data transmission status, corresponding network synchronization requests are generated.
  • the network synchronization methods are diversified and improve the network synchronization. Intelligence and convenience, in the entire network status update process, the network side follows the existing 3GPP protocol framework, and adopts the general tracking area update request process or business service request process to complete, which improves the universality of network status update and Universality.
  • FIG. 8 is a schematic flowchart of another embodiment of a network state synchronization method proposed by the present application. specific:
  • Step S401 when the first device goes offline and restores the network, obtain the current tracking area identifier of the network;
  • step S101 For details, refer to step S101, which will not be repeated here.
  • Step S402 If the tracking area identifier exists in the tracking area identifier list before going offline, obtain synchronization judgment information, and determine to perform network state synchronization to the network based on the synchronization judgment information.
  • the first device may pre-determine the first temporary identity of the first device on the network when determining to perform network state synchronization to the network based on the synchronization decision information. a storage state.
  • the first temporary identity is the temporary identity stored by the network for the first device, and the network will perform the identification based on the identity (IMSI and/or IMEI information) of the first device before the first device is offline.
  • the assignment of the temporary ID also establishes a mapping relationship between the temporary ID and the ID of the first device, and the network can uniquely identify the first device based on the carried temporary ID in subsequent air interface signaling.
  • the first storage state is whether the first temporary identity identifier on the network is well-preserved, and the first storage state may be a storage loss state, that is, the first temporary identity is lost due to abnormal data sent by the network; the first storage state may be: Store the normal state.
  • the first stored state is of high importance in the network state synchronization process, and determines whether the network state synchronization is successful.
  • Step S403 Acquire the second storage state of at least one second device; the second storage state is the storage state of the second temporary identity corresponding to the second device on the network terminal; the second device and the The first device is under the same local area network;
  • the first device when the first device is in an offline state, the first device cannot interact with the network, that is, the first storage state of the first temporary identity identifier on the network cannot be determined. Whether the first storage state is a normal storage state will be directly related to the verification result of subsequent initiation of a network synchronization request carrying a temporary identity identifier.
  • the first device may determine the first storage state of the local end by referring to the storage state of the temporary identities of other devices available for reference at the network end.
  • the first device can refer to the judgment of the first storage based on the second storage states of other referenced second devices in the same environment. state.
  • the holder of the first device and multiple reference devices may move to areas with poor signal quality, such as elevators, underground garages, and some specific shielded places, due to insufficient coverage, occlusion or artificial shielding. , which will lead to poor or even no signal of the mobile phone; at this time, the first device and each reference device can be offline at the same time, and because each holder moves in a similar environment, the first device and the reference device are usually disconnected from the network.
  • the first device and the reference device are in the same environment during the whole process, and the definition of the same environment can be based on the position difference between the first device and the reference device (distance difference value, angle difference value ) to determine whether the reference device can be included in the reference, and the position difference degree satisfies certain constraints, such as a preset difference threshold. If it is less than the difference threshold, it is considered that the constraint condition is satisfied, and the reference device is considered to be the second device that meets the reference requirement.
  • the Include reference to a certain second device that has completed network synchronization and obtain the second storage state of at least one second device, where the second storage state is the second temporary identity corresponding to the second device on the network side.
  • the storage state based on the second storage state, assists in judging the storage state of the first identity paired with the local end of the first device.
  • the second storage state and the second temporary identity identifier are similar to the above-mentioned "first identity storage state and the first temporary identity identifier", and only the main body of the device is different, which will not be repeated here.
  • a network storage state sharing strategy can be pre-agreed between the first device and each second device, and after any device completes the synchronization of the network state after being disconnected from the network and restored, the temporary identity of the local end is stored in the storage state of the network end. sharing; wherein, the network storage state sharing strategy may be based on the first device and each second device joining the same local area network in advance, wherein the local area network is different from the communication network provided by the network end, and is independent of each other and does not affect each other, the local area network It can be a local area network based on Bluetooth communication, a local area network based on Zifeng communication, a local area network based on zigbee communication, or a local area network based on WIFI communication.
  • FIG. 9 is a schematic diagram of a scenario of device status synchronization in a local area network involved in the present application.
  • the second device is electronic device 2 as an example, the holders of the first device and the second device have no signal because they move to areas with poor signal quality, such as elevators and underground garages; at this time, the first device and the second device can be simultaneously In an offline state, the second device initiates synchronization of the network state involved in this application with the first device, so that the second storage state is pre-determined according to the network state synchronization process.
  • the second device can synchronize the second storage state to For the first device under the same local area network, the first device can obtain the second storage state synchronized by the second device at this time.
  • the first device can acquire the second storage states of the multiple second devices.
  • the above synchronization may be that the second device transmits to each device under the local area network one by one by means of point-to-point transmission, or the second device may synchronize the second storage state by means of information broadcasting.
  • the second device re-initiates the network identity registration process during the network state synchronization process.
  • the first device takes the second storage state as a reference, and determines that the first storage state of the first temporary identity identifier of the first device on the network end is the storage loss state.
  • S405 If the second storage state is a normal storage state, determine that the storage state of the first temporary identity identifier of the first device on the network terminal is a normal storage state.
  • the first device acquires the second storage state
  • the second storage state is the normal storage state
  • usually the second device does not initiate the network identity registration process during the network state synchronization process, and the network does not lose the temporary storage status of the second device.
  • ID at this time, the first device uses the second storage state as a reference, and determines that the first storage state of the first temporary ID for the first device on the network end is the storage normal state.
  • S406 Perform network state synchronization to the network terminal based on the first storage state.
  • the first device can directly initiate a network identity registration process to the network end without generating a network state synchronization request for sending, because even if the network end is sent, the high The probability request is rejected, therefore, the network identity registration process can be directly initiated to the network terminal, saving signaling flow time, and improving the efficiency of network state synchronization.
  • the network identity registration process After the network identity registration process is successful, it is determined that the network state synchronization is successful;
  • the first device normally sends a network synchronization request to the network end, so that the network end performs network recovery verification on the first device; it is determined that the network state synchronization is successful.
  • the network synchronization request carries the first temporary identity identifier.
  • S407 Synchronize the first storage state of the first temporary identity with at least one third device, so that the third device can determine whether the third temporary identity of the third device is on the network side. a third storage state, and synchronizing the network state to the network terminal based on the third storage state;
  • the third device and the first device are under the same local area network.
  • the first device may synchronize the first storage state of the first temporary identity on the network side to the local area network, so that the third device that has not yet synchronized the network state uses the first storage state
  • the third device determines the third storage state of the third temporary identity identifier of the third device on the network end, and synchronizes the network state to the network end based on the third storage state.
  • the third device judges the third storage state of the third temporary identity identifier of the third device on the network side, and synchronizes the network state to the network side based on the third storage state.
  • the first device acquires the current tracking area identifier of the network when the first device goes offline and restores the network; if the tracking area identifier exists in the list of tracking area identifiers before disconnection, the first device A device can synchronize the network state to the network, thereby avoiding the time of network state synchronization caused by waiting for the network to perform paging when the tracking area identifier exists in the tracking area identifier list before offline in the related art.
  • the problem of high delay greatly reduces the synchronization delay of the network status and ensures the normal business services of subsequent devices.
  • the intelligent judgment of network state synchronization can be realized. It is initiated when network status synchronization is required, thereby avoiding signaling compliance and reducing the probability of signaling storms; and based on the corresponding data transmission status, corresponding network synchronization requests are generated.
  • the network synchronization methods are diversified and improve the network synchronization. Intelligence and convenience, in the entire network status update process, the network side follows the existing 3GPP protocol framework, and adopts the general tracking area update request process or business service request process to complete, which improves the universality of network status update and Universality.
  • FIG. 10 is a schematic structural diagram of a network state synchronization system according to an embodiment of the present application.
  • the network state synchronization system includes a network terminal 200 and a first device 100 .
  • the network terminal 20 is used to provide a communication network corresponding to the wireless communication system, and the network terminal 20 includes but is not limited to a core network (Core Network, CN) and an access network (Radio Access Network, RAN) corresponding to the network equipment composition.
  • the core network is responsible for non-access stratum affairs, such as the location update of the first device 100 such as the terminal, etc., and is the anchor point of the user plane.
  • the access network includes base stations, or base stations and base station controllers.
  • the access network is responsible for access layer affairs (such as radio resource management, etc.), and there may be physical or logical connections between base stations according to actual conditions.
  • One or more than one core network node in the core network is connected.
  • the first device 100 refers to various devices that can communicate with a wireless communication network, such as a mobile phone, a notebook computer, etc., and the terminal accesses the core network through the base station.
  • the MTC service is the machine type communication service. No human participation is required in the MTC business, and all communications are completed autonomously by machines.
  • an MTC terminal obtains data through sensing devices such as sensors, and the data is managed by a mobile operator or a specific server of a dedicated MTC operator, and can be viewed by MTC users or MTC managers. Then, the MTC terminal reports the data to the mobile communication network, and accesses the public data network through the mobile communication network, such as logistics monitoring, safety monitoring, remote medical detection, remote meter reading and other applications.
  • the mobility management entity (MME, Mobility Management Entity) obtains the subscription information of the first device 100 from the home user server and saves it locally .
  • the MME is an entity in the core network for managing terminal control signaling.
  • the first device 100 is usually assigned to a tracking area by the network. When the first device 100 moves out of the tracking area, it needs to send a Tracking Area Update (TAU) request to the network side, so that the network side can modify the tracking area locally. Tracking area location information for a device 100 .
  • TAU Tracking Area Update
  • the first device 100 When the first device 100 does not move and is in an idle state, the first device 100 usually needs to perform a periodic TAU process, that is, in a cycle, the first device 100 sends a TAU request to the network, and the network can move
  • a TAU acceptance message is returned to the first device 100, and the next cycle is entered.
  • the first device 100 moves out of the tracking area, that is, the tracking area identifier corresponding to the current cell on the network of the first device 100 is no longer in the tracking area identifier list delivered by the network.
  • the embodiments involved in this application mainly involve: The network status update method when the tracking area identifier corresponding to the current resident network cell of the first device 100 is added to the tracking area identifier list delivered by the network.
  • the first device, the second device, and the third device may be electronic devices with a network state synchronization function
  • the electronic devices include but are not limited to: wearable devices, handheld devices, personal computers, and tablets Computers, in-vehicle devices, smartphones, computing devices, or other processing devices connected to wireless modems, etc.
  • the first device can be called by different names in different networks, for example: user equipment, access first device, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote first device, mobile device, user A first device, a first device, a wireless communication device, a user agent or user equipment, a cellular phone, a cordless phone, a personal digital assistant (PDA), an electronic device in a 5G network or a future evolution network, and the like.
  • PDA personal digital assistant
  • network state synchronization system embodiments provided by the above embodiments and the network state synchronization methods in some embodiments belong to the same concept, and the implementation process of the embodiments is detailed in the method embodiments, which will not be repeated here.
  • FIG. 11 shows a schematic structural diagram of a network state synchronization apparatus provided by an exemplary embodiment of the present application.
  • the device for synchronizing network status can be implemented as a whole or a part of the device through software, hardware or a combination of the two.
  • the device 1 includes an identification acquisition module 11 and a state synchronization module 12 .
  • the identification acquisition module 11 is used to acquire the current tracking area identification of the network when the first device is disconnected from the network and the network is restored; the state synchronization module 12 is used for tracking if the tracking area identification exists before being disconnected from the network. In the list of zone identifiers, the network status is synchronized to the network side.
  • the state synchronization module 12 is specifically configured to: acquire synchronization decision information, and perform network state synchronization to the network based on the synchronization decision information.
  • the state synchronization module 12 includes: a first synchronization unit 121, configured to perform network state synchronization to the network end if the off-network duration is greater than a preset duration threshold, the said The synchronization decision information is the off-network duration; the second synchronization unit 122 is used for the synchronization decision information to be the network interaction information before the first device is disconnected from the network.
  • the network terminal performs network state synchronization; the network interaction information includes at least one of network interaction frequency, network interaction data volume, and network interaction scenarios.
  • the state synchronization module 12 is specifically configured to: send a network synchronization request to the network, so that the network performs network recovery verification on the network synchronization request; receive the verification sent by the network As a result, it is determined that the network state synchronization is successful based on the verification result.
  • the state synchronization module 12 is specifically configured to: acquire a data transmission state, generate a network synchronization request based on the data transmission state; and send a network synchronization request to the network end.
  • the state synchronization module 12 is specifically configured to: if the data transmission state is the calling service state, generate a service service request; if the data transmission state is the called service state or the idle service state, then Generate a tracking area update request.
  • the device 1 is specifically configured to: send a network synchronization request carrying a temporary identity to the network, so that the network performs network recovery verification on the network synchronization request based on the temporary identity. .
  • the device 1 is specifically configured to: receive the verification failure information sent by the network end, and determine that the first temporary identity of the network end is lost; initiate a network identity registration process to the network end, and in the After the network identity registration process is successful, it is determined that the network state synchronization is successful.
  • the apparatus 1 is specifically configured to: receive the verification success information sent by the network terminal, and determine that the network state synchronization is successful.
  • the device 1 is specifically configured to: if the synchronization judgment information satisfies the network synchronization condition, perform network synchronization waiting, and monitor the network service instruction for the network calling service;
  • the apparatus 1 is specifically configured to: start a monitoring timer for the network calling service, and monitor the network service instruction for the network calling service based on the monitoring timer.
  • the apparatus 1 is specifically configured to: determine the first storage state of the first temporary identity identifier of the first device on the network end; perform network state information to the network end based on the first storage state. Synchronize.
  • the apparatus 1 is specifically configured to: obtain a second storage state of at least one second device; the second storage state is a second temporary identity corresponding to the second device on the network end. storage state; the second device and the first device are in the same local area network; if the second storage state is a storage loss state, the first temporary identity identifier of the first device on the network end The storage state is the storage loss state; if the second storage state is the storage normal state, it is determined that the storage state of the first temporary identity for the first device on the network terminal is the storage normal state.
  • the apparatus 1 is specifically configured to: synchronize the first storage state of the first temporary identity with at least one third device, so that the third device determines that the the third storage state of the third temporary identity identifier of the third device, and perform network state synchronization to the network terminal based on the third storage state;
  • the third device and the first device are under the same local area network.
  • the device 1 is specifically configured to: if the first storage state is a storage loss state, initiate a network identity registration process to the network terminal, and determine the network state after the network identity registration process is successful. The synchronization is successful; if the first storage state is a normal storage state, a network synchronization request is sent to the network end, so that the network end performs network recovery verification on the first device; it is determined that the network state synchronization is successful.
  • the network state synchronization apparatus when the network state synchronization apparatus provided in the above embodiments executes the network state synchronization method, only the division of the above functional modules is used as an example for illustration. In practical applications, the above functions may be allocated to different functions as required. Module completion means dividing the internal structure of the device into different functional modules to complete all or part of the functions described above.
  • the apparatus for synchronizing network status provided by the above embodiments and the method embodiments for synchronizing network status belong to the same concept, and the embodiment and implementation process thereof are detailed in the method embodiments, which will not be repeated here.
  • An embodiment of the present application further provides a computer storage medium, where the computer storage medium can store a plurality of instructions, and the instructions are suitable for being loaded by a processor and executing the above-described embodiments shown in FIG. 1 to FIG. 10 .
  • the network state synchronization method for the specific execution process, reference may be made to the specific description of the embodiments shown in FIG. 1 to FIG. 10 , which will not be repeated here.
  • the present application also provides a computer program product, where the computer program product stores at least one instruction, and the at least one instruction is loaded by the processor and executes the network state of the embodiments shown in the foregoing FIG. 1 to FIG. 10 .
  • the computer program product stores at least one instruction
  • the at least one instruction is loaded by the processor and executes the network state of the embodiments shown in the foregoing FIG. 1 to FIG. 10 .
  • the synchronization method for the specific execution process, reference may be made to the specific description of the embodiments shown in FIG. 1 to FIG. 10 , which will not be repeated here.
  • FIG. 13 shows a structural block diagram of an electronic device provided by an exemplary embodiment of the present application.
  • An electronic device in this application may include one or more of the following components: a processor 110 , a memory 120 , an input device 130 , an output device 140 and a bus 150 .
  • the processor 110 , the memory 120 , the input device 130 and the output device 140 may be connected through a bus 150 .
  • the processor 110 may include one or more processing cores.
  • the processor 110 uses various interfaces and lines to connect various parts in the entire electronic device, and executes the electronic device by running or executing the instructions, programs, code sets or instruction sets stored in the memory 120, and calling the data stored in the memory 120.
  • Various functions of the device 100 and processing data may adopt at least one of digital signal processing (digital signal processing, DSP), field-programmable gate array (field-programmable gate array, FPGA), and programmable logic array (programmable logic Array, PLA).
  • DSP digital signal processing
  • FPGA field-programmable gate array
  • PLA programmable logic array
  • a hardware form is implemented.
  • the processor 110 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a modem, and the like.
  • the CPU mainly handles the operating system, user interface and application programs, etc.; the GPU is used for rendering and drawing of the display content; the modem is used to handle wireless communication. It can be understood that, the above-mentioned modem may also not be integrated into the processor 110, and is implemented by a communication chip alone.
  • the memory 120 may include random access memory (RAM), or may include read-only memory (ROM).
  • the memory 120 includes a non-transitory computer-readable storage medium.
  • Memory 120 may be used to store instructions, programs, codes, sets of codes, or sets of instructions.
  • the memory 120 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playback function, an image playback function, etc.) , instructions for implementing the following method embodiments, etc.
  • the operating system can be an Android (Android) system, including a system based on the deep development of the Android system, an IOS system developed by Apple, including a system based on the deep development of the IOS system or other systems.
  • the storage data area can also store data created by the electronic device in use, such as a phone book, audio and video data, chat record data, and the like.
  • the memory 120 can be divided into an operating system space and a user space, the operating system runs in the operating system space, and the native and third-party applications run in the user space.
  • the operating system allocates corresponding system resources to different third-party applications.
  • different application scenarios in the same third-party application also have different requirements for system resources.
  • the third-party application has higher requirements on the disk read speed; in the animation rendering scenario, the first Third-party applications have higher requirements on GPU performance.
  • the operating system and the third-party application are independent of each other, and the operating system often cannot perceive the current application scenario of the third-party application in time, so that the operating system cannot perform targeted system resource adaptation according to the specific application scenario of the third-party application.
  • the memory 120 may store the Linux kernel layer 320, the system runtime library layer 340, the application framework layer 360 and the application layer 380, Among them, the Linux kernel layer 320, the system runtime layer 340 and the application framework layer 360 belong to the operating system space, and the application layer 380 belongs to the user space.
  • the Linux kernel layer 320 provides underlying drivers for various hardwares of electronic devices, such as display drivers, audio drivers, camera drivers, Bluetooth drivers, Wi-Fi drivers, power management and the like.
  • the system runtime layer 340 provides main feature support for the Android system through some C/C++ libraries.
  • the SQLite library provides database support
  • the OpenGL/ES library provides 3D drawing support
  • the Webkit library provides browser kernel support.
  • An Android runtime library (Android runtime) is also provided in the system runtime library layer 340, which mainly provides some core libraries, which can allow developers to use the Java language to write Android applications.
  • the application framework layer 360 provides various APIs that may be used when building applications. Developers can also build their own applications by using these APIs, such as activity management, window management, view management, notification management, content provider, Package management, call management, resource management, location management.
  • the IOS system includes: a core operating system layer 420 (Core OS layer), a core service layer 440 (Core Services layer), a media layer 460 (Media layer), touchable layer 480 (Cocoa Touch Layer).
  • the core operating system layer 420 includes the operating system kernel, drivers, and low-level program frameworks, which provide functions closer to hardware for use by the program frameworks located in the core service layer 440 .
  • the core service layer 440 provides system services and/or program frameworks required by application programs, such as a foundation framework, an account framework, an advertisement framework, a data storage framework, a network connection framework, a geographic location framework, a motion framework, and the like.
  • the media layer 460 provides audiovisual interfaces for applications, such as graphics and image related interfaces, audio technology related interfaces, video technology related interfaces, and audio and video transmission technology wireless playback (AirPlay) interfaces.
  • the touchable layer 480 provides various common interface-related frameworks for application development, and the touchable layer 480 is responsible for the user's touch interaction operation on the electronic device. Such as local notification service, remote push service, advertising framework, game tool framework, message user interface interface (User Interface, UI) framework, user interface UIKit framework, map framework and so on.
  • the frameworks related to most applications include but are not limited to: the basic framework in the core service layer 440 and the UIKit framework in the touchable layer 480 .
  • the basic framework provides many basic object classes and data types, and provides the most basic system services for all applications, regardless of UI.
  • the classes provided by the UIKit framework are the basic UI class libraries for creating touch-based user interfaces.
  • iOS applications can provide UI based on the UIKit framework, so it provides the application's infrastructure for building user interfaces, drawing , handling and user interaction events, responding to gestures, and more.
  • the method and principle of implementing data communication between a third-party application and an operating system in the IOS system may refer to the Android system, which will not be repeated in this application.
  • the input device 130 is used for receiving input instructions or data, and the input device 130 includes but is not limited to a keyboard, a mouse, a camera, a microphone or a touch device.
  • the output device 140 is used for outputting instructions or data, and the output device 140 includes, but is not limited to, a display device, a speaker, and the like.
  • the input device 130 and the output device 140 may be co-located, and the input device 130 and the output device 140 are a touch display screen, the touch display screen is used to receive any suitable objects such as a user's finger, a touch pen, etc. Nearby touch actions, as well as displaying the user interface of each application.
  • the touch display is usually provided on the front panel of the electronic device.
  • the touch screen can be designed as a full screen, a curved screen or a special-shaped screen.
  • the touch display screen can also be designed to be a combination of a full screen and a curved screen, or a combination of a special-shaped screen and a curved screen, which is not limited in the embodiments of the present application.
  • the structure of the electronic device shown in the above drawings does not constitute a limitation to the electronic device, and the electronic device may include more or less components than those shown in the drawings, or a combination of certain components may be included. some components, or a different arrangement of components.
  • the electronic device also includes components such as a radio frequency circuit, an input unit, a sensor, an audio circuit, a wireless fidelity (WiFi) module, a power supply, and a Bluetooth module, which will not be repeated here.
  • WiFi wireless fidelity
  • the execution body of each step may be the electronic device described above.
  • the execution subject of each step is an operating system of the electronic device.
  • the operating system may be an Android system, an IOS system, or other operating systems, which are not limited in this embodiment of the present application.
  • the electronic device may also have a display device installed thereon, and the display device may be various devices that can realize a display function, such as a cathode ray tube display (Cathode ray tube display, CR for short), a light emitting diode display (light emitting diode display).
  • a cathode ray tube display Cathode ray tube display, CR for short
  • a light emitting diode display light emitting diode display
  • - emitting diode display referred to as LED
  • electronic ink screen liquid crystal display (liquid crystal display, referred to as LCD), plasma display panel (plasma display panel, referred to as PDP) and so on.
  • LCD liquid crystal display
  • PDP plasma display panel
  • the user can use the display device on the electronic device 101 to view the displayed text, image, video and other information.
  • the electronic device may be a smart phone, a tablet computer, a gaming device, an AR (Augmented Reality) device, a car, a data storage device, an audio playback device, a video playback device, a notebook, a desktop computing device, a wearable device such as an electronic device. Watches, electronic glasses, electronic helmets, electronic bracelets, electronic necklaces, electronic clothing and other equipment.
  • the processor 110 can be used to call the network state synchronization application program stored in the memory 120, and specifically perform the following operations:
  • tracking area identifier exists in the tracking area identifier list before disconnection, perform network state synchronization to the network end.
  • the processor 110 when performing the network state synchronization to the network, specifically performs the following operations: acquiring synchronization decision information, and synchronizing the network state to the network based on the synchronization decision information.
  • the processor 110 when the processor 110 performs the network state synchronization to the network based on the synchronization decision information, the processor 110 specifically performs the following operations: the synchronization decision information is the off-network duration, if the off-network If the duration is greater than the preset duration threshold, the network state is synchronized to the network; or, the synchronization judgment information is the network interaction information before the first device goes offline, and if the network interaction information matches the reference interaction information, The network state synchronization is performed to the network end; the network interaction information includes at least one of network interaction frequency, network interaction data volume, and network interaction scenarios.
  • the processor 110 when performing the network state synchronization to the network, specifically performs the following operations: sending a network synchronization request to the network, so that the network synchronizes the network Request to perform network recovery verification; receive the verification result sent by the network terminal, and determine that the network state synchronization is successful based on the verification result.
  • the processor 110 specifically performs the following operations when performing the sending of the network synchronization request to the network: acquiring a data transmission state, and generating a network synchronization request based on the data transmission state; The network side sends a network synchronization request.
  • the processor 110 specifically performs the following operations when performing the acquiring the data transmission state and generating the network synchronization request based on the data transmission state: if the data transmission state is the calling service state, then A service service request is generated; if the data transmission state is the called service state or the idle service state, a tracking area update request is generated.
  • the processor 110 when the processor 110 executes the sending a network synchronization request to the network, so that the network performs network recovery verification on the network synchronization request, the processor 110 specifically performs the following operations: sending a network synchronization request to the network The network terminal sends a network synchronization request carrying a temporary identity identifier, so that the network terminal performs network recovery verification on the network synchronization request based on the temporary identity identifier.
  • the processor 110 specifically performs the following operations when performing the receiving the verification result sent by the network terminal, and determining that the network state synchronization is successful based on the verification result: receiving the verification result sent by the network terminal Failure information, it is determined that the first temporary identity of the network end is lost; a network identity registration process is initiated to the network end, and after the network identity registration process is successful, it is determined that the network state synchronization is successful.
  • the processor 110 specifically performs the following operations when it is determined that the network state synchronization is successful based on the verification result sent by the network receiving the verification result:
  • the verification success information sent by the network terminal is received, and it is determined that the synchronization of the network state is successful.
  • the processor 110 when the processor 110 performs the network state synchronization to the network based on the synchronization decision information, the processor 110 specifically performs the following operations: if the synchronization decision information satisfies a network synchronization condition, perform network synchronization Wait, and monitor the network service instruction for the network calling service; determine that the network service instruction is monitored, and perform network state synchronization to the network end.
  • the processor 110 when the processor 110 executes the monitoring network request instruction for the network service, the processor 110 specifically performs the following operations: starting a monitoring timer for the network calling service, and monitoring the monitoring target based on the monitoring timer. Describe the network service command of the network calling service. In one embodiment, when the processor 110 performs the network state synchronization to the network end, the processor 110 specifically performs the following operations: judging the first storage state of the first temporary identity identifier of the first device on the network end ; Perform network state synchronization to the network terminal based on the first storage state.
  • the processor 110 specifically performs the following operations when performing the determining of the storage state of the first temporary identity of the first device on the network side: acquiring the second data of at least one second device. storage state; the second storage state is the storage state of the second temporary identity identifier corresponding to the second device on the network end; the second device and the first device are in the same local area network; if the The second storage state is the storage loss state, then the first storage state on the network for the first temporary identity of the first device is the storage loss state; if the second storage state is the storage normal state, then It is determined that the storage state of the first temporary identity for the first device on the network end is a normal storage state.
  • processor 110 executes the method for updating the network state, the following steps are further performed:
  • the third device and the first device are under the same local area network.
  • the process when the processor 110 performs the network state synchronization to the network based on the first storage state, the process includes: if the first storage state is a storage loss state, sending a The network end initiates a network identity registration process, and after the network identity registration process is successful, it is determined that the network state synchronization is successful; if the first storage state is a normal storage state, a network synchronization request is sent to the network end, so that all The network terminal performs network recovery verification on the first device; it is determined that the network state synchronization is successful.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Debugging And Monitoring (AREA)

Abstract

本申请实施例公开了一种网络状态同步方法、装置、存储介质及电子设备，其中，方法包括：在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；若所述跟踪区标识存在于脱网前的跟踪区标识列表中，向网络端进行网络状态同步。采用本申请实施例，可以降低网络状态同步的时延。

Description

网络状态同步方法、装置、存储介质及电子设备
本申请要求了2021年01月22日提交的、申请号为2021100900823、发明名称为“网络状态同步方法、装置、存储介质及电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种网络状态同步方法、装置、存储介质及电子设备。
背景技术
随着通信技术的发展，电子设备也随之快速普及。通常，当电子设备(如终端)的使用者所持电子设备进行移动，电子设备会存在从信号质量好的区域移动到信号质量不佳的区域，从而导致脱网，当电子设备重新回到信号质量好的区域，又会恢复网络。
在上述电子设备脱网并恢复网络的过程中，通常为了保障后续业务服务的正常进行，会涉及到与网络侧进行网络状态同步，如通知网络端电子设备当前所处的驻网小区，又如通知网络端电子设备当前网络恢复。
发明内容
本申请实施例提供了一种网络状态同步方法、装置、存储介质及电子设备，可以为业务线程分配到合适的处理器集群。本申请实施例的技术方案如下：
第一方面，本申请实施例提供了一种网络状态同步方法，所述方法包括：
在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；
若所述跟踪区标识存在于脱网前的跟踪区标识列表中，向网络端进行网络状态同步。
第二方面，本申请实施例提供了一种网络状态同步装置，所述装置包括：
标识获取模块，用于在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；
状态同步模块，用于若所述跟踪区标识存在于脱网前的跟踪区标识列表中，向网络端进行网络状态同步。
第三方面，本申请实施例提供一种计算机存储介质，所述计算机存储介质存储有多条指令，所述指令适于由处理器加载并执行上述的方法步骤。
第四方面，本申请实施例提供一种电子设备，可包括：处理器和存储器；其中，所述存储器存储有计算机程序，所述计算机程序适于由所述处理器加载并执行上述的方法步骤。
本申请一些实施例提供的技术方案带来的有益效果至少包括：
在本申请一个或多个实施例中，第一设备在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；若所述跟踪区标识存在于脱网前的跟踪区标识列表中，第一设备可以向网络端进行网络状态同步，从而避免在相关技术中，由于跟踪区标识存在于脱网前的跟踪区标识列表的情况下，等待网络端进行寻呼所造成的网络状态同步的时延较高的问题，大幅降低了网络状态的同步时延，保障了后续设备正常业务服务的进行，以及，确保了第一设备在脱网恢复后与网络状态同步的实时性。
附图说明
为了更清楚地说明本申请实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本申请实施例提供的一种网络状态同步方法的流程示意图；
图2是本申请实施例提供的网络状态同步方法涉及到的一种设备移动场景示意图；
图3是本申请实施例提供的网络状态同步方法涉及到的另一种设备移动场景示意图；
图4是本申请实施例提供的另一种网络状态同步方法的流程示意图；
图5是本申请实施例提供的另一种网络状态同步方法的流程示意图；
图6是本申请实施例提供的网络状态同步方法涉及到的一种脱网恢复的场景示意图；
图7是本申请实施例提供的网络状态同步方法涉及到的另一种脱网恢复的场景示意图；
图8是本申请实施例提供的另一种网络状态同步方法的流程示意图；
图9是本申请实施例提供网络状态同步方法涉及到的一种局域网内设备状态同步的场景示意图；
图10是本申请实施例提供的一种网络状态同步的场景架构示意图；
图11是本申请实施例提供的一种网络状态同步装置的结构示意图；
图12是本申请实施例提供的一种状态同步模块的结构示意图；
图13是本申请实施例提供的一种电子设备的结构示意图；
图14是本申请实施例提供的操作***和用户空间的结构示意图；
图15是图13中安卓操作***的架构图；
图16是图13中IOS操作***的架构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
在本申请的描述中，需要理解的是，术语“第一”、“第二”等仅用于描述目的，而不能理解为指示或暗示相对重要性。在本申请的描述中，需要说明的是，除非另有明确的规定和限定，“包括”和“具有”以及它们任何变形，意图在于覆盖不排他的包含。例如包含了一系列步骤或单元的过程、方法、***、产品或设备没有限定于已列出的步骤或单元，而是可选地还包括没有列出的步骤或单元，或可选地还包括对于这些过程、方法、产品或设备固有的其他步骤或单元。对于本领域的普通技术人员而言，可以具体情况理解上述术语在本申请中的具体含义。此外，在本申请的描述中，除非另有说明，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。字符“/”一般表示前后关联对象是一种“或”的关系。
本说明书提供一种网络状态同步方法，应用于第一设备，所述方法包括：
在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；
若所述跟踪区标识存在于脱网前的跟踪区标识列表中，向网络端进行网络状态同步。
在一种实施方式中，所述向网络端进行网络状态同步，包括：
获取同步判决信息，基于所述同步判决信息向网络端进行网络状态同步。
在一种实施方式中，所述基于所述同步判决信息向网络端进行网络状态同步，包括：
所述同步判决信息为脱网时长，若所述脱网时长大于预设时长阈值，则向网络端进行网络状态同步；或，
所述同步判决信息为所述第一设备脱网前的网络交互信息，若所述网络交互信息与参考交互信息相匹配，则向网络端进行网络状态同步；所述网络交互信息包括网络交互频率、网络交互数据量、网络交互场景中的至少一种。
在一种实施方式中，所述向网络端进行网络状态同步，包括：
向所述网络端发送网络同步请求，以使所述网络端对所述网络同步请求进行网络恢复验证；
接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功。
在一种实施方式中，所述向所述网络端发送网络同步请求，包括：
获取数据传输状态，基于所述数据传输状态生成网络同步请求；
向所述网络端发送网络同步请求。
在一种实施方式中，所述获取数据传输状态，基于所述数据传输状态生成网络同步请求，包括：
若所述数据传输状态为主叫业务状态，则生成业务服务请求；
若所述数据传输状态为被叫业务状态或空闲业务状态，则生成跟踪区更新请求。
在一种实施方式中，所述向所述网络端发送网络同步请求，以使所述网络端对所述网络同步请求进行网络恢复验证，包括：
向所述网络端发送携带临时身份标识的网络同步请求，以使所述网络端基于所述临时身份标识对所述网络同步请求进行网络恢复验证。
在一种实施方式中，所述接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功，包括：
接收所述网络端发送的验证失败信息，确定所述网络端的第一临时身份标识丢失；
向所述网络端发起网络身份注册流程，在所述网络身份注册流程成功后，确定网络状态同步成功。
在一种实施方式中，所述接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功，包括：
接收所述网络端发送的验证成功信息，确定网络状态同步成功。
在一种实施方式中，所述基于所述同步判决信息向网络端进行网络状态同步，包括：
若所述同步判决信息满足网络同步条件，则进行网络同步等待，并监测针对网络主叫业务的网络业务指令；
确定监测到所述网络业务指令，向网络端进行网络状态同步。
在一种实施方式中，所述监测针对网络业务的网络请求指令，包括：
开启针对网络主叫业务的监测定时器，基于所述监测定时器监测针对所述网络主叫业务的网络业务指令。
在一种实施方式中，所述向网络端进行网络状态同步，包括：
判断网络端上针对所述第一设备的第一临时身份标识的第一存储状态；
基于所述第一存储状态向所述网络端进行网络状态同步。
在一种实施方式中，所述判断网络端上针对所述第一设备的第一临时身份标识的存储状态，包括：
获取至少一个第二设备的第二存储状态；所述第二存储状态为所述网络端上所述第二设备对应的第二临时身份标识的存储状态；所述第二设备与所述第一设备处于同一局域网下；
若所述第二存储状态为存储丢失状态，则网络端上针对所述第一设备的第一临时身份标识的第一存储状态为所述存储丢失状态；
若所述第二存储状态为存储正常状态，则确定所述网络端上针对所述第一设备的第一临时身份标识的存储状态为存储正常状态。
在一种实施方式中，所述方法还包括：
向至少一个第三设备同步所述第一临时身份标识的所述第一存储状态，以使所述第三设备判断所述网络端上针对所述第三设备的第三临时身份标识的第三存储状态，并基于所述第三存储状态向所述网络端进行网络状态同步；
其中，所述第三设备与所述第一设备处于同一局域网下。
在一种实施方式中，所述基于所述第一存储状态向所述网络端进行网络状态同步，包括：
若所述第一存储状态为存储丢失状态，则向所述网络端发起网络身份注册流程，在所述网络身份注册流程成功后，确定网络状态同步成功；
若所述第一存储状态为存储正常状态，则向所述网络端发送网络同步请求，以使所述网络端对所述第一设备进行网络恢复验证；确定网络状态同步成功。
下面结合具体的实施例对本申请进行详细说明。
在一个实施例中，如图1所示，特提出了一种网络状态同步方法，该方法可依赖于计算机程序实现，可运行于基于冯诺依曼体系的网络状态同步装置上。该计算机程序可集成在应用中，也可作为独立的工具类应用运行。
具体的，该网络状态同步方法包括：
步骤S101：在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；
在实际应用中，第一设备通常基于网络端对应的服务小区获取相应的通信网络服务。
服务小区是指当前为第一设备(如终端UE)提供网络数据服务的当前驻网小区，而网络服务小区也称第一设备当前可获得网络服务(如LTE网络服务、NR网络服务)的区域，是从网络端所提供的整个通信服务区(如LTE通信服务区、NR网络服务区)中划分出来的小区，小区内设有用于通信的基站(eNB)，负责与小区中的各电子设备建立无线连接，如第一设备，支持通信服务对应通信制式(如LTE通信制式)的电子设备在通信服务区内的任意小区里均能进行通信，如利用服务小区承载语音通话上/下行的业务数据。
在第一设备移动过程中，如用户所持第一设备进行移动，如图2所示，图2是本申请涉及到的一种设备移动场景示意图，第一设备在t1时间点处于图2中的A位置，属于A小区基站信号覆盖范围内，若第一设备从当前的服务小区移动到服务小区信号质量较弱的区域，在t2时间点处于图2中的B位置，在这个移动过程中，若第一设备从当前的A小区基站移动到服务小区信号质量较弱的区域，比如电梯、地下车库，以及一些特定的屏蔽场所等因为覆盖不足、遮挡或人为屏蔽，会导致网络信号质量较弱，则会由于信号质量不佳导致脱网的情况，当第一设备重新进入信号质量较好的服务小区覆盖区域(如另一服务小区B)时，第一设备可以重新驻网服务小区B，此时，第一设备即从脱网恢复到驻网，也即重新恢复网络，重新恢复网络之后，第一设备可以是处于正常服务空闲状态(即此时无上下行传输业务进行)。
具体的，在第一设备脱网并恢复网络过程中，第一设备可以获取到所属网络当前的服务小区的跟踪区标识，也即获取到当前驻网的服务小区所对应的跟踪区标识(TrackingAreaIdentity，TAI)。
示意性的，移动通信***中，例如长期演进(Long Term Evolution，LTE)***，处于空闲(IDLE)态的第一设备在移动过程中由于信号质量变化，需要进行小区重选时，会对当前服务小区及其它相邻服务小区的小区参考信号进行测量，并基于测量结果确定是否启动小区重选过程。在第一设备从其它相邻服务小区中确定目标服务小区，也就是完成小区重选完成之后，第一设备可以通过主通信接口接收目标服务小区的***消息块1(System InformationBlock1，SIB1)，从SIB1中获取目标服务小区的跟踪区标识(Tracking Area Identity，TAI)。
示意性的，第一设备也可以在处于当前服务小区信号覆盖范围之内时，服务小区对应的基站会广播同步帧，如同步唤醒包，第一设备从通过网络接口接收的当前服务小区的网络设备(如基站)广播发送的同步帧中得到当前服务小区所属TA的标识信息，进而根据当前服务小区所属TA的标识信息确定目标服务小区所属TA的TAI，也即跟踪区同步标识。
其中，跟踪区(Tracking Area)是网络通信***为UE(如第一设备)的位置管理设立的概念。当UE处于空闲状态时，跟踪区是用来进行寻呼和位置更新的区域，诸如核心网络等网络端能够知道UE(如第一设备)所在的跟踪区，同时当处于空闲状态的UE需要被寻呼(也即被网络端寻呼时)时，通常仅能在UE所注册的跟踪区的所有小区进行寻呼。其中，UE(如第一设备)所注册的跟踪区的所有小区通常以跟踪区标识的形式进行表征，且UE(如第一设备)所注册的跟踪区的所有小区对应的跟踪区标识属于网络端在UE(如第一设备)驻网前下发的跟踪区标识列表中。
另外，TA是小区级的配置，多个小区可以配置相同的TA，且一个小区只能属于一个TA。也即每个小区均对应一个唯一的跟踪区标识，且同一跟踪区标识下的小区可以是多个。
步骤S102：若所述跟踪区标识存在于脱网前的跟踪区标识列表中，向网络端进行网络状态同步。
在实际应用中，第一设备脱网前的初始驻网阶段会向网络端发起附着(attach)流程，在网络附着流程里，第一设备与网络端之间，如移动管理实体(MobilityManagementEntity，MME)，需要进行附着请求(AttachRequest)/附着确认(AttachAccept)/附着完成(AttachComplete)等交互流程，网络端在附着确认消息中，携带跟踪区标识(TrackingAreaIdentity，TAI)列表给第一设备。
具体的，跟踪区标识(TrackingAreaIdentity，TAI)列表由网络端在第一设备发起驻网时向其分配，跟踪区标识(TrackingAreaIdentity，TAI)列表中包含多个跟踪区标识，第一设备获取所述网络当前的跟踪区 标识，通常若跟踪区标识不存在于脱网前的跟踪区标识列表中时，网络端对应的各网络设备(如跟踪区标识列表中相应跟踪区标识对应的网络设备，如基站)都可以通过发送寻呼消息找到该UE。当跟踪区标识不存在于脱网前的跟踪区标识列表中，此时第一设备移动出了该跟踪区范围时，也就是第一设备在重选到的小区不在跟踪区范围时，为了当有下行数据业务时，还能寻呼到第一设备，通常第一设备会主动发起网络状态同步。
在相关技术中，若跟踪区标识存在于脱网前的跟踪区标识列表中，通常网络端所对应的各网络设备是可以在有相应数据业务产生时寻呼到第一设备，因此，第一设备在这种情况下，第一设备会在网络恢复之后，处于空闲状态，等待网络端的寻呼才能与网络端进行网络状态同步，在脱网的那段时间内，网络端可能会有些流程(如下行数据)要与第一设备进行交互，而第一设备因为当时在脱网状态，无法及时知道这些信息。因此等到第一设备恢复网络后，由于当前驻网小区的跟踪区标识存在于脱网前的跟踪区标识列表中，通常第一设备不会向网络端发起跟踪区更新而网络端此时就无法即时确定第一设备已经恢复网络。具体如下：如图3所示，图3是一种本申请涉及到的一种脱网网络端寻呼时序图；
处于空闲(IDLE)态的第一设备在移动过程中由于信号质量变化，第一设备此时从当前的服务小区A移动到服务小区信号质量较弱的区域，在这个移动过程中，信号质量较弱的区域比如电梯、地下车库，以及一些特定的屏蔽场所等因为覆盖不足、遮挡或人为屏蔽，会导致网络信号质量较弱，则会由于信号质量不佳导致脱网的情况，假设第一设备在t2时间点脱网处于当前驻网小区A处于无信号区域，在第一设备脱网阶段，第一设备会进行小区搜网，以及进行小区重选，这个过程中会对当前服务小区及其它相邻服务小区的小区参考信号进行测量，并基于测量结果确定启动小区重选过程。若第一设备重新进入信号质量较好的服务小区覆盖区域，第一设备从其它相邻服务小区中确定一个信号质量好的目标服务小区B，第一设备可以重新驻网服务小区B，此时重新驻网服务小区B也即t3时间点；
第一设备获取重新驻网服务小区B的跟踪区标识，若所述跟踪区标识存在于脱网前的跟踪区标识列表中通常会等待网络端进行寻呼。在上述脱网过程中，若网络端存在网络业务需要与第一设备进行交互(如下行数据场景)，如在t3到t2时间段的某个时间点需要与第一设备进行交互，则网络端会发起针对第一设备的寻呼过程(也即寻呼流程)，此时，由于第一设备当前网络信号质量不佳处于脱网无服务状态，因此，网络端发起的寻呼过程失败，在相关技术中网络端通常对应寻呼失败的寻呼处理策略，如在寻呼无响应时会缓存相关业务数据，然后相隔一段时间在重新发起寻呼过程，而在网络端重新发起寻呼过程之前，第一设备会存在上述在t3时间内网络恢复的情况，由于重新驻网的小区的跟踪区标识存在于脱网前的跟踪区标识列表，此时，第一设备又处于空闲状态，第一设备通常不会去发起网络同步，在这种场景下，第一设备仅能等候网络端重新发起寻呼过程，假设网络端重新发起寻呼过程在t5时间点，由于此时第一设备已经网络恢复，则此时重试寻呼成功，然后网络端才会传输业务数据；
此时，对应第一设备而言就会存在数据接收不及时的情况，延迟时间为(t5-t4)，同时寻呼响应时延也较高，网络状态同步也不及时。
在本申请中，第一设备可以执行本申请的网络状态同步方法，若所述跟踪区标识存在于脱网前的跟踪区标识列表中，第一设备可以在网络恢复之后向网络端进行网络状态同步。以使网络端可以基于第一设备发起的网络状态同步流程，以便网络端可以及时确定第一设备的网络状态，从而保证第一设备与网络端之间的业务信息准确实时同步。
一种网络同步方式可以是：第一设备与网络端预先预定网络同步策略，在第一设备网络恢复时，可以基于网络同步策略向网络端发送同步信息，如可以发送一个心跳包(心跳包中的数据为空)，以降低传输开销，从而便于网络端确定终端网络状态恢复。
一种网络同步方式：第一设备可以主动向网络端发业务服务请求，其中业务服务请求主要涉及主叫场景，也就是在第一设备存在上行业务数据的场景时，才会产生上行业务的业务服务请求，在本申请中，第一设备首选判决当前是否存在主叫业务，需要基于网络端发送上行业务数据，
若存在主叫业务，第一设备即随之生成业务服务请求，将业务服务请求发送至网络端，以便网络端可确定第一设备当前网络状态恢复；
若不存在主叫业务，此时第一设备通常处于空闲状态，此时，通常不会主动发起业务请求，为了实现网络状态的实时同步，第一设备可以进行主叫模拟，也即主动作为主叫方，模拟主叫场景，生成业务服务请求，将业务服务请求发送至网络端，以便网络端可确定第一设备当前网络状态恢复；其中主叫模拟，可以是按照预设的主叫模拟策略，向指定设备发起主叫场景，此时即可按照正常流程生成业务服务请求。进一步的，所述指定设备可以是预设的，也可以是基于第一设备的历史交互场景随机确定的一个电子设备。实际应用中，模拟主叫的目的在于产生业务服务请求，以符合网络端的业务流程，避免被网络端的业务响应策略所屏蔽。
一种网络同步方式：第一设备可以在当前场景下主动生成跟踪区更新请求，将跟踪区更新请求发送至网络端，以便网络端可确定第一设备当前网络状态恢复。
进一步的，第一设备在向网络端进行网络状态同步的过程中，网络端接收到第一设备主动发起的任一类型请求或信息之后，还需要进行网络恢复验证，也即重新发起针对第一设备的寻呼过程，基于寻呼过程的寻呼结果来确定寻呼成功，寻呼成功也即网络状态同步成功。
在本申请实施例中，第一设备在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；若所述跟踪区标识存在于脱网前的跟踪区标识列表中，第一设备可以向网络端进行网络状态同步，从而避免在相关技术中，由于跟踪区标识存在于脱网前的跟踪区标识列表的情况下，等待网络端进行寻呼所造成的网络状态同步的时延较高的问题，大幅降低了网络状态的同步时延，保障了后续设备正常业务服务的进行。以及，确保了第一设备在脱网恢复后与网络状态同步的实时性。
请参见图4，图4是本申请提出的一种网络状态同步方法的另一种实施例的流程示意图。具体的：
步骤S201：在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；
具体可参见步骤S101，此处不再赘述。
步骤S202：若所述跟踪区标识存在于脱网前的跟踪区标识列表中，则获取同步判决信息。
在本申请中，若所述跟踪区标识存在于脱网前的跟踪区标识列表中，可以不基于当前的实际应用环境，来衡量网络同步的需求，判决是否需要立即进行网络状态同步，在需要进行网络状态同步时才发起，从而避免信令符合，降低信令风暴的几率。
具体的，第一设备可以预先设置同步判决规则，基于同步判决规则来衡量且量化当前网络同步的迫切程度以及及时程度。不同的同步判决规则对应不同类型的同步判决信息，具体同步判决规则可基于实际应用环境确定。
可选的同步判决规则可以是对脱网时长进行判决，通过获取大量实际应用环境下的样本数据，来确定一时长阈值，基于时长阈值来衡量是否进行网络同步。
其中，第一设备可以由于信号质量不佳处于脱网状态时，开启脱网定时器，当第一设备脱网的时候，记录为时间t1；当第一设备恢复信号成功驻网时，记录为时间t2；t1和t2的间隔记录为Tsync，Tsync也即上述所需获取的脱网时长。
可选的，同步判决规则可以是对网络交互信息进行判决，所述网络交互信息包括网络交互频率、网络交互数据量、网络交互场景中的至少一种。
其中，网络交互频率为上行数据与下行数据的交互频率度量值，如以交互时间间隔参数作为网络交互频率。
网络交互数据量为一定时间段网络上行以及下行数据的总数据量。
网络交互场景为第一设备的交互应用场景，如即时通讯场景、电子商务场景、邮件收发场景、视频数据场景等等，网络交互场景通常与第一设备上后台应用服务相关联，可基于后台应用服务确定。
步骤S203：基于所述同步判决信息向网络端进行网络状态同步。
在一种可行的实施方式中：所述同步判决信息为脱网时长，则可以判断脱网时长是否满足网络同步条件，网络同步条件可以是脱网时长大于预设时长阈值；
1、若获取的所述脱网时长小于或等于预设时长阈值，则可以先进行网络同步等待，不立即发起向 网络端的网络状态同步，而是在存在主叫业务时，在发起网络状态同步。
2、若获取的所述脱网时长大于预设时长阈值，则可以立即触发向网络端进行网络状态同步。
进一步的，第一设备可以在脱网时即实时对脱网时长进行同步判决，当在脱网下的某一时刻大于预设时长阈值是，第一设备可进行网络恢复时的同步标记，目的在于在网络恢复时可直接基于标识的同步标记，第一设备直接发起向网络端的网络状态同步。
在一种可行的实施方式中：所述同步判决信息为所述第一设备脱网前的网络交互信息，若所述网络交互信息与参考交互信息相匹配，则向网络端进行网络状态同步；
其中，所述网络交互信息包括但不限于网络交互频率、网络交互数据量、网络交互场景中的至少一种。
如，可以基于网络交互频率设置交互频率阈值，若网络交互频率大于交互频率阈值，则可以立即触发向网络端进行网络状态同步；反之则进行网络同步等待。
如，可以基于网络交互数据量设置数据量阈值，若网络交互数据量大于数据量阈值，则可以立即触发向网络端进行网络状态同步；反之则进行网络同步等待。
如，可以基于网络交互场景预先设置至少一个参考交互场景，若网络交互场景属于参考交互场景，则可以立即触发向网络端进行网络状态同步；反之则进行网络同步等待。
当选取的判决维度参数为多个时，如同时选取网络交互频率、网络交互数据量，则可以设置为只要至少一个判决维度参数满足同步判决条件，则可以立即触发向网络端进行网络状态同步；进一步的，也可以基于实际应用环境进行设置，如进行参数加权，基于加权值来进行判决等等。
步骤S204：进行网络同步等待，并监测针对网络主叫业务的网络业务指令；
在一种可行的实施方式中，可以基于实际应用环境，设置相应执行策略，也即即使在同步判决信息满足网络同步条件时，如脱网时长大于时长阈值的情况下，也不立即向网络端进行网络状态同步，以避免信令开销造成的网络负荷，进而避免后续寻呼过程中频繁的寻呼信令造成信令风暴。第一设备可以在所述同步判决信息满足网络同步条件时，进行网络同步等待，也即不立即进行网络同步，因为此时通常而言，第一设备处于空闲状态，可以无需较早发起网络同步，而是可以监测针对网络主叫业务的网络业务指令，也即检测当前第一设备是否处于主叫业务场景，是否存在上行数据进行发送，用来判断在同步执行之前是否很快有上行数据要发送。如果是，则通过3GPP协议的主叫服务过程来完成，无需再执行一些实施方式中的同步过程(如跟踪区列表同步)。
示意性的，监测针对网络主叫业务的网络业务指令，实施中：可以开启针对网络主叫业务的监测定时器T data，，基于所述监测定时器监测针对所述网络主叫业务的网络业务指令。
步骤S205：确定监测到所述网络业务指令，向网络端进行网络状态同步。
其中监测定时器T data可以设置有倒计时，倒计时可以基于实际应用环境确定，也可以在第一设备出厂时设置好，然后第一设备可以提供人机交互界面由用户自定义确定。
进一步的，如果Tdata定时器倒计时结束之前有主叫业务对应的网络业务指令发起，则通过发起服务请求过程(Service Request)，也即生成业务服务请求，基于业务服务请求发起服务请求过程。如果Tdata定时器也超时，也即倒计时结束，则第一设备执行向网络端的网络状态同步过程，如发起跟踪区列表同步过程。
可选的，上述对网络业务指令的检测可以是：第一设备在同步判决信息满足网络同步条件之后，创建用于检测网络业务指令的业务进程，并调用第一设备所包含的资源池中的资源(如线程量、I/O口、内存)，将资源分配至业务进程，基于业务进程实现对网络业务指令的监测。进一步的，业务进程可以设置业务运行时长，在运行时长内若监测到所述网络业务指令，向网络端进行网络状态同步；若监测所述网络业务指令的时长超过运行时长，则在超时后向网络端进行网络状态同步。
在本申请实施例中，第一设备在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；若所述跟踪区标识存在于脱网前的跟踪区标识列表中，第一设备可以向网络端进行网络状态同步，从而避免在相关技术中，由于跟踪区标识存在于脱网前的跟踪区标识列表的情况下，等待网络端进行寻呼所 造成的网络状态同步的时延较高的问题，大幅降低了网络状态的同步时延，保障了后续设备正常业务服务的进行。以及，确保了第一设备在脱网恢复后与网络状态同步的实时性；以及基于多种同步判决信息可以实现对网络状态同步的智能判决，从实际通信环境出发，衡量网络同步的需求，在需要进行网络状态同步时才发起，从而避免信令符合，降低信令风暴的几率。
请参见图5，图5是本申请提出的一种网络状态同步方法的另一种实施例的流程示意图。具体的：
步骤S301：在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；
具体可参见步骤S101，此处不再赘述。
步骤S302：确定所述跟踪区标识存在于脱网前的跟踪区标识列表中。
具体可参见步骤S102，此处不再赘述。
步骤S303：获取数据传输状态，基于所述数据传输状态生成网络同步请求；
在本申请中，数据传输状态包括但不限于主叫业务状态、被叫业务状态以及空闲业务状态；
其中，处于主叫业务状态的第一设备，通常第一设备处于上行数据(如通话数据、网络应用数据)传输的业务场景，如第一设备上的应用存在上行数据需要通过网络端发送至目的地址指示的另一设备。
处于被叫业务状态的第一设备，通常第一设备处于下行数据(如通话数据、网络应用数据)传输的业务场景，如网络端存在下行数据到达需要通过网络端发送至接收地址指示的第一设备。
处于空闲业务状态的第一设备，通常第一设备无下行数据或上行数据需要传输，此时第一设备也即处于网络业务空闲的。
在一种可行的实施方式中，第一设备可检测当前时间点的数据传输状态，具体实施中可遍历后台所有业务进程是否存在数据需要传输(如下载下行数据、上传上行数据)，基于业务进程的数据传输的业务场景可检测出当前时间点的数据传输场景，继而基于数据传输场景来确定数据传输状态。
在一种可行的实施方式中，由于第一设备处于脱网恢复的场景中，会存在脱网前有相应业务进程的数据传输业务产生中断，因此造成所有数据传输业务处于业务等待状态或业务暂停状态，通常仅检测当前时间的数据传输状态难以适用于所有实际应用场景，因此，第一设备可设置一检测时长，该检测时长覆盖脱网前的任一时间点至当前的时间点，第一设备可对该检测时长内的所有业务进程的运行记录信息进行分析检测，以确定是否存在处于业务等待状态或业务暂停状态的数据传输业务，分析检测的手段可以是通过检测状态标识、传输数据进度等方式进行。
在一种具体的实施场景中，第一设备获取数据传输状态，若所述数据传输状态为主叫业务状态，则生成业务服务请求。其中，业务服务请求为在处于主叫业务状态下，第一设备由于业务场景需要，存在上行数据需要通过网络端发送至目的地址指示的另一设备时，就可以生成业务服务请求，实际应用中，第一设备发起业务服务请求用于向网络端请求上行数据传输业务，网络端会基于业务服务请求进行业务鉴权，只有在业务鉴权通过后网络端服务请求验证鉴权通过，此时通知到第一设备，第一设备才可进行后续主叫业务中上行数据的传输。另外，业务服务请求通常可以仅在第一设备处于主叫业务状态时才生成。
在一种具体的实施场景中，第一设备获取数据传输状态，若所述数据传输状态为被叫业务状态或空闲业务状态，则可以生成跟踪区更新请求。通常，在处于被叫业务状态或空闲业务状态下的第一设备，第一设备通常等待网络端在下一寻呼间隔到来时，网络端发起针对第一设备的寻呼流程，此时基于寻呼流程网络端才会与第一设备进行网络状态同步，在寻呼成功时，若存在下行数据到达则会在寻呼成功之后向第一设备进行下行数据的传输；然而实际应用中，这种方式会有与网络状态不及时，造成业务响应或处理不及时的情况；通过执行本申请的网络状态同步方法，可以在第一设备处于被叫业务状态或空闲业务状态的情况下，主动向网络端发起网络状态同步；进一步的，为了避免发生任一同步消息而该同步消息会存在被网络端的相关策略(如负载策略)屏蔽，因此，第一设备此时可以生成跟踪区更新请求，跟踪区更新请求通常在网络端的任务优先级较高，通常网络端可以对跟踪区更新请求进行及时响应。
实际应用中，第一设备在基于所述数据传输状态生成网络同步请求之后，如跟踪区更新请求、业务 服务请求，第一设备可以向所述网络端发送网络同步请求。
步骤S304：向所述网络端发送网络同步请求，以使所述网络端对所述网络同步请求进行网络恢复验证。
在实际应用中，网络端与相应设备的通信请求过程，通常会涉及到网络验证，网络验证的顺利进行基于相应设备的身份标识，如临时身份标识。
具体的，第一设备在生成网络同步请求时，如跟踪区更新请求、业务服务请求；网络同步请求会携带身份标识，身份标识可便于网络端对网络同步请求进行网络恢复验证，通常网络端在收到网络同步请求之前由于针对第一设备的寻呼流程失败，因此会认定该第一设备由于网络故障处于失联或下线中，在接收到该网络恢复验证之后，即可基于该网络同步请求携带的身份标识进行网络恢复验证，也即检测第一设备是否恢复网络。网络恢复验证的过程中，网络端会涉及到对第一设备的身份标识的验证过程，基于将身份标识与第一设备脱网前保存的参考身份标识进行匹配，若匹配则身份验证通过，不匹配则拒绝该网络同步请求，此时网络同步失败。
其中，身份标识可以是国际移动用户识别码(International Mobile Subscriber Identification Number，IMSI)，IMSI是区别移动用户的标志，储存在SIM卡中，可用于区别移动用户的有效信息。或者国际移动台设备标识(International Mobile Station Equipment Identity，IMEI)，用以识别网络端对应的某一移动通信网中的移动用户(如第一设备)。
进一步的，身份标识如IMSI通常为涉及设备隐私的安全数据，在实际通信网络环境中，考虑到空口数据安全的需求，UE(也即第一设备)不会在诸如网络同步请求等空口信令中携带IMSI和IMEI信息；同时由于网络端对应的无线网的eNodeB和核心网的MME(移动管理实体)网元之间的链路为网际协议(Internet Protocol，IP)承载链路，同样考虑到网络端对应的IP承载链路可能带来的数据安全问题，一般不在IP承载链路中传递IMSI和IMEI信息。在这些场景中，会基于网络端分配的临时移动用户标识(S-Temporary Mobile Subscriber Identity，S-TMSI)进行，S-TMSI的分配过程可以是在：第一设备附着网络端所包含的MME时，网络端会基于第一设备的身份标识(IMSI和/或IMEI信息)进行临时移动用户标识(与下述临时身份标识为同一概念)的分配，同时也建立临时移动用户标识与第一设备的身份标识的映射关系，则后续空口信令中网络端可基于携带的临时身份标识来唯一识别到该第一设备，可以理解的是，当第一设备存储的临时身份标识，或网络端存储的临时移动用户标识与第一设备的身份标识的映射关系出错或丢失，则会出现空口信令不响应或响应失败的情况下，如空口信令为网络同步请求时，则就会出现网络验证失败的情况。
实际应用中，第一设备向所述网络端发送携带临时身份标识的网络同步请求，如发送携带临时身份标识的跟踪区更新请求、如发送携带临时身份标识的业务服务请求，网络端在接收到该网络同步请求之后，可获取网络同步请求携带的临时身份标识S-TMSI，基于临时身份标识S-TMSI进行针对第一设备的身份验证以及其他网络恢复验证流程(如在身份验证后发起针对第一设备的寻呼流程)再进行对所述网络同步请求进行网络恢复验证。
步骤S305：接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功。
所述验证结果为网络端进行网络恢复验证过程中的验证后结果，包括但不限于验证成功信息和验证失败信息。
在一种具体的实施场景中，可参考图6，图6是本申请涉及的一种脱网恢复的场景示意图，第一设备在脱网恢复(此时处于图6中的t3时间点)后获取当前重新驻网服务小区的跟踪区标识，若所述跟踪区标识存在于脱网前的跟踪区标识列表中通常会等待网络端进行寻呼。在上述脱网过程中，若网络端存在网络业务需要与第一设备进行交互(如下行数据场景)，如在t3到t2时间段的某个时间点需要与第一设备进行交互，则网络端会发起针对第一设备的S-TMSI寻呼过程(也即寻呼流程)，此时，由于第一设备当前网络信号质量不佳处于脱网无服务状态，因此，网络端发起的寻呼过程失败，在相关技术中网络端通常对应寻呼失败的寻呼处理策略，如在寻呼无响应时会缓存相关业务数据，然后相隔一段时间在重新发起寻呼过程，而在网络端重新发起寻呼过程之前，第一设备会存在上述在t3时间内网络恢复的情况， 在本申请中重新驻网的小区的跟踪区标识存在于脱网前的跟踪区标识列表中，第一设备向所述网络端发送网络同步请求，网络同步请求携带S-TMSI，以使所述网络端基于S-TMSI对所述网络同步请求进行网络恢复验证；网络端接收到网络同步请求获取携带的S-TMSI，基于预存的S-TMSI临时移动用户标识与第一设备的身份标识的映射关系，来判决网络同步请求中的S-TMSI是否正确，若正确，此时网络端网络同步请求接收，通常可反馈一个同步请求接收的讯息至第一设备，然后网络端可如图6所示，再次发起针对第一设备的S-TMSI寻呼过程，当S-TMSI寻呼过程重试寻呼成功时，网络端可生成验证成功讯息至第一设备，此时第一设备即可接收所述网络端发送的验证成功信息，确定网络状态同步成功。
其中，网络同步的关键通常在于网络端保存的S-TMSI临时移动用户标识与第一设备的身份标识的映射关系是否存储正常，若数据存储正常(如未丢失)，通常同步请求成功，进而网络恢复验证对应的网络同步通常也会同步成功，反之，则会失败。
在一种具体的实施场景中，可参考图7，图7是本申请涉及的另一种脱网恢复的场景示意图，以下将结合图7对网络端针对第一设备的S-TMSI丢失的场景进行释义，如下：
在上述脱网过程中，若网络端存在网络业务需要与第一设备进行交互(如下行数据、设备状态确认场景)，如在t3到t2时间段的某个时间点需要与第一设备进行交互，但是若在第一设备脱网器件，网络端数据异常导致预存的S-TMSI临时移动用户标识与第一设备的身份标识的映射关系丢失，网络端在针对第一设备的S-TMSI寻呼过程(也即寻呼流程)必然会由于数据缺失寻呼失败，因此，在相关技术中网络端通常对应寻呼失败的寻呼处理策略，如在寻呼无响应时会缓存关于第一设备的相关业务数据，然后后续由于S-TMSI丢失后续不会重新发起S-TMSI寻呼过程，而第一设备会存在上述在t3时间后网络恢复的情况，在本申请中第一设备重新驻网的小区的跟踪区标识存在于脱网前的跟踪区标识列表中，第一设备会继续向所述网络端发送携带临时身份标识的网络同步请求，以使所述网络端基于S-TMSI对所述网络同步请求进行网络恢复验证；网络端接收到网络同步请求获取携带的S-TMSI，由于预存的S-TMSI临时移动用户标识与第一设备的身份标识的映射关系存储异常，无法针对第一设备判决网络同步请求中的S-TMSI是否正确，则会进行同步请求拒绝，通常网络端会向第一设备发送随之生成的验证失败信息。第一设备接收到所述网络端发送的验证失败信息，此时可确定所述网络端的第一临时身份标识丢失；
其中，第一临时身份标识为网络端存储的关于第一设备的临时身份标识S-TMSI，用于进行空口指令中的设备身份验证。
此时，第一设备向所述网络端发起网络身份注册流程(也即图7中的重注册过程)，在所述网络身份注册流程成功后，第一设备可确定网络状态同步成功。
一种网络身份注册过程可以是：第一设备向网络端发起网络附着(Attach)流程，网络附着流程中，第一设备会发送携带身份标识(IMSI和/或IMEI信息)的Attach Request消息至网络端所包含的网络设备(如MME)，网络端会基于第一设备的身份标识(IMSI和/或IMEI信息)进行临时身份标识的分配，同时也建立临时身份标识与第一设备的身份标识的映射关系，则后续空口信令中第一设备可基于携带的临时身份标识进行，如在t5时间段，第一设备存在主叫业务，则第一设备生成携带临时身份标识的网络业务服务请求，将该网络业务服务请求发送至网络端，网络端即可基于携带的临时身份标识来唯一识别到该第一设备，进而进行业务服务接受流程。
在本申请中，第一设备在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；若所述跟踪区标识存在于脱网前的跟踪区标识列表中，第一设备可以向网络端进行网络状态同步，从而避免在相关技术中，由于跟踪区标识存在于脱网前的跟踪区标识列表的情况下，等待网络端进行寻呼所造成的网络状态同步的时延较高的问题，大幅降低了网络状态的同步时延，保障了后续设备正常业务服务的进行。以及，确保了第一设备在脱网恢复后与网络状态同步的实时性；以及基于多种同步判决信息可以实现对网络状态同步的智能判决，从实际通信环境出发，衡量网络同步的需求，在需要进行网络状态同步时才发起，从而避免信令符合，降低信令风暴的几率；以及基于相应的数据传输状态，来对应生成相应的网络同步请求，网络同步方式多样化，提高了网络同步的智能性和便捷性，在整个网络状态更新过程中，网络侧沿用现有的3GPP协议框架，采用一般的跟踪区更新请求流程或业务服务请求流程来完成， 提高了网络状态更新的普适性以及通用性。
请参见图8，图8是本申请提出的一种网络状态同步方法的另一种实施例的流程示意图。具体的：
步骤S401：在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；
具体可参见步骤S101，此处不再赘述。
步骤S402：若所述跟踪区标识存在于脱网前的跟踪区标识列表中，获取同步判决信息，基于所述同步判决信息确定向网络端进行网络状态同步。
具体的，第一设备在获取同步判决信息之后，在基于所述同步判决信息确定向网络端进行网络状态同步时，可以预先判断网络端上针对所述第一设备的第一临时身份标识的第一存储状态。
其中，所述第一临时身份标识为网络端存储的针对第一设备的临时身份标识，网络端会在第一设备为脱网前基于第一设备的身份标识(IMSI和/或IMEI信息)进行临时身份标识的分配，同时也建立临时身份标识与第一设备的身份标识的映射关系，则后续空口信令中网络端可基于携带的临时身份标识来唯一识别到该第一设备。
所述第一存储状态为网络端上第一临时身份标识是否保存完好，第一存储状态可以是存储丢失状态，也即网络端发送数据异常导致第一临时身份标识丢失；第一存储状态可以是存储正常状态。第一存储状态在网络状态同步过程中重要性高，决定网络状态同步是否成功。
步骤S403：获取至少一个第二设备的第二存储状态；所述第二存储状态为所述网络端上所述第二设备对应的第二临时身份标识的存储状态；所述第二设备与所述第一设备处于同一局域网下；
在实际应用中，第一设备处于脱网状态下时，第一设备无法与网络端进行交互，也即无法确定网络端上第一临时身份标识的第一存储状态。而第一存储状态是否为存储正常状态，将直接关系到后续发起携带临时身份标识的网络同步请求的验证结果。在本申请中，第一设备可借鉴其他可供参考的设备的临时身份标识在网络端的存储状态来判决本端的第一存储状态。
在实际应用中，若多个设备之间所处环境的差异较小，第一设备可基于处于同一环境下的其他的可供参考的第二设备的第二存储状态，来参考判决第一存储状态。
例如第一设备与多个参***的持有者在日常使用过程中，由于移动至信号质量较差的区域，如电梯、地下车库，以及一些特定的屏蔽场所等因为覆盖不足、遮挡或人为屏蔽，会导致手机信号差甚至没有信号；此时第一设备与各参***可同时处于脱网状态，且由于各持有者在相似环境中移动具备共性，第一设备通常会与参***在脱网后又重新恢复网络，由于整个过程中，第一设备与参***间所处同一环境，其中同一环境的定义，可以是基于第一设备与参***的位置差异度(距离差异值、角度差异值)确定是否可将参***纳入参考，在位置差异度满足一定的约束条件，如预先设置差异阈值，。小于差异阈值认为满足约束条件，则认为参***是满足参考需求的第二设备。进一步的，在实际应用中，由于第一设备与各第二设备之间的设备个体差异，如设备性能，如存在某一第二设备向完成网络恢复后网络同步的情况，则此时可将向完成网络同步的某一第二设备纳入参考，获取至少一个第二设备的第二存储状态，所述第二存储状态为所述网络端上所述第二设备对应的第二临时身份标识的存储状态，基于第二存储状态来辅助判断第一设备本端对与的第一身份存储状态。
其中，第二存储状态以及第二临时身份标识与上述“第一身份存储状态以及第一临时身份标识”类似，仅设备主体不同，此处不再赘述。
进一步的，第一设备与各第二设备之间可预先进行约定网络存储状态共享策略，在任一设备完成脱网并恢复后的网络状态同步之后，将本端的临时身份标识在网络端的存储状态进行共享；其中，网络存储状态共享策略可基于第一设备与各第二设备预先加入同一局域网络，其中所述局域网络与网络端提供的通信网络不一样，且相互独立互不影响，该局域网络可以是基于蓝牙通信方式的局域网络，可以是基于紫峰通信方式的局域网络，可以是基于zigbee通信方式的局域网络，可以是基于WIFI通信方式的局域网络。具体可根据实际应用环境确定，如图9所示，图9是一种本申请涉及的局域网内设备状态同步的场景示意图，在图9中，以第一设备为电子设备1为例，以第二设备为电子设备2为例，第一设备与 第二设备的持有者由于移动至信号质量较差的区域，如电梯、地下车库导致没有信号；此时第一设备与第二设备可同时处于脱网状态，第二设备早与第一设备发起本申请涉及的网络状态同步，从而根据网络状态同步过程预先确定第二存储状态，此时，第二设备即可将第二存储状态同步至处于同一局域网下的第一设备，此时第一设备即可获取到第二设备同步的第二存储状态。当第二设备数量为多个时，此时第一设备即可获取到多个第二设备的第二存储状态。
其中，上述同步可以是第二设备采用点对点传输方式逐一向局域网下的各设备进行发送，可以是第二设备采用信息广播的方式将第二存储状态进行同步。
S404：若所述第二存储状态为存储丢失状态，则确定网络端上针对所述第一设备的第一临时身份标识的第一存储状态为所述存储丢失状态；
具体的，第一设备获取到第二存储状态之后，若第二存储状态为存储丢失状态，通常第二设备在网络状态同步过程中重新了发起网络身份注册流程。此时第一设备以第二存储状态为参考，确定网络端上针对所述第一设备的第一临时身份标识的第一存储状态为所述存储丢失状态。
S405：若所述第二存储状态为存储正常状态，则确定所述网络端上针对所述第一设备的第一临时身份标识的存储状态为存储正常状态。
具体的，第一设备获取到第二存储状态之后，若第二存储状态为存储正常状态，通常第二设备在网络状态同步过程中未发起网络身份注册流程，网络端未丢失第二设备的临时身份标识，此时第一设备以第二存储状态为参考，确定网络端上针对所述第一设备的第一临时身份标识的第一存储状态为所述存储正常状态。
S406：基于所述第一存储状态向所述网络端进行网络状态同步。
具体的，若所述第一存储状态为存储丢失状态，则第一设备可直接向所述网络端发起网络身份注册流程，而无需生成网络状态同步请求进行发送，因为即使发送网络端也会高概率请求拒绝，因此，可直接向所述网络端发起网络身份注册流程，节省信令流转时间，提高网络状态同步效率，在所述网络身份注册流程成功后，确定网络状态同步成功；
若所述第一存储状态为存储正常状态，则第一设备正常向所述网络端发送网络同步请求，以使所述网络端对所述第一设备进行网络恢复验证；确定网络状态同步成功。其中，网络同步请求携带第一临时身份标识。
S407：向至少一个第三设备同步所述第一临时身份标识的所述第一存储状态，以使所述第三设备判断所述网络端上针对所述第三设备的第三临时身份标识的第三存储状态，并基于所述第三存储状态向所述网络端进行网络状态同步；
其中，所述第三设备与所述第一设备处于同一局域网下。
具体的，第一设备在网络状态同步成功之后，可向局域网同步所述第一临时身份标识在网络端的所述第一存储状态，以使还未网络状态同步的第三设备以第一存储状态为参考，第三设备判断网络端上针对所述第三设备的第三临时身份标识的第三存储状态，并基于所述第三存储状态向所述网络端进行网络状态同步。
其中，“所述第三设备判断所述网络端上针对所述第三设备的第三临时身份标识的第三存储状态，并基于所述第三存储状态向所述网络端进行网络状态同步”可参考步骤S401-S406的相关步骤的释义，经执行主体不一样，其余执行步骤类似，此处不再赘述。
在本申请中，第一设备在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；若所述跟踪区标识存在于脱网前的跟踪区标识列表中，第一设备可以向网络端进行网络状态同步，从而避免在相关技术中，由于跟踪区标识存在于脱网前的跟踪区标识列表的情况下，等待网络端进行寻呼所造成的网络状态同步的时延较高的问题，大幅降低了网络状态的同步时延，保障了后续设备正常业务服务的进行。以及，确保了第一设备在脱网恢复后与网络状态同步的实时性；以及基于多种同步判决信息可以实现对网络状态同步的智能判决，从实际通信环境出发，衡量网络同步的需求，在需要进行网络状态同步时才发起，从而避免信令符合，降低信令风暴的几率；以及基于相应的数据传输状态，来对应生成相 应的网络同步请求，网络同步方式多样化，提高了网络同步的智能性和便捷性，在整个网络状态更新过程中，网络侧沿用现有的3GPP协议框架，采用一般的跟踪区更新请求流程或业务服务请求流程来完成，提高了网络状态更新的普适性以及通用性。
请参见图10，为本申请实施例提供的一种网络状态同步***的架构示意图。如图10所示，所述网络状态同步***包括网络端200以及第一设备100。
网络端20用于提供无线通信***对应的通信网络，网络端20包括但不限于核心网(Core Network，CN)、接入网(Radio Access Network，RAN)对应的网络设备组成。核心网负责非接入层事务，例如终端等第一设备100的位置更新等，并且是用户面的锚点。接入网包括基站，或者基站和基站控制器，接入网负责接入层事务(如，无线资源的管理等)，基站之间可以根据实际情况存在物理或者逻辑上的连接，各基站可以和核心网中的一个或者一个以上的核心网节点连接。第一设备100，是指可以和无线通讯网络通信的各种设备，比如移动电话、笔记电脑等，终端通过基站接入核心网。
MTC业务即机器类通信业务。在MTC业务中不需要人的参与，所有的通信由机器自主完成。具体地，在MTC业务中，MTC终端通过传感器等感知设备获得数据，该数据由移动运营商或者专门的MTC运营商的特定服务器进行管理，可供MTC用户或MTC管理者查看。然后，MTC终端将所述数据上报给移动通信网络，并通过移动通信网络接入到公共数据网，例如物流监控、安全监测、远程医疗检测、远程抄表等应用上。
当诸如终端等第一设备100附着到网络端200所提供的网络上时，移动性管理实体(MME，Mobility Management Entity)从归属用户服务器中获得该第一设备100的签约信息，并保存在本地。MME是核心网中用于管理终端控制信令的实体。
而第一设备100通常被网络端分配在一个跟踪区，当第一设备100移动出跟踪区时，需要发送跟踪区更新(Tracking Area Update，TAU)请求给网络侧，以便网络侧在本地修改第一设备100的跟踪区位置信息。当第一设备100不运动并且处于空闲状态时，第一设备100通常还需要进行周期性的TAU过程，即：在一个周期内，第一设备100发送TAU请求给网络端，网络端通过移动可达性计时器监视到第一设备100在线，则向第一设备100返回TAU接受消息，进入下一个周期。
第一设备100移动出跟踪区，也即第一设备100当前的驻网小区对应的跟踪区标识不再网络端下发的跟踪区标识列表中，在本申请涉及的各实施例中主要涉及到第一设备100当前的驻网小区对应的跟踪区标识再网络端下发的跟踪区标识列表时，网络状态更新方式。
在本申请中各实施例中，第一设备、第二设备以及第三设备可以是具有网络状态同步功能的电子设备，该电子设备包括但不限于：可穿戴设备、手持设备、个人电脑、平板电脑、车载设备、智能手机、计算设备或连接到无线调制解调器的其它处理设备等。在不同的网络中第一设备设备可以叫做不同的名称，例如：用户设备、接入第一设备、用户单元、用户站、移动站、移动台、远方站、远程第一设备、移动设备、用户第一设备、第一设备、无线通信设备、用户代理或用户装置、蜂窝电话、无绳电话、个人数字处理(personal digital assistant，PDA)、5G网络或未来演进网络中的电子设备等。
另外，上述实施例提供的网络状态同步***实施例与一些实施例中的所述网络状态同步方法属于同一构思，其体现实现过程详见方法实施例，这里不再赘述。
下述为本申请装置实施例，可以用于执行本申请方法实施例。对于本申请装置实施例中未披露的细节，请参照本申请方法实施例。
请参见图11，其示出了本申请一个示例性实施例提供的网络状态同步装置的结构示意图。该网络状态同步装置可以通过软件、硬件或者两者的结合实现成为装置的全部或一部分。该装置1包括标识获取模块11以及状态同步模块12。
标识获取模块11，用于在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；状态同步模块12，用于若所述跟踪区标识存在于脱网前的跟踪区标识列表中，向网络端进行网络状态同步。
可选的，所述状态同步模块12，具体用于：获取同步判决信息，基于所述同步判决信息向网络端进 行网络状态同步。
可选的，如图12所示，所述状态同步模块12，包括：第一同步单元121，用于若所述脱网时长大于预设时长阈值，则向网络端进行网络状态同步，所述同步判决信息为脱网时长；第二同步单元122，用于所述同步判决信息为所述第一设备脱网前的网络交互信息，若所述网络交互信息与参考交互信息相匹配，则向网络端进行网络状态同步；所述网络交互信息包括网络交互频率、网络交互数据量、网络交互场景中的至少一种。
可选的，所述状态同步模块12，具体用于：向所述网络端发送网络同步请求，以使所述网络端对所述网络同步请求进行网络恢复验证；接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功。
可选的，所述状态同步模块12，具体用于：获取数据传输状态，基于所述数据传输状态生成网络同步请求；向所述网络端发送网络同步请求。
可选的，所述状态同步模块12，具体用于：若所述数据传输状态为主叫业务状态，则生成业务服务请求；若所述数据传输状态为被叫业务状态或空闲业务状态，则生成跟踪区更新请求。
可选的，所述装置1，具体用于：向所述网络端发送携带临时身份标识的网络同步请求，以使所述网络端基于所述临时身份标识对所述网络同步请求进行网络恢复验证。
可选的，所述装置1，具体用于：接收所述网络端发送的验证失败信息，确定所述网络端的第一临时身份标识丢失；向所述网络端发起网络身份注册流程，在所述网络身份注册流程成功后，确定网络状态同步成功。
可选的，所述装置1，具体用于：接收所述网络端发送的验证成功信息，确定网络状态同步成功。
可选的，所述装置1，具体用于：若所述同步判决信息满足网络同步条件，则进行网络同步等待，并监测针对网络主叫业务的网络业务指令；
确定监测到所述网络业务指令，向网络端进行网络状态同步。
可选的，所述装置1，具体用于：开启针对网络主叫业务的监测定时器，基于所述监测定时器监测针对所述网络主叫业务的网络业务指令。
可选的，所述装置1，具体用于：判断网络端上针对所述第一设备的第一临时身份标识的第一存储状态；基于所述第一存储状态向所述网络端进行网络状态同步。
可选的，所述装置1，具体用于：获取至少一个第二设备的第二存储状态；所述第二存储状态为所述网络端上所述第二设备对应的第二临时身份标识的存储状态；所述第二设备与所述第一设备处于同一局域网下；若所述第二存储状态为存储丢失状态，则网络端上针对所述第一设备的第一临时身份标识的第一存储状态为所述存储丢失状态；若所述第二存储状态为存储正常状态，则确定所述网络端上针对所述第一设备的第一临时身份标识的存储状态为存储正常状态。
可选的，所述装置1，具体用于：向至少一个第三设备同步所述第一临时身份标识的所述第一存储状态，以使所述第三设备判断所述网络端上针对所述第三设备的第三临时身份标识的第三存储状态，并基于所述第三存储状态向所述网络端进行网络状态同步；
其中，所述第三设备与所述第一设备处于同一局域网下。
可选的，所述装置1，具体用于：若所述第一存储状态为存储丢失状态，则向所述网络端发起网络身份注册流程，在所述网络身份注册流程成功后，确定网络状态同步成功；若所述第一存储状态为存储正常状态，则向所述网络端发送网络同步请求，以使所述网络端对所述第一设备进行网络恢复验证；确定网络状态同步成功。
需要说明的是，上述实施例提供的网络状态同步装置在执行网络状态同步方法时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的网络状态同步装置与网络状态同步方法实施例属于同一构思，其体现实现过程详见方法实施例，这里不再赘述。
上述本申请实施例序号仅仅为了描述，不代表实施例的优劣。
本申请实施例还提供了一种计算机存储介质，所述计算机存储介质可以存储有多条指令，所述指令适于由处理器加载并执行如上述图1-图10所示实施例的所述网络状态同步方法，具体执行过程可以参见图1-图10所示实施例的具体说明，在此不进行赘述。
本申请还提供了一种计算机程序产品，该计算机程序产品存储有至少一条指令，所述至少一条指令由所述处理器加载并执行如上述图1-图10所示实施例的所述网络状态同步方法，具体执行过程可以参见图1-图10所示实施例的具体说明，在此不进行赘述。
请参考图13，其示出了本申请一个示例性实施例提供的电子设备的结构方框图。本申请中的电子设备可以包括一个或多个如下部件：处理器110、存储器120、输入装置130、输出装置140和总线150。处理器110、存储器120、输入装置130和输出装置140之间可以通过总线150连接。
处理器110可以包括一个或者多个处理核心。处理器110利用各种接口和线路连接整个电子设备内的各个部分，通过运行或执行存储在存储器120内的指令、程序、代码集或指令集，以及调用存储在存储器120内的数据，执行电子设备100的各种功能和处理数据。可选地，处理器110可以采用数字信号处理(digital signal processing，DSP)、现场可编程门阵列(field－programmable gate array，FPGA)、可编程逻辑阵列(programmable logic Array，PLA)中的至少一种硬件形式来实现。处理器110可集成中央处理器(central processing unit，CPU)、图像处理器(graphics processing unit，GPU)和调制解调器等中的一种或几种的组合。其中，CPU主要处理操作***、用户界面和应用程序等；GPU用于负责显示内容的渲染和绘制；调制解调器用于处理无线通信。可以理解的是，上述调制解调器也可以不集成到处理器110中，单独通过一块通信芯片进行实现。
存储器120可以包括随机存储器(random Access Memory，RAM)，也可以包括只读存储器(read-only memory，ROM)。可选地，该存储器120包括非瞬时性计算机可读介质(non-transitory computer-readable storage medium)。存储器120可用于存储指令、程序、代码、代码集或指令集。存储器120可包括存储程序区和存储数据区，其中，存储程序区可存储用于实现操作***的指令、用于实现至少一个功能的指令(比如触控功能、声音播放功能、图像播放功能等)、用于实现下述各个方法实施例的指令等，该操作***可以是安卓(Android)***，包括基于Android***深度开发的***、苹果公司开发的IOS***，包括基于IOS***深度开发的***或其它***。存储数据区还可以存储电子设备在使用中所创建的数据比如电话本、音视频数据、聊天记录数据，等。
参见图14所示，存储器120可分为操作***空间和用户空间，操作***即运行于操作***空间，原生及第三方应用程序即运行于用户空间。为了保证不同第三方应用程序均能够达到较好的运行效果，操作***针对不同第三方应用程序为其分配相应的***资源。然而，同一第三方应用程序中不同应用场景对***资源的需求也存在差异，比如，在本地资源加载场景下，第三方应用程序对磁盘读取速度的要求较高；在动画渲染场景下，第三方应用程序则对GPU性能的要求较高。而操作***与第三方应用程序之间相互独立，操作***往往不能及时感知第三方应用程序当前的应用场景，导致操作***无法根据第三方应用程序的具体应用场景进行针对性的***资源适配。
为了使操作***能够区分第三方应用程序的具体应用场景，需要打通第三方应用程序与操作***之间的数据通信，使得操作***能够随时获取第三方应用程序当前的场景信息，进而基于当前场景进行针对性的***资源适配。
以操作***为Android***为例，存储器120中存储的程序和数据如图15所示，存储器120中可存储有Linux内核层320、***运行时库层340、应用框架层360和应用层380，其中，Linux内核层320、***运行库层340和应用框架层360属于操作***空间，应用层380属于用户空间。Linux内核层320为电子设备的各种硬件提供了底层的驱动，如显示驱动、音频驱动、摄像头驱动、蓝牙驱动、Wi-Fi驱动、电源管理等。***运行库层340通过一些C/C++库来为Android***提供了主要的特性支持。如SQLite库提供了数据库的支持，OpenGL/ES库提供了3D绘图的支持，Webkit库提供了浏览器内核的支持等。在***运行时库层340中还提供有安卓运行时库(Android runtime)，它主要提供了一些核心库，能够允 许开发者使用Java语言来编写Android应用。应用框架层360提供了构建应用程序时可能用到的各种API，开发者也可以通过使用这些API来构建自己的应用程序，比如活动管理、窗口管理、视图管理、通知管理、内容提供者、包管理、通话管理、资源管理、定位管理。应用层380中运行有至少一个应用程序，这些应用程序可以是操作***自带的原生应用程序，比如联系人程序、短信程序、时钟程序、相机应用等；也可以是第三方开发者所开发的第三方应用程序，比如游戏类应用程序、即时通信程序、相片美化程序、网络状态同步程序等。
以操作***为IOS***为例，存储器120中存储的程序和数据如图16所示，IOS***包括：核心操作***层420(Core OS layer)、核心服务层440(Core Services layer)、媒体层460(Media layer)、可触摸层480(Cocoa Touch Layer)。核心操作***层420包括了操作***内核、驱动程序以及底层程序框架，这些底层程序框架提供更接近硬件的功能，以供位于核心服务层440的程序框架所使用。核心服务层440提供给应用程序所需要的***服务和/或程序框架，比如基础(Foundation)框架、账户框架、广告框架、数据存储框架、网络连接框架、地理位置框架、运动框架等等。媒体层460为应用程序提供有关视听方面的接口，如图形图像相关的接口、音频技术相关的接口、视频技术相关的接口、音视频传输技术的无线播放(AirPlay)接口等。可触摸层480为应用程序开发提供了各种常用的界面相关的框架，可触摸层480负责用户在电子设备上的触摸交互操作。比如本地通知服务、远程推送服务、广告框架、游戏工具框架、消息用户界面接口(User Interface，UI)框架、用户界面UIKit框架、地图框架等等。
在图16所示出的框架中，与大部分应用程序有关的框架包括但不限于：核心服务层440中的基础框架和可触摸层480中的UIKit框架。基础框架提供许多基本的对象类和数据类型，为所有应用程序提供最基本的***服务，和UI无关。而UIKit框架提供的类是基础的UI类库，用于创建基于触摸的用户界面，iOS应用程序可以基于UIKit框架来提供UI，所以它提供了应用程序的基础架构，用于构建用户界面，绘图、处理和用户交互事件，响应手势等等。其中，在IOS***中实现第三方应用程序与操作***数据通信的方式以及原理可参考Android***，本申请在此不再赘述。
其中，输入装置130用于接收输入的指令或数据，输入装置130包括但不限于键盘、鼠标、摄像头、麦克风或触控设备。输出装置140用于输出指令或数据，输出装置140包括但不限于显示设备和扬声器等。在一个示例中，输入装置130和输出装置140可以合设，输入装置130和输出装置140为触摸显示屏，该触摸显示屏用于接收用户使用手指、触摸笔等任何适合的物体在其上或附近的触摸操作，以及显示各个应用程序的用户界面。触摸显示屏通常设置在电子设备的前面板。触摸显示屏可被设计成为全面屏、曲面屏或异型屏。触摸显示屏还可被设计成为全面屏与曲面屏的结合，异型屏与曲面屏的结合，本申请实施例对此不加以限定。
除此之外，本领域技术人员可以理解，上述附图所示出的电子设备的结构并不构成对电子设备的限定，电子设备可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。比如，电子设备中还包括射频电路、输入单元、传感器、音频电路、无线保真(wireless fidelity，WiFi)模块、电源、蓝牙模块等部件，在此不再赘述。
在本申请实施例中，各步骤的执行主体可以是上文介绍的电子设备。可选地，各步骤的执行主体为电子设备的操作***。操作***可以是安卓***，也可以是IOS***，或者其它操作***，本申请实施例对此不作限定。
本申请实施例的电子设备，其上还可以安装有显示设备，显示设备可以是各种能实现显示功能的设备，例如：阴极射线管显示器(cathode ray tubedisplay，简称CR)、发光二极管显示器(light-emitting diode display，简称LED)、电子墨水屏、液晶显示屏(liquid crystal display，简称LCD)、等离子显示面板(plasma display panel，简称PDP)等。用户可以利用电子设备101上的显示设备，来查看显示的文字、图像、视频等信息。所述电子设备可以是智能手机、平板电脑、游戏设备、AR(Augmented Reality，增强现实)设备、汽车、数据存储装置、音频播放装置、视频播放装置、笔记本、桌面计算设备、可穿戴设备诸如电子手表、电子眼镜、电子头盔、电子手链、电子项链、电子衣物等设备。
在图13所示的电子设备中，其中电子设备可以是一种第一设备，处理器110可以用于调用存储器 120中存储的网络状态同步应用程序，并具体执行以下操作：
在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；
若所述跟踪区标识存在于脱网前的跟踪区标识列表中，向网络端进行网络状态同步。
在一个实施例中，所述处理器110在执行所述向网络端进行网络状态同步时，具体执行以下操作：获取同步判决信息，基于所述同步判决信息向网络端进行网络状态同步。
在一个实施例中，所述处理器110在执行所述基于所述同步判决信息向网络端进行网络状态同步时，具体执行以下操作：所述同步判决信息为脱网时长，若所述脱网时长大于预设时长阈值，则向网络端进行网络状态同步；或，所述同步判决信息为所述第一设备脱网前的网络交互信息，若所述网络交互信息与参考交互信息相匹配，则向网络端进行网络状态同步；所述网络交互信息包括网络交互频率、网络交互数据量、网络交互场景中的至少一种。
在一个实施例中，所述处理器110在执行所述向网络端进行网络状态同步时，具体执行以下操作：向所述网络端发送网络同步请求，以使所述网络端对所述网络同步请求进行网络恢复验证；接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功。
在一个实施例中，所述处理器110在执行所述向所述网络端发送网络同步请求时，具体执行以下操作：获取数据传输状态，基于所述数据传输状态生成网络同步请求；向所述网络端发送网络同步请求。
在一个实施例中，所述处理器110在执行所述获取数据传输状态，基于所述数据传输状态生成网络同步请求时，具体执行以下操作：若所述数据传输状态为主叫业务状态，则生成业务服务请求；若所述数据传输状态为被叫业务状态或空闲业务状态，则生成跟踪区更新请求。
在一个实施例中，所述处理器110在执行所述向所述网络端发送网络同步请求，以使所述网络端对所述网络同步请求进行网络恢复验证时，具体执行以下操作：向所述网络端发送携带临时身份标识的网络同步请求，以使所述网络端基于所述临时身份标识对所述网络同步请求进行网络恢复验证。
在一个实施例中，所述处理器110在执行所述接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功时，具体执行以下操作：接收所述网络端发送的验证失败信息，确定所述网络端的第一临时身份标识丢失；向所述网络端发起网络身份注册流程，在所述网络身份注册流程成功后，确定网络状态同步成功。
在一个实施例中，所述处理器110在执行所述接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功时，具体执行以下操作：
接收所述网络端发送的验证成功信息，确定网络状态同步成功。
在一个实施例中，所述处理器110在执行所述基于所述同步判决信息向网络端进行网络状态同步时，具体执行以下操作：若所述同步判决信息满足网络同步条件，则进行网络同步等待，并监测针对网络主叫业务的网络业务指令；确定监测到所述网络业务指令，向网络端进行网络状态同步。
在一个实施例中，所述处理器110在执行所述监测针对网络业务的网络请求指令时，具体执行以下操作：开启针对网络主叫业务的监测定时器，基于所述监测定时器监测针对所述网络主叫业务的网络业务指令。在一个实施例中，所述处理器110在执行所述向网络端进行网络状态同步时，具体执行以下操作：判断网络端上针对所述第一设备的第一临时身份标识的第一存储状态；基于所述第一存储状态向所述网络端进行网络状态同步。
在一个实施例中，所述处理器110在执行所述判断网络端上针对所述第一设备的第一临时身份标识的存储状态时，具体执行以下操作：获取至少一个第二设备的第二存储状态；所述第二存储状态为所述网络端上所述第二设备对应的第二临时身份标识的存储状态；所述第二设备与所述第一设备处于同一局域网下；若所述第二存储状态为存储丢失状态，则网络端上针对所述第一设备的第一临时身份标识的第一存储状态为所述存储丢失状态；若所述第二存储状态为存储正常状态，则确定所述网络端上针对所述第一设备的第一临时身份标识的存储状态为存储正常状态。
在一个实施例中，所述处理器110在执行所述网络状态更新方法时，还执行以下步骤：
向至少一个第三设备同步所述第一临时身份标识的所述第一存储状态，以使所述第三设备判断所述 网络端上针对所述第三设备的第三临时身份标识的第三存储状态，并基于所述第三存储状态向所述网络端进行网络状态同步；
其中，所述第三设备与所述第一设备处于同一局域网下。
在一个实施例中，所述处理器110在执行所述基于所述第一存储状态向所述网络端进行网络状态同步，包括：若所述第一存储状态为存储丢失状态，则向所述网络端发起网络身份注册流程，在所述网络身份注册流程成功后，确定网络状态同步成功；若所述第一存储状态为存储正常状态，则向所述网络端发送网络同步请求，以使所述网络端对所述第一设备进行网络恢复验证；确定网络状态同步成功。
以上所述者，仅为本公开的示例性实施例，不能以此限定本公开的范围。即但凡依本公开教导所作的等效变化与修饰，皆仍属本公开涵盖的范围内。本领域技术人员在考虑说明书及实践这里的公开后，将容易想到本公开的其它实施方案。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未记载的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的范围和精神由权利要求限定。

Claims (20)

  1. 一种网络状态同步方法，应用于第一设备，所述方法包括：
    在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；
    若所述跟踪区标识存在于脱网前的跟踪区标识列表中，向网络端进行网络状态同步。
  2. 根据权利要求1所述的方法，所述向网络端进行网络状态同步，包括：
    获取同步判决信息，基于所述同步判决信息向网络端进行网络状态同步。
  3. 根据权利要求2所述的方法，所述基于所述同步判决信息向网络端进行网络状态同步，包括：
    所述同步判决信息为脱网时长，若所述脱网时长大于预设时长阈值，则向网络端进行网络状态同步；或，
    所述同步判决信息为所述第一设备脱网前的网络交互信息，若所述网络交互信息与参考交互信息相匹配，则向网络端进行网络状态同步；所述网络交互信息包括网络交互频率、网络交互数据量、网络交互场景中的至少一种。
  4. 根据权利要求1所述的方法，所述向网络端进行网络状态同步，包括：
    向所述网络端发送网络同步请求，以使所述网络端对所述网络同步请求进行网络恢复验证；
    接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功。
  5. 根据权利要求4所述的方法，所述向所述网络端发送网络同步请求，包括：
    获取数据传输状态，基于所述数据传输状态生成网络同步请求；
    向所述网络端发送网络同步请求。
  6. 根据权利要求5所述的方法，所述获取数据传输状态，基于所述数据传输状态生成网络同步请求，包括：
    若所述数据传输状态为主叫业务状态，则生成业务服务请求；
    若所述数据传输状态为被叫业务状态或空闲业务状态，则生成跟踪区更新请求。
  7. 根据权利要求4所述的方法，所述向所述网络端发送网络同步请求，以使所述网络端对所述网络同步请求进行网络恢复验证，包括：
    向所述网络端发送携带临时身份标识的网络同步请求，以使所述网络端基于所述临时身份标识对所述网络同步请求进行网络恢复验证。
  8. 根据权利要求4所述的方法，所述接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功，包括：
    接收所述网络端发送的验证失败信息，确定所述网络端的第一临时身份标识丢失；
    向所述网络端发起网络身份注册流程，在所述网络身份注册流程成功后，确定网络状态同步成功。
  9. 根据权利要求4所述的方法，所述接收所述网络端发送的验证结果，基于所述验证结果确定网络状态同步成功，包括：
    接收所述网络端发送的验证成功信息，确定网络状态同步成功。
  10. 根据权利要求2所述的方法，所述基于所述同步判决信息向网络端进行网络状态同步，包括：
    若所述同步判决信息满足网络同步条件，则进行网络同步等待，并监测针对网络主叫业务的网络业务指令；
    确定监测到所述网络业务指令，向网络端进行网络状态同步。
  11. 根据权利要求10所述的方法，所述监测针对网络业务的网络请求指令，包括：
    开启针对网络主叫业务的监测定时器，基于所述监测定时器监测针对所述网络主叫业务的网络业务指令。
  12. 根据权利要求1所述的方法，所述向网络端进行网络状态同步，包括：
    判断网络端上针对所述第一设备的第一临时身份标识的第一存储状态；
    基于所述第一存储状态向所述网络端进行网络状态同步。
  13. 根据权利要求12所述的方法，所述判断网络端上针对所述第一设备的第一临时身份标识的存储状态，包括：
    获取至少一个第二设备的第二存储状态；所述第二存储状态为所述网络端上所述第二设备对应的第二临时身份标识的存储状态；所述第二设备与所述第一设备处于同一局域网下；
    若所述第二存储状态为存储丢失状态，则网络端上针对所述第一设备的第一临时身份标识的第一存储状态为所述存储丢失状态；
    若所述第二存储状态为存储正常状态，则确定所述网络端上针对所述第一设备的第一临时身份标识的存储状态为存储正常状态。
  14. 根据权利要求12所述的方法，所述方法还包括：
    向至少一个第三设备同步所述第一临时身份标识的所述第一存储状态，以使所述第三设备判断所述网络端上针对所述第三设备的第三临时身份标识的第三存储状态，并基于所述第三存储状态向所述网络端进行网络状态同步；
    其中，所述第三设备与所述第一设备处于同一局域网下。
  15. 根据权利要求13所述的方法，所述基于所述第一存储状态向所述网络端进行网络状态同步，包括：
    若所述第一存储状态为存储丢失状态，则向所述网络端发起网络身份注册流程，在所述网络身份注册流程成功后，确定网络状态同步成功；
    若所述第一存储状态为存储正常状态，则向所述网络端发送网络同步请求，以使所述网络端对所述第一设备进行网络恢复验证；确定网络状态同步成功。
  16. 一种网络状态同步装置，所述装置包括：
    标识获取模块，用于在所述第一设备脱网并恢复网络时，获取所述网络当前的跟踪区标识；
    状态同步模块，用于若所述跟踪区标识存在于脱网前的跟踪区标识列表中，向网络端进行网络状态同步。
  17. 根据权利要求16所述的方法，所述状态同步模块，具体用于：
    获取同步判决信息，基于所述同步判决信息向网络端进行网络状态同步。
  18. 根据权利要求16所述的方法，所述状态同步模块，包括：
    第一同步单元，用于若所述脱网时长大于预设时长阈值，则向网络端进行网络状态同步，所述同步判决信息为脱网时长；
    第二同步单元，用于所述同步判决信息为所述第一设备脱网前的网络交互信息，若所述网络交互信息与参考交互信息相匹配，则向网络端进行网络状态同步；所述网络交互信息包括网络交互频率、网络交互数据量、网络交互场景中的至少一种。
  19. 一种计算机存储介质，所述计算机存储介质存储有多条指令，所述指令适于由处理器加载并执行如权利要求1～15任意一项的方法步骤。
  20. 一种电子设备，包括：处理器和存储器；其中，所述存储器存储有计算机程序，所述计算机程序适于由所述处理器加载并执行如权利要求1～15任意一项的方法步骤。
PCT/CN2021/130910 2021-01-22 2021-11-16 网络状态同步方法、装置、存储介质及电子设备 WO2022156332A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110090082.3A CN112788639B (zh) 2021-01-22 2021-01-22 网络状态同步方法、装置、存储介质及电子设备
CN202110090082.3 2021-01-22

Publications (1)

Publication Number Publication Date
WO2022156332A1 true WO2022156332A1 (zh) 2022-07-28

Family

ID=75758645

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/130910 WO2022156332A1 (zh) 2021-01-22 2021-11-16 网络状态同步方法、装置、存储介质及电子设备

Country Status (2)

Country Link
CN (1) CN112788639B (zh)
WO (1) WO2022156332A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112788639B (zh) * 2021-01-22 2023-08-25 Oppo广东移动通信有限公司 网络状态同步方法、装置、存储介质及电子设备
CN113766638B (zh) * 2021-11-09 2022-03-08 深圳传音控股股份有限公司 提醒方法、终端设备、网络设备及存储介质
CN116627772B (zh) * 2023-07-20 2023-09-15 北京微吼时代科技有限公司 缓存的跟踪监控方法和***

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101494852A (zh) * 2008-01-24 2009-07-29 大唐移动通信设备有限公司 为切换过程中用户分配跟踪区标识列表的方法及装置
CN101577962A (zh) * 2008-07-10 2009-11-11 中兴通讯股份有限公司 一种关联关系更新的实现方法及相应终端
CN107682860A (zh) * 2017-09-30 2018-02-09 奇酷互联网络科技（深圳）有限公司 重定向管控方法、装置、网络设备和移动终端
CN112788639A (zh) * 2021-01-22 2021-05-11 Oppo广东移动通信有限公司 网络状态同步方法、装置、存储介质及电子设备

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8537751B2 (en) * 2011-02-01 2013-09-17 Telefonaktiebolaget Lm Ericsson (Publ) Minimizing tracking area updates in heterogeneous radio access network
CN103220653B (zh) * 2012-01-18 2018-09-25 中兴通讯股份有限公司 移动中继跟踪区域配置及位置更新方法和装置
CN105307131B (zh) * 2014-06-10 2018-10-09 普天信息技术有限公司 集群***中的组呼被叫终端重选小区时的通信方法
CN104918229B (zh) * 2015-05-06 2019-01-25 北京佰才邦技术有限公司 基站标识的确定方法和装置
WO2017045099A1 (zh) * 2015-09-14 2017-03-23 华为技术有限公司 一种寻呼的方法、设备以及***
CN109600829B (zh) * 2017-09-30 2020-11-06 深圳市海思半导体有限公司 一种恢复网络的方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101494852A (zh) * 2008-01-24 2009-07-29 大唐移动通信设备有限公司 为切换过程中用户分配跟踪区标识列表的方法及装置
CN101577962A (zh) * 2008-07-10 2009-11-11 中兴通讯股份有限公司 一种关联关系更新的实现方法及相应终端
CN107682860A (zh) * 2017-09-30 2018-02-09 奇酷互联网络科技（深圳）有限公司 重定向管控方法、装置、网络设备和移动终端
CN112788639A (zh) * 2021-01-22 2021-05-11 Oppo广东移动通信有限公司 网络状态同步方法、装置、存储介质及电子设备

Also Published As

Publication number Publication date
CN112788639B (zh) 2023-08-25
CN112788639A (zh) 2021-05-11

Similar Documents

Publication Publication Date Title
WO2022156332A1 (zh) 网络状态同步方法、装置、存储介质及电子设备
CN111869303B (zh) 一种资源调度的方法、装置、通信设备及存储介质
EP2591590B1 (en) System, apparatus and mechanism for dynamic assignment of survivability services to mobile devices
JP7412841B2 (ja) データ処理方法及び装置、電子機器、端末機器及びコンピュータプログラム
CN112260853B (zh) 容灾切换方法、装置、存储介质及电子设备
WO2020029823A1 (zh) 小区波束失败处理方法、移动通信终端和网络侧设备
CN103491162B (zh) 基于移动互联网的信息分享方法及***
CN107223363B (zh) 一种分配调度请求sr资源的方法和装置
WO2019210817A1 (zh) 无线链路恢复方法和终端
CN103338144A (zh) 一种会话数据同步方法和装置
WO2020087505A1 (zh) 数据传输方法及装置
CN114980065B (zh) 语音呼叫方法、装置及电子设备
WO2019201036A1 (zh) 覆盖级别更新方法、装置、基站、终端和可读存储介质
WO2024046169A1 (zh) 定位方法、设备和存储介质
WO2023093894A1 (zh) 感知业务实现方法、装置、网络侧设备及终端
CN113286349B (zh) 个人热点连接方法、装置、终端及存储介质
US20230292365A1 (en) Method for random access communication device, and storage medium
CN110944359B (zh) 信道带宽的控制方法、装置、存储介质及站点
CN112188245B (zh) 一种前端摄像头实时视频点播方法及装置、电子设备
CN110827971A (zh) 一种医疗后勤智能管理***
CN111147475A (zh) 语音呼叫方法、装置、存储介质及终端
CN111600757A (zh) 分布式处理计算机三维图像渲染的方法及***
US11653307B2 (en) Modifying idle mode DRX on wireless devices
CN114125048B (zh) 一种消息推送设置方法、装置、存储介质及电子设备
WO2022116211A1 (zh) 紧急呼叫方法、装置、存储介质以及终端

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21920708

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21920708

Country of ref document: EP

Kind code of ref document: A1