Software version number updating method and device, electronic equipment and computer readable storage medium

Abstract

This application discloses a method, apparatus, electronic device, and computer-readable storage medium for updating software version numbers, relating to the field of software update technology. The method includes: downloading an updated SVN configuration file and initiating an SVN setting request through a system component interface; responding to the SVN setting request, parsing the SVN configuration file to obtain the SVN and verifying the validity of the SVN; storing the verified SVN to an underlying permanent storage partition and setting SVN system properties to trigger a silent modem restart; after the modem restarts silently, initializing the modem based on the SVN system properties and the maximum value between the SVN information in the permanent storage partition and the original local SVN information; updating the SVN retrieval interface of the client's telephony service component and updating the SVN display through the SVN retrieval interface. Thus, this solution can update the SVN without restarting the client.

Description

Technical Field

[0001] This application relates to the field of software update technology, specifically to a software version number update method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] Regular updates to the Software Version Number (SVN) of Android devices rely on over-the-air (OTU) firmware updates. The The Air (FOTA) solution provides system and SVN update services to network-enabled terminals via the cloud. However, FOTA SVN updates require a device reboot to take effect, and the upgrade process is cumbersome and time-consuming, making it difficult to meet the demand for timely SVN updates. Furthermore, FOTA involves significant investment of manpower and maintenance resources, resulting in high overall operating costs. Therefore, there is an urgent need for an SVN update solution that offers flexibility, low resource consumption, and a superior user experience. Summary of the Invention

[0003] This application provides a software version number update method, apparatus, electronic device, and computer-readable storage medium that can update SVN without restarting the client.

[0004] In a first aspect, embodiments of this application provide a software version number update method, applied to a client, the method comprising: When an SVN update to the software version number is detected in the data center, the updated SVN configuration file is downloaded and an SVN configuration request is initiated through the system component interface; wherein, the SVN configuration file is configured and compiled by the online customization platform and then pushed to the data center; In response to the SVN setup request, the SVN configuration file is parsed to obtain the SVN, and the validity of the SVN is verified. The verified SVN is stored in the underlying permanent storage partition, and SVN system properties are set to trigger a silent modem restart; After the modem silently restarts, the modem is initialized based on the SVN system attributes and the maximum value between the SVN information in the permanent storage partition and the original local SVN information. Update the SVN retrieval interface of the client's telephony service component, and update the SVN display through the SVN retrieval interface.

[0005] In one embodiment, the method further includes: Based on the SVN download interface provided by the data center, the data center is periodically polled to determine whether there are SVN updates in the data center.

[0006] In one embodiment, storing the verified SVN to the underlying permanent storage partition and setting SVN system properties to trigger a silent modem reboot includes: Store the verified SVN to the permanent storage partition and set the SVN system properties; The client's telephony service component listens for change events of the SVN system properties; The telephony service component triggers a silent restart of the modem after detecting a change in the SVN system properties.

[0007] In one embodiment, the method further includes: The underlying layer of the client reads the SVN from the permanent storage partition and generates a system read-only attribute when the system boots up; The modem reads the system's read-only attributes to obtain SVN information during initialization.

[0008] In one embodiment, the method further includes: Collect status information during the SVN update process and upload it to the data center so that the data center can display the SVN update status through a Kanban board.

[0009] In one embodiment, the online customization platform provides online visual customization capabilities for SVN data; The SVN configuration file is obtained by the online customization platform through a compilation pipeline that compiles the customized SVN data.

[0010] In one embodiment, the online customization platform supports the regression of SVN data into the code repository after SVN release.

[0011] Secondly, embodiments of this application provide a software version number update device, applied to a client, the device comprising: The update download module is used to download the updated SVN configuration file and initiate an SVN configuration request through the system component interface when an SVN update is detected in the data center; wherein, the SVN configuration file is configured and compiled by the online customization platform and then pushed to the data center; The parsing and verification module is used to respond to the SVN setting request, parse the SVN configuration file to obtain the SVN, and verify the validity of the SVN; The SVN storage module is used to store the verified SVN to the underlying permanent storage partition and set SVN system properties to trigger a silent restart of the modem. An initialization module is used to initialize the modem after the modem has silently restarted, based on the SVN system attributes and the maximum value between the SVN information in the permanent storage partition and the original local SVN information. The update display module is used to update the SVN retrieval interface of the client's telephony service component, and update the SVN display through the SVN retrieval interface.

