A service recovery method, device, apparatus and readable storage medium

Abstract

The application discloses a service recovery method and device, equipment and a readable storage medium in the field of vehicle-mounted communication technology. The method acquires and updates a context snapshot for recovering a service state of a modem subsystem based on communication context information in a running process of the modem subsystem; sends a service maintenance notification to a network side; controls the modem subsystem to perform a restart operation; reads the context snapshot after the modem subsystem completes the restart, and recovers the service state corresponding to the modem subsystem based on the context snapshot. The application ensures complete reservation of the service state before the restart through dynamic maintenance of the context snapshot, ensures effective reservation of network side resources during the restart through network side cooperation and maintenance, and directly recovers the service running state by skipping a redundant communication state reconstruction process after the restart based on the snapshot, so that the service recovery speed and communication continuity of the vehicle-mounted modem subsystem in an abnormal restart scenario can be improved.

Description

Technical Field

[0001] This application relates to the field of vehicle communication technology, and in particular to a service recovery method, apparatus, device, and readable storage medium. Background Technology

[0002] With the development of vehicle-mounted communication technology, the modem subsystem in the vehicle-mounted T-BOX (Telematics Control Unit) is used to realize the communication connection and service data transmission between the terminal device and the network side. In actual operation, due to software abnormalities, abnormal resource usage, and other reasons, the modem subsystem may experience communication failures, requiring a restart to restore operation.

[0003] Currently, after a modem subsystem restarts, it typically needs to re-establish communication with the network side, including re-establishing network connections and restoring service sessions. This results in a long service recovery time and can easily cause data service interruptions.

[0004] Therefore, how to improve the speed of service recovery in the event of an abnormal restart of the modem subsystem is a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a service recovery method, apparatus, device, and readable storage medium to improve service recovery speed in the event of an abnormal restart of the modem subsystem.

[0006] To solve the above-mentioned technical problems, this application provides the following technical solution: A business recovery method includes: Obtain communication context information during the operation of the modem subsystem, and update the context snapshot used to restore the service state of the modem subsystem based on the communication context information; Before the modem subsystem performs a reboot operation, a service retention notification is sent to the network side to ensure that the network side maintains the communication connection status and related communication resources corresponding to the modem subsystem. Control the modem subsystem to perform a reboot operation; After the modem subsystem completes its reboot, the context snapshot is read, and the service status corresponding to the modem subsystem is restored based on the context snapshot.

[0007] Preferably, obtaining communication context information during the operation of the modem subsystem includes: Obtain the air interface access layer context information, core network access layer context information, and service session context information corresponding to the modem subsystem; The air interface access layer context information, the core network access layer context information, and the service session context information are determined as the communication context information.

[0008] Preferably, after updating the context snapshot, the method further includes: The context snapshot is stored in a storage area that remains valid during a reboot of the modem subsystem; wherein the storage area is a shared storage area between the modem subsystem and the application processor.

[0009] Preferably, controlling the modem subsystem to perform a reboot operation includes: The modem core and communication protocol stack in the modem subsystem are rebooted, and the shared storage area is kept powered during the reboot to avoid data loss in the shared storage area.

[0010] Preferably, updating the context snapshot further includes: Add integrity verification information, validity period information, and version identification information to the context snapshot; Accordingly, restoring the service state corresponding to the modem subsystem based on the context snapshot includes: The validity of the context snapshot is verified based on the integrity verification information, the validity time information, and the version identification information. If the validity verification of the context snapshot fails, the network connection establishment process is re-executed to establish a communication connection between the modem subsystem and the network side. If the validity of the context snapshot is successfully verified, the service status corresponding to the modem subsystem is restored based on the context snapshot.

[0011] Preferably, sending a service retention notification to the network side includes: A service preservation notification is sent to the network side to instruct the modem subsystem to perform a temporary reboot operation, so that the network side can maintain the corresponding wireless connection status, core network connection status, and service session resources during the reboot of the modem subsystem.

[0012] Preferably, restoring the service state corresponding to the modem subsystem based on the context snapshot includes: Based on the air interface access layer context information in the context snapshot, remain in the original cell to skip the full cell search; Based on the core network access layer context information in the context snapshot, align the state with the core network to skip at least one of the network registration process and authentication process; Based on the business session context information in the context snapshot, the data business session state is restored to skip the business session establishment process.

[0013] A business recovery device, comprising: The snapshot management module is used to acquire communication context information during the operation of the modem subsystem, and update the context snapshot used to restore the service state of the modem subsystem based on the communication context information. The service retention notification module is used to send a service retention notification to the network side before the modem subsystem performs a restart operation, so that the network side maintains the communication connection status and related communication resources corresponding to the modem subsystem. The restart control module is used to control the modem subsystem to perform a restart operation; A service recovery module is used to read the context snapshot after the modem subsystem completes a reboot, and restore the service state corresponding to the modem subsystem based on the context snapshot. An electronic device includes: Memory, used to store computer programs; A processor is used to implement the steps of the above-described service recovery method when executing the computer program.

