CN112732735A

CN112732735A - Data updating method, device, computer program product and storage medium

Info

Publication number: CN112732735A
Application number: CN202110007861.2A
Authority: CN
Inventors: 翟堃
Original assignee: Alibaba Group Holding Ltd
Current assignee: Alibaba Group Holding Ltd
Priority date: 2021-01-05
Filing date: 2021-01-05
Publication date: 2021-04-30

Abstract

The embodiment of the application provides a data updating method, data updating equipment, a computer program product and a storage medium. In the embodiment of the application, a plurality of data hot update modes can be provided for a data user to flexibly customize. When new data is generated, a target data hot updating mode customized by a data user can be obtained, and a related data hot switching process is executed according to configuration information of the target data hot updating mode, so that local data is switched into the new data, and the data hot updating is realized according to the data hot updating mode customized by the data user, so that the data user can customize the data updating mode individually, the flexibility of data updating is improved, and the requirements of different data users can be met.

Description

Data updating method, device, computer program product and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a data updating method, device, computer program product, and storage medium.

Background

With the development of internet technology and the popularization of intelligent terminals, more and more application software is widely installed and used. These application class software needs to run based on relevant data. For example, trip application software needs to implement functions such as navigation and map rendering based on map data.

In practical applications, related data may be updated periodically or aperiodically in order to improve service performance of application software. In the prior art, data updating can be performed only by adopting a single mode, the flexibility is poor, and the requirements of different data users cannot be met. Therefore, how to implement the autonomous customization of the update method by the data user becomes a technical problem to be solved urgently.

Disclosure of Invention

Aspects of the present application provide a map data updating method, device, computer program product, and storage medium, so as to implement personalized customization of data updating modes by a data using party, thereby improving flexibility of data updating.

The embodiment of the application provides a map data updating method, which is used for updating map data stored on a navigated object and comprises the following steps:

acquiring new map data;

acquiring the state of the navigated object;

and if the state of the navigated object meets the thermal update condition, updating the map data locally stored by the navigated object into the new map data.

The embodiment of the present application further provides a data updating method, including:

acquiring a target data hot updating mode customized by a data user;

acquiring new data;

and executing a flow related to data hot switching according to the configuration information of the target data hot updating mode so as to switch the local data into the new data.

An embodiment of the present application further provides a computer program product, including: a computer readable storage medium of computer instructions which, when executed by one or more processors, cause the one or more processors to perform the steps of the map data update and/or data update method described above.

An embodiment of the present application further provides a terminal device, including: a memory and a processor; the memory for storing a computer program;

the processor is coupled to the memory for executing the computer program for performing the steps of the above described map data updating and/or data updating method.

Embodiments of the present application also provide a computer-readable storage medium storing computer instructions, wherein the computer instructions, when executed by one or more processors, cause the one or more processors to perform the steps of the map data updating and/or data updating method described above.

In the embodiment of the application, a plurality of data hot update modes can be provided for a data user to flexibly customize. When new data is generated, a target data hot updating mode customized by a data user can be obtained, and a related data hot switching process is executed according to configuration information of the target data hot updating mode, so that local data is switched into the new data, and the data hot updating is realized according to the data hot updating mode customized by the data user, so that the data user can customize the data updating mode individually, the flexibility of data updating is improved, and the requirements of different data users can be met.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1a and fig. 1b are schematic structural diagrams of a data processing system according to an embodiment of the present application;

FIG. 1c is a schematic diagram of a data update process without authorization of a data consumer according to an embodiment of the present application;

FIGS. 1 d-1 h are schematic diagrams of several map data updating processes requiring authorization of a data user according to an embodiment of the present application;

fig. 1i is a schematic structural diagram of a map data system according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a data updating method according to an embodiment of the present application;

fig. 3a and fig. 3b are schematic flow charts of another data updating method provided in the embodiment of the present application;

fig. 4 is a schematic flowchart of a map data updating method according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In order to solve the above technical problem, in some embodiments of the present application, a plurality of data hot update modes may be provided for a data user to flexibly customize. When new data is generated, a target data hot updating mode customized by a data user can be obtained, and a related data hot switching process is executed according to configuration information of the target data hot updating mode, so that local data is switched into the new data, and the data hot updating is realized according to the data hot updating mode customized by the data user, so that the data user can customize the data updating mode individually, the flexibility of data updating is improved, and the requirements of different data users can be met.

The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.

It should be noted that: like reference numerals refer to like objects in the following figures and embodiments, and thus, once an object is defined in one figure or embodiment, further discussion thereof is not required in subsequent figures and embodiments.

Fig. 1a is a schematic structural diagram of a data processing system according to an embodiment of the present disclosure. As shown in fig. 1a, the system comprises: a data provider 11 and a data consumer 12.

In the present embodiment, the data provider 11 refers to a software functional module that can provide data. The function module can provide data, and can also request data from the data server 13 to update the data.

The data consumer 12 refers to a software function module that calls data for use, and the function module may also implement a specific function based on the called data.

The data provided by the data provider 11 and the data consumer 12 realize different functions based on the data, depending on the application. For example, for map applications, a data provider may provide map data, obtain new map data from a map service, update the map data, and so on. Accordingly, the data consumer 12 may perform positioning, navigation, routing, etc. functions based on the map data. Optionally, the data user 12 may be a car machine system, or may be travel application software integrated in the car machine device.

Alternatively, the data provider 11 and the data consumer 12 may be different functional modules in one software product, and may also be functional modules in different software products. The Software product may be a client, an application program (APP), or a Software Development Kit (SDK).

In actual practice, as shown in fig. 1b, the data provider 11 may request data from the data server 13 and may update the locally stored data to the newly requested data (defined as new data).

In the present embodiment, the data provider 11 supports a plurality of data hot update methods. Wherein, a plurality means 2 or more. Optionally, the plurality of data hot update modes may be: the method does not need at least two modes of a data user authorization mode, a data user synchronous authorization updating (synchronous type for short), a data user asynchronous authorization mode (including event type asynchronous and/or periodic type asynchronous), a mode of combining the data user synchronous and periodic type asynchronous authorization modes, and a mode of combining the data user synchronous and event type asynchronous authorization modes.

The data user 12 can autonomously customize the data hot-update mode according to the application requirement thereof, and provide the customization information for the data hot-update mode to the data provider 11. The data provider 11 can acquire customized information for the data hot update mode, and according to the customized information, determine a target data hot update mode from multiple supported data hot update modes; and then, setting the data hot update mode of the data as the target data hot update mode. Optionally, the data provider 11 may obtain configuration information corresponding to a target data hot update mode; and setting the data hot updating mode of the data as the target data hot updating mode according to the configuration information corresponding to the target data hot updating mode. The configuration information corresponding to the target data hot update mode may include: configuration information of a target data hot update mode, and the like.

The target data are updated in different hot updating modes, and the corresponding configuration information is different. For example, for a data consumer-free authorization approach, the configuration information may include: whether flag bit information authorized by a data user is required, whether the data user supports data hot-update, and the like. For data consumer synchronization authorization, the configuration information may include: the method comprises the steps of judging whether flag bit information authorized by a data user is needed, identifying a data hot update mode, judging whether the data user supports data hot update, and the like.

For the data usage-based event-based asynchronous authorization scheme, the configuration information may include: flag bit information of whether the data user side is authorized, identification of a data hot update mode, timeout time (marked as first timeout T1) of update authorization, whether the data user side supports data hot update and the like. Wherein, the timeout time of the update authorization means: the data provider starts timing from acquiring new data until receiving a time threshold allowed by an updating authorization notice of a data user; if the data provider does not receive the authorization success notice after acquiring new data and the timeout time is reached, the data provider does not execute data updating; accordingly; and if the data provider starts to count time from acquiring new data and receives an update success notice within the overtime time, executing data update.