[0012] Thirdly, embodiments of this application also provide an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, it implements the steps in the software version number update method described above.

[0013] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the software version number update method described above.

[0014] Fifthly, embodiments of this application also provide a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods provided in the various optional implementations described in embodiments of this application.

[0015] The embodiments of this application have the following beneficial effects: The online customization platform can configure and compile SVN configuration files and push them to the data center. When the client detects an SVN update in the data center, it can automatically download the updated SVN configuration file and configure SVN settings. Users only need to configure SVN through the online customization platform to achieve proactive SVN update triggering, without the need for extensive manpower. The platform parses the SVN configuration file to obtain the SVN and verifies its validity, filtering out invalid or abnormal SVNs, thus improving the accuracy and reliability of SVN updates. Verified SVNs are stored in the underlying permanent storage partition, and SVN system properties are set to trigger a silent modem restart. Based on the SVN system properties and the maximum value between the SVN information in the permanent storage partition and the original local SVN information, the modem is initialized, enabling the persistence of the SVN. Persistence is achieved by ensuring that the SVN can be read from the permanent storage partition even after a silent restart of the modem. The modem is initialized based on the maximum value between the updated SVN and the original SVN information, ensuring the latest SVN takes effect and the SVN update is effective. The silent restart process does not affect the user experience. Updating the SVN retrieval interface of the client's telephony service component and updating the SVN display through this interface enables the client's telephony service component to quickly identify, synchronize, and display the new SVN, completing the update process loop and ensuring the real-time version information on the user side. Thus, the entire solution only requires restarting the modem without restarting the entire client machine. This allows for efficient, accurate, and low-power SVN updates while preserving the normal operation of other client functions, avoiding user experience interruptions caused by a full machine restart and optimizing the user experience. Attached Figure Description

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

[0017] Figure 1 This is a schematic diagram illustrating the steps of a software version number update method provided in an embodiment of this application; Figure 2 This is a schematic diagram of the architecture of a software version number update method provided in an embodiment of this application; Figure 3 This is a flowchart illustrating a software version number update method provided in an embodiment of this application; Figure 4 This is a schematic diagram of the structure of a software version number update device provided in an embodiment of this application; Figure 5This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0018] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0019] To facilitate understanding, some terms used in this application will be explained first.

[0020] SVN is a field used to identify the software version on a client device. It can be used to identify the software iteration status, distinguish version differences, and is a key identifier for devices to recognize software updates and ensure version consistency. Updating the SVN allows the client to accurately display the current software version number, avoiding version information errors. Accurate SVN helps users quickly locate device software problems and track version iterations.

[0021] The online customization platform is a visual operation platform within the Configuration over the Air (COTA) solution, providing users with a means to customize, edit, and configure SVN. The platform compiles customized SVN data into a standard configuration file and pushes it to the data center for client download. After the SVN update is complete, the data can be saved back to the code repository. COTA is a complete cloud-to-device technical solution for SVN updates on Android terminals. This solution enables cloud-based online customization of SVN, remote push updates, and updates without terminal restart. It also collects, transmits, and visualizes the update status, replacing traditional FOTA for efficient and independent SVN updates.

[0022] The data center is a service node for storing and distributing SVN configuration files in the cloud. It serves as a data transfer station between the cloud and clients, connecting the SVN configuration process from customization to client download. It can receive SVN data pushed by the online customization platform and provide SVN download interfaces to external users.

[0023] A modem is a module in an Android device responsible for processing communication signals and handling data transmission between the device and the communication network.

[0024] Telephony is a core component of Android devices that handles telephone and mobile network-related functions. Developers can use it to interact with the device's telecommunications services and enhance application functionality.

