WO2021087970A1

WO2021087970A1 - Method and apparatus for updating tag data, electronic device, and storage medium

Info

Publication number: WO2021087970A1
Application number: PCT/CN2019/116679
Authority: WO
Inventors: 黄江伟
Original assignee: 深圳市欢太科技有限公司; Oppo广东移动通信有限公司
Priority date: 2019-11-08
Filing date: 2019-11-08
Publication date: 2021-05-14
Also published as: CN114365111A

Abstract

A method and apparatus for updating tag data, an electronic device, and a storage medium. The method for updating tag data comprises: when tag data to be updated is obtained, acquiring the type of the tag data, wherein different types of tag data have different levels in real-time performance during updating (S110); caching the tag data to an update queue corresponding to the type, wherein different update queues correspond to different data update speeds (S120); and updating the tag data in the update queue according to a data update speed corresponding to the update queue (S130). By means of the method, real-time updating of tag data can be realized.

Description

Method, device, electronic equipment and storage medium for updating label data

Technical field

This application relates to the field of data processing technology, and more specifically, to a method, device, electronic device, and storage medium for updating tag data.

Background technique

With the rapid development of network information technology, big data technology appears more frequently in daily life. A more typical application scheme is information recommendation technology. In information recommendation technology, recommendations are usually based on user tags. User tags play a very important role in information recommendation technology. Therefore, the update of user tags is the key to information recommendation technology.

Summary of the invention

In view of the above problems, this application proposes a method, device, electronic device and storage medium for updating tag data.

In the first aspect, an embodiment of the present application provides a method for updating label data. The method includes: when the label data to be updated is obtained, the type of the label data is obtained, and different types of label data are updated in real time. Different levels of sexuality; cache the tag data in the update queue corresponding to the type, where different update queues correspond to different data update speeds; according to the data update speed corresponding to the update queue, all data in the update queue The label data is updated.

In a second aspect, an embodiment of the present application provides a device for updating tag data. The device includes: a type acquisition module, a data caching module, and a data update module. The type acquisition module is used to obtain the tag to be updated. When data is acquired, the type of the tag data is obtained. Different types of tag data have different real-time levels during update; the data caching module is used to cache the tag data to the update queue corresponding to the type, where different The update queue corresponds to different data update speeds; the data update module is used to update the tag data in the update queue according to the data update speed corresponding to the update queue.

In a third aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a memory; one or more application programs, wherein the one or more application programs are stored in the memory and It is configured to be executed by the one or more processors, and the one or more programs are configured to execute the method for updating tag data provided in the first aspect described above.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium stores program code, and the program code can be called by a processor to execute the tag provided in the first aspect. How to update the data.

The solution provided by this application obtains the type of label data when obtaining the label data to be updated. Different types of label data have different real-time levels when updating, and then caches the label data to the update queue corresponding to the type. Update the data update speed corresponding to the update queue, update the tag data in the update queue, so as to realize that the tag data of different real-time levels can be entered into different update queues, and the tags are updated according to the data update speed corresponding to the update queue. The data is updated to ensure the real-time update of label data.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings that need to be used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

Fig. 1 shows a schematic diagram of the principle of tag data update provided by an embodiment of the present application.

Fig. 2 shows a flowchart of a method for updating tag data according to an embodiment of the present application.

Fig. 3 shows a flowchart of a method for updating tag data according to another embodiment of the present application.

FIG. 4 shows a flowchart of step S210 in the method for updating tag data provided by another embodiment of the present application.

FIG. 5 shows another flowchart of step S210 in the method for updating tag data provided by another embodiment of the present application.

FIG. 6 shows a schematic diagram of the principle of a method for updating tag data provided by another embodiment of the present application.

Fig. 7 shows a flowchart of a method for updating tag data according to another embodiment of the present application.

Fig. 8 shows a flowchart of a method for updating tag data according to another embodiment of the present application.

FIG. 9 shows a flowchart of step S430 in the method for updating tag data according to another embodiment provided by the present application.

FIG. 10 shows another flow chart of step S430 in the method for updating tag data in another embodiment provided by the present application.

Fig. 11 shows a block diagram of a device for updating tag data according to an embodiment of the present application.

Fig. 12 shows a block diagram of the type acquisition module in the device for updating tag data according to an embodiment of the present application.

Fig. 13 shows another block diagram of the type acquisition module in the device for updating tag data according to an embodiment of the present application.

FIG. 14 is a block diagram of an electronic device for executing the method for updating tag data according to an embodiment of the present application according to an embodiment of the present application.

Fig. 15 is a storage unit for storing or carrying program code implementing the method for updating tag data according to the embodiment of the present application according to an embodiment of the present application.

Detailed ways

In order to enable those skilled in the art to better understand the solutions of the present application, the technical solutions in the embodiments of the present application will be described clearly and completely in conjunction with the accompanying drawings in the embodiments of the present application.

With the rapid development of information technology, the Internet has brought more and more convenience to people's lives and work. Among them, information recommendation technology based on big data technology can recommend content that people need, which can better meet the needs of users. For example, people can use the Internet to shop, entertain, and publish personal status information (for example, Weibo), etc. Merchants can obtain people’s consumption, entertainment, and personal status information through the Internet, which can provide a more comprehensive understanding of the public’s information. Demand, and then provide recommendations for people based on the needs of the public. While businesses provide people with recommendation services, businesses also make profits.

In the information recommendation technology, it mainly applies user tags, so that the recommended content can meet the needs of users. User tags are mainly data used to reflect information such as users' social attributes, living habits, and consumption behaviors, and user tags are feature identifiers obtained by analyzing user information. The user tag continuously updates the tag data, so that the user tag can ensure accuracy.

In traditional technology, tag data is mainly stored in a database, and electronic devices that manage user tags usually collect tag data from different data sources and write the tag data into the tag database. The data source can be a server, a mobile terminal, etc., which is not limited here.