[0014] A readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the above-described service recovery method.

[0015] The method provided in this application embodiment obtains communication context information during the operation of the modem subsystem and updates the context snapshot for restoring the service state of the modem subsystem based on the communication context information; before the modem subsystem performs a restart operation, a service retention notification is sent to the network side to ensure that the network side maintains the communication connection state and related communication resources corresponding to the modem subsystem; the modem subsystem is controlled to perform a restart operation; after the modem subsystem completes the restart, the context snapshot is read and the service state corresponding to the modem subsystem is restored based on the context snapshot.

[0016] After a physical reset and reboot, the modem subsystem's internal runtime information is completely erased. Upon reboot, the entire communication state establishment process, including cell search, network attachment, authentication and encryption, and session activation, must be re-executed from scratch, resulting in prolonged service recovery time and potential data service interruptions. To accelerate service recovery, this application proposes acquiring the modem subsystem's communication context information during normal operation and dynamically updating the context snapshot used for service state recovery based on the runtime status, ensuring that the snapshot data remains consistent with the current service state. Thus, when an anomaly triggers a reboot, the modem subsystem's critical service state is pre-stored in a storage area unaffected by the reboot, providing a reliable data foundation for rapid recovery after the reboot.

[0017] Furthermore, when the modem subsystem performs a reboot, its temporary unavailability may be mistaken by the network side as signal loss or abnormal disconnection, causing the network side to prematurely release the RRC connection, core network registration status, and PDP / PDU session resources corresponding to that terminal. To address this, this application proactively sends a service preservation notification to the network side before the modem subsystem performs the reboot, explicitly informing the network side that the current terminal is about to undergo a temporary reboot. Upon receiving this notification, the network side maintains the corresponding communication connection status and related communication resources, thus preventing their release. After the reboot is complete, the modem subsystem can directly utilize the existing resources reserved by the network side to resume communication, avoiding the overhead of secondary reconstruction caused by the release of network side resources.

[0018] After the modem subsystem completes its reboot, it directly reads the context snapshot and restores the corresponding service state based on the communication context information in the snapshot. Since the modem subsystem does not need to re-execute the complete communication state establishment process, it can quickly align the service state with the resources retained by the network side using the snapshot data. Even under the adverse condition of physical reset clearing the internal operating state, it can still restore the service operating state before the reboot with minimal signaling interaction without re-establishing the communication connection.

[0019] In other words, this application ensures the complete retention of the service state before restart through dynamic maintenance of context snapshots, ensures the effective reservation of network resources during restart through network-side collaboration, and skips the redundant communication state reconstruction process based on snapshots after restart, directly restoring the service operation state. This can improve the service recovery speed and communication continuity of the vehicle modem subsystem in abnormal restart scenarios.

[0020] Accordingly, embodiments of this application also provide a service recovery apparatus, device, and readable storage medium corresponding to the above-described service recovery method, which have the aforementioned technical effects, and will not be elaborated further here. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0022] Figure 1 This is a flowchart illustrating the implementation of a service recovery method according to an embodiment of this application. Figure 2 This is a flowchart illustrating a specific implementation of a service recovery method in this application. Figure 3 This is a schematic diagram of the structure of a service recovery device according to an embodiment of this application; Figure 4 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application; Figure 5 This is a schematic diagram of the specific structure of an electronic device in an embodiment of this application. Detailed Implementation

[0023] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are merely some embodiments of the present application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0024] Please refer to Figure 1 , Figure 1 This is a flowchart of a method for fast recovery of modem services according to an embodiment of this application. The method includes the following steps.

[0025] S101. Obtain communication context information during the operation of the modem subsystem, and update the context snapshot used to restore the service state of the modem subsystem based on the communication context information.

[0026] During normal operation, the modem subsystem maintains various status information related to network communication, including the air interface connection status with the base station, the registration status with the core network, and the status of established data sessions. This status information is fundamental to the modem subsystem's ability to send and receive data normally. However, when the modem subsystem needs to be restarted due to software malfunctions, protocol stack deadlocks, or transient hardware failures, all of the above status information will be cleared during the physical reset of the modem subsystem.

[0027] In this embodiment, during the operation of the modem subsystem, communication context information is continuously acquired, and the context snapshot is dynamically updated using this communication context information. Thus, the latest acquired communication context information is stored in the context snapshot.

[0028] In practical applications, communication context information can be obtained in conjunction with anomaly detection. When an anomaly that may cause the modem to restart is detected, the communication context information can be obtained.