[0025] The OEM configuration (Oembin) partition is a permanent storage partition at the bottom layer of the Android device. The data in this partition will not be lost due to terminal restart or temporary system operations. When the client boots up, the system can read SVN data from this partition and generate read-only attributes, providing a stable version number source for components such as the Modem.

[0026] In one embodiment, such as Figure 1 As shown, a software version number update method is provided. Although the logical order is illustrated in the step diagram, in some cases, the steps shown or described can be performed in a different order than that shown in the diagram. Specifically, this software version number update method can be applied to a client, which may include an application layer, a system layer, and a lower layer, such as... Figure 2 As shown, the system layer may include Telephony and dynamically customized components, while the bottom layer may include Modem and Non-Volatile Memory (NVRAM), which may include permanent storage partitions.

[0027] The client can be one or more of the following: smart TVs, smart air conditioners, smart refrigerators, smartphones, tablets, laptops, desktop computers, and in-vehicle computers. These will be described in detail below. It should be noted that the order of description of the following embodiments is not intended to limit the priority of the embodiments.

[0028] according to Figure 1 The software version number update method shown includes at least steps S110 to S150, which are described in detail below: In step S110, upon detecting a software version number SVN update in the data center, the updated SVN configuration file is downloaded, and an SVN configuration request is initiated through the system component interface. This SVN configuration file is configured and compiled by the online customization platform and then pushed to the data center.

[0029] The online customization platform provides online visual customization capabilities for SVN data, supporting various SVN data customization needs. Configuration personnel can perform visual customization of SVN data based on the online platform, including but not limited to modification, editing, and configuration. The online customization platform can then compile the customized SVN data into an SVN configuration file through a compilation pipeline. This SVN configuration file, obtained by the online customization platform through the compilation pipeline, serves as a standardized carrier for transmitting SVN update data to clients. This SVN configuration file can be an svn.xml file.

[0030] In this way, configuration personnel can easily complete the customization operation to meet various SVN customization needs. The online customization platform will automatically compile the customized SVN data into a configuration file, which can realize the standardization and automation of SVN customization and compilation, and greatly improve the efficiency of SVN configuration.

[0031] After compiling the SVN configuration file, the online customization platform can push the SVN configuration file to the data center, where it can store the file. Clients can periodically check the data center for SVN updates to the software version number according to a preset time interval.

[0032] In one embodiment, the client can periodically poll the data center based on the SVN download interface provided by the data center to determine whether there are SVN updates in the data center.

[0033] The SVN download interface is a service interface provided by the data center to clients for obtaining SVN configuration files. It serves as the channel for clients to download SVN-related data from the data center. Clients can continuously send polling requests to the data center according to a preset system time period using the SVN download interface. This polling request is used to detect whether there are SVN updates in the data center. During each poll, data interaction can be performed with the data center through the SVN download interface to verify whether the data center stores the latest SVN configuration file, configured and compiled by the online customization platform, to determine whether an updatable SVN exists in the data center.

[0034] In this way, SVN update detection can be automatically achieved without manual intervention; polling based on the SVN download interface has the advantages of efficient and targeted data interaction, which can improve the timeliness of SVN updates.

[0035] When an SVN update is detected within the data center, the client can obtain the updated SVN configuration file through the data center's SVN download interface. After successfully downloading the SVN configuration file, the client can initiate an SVN settings request through the client's built-in system component interface to trigger the client-side SVN update process. The SVN settings request is a client-initiated operation request used to trigger the entire process of SVN parsing, verification, storage, and activation on the client side.

[0036] In step S120, in response to the SVN setup request, the SVN configuration file is parsed to obtain the SVN, and the validity of the SVN is verified.

[0037] like Figure 2As shown, the dynamic customization component at the client system layer can perform SVN verification after receiving an SVN settings request from the client application layer. The dynamic customization component can parse the downloaded SVN configuration file, extract the specific SVN values, and verify the legality and validity of the SVN according to preset verification rules, ensuring that the SVN conforms to the client device's version number specifications and update requirements. These preset verification rules may include SVN format rules and value ranges.

[0038] In step S130, the verified SVN is stored to the underlying permanent storage partition, and SVN system properties are set to trigger a silent modem restart.