The tag data update in the traditional technology usually processes all tag data in a unified manner. When tag data arrives, the data is offline processed, and after all the data is offline calculated, the storage or update request is uniformly initiated to the tag management system. In this way, when a large amount of data is updated, it can efficiently perform aggregation processing and reduce the pressure on the label management system.

After long-term research, the inventor found that the update scheme for tag data in the traditional technology cannot satisfy the update of tag data that is updated frequently. For example, the geographical location is updated according to the traditional scheme. Because the offline time is long, there will be users who have actually moved to another place, and the previous geographical location is actually written into the tag database. If the previous geographical location is used again Treatment is not conducive to the use of business. For example, as shown in Figure 1, when the number of geographic locations and other data are obtained (data A, data B), they will be aggregated together, enter the same buffer queue 701, and then be updated to the label by the label update program 702. In the storage system 703, the entire process takes a lot of time, and data with high real-time requirements is likely to lose timeliness.

In response to the above problems, the inventors proposed the method, device, electronic device and storage medium for updating tag data provided by the embodiments of the present application. When the tag data to be updated is obtained, the tag data is cached according to the type of the tag data. The update queue corresponds to its type, and the tag data is updated according to the data update speed corresponding to the update queue to ensure the real-time update of the tag data. Among them, the specific method for updating the tag data will be described in detail in the subsequent embodiments.

Please refer to FIG. 2, which shows a schematic flowchart of a method for updating tag data provided by an embodiment of the present application. The tag data update method is used to realize that tag data of different real-time levels can be entered into different update queues, and the tag data is updated according to the data update speed corresponding to the update queue to ensure the real-time update of tag data Sex. In a specific embodiment, the tag data updating method is applied to the tag data updating device 400 as shown in FIG. 11 and the electronic device 100 configured with the tag data updating device 400 (FIG. 14 ). The following will take an electronic device as an example to describe the specific process of this embodiment. Of course, it is understandable that the electronic device applied in this embodiment may be a server, a mobile terminal, etc., which is not limited herein. The process shown in FIG. 2 will be described in detail below, and the method for updating label data may specifically include the following steps:

Step S110: When the tag data to be updated is obtained, the type of the tag data is obtained, and different types of tag data have different real-time levels when being updated.

In the embodiment of the present application, the electronic device can manage the user's tag data, and the tag data managed by the electronic device can come from a data source. Among them, the data source may be a server, or a mobile terminal, etc., which is not limited here. The electronic device can obtain the label data from the data source to update the user's label data. The label data refers to data corresponding to the label, and specifically may be user data corresponding to the label. For example, the occupation of user A at the first moment is a student, and the occupation at the second moment is a teacher. At the first moment, the data corresponding to the occupation in the label of user A is student. At the second moment, the label of user A The data corresponding to the middle occupation is teachers. Since the user’s label data is changing over time, it is necessary to continuously update the user’s label data so that the user’s label data can match the user’s latest status, so as to provide users with the ability to meet their needs based on the label data. Service.

In some embodiments, the electronic device may actively obtain the tag data to be updated from the data source, or may receive the tag data to be updated sent by the data source. The label data to be updated refers to the obtained label data that needs to be written into the label data database, and can also be understood as the label data used to update the user label.

In some embodiments, the electronic device may obtain the tag data to be updated from the data source regularly or irregularly. For example, the electronic device may obtain the tag data to be updated from the data source at a preset interval. For another example, the electronic device may receive the tag data to be updated from the data source in real time.

In the embodiment of the present application, when the electronic device obtains the tag data to be updated, it can determine the type of the tag data to be updated. Different types of label data have different real-time levels when they are updated. Among them, the real-time level of label data when it is updated can refer to the level of real-time demand for label data when it is updated. The higher the real-time level, the higher the real-time level of the label data. The more real-time updates are needed. For example, the types of tag data include type A, type B, and type C. The tag data of type A, type B, and type C have different real-time levels. The tag data of type A can have a higher real-time level than type C. The real-time level corresponding to the label data of B, the real-time level corresponding to the label data of type B can be greater than the real-time level corresponding to the label data of type C. Of course, the above is only an example, and does not represent the specific type and real-time Limitation of the level of relationship.

In some embodiments, the type of label data may be the classification result of different label data classified in advance according to the real-time level corresponding to the label data. Each classification result may correspond to a type and belong to the same type. The real-time level corresponding to the tag data can be the same. For example, the user’s location, the user’s web browsing information, etc. have very strong real-time requirements for updating, and its real-time level is at the first level, then the location, web browsing information, etc. can be used as a type; the user’s dining and consumption Amount, etc., have a strong demand for real-time during update, and its real-time level is at the second level, so the user’s meal, consumption amount, etc. can be used as a type; the user’s occupation, age, etc. do not have a strong demand for real-time during update , Its real-time level is at the third level, the user’s occupation, age, etc. can be used as a type, where the first level, the second level, and the third level are in descending order. Of course, the above is only For example, it does not represent a limitation on specific types.

In some embodiments, the type of tag data can be pre-stored in the electronic device, and the electronic device can determine the type of tag data by identifying the field data in the tag data, the data source of the source, the user identification, etc., which is not limited here.

Step S120: Buffer the tag data in the update queue corresponding to the type, where different update queues correspond to different data update speeds.

In the embodiment of the present application, a plurality of update queues may be pre-created in the memory of the electronic device, and the update queues are used to cache tag data to be updated. In addition, each update queue corresponds to a type of tag data, the data update speed corresponding to each update queue is different, the number of update queues is the same as the number of types, and the specific number of update queues is not limited. For example, if the types corresponding to the tag data include the first type, the second type, and the third type, three update queues can be created in advance in the electronic device, and the three update queues correspond to the first type, the second type, and the third type, respectively. . The data update speed corresponding to the update queue may refer to the speed in the subsequent process of taking out the tag data from the update queue and updating it.