[0029] In one specific embodiment of this application, obtaining communication context information during the operation of the modem subsystem includes: Obtain the air interface access layer context information, core network access layer context information, and service session context information corresponding to the modem subsystem; The air interface access layer context information, core network access layer context information, and service session context information are identified as communication context information.

[0030] The air interface access layer context information refers to the state information related to the wireless connection maintained between the modem subsystem and the base station. It is mainly used for the modem subsystem to quickly camp on the original cell and restore the air interface connection after restarting. Specifically, it may include radio resource control status, cell identifier, physical cell identifier, frequency configuration information, random access resources, and signal quality parameters. The above information is the basis for the modem subsystem to camp on the cell and perform air interface communication.

[0031] Core network access layer context information refers to the registration and mobility management-related state information maintained between the modem subsystem and the core network. It is primarily used for quickly aligning the modem subsystem's state with the core network after a reboot and skipping authentication and encryption processes. For example, it may include network attachment status, tracking area information, security context, signaling connection identifier, and terminal capability information. This information is used to achieve state alignment between the modem subsystem and the core network.

[0032] Service session context information refers to the status information related to the service session established between the modem subsystem and the data network. It is mainly used to quickly restore data services and maintain the IP address and service connection after the modem subsystem restarts. It may include access point name, PDN connection identifier, PDU session identifier, IP address information, quality of service configuration parameters, service-related parameters, and data cache pointers, etc. The above information is used to restore the data service transmission capability of the modem subsystem.

[0033] By defining the above three types of context information as communication context information, the context snapshot can fully cover the entire link status from air interface access and core network registration to service sessions, providing sufficient data support for subsequent rapid recovery.

[0034] In one specific embodiment of this application, after updating the context snapshot, the method further includes: The context snapshot is stored in a storage area that remains valid during a reboot of the modem subsystem; wherein the storage area is a shared storage area between the modem subsystem and the application processor.

[0035] The application processor is the main processor that runs the operating system and user applications. The modem subsystem and the application processor typically share a memory area. For example, a shared partition in Double Data Rate Synchronous Dynamic Random Access Memory (DDR) is used. This memory area remains powered even when the modem subsystem performs a physical reset, and the data within it is not lost due to a restart of the modem subsystem.

[0036] This application utilizes the shared storage area as the storage medium for context snapshots. Snapshot data is written to this area after each snapshot update, ensuring that snapshot data is not lost during restarts and can be accessed quickly. Simultaneously, to protect the security of the snapshot data, a cyclic redundancy check (CRC) is added to the snapshot data to verify data integrity, a timestamp is added to record the snapshot generation time and determine snapshot validity, and a version number is added to identify the modem firmware version corresponding to the snapshot to adapt to data structure differences between different firmware versions. In terms of storage strategy, only the latest context snapshot is saved, and each time a new snapshot is triggered, the old snapshot is automatically overwritten to avoid multi-version conflicts and reduce memory usage.

[0037] In one specific embodiment of this application, the update of the context snapshot can be achieved through a combination of active and passive triggering, where either condition is met to trigger a snapshot update. Specifically, the passive triggering method refers to triggering a snapshot update immediately before the restart when an anomaly is detected in the modem subsystem and an imminent restart is triggered, in order to capture the latest service status before the anomaly occurs. The periodic triggering method refers to automatically performing a snapshot update every preset time period, such as 10 seconds, during normal operation to ensure the timeliness of the snapshot data. The two methods can also be used in combination, that is, periodically maintaining snapshots during normal operation, while triggering an additional snapshot collection when an anomaly occurs, thereby maximizing the integrity and timeliness of the snapshot data.

[0038] For example, the context snapshot includes: Air Access Layer (AS) context, Core Network Access Layer (NAS) context, and PDP / PDU session context. The Air Access Layer (AS) context is primarily used for quickly re-establishing the original cell and restoring air interface connections after a modem reboot, and specifically includes: RRC status, cell-related information, frequency configuration, random access resources, and signal quality parameters. The Core Network Access Layer (NAS) context is primarily used for quickly aligning the modem with the core network after a reboot, skipping the authentication and encryption process, and specifically includes: Attach status, Tracking Area (TA) information, security context, signaling connection identifier, and terminal capability information. The PDP / PDU session context is primarily used for quickly restoring data services after a modem reboot, maintaining the IP address and service connection unchanged, and specifically includes: Access Point Name (APN), PDN connection ID, IP address information, QoS configuration, service-related parameters, and data cache pointer. The context snapshot triggering timing uses a combination of active and passive triggering; a snapshot is triggered when either condition is met, ensuring that the context is completely preserved before an abnormal reboot. The specific triggering timing is as follows: Passive trigger: A context snapshot is recorded before a Modem anomaly is detected and a reboot is about to be triggered.