For the data usage-based periodic asynchronous authorization scheme, the configuration information may include: flag bit information of whether data user authorization is needed, identification of data hot update mode and timeout time of update authorization

(noted as second timeout T2), a threshold N of the number of times an authorization success notification is received within the second timeout T2, whether the data consumer supports data hot updates, etc. If the data provider 11 receives the authorization success notification N times within the second timeout period T2, data update is performed; if the data provider 11 does not receive the authorization success notification N times within the second timeout period T2, no data update is performed. Wherein N is a positive integer. Alternatively, N ≧ 2.

For the data hot update mode combining the synchronous and periodic asynchronous authorization of the data user, the configuration information comprises the synchronous configuration information of the data user and the periodic asynchronous authorization configuration information; for the data hot update mode combining the synchronous and event asynchronous authorization of the data user, the configuration information may include the configuration information of the synchronous and event asynchronous authorization of the data user.

Further, for the data consumer 12, when the data provider 11 acquires new data, it may acquire a target data hot update mode customized by the data consumer 12; and executing a flow related to data hot switching according to the configuration information of the target data hot updating mode so as to switch the locally stored data into new data.

In the data processing system provided by this embodiment, the data provider can provide a data hot-update mode for a plurality of data, so that the data user can flexibly customize the data. The data provider can respond to the customization information aiming at the data hot updating mode, determine the selected target data hot updating mode from the supported data hot updating modes, and set the data hot updating mode of the data as the target data hot updating mode; for a data user, a data provider can be authorized to update data according to a target data hot update mode, so that the data user can customize the data hot update mode, the flexibility of data update is improved, and the requirements of different data users can be met.

In this embodiment, the specific implementation of the data consumer 12 customizing the data hot update mode is not limited. Several alternative embodiments are exemplified below.

Alternative embodiment 1: data consumer 12 may customize the data hot-update approach via a configuration file. Wherein the configuration file comprises: and hot updating the configuration information of the mode according to the selected data. For the description of the configuration information of the data hot update method, reference may be made to the relevant contents of the above embodiments, and details are not described herein again. In optional embodiment 1, the configuration information of the data hot update method includes: and the identification of the selected data hot updating mode.

Further, the data provider 11 may provide a configuration file for a data hot update method (simply referred to as a hot update configuration file) to the data consumer 12. The configuration file includes: and the identification of the selected data hot updating mode. The data provider 11 may receive the hot update profile provided by the data consumer as the customization information. Further, the data provider 11 may obtain configuration information for the data hot-update mode from the hot-update configuration file; and determining a target updating mode according to the configuration information of the hot updating mode. Optionally, the configuration information of the hot update configuration file includes an identification of a customized data hot update mode. Accordingly, the data provider 11 can determine, as the target data hot update method, a data hot update method corresponding to the identification of the data hot update method customized by the data consumer 12 from among the plurality of data hot update methods.

Further, the data provider 11 may also parse a target data hot update mode from the configuration file; and setting the data hot updating mode of the data as the target data hot updating mode according to the configuration information corresponding to the target data hot updating mode.

Alternative embodiment 2: the data provider 11 may provide an Application Program Interface (API) for a variety of hot updates of data. Data consumer 12 may customize the data hot update style through an API. The data provider 11 may respond to the calling operation of the data user for the application program interfaces of the multiple data hot update modes, and take the data hot update mode corresponding to the called application program interface as the target data hot update mode.

Further, the data provider 11 may also obtain configuration information corresponding to the called application program interface, as configuration information corresponding to the target data hot update mode; and setting the data hot updating mode as the target data hot updating mode according to the configuration information corresponding to the target data hot updating mode.

Optional embodiment 3: the data provider 11 may provide the data consumer 12 with a human-machine interface that may present an identification of a plurality of data hot-update modes. A developer of the data user 12 can customize a data hot update mode through the man-machine interaction interface.

The identity of the various data hot-update modes may be exposed to the data provider 11. The developer of the data user 12 can touch the identifier of the selected data hot update mode to customize the data hot update mode. Accordingly, for the data provider 12, in response to the touch operation for the identification of the data hot update mode, the data hot update mode selected by the touch operation may be the target data hot update mode.

The data provider 11 may also preset a corresponding relationship between the identifier of the data hot update mode and the configuration information, so that the data provider 11 may obtain the configuration information corresponding to the target data hot update mode according to the identifier of the target data hot update mode and the preset corresponding relationship between the identifier of the data hot update mode and the configuration information. That is, the data provider 11 may match the correspondence between the identifier of the target data hot update mode and the preset identifier of the data hot update mode and the configuration information to obtain the configuration information corresponding to the target data hot update mode.

Further, the data provider 11 may set the data hot update mode of the data to the target data hot update mode according to the configuration information corresponding to the target data hot update mode.

The process of customizing the data hot update mode by the data user 12 provided in the above embodiment may be completed before the terminal where the data user 12 is located is shipped from a factory, or may be performed by a developer of the data user 12 through remote customization of the data hot update mode after shipment from the factory. For example, a developer may remotely customize the data hot-update style of data consumer 12 via OTA techniques.

For the terminal which is customized by the hot update mode of the customized data, in the actual use process, the data update data can be executed according to the customized hot update mode of the target data. The following is an exemplary description of the data updating process in the actual usage process.

In the actual use process, the data provider 11 may obtain the configuration information of the target hot update mode, and determine whether the target hot update mode needs the authorization of the data user; if the authorization of the data user is needed, the data user interacts with the data user according to the authorization mode included by the configuration information to obtain the hot switching authorization of the data; and executing the flow related to the data hot switching under the condition of obtaining the data hot switching authorization; if no data consumer authorization is required, the flow associated with data hot-handoff may be performed directly, as shown in FIG. 1 c.

Optionally, the data provider 11 may obtain flag bit information indicating whether authorization of the data user is required from the target data hot update mode; and if the flag bit information indicates that the data user is required to be authorized, determining to interact with the data user according to an authorization mode included by the configuration information so as to obtain data hot-switch authorization. Accordingly, if the flag bit information indicates that no authorization of the data user is required, the procedure related to the data hot handover is directly performed.

Alternatively, before the data provider 11 determines whether the target data hot-update method requires authorization of the data consumer, it may also determine whether the data consumer 12 supports hot-update according to configuration information of the target data hot-update method. If the judgment result is yes, executing the operation of judging whether the target data hot updating mode needs the authorization of the data user; if the judgment result is no, the data hot switching is not carried out.

For a target data hot update mode requiring authorization of a data user, authorization modes included in configuration information are different, and interaction modes of a data provider and the data user are different. The following is an exemplary description with reference to specific authorization methods.

The above interaction process is exemplified below in connection with several ways that require map data consumer update authorization.

Authorization mode 1: for the synchronous mode, as shown in fig. 1d, in the authorization mode 1, the data provider 11 may obtain configuration information of a target data hot update mode; the configuration information includes a flag bit whether the data consumer supports hot updates. Judging whether the flag bit is in an enabling state; if the judgment result is yes, the data user 12 is determined to support hot update, and a hot switch authorization request is sent to the data user 12 through the synchronization API. Accordingly, if the data consumer 12 determines that the data provider 11 can perform data hot-swap, an authorization success notification may be provided to the data provider 11 through the synchronization API; if the data consumer 12 determines that the data provider 11 cannot perform a data hot-swap, an authorization failure notification or no authorization success notification may be provided to the data provider 11 through the synchronization API.