In some embodiments, because different update queues correspond to different types of tag data, and different types of tag data have different real-time levels when they are updated, the data update speed corresponding to the update queue may correspond to the corresponding type of tag data. The real-time level during the update corresponds to, so that the update queue can meet the real-time requirements of the corresponding type of tag data during the update. Specifically, the higher the real-time level of the tag data corresponding to the update queue, the faster the data update speed corresponding to the update queue, thereby ensuring that the tag data with high real-time level can be updated quickly and ensuring the timeliness of the tag data Sex.

In the embodiment of the present application, after the electronic device determines the type corresponding to the tag data to be updated, it can determine the update queue corresponding to the type from a plurality of pre-created update queues according to the type corresponding to the tag data. The update queue corresponding to this type determined by the electronic device is used to cache the obtained tag data. The electronic device may cache the tag data obtained in step S110 in the update queue corresponding to this type, so as to subsequently update the obtained tag data .

In some embodiments, the data update speed corresponding to different update queues can be controlled according to the speed of fetching tag data from the update queue and the speed of updating the tag data to the tag database. Of course, the specific implementation of different update queues corresponding to different update speeds may not be regarded as a limitation.

Step S130: Update the tag data in the update queue according to the data update speed corresponding to the update queue.

In the embodiment of the present application, after the obtained tag data is cached in the corresponding update queue, the tag data in the update queue can be updated according to the data update speed corresponding to the update queue, so that the obtained tag data is updated The speed corresponds to its corresponding real-time level. And because the higher the real-time level of the tag data corresponding to the update queue, the faster the data update speed corresponding to the update queue, so that the tag data with high real-time level can be updated quickly, ensuring the timeliness of the tag data . In addition, since ensuring that the data update speed is high will occupy more resources of the electronic device, not all the update speeds of the update queues in the electronic device correspond to the higher data update speed. For the label data with low real-time level, it will enter To the update queue with a relatively slow data update speed, instead of all tag data entering the update queue with a relatively fast data update speed, the resources of the electronic device will not be occupied by too many resources by the update task of the tag data, which is effective Utilizes the resources of electronic equipment.

The method for updating tag data provided in the embodiments of the present application determines the type of tag data when obtaining tag data to be updated, then caches the tag data in the update queue corresponding to the type, and then according to the data corresponding to the update queue Update speed, update the label data in the update queue, so that the speed at which the obtained label data is updated corresponds to the corresponding real-time level, so that the label data with high real-time level can be updated quickly, ensuring the label Timeliness of data.

Please refer to FIG. 3, which shows a schematic flowchart of a method for updating tag data provided by another embodiment of the present application. This method is applied to the above-mentioned electronic equipment. The process shown in FIG. 3 will be described in detail below. The method for updating label data may specifically include the following steps:

Step S210: When the tag data to be updated is obtained, the type of the tag data is obtained, and different types of tag data have different real-time levels when being updated.

In the embodiment of the present application, the type of the tag data may correspond to the type identification of the tag data, or it may correspond to the data source of the tag data. When the electronic device obtains the type of tag data, it can be determined according to the type identification of the tag data or the data source corresponding to the tag data.

In an example, each tag data may include a three-segment identification, the three-segment identification is composed of an identification a, an identification b, and an identification c, and the identification a may be used to indicate the large Category (for example, category includes personal type and family type), the identifier b is used to indicate the type corresponding to the real-time level, the type corresponding to the real-time level can be determined by the identifier b, and the identifier c can be used to indicate the label name. For example, the types of tag data are divided into a first type and a second type, b1 can represent the first type, and b2 can represent the second type. Of course, the above is only an example, and does not represent a limitation on the actual type identification.

In some embodiments, referring to FIG. 4, step S210 may include:

Step S211A: Obtain a type identifier in the tag data, where the type identifier is used to characterize the type of tag data;

Step S212A: Determine the type of the tag data according to the type identification.

It is understandable that the tag data may include a type identification. The type identification is in the setting field of the label data. The electronic device can obtain the type identification of the label data by obtaining the data of the setting field in the label data. After the electronic device obtains the type identification of the label data, it can identify according to the type, Determine the type of label data.

In other embodiments, referring to FIG. 5, step S210 may include:

Step S211B: Obtain the data source of the tag data;

Step S212B: Determine the type of the tag data according to the data source.

In some embodiments, the label data of different data sources may have different real-time levels when they are updated. The real-time level of the label data of the data source when it is updated can refer to the real-time performance of the label data of the data source when it is updated. The demand level, the higher the real-time level, the more the label data of the data source needs to be updated in real time. In addition, the type of tag data is classified based on the real-time level of tag data when it is updated. Therefore, the type of tag data can be determined according to the data source of the tag data.

As a specific implementation, the corresponding relationship between the identities and types of different data sources can be stored in the electronic device in advance. The electronic device can identify the identity of the data source, etc., after determining the data source, according to the corresponding relationship and the data source’s corresponding relationship. Identification, which determines the type of label data.

In some embodiments, the types of tag data can be divided into a first type and a second type, and the real-time level corresponding to the first type of tag data may be higher than the real-time level corresponding to the second type of tag data. Among them, the first type of label data can be label data that requires high real-time performance when updating label data, and label data with strong immediate effect. If the label data of this type is not updated in real time, it will cause the first label data to be updated. One type of label data loses its function. For example, the first type of label data can be location data, web browsing information, consumption records, web browsing records and other time-sensitive data, and the second type of label data can be user age, user occupation, user gender and other time-sensitive data. Strong data.

Step S220: When the type is the first type, buffer the tag data in the first update queue.