[0039] Periodic backup trigger: During normal operation, a context snapshot is automatically backed up every 10 seconds.

[0040] To ensure that context snapshots are not lost during modem restarts and can be accessed quickly, this invention adopts the following storage method: Storage medium: Stored in the shared memory of the modem and the access point (such as the DDR shared area). This area will not lose power when the modem subsystem restarts and can be accessed quickly.

[0041] Data protection: Add CRC checksum (for verifying data integrity), timestamp (for determining the validity of the snapshot, e.g., timeout is set to 20 seconds), and version number (for adapting to different modem firmware versions) to the snapshot data.

[0042] Storage strategy: Only the latest context snapshot is saved. Each time a new snapshot is triggered, the old snapshot is automatically overwritten to avoid multiple version conflicts and reduce memory usage.

[0043] S102. Before the modem subsystem performs a restart operation, a service retention notification is sent to the network side to ensure that the network side maintains the communication connection status and related communication resources corresponding to the modem subsystem.

[0044] When the modem subsystem performs a reboot, it will disappear from the network due to temporary unavailability. If the network does not receive any signal from the terminal during this period, it will determine the terminal as having lost signal or abnormally disconnected from the network according to the network protocol, and will then actively release the radio resource control connection, core network registration status, and packet data network connection or protocol data unit session resources corresponding to the terminal. Once the network releases the above resources, even if the modem subsystem retains a complete context snapshot locally after rebooting, it still needs to re-initiate the complete attach and session establishment process, which will severely weaken the effectiveness of the snapshot recovery mechanism. The radio resource control connection refers to the logical connection between the terminal and the base station used for transmitting signaling and data, while the packet data network connection or protocol data unit session refers to the logical channel established between the terminal and the data network for data transmission.

[0045] To address this issue, this embodiment proactively sends a service hold notification to the network side using the still-valid air interface signaling link before the modem subsystem performs a physical reset. This notification informs the network side that the terminal is about to undergo a brief reboot and requests that the network side maintain the established communication connection status and related communication resources during this period. Upon receiving this notification, the network side marks the corresponding terminal context as temporarily suspended, maintaining the validity and integrity of the radio resource control connection, core network registration status, and packet data network connection or protocol data unit session resources, awaiting reconnection after the terminal reboots.

[0046] In one specific embodiment of this application, sending a service retention notification to the network side includes: sending a service retention notification to the network side to instruct the modem subsystem to perform a temporary reboot operation, so that the network side maintains the corresponding wireless connection state, core network connection state, and service session resources during the reboot of the modem subsystem.

[0047] Specifically, the service hold notification can carry indication information to specify the expected duration or type of the current restart operation. For example, the notification may include a preset hold duration parameter, instructing the network side to keep resources unreleased within this duration. The network side can set a corresponding hold timer based on this parameter, and only release resources if the terminal fails to restore the connection before the timer expires, thereby avoiding prolonged invalid occupation of network resources due to terminal recovery failure. Alternatively, the notification may only carry a temporary suspension indication, with the network side determining the resource hold time based on its own configuration policy.

[0048] S103, Control the modem subsystem to perform a restart operation.

[0049] After updating and storing the context snapshot and sending a service hold notification to the network side, the modem subsystem can be restarted. This restart operation is controlled by the application processor, which resets the power supply or reset signal of the modem subsystem, clearing all its internal runtime information, including CPU register values, internal random access memory data, and protocol stack runtime status, thereby eliminating problems such as software deadlock, memory leaks, or state machine malfunctions that could cause anomalies.

[0050] In one specific embodiment of this application, controlling the modem subsystem to perform a restart operation includes: restarting the modem core and communication protocol stack in the modem subsystem, and maintaining power to the shared storage area during the restart to avoid losing data in the shared storage area.

[0051] The modem subsystem internally includes a modem core, i.e., the baseband processing core, responsible for running the communication protocol stack and control logic, i.e., the software code implementing the physical layer to network layer communication protocol. The reboot operation in this application is performed on the modem core and the communication protocol stack, i.e., resetting the modem core's operating state and reloading the communication protocol stack. During this process, the shared memory area between the modem subsystem and the upper-layer application processor remains powered and in normal working order, and the context snapshot data stored therein is unaffected. By rebooting only the core and protocol stack, rather than power-off rebooting the entire modem chip, the integrity of the snapshot data in the shared memory area is protected to the greatest extent while clearing abnormal operating states.

[0052] S104. After the modem subsystem completes the reboot, read the context snapshot and restore the corresponding service status of the modem subsystem based on the context snapshot.