[0039] Validated SVN entries can be stored in a persistent storage partition on the client device. This persistent storage partition ensures long-term data preservation and prevents data loss due to temporary device restarts, power outages, or other unforeseen circumstances. This persistent storage can be an Oembin partition, a dedicated partition for storing binary format device configuration data.

[0040] After SVN storage is complete, dynamically customized components can set the client's SVN system properties, triggering property change events. SVN system properties are the core basis for various client components (such as Modem and Telephony) to obtain SVN information; changes to SVN system properties can drive the client to complete SVN updates. SVN system property change events can directly drive the client's modem to perform a silent reboot operation, and this reboot process is imperceptible and will not affect the user's normal use of the client.

[0041] In step S140, after the modem is silently restarted, the modem is initialized based on the SVN system attributes and the maximum value between the SVN information in the permanent storage partition and the original local SVN information.

[0042] After a silent reboot, the modem enters the initialization process. The modem reads the updated SVN system properties from the client, retrieves the latest SVN information stored in the permanent storage partition and the existing local SVN information, compares the latest SVN information in the permanent storage partition with the existing local SVN information, determines the maximum value between the latest and existing SVN as the final SVN, and performs its own SVN initialization based on the final SVN, ensuring that the modem's SVN remains synchronized with the latest SVN. A larger SVN value indicates a newer version.

[0043] By determining the maximum value between the latest SVN and the original SVN as the final SVN, it can be ensured that the client always uses the latest and highest-level SVN, avoiding the client's fallback to the old SVN due to data synchronization anomalies, push delays and other issues, thus guaranteeing SVN upgrades.

[0044] In step S150, the SVN retrieval interface of the client's telephony service component is updated, and the SVN display is updated through the SVN retrieval interface.

[0045] After the modem completes SVN initialization, the client's Telephony component can update the SVN retrieval interface, refresh the SVN data reading logic of the interface, and enable the SVN retrieval interface to retrieve the updated SVN data within the client.

[0046] The client's various display interfaces can read and display the latest SVN information through the updated SVN retrieval interface, allowing users to intuitively see the latest SVN information on the client.

[0047] Using the technical solution of this application embodiment, the online customization platform can configure and compile SVN configuration files and push them to the data center. When the client detects an SVN update in the data center, it can automatically download the updated SVN configuration file and configure SVN. Users only need to configure SVN through the online customization platform to achieve proactive SVN update triggering, without requiring extensive manpower. Parsing the SVN configuration file to obtain the SVN and verifying its validity can filter invalid or abnormal SVNs, improving the accuracy and reliability of SVN updates. The verified SVN is stored in the underlying permanent storage partition, and SVN system properties are set to trigger a silent modem restart. Based on the SVN system properties and the maximum value between the SVN information in the permanent storage partition and the original local SVN information, the modem is initialized, enabling... The current SVN persistence ensures that the SVN can be read from the permanent storage partition even after a silent modem restart. The modem is initialized based on the maximum value between the updated SVN and the original SVN information, ensuring the latest SVN takes effect and the SVN update is effective. The silent restart process does not affect the user experience. Updating the SVN retrieval interface of the client's telephony service component and updating the SVN display through this interface enables the client's telephony service component to quickly identify, synchronize, and display the new SVN, completing the update process loop and ensuring the real-time version information on the user side. Thus, the entire solution only requires a modem restart without restarting the entire client machine. This allows for efficient, accurate, and low-power SVN updates while preserving the normal operation of other client functions, avoiding user experience interruptions caused by a full machine restart and optimizing the user experience.

[0048] Based on the above technical solution, as an example, storing the verified SVN to the underlying permanent storage partition and setting SVN system properties to trigger a silent restart of the modem may include: storing the verified SVN to the permanent storage partition and setting SVN system properties; the client's telephony service component listening for changes in SVN system properties; and triggering a silent restart of the modem after the telephony service component detects a change in SVN system properties.

[0049] Validated SVN entries can be stored in the client device's underlying permanent storage partition, preventing data loss due to temporary device restarts, power outages, or other unforeseen circumstances. After SVN storage is complete, the dynamically customized component can set the client's SVN system properties, trigger property change events, and modify the SVN property values ​​to match the specified SVN entry, thus completing SVN synchronization at the property level.