Accordingly, the data provider 11 can obtain an authorization result notification returned by the data provider 12 through the synchronization API. And if the authorization result is informed that the authorization is successful, determining to acquire data hot-switch authorization. Correspondingly, if the authorization result notification is an authorization failure notification or the authorization result notification is not received, it is determined that the data hot-switch authorization is not obtained, and the relevant flow of executing the data hot-switch is abandoned.

Authorization mode 2: for the event asynchronous authorization mode, as shown in fig. 1e, in the authorization mode 2, the data provider 11 may also determine whether the data consumer 12 supports hot update, and for the description of the process, reference may be made to the related contents in the authorization mode 1, which is not described herein again. Further, in the case where the data consumer 12 supports hot-update, the data provider 11 may send a hot-switch authorization request to the data consumer 12 through the asynchronous API. Accordingly, the data consumer 12 receives the hot handover authorization request. If the data consumer 12 determines that the data provider 11 can perform a data hot-swap, an authorization success notification may be provided to the data provider 11 through the synchronization API; if the data consumer 12 determines that the data provider 11 cannot perform a data hot-swap, an authorization failure notification or no authorization success notification may be provided to the data provider 11 through the synchronization API.

Accordingly, for the data provider 11, when acquiring new data starts, if an authorization result notification returned by the data user is received within the preset first duration T1 (i.e., the first timeout duration T1), and the authorization result notification is successful, the data hot-swap authorization may be acquired.

If the time length from the start of obtaining new data to the time length exceeding or reaching the first time length T1 does not receive the authorization result notification sent by the data provider 11 or the received authorization result notification is an authorization failure, the data hot switch is cancelled, that is, the operation of switching the local data to new data is not executed.

Authorization mode 3: periodic asynchronous mode. As shown in fig. 1f, in the authorization method 3, the data provider 11 may also determine whether the data consumer 12 supports hot update, and for the description of the process, reference may be made to the related contents in the authorization method 1, which is not described herein again. Further, in the case where the data consumer 12 supports hot-update, the data provider 11 may send a hot-switch authorization request to the data consumer 12 through the asynchronous API.

If the data consumer 12 determines that the data provider 11 can perform a data hot-swap, an authorization success notification can be periodically provided to the data provider 11 through the synchronization API; if the data consumer 12 determines that the data provider 11 cannot perform a data hot-swap, an authorization failure notification or no authorization success notification may be periodically provided to the data provider 11 through the synchronization API.

For the data provider 11, timing may be started when new data is acquired, and the number of times of receiving the authorization result notification within the timing duration may be counted; if N authorization result notifications are received within the preset second duration (i.e., the second timeout time) T2, and the N authorization result notifications are successful in authorization, the data hot-handover authorization is obtained. Where N is a threshold (lower limit) of the number of times the update authorization notification is received within the second timeout period T2. And if authorization failure exists in the N-time authorization result notifications or the N-time authorization result notifications are not received, canceling the hot switching of the data, namely not executing the operation of switching the local data into new data.

Authorization mode 4: synchronous and periodic asynchronous grants are combined. As shown in fig. 1g, in the authorization method 4, the data provider 11 may also determine whether the data consumer 12 supports hot update, and for the description of the process, reference may be made to the related contents in the authorization method 1, which is not described herein again. Further, in the case that the data consumer 12 supports hot update, the interaction between the data provider 11 and the data consumer 12 can be referred to as the authorization method 1 and the authorization method 3. In this embodiment, the synchronous grant and the periodic asynchronous grant of the data user can be executed in parallel or sequentially. When the two are executed in sequence, the execution sequence of the synchronous authorization and the periodic asynchronous authorization of the data user is not limited. Fig. 1g illustrates the synchronous grant mode first and the periodic asynchronous grant mode later, but the present invention is not limited thereto.

Alternatively, in the authorization manner 4, the data provider 11 may obtain the data hot-handover authorization as long as there is an authorization manner that satisfies the authorization condition between the data user synchronous authorization and the periodic asynchronous authorization; or, the data provider 11 may obtain the data hot-handover authorization under the condition that both the data user synchronous authorization and the periodic asynchronous authorization are satisfied; and so on. If the synchronous authorization mode is executed first and then the periodic asynchronous authorization mode is executed, the data provider 11 may send a hot-switch authorization request to the data consumer 12 through the asynchronous API after receiving an authorization success notification obtained through the synchronous authorization mode. Correspondingly, if the successful authorization notice obtained by the synchronous authorization mode is not received, the hot switching of the data is cancelled.

Similarly, for the case of executing the periodic asynchronous authorization mode first and then executing the synchronous authorization, the data provider 11 may receive the authorization result notifications N times in the second time duration T2, and send the hot-switch authorization request to the data consumer 12 through the synchronous API when all the authorization result notifications N times are successful. Correspondingly, if the authorization result notification is not received N times or the authorization result notification is failed N times within the second time length T2, the data hot switch is cancelled.

Authorization mode 5: data consumer synchronous and event asynchronous authorization. As shown in fig. 1h, in the authorization method 5, the data provider 11 may also determine whether the data consumer 12 supports hot update, and for the description of the process, reference may be made to the related contents in the authorization method 1, which is not described herein again. Further, in the case that the data consumer 12 supports hot update, the interaction between the data provider 11 and the data consumer 12 can be referred to as the authorization method 1 and the authorization method 2. In this embodiment, the synchronous authorization and the event asynchronous authorization of the data user can be executed in parallel or sequentially. When the two are executed in sequence, the execution sequence of the synchronous authorization and the periodic asynchronous authorization of the data user is not limited. Fig. 1g illustrates the synchronous authorization method first and the event asynchronous authorization method later, but the method is not limited thereto.

Alternatively, in the authorization mode 5, the data provider 11 may obtain the data hot-handover authorization as long as there is an authorization mode satisfying the authorization condition for the data user synchronous authorization and the event asynchronous authorization; the data provider 11 may also obtain data hot-handover authorization under the condition that both the data user synchronous authorization and the periodic asynchronous authorization are satisfied; and so on. If the synchronous authorization mode is executed first and then the event asynchronous authorization mode is executed, the data provider 11 may send a hot-switch authorization request to the data consumer 12 through the asynchronous API after receiving an authorization success notification obtained through the synchronous authorization mode. Correspondingly, if the update authorization notification obtained by the synchronous authorization mode is not received, the data update is cancelled.

Similarly, for the case of executing the event asynchronous authorization mode first and then executing the synchronous authorization, the data provider 11 may send the hot-swap authorization request to the data consumer 12 through the synchronous API when receiving the authorization success notification in the first duration T1. Accordingly, if the authorization success notification or the authorization failure notification is not received within the first time period T1, the data update is cancelled.

It should be noted that the data updating method provided by the embodiment of the present application is suitable for data updating of any application. Such as map data, online shopping data, video data, and so forth. The data is reflected differently, and the manner of determining whether the data consumer 12 allows the data provider 11 to perform hot-swap differs. The following description will take map data as an example.

Fig. 1i is a schematic architecture diagram of a map data processing system according to an embodiment of the present disclosure. As shown in fig. 1a, the map data processing system includes: a map data provider 11 and a map data consumer 12.

In the present embodiment, the map data provider 11 refers to a software functional module that can provide map data. The function module can provide map data, and can also request the map data from the map application server to update the map data.

The map data consumer 12 refers to a software function module that calls map data for use, and that can also implement a specific function based on the map data. For example, the positioning function module may use map data for positioning, and the navigation function module may use map data for navigation, etc.

Alternatively, the map data user 12 may be a car machine system, or may be travel application software integrated in the car machine device.