In some embodiments, the first type may correspond to the first update queue, the second type may correspond to the second update queue, and the data update rate corresponding to the first update queue is the data update rate corresponding to the second update queue. Therefore, if the obtained tag data is of the first type, the tag data can be cached in the first update queue; if the obtained tag data is of the second type, the tag data can be cached in the second update queue.

In some embodiments, the data update speed corresponding to the first update queue may be greater than the set speed, so that each tag data of the first type takes less time to update, thereby realizing the real-time data of the first type tag. Update. The specific value of the setting speed may not be limited. For example, the setting speed may be 2 pieces/minute, that is, two pieces of label data are updated every minute, or the time it takes to update each piece of label data is 30 seconds.

In some embodiments, step S220 may include: when the type is the first type, determining whether the current amount of data in the first update queue reaches a cache threshold; if the current amount of data does not reach the cache threshold, The tag data is cached in the first update queue.

Among them, because the tag data in the first update queue can be updated in real time, the throughput of the first update queue (that is, the amount of cached data) is small, and the tag data in it will be updated quickly, which is suitable for processing small batches. Label data. In other words, if the amount of data that can be cached in the first update queue is large and the amount of data cached in the first update queue reaches the cache threshold, the tag data at the end of the update queue will not be updated until a long time. , It cannot be updated in real time and loses its timeliness. Therefore, the amount of data that can be cached in the first update queue will not be too large, so as to ensure that the tag data at the end of the queue remains the same when there are more tag data in the first update queue. Can be updated in real time. On the contrary, the second update queue is suitable for large batches of tag data, has a higher throughput, and takes longer to update the tag data.

Therefore, when the type of tag data is the first type, before the tag data is cached in the first update queue, it can be determined whether the current amount of data in the first update queue reaches the cache threshold. Among them, the current data volume in the first update queue refers to the current data volume of the tag data that has been cached in the first update queue; the cache threshold can refer to the data volume that the first update queue can hold, or it can be smaller than the first update queue. The value of the amount of data that the update queue can hold is not limited here. After determining whether the current data volume in the first update queue reaches the cache threshold, if the current data volume does not reach the cache threshold, the tag data may be cached in the first update queue. However, if the current data volume reaches the cache threshold, it means that other tag data cannot be accommodated in the first update queue, and therefore the tag data cannot be directly cached to the first update queue.

Further, the method for updating tag data may further include: if the current data volume reaches a cache threshold, determining the cache duration of each tag data in the first update queue after being cached in the first update queue; For the first tag data in the first update queue, the buffer duration corresponding to the first tag data is greater than the set duration; after the first tag data is cleared from the first update queue, if the first update The current amount of data in the queue does not reach the cache threshold, and the tag data is cached in the first update queue.

In this way, when the current data volume reaches the cache threshold, it means that other tag data cannot be accommodated in the first update queue. At this time, the tag data whose cache duration is greater than the set duration can be determined from the first update queue as The first label data. Wherein, the cache duration of the first tag data is greater than the set duration, which means that the update speed may be slow due to current device factors, so that the first tag data has been cached for a long time without being updated, and the timeliness is lost. Therefore, the first tag data can be cleared from the first update queue, and the tag data to be updated can be cached in the first update queue, so that the tag data to be updated can be updated.

Further, the first update queue and the second update queue are located in memory. Before the clearing of the first tag data from the first update queue, the method for updating the tag data may further include: buffering the first tag data in the second update queue; or storing the first tag data in the second update queue; The first label data is stored to the local disk. It is understandable that since the first tag data cannot be updated in real time, but in order not to lose the first tag data, the first tag data can still be saved. Specifically, the first tag data can be cached in the second update queue. , So that the first tag data can be subsequently updated to the tag database, or the first tag data can be stored in a local disk, so as to achieve data retention.

In some embodiments, when the current data volume reaches the cache threshold, if the first tag data does not exist in the first update queue, the tag data to be updated can be temporarily cached to the local disk or cached in the memory. In the buffer queue, when the current data volume in the first update queue is lower than the buffer threshold, the tag data to be updated is retrieved and cached in the first update queue, so that the first update queue can still be updated relatively quickly.

In some embodiments, the method for updating tag data may further include: obtaining a user ID and tag name corresponding to the tag data; determining whether there is second tag data in the first update queue, and the second tag data Identify the tag data of the tag name corresponding to the user; if the second tag data exists in the first update queue, clear the second tag data in the first update queue.

It is understandable that before the tag data to be updated is cached in the first update queue, it can also be determined that the tag data in the first update queue and the tag data to be updated belong to the same user and have the same tag name. Therefore, the tag data to be updated can be obtained. Tag data corresponding to the user ID and tag name, and determine whether there is tag data (second tag data) that is the same as the user ID and tag name in the first update queue. If there is second tag data, it can be Clear, so as to subsequently update the latest label data with the same name to the label data of the user, so as to avoid updating the second label data that is not up to date and occupy the update time, which improves the speed of label update. For example, the tag data to be updated is the current location data with the user identification as M1, the current location data with the user identification as M1 exists in the first update queue, and the current location data in the first update queue is no longer the user identification as The latest current location data of the user of M1 loses its role as the current location data of the user. Therefore, the current location data of the user identified as M1 in the first update queue can be cleared to improve the tag update speed.

Step S230: When the type is the second type, buffer the tag data to the second update queue.

In the embodiment of the present application, when the type of the tag data to be updated is the second type, since the second type of tag data does not have a high demand for real-time performance during update, the tag data can be cached in the second update queue. It will not affect the actual function of the label data.

Step S240: Update the tag data in the update queue according to the data update speed corresponding to the update queue.

In the embodiment of the present application, step S240 can refer to the content of the foregoing embodiment, which will not be repeated here.