[0050] The client's built-in telephony service component continuously monitors for changes to SVN system properties. This monitoring process can run silently in the background. When the telephony service component detects a change in an SVN system property, it can send a restart command to the modem, initiating a silent restart process. This silent restart can be completed in the client's background, without interrupting ongoing calls, application usage, or causing any issues such as a black screen or interface lag; the user is completely unaware of the change.

[0051] A silent restart of the modem is a necessary step for the SVN version number to take effect at the hardware level. By silently restarting the modem, the modem can reread the latest SVN, ensuring that the SVN of the hardware module is consistent with the SVN stored at the system level, and ultimately achieving a unified update of the SVN version number for all client components.

[0052] The technical solution adopted in this application embodiment, the SVN system attribute setting and monitoring mechanism, can realize the real-time capture of attribute changes, thereby triggering a silent restart of the modem, so that SVN takes effect imperceptibly at the hardware level, which not only does not interrupt user operation and improves experience, but also achieves SVN version consistency between hardware and system levels, ensuring update effectiveness.

[0053] Based on the above technical solution, as an example, the client's underlying layer can read SVN from the permanent storage partition and generate system read-only attributes when it boots up; the modem can read the system read-only attributes to obtain SVN information during initialization.

[0054] During the client device boot process, the client's underlying driver and system initialization module can preferentially read the stored and verified SVN from the permanent storage partition. This permanent storage partition is a stable storage medium that is not lost even when power is off, ensuring that the latest and valid SVN is obtained every time the device boots. After reading the SVN, the system can generate a corresponding system read-only attribute based on the read SVN. System read-only attributes are system-level attributes in the Android system that can only be set during boot or specific initialization phases and cannot be modified by ordinary applications or processes during runtime (such as ro.boot.csvn). They can be used to store core device configuration and version information, ensuring data security and consistency. Generating system read-only attributes corresponding to SVN ensures that SVN version information is secure, stable, and tamper-proof.

[0055] During the terminal system startup and communication module loading phase, the modem can enter initialization. In this initialization, the modem can directly read the aforementioned system read-only attributes, quickly obtaining standard, unified SVN information without needing to access the underlying storage partition again, thus reducing system overhead and time consumption caused by frequent reads. By pre-generating at boot and directly reading during initialization, the consistency and reliability of SVN information are ensured, improving modem initialization efficiency and keeping the client communication module synchronized with the system version information.

[0056] By adopting the technical solution of this application embodiment, the SVN is read from the permanent storage partition and a system read-only attribute is generated during boot. This can ensure that the SVN data is stable, not lost, and not tampered with, and can provide a unified and reliable version base for the system and hardware. The modem reads the system read-only attribute directly during initialization, which can save the overhead of repeatedly accessing the underlying partition, improve boot efficiency, and at the same time ensure that the SVN information of the modem and the system is consistent, avoid version confusion, and ensure stable and reliable terminal communication and version management.

[0057] Based on the above technical solution, as an example, the software version number update method may include: collecting status information during the SVN update process and uploading it to the data center so that the data center can display the SVN update status through a Kanban board.

[0058] During the SVN update process, the client can collect status information at each stage of the update in real time, ensuring that the status of each operation is traceable and monitorable. The collected status information can include the entire update process, including SVN configuration file download status (successful download, failed download, download progress), SVN validity verification results (verification passed, verification failed, and reason for failure), SVN write status to the permanent storage partition, SVN system property settings, and key information such as modem silent restart status and the final effective status of terminal SVN. The client can organize the collected status information and upload it to the data center periodically or in real time, according to the data center's pre-defined interface specifications.

[0059] After receiving status data, the data center can summarize and parse the various status information, transforming fragmented status information into visualized data. The data center can use dashboards to intuitively display the SVN update status of clients, which can include client identifier, update progress, current status, update time, and anomaly information, making it convenient for operations and maintenance personnel to monitor the SVN update status of clients in real time, quickly troubleshoot anomalies, and grasp the overall update progress.