[0053] After the modem subsystem completes a physical reset and reloads the communication protocol stack, all its internal runtime information is cleared, and it does not yet have the ability to communicate with the network. Traditionally, this would require starting from scratch with a complete communication state establishment process, including full-band cell search, network attachment, authentication and encryption, packet data network connection, or protocol data unit session activation, which is time-consuming. Considering that a context snapshot has been pre-maintained in S101 and that the network side has kept resources from being released in S102, this embodiment first reads the context snapshot from the shared storage area after the modem subsystem restarts. Then, based on the communication context information saved in the snapshot, it restores the corresponding service state of the modem subsystem level by level.

[0054] In one specific embodiment of this application, updating the context snapshot further includes: Add integrity verification information, validity period information, and version identification information to the context snapshot; Accordingly, the service state of the modem subsystem is restored based on the context snapshot, including: The validity of the context snapshot is verified based on the integrity verification information, validity period information, and version identification information. If the validity verification of the context snapshot fails, the network connection establishment process is re-executed to establish a communication connection between the modem subsystem and the network side. If the validity of the context snapshot is successfully verified, the service state corresponding to the modem subsystem is restored based on the context snapshot.

[0055] like Figure 2 As shown, after reading the context snapshot, its validity can be verified. Specifically, data integrity is determined based on the Cyclic Redundancy Check (CRC) code in the snapshot. This involves recalculating the CRC value of the snapshot data and comparing it with the stored value. If they match, the data is considered complete and valid; otherwise, it indicates that the data has been corrupted or tampered with. The snapshot's timestamp is used to determine if it has expired. This involves comparing the current time with the snapshot's creation time. If the time difference is within a preset validity period (e.g., 20 seconds), it is considered valid; otherwise, it is considered expired. The version number in the snapshot is used to determine if it matches the current modem firmware version. This involves comparing the version number in the snapshot with the current firmware version. If they match, it is considered a match; otherwise, it is considered a mismatch. If all three verifications pass, the context snapshot is considered valid, and the snapshot-based fast recovery process begins. If any verification fails, such as data tampering, expiration, or version mismatch, the process automatically reverts to the traditional restart process. This involves re-executing the entire process of cell search, network attachment, authentication and encryption, packet data network connection, or protocol data unit session activation to avoid prolonged service interruptions caused by recovery anomalies.

[0056] In one specific embodiment of this application, restoring the service state corresponding to the modem subsystem based on a context snapshot includes: Based on the air interface access layer context information in the context snapshot, remain in the original cell to skip the full cell search; Based on the core network access layer context information in the context snapshot, align the state with the core network to skip at least one of the network registration process and authentication process; Based on the business session context information in the context snapshot, restore the data business session state to skip the business session establishment process.

[0057] To more clearly illustrate the steps skipped in this application compared to the full business recovery process after a restart, and their technical effects, a comparison is made below between the traditional complete connection establishment process and the rapid recovery process of this application.

[0058] The traditional complete connection establishment process includes the following steps: Step 1: Full-band cell search. The modem scans all supported frequency bands, measures the signal strength of each cell, synchronizes the downlink, and completes cell selection.

[0059] Step 2, Network Attach Request. The modem sends an attach request message to the core network, carrying the terminal's identity and capability information.

[0060] Step 3: Authentication and Encryption Negotiation. The core network authenticates the terminal, and both parties negotiate the encryption algorithm and integrity protection algorithm to generate a security key.

[0061] Step four: Packet data network connection or protocol data unit session activation. The modem negotiates the access point name with the core network, the core network assigns an IP address to the terminal, establishes a quality of service flow, and completes the establishment of the data service session.

[0062] The rapid recovery process for this application includes the following steps: Step 1: Based on the cell identifier, physical cell identifier and frequency configuration information in the air interface access layer context, the radio frequency front-end is directly tuned to the corresponding frequency to quickly camp on the original cell.

[0063] Step 2: Based on the attachment state, tracking area information, and security context in the core network access layer context, directly align the state with the core network.

[0064] Step 3: Based on information such as the access point name, IP address, quality of service configuration, packet data network connection identifier, or protocol data unit session identifier in the service session context, directly restore the established session connection.

[0065] A comparison of the two above shows that: The first step of the traditional process is a full-band cell search, while the first step of this application is to directly camp on the original cell based on a snapshot. Compared with the two, this application skips the full-band scanning and cell search processes.

[0066] The traditional process involves a network attach request as step two, while this application involves core network state alignment as step two. In contrast, this application skips the network attach request process.

[0067] The traditional process involves authentication and encryption negotiation in step three, while this application simultaneously completes core network state alignment in step two. In comparison, this application skips the authentication and encryption negotiation process.

[0068] The traditional process involves step four, which is the activation of a packet data network connection or protocol data unit session. In contrast, step three of this application involves directly restoring the session connection based on a snapshot. Compared to the traditional process, this application skips the complete session activation process.