In this embodiment, the map data provider 11 and the map data consumer 12 may be integrated into a car device that is mounted on the object to be navigated and moves as the object to be navigated moves. The vehicle-mounted equipment can be a navigation terminal and the like. The navigated object may be any object that can be moved. For example, the navigated object may be a motor vehicle, such as a car, taxi, van, motorcycle, electric car, etc., or an autonomous mobile device, such as a robot, unmanned vehicle, etc.

In actual use, the map data provider 11 and the map data consumer 12 may be mounted on a vehicle-mounted device that is mounted on an object to be navigated, and the map data provider 11 and the map data consumer 12 may be used to provide services such as positioning and navigation for the object to be navigated.

In the present embodiment, the map data provider 11 can acquire new map data. Several embodiments of the map data provider 11 for acquiring new map data are explained below.

Embodiment A: the map data provider 11 may acquire new map data for a new geographic area when a navigated object enters the geographic area. Alternatively, the map data consumer 12 may perform real-time positioning on the navigated object based on the map data, obtain real-time positioning information of the navigated object, and provide the real-time positioning information of the navigated object to the map data provider 11. The map data provider 11 may determine whether the navigated object enters a new geographic area according to the real-time positioning information of the navigated object; and when the navigated object enters a new geographic area, requesting map data corresponding to the new geographic area from the map application server. The map application server queries whether the map data of the new geographic area is updated, and if the map data of the new geographic area is updated, sends the new map data corresponding to the new geographic area to the map data provider 11. The map data provider 11 receives, as the new map data, new map data corresponding to the new geographic area provided by the map application server.

Embodiment B: the map data provider 11 may request new map data from the map application server every time the in-vehicle device is started. The map application server inquires whether the map data is updated, and if the map data is updated, the new map data is sent to the map data provider 11. The map data provider 11 receives, as the new map data, new map data corresponding to the new geographic area provided by the map application server.

In some embodiments, the in-vehicle device may be automatically started during the starting process of the navigated object. For example, for an autonomous mobile device such as a robot or an unmanned vehicle, the in-vehicle device may be automatically started during the starting process of the autonomous mobile device. For another example, for some motor vehicles, the vehicle equipment may also be automatically started when the vehicle lane is started. In other embodiments, the in-vehicle device may be autonomously activated by the user. For example, for some motor vehicles, the in-vehicle device may be autonomously activated by a user of the motor vehicle. In this case, when the in-vehicle device is started, the navigated object may be in a traveling process or may be in a stopped traveling state.

Embodiment C: the map application server side can push new map data to the vehicle-mounted device every time the map data are updated. For the map data provider 11, new map data pushed by the map application server may be acquired. In embodiment C, when the map application server pushes new map data, the object to be navigated may be in a traveling state or a stopped state.

The map data providing unit 11 acquires new map data when the object to be navigated is in the stopped state. The map data consumer 12 can authorize the map data provider 11 to update the map data directly in the target data hot-update manner. The map data updating mode of the navigated object in the stopped state is a cold updating mode, and the safety is high.

In actual application, the map data provider 11 may acquire new map data while the navigated object travels based on the map data. In the case where the map data provider 11 acquires new map data while the object to be navigated is traveling based on the map data, it often waits until the object to be navigated stops traveling to update the map data for safety reasons. Such map data update method has low update instantaneity and efficiency, and may cause the navigated object to walk by mistake when traveling based on the map data. For example, in a long distance driving scenario, if the version of the map data provided by the map data provider 11 is too old, but the actual road has changed, this may cause the user to go wrong. For another example, in some scenarios, the administrative area has changed, but the map data provided by the map data provider 11 is still an old version of map data, and so on.

In order to reduce the probability of poor effect of using the map data by the user due to untimely update of the map data, the embodiment of the present application provides a map data hot update method, that is, if the map data provider 11 acquires new map data during the traveling process of the navigated object based on the map data, the map data is updated during the traveling process of the navigated object. The specific implementation mode is as follows:

the map data provider 11 acquires new map data; the map data user 12 acquires the state of the navigated object; and authorizes the map data provider 11 to update the locally stored map data to new map data in a case where the state of the navigated object satisfies the hot update condition.

In some embodiments, the map data provider 11 acquires new map data during the course of the navigated object traveling based on the map data. When the object to be navigated is still in a traveling state, the map data consumer 12 authorizes the map data provider 11 to update the map data in accordance with the target data hot update method customized by the map data consumer 12. Under the condition of obtaining the map data updating authorization, the map data provider 11 switches the locally stored map data into new map data, and completes the map data updating in the traveling process of the navigated object, that is, realizes the hot updating of the map data, and improves the real-time performance and efficiency of the map data updating. In this way, the map data user 12 can complete related operations, such as positioning and navigation, based on the new map data, which is helpful for reducing the probability of the navigated object walking wrongly due to untimely update of the map data, and is further helpful for improving the user experience.

In this embodiment, the map data provider 11 may acquire the configuration information of the target data hot update method and acquire new map data in parallel, or may acquire the configuration information of the target data hot update method and acquire new map data in series. The map data provider 11 serially obtains the configuration information of the target data hot update mode and obtains new map data, and does not limit the sequence of obtaining the configuration information of the target data hot update mode and obtaining the new map data.

In other embodiments, if the customized target update authorization manner is that authorization of the map data user is required, the map data provider 11 may send a hot-switch authorization request to the map data user 12 by using an application program interface corresponding to the target update authorization manner. Optionally, the map data provider 11 may obtain configuration information of a target update authorization manner; the configuration information includes a flag indicating whether the map data user supports hot update. Judging whether the flag bit is in an enabling state; if the judgment result is yes, the map data using party 12 is determined to support hot updating, and a hot switch authorization request is sent to the map data using party 12 by using an Application Program Interface (API) corresponding to the target updating authorization mode.

Accordingly, as shown in fig. 1d to 1h, the map data user 12 receives the hot-switch authorization request and obtains the state of the navigated object; and in the case where the state of the navigated object satisfies the hot update condition, transmits an authorization success notification to the map data provider 11 to authorize the map data provider 11 to update the map data.

Alternatively, the map data consumer 12 may obtain real-time positioning information of the navigated object; judging whether the real-time positioning information of the navigated object is in an area allowing map data to be updated; if the judgment result is yes, determining that the state of the navigated object is an updatable state; correspondingly, if the judgment result is negative, the state of the navigated object is determined to be the non-updatable state. Further, the map data provider 11 may determine that the navigated object satisfies the hot update condition in a case where the state of the navigated object is an updatable status.

The application scenes are different, and the areas where the map data are allowed to be updated are different. In some embodiments, the navigated object is an unmanned vehicle and the area allowing map data updates may be an area that does not support autonomous driving. In other embodiments, the navigated object is a motor vehicle, and the area allowing map data updates may be a non-highway driving area, or a non-turning area, among others.

Alternatively, the map data consumer 12 may also acquire the travel speed of the navigated object. Optionally, the navigated object may be mounted with a speed sensor that can capture the speed of travel of the navigated object. The map data consumer 12 can acquire the travel speed of the navigated object collected by the speed sensor.

Further, if the traveling speed of the navigated object is less than or equal to the set speed threshold, determining that the state of the navigated object is an updatable state; correspondingly, if the judgment result is negative, the state of the navigated object is determined to be the non-updatable state. Further, the map data provider 11 may determine that the navigated object satisfies the hot update condition in a case where the state of the navigated object is an updatable status. The speed threshold value can be flexibly set according to the actual scene.

It should be noted that the above two ways of determining whether the state of the navigated object satisfies the thermal update condition may be implemented separately or in combination, and when the two ways are implemented in combination, the navigated object is in the area where the map data is allowed to be updated, and the traveling speed is less than or equal to the set speed threshold, and is in a state satisfying the thermal update condition.