[0060] By adopting the technical solution of this application embodiment, the update process can be monitored and traced in real time by collecting and uploading the status information of SVN updates, which facilitates the timely detection of abnormal problems. The status information is displayed in a Kanban format, which allows users to intuitively grasp the overall update progress and results of the client, greatly improving version management efficiency, reducing operation and maintenance costs, and ensuring the implementation of SVN online customization solutions.

[0061] Based on the above technical solution, as an example, this online customization platform supports returning SVN data to the code repository after SVN release.

[0062] The online customization platform has comprehensive SVN data lifecycle management capabilities. After completing the entire process of SVN customization, compilation, push, and client update, this version of SVN can be released (i.e., the client is updated or the preset release conditions are met).

[0063] After releasing SVN, the online customization platform can automatically trigger a data regression mechanism. The platform can organize user-customized SVN data, including complete configuration parameters, version information, and compilation records, according to the code repository's storage standards. The platform can then connect to the code repository via a pre-defined interface, automatically synchronizing the organized SVN data to the repository. This achieves closed-loop management of SVN data from customization and distribution to archiving, providing reliable data support for subsequent SVN version iterations, traceability, and reuse.

[0064] By adopting the technical solution of this application embodiment, SVN data is returned to the code repository, which can realize the unified archiving and version retention of SVN configuration information, ensure data traceability, meet the requirements of standardized configuration management, and form a complete closed loop of online customization, compilation, release and archiving. This avoids configuration loss or version chaos, facilitates subsequent problem location, version backtracking and iterative reuse, and can also improve the security, standardization and maintainability of configuration management.

[0065] Figure 3 This is a flowchart illustrating a software version number update method provided in an embodiment of this application; see reference. Figure 3 The COTA application layer can download the SVN configuration file from the data center. After downloading, the system component layer can sequentially perform the decompression, parsing, and loading operations of the SVN configuration file, and accurately write the verified SVN data to the Oembin partition. The system component can judge the parsing result; if parsing fails, a polling re-download mechanism is triggered to ensure the integrity of the configuration file; if parsing succeeds, the installation interface can be loaded.

[0066] After the client restarts, the system can read SVN from the Oembin partition and generate the system read-only attribute of SVN (ro.boot.csvn).

[0067] The Telephony component can listen for changes to SVN system properties. Upon detecting a change in an SVN system property value, it can send a command to the modem, triggering a silent restart. After restarting, the modem can enter the initialization phase, directly reading the updated SVN system properties at the system layer to obtain the latest version number information. Based on this value, it completes the initialization of its own modules, achieving version consistency between the hardware and system layers.

[0068] After the modem completes SVN initialization, the Telephony component can update its SVN retrieval interface to ensure it can read the latest SVN data. Subsequently, the Settings module can use this updated SVN retrieval interface to obtain the latest SVN data and display it on the interface, completing the visual presentation on the client side.

[0069] The entire process enables seamless integration of cloud customization, client download, underlying storage, hardware activation, and interface display. This ensures accurate synchronization of SVN version numbers and enables users to update without being noticing through a silent restart mechanism, thereby improving the efficiency and convenience of terminal configuration management.

[0070] To facilitate better implementation of the software version number update method of this application, this application also provides a software version number update apparatus based on the above-described software version number update method. The meanings of the terms used are the same as in the software version number update method described above, and specific implementation details can be found in the descriptions of the method embodiments.

[0071] Please see Figure 4 , Figure 4 This is a schematic diagram of the structure of the software version number update device provided in the embodiments of this application, wherein the software version number update device includes: The update download module 401 is used to download the updated SVN configuration file and initiate an SVN configuration request through the system component interface when an SVN update is detected in the data center; wherein, the SVN configuration file is configured and compiled by the online customization platform and then pushed to the data center; The parsing and verification module 402 is used to respond to the SVN setting request, parse the SVN configuration file to obtain the SVN, and verify the validity of the SVN; SVN storage module 403 is used to store the verified SVN to the underlying permanent storage partition and set SVN system properties to trigger a silent restart of the modem; The initialization module 404 is used to initialize the modem after the modem is silently restarted, based on the SVN system attributes and the maximum value between the SVN information in the permanent storage partition and the original local SVN information. The update display module 405 is used to update the SVN retrieval interface of the client's telephony service component and update the SVN display through the SVN retrieval interface.