In an example, please refer to FIG. 6. FIG. 6 shows a schematic diagram of the principle of a method for updating tag data provided by an embodiment of the present application. In the figure, tag data with strong timeliness such as geographic location can be identified as the first Type, so as to be cached in the first buffer queue 704, while other tag data with less timeliness can be identified as the second type and cached in the second buffer queue 705, and the first buffer queue corresponds to the first update Program 706, the second buffer queue 705 corresponds to the second update program 707. The update speed of the first update program 706 to the tag data can be greater than the update speed of the second update program 707 to the tag data. The first update program 706 updates the tag data. The update speed can be greater than the set speed, and real-time update of tag data with strong timeliness such as geographic location can be realized. Among them, the first update program 706 can be implemented by tools such as Flink, SparkStreaming, Storm, and Samza.

The method for updating tag data provided by the embodiments of the present application determines the type of tag data when obtaining tag data to be updated, and then caches the tag data in the first update queue corresponding to the first type, or caches the tag data In the second update queue corresponding to the second type, the tag data in the update queue is updated according to the data update speed corresponding to the update queue. This enables label data with a high real-time level to be updated in real time, ensuring the timeliness of label data.

Please refer to FIG. 7. FIG. 7 shows a schematic flowchart of a method for updating tag data provided by another embodiment of the present application. The method for updating label data is applied to the above-mentioned electronic equipment. The following will describe the process shown in FIG. 7 in detail. The method for updating label data may specifically include the following steps:

Step S310: When the tag data to be updated is obtained, the type of the tag data is obtained. Different types of tag data have different real-time levels when updating.

In the embodiment of the present application, step S310 can refer to the content of the foregoing embodiment, which will not be repeated here.

Step S320: Determine the update queue corresponding to the type, and determine whether the data update speed corresponding to the update queue is greater than the set speed.

Step S330: If the data update speed corresponding to the update queue is greater than the set speed, obtain the remaining utilization of the processor.

In the embodiment of the present application, since the data update speed corresponding to the update queue is relatively large, the processor resources occupied during the update are also large, and if the remaining resources of the processor are small, the tag data is continuously updated at a relatively large update speed. The update may cause the operation of the electronic device to crash. Therefore, the data update speed corresponding to the update queue can be determined, and when the data update speed corresponding to the update queue is greater than the set speed, the remaining utilization rate of the processor is obtained, so as to determine whether the remaining resources of the processor are at a low level. When the data update speed corresponding to the update queue is less than or equal to the set speed, the tag data to be updated can be cached in the update queue, and the tag data to be updated is subsequently updated. Among them, the set speed can be used as a judgment basis for judging whether the label update may cause operation crash, and its specific size may not be used as a limitation.

Step S340: If the remaining utilization rate is higher than the set utilization rate, buffer the tag data to the update queue corresponding to the type.

In the embodiment of the present application, if the remaining utilization rate of the processor is higher than the set utilization rate, it can indicate that the remaining resources of the processor are more. Therefore, the data update speed corresponding to the update queue is subsequently used to update the tag data. It will not cause the operation of the electronic device to crash, so that the tag data can be cached in the update queue. Among them, the set utilization rate can be used as a basis for judging whether the operation of the electronic device will crash, and the specific size is not limited, for example, it can be 10% or 5%.

Step S350: If the remaining utilization rate is less than or equal to the set utilization rate, buffer the tag data to a target update queue, and the data update speed corresponding to the update queue is greater than the data update speed corresponding to the target update queue.

In the embodiment of the present application, if the remaining utilization rate of the processor is less than or equal to the set utilization rate, it can indicate that the remaining resources of the processor are less, so the tag data is updated subsequently using the data update speed corresponding to the update queue. It may cause the operation of electronic equipment to crash. In this case, the tag data can be cached in a target update queue with a relatively low data update speed to avoid jams and crashes when the tag data is updated.

Step S360: Update the tag data in the update queue according to the data update speed corresponding to the update queue.

In the embodiment of the present application, step S360 can refer to the content of the foregoing embodiment, which will not be repeated here.

The method for updating tag data provided by the embodiments of the present application determines the type of tag data when obtaining the tag data to be updated, and then the update queue corresponding to the type, and when the update speed of the update queue is greater than the set speed, obtain The remaining utilization rate of the processor. When the remaining utilization rate is greater than the set utilization rate, the tag data to be updated will be cached to the update queue. When the remaining utilization rate is less than or equal to the set utilization rate, the tag data to be updated will be cached. Cache to the target update queue, and then update the tag data in the update queue according to the data update speed corresponding to the update queue. This enables label data with a high real-time level to be updated in real time, guarantees the timeliness of the label data, and avoids the crash of the electronic device during operation.

Please refer to FIG. 8. FIG. 8 shows a schematic flowchart of a method for updating tag data provided by another embodiment of the present application. The method for updating label data is applied to the above-mentioned electronic equipment. The following will describe the process shown in FIG. 8 in detail. The method for updating label data may specifically include the following steps:

Step S410: When the tag data to be updated is obtained, the type of the tag data is obtained. Different types of tag data have different real-time levels when updating.

Step S420: Buffer the tag data in the update queue corresponding to the type, where different update queues correspond to different data update speeds.

In the implementation of this application, step S410 and step S420 can refer to the content of the foregoing embodiment, which will not be repeated here.

Step S430: If the type is the set type, sort all the tag data according to the type of each tag data of all the tag data in the update queue.

In some embodiments, the update queue can correspond to multiple types of tag data, that is, the electronic device can cache tag data with different real-time levels in the same update queue. For example, the electronic device can have update queue 1 and update queue 2, and the real-time level corresponding to the tag data is divided into real-time level 1, real-time level 2, real-time level 3, and real-time level 4, then real-time level 1 Tag data of real-time level 2 and real-time level 2 can be cached in update queue 1, and tag data of real-time level 3 and real-time level 4 can be cached in update queue 2. In this case, there may be multiple types of tag data (ie, multiple real-time levels of tag data) in the update queue to which the tag data to be updated is cached. In this case, the tag data can also be adjusted according to the type of tag data. The position of the data in the update queue is sorted.