[0069] In summary, this application skips four main steps in the traditional complete connection establishment process during modem restart recovery: full-band cell search, network attach request, authentication and encryption negotiation, and packet data network connection or protocol data unit session activation. Based on the above comparison, it is clear that the traditional process requires a considerable amount of time to complete service recovery, while this application only needs to perform snapshot reading, verification, and rapid recovery operations to significantly shorten service interruption time, achieving seamless recovery on both the user and network sides. This significantly improves the service recovery speed and communication continuity of the vehicle modem subsystem in abnormal restart scenarios.

[0070] It should be noted that the above three-layer recovery process has a strict time dependency: the air interface connection, i.e., the camped cell, must be restored first before core network state alignment can be performed, and finally, the data session can be restored. This order is determined by the hierarchical structure of the communication protocol stack; upper-layer protocols must rely on the basic connection established by lower-layer protocols. This application strictly follows this time sequence to perform the recovery, ensuring that each layer is restored and provides a foundation for the next layer before proceeding to the next, thereby guaranteeing the stability and success rate of the recovery process. If any recovery step fails, it automatically switches to the traditional connection establishment process, performing the entire process of cell search, network attachment, authentication and encryption, packet data network connection, or protocol data unit session activation, to ensure that the terminal can restore its communication capability under any circumstances.

[0071] The method provided in this application embodiment obtains communication context information during the operation of the modem subsystem and updates the context snapshot for restoring the service state of the modem subsystem based on the communication context information; before the modem subsystem performs a restart operation, a service retention notification is sent to the network side to ensure that the network side maintains the communication connection state and related communication resources corresponding to the modem subsystem; the modem subsystem is controlled to perform a restart operation; after the modem subsystem completes the restart, the context snapshot is read and the service state corresponding to the modem subsystem is restored based on the context snapshot.

[0072] After a physical reset and reboot, the modem subsystem's internal runtime information is completely erased. Upon reboot, the entire communication state establishment process, including cell search, network attachment, authentication and encryption, and session activation, must be re-executed from scratch, resulting in prolonged service recovery time and potential data service interruptions. To accelerate service recovery, this application proposes acquiring the modem subsystem's communication context information during normal operation and dynamically updating the context snapshot used for service state recovery based on the runtime status, ensuring that the snapshot data remains consistent with the current service state. Thus, when an anomaly triggers a reboot, the modem subsystem's critical service state is pre-stored in a storage area unaffected by the reboot, providing a reliable data foundation for rapid recovery after the reboot.

[0073] Furthermore, when the modem subsystem performs a reboot, its temporary unavailability may be mistaken by the network side as signal loss or abnormal disconnection, causing the network side to prematurely release the RRC connection, core network registration status, and PDP / PDU session resources corresponding to that terminal. To address this, this application proactively sends a service preservation notification to the network side before the modem subsystem performs the reboot, explicitly informing the network side that the current terminal is about to undergo a temporary reboot. Upon receiving this notification, the network side maintains the corresponding communication connection status and related communication resources, thus preventing their release. After the reboot is complete, the modem subsystem can directly utilize the existing resources reserved by the network side to resume communication, avoiding the overhead of secondary reconstruction caused by the release of network side resources.

[0074] After the modem subsystem completes its reboot, it directly reads the context snapshot and restores the corresponding service state based on the communication context information in the snapshot. Since the modem subsystem does not need to re-execute the complete communication state establishment process, it can quickly align the service state with the resources retained by the network side using the snapshot data. Even under the adverse condition of physical reset clearing the internal operating state, it can still restore the service operating state before the reboot with minimal signaling interaction without re-establishing the communication connection.

[0075] In other words, this application ensures the complete retention of the service state before restart through dynamic maintenance of context snapshots, ensures the effective reservation of network resources during restart through network-side collaboration, and skips the redundant communication state reconstruction process based on snapshots after restart, directly restoring the service operation state. This can improve the service recovery speed and communication continuity of the vehicle modem subsystem in abnormal restart scenarios.

[0076] Corresponding to the above method embodiments, this application also provides a service recovery device, and the service recovery device described below can be referred to in correspondence with the service recovery method described above.

[0077] See Figure 3 As shown, the device includes the following modules: The snapshot management module 101 is used to obtain communication context information during the operation of the modem subsystem and update the context snapshot used to restore the service status of the modem subsystem based on the communication context information. The service retention notification module 102 is used to send a service retention notification to the network side before the modem subsystem performs a restart operation, so that the network side maintains the communication connection status and related communication resources corresponding to the modem subsystem. The restart control module 103 is used to control the modem subsystem to perform a restart operation; The service recovery module 104 is used to read the context snapshot after the modem subsystem has restarted and restore the corresponding service status of the modem subsystem based on the context snapshot.