Further, the map data using party 12 transmits an authorization success notification to the map data providing party in a case where the state of the navigated object satisfies the hot update condition, to authorize the map data providing party 11 to update the map data. Accordingly, in the case where the map data provider 11 receives the authorization success notification, the locally stored map data is updated to new map data.

The customized target data are updated in different ways, and the interaction process between the map data provider 11 and the map data consumer 12 is different when the map data is authorized to be updated. For the interaction process between the map data provider 11 and the map data consumer 12, reference may be made to the related contents in the authorization manners 1-5, and details thereof are not repeated here.

In addition to the data processing system described above, the present application also provides a data update method. An exemplary description is provided below.

Fig. 2 is a schematic flow chart of a data updating method according to an embodiment of the present application. As shown in fig. 2, the method includes:

201. and acquiring a target data hot updating mode customized by a data user.

202. And acquiring new data.

203. And executing a flow related to the data hot switching according to the configuration information of the target data hot updating mode so as to switch the local data into new data.

In this embodiment, a plurality of hot data update methods can be provided. The hot update mode of the data can be as follows: the method does not need at least two modes of a data user authorization mode, a data user synchronous authorization updating (synchronous type for short), a data user asynchronous authorization mode (including event type asynchronous and/or periodic type asynchronous), a mode of combining the data user synchronous and periodic type asynchronous authorization modes, and a mode of combining the data user synchronous and event type asynchronous authorization modes.

The data user can customize the data hot updating mode autonomously according to the application requirement of the data user, and the customization information aiming at the data hot updating mode is provided for the data provider. Optionally. The method comprises the steps of obtaining customized information aiming at a data hot updating mode, and determining a target data hot updating mode from a plurality of supported data hot updating modes according to the customized information; and then, setting the data hot update mode of the data as the target data hot update mode. Optionally, configuration information corresponding to a target data hot update mode can be acquired; and setting the data hot updating mode of the data as the target data hot updating mode according to the configuration information corresponding to the target data hot updating mode. The configuration information corresponding to the target data hot update mode may include: configuration information of a target data hot update mode, and the like.

The target data are updated in different hot updating modes, and the corresponding configuration information is different. For the description of the configuration information, reference may be made to the relevant contents of the above embodiments, which are not described herein again.

Further, in step 201, a target data hot update mode customized by a data user can be obtained; in step 202, new data may be acquired, and in step 203, according to the configuration information of the target data hot update mode, a flow related to data hot switch is executed to switch the locally stored data to new data. In the embodiment of the present application, step 201 and step 202 may be executed in parallel or in series. When

steps

201 and 202 are executed serially, the execution order of the two steps is not limited. Alternatively, in the case of acquiring new data, a target data hot update mode customized by the data user may be acquired again.

The embodiment can provide a data hot-update mode of various data for flexible customization by a data user, and thus, under the condition of acquiring new data, the flow related to the data hot-switch can be executed according to the configuration information of the target data hot-update mode so as to switch the locally stored data into the new data, thereby realizing personalized customization of the data hot-update mode, improving the flexibility of data update and being beneficial to meeting the requirements of different data users.

In this embodiment, the specific implementation of the hot update method of the customization data is not limited. Several alternative embodiments are exemplified below.

Alternative embodiment 1: the data hot update mode can be customized through the configuration file. Wherein the configuration file comprises: and hot updating the configuration information of the mode according to the selected data. For the description of the configuration information of the data hot update method, reference may be made to the relevant contents of the above embodiments, and details are not described herein again. In optional embodiment 1, the configuration information of the data hot update method includes: an identification of a customized data hot update style.

Further, a hot update configuration file provided by a data user can be obtained, and configuration information aiming at a data hot update mode in the hot update configuration file is obtained; and determining a target updating mode according to the configuration information of the hot updating mode. Optionally, the configuration information of the hot update configuration file includes an identification of a customized data hot update mode. Accordingly, the data hot-update mode corresponding to the identifier of the data hot-update mode customized by the data user can be determined from the plurality of data hot-update modes as the target data hot-update mode.

Furthermore, a target data hot updating mode can be analyzed from the configuration file; and setting the data hot updating mode of the data as the target data hot updating mode according to the configuration information corresponding to the target data hot updating mode.

Alternative embodiment 2: an Application Program Interface (API) may provide a variety of ways of hot updating data. The data hot update mode can be customized through the API. And regarding the calling operation of the application program interface which can respond to the data user aiming at the plurality of data hot updating modes, taking the data hot updating mode corresponding to the called application program interface as the target data hot updating mode.

Further, configuration information corresponding to the called application program interface can be obtained and used as configuration information corresponding to the target data hot updating mode; and setting the data hot updating mode as the target data hot updating mode according to the configuration information corresponding to the target data hot updating mode.

Optional embodiment 3: a man-machine interaction interface can be provided for a data user, and the interface can display the identification of a plurality of data hot updating modes. A developer of a data user can customize a data hot updating mode through the man-machine interaction interface.

The data provider can be exposed to the identification of a plurality of data hot update modes. And a developer of the data user can touch the identifier of the selected data hot updating mode to customize the data hot updating mode. Accordingly, the data hot-update mode selected by the touch operation can be the target data hot-update mode in response to the identified touch operation for the data hot-update mode.

Optionally, a corresponding relationship between the identifier of the data hot-update mode and the configuration information may also be preset, so that the configuration information corresponding to the target data hot-update mode may be obtained according to the identifier of the target data hot-update mode and the preset corresponding relationship between the identifier of the data hot-update mode and the configuration information. Further, the data hot-update mode of the data can be set as the target data hot-update mode according to the configuration information corresponding to the target data hot-update mode.

For the terminal which is customized by the hot update mode of the customized data, in the actual use process, the data update data can be executed according to the customized hot update mode of the target data. The following is an exemplary description of the data updating process in the actual usage process. As shown in fig. 3a, the data update process may include:

301. and acquiring configuration information of the target hot update mode.

302. And judging whether the target data hot updating mode needs the authorization of a data user or not according to the configuration information of the target data hot updating mode. If yes, go to step 303; if the determination result is negative, go to step 304.

303. Interacting with the data user according to the authorization mode included by the configuration information to obtain data hot-switch authorization; and in the event that a data hot-handoff grant is obtained, step 304 is performed.

304. A flow associated with the data hot handoff is performed.

Optionally, as shown in fig. 3b, before step 302, step 305 may also be performed: and judging whether the data user supports hot updating or not according to the configuration information of the target data hot updating mode. If yes, go to step 302; if the determination result is negative, execute step 306: and giving up the hot switching of the data.

Authorization mode 1: for the synchronization mode, as shown in fig. 1d, in the authorization mode 1, configuration information of the target data hot update mode may be obtained; the configuration information includes a flag bit whether the data consumer supports hot updates. Judging whether the flag bit is in an enabling state; if the judgment result is yes, the data user side is determined to support hot updating, and a hot switching authorization request is sent to the data user side through the synchronous API. Accordingly, if the data consumer determines that the data provider can perform data hot-swap, an authorization success notification can be provided to the data provider through the synchronization API; if the data consumer determines that the data provider cannot perform a data hot-swap, an authorization failure notification or no authorization success notification may be provided to the data provider through the synchronization API.

Accordingly, for the data provider, an authorization result notification returned by the data provider through the synchronization API may be obtained. And if the authorization result is informed that the authorization is successful, determining to acquire data hot-switch authorization. Correspondingly, if the authorization result notification is an authorization failure notification or the authorization result notification is not received, it is determined that the data hot-switch authorization is not obtained, and the relevant flow of executing the data hot-switch is abandoned.