In some embodiments, the real-time level corresponding to the setting type may be the highest real-time level, that is, the label data of the setting type has a very high demand for real-time performance when updating. In addition, when the electronic device updates the tag data in the update queue, it reads each tag data in turn according to the arrangement order of the tag data in the update queue, and updates each tag data, that is, the buffer queue For the principle of first-in, first-out and last-in-last-out, the label data is taken out in sequence according to the arrangement order of the label data in the update queue, and the label data is updated. Therefore, for the tag data of the set type, the tag data can be updated as soon as possible. Therefore, if the type of the tag data to be updated is the set type, the tag data can also be cached in the update queue to update the update queue. Sort the label data in.

As a way, referring to FIG. 9, step S430 may include:

Step S431A: Determine whether there is other tag data of the set type other than the tag data in the update queue.

Step S432A: If there is no other tag data of the set type in the update queue, sort the tag data to the head of the update queue.

Step S433A: If the other tag data exists in the update queue, sort the tag data to a position adjacent to the other tag data after the other tag data in the update queue.

It is understandable that if the type of the tag data to be updated is the set type, the tag data can be inserted into the queue, that is, the tag data can be inserted to the front position. In order to make the tag data to be updated at the top of the update queue as much as possible, it can be determined whether there is other tag data of a set type in the update queue. Since other tag data has a very high demand for real-time performance during update, and it is cached in the update queue earlier than the tag data to be updated, it is impossible to make the position of the tag data to be updated in the update queue closer to the position of other tag data. before. Therefore, when there is no other tag data in the update queue, the tag data to be updated can be queued to the top of the update queue, and when there are other tag data in the update queue, the tag data to be updated can be placed in the update queue. The label data is arranged after the position of other label data and is adjacent to other label data, so that the label data to be updated is in the front position as much as possible, ensuring that the label data to be updated can be updated earlier. The timeliness performance of the label data to be updated is better guaranteed.

As another way, referring to FIG. 10, step S430 may include:

Step S431B: Determine the priority corresponding to each tag data according to the type of each tag data in the update queue.

Step S432B: Sort the tag data with different priorities in all the tag data according to the order of the priority corresponding to each tag data.

Step S433B: If tag data of the same priority exists in the update queue, sort the tag data of the same priority according to the sequence of the time when the tag data is cached in the update queue.

In this way, when sorting the tag data in the update queue, it can also be sorted according to the priority of the tag data. Among them, since different types of tag data correspond to different real-time levels, the type of each tag data in the update queue can be determined according to the determined type of tag data, and the priority of each tag data can be determined according to the type. And the higher the real-time level corresponding to the tag data, the higher its priority can be. For example, the type of tag data is C1, its corresponding real-time level is D1, the type of tag data is C2, and its corresponding real-time level is D2, if D1 is greater than D2, the corresponding priority of C1 type tag data is The first priority, the priority corresponding to the C2 type tag data is the second priority, and the first priority is greater than the second priority.

After the electronic device determines the order of priority, it can sort the tag data of different priorities in all tag data in the order of priority from high to low. And for the tag data of the same priority, the tag data of the same priority is sorted according to the sequence of the time when it is cached in the update queue. As a result, the tag data to be updated can be placed at the front position in the update queue as much as possible, so that the timeliness performance of the tag data to be updated can be better guaranteed.

Step S440: Update the tag data in the update queue according to the data update speed corresponding to the update queue.

In the embodiment of the present application, when the tag data to be updated is obtained, the type of the tag data is determined, and then the tag data is cached in the update queue corresponding to the type, and the update queue is updated according to the type of the tag data in the update queue. The position of the tag data is sorted, and then the tag data in the update queue is updated according to the data update speed corresponding to the update queue, so that the speed at which the obtained tag data is updated corresponds to its corresponding real-time level. High-level label data can be updated quickly, ensuring the timeliness of label data. In addition, the tag data to be updated is made to be at the front position in the update queue as much as possible, so that the timeliness performance of the tag data to be updated is better guaranteed.

Please refer to FIG. 11, which shows a structural block diagram of a tag data updating apparatus 400 provided by an embodiment of the present application. The tag data updating device 400 includes: a type obtaining module 410, a data caching module 420, and a data updating module 430. The type obtaining module 410 is used to obtain the type of the tag data when the tag data to be updated is obtained. Different types of tag data have different real-time levels when updating; the data caching module 420 is used to The tag data is cached in the update queue corresponding to the type, wherein different update queues correspond to different data update speeds; the data update module 430 is configured to update the update queue according to the data update speed corresponding to the update queue. The tag data in is updated.

In some embodiments, referring to FIG. 12, the type obtaining module 410 may include an identification obtaining unit 411 and a first type determining unit 412. Wherein, the identification acquiring unit 411 is configured to acquire the type identification in the tag data, and the type identification is used to characterize the type of tag data; the first type determining unit 412 is configured to determine the type identification according to the type identification. Describe the type of label data.

In other embodiments, referring to FIG. 13, the type obtaining module 410 may include a data source obtaining unit 413 and a second type determining unit 414. The data source obtaining unit 413 is configured to obtain the data source of the tag data; the second type determining unit 414 is configured to determine the type of the tag data according to the data source.

In some embodiments, the data caching module 420 may include a first caching unit and a second caching unit. The first buffer unit is used for buffering the tag data to the first update queue when the type is the first type; the second buffer unit is used for buffering the tag data when the type is the second type To the second update queue, wherein the real-time level corresponding to the first type of tag data is greater than the real-time level corresponding to the second type of tag data, and the data update speed corresponding to the first update queue is greater than the The data update speed corresponding to the second update queue.