[0078] Using the apparatus provided in the embodiments of this application, communication context information during the operation of the modem subsystem is obtained, and a context snapshot for restoring the service state of the modem subsystem is updated based on the communication context information; before the modem subsystem performs a restart operation, a service retention notification is sent to the network side so that the network side maintains the communication connection state and related communication resources corresponding to the modem subsystem; the modem subsystem is controlled to perform a restart operation; after the modem subsystem completes the restart, the context snapshot is read, and the service state corresponding to the modem subsystem is restored based on the context snapshot.

[0079] After a physical reset and reboot, the modem subsystem's internal runtime information is completely erased. Upon reboot, the entire communication state establishment process, including cell search, network attachment, authentication and encryption, and session activation, must be re-executed from scratch, resulting in prolonged service recovery time and potential data service interruptions. To accelerate service recovery, this application proposes acquiring the modem subsystem's communication context information during normal operation and dynamically updating the context snapshot used for service state recovery based on the runtime status, ensuring that the snapshot data remains consistent with the current service state. Thus, when an anomaly triggers a reboot, the modem subsystem's critical service state is pre-stored in a storage area unaffected by the reboot, providing a reliable data foundation for rapid recovery after the reboot.

[0080] Furthermore, when the modem subsystem performs a reboot, its temporary unavailability may be mistaken by the network side as signal loss or abnormal disconnection, causing the network side to prematurely release the RRC connection, core network registration status, and PDP / PDU session resources corresponding to that terminal. To address this, this application proactively sends a service preservation notification to the network side before the modem subsystem performs the reboot, explicitly informing the network side that the current terminal is about to undergo a temporary reboot. Upon receiving this notification, the network side maintains the corresponding communication connection status and related communication resources, thus preventing their release. After the reboot is complete, the modem subsystem can directly utilize the existing resources reserved by the network side to resume communication, avoiding the overhead of secondary reconstruction caused by the release of network side resources.

[0081] After the modem subsystem completes its reboot, it directly reads the context snapshot and restores the corresponding service state based on the communication context information in the snapshot. Since the modem subsystem does not need to re-execute the complete communication state establishment process, it can quickly align the service state with the resources retained by the network side using the snapshot data. Even under the adverse condition of physical reset clearing the internal operating state, it can still restore the service operating state before the reboot with minimal signaling interaction without re-establishing the communication connection.

[0082] In other words, this application ensures the complete retention of the service state before restart through dynamic maintenance of context snapshots, ensures the effective reservation of network resources during restart through network-side collaboration, and skips the redundant communication state reconstruction process based on snapshots after restart, directly restoring the service operation state. This can improve the service recovery speed and communication continuity of the vehicle modem subsystem in abnormal restart scenarios.

[0083] In one specific embodiment of this application, the snapshot management module is specifically used to obtain the air interface access layer context information, core network access layer context information, and service session context information corresponding to the modem subsystem; and to determine the air interface access layer context information, core network access layer context information, and service session context information as communication context information.

[0084] In one specific embodiment of this application, the snapshot management module is further configured to store the context snapshot in a storage area that remains valid during the modem subsystem's reboot operation after updating the context snapshot; wherein, the storage area is a shared storage area between the modem subsystem and the application processor.

[0085] In one specific embodiment of this application, the restart control module is specifically used to restart the modem core and communication protocol stack in the modem subsystem, and the shared storage area is kept powered during the restart to avoid losing data in the shared storage area.

[0086] In one specific embodiment of this application, the snapshot management module is further configured to add integrity verification information, validity period information, and version identification information to the context snapshot when updating the context snapshot; the service recovery module is specifically configured to verify the validity of the context snapshot based on the integrity verification information, validity period information, and version identification information; if the validity verification of the context snapshot fails, the network connection establishment process is re-executed to establish a communication connection between the modem subsystem and the network side; if the validity verification of the context snapshot succeeds, the service status corresponding to the modem subsystem is restored based on the context snapshot.

[0087] In one specific embodiment of this application, the service retention notification module is specifically used to send a service retention notification to the network side to instruct the modem subsystem to perform a temporary restart operation, so that the network side maintains the corresponding wireless connection status, core network connection status, and service session resources during the modem subsystem restart.

[0088] In one specific embodiment of this application, the service recovery module is specifically used to: stay in the original cell to skip the full cell search based on the air interface access layer context information in the context snapshot; align with the core network state based on the core network access layer context information in the context snapshot to skip at least one of the network registration process and the authentication process; and restore the data service session state based on the service session context information in the context snapshot to skip the service session establishment process.

[0089] Corresponding to the above method embodiments, this application also provides an electronic device. The electronic device described below and the service recovery method described above can be referred to in correspondence.

[0090] See Figure 4 As shown, the electronic device includes: Memory 332 is used to store computer programs; The processor 322 is used to implement the steps of the service recovery method in the above method embodiment when executing a computer program.