Authorization mode 2: for the event asynchronous authorization mode, as shown in fig. 1e, in the authorization mode 2, the data provider may send a hot-switch authorization request to the data consumer through an asynchronous API. Accordingly, the data consumer receives the hot handover authorization request. If the data usage determines that the data provider can perform data hot switching, an authorization success notification can be provided to the data provider through the synchronization API; if the data consumer determines that the data provider cannot perform a data hot-swap, an authorization failure notification or no authorization success notification may be provided to the data provider through the synchronization API.

Accordingly, for the data provider, when acquiring new data starts, if an authorization result notification returned by the data user is received within the preset first duration T1 (i.e., the first timeout duration T1), and the authorization result notification is successful, the data hot-swap authorization may be acquired.

If the time length from the time of acquiring new data to the time of acquiring the new data exceeds or reaches the first time length T1, the authorization result notification sent by the data provider is not received or the received authorization result notification is an authorization failure, the data hot switch is cancelled, that is, the operation of switching the local data into the new data is not executed.

Authorization mode 3: periodic asynchronous mode. As shown in fig. 1f, in authorization mode 3, the data provider may send a hot-switch authorization request to the data consumer through an asynchronous API.

If the data user determines that the data provider can execute data hot switching, an authorization success notice can be periodically provided for the data provider through the synchronous API; if the data consumer determines that the data provider cannot perform a data hot-swap, an authorization failure notification or no authorization success notification may be provided to the data provider periodically through the synchronization API.

For a data provider, timing can be started when new data is acquired, and the number of times of receiving the authorization result notification in the timing duration is counted; if N authorization result notifications are received within the preset second duration (i.e., the second timeout time) T2, and the N authorization result notifications are successful in authorization, the data hot-handover authorization is obtained. Where N is a threshold (lower limit) of the number of times the update authorization notification is received within the second timeout period T2. And if authorization failure exists in the N-time authorization result notifications or the N-time authorization result notifications are not received, canceling the hot switching of the data, namely not executing the operation of switching the local data into new data.

Authorization mode 4: synchronous and periodic asynchronous grants are combined. As shown in fig. 1g, the interaction manner between the data provider and the data consumer can refer to the authorization manner 1 and the authorization manner 3 and the related contents of the system embodiments, which are not described herein again.

Authorization mode 5: data consumer synchronous and event asynchronous authorization. As shown in fig. 1h, the interaction mode between the data provider and the data consumer can refer to the authorization mode 1 and the authorization mode 2 and related contents in the system embodiment, which are not described herein again.

It should be noted that the data updating method provided by the embodiment of the present application is suitable for data updating of any application. Such as map data, online shopping data, video data, and so forth. The data reflecting content is different, and the judging mode of whether the data user allows the data provider to execute the hot switching of the data is different. The following description will take map data as an example.

Optionally, the state of the navigated object may be obtained; and sending an authorization success notification to the map data provider to authorize the map data provider to update the map data when the state of the navigated object satisfies the hot update condition.

Optionally, real-time positioning information of the navigated object may be obtained; judging whether the real-time positioning information of the navigated object is in an area allowing map data to be updated; if the judgment result is yes, determining that the state of the navigated object is an updatable state; correspondingly, if the judgment result is negative, the state of the navigated object is determined to be the non-updatable state. Further, it may be determined that the navigated object satisfies the hot update condition if the state of the navigated object is an updatable status.

The application scenes are different, and the areas where the map data are allowed to be updated are different. For the areas allowing map data to be updated, reference may be made to the related contents of the above system embodiments, and details are not repeated here.

Alternatively, the travel speed of the navigated object may be obtained. Further, if the traveling speed of the navigated object is less than or equal to the set speed threshold, determining that the state of the navigated object is an updatable state; correspondingly, if the judgment result is negative, the state of the navigated object is determined to be the non-updatable state. Further, it may be determined that the navigated object satisfies the hot update condition if the state of the navigated object is an updatable status. The speed threshold value can be flexibly set according to the actual scene.

Further, in a case where the state of the navigated object satisfies the hot update condition, an authorization success notification is sent to the map data provider to authorize the map data provider to update the map data. Accordingly, in the case where the authorization success notification is received, the locally stored map data is updated to new map data.

The customized target data are different in hot updating modes, and when the map data are authorized to be updated, the interaction process of a map data provider and a map data user is different. For the interaction process between the map data provider and the map data user, reference may be made to the related contents in the authorization manners 1-5, and details are not described herein again.

The embodiment of the application also provides a map data updating method, which is used for updating the map data stored on the navigated object. As shown in fig. 4, the method includes:

401. new map data is acquired.

402. The state of the navigated object is obtained.

403. And if the state of the navigated object meets the hot update condition, updating the locally stored map data into new map data.

The map data updating method provided by the embodiment is suitable for the vehicle-mounted equipment. The vehicle-mounted equipment can be mounted on a navigated object. For the description of the implementation form of the navigated object, reference may be made to the related contents of the above system embodiments, and details are not repeated herein.

In this embodiment, in the case where new map data is generated, the state of the navigated object may be acquired, and in the case where the state of the navigated object satisfies the thermal update condition, the locally stored map data is updated to the new map data. The map data is updated in a hot mode under the condition that the state of the navigated object meets the hot updating condition, the map data can be updated in a hot mode on the premise that the use of the map data by the navigated object or the trip application software on the navigated object is not affected, and the map data updating timeliness is improved.

Optionally, acquiring real-time positioning information of the navigated object; judging whether the real-time positioning information of the navigated object is in an area allowing map data to be updated; if the judgment result is yes, determining that the state of the navigated object is an updatable state; correspondingly, if the judgment result is negative, the state of the navigated object is determined to be the non-updatable state. Further, it may be determined that the navigated object satisfies the hot update condition if the state of the navigated object is an updatable status.

Optionally, a hot update mode of target data customized by a map data user can be obtained. Further, in the case that the state of the navigated object satisfies the hot update condition, a hot-switch related flow may be executed according to the configuration information of the target data hot update manner, so as to switch the locally stored map data to new map data. For a specific implementation of performing a hot-handoff related procedure according to the configuration information of the target data hot-update mode, reference may be made to the relevant contents of the above embodiments, and details are not described herein again.

Optionally, customized information for a map data hot update mode can be acquired; and determining a target data hot update mode from the supported data hot update modes according to the customization information. For specific implementation, reference may be made to relevant contents of the foregoing embodiments, which are not described herein again.

It should be noted that the execution subjects of the steps of the methods provided in the above embodiments may be the same device, or different devices may be used as the execution subjects of the methods. For example, the execution subject of

steps

301 and 302 may be device a; for another example, the execution subject of step 301 may be device a, and the execution subject of step 302 may be device B; and so on.

In addition, in some of the flows described in the above embodiments and the drawings, a plurality of operations are included in a specific order, but it should be clearly understood that the operations may be executed out of the order presented herein or in parallel, and the sequence numbers of the operations, such as 301, 302, etc., are merely used for distinguishing different operations, and the sequence numbers do not represent any execution order per se. Additionally, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel.

Accordingly, embodiments of the present application also provide a computer-readable storage medium storing computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the map data updating and/or data updating method described above.

An embodiment of the present application further provides a computer program product, including: a computer-readable storage medium storing computer instructions which, when executed by one or more processors, cause the steps in the map data update and/or data update methods described above.

Fig. 5 is a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in fig. 5, the terminal device includes: a memory 50a and a processor 50 b. A memory 50a for storing a computer program.