In this manner, the first caching unit may be specifically configured to: when the type is the first type, determine whether the current amount of data in the first update queue reaches the cache threshold; if the current amount of data does not reach the cache threshold, Threshold, buffer the tag data to the first update queue.

Further, the first caching unit may be further configured to: if the current amount of data reaches a caching threshold, determine the caching duration of each tag data in the first update queue after it is cached in the first update queue; and obtain the For the first tag data in the first update queue, the buffer duration corresponding to the first tag data is greater than the set duration; after the first tag data is cleared from the first update queue, if the first update queue The current amount of data in the database does not reach the cache threshold, and the tag data is cached in the first update queue.

In some embodiments, the first update queue and the second update queue are located in memory. The first cache unit may also be used to cache the first tag data in the second update queue before the first tag data is cleared from the first update queue; or to store the first tag data in the second update queue. The label data is stored on the local disk.

In some embodiments, the tag data updating device 400 may further include: a tag information acquisition module, a first tag data judgment module, and a tag data clearing module. Wherein, the tag information obtaining module is used to obtain the user identification and tag name corresponding to the tag data; the first tag data judging module is used to judge whether there is second tag data in the first update queue, and the second tag data Is the tag data that is the same as the user identification and the tag name; the tag data clearing module is used for removing the second tag data in the first update queue if the second tag data exists in the first update queue Second, the label data is cleared.

In some embodiments, the data cache module 420 may include a speed judgment unit, a utilization rate acquisition unit, and a cache execution unit. The speed judgment unit is used to judge whether the data update speed corresponding to the update queue is greater than the set speed; the utilization rate acquisition unit is used to obtain the remaining utilization rate of the processor if the data update speed corresponding to the update queue is greater than the set speed; The cache execution unit is configured to, if the remaining utilization rate is higher than the set utilization rate, cache the tag data to the update queue corresponding to the type.

In this manner, the cache execution unit may also be used to: if the remaining utilization rate is less than or equal to the set utilization rate, cache the tag data to the target update queue, and the data update speed corresponding to the update queue is greater than the The data update speed corresponding to the target update queue.

In some embodiments, the update queue corresponds to multiple types of tag data, and the device for updating tag data may further include a position sorting module. The position sorting module is configured to: after the tag data is cached in the update queue corresponding to the type, if the type is a set type, according to the type of each tag data in the update queue To sort all the tag data.

As a way, the position sorting module may be specifically used to determine whether there is other tag data of the setting type other than the tag data in the update queue; if the setting does not exist in the update queue For other tag data of the type, the tag data is sorted to the head of the update queue.

Further, the position sorting module may also be used to: if the other tag data exists in the update queue, sort the tag data after the other tag data in the update queue and be the same as the other tag data. The location of the neighbor.

As another way, the position sorting module may be specifically configured to: determine the priority corresponding to each tag data according to the type of each tag data of all tag data in the update queue; Corresponding to the high and low order of priority, the tag data of different priorities in all the tag data are sorted.

Further, the position sorting module may also be used to: according to the priority order of each tag data, after sorting the tag data of different priorities in all the tag data, if there is any tag data in the update queue The tag data of the same priority is sorted according to the sequence of the time when the tag data is cached in the update queue.

Those skilled in the art can clearly understand that, for the convenience and conciseness of description, the specific working process of the device and module described above can refer to the corresponding process in the foregoing method embodiment, which will not be repeated here.

In the several embodiments provided in this application, the coupling between the modules may be electrical, mechanical or other forms of coupling.

In addition, each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or software function modules.

In summary, by obtaining the type of tag data when obtaining the tag data to be updated, different types of tag data have different real-time levels when updating, and then the tag data is cached to the update queue corresponding to the type, and the tag data is cached in accordance with the update queue. The data update speed corresponding to the queue updates the tag data in the update queue, so that tag data of different real-time levels can be entered into different update queues, and the tag data is updated according to the data update speed corresponding to the update queue. Update to ensure the real-time update of label data.

Please refer to FIG. 14, which shows a structural block diagram of an electronic device provided by an embodiment of the present application. The electronic device 100 may be an electronic device capable of running application programs, such as a smart phone, a tablet computer, or an e-book. The electronic device 100 in this application may include one or more of the following components: a processor 110, a memory 120, and one or more application programs. One or more application programs may be stored in the memory 120 and configured to be Or multiple processors 110 execute, and one or more programs are configured to execute the method described in the foregoing method embodiment.

The processor 110 may include one or more processing cores. The processor 110 uses various interfaces and lines to connect various parts of the entire electronic device 100, and executes by running or executing instructions, programs, code sets, or instruction sets stored in the memory 120, and calling data stored in the memory 120. Various functions and processing data of the electronic device 100. Optionally, the processor 110 may adopt at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). A kind of hardware form to realize. The processor 110 may be integrated with one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a modem, and the like. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is used for rendering and drawing of display content; the modem is used for processing wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 110, but may be implemented by a communication chip alone.

The memory 120 may include random access memory (RAM) or read-only memory (Read-Only Memory). The memory 120 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 120 may include a program storage area and a data storage area, where the program storage area may store instructions for implementing the operating system and instructions for implementing at least one function (such as touch function, sound playback function, image playback function, etc.) , Instructions used to implement the following various method embodiments, etc. The data storage area can also store data (such as phone book, audio and video data, chat record data) created by the terminal 100 during use.

Please refer to FIG. 15, which shows a structural block diagram of a computer-readable storage medium provided by an embodiment of the present application. The computer-readable medium 800 stores program code, and the program code can be invoked by a processor to execute the method described in the foregoing method embodiment.