[0091] For details, please refer to Figure 5 , Figure 5 This is a schematic diagram of the specific structure of an electronic device provided in this embodiment. The electronic device can vary significantly due to differences in configuration or performance. It may include one or more central processing units (CPUs) (e.g., one or more processors) and a memory 332. The memory 332 stores one or more computer programs 342 or data 344. The memory 332 can be temporary or permanent storage. The program stored in the memory 332 may include one or more modules (not shown in the diagram), each module may include a series of instruction operations on the data processing device. Furthermore, the processor 322 may be configured to communicate with the memory 332 and execute the series of instruction operations stored in the memory 332 on the electronic device 301.

[0092] Electronic device 301 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input / output interfaces 358, and / or one or more operating systems 341.

[0093] The steps in the service recovery method described above can be implemented by the structure of the electronic device.

[0094] Corresponding to the above method embodiments, this application also provides a readable storage medium. The readable storage medium described below and the service recovery method described above can be referred to in correspondence.

[0095] A readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of the service recovery method described in the above method embodiments.

[0096] The readable storage medium can specifically be a USB flash drive, external hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk, or any other readable storage medium capable of storing program code.

[0097] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0098] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0099] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0100] Finally, it should be noted that in this document, relationships such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "include," "contain," or any other variations are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus.

[0101] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A service recovery method, characterized in that, include: Obtain communication context information during the operation of the modem subsystem, and update the context snapshot used to restore the service state of the modem subsystem based on the communication context information; Before the modem subsystem performs a reboot operation, a service retention notification is sent to the network side to ensure that the network side maintains the communication connection status and related communication resources corresponding to the modem subsystem. Control the modem subsystem to perform a reboot operation; After the modem subsystem completes its reboot, the context snapshot is read, and the service status corresponding to the modem subsystem is restored based on the context snapshot.

2. The method according to claim 1, characterized in that, Obtaining communication context information during the operation of the modem subsystem includes: Obtain the air interface access layer context information, core network access layer context information, and service session context information corresponding to the modem subsystem; The air interface access layer context information, the core network access layer context information, and the service session context information are determined as the communication context information.

3. The method according to claim 1, characterized in that, After updating the context snapshot, it also includes: The context snapshot is stored in a storage area that remains valid during a reboot of the modem subsystem; wherein the storage area is a shared storage area between the modem subsystem and the application processor.

4. The method according to claim 3, characterized in that, Controlling the modem subsystem to perform a reboot operation includes: The modem core and communication protocol stack in the modem subsystem are rebooted, and the shared storage area is kept powered during the reboot to avoid data loss in the shared storage area.

5. The method according to claim 1, characterized in that, When updating the context snapshot, the method also includes: Add integrity verification information, validity period information, and version identification information to the context snapshot; Accordingly, restoring the service state corresponding to the modem subsystem based on the context snapshot includes: The validity of the context snapshot is verified based on the integrity verification information, the validity time information, and the version identification information. If the validity verification of the context snapshot fails, the network connection establishment process is re-executed to establish a communication connection between the modem subsystem and the network side. If the validity of the context snapshot is successfully verified, the service status corresponding to the modem subsystem is restored based on the context snapshot.

6. The method according to claim 1, characterized in that, Sending a service retention notification to the network side includes: A service preservation notification is sent to the network side to instruct the modem subsystem to perform a temporary reboot operation, so that the network side can maintain the corresponding wireless connection status, core network connection status, and service session resources during the reboot of the modem subsystem.

7. The method according to any one of claims 1 to 6, characterized in that, Restore the service status of the modem subsystem based on the context snapshot, including: Based on the air interface access layer context information in the context snapshot, remain in the original cell to skip the full cell search; Based on the core network access layer context information in the context snapshot, align the state with the core network to skip at least one of the network registration process and authentication process; Based on the business session context information in the context snapshot, the data business session state is restored to skip the business session establishment process.

8. A service recovery device, characterized in that, include: The snapshot management module is used to acquire communication context information during the operation of the modem subsystem, and update the context snapshot used to restore the service state of the modem subsystem based on the communication context information. The service retention notification module is used to send a service retention notification to the network side before the modem subsystem performs a restart operation, so that the network side maintains the communication connection status and related communication resources corresponding to the modem subsystem. The restart control module is used to control the modem subsystem to perform a restart operation; The service recovery module is used to read the context snapshot after the modem subsystem has completed a reboot, and restore the service status corresponding to the modem subsystem based on the context snapshot.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor, configured to implement the steps of the service recovery method as described in any one of claims 1 to 7 when executing the computer program.

10. A readable storage medium, characterized in that, The readable storage medium stores a computer program that, when executed by a processor, implements the steps of the service recovery method as described in any one of claims 1 to 7.

Images