[0072] In one embodiment, the device further includes: The polling module is used to periodically poll the data center based on the SVN download interface provided by the data center to determine whether there are SVN updates in the data center.

[0073] In one embodiment, the SVN storage module 403 is specifically used to perform: Store the verified SVN to the permanent storage partition and set the SVN system properties; The client's telephony service component listens for change events of the SVN system properties; The telephony service component triggers a silent restart of the modem after detecting a change in the SVN system properties.

[0074] In one embodiment, the device further includes: A read-only attribute generation module is used by the client's underlying system to read the SVN from the permanent storage partition and generate system read-only attributes when the client boots up. The attribute reading module is used to control the modem to read the system read-only attributes to obtain SVN information during initialization.

[0075] In one embodiment, the device further includes: The status upload module collects status information during the SVN update process and uploads it to the data center so that the data center can display the SVN update status through a Kanban board.

[0076] In one embodiment, the online customization platform provides online visual customization capabilities for SVN data; The SVN configuration file is obtained by the online customization platform through a compilation pipeline that compiles the customized SVN data.

[0077] In one embodiment, the online customization platform supports the regression of SVN data into the code repository after SVN release.

[0078] Using the technical solution of this application embodiment, the online customization platform can configure and compile SVN configuration files and push them to the data center. When the client detects an SVN update in the data center, it can automatically download the updated SVN configuration file and configure SVN. Users only need to configure SVN through the online customization platform to achieve proactive SVN update triggering, without requiring extensive manpower. Parsing the SVN configuration file to obtain the SVN and verifying its validity can filter invalid or abnormal SVNs, improving the accuracy and reliability of SVN updates. The verified SVN is stored in the underlying permanent storage partition, and SVN system properties are set to trigger a silent modem restart. Based on the SVN system properties and the maximum value between the SVN information in the permanent storage partition and the original local SVN information, the modem is initialized, enabling... The current SVN persistence ensures that the SVN can be read from the permanent storage partition even after a silent modem restart. The modem is initialized based on the maximum value between the updated SVN and the original SVN information, ensuring the latest SVN takes effect and the SVN update is effective. The silent restart process does not affect the user experience. Updating the SVN retrieval interface of the client's telephony service component and updating the SVN display through this interface enables the client's telephony service component to quickly identify, synchronize, and display the new SVN, completing the update process loop and ensuring the real-time version information on the user side. Thus, the entire solution only requires a modem restart without restarting the entire client machine. This allows for efficient, accurate, and low-power SVN updates while preserving the normal operation of other client functions, avoiding user experience interruptions caused by a full machine restart and optimizing the user experience.

[0079] Specific limitations regarding the software version number update device can be found in the limitations of the software version number update method described above, and will not be repeated here. Each module in the aforementioned software version number update device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in the computer device in hardware form, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0080] In addition, this application also provides an electronic device, such as Figure 5 As shown, it illustrates the structural diagram of the electronic device involved in this application, specifically: The electronic device may include components such as a processor 501 with one or more processing cores and a memory 502 with one or more computer-readable storage media. Those skilled in the art will understand that... Figure 5The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein: The processor 501 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines. By running or executing software programs and / or modules stored in the memory 502, and by calling data stored in the memory 502, it performs various functions and processes data, thereby providing overall monitoring of the electronic device. Optionally, the processor 501 may include one or more processing cores; preferably, the processor 501 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 501.

[0081] The memory 502 can be used to store software programs and modules. The processor 501 executes various functional applications and data processing by running the software programs and modules stored in the memory 502. The memory 502 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 502 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 502 may also include a memory controller to provide the processor 501 with access to the memory 502.