The computer-readable storage medium 800 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM, hard disk, or ROM. Optionally, the computer-readable storage medium 800 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 800 has storage space for the program code 810 for executing any method steps in the above-mentioned methods. These program codes can be read from or written into one or more computer program products. The program code 810 may be compressed in a suitable form, for example.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the application, not to limit them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions recorded in the foregoing embodiments are modified, or some of the technical features thereof are equivalently replaced; these modifications or replacements do not drive the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A method for updating label data, characterized in that the method includes:

When the label data to be updated is obtained, the type of the label data is obtained, and different types of label data have different real-time levels when being updated;

Buffering the tag data in the update queue corresponding to the type, where different update queues correspond to different data update speeds;

The tag data in the update queue is updated according to the data update speed corresponding to the update queue.
The method according to claim 1, wherein said obtaining the type of said tag data comprises:

Acquiring a type identifier in the tag data, where the type identifier is used to characterize the type of the tag data;

According to the type identification, the type of the tag data is determined.
The method according to claim 1, wherein said obtaining the type of said tag data comprises:

Acquiring the data source of the tag data;

According to the data source, the type of the tag data is determined.
The method according to any one of claims 1-3, wherein the buffering the tag data to the update queue corresponding to the type comprises:

When the type is the first type, buffer the tag data to the first update queue;

When the type is the second type, the tag data is cached in the second update queue, wherein the real-time level corresponding to the first type of tag data is greater than the real-time level corresponding to the second type of tag data Level, the data update speed corresponding to the first update queue is greater than the data update speed corresponding to the second update queue.
The method according to claim 4, wherein when the type is the first type, buffering the tag data in a first update queue comprises:

When the type is the first type, judging whether the current amount of data in the first update queue reaches a cache threshold;

If the current data volume does not reach the cache threshold, cache the tag data in the first update queue.
The method according to claim 5, wherein the method further comprises:

If the current data volume reaches the cache threshold, determine the cache duration of each tag data in the first update queue after being cached in the first update queue;

Acquiring the first tag data in the first update queue, and the buffer duration corresponding to the first tag data is greater than a set duration;

After the first tag data is cleared from the first update queue, if the current amount of data in the first update queue does not reach the cache threshold, the tag data is cached in the first update queue.
The method according to claim 6, wherein the first update queue and the second update queue are located in a memory, and before the first tag data is cleared from the first update queue, The method also includes:

Buffer the first tag data to the second update queue; or

Store the first label data to a local disk.
The method according to any one of claims 4-7, wherein the method further comprises:

Obtaining the user ID and the label name corresponding to the label data;

Determining whether there is second tag data in the first update queue, where the second tag data is tag data that is the same as the user identifier and the tag name;

If the second tag data exists in the first update queue, the second tag data in the first update queue is cleared.
The method according to any one of claims 1-8, wherein the buffering the tag data to the update queue corresponding to the type comprises:

Judging whether the data update speed corresponding to the update queue is greater than the set speed;

If the data update speed corresponding to the update queue is greater than the set speed, obtain the remaining utilization rate of the processor;

If the remaining utilization rate is higher than the set utilization rate, buffer the tag data to the update queue corresponding to the type.
The method according to claim 9, wherein the method further comprises:

If the remaining utilization rate is less than or equal to the set utilization rate, the tag data is buffered in a target update queue, and the data update speed corresponding to the update queue is greater than the data update speed corresponding to the target update queue.
The method according to any one of claims 1-10, wherein the update queue corresponds to multiple types of tag data, and after the tag data is cached in the update queue corresponding to the type, The method also includes:

If the type is the set type, sort all the tag data according to the type of each tag data of all the tag data in the update queue.
The method according to claim 11, wherein the sorting all the tag data according to the type of each tag data of all the tag data in the update queue comprises:

Judging whether there is other tag data of the set type other than the tag data in the update queue;

If there is no other tag data of the set type in the update queue, the tag data is sorted to the top of the queue in the update queue.
The method according to claim 12, wherein the method further comprises:

If the other tag data exists in the update queue, the tag data is sorted to a position next to the other tag data in the update queue after the other tag data.
The method according to claim 11, wherein the sorting all the tag data according to the type of each tag data of all the tag data in the update queue comprises:

Determine the priority corresponding to each tag data according to the type of each tag data in the update queue;

According to the priority order of each tag data, the tag data of different priorities in all the tag data are sorted.
The method according to claim 14, characterized in that, after sorting the tag data of different priorities in all the tag data according to the priority order of each tag data, the method Also includes:

If tag data of the same priority exists in the update queue, the tag data of the same priority is sorted according to the sequence of the time when the tag data is cached in the update queue.
A device for updating label data, characterized in that the device includes: a type acquisition module, a data cache module, and a data update module, wherein:

The type acquisition module is used to acquire the type of the label data when the label data to be updated is obtained, and different types of label data have different real-time levels when being updated;

The data buffer module is configured to buffer the tag data in the update queue corresponding to the type, wherein different update queues correspond to different data update speeds;

The data update module is configured to update the tag data in the update queue according to the data update speed corresponding to the update queue.
The device according to claim 16, wherein the type acquiring module comprises an identification acquiring unit and a first type determining unit, wherein:

The identification acquiring unit is used to acquire a type identification in the tag data, and the type identification is used to characterize the type of the tag data;

The first type determining unit is configured to determine the type of the tag data according to the type identifier.
The device according to claim 16, wherein the type acquisition module comprises a data source acquisition unit and a second type determination unit, wherein:

The data source obtaining unit is used to obtain the data source of the tag data;

The second type determining unit is configured to determine the type of the tag data according to the data source.
An electronic device, characterized in that it comprises:

One or more processors;

Memory

One or more application programs, wherein the one or more application programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to execute such as The method of any one of claims 1-15.
A computer-readable storage medium, wherein the computer-readable storage medium stores program code, and the program code can be called by a processor to execute the method according to any one of claims 1-15 .