The processor 50b is coupled to the memory 50a for executing a computer program for: acquiring new map data; acquiring the state of a navigated object; and if the state of the navigated object meets the hot update condition, updating the locally stored map data into new map data.

Optionally, when acquiring the state of the navigated object, the processor 50b is specifically configured to: acquiring real-time positioning information of a navigated object; judging whether the real-time positioning information of the navigated object is located in a preset geographical position area allowing map data to be updated; if the judgment result is yes, determining that the state of the navigated object is an updatable state; and determining that the state of the navigated object satisfies the hot update condition if the state of the navigated object is an updatable state.

Optionally, when acquiring the state of the navigated object, the processor 50b is specifically configured to: acquiring the traveling speed of a navigated object; judging whether the traveling speed of the navigated object is less than a preset speed threshold value or not; if the judgment result is yes, determining that the state of the navigated object is an updatable state; and determining that the state of the navigated object satisfies the hot update condition if it is determined that the state of the navigated object is an updatable state.

Optionally, when the locally stored map data is updated to new map data, the processor 50b is specifically configured to: acquiring a target data hot updating mode customized by a map data user; and executing a flow related to data hot switching according to the configuration information of the target data hot updating mode so as to update the locally stored map data into new map data.

The terminal device provided by the embodiment can acquire the state of the navigated object when new map data is generated, and update the map data locally stored in the navigated object to the new map data when the state of the navigated object meets the thermal update condition. The map data is updated in a hot mode under the condition that the state of the navigated object meets the hot updating condition, the map data can be updated in a hot mode on the premise that the use of the map data by the navigated object or the trip application software on the navigated object is not affected, and the map data updating timeliness is improved.

In some embodiments of the present application, the processor 50b is further configured to: acquiring a target data hot updating mode customized by a data user; and, obtaining new data; and executing a flow related to the hot switching of the data according to the configuration information of the hot updating mode of the target data so as to switch the local data into new data.

Optionally, when executing the flow related to data hot handoff, the processor 50b is specifically configured to: judging whether the target data hot updating mode needs the authorization of a data user or not according to the configuration information of the target data hot updating mode; if the authorization of the data user is needed, the data user interacts with the data user according to the authorization mode included by the configuration information to obtain the hot switching authorization of the data; and executing the flow related to the data hot switching under the condition of obtaining the data hot switching authorization. Correspondingly, if the target data hot update mode does not need the authorization of the data user, the flow related to the data hot switching is directly executed.

Optionally, the processor 50b is further configured to: before judging whether the data hot-updating mode needs the authorization of a data user, judging whether the data user supports data hot-switching according to the configuration information of the target data hot-updating mode; if the data hot switching is supported, the operation of judging whether the target data hot updating mode needs the authorization of the data user is executed.

In some embodiments, the authorization means comprises a synchronization means. Correspondingly, when the processor 30b interacts with the data user according to the authorization manner included in the configuration information, the processor is specifically configured to: sending a hot-switch authorization request to the synchronous interface of the data consumer through the communication component 30c to request data hot-switch authorization from the data consumer; and obtaining an authorization result notice returned by the data provider through the synchronous interface; and if the authorization result is informed that the authorization is successful, determining to obtain the data hot-switch authorization.

Further, optionally, the authorization manner further includes: event asynchronous mode, the processor 50b is further configured to: after acquiring the authorization success notification returned by the data provider through the synchronous interface, sending a hot-switch authorization request to the asynchronous interface of the data consumer through the communication component 50c to request data hot-switch authorization from the data consumer; and if the authorization result notification returned by the data user is received within the preset third duration and the authorization result notification is successful, obtaining hot-hot switching authorization.

Or, the authorization mode further comprises: periodically, asynchronously, the processor 50b is further configured to: after obtaining the authorization success notification returned by the data consumer through the synchronous interface, sending a hot-switch authorization request to the asynchronous interface of the data consumer through the communication component 50c to request data hot-switch authorization from the data consumer; and if N times of authorization result notifications returned by the data user are received within the preset fourth time length and the N times of authorization result notifications are successful, obtaining the data hot-switching authorization.

In other embodiments, the authorization manner includes an event asynchronous manner, and the processor 50b is specifically configured to, when interacting with the data user according to the authorization manner included in the configuration information: sending a hot-switch authorization request to the asynchronous interface of the data consumer through the communication component 50c to request data hot-switch authorization from the data consumer; and if the authorization result notification returned by the data user is received within the preset first duration and the authorization result notification is successful, obtaining the data hot-switch authorization.

In still other embodiments, the authorization manner includes a periodic asynchronous manner, and the processor 50b is specifically configured to, when interacting with the data user according to the authorization manner included in the configuration information: sending a hot-switch authorization request to the asynchronous interface of the data consumer through the communication component 50c to request data hot-switch authorization from the data consumer; if N times of authorization result notifications returned by the data user are received within a preset second time length and the N times of authorization result notifications are successful, obtaining data hot-switching authorization; wherein N is a positive integer.

In an embodiment of the present application, the data may be map data. The processor 50b is further configured to: acquiring the state of a navigated object carried by a terminal storing map data; and if the state of the navigated object meets the hot updating condition, executing a flow related to hot switching of data according to the configuration information of the target data hot updating mode so as to switch the map data stored locally into new map data.

Optionally, the processor 50b, when acquiring the state of the navigated object carried by the terminal storing the map data, is specifically configured to: acquiring real-time positioning information of a navigated object; judging whether the real-time positioning information of the navigated object is located in a preset geographical position area allowing map data to be updated; if the judgment result is yes, determining that the state of the navigated object is an updatable state; and determining that the state of the navigated object satisfies the hot update condition if the state of the navigated object is an updatable state.

Optionally, when acquiring the state of the navigated object, the processor 50b is specifically configured to: acquiring the traveling speed of a navigated object; judging whether the traveling speed of the navigated object is less than a preset speed threshold value or not; if the judgment result is yes, determining that the state of the navigated object is an updatable state; and determining that the state of the navigated object satisfies the hot update condition if the state of the navigated object is an updatable state.

In some embodiments, the processor 50b is further configured to: acquiring a hot update configuration file provided by a data user; acquiring configuration information aiming at a data hot update mode from a hot update configuration file; determining a target hot updating mode according to the configuration information of the data hot updating mode; or responding to the calling operation of the data user for the application program interface of the data hot updating mode, and taking the data hot updating mode corresponding to the called application program interface as a target hot updating mode; alternatively, the display component 50d displays an identification of at least one data hot update mode; and responding to the touch operation aiming at the identification of the data hot updating mode, and taking the data hot updating mode selected by the touch operation as a target hot updating mode.

In some optional embodiments, as shown in fig. 5, the terminal device may further include: power components 50e, audio components 50f, and the like. Only some of the components are schematically shown in fig. 5, and it does not mean that the terminal device must include all of the components shown in fig. 5, nor that the terminal device can include only the components shown in fig. 5.

In embodiments of the present application, the memory is used to store computer programs and may be configured to store other various data to support operations on the device on which it is located. Wherein the processor may execute a computer program stored in the memory to implement the corresponding control logic. The memory may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

In the embodiments of the present application, the processor may be any hardware processing device that can execute the above described method logic. Alternatively, the processor may be a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), or a Micro Controller Unit (MCU); programmable devices such as Field-Programmable Gate arrays (FPGAs), Programmable Array Logic devices (PALs), General Array Logic devices (GAL), Complex Programmable Logic Devices (CPLDs), etc. may also be used; or Advanced Reduced Instruction Set (RISC) processors (ARM), or System On Chips (SOC), etc., but is not limited thereto.