[0082] In one embodiment, the electronic device further includes a power supply 503 that supplies power to the various components. Preferably, the power supply 503 can be logically connected to the processor 501 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 503 may also include one or more DC or AC power supplies, recharging systems, power equipment debugging circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0083] In one embodiment, the electronic device may further include an input unit 504, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0084] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 501 in the electronic device loads the executable files corresponding to the processes of one or more applications into the memory 502 according to the following instructions, and the processor 501 runs the applications stored in the memory 502, thereby implementing the steps in any of the software version number update methods provided in the embodiments of this application.

[0085] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the electronic device to which the present application is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements.

[0086] In one embodiment, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the methods described in any embodiment of this application.

[0087] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method described in any embodiment of this application.

[0088] In some embodiments, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the methods described in any embodiment of this application.

[0089] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0090] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0091] Therefore, this application provides a computer-readable storage medium storing a computer program that can be loaded by a processor to perform the steps in any of the software version number update methods provided in this application.

[0092] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0093] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0094] Since the instructions stored in the computer-readable storage medium can execute the steps in any of the software version number update methods provided in this application, the beneficial effects that any of the software version number update methods provided in this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.

[0095] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only 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 "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device 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 terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0096] The above provides a detailed description of a software version number update method, apparatus, electronic device, and computer-readable storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, those skilled in the art will recognize that there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A method for updating software version numbers, characterized in that, Applied to a client, the method includes: When an SVN update to the software version number is detected in the data center, the updated SVN configuration file is downloaded and an SVN configuration request is initiated through the system component interface; wherein, the SVN configuration file is configured and compiled by the online customization platform and then pushed to the data center; In response to the SVN setup request, the SVN configuration file is parsed to obtain the SVN, and the validity of the SVN is verified. The verified SVN is stored in the underlying permanent storage partition, and SVN system properties are set to trigger a silent modem restart; After the modem silently restarts, the modem is initialized based on the SVN system attributes and the maximum value between the SVN information in the permanent storage partition and the original local SVN information. Update the SVN retrieval interface of the client's telephony service component, and update the SVN display through the SVN retrieval interface.

2. The method according to claim 1, characterized in that, The method further includes: Based on the SVN download interface provided by the data center, the data center is periodically polled to determine whether there are SVN updates in the data center.

3. The method according to claim 1, characterized in that, The step of storing the verified SVN to the underlying permanent storage partition and setting SVN system properties to trigger a silent modem restart includes: Store the verified SVN to the permanent storage partition and set the SVN system properties; The client's telephony service component listens for change events of the SVN system properties; The telephony service component triggers a silent restart of the modem after detecting a change in the SVN system properties.

4. The method according to claim 1, characterized in that, The method further includes: The underlying layer of the client reads the SVN from the permanent storage partition and generates a system read-only attribute when the system boots up; The modem reads the system's read-only attributes to obtain SVN information during initialization.

5. The method according to claim 1, characterized in that, The method further includes: Collect status information during the SVN update process and upload it to the data center so that the data center can display the SVN update status through a Kanban board.

6. The method according to claim 1, characterized in that, The online customization platform provides online, visual customization capabilities for SVN data. The SVN configuration file is obtained by the online customization platform through a compilation pipeline that compiles the customized SVN data.

7. The method according to claim 6, characterized in that, The online customization platform supports restoring the SVN data to the code repository after SVN release.

8. A software version number update device, characterized in that, Applied to a client, the device includes: The update download module is used to download the updated SVN configuration file and initiate an SVN configuration request through the system component interface when an SVN update is detected in the data center; wherein, the SVN configuration file is configured and compiled by the online customization platform and then pushed to the data center; The parsing and verification module is used to respond to the SVN setting request, parse the SVN configuration file to obtain the SVN, and verify the validity of the SVN; The SVN storage module is used to store the verified SVN to the underlying permanent storage partition and set SVN system properties to trigger a silent restart of the modem. An initialization module is used to initialize the modem after the modem has silently restarted, based on the SVN system attributes and the maximum value between the SVN information in the permanent storage partition and the original local SVN information. The update display module is used to update the SVN retrieval interface of the client's telephony service component, and update the SVN display through the SVN retrieval interface.

9. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps in the software version number update method as described in any one of claims 1 to 7.

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

Images