In embodiments of the present application, the communication component is configured to facilitate wired or wireless communication between the device in which it is located and other devices. The device in which the communication component is located can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G, 5G or a combination thereof. In an exemplary embodiment, the communication component receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component may also be implemented based on Near Field Communication (NFC) technology, Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, or other technologies.

In the embodiment of the present application, the display assembly may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the display assembly includes a touch panel, the display assembly may be implemented as a touch screen to receive input signals from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation.

In embodiments of the present application, a power supply component is configured to provide power to various components of the device in which it is located. The power components may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device in which the power component is located.

In embodiments of the present application, the audio component may be configured to output and/or input audio signals. For example, the audio component includes a Microphone (MIC) configured to receive an external audio signal when the device in which the audio component is located is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in a memory or transmitted via a communication component. In some embodiments, the audio assembly further comprises a speaker for outputting audio signals. For example, for devices with language interaction functionality, voice interaction with a user may be enabled through an audio component, and so forth.

In the terminal device provided by this embodiment, a plurality of data hot update modes can be provided for a data user to flexibly customize. When data is updated, a target data hot updating mode customized by a data user can be obtained, and a flow related to data hot switching is executed according to configuration information of the target data hot updating mode customized by the data user, so that local data is switched into new data, data updating according to the data hot updating mode customized by the data user is realized, personalized customization of the data hot updating mode by the data user is realized, data authorization flexibility is improved, and the requirements of different data users are favorably met.

It should be noted that, the descriptions of "first", "second", etc. in this document are used for distinguishing different messages, devices, modules, etc., and do not represent a sequential order, nor limit the types of "first" and "second" to be different.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

The above description is only an example of the present application and is not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A data updating method, comprising:

acquiring a target data hot updating mode customized by a data user;

acquiring new data;

2. The method according to claim 1, wherein the executing a flow related to data hot-handoff according to the configuration information of the target data hot-update mode specifically includes:

judging whether the target data hot updating mode needs the authorization of a data user or not according to the configuration information of the target data hot updating mode;

if the authorization of the data user is needed, the data user is interacted with the authorization mode included by the configuration information so as to obtain the hot switching authorization of the data; and executing the flow related to the data hot switching under the condition of obtaining the data hot switching authorization.

3. The method of claim 2, wherein before determining whether the data hot-update mode requires authorization of a data user, further comprising:

judging whether the data user supports data hot switching or not according to the configuration information of the target data hot updating mode;

and if the data hot switching is supported, executing the operation of judging whether the target data hot updating mode needs the authorization of a data user.

4. The method according to claim 2, wherein the authorization manner includes a synchronization manner, and the interacting with the data consumer according to the authorization manner included in the configuration information to obtain data hot-handover authorization specifically includes:

sending a hot-switch authorization request to a synchronous interface of the data user to request data hot-switch authorization from the data user;

obtaining an authorization result notice returned by the data provider through a synchronous interface;

and if the authorization result is informed that the authorization is successful, determining to obtain data hot-switching authorization.

5. The method according to claim 2, wherein the authorization manner includes an event asynchronous manner, and the interacting with the data consumer according to the authorization manner included in the configuration information to obtain the data hot-handover authorization specifically includes:

sending a hot-switch authorization request to an asynchronous interface of the data consumer to request data hot-switch authorization from the data consumer;

and if the authorization result notification returned by the data user is received within a preset first duration and the authorization result notification is successful, obtaining data hot-switching authorization.

6. The method according to claim 2, wherein the authorization manner includes a periodic asynchronous manner, and the interacting with the data user according to the authorization configuration included in the configuration information to obtain the data hot-handover authorization specifically includes:

if N times of authorization result notifications returned by the data user are received within a preset second time length and the N times of authorization result notifications are successful, obtaining data hot-switching authorization;

wherein N is a positive integer.

7. The method of claim 4, wherein the authorization manner further comprises: in the event asynchronous manner, after obtaining the authorization success notification returned by the data provider through the synchronous interface, the method further includes:

and if the authorization result notification returned by the data user is received within the preset third duration and the authorization result notification is successful, obtaining hot-hot switching authorization.

8. The method of claim 4, wherein the authorization manner further comprises: periodically, asynchronously, after obtaining the authorization success notification returned by the data consumer through the synchronous interface, the method further comprises:

and if N times of authorization result notifications returned by the data user are received within a preset fourth time length and the N times of authorization result notifications are successful, obtaining data hot-switching authorization.

9. The method of any of claims 1-8, wherein the data is map data, the method further comprising:

acquiring the state of a navigated object carried by a terminal storing map data;

and if the state of the navigated object meets the hot updating condition, executing a flow related to hot switching of data according to the configuration information of the target data hot updating mode so as to switch the locally stored map data into new map data.

10. The method of claim 9, wherein the obtaining of the state of the navigated object hosted by the terminal storing map data comprises:

acquiring real-time positioning information of the navigated object;

judging whether the real-time positioning information of the navigated object is located in a preset geographical position area allowing map data to be updated;

if the judgment result is yes, determining that the state of the navigated object is an updatable state; and determining that the state of the navigated object satisfies a hot update condition if the state of the navigated object is an updatable state.

11. The method of claim 9, wherein the obtaining the state of the navigated object comprises:

acquiring the traveling speed of the navigated object;

judging whether the traveling speed of the navigated object is less than a preset speed threshold value or not;

12. The method of any of claims 1-8, wherein the method further comprises:

acquiring a hot update configuration file provided by the data user; acquiring configuration information aiming at a data hot update mode from the hot update configuration file; determining the target hot updating mode according to the configuration information of the data hot updating mode;

alternatively, the first and second electrodes may be,

responding to the calling operation of a data user for the application program interface of the data hot updating mode, and taking the data hot updating mode corresponding to the called application program interface as the target hot updating mode;

alternatively, the first and second electrodes may be,

responding to the touch operation aiming at the identification of the data hot updating mode, and taking the data hot updating mode selected by the touch operation as the target hot updating mode.

13. The method of claim 2, further comprising:

and if the target data hot updating mode does not need the authorization of the data user, directly executing the flow related to the data hot switching.

14. A map data updating method for updating map data stored on a navigated object, comprising:

acquiring new map data;

acquiring the state of the navigated object;

and if the state of the navigated object meets the thermal update condition, updating the locally stored map data into the new map data.

15. The method of claim 14, wherein the obtaining the state of the navigated object comprises:

acquiring real-time positioning information of the navigated object;

16. The method of claim 14, wherein the obtaining the state of the navigated object comprises:

acquiring the traveling speed of the navigated object;

if the judgment result is yes, determining that the state of the navigated object is an updatable state; and determining that the state of the navigated object satisfies a hot update condition if the determination is that the state of the navigated object is an updatable state.

17. The method of claim 14, wherein updating the locally stored map data to the new map data comprises:

acquiring a target data hot updating mode customized by a map data user;

and executing a flow related to data hot switching according to the configuration information of the target data hot updating mode so as to update the locally stored map data into the new map data.

18. The method of claim 17, further comprising:

obtaining customized information aiming at a map data hot updating mode;

and according to the customization information, determining a target data hot updating mode from the supported data hot updating modes.

19. A computer program product, comprising: a computer-readable storage medium storing computer instructions that, when executed by one or more processors, cause the one or more processors to perform the steps of the method of any one of claims 1-18.

20. A terminal device, comprising: a memory and a processor; the memory for storing a computer program;

the processor is coupled to the memory for executing the computer program for performing the steps of the method of any of claims 1-18.

21. A computer-readable storage medium storing computer instructions, which, when executed by one or more processors, cause the one or more processors to perform the steps of the method of any one of claims 1-18.