CN114365111A

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

Info

Publication number: CN114365111A
Application number: CN201980100127.1A
Authority: CN
Inventors: 黄江伟
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd; Shenzhen Huantai Technology Co Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd; Shenzhen Huantai Technology Co Ltd
Priority date: 2019-11-08
Filing date: 2019-11-08
Publication date: 2022-04-15
Also published as: WO2021087970A1

Abstract

The updating method of the label data comprises the following steps: when the tag data to be updated is obtained, the type of the tag data is obtained, and the real-time levels of different types of tag data are different during updating (S110); caching the label 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 the data update speed corresponding to the update queue (S130). The method can realize real-time update of the tag data.

Description

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

Technical Field

The present application relates to the field of data processing technologies, and in particular, to a method and an apparatus for updating tag data, an electronic device, and a storage medium.

Background

With the rapid development of network information technology, big data technology appears in daily life more frequently. A more typical application scheme is an information recommendation technology, in which recommendation is usually performed according to a user tag, and the user tag plays a very important role in the information recommendation technology, so that updating of the user tag is a key in the information recommendation technology.

Disclosure of Invention

In view of the foregoing problems, the present application provides a method and an apparatus for updating tag data, an electronic device, and a storage medium.

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

In a second aspect, an embodiment of the present application provides an apparatus for updating tag data, where the apparatus includes: the device comprises a type acquisition module, a data cache module and a data updating module, wherein the type acquisition module is used for acquiring the type of tag data when the tag data to be updated is acquired, and the real-time levels of different types of tag data are different during updating; the data caching module is used for caching the tag data to the updating queues corresponding to the types, wherein different updating queues correspond to different data updating speeds; and the data updating module is used for updating the label data in the updating queue according to the data updating speed corresponding to the updating 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 applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method of updating tag data as provided in the first aspect above.

In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, where a program code is stored in the computer-readable storage medium, and the program code may be called by a processor to execute the method for updating tag data provided in the first aspect.

According to the scheme, when the tag data to be updated are obtained, the types of the tag data are obtained, the real-time levels of different types of tag data during updating are different, then the tag data are cached to the updating queue corresponding to the types, the tag data in the updating queue are updated according to the data updating speed corresponding to the updating queue, therefore, the tag data with different real-time levels can enter different updating queues, the tag data are updated according to the data updating speed corresponding to the updating queue, and the real-time performance of the tag data updating is guaranteed.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 shows a schematic diagram of a tag data update provided in 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 a method for updating tag data according to another embodiment of the present application.

Fig. 5 shows another flowchart of step S210 in a method for updating tag data according to another embodiment of the present application.

Fig. 6 is a schematic diagram illustrating an updating method of tag data according to 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 still another embodiment of the present application.

Fig. 9 shows a flowchart of step S430 in the updating method of tag data according to still another embodiment of the present application.

Fig. 10 shows another flowchart of step S430 in the updating method of tag data according to still another embodiment provided in the present application.

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

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

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

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

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

Detailed Description

In order to make the technical solutions better understood by those skilled in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.

With the rapid development of information technology, the internet brings more and more convenience to the life and work of people. The information recommendation technology based on the big data technology can recommend contents required by people and can well meet the use requirements. For example, people can shop, entertain and release personal status information (e.g., send microblogs) through the internet, and merchants can acquire the contents of the consumption, the entertainment, the personal status information and the like of people through the internet, so that the demands of the masses can be more comprehensively known, and then recommendation services can be provided for the people according to the demands of the masses. The business is also profitable while providing recommendation service for people.

In the information recommendation technology, user tags are mainly applied, so that recommended contents can meet the requirements of users. The user label is mainly data for reflecting information such as social attributes, living habits and consumption behaviors of the user, and the user label is a feature identifier obtained by analyzing user information. The user label continuously updates the label data, so that the accuracy of the user label can be ensured.

In conventional techniques, tag data is primarily stored in a database, and electronic devices that manage user tags typically collect tag data from different data sources and write the tag data to the tag database. The data source may be a server, a mobile terminal, etc., and is not limited herein.

In the conventional technology, all label data are generally processed in a unified manner, when the label data arrive, data are processed in an offline manner, and after all offline calculation of the data is completed, a storage or update request is uniformly sent to a label management system, so that when a large amount of data are updated, aggregation processing can be efficiently performed, and the pressure on the label management system is reduced.

The inventor finds that the updating scheme of the tag data in the traditional technology cannot meet the requirement of updating the tag data with more frequent updating. For example, the geographical location is updated according to the conventional scheme, because the time of offline is long, there is a case that the user actually moves to another place and actually writes to the previous geographical location of the tag database, and if the previous geographical location is reused for processing, the service is not beneficial to use. For example, as shown in fig. 1, when the geographic location number and other data are acquired (data a and data B), the geographic location number and other data are aggregated together, and enter the same buffer queue 701, and then are updated into the tag storage system 703 by the tag update program 702 in a unified manner.

In view of the above problems, the inventor provides a method and an apparatus for updating tag data, an electronic device, and a storage medium, which are provided in this embodiment of the present application, and when tag data to be updated is acquired, the tag data is cached in an update queue corresponding to a type of the tag data according to the type of the tag data, and the tag data is updated according to a data update speed corresponding to the update queue, so as to ensure real-time performance of updating the tag data. The specific updating method of the tag data is described in detail in the following embodiments.

Referring to fig. 2, fig. 2 is a schematic flowchart illustrating a method for updating tag data according to an embodiment of the present application. The updating method of the label data is used for enabling the label data with different real-time levels to enter different updating queues, updating the label data according to the data updating speed corresponding to the updating queues and ensuring the real-time performance of the label data updating. In a specific embodiment, the method for updating the tag data is applied to the updating apparatus 400 for the tag data shown in fig. 11 and the electronic device 100 (fig. 14) configured with the updating apparatus 400 for the tag data. The following will describe a specific flow of the present embodiment by taking an electronic device as an example, and it is understood that the electronic device applied in the present embodiment may be a server, a mobile terminal, and the like, and is not limited herein. As will be described in detail with respect to the flow shown in fig. 2, the method for updating the tag 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 the real-time levels of different types of tag data are different during updating.

In this embodiment of the application, the electronic device may manage tag data of a user, and the tag data managed by the electronic device may originate from a data source. The data source may be a server, a mobile terminal, or the like, and is not limited herein. The electronic device may obtain tag data from a data source to update the tag data of the user. The tag data refers to data corresponding to a tag, and may specifically be user data corresponding to the tag. For example, the career of the user a at the first time is a student, the career of the user a at the second time is a teacher, the data corresponding to the career in the tag of the user a at the first time is the student, and the data corresponding to the career in the tag of the user a at the second time is the teacher. Since the tag data of the user changes with the passage of time, the tag data of the user needs to be updated continuously so that the tag data of the user can be matched with the latest state of the user, and therefore, the service meeting the requirements can be provided for the user according to the tag data.

In some embodiments, the electronic device may actively acquire the tag data to be updated from the data source, and may also receive the tag data to be updated sent by the data source. The tag data to be updated refers to the obtained tag data that needs to be written into the database of the tag data, and may also be understood as tag data for updating the user tag.

In some embodiments, the electronic device may obtain tag data to be updated from a data source on a timed or non-timed basis. For example, the electronic device may obtain the tag data to be updated from the data source at preset intervals, and for example, the electronic device may receive the tag data to be updated from the data source in real time.

In the embodiment of the application, when the electronic device obtains the tag data to be updated, the electronic device may determine the type of the tag data to be updated. The real-time levels of different types of tag data during updating are different, wherein the real-time level of the tag data during updating can indicate the level of the tag data required for real-time performance during updating, and the higher the real-time level is, the more the tag data needs to be updated in real time. For example, the types of the tag data include type a, type B, and type C, and then the real-time levels corresponding to the tag data of type a, type B, and type C are different from each other, the real-time level corresponding to the tag data of type a may be greater than the real-time level corresponding to the tag data of type B, and the real-time level corresponding to the tag data of type B may be greater than the real-time level corresponding to the tag data of type C.

In some embodiments, the types of the tag data may be classification results obtained by classifying different tag data in advance according to different levels of real-time performance corresponding to the tag data, each classification result may correspond to one type, and the levels of real-time performance corresponding to tag data belonging to the same type may be the same. For example, the positioning position of the user, the web browsing information of the user, and the like have very strong real-time requirements for updating, and the real-time level is at the first level, so that the positioning position, the web browsing information, and the like can be taken as one type; the real-time requirements of the user on dining, consumption amount and the like during updating are strong, the real-time level of the user is at the second level, and the user can take the dining, consumption amount and the like as one type; the occupation and age of the user are not strongly required for real-time performance during updating, and the real-time performance level is at the third level, so the occupation and age of the user can be regarded as a type, where the order of the first level, the second level, and the third level is sequentially decreasing, which is, of course, the above is merely an example and does not represent a limitation on a specific type.

In some embodiments, the type of the tag data may be pre-stored in the electronic device, and the electronic device may determine the type of the tag data by identifying field data in the tag data, a data source of the source, a user identifier, and the like, which is not limited herein.

Step S120: and caching the label data to an updating queue corresponding to the type, wherein different updating queues correspond to different data updating speeds.

In this embodiment of the present application, a plurality of update queues may be created in advance in a memory of an electronic device, where the update queues are used to cache tag data to be updated. Moreover, 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 may not be limited. For example, the types corresponding to the tag data include a first type, a second type, and a third type, and then three update queues may be created in advance in the electronic device, where 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 a speed in a process of subsequently taking out the tag data from the update queue and updating the tag data.

In some embodiments, since different update queues correspond to different types of tag data, and the real-time levels of the different types of tag data at the time of update are different, the data update speed corresponding to an update queue may correspond to the real-time level of the corresponding type of tag data at the time of update, so that the update queue may meet the real-time requirement of the corresponding type of tag data at the time of update. Specifically, the higher the real-time level of the type of tag data corresponding to the update queue is, the faster the data update speed corresponding to the update queue is, so that the tag data with high real-time level can be quickly updated, and the timeliness of the tag data is ensured.

In the embodiment of the application, after determining the type corresponding to the tag data to be updated, the electronic device may determine, according to the type corresponding to the tag data, an update queue corresponding to the type from a plurality of update queues created in advance. The update queue corresponding to the type determined by the electronic device is used for caching the obtained tag data, and the electronic device may cache the tag data obtained in step S110 in the update queue corresponding to the type, so as to update the obtained tag data subsequently.

In some embodiments, the data update speed corresponding to different update queues may be controlled according to the speed of fetching the tag data from the update queue and the speed of updating the tag data into the tag database. Of course, the way of implementing different update queues corresponding to different update speeds may not be limited.

Step S130: and updating the label data in the update queue according to the data update speed corresponding to the update queue.

In this embodiment of the present application, after the obtained tag data is cached in the corresponding update queue, the tag data in the update queue may be updated according to the data update speed corresponding to the update queue, so that the update speed of the obtained tag data corresponds to the corresponding real-time level. And the higher the real-time level of the type of the label data corresponding to the update queue is, the higher the data update speed corresponding to the update queue is, so that the label data with high real-time level can be updated quickly, and the timeliness of the label data is guaranteed. In addition, as the fact that the electronic equipment occupies more resources due to the fact that the high data updating speed is guaranteed, the updating speed of all the updating queues in the electronic equipment does not correspond to the high data updating speed, for the tag data with the low real-time level, the updating queues with the relatively low data updating speed are entered, and not all the tag data enter the updating queues with the relatively high data updating speed, the resources of the electronic equipment cannot be occupied by the updating tasks of the tag data, and the resources of the electronic equipment are effectively utilized.

According to the updating method of the tag data, when the tag data to be updated is obtained, the type of the tag data is determined, then the tag data is cached into the updating queue corresponding to the type, and then the tag data in the updating queue is updated according to the data updating speed corresponding to the updating queue, so that the updating speed of the obtained tag data corresponds to the real-time level corresponding to the updating speed, the tag data with high real-time level can be updated quickly, and the timeliness of the tag data is guaranteed.

Referring to fig. 3, fig. 3 is a schematic flowchart illustrating a method for updating tag data according to another embodiment of the present application. The method is applied to the electronic device, and will be described in detail with reference to the flow shown in fig. 3, where the method for updating the tag data specifically includes the following steps:

step S210: when the tag data to be updated is obtained, the type of the tag data is obtained, and the real-time levels of different types of tag data are different during updating.

In this embodiment of the application, the type of the tag data may correspond to a type identifier of the tag data, or may correspond to a data source of the tag data. When the electronic device obtains the type of the tag data, the type identification of the tag data or the data source corresponding to the tag data may be determined.

In an example, each tag data may include a three-stage identity, where the three-stage identity is composed of an identifier a, an identifier b, and an identifier c, the identifier a may be used to indicate a large class to which the tag data belongs (for example, the large class includes a personal type and a family type), the identifier b is used to indicate a type corresponding to a real-time level, the type corresponding to the real-time level may be determined by the identifier b, and the identifier c may be used to indicate a tag name. For example, the types of the tag data are classified into a first type and a second type, b1 may represent the first type, and b2 may represent the second type. Of course, the above is merely an example and does not represent a limitation on the actual type identifier.

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

step S211A: obtaining a type identifier in the tag data, wherein the type identifier is used for representing the type of the tag data;

step S212A: and determining the type of the tag data according to the type identifier.

It will be appreciated that type identification may be included in the tag data. The type identifier is located in a set field of the tag data, the electronic device can obtain the type identifier of the tag data by obtaining data of the set field in the tag data, and after the electronic device obtains the type identifier of the tag data, the type of the tag data can be determined according to the type identifier.

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

step S211B: acquiring a data source of the label data;

step S212B: and determining the type of the tag data according to the data source.

In some embodiments, the real-time level of the tag data of different data sources during updating may be different, and the real-time level of the tag data of a data source during updating may refer to a level of a requirement of the tag data of the data source for real-time during updating, where the higher the real-time level is, the more the tag data of the data source needs to be updated in real time. In addition, the type of the tag data is divided and determined according to the real-time level of the tag data during updating, so that the type of the tag data can be determined according to the data source of the tag data.

As a specific implementation manner, the correspondence between the identifiers and the types of the different data sources may be stored in the electronic device in advance, and after the electronic device determines the data source by identifying the identifier of the data source, the type of the tag data may be determined according to the correspondence and the identifier of the data source.

In some embodiments, the types of the tag data may be classified 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. The first type of tag data may be tag data with a high real-time requirement when updating tag data, i.e., tag data with high real-time performance, and if the type of tag data is not updated in real time, the first type of tag data may lose its effect. For example, the first type of tag data may be location data, web browsing information, consumption records, web browsing records, and the like, which are highly time-efficient, and the second type of tag data may be data which is not highly time-efficient, such as user age, user occupation, user gender, and the like.

Step S220: and when the type is the first type, caching the tag data to a first updating queue.

In some embodiments, the first type may correspond to a first update queue, the second type may correspond to a second update queue, and the first update queue may correspond to a data update rate and the second update queue may correspond to a data update rate. Therefore, if the obtained tag data is of the first type, the tag data may be buffered to a first update queue; if the obtained tag data is of the second type, the tag data may be buffered to a 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 first type of tag data takes less time when being updated, thereby implementing real-time update of the first type of tag data. The specific value of the set speed may not be limited, and for example, the set speed may be 2 bars/minute, that is, two pieces of tag data are updated every minute, or the time taken for updating each piece of tag data may be 30 seconds.

In some embodiments, step S220 may include: when the type is a first type, judging whether the current data volume in the first updating queue reaches a cache threshold value; and if the current data volume does not reach a cache threshold value, caching the tag data to a first updating queue.

In order to update the tag data in the first update queue in real time, the throughput (i.e., the amount of cacheable data) of the first update queue is small, and the tag data therein will be updated soon, which is suitable for processing small batches of tag data. That is, if the amount of data cacheable by the first update queue is large and the amount of data buffered in the first update queue reaches the buffer threshold, the tag data at the end of the update queue can be updated only after a long time, but cannot be updated in real time, and the timeliness of the tag data is lost, so that the amount of data cacheable by the first update queue is not too large, and it is ensured that the tag data at the end of the queue can still be updated in real time when there is a large amount of tag data in the first update queue. In contrast, the second update queue is suitable for a large amount of tag data, has a higher throughput, and takes a longer time to update the tag data.

Thus, when the type of the tag data is the first type, it may be determined whether a current amount of data in the first update queue reaches a buffering threshold before buffering the tag data in the first update queue. The current data volume in the first update queue refers to the data volume of the tag data cached in the current first update queue; the buffering threshold may refer to a size of a data amount that the first update queue can hold, or may be a numerical value smaller than the size of the data amount that the first update queue can hold, which is not limited herein. After determining whether the current amount of data in the first update queue reaches the buffering threshold, the tag data may be buffered in the first update queue if the current amount of data does not reach the buffering threshold. And if the current data volume reaches the buffer threshold value, the tag data cannot be directly buffered to the first update queue because the tag data cannot be accommodated in the first update queue.

Further, the method for updating the tag data may further include: if the current data volume reaches a cache threshold value, determining the cache duration of each tag data in the first update queue after the tag data is cached in the first update queue; acquiring first tag data in the first updating queue, wherein the cache duration corresponding to the first tag data is longer than a set duration; after the first tag data is cleared from the first updating queue, if the current data volume in the first updating queue does not reach the cache threshold value, caching the tag data into the first updating queue.

In this way, when the current data amount reaches the buffer threshold, it indicates that other tag data cannot be accommodated in the first update queue, and at this time, the tag data whose buffer duration is greater than the set duration may be determined from the first update queue as the first tag data. If the cache duration of the first tag data is longer than the set duration, it indicates that the update speed is slow due to the current device factor, so that the first tag data is cached for a long time and is not 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 buffered 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 the memory. Before the clearing the first tag data from the first update queue, the method for updating the tag data may further include: caching the first tag data to the second update queue; or storing the first tag data to a local disk. It can be understood that, since the first tag data cannot be updated in real time, in order to avoid the first tag data from being lost, the first tag data may still be stored, specifically, the first tag data may be cached in the second update queue, so that the first tag data may be subsequently updated to the tag database, or the first tag data may be stored in the local disk, so as to implement the data retention.

In some embodiments, when the current data amount reaches the cache threshold, if the first tag data does not exist in the first update queue, the tag data to be updated may be temporarily cached in the local disk or in the buffer queue in the memory, and when the current data amount in the first update queue is lower than the cache threshold, the tag data to be updated is taken out and then cached in the first update queue, so that the first update queue may still be updated faster.

In some embodiments, the method for updating tag data may further include: acquiring a user identifier and a label name corresponding to the label data; judging whether second label data exists in the first updating queue or not, wherein the second label data is label data of the label name corresponding to the user identifier; and clearing the second label data in the first updating queue if the second label data exists in the first updating queue.

It can be understood that before the tag data to be updated is cached in the first update queue, it may be further determined that the tag data to be updated in the first update queue belongs to the same user and has the same tag name as the tag data to be updated, so that the user identifier and the tag name corresponding to the tag data to be updated may be obtained, and it may be determined whether the tag data (second tag data) identical to the user identifier and the tag name exists in the first update queue, and if the second tag data exists, the second tag data may be cleared, so that the latest tag data having the same name is subsequently updated to the tag data of the user, so as to avoid updating the second tag data which is not the latest, occupy the update time, and improve the tag update speed. For example, the tag data to be updated is the current location data of the user identifier M1, the current location data of the user identifier M1 exists in the first update queue, and for the current location data in the first update queue, the latest current location data of the user not identified as M1 is lost, so that the current location data of the user identified as M1 existing in the first update queue can be cleared, and the tag update speed is increased.

Step S230: and when the type is a second type, caching the label data to a second updating queue.

In this embodiment of the application, when the type of the tag data to be updated is the second type, the tag data may be buffered in the second update queue without affecting the actual effect of the tag data because the real-time requirement of the tag data of the second type for the update is not high.

Step S240: and updating the label 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 may refer to the contents of the foregoing embodiments, which are not described herein again.

In an example, please refer to fig. 6, fig. 6 shows a schematic diagram of a method for updating tag data according to an embodiment of the present application, in which tag data with stronger timeliness, such as geographic location, may be identified as a first type and buffered in a first buffer queue 704, and other tag data with weaker timeliness may be identified as a second type and buffered in a second buffer queue 705, and the first buffer queue corresponds to a first updating program 706, and the second buffer queue 705 corresponds to a second updating program 707, and an updating speed of the first updating program 706 for tag data may be greater than an updating speed of the second updating program 707 for tag data, and an updating speed of the first updating program 706 for tag data may be greater than a set speed, so as to implement real-time updating of tag data with stronger timeliness, such as geographic location. The first update program 706 may be implemented by a tool such as Flink, SparkStreaming, Storm, and Samza.

According to the updating method of the tag data provided by the embodiment of the application, when the tag data to be updated is obtained, the type of the tag data is determined, then the tag data is cached in a first updating queue corresponding to the first type, or the tag data is cached in a second updating queue corresponding to the second type, and then the tag data in the updating queue is updated according to the data updating speed corresponding to the updating queue. Therefore, the tag data with high real-time level can be updated in real time, and the timeliness of the tag data is guaranteed.

Referring to fig. 7, fig. 7 is a flowchart illustrating a method for updating tag data according to another embodiment of the present application. The method for updating tag data is applied to the electronic device, and will be described in detail with reference to the flow shown in fig. 7, where the method for updating tag 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, and the real-time levels of different types of tag data are different during updating.

In the embodiment of the present application, the step S310 may refer to the contents of the foregoing embodiments, and is not described herein again.

Step S320: and determining the updating queue corresponding to the type, and judging whether the data updating speed corresponding to the updating queue is greater than the set speed.

Step S330: and if the data updating speed corresponding to the updating queue is greater than the set speed, acquiring the residual utilization rate of the processor.

In the embodiment of the application, because the data update speed corresponding to the update queue is higher, more resources of the processor are occupied during updating, and if the remaining resources of the processor are less, the tag data is continuously updated at a higher update speed, which may cause operation crash of the electronic device. Therefore, the data updating speed corresponding to the updating queue can be determined, and when the data updating speed corresponding to the updating 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 lower level. And when the data updating speed corresponding to the updating queue is less than or equal to the set speed, the tag data to be updated can be cached to the updating queue, and the tag data to be updated is updated subsequently. The set speed may be used as a criterion for determining whether the tag update may cause the operation crash, and the specific size may not be limited.

Step S340: and if the residual utilization rate is higher than the set utilization rate, caching the tag data to an update queue corresponding to the type.

In this embodiment of the application, if the remaining utilization rate of the processor is higher than the set utilization rate, it may be indicated that more remaining resources of the processor are available, and therefore, the tag data is updated at the data update speed corresponding to the update queue subsequently, and the electronic device is not caused to run down, so that the tag data may be cached in the update queue. The set utilization rate may be used as a criterion for determining whether the operation of the electronic device is broken down, and the specific size may not be limited, and may be, for example, 10% or 5%.

Step S350: and if the residual utilization rate is less than or equal to the set utilization rate, caching the tag data to a target updating queue, wherein the data updating speed corresponding to the updating queue is greater than the data updating speed corresponding to the target updating queue.

In this embodiment of the application, if the remaining utilization rate of the processor is less than or equal to the set utilization rate, it may indicate that the remaining resources of the processor are less, and therefore, the tag data is updated at the data update speed corresponding to the update queue subsequently, which may cause the electronic device to crash. In this case, the tag data may be cached in a target update queue with a relatively low data update speed, so as to avoid the jamming and breakdown caused by updating the tag data.

Step S360: and updating the label 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 may refer to the contents of the foregoing embodiments, and is not described herein again.

The method for updating tag data provided in the embodiment of the application determines the type of the tag data when the tag data to be updated is obtained, then updates the queue corresponding to the type, obtains the remaining utilization rate of the processor when the update speed of the update queue is greater than the set speed, caches the tag data to be updated to the update queue only when the remaining utilization rate is greater than the set utilization rate, caches the tag data to be updated to the target update queue when the remaining utilization rate is less than or equal to the set utilization rate, and updates the tag data in the update queue according to the data update speed corresponding to the update queue. Therefore, the label data with high real-time level can be updated in real time, the timeliness of the label data is guaranteed, and the crash of the electronic equipment during operation is avoided.

Referring to fig. 8, fig. 8 is a flowchart illustrating a method for updating tag data according to still another embodiment of the present application. The method for updating tag data is applied to the electronic device, and will be described in detail with reference to the flow shown in fig. 8, where the method for updating tag 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, and the real-time levels of different types of tag data are different during updating.

Step S420: and caching the label data to an updating queue corresponding to the type, wherein different updating queues correspond to different data updating speeds.

In the implementation of the present application, step S410 and step S420 may refer to the content of the foregoing embodiments, and are not described herein again.

Step S430: and if the type is a set type, sequencing all the label data according to the type of each label data of all the label data in the update queue.

In some embodiments, the update queue may correspond to multiple types of tag data, that is, the electronic device may cache tag data with different levels of real-time performance in the same update queue. For example, an update queue 1 and an update queue 2 may be established in the electronic device, and the real-time levels corresponding to the tag data are divided into a real-time level 1, a real-time level 2, a real-time level 3, and a real-time level 4, so that the tag data of the real-time level 1 and the real-time level 2 may be buffered in the update queue 1, and the tag data of the real-time level 3 and the real-time level 4 may be buffered in the update queue 2. In this way, there may be multiple types of tag data (i.e., multiple real-time level tag data) in the update queue to which the tag data to be updated is cached.

In some embodiments, the real-time performance level corresponding to the set type may be the highest real-time performance level, that is, the tag data of the set type has a very high real-time performance requirement for updating. In addition, when the electronic device updates the tag data in the update queue, each tag data is sequentially read according to the arrangement sequence of the tag data in the update queue, and each tag data is updated, that is, the buffer queue is in a first-in first-out, first-in and last-out principle, the tag data is sequentially taken out according to the arrangement sequence of the tag data in the update queue, and the tag data is updated. Therefore, for the tag data of the set type, the tag data can be updated reasonably as early as possible, so that if the type of the tag data to be updated is the set type, the tag data can be buffered in the update queue, and the tag data in the update queue can be sorted.

In one way, referring to fig. 9, step S430 may include:

step S431A: and judging whether other tag data of the set type except the tag data exists in the updating queue.

Step S432A: and if the other tag data of the set type do not exist in the updating queue, the tag data is arranged to the head of the updating queue.

Step S433A: and if the other label data exist in the updating queue, the label data is arranged at a position which is behind the other label data and is adjacent to the other label data in the updating queue.

It is understood that if the type of the tag data to be updated is a set type, the tag data may be queued, that is, inserted to a front position. In order to make the tag data to be updated in the update queue at the top position as much as possible, it can be determined whether there is other tag data of a set type in the update queue. Since the real-time requirement of other tag data for updating is also very high and the tag data to be updated is buffered to the update queue earlier than the tag data to be updated, the position of the tag data to be updated in the update queue cannot be made earlier than the position of other tag data. Therefore, when other tag data do not exist in the update queue, the tag data to be updated can be arranged to the head of the update queue, and when other tag data exist in the update queue, the tag data to be updated can be arranged to the position behind the other tag data and adjacent to the other tag data in the update queue, so that the tag data to be updated is located at the front position as far as possible, the tag data to be updated can be updated earlier, and the timeliness of the tag data to be updated can be better guaranteed.

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

step S431B: and determining the priority corresponding to each label data according to the type of each label data in the update queue.

Step S432B: and sorting the label data with different priorities in all the label data according to the high-low order of the priority corresponding to each label data.

Step S433B: and if the label data with the same priority exist in the updating queue, sorting the label data with the same priority according to the sequence of the time of caching the label data to the updating queue.

In this manner, when sorting the tag data in the update queue, the tag data may be sorted according to the priority of the tag data. The real-time levels corresponding to different types of label data are different, so that the type of each label data in the update queue can be determined according to the determined type of the label data, and the priority of each label data is determined according to the type. And the higher the real-time level corresponding to the tag data is, the higher the priority thereof may be. For example, the type of tag data is C1, the corresponding real-time level is D1, the type of tag data is C2, the corresponding real-time level is D2, if D1 is greater than D2, the priority corresponding to the tag data of C1 type is a first priority, the priority corresponding to the tag data of C2 type is a second priority, and the first priority is greater than the second priority.

After determining the order of the priority levels, the electronic device may sort the tag data with different priority levels in all the tag data according to the order of the priority levels from high to low. And for the label data with the same priority, sorting the label data with the same priority according to the sequence of the time from the cache to the update queue. Therefore, the label data to be updated can be positioned at the front position in the updating queue as far as possible, and the timeliness of the label data to be updated is better ensured.

Step S440: and updating the label data in the update queue according to the data update speed corresponding to the update queue.

In the embodiment of the application, when the tag data to be updated is obtained, the type of the tag data is determined, then the tag data is cached in the updating queue corresponding to the type, the positions of the tag data in the updating queue are sequenced according to the type of the tag data in the updating queue, and then the tag data in the updating queue is updated according to the data updating speed corresponding to the updating queue, so that the obtained updating speed of the tag data corresponds to the real-time level corresponding to the updating speed, therefore, the tag data with high real-time level can be updated quickly, and the timeliness of the tag data is guaranteed. In addition, the label data to be updated is positioned at the front position in the updating queue as far as possible, so that the timeliness of the label data to be updated is better ensured.

Referring to fig. 11, a block diagram of a tag data updating apparatus 400 according to an embodiment of the present disclosure is shown. The apparatus 400 for updating tag data includes: a type obtaining module 410, a data caching module 420, and a data updating module 430. The type obtaining module 410 is configured to obtain the type of the tag data when obtaining the tag data to be updated, where the real-time levels of different types of tag data during updating are different; the data caching module 420 is configured to cache the tag data to an update queue corresponding to the type, where different update queues correspond to different data update speeds; the data updating module 430 is configured to update the tag data in the update queue according to a data updating speed corresponding to the update queue.

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. The identifier obtaining unit 411 is configured to obtain a type identifier in the tag data, where the type identifier is used to represent a type of the tag data; the first type determining unit 412 is configured to determine the type of the tag data according to the type identifier.

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 a 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 cache unit is used for caching the tag data to a first updating queue when the type is a first type; the second cache unit is configured to cache the tag data to a second update queue when the type is a second type, where a real-time level corresponding to the tag data of the first type is greater than a real-time level corresponding to the tag data of the second type, and a data update speed corresponding to the first update queue is greater than a data update speed corresponding to the second update queue.

In this manner, the first cache unit may be specifically configured to: when the type is a first type, judging whether the current data volume in the first updating queue reaches a cache threshold value; and if the current data volume does not reach a cache threshold value, caching the tag data to a first updating queue.

Further, the first cache unit may be further configured to: if the current data volume reaches a cache threshold value, determining the cache duration of each tag data in the first update queue after the tag data is cached in the first update queue; acquiring first tag data in the first updating queue, wherein the cache duration corresponding to the first tag data is longer than a set duration; after the first tag data is cleared from the first updating queue, if the current data volume in the first updating queue does not reach the cache threshold value, caching the tag data into the first updating queue.

In some embodiments, the first update queue and the second update queue are located in memory. The first buffer unit may be further configured to buffer the first tag data to the second update queue before the first tag data is cleared from the first update queue; or storing the first tag data to a local disk.

In some embodiments, the apparatus 400 for updating tag data may further include: the device comprises a tag information acquisition module, a first tag data judgment module and a tag data clearing module. The tag information acquisition module is used for acquiring a user identifier and a tag name corresponding to the tag data; the first tag data judging module is used for judging whether second tag data exists in the first updating queue or not, wherein the second tag data is the same as the user identifier and the tag name; the tag data clearing module is configured to clear the second tag data in the first update queue if the second tag data exists in the first update queue.

In some embodiments, the data caching module 420 may include a speed determination unit, a utilization rate obtaining unit, and a cache execution unit. The speed judging unit is used for judging whether the data updating speed corresponding to the updating queue is greater than a set speed or not; the utilization rate obtaining unit is used for obtaining the residual utilization rate of the processor if the data updating speed corresponding to the updating queue is greater than the set speed; and the cache execution unit is used for caching the tag data to the update queue corresponding to the type if the residual utilization rate is higher than the set utilization rate.

In this manner, the cache execution unit may be further configured to: and if the residual utilization rate is less than or equal to the set utilization rate, caching the tag data to a target updating queue, wherein the data updating speed corresponding to the updating queue is greater than the data updating speed corresponding to the target updating queue.

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

As one way, the position sorting module may be specifically configured to: judging whether other tag data of the set type except the tag data exists in the updating queue; and if the other tag data of the set type do not exist in the updating queue, the tag data is arranged to the head of the updating queue.

Further, the position sorting module may be further configured to: and if the other label data exist in the updating queue, the label data is arranged at a position which is behind the other label data and is adjacent to the other label data in the updating queue.

As another way, the position sorting module may be specifically configured to: determining the priority corresponding to each label data according to the type of each label data of all the label data in the updating queue; and sorting the label data with different priorities in all the label data according to the high-low order of the priority corresponding to each label data.

Further, the position sorting module may be further configured to: and after sorting the label data with different priorities in all the label data according to the high-low sequence of the priority corresponding to each label data, if the label data with the same priority exists in the updating queue, sorting the label data with the same priority according to the sequence of the time for caching the label data to the updating queue.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described apparatuses and modules may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

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

In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.

In summary, when the tag data to be updated is obtained, the types of the tag data are obtained, the real-time levels of different types of tag data are different during updating, then the tag data are cached in the updating queue corresponding to the types, and the tag data in the updating queue is updated according to the data updating speed corresponding to the updating queue, so that the tag data with different real-time levels can enter different updating queues, the tag data is updated according to the data updating speed corresponding to the updating queue, and the real-time performance of the tag data updating is ensured.

Referring to fig. 14, a block diagram of an electronic device according to an embodiment of the present application is shown. The electronic device 100 may be a smart phone, a tablet computer, an electronic book, or other electronic devices capable of running an application program. The electronic device 100 in the present application may include one or more of the following components: a processor 110, a memory 120, and one or more applications, wherein the one or more applications may be stored in the memory 120 and configured to be executed by the one or more processors 110, the one or more programs configured to perform a method as described in the aforementioned method embodiments.

Processor 110 may include one or more processing cores. The processor 110 connects various parts within the overall electronic device 100 using various interfaces and lines, and performs various functions of the electronic device 100 and processes data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 120 and calling data stored in the memory 120. Alternatively, the processor 110 may be implemented in hardware using at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 110 may integrate one or more of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing display content; the modem is used to handle wireless communications. It is understood that the modem may not be integrated into the processor 110, but may be implemented by a communication chip.

The Memory 120 may include a Random Access Memory (RAM) or a Read-Only Memory (Read-Only Memory). The memory 120 may be used to store instructions, programs, code sets, or instruction sets. The memory 120 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for implementing at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing various method embodiments described below, and the like. The storage data area may also store data created by the terminal 100 in use, such as a phonebook, audio-video data, chat log data, and the like.

Referring to fig. 15, a block diagram of a computer-readable storage medium according to an embodiment of the present application is shown. The computer-readable medium 800 has stored therein a program code that can be called by a processor to execute the method described in the above-described method embodiments.

The computer-readable storage medium 800 may be an electronic memory such as a flash memory, an EEPROM (electrically erasable programmable read only memory), an EPROM, a hard disk, or a ROM. Alternatively, the computer-readable storage medium 800 includes a non-volatile computer-readable storage medium. The computer readable storage medium 800 has storage space for program code 810 to perform any of the method steps of the method described above. The program code can be read from or written to one or more computer program products. The program code 810 may be compressed, for example, in a suitable form.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not necessarily depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

A method for updating tag data, the method comprising:

when the tag data to be updated is obtained, the type of the tag data is obtained, and the real-time levels of different types of tag data are different during updating;

caching the label data to an updating queue corresponding to the type, wherein different updating queues correspond to different data updating speeds;

and updating the label data in the update queue according to the data update speed corresponding to the update queue.
The method of claim 1, wherein the obtaining the type of the tag data comprises:

obtaining a type identifier in the tag data, wherein the type identifier is used for representing the type of the tag data;

and determining the type of the tag data according to the type identifier.
The method of claim 1, wherein the obtaining the type of the tag data comprises:

acquiring a data source of the label data;

and determining the type of the tag data according to the data source.
The method according to any one of claims 1-3, wherein the caching the tag data into an update queue corresponding to the type comprises:

when the type is a first type, caching the tag data to a first updating queue;

and when the type is a second type, caching the tag data to a second updating queue, wherein the real-time level corresponding to the tag data of the first type is greater than the real-time level corresponding to the tag data of the second type, and the data updating speed corresponding to the first updating queue is greater than the data updating speed corresponding to the second updating queue.
The method of claim 4, wherein when the type is a first type, the buffering the tag data to a first update queue comprises:

when the type is a first type, judging whether the current data volume in the first updating queue reaches a cache threshold value;

and if the current data volume does not reach a cache threshold value, caching the tag data to the first updating queue.
The method of claim 5, further comprising:

if the current data volume reaches a cache threshold value, determining the cache duration of each tag data in the first update queue after the tag data is cached in the first update queue;

acquiring first tag data in the first updating queue, wherein the cache duration corresponding to the first tag data is longer than a set duration;

after the first tag data is cleared from the first updating queue, if the current data volume in the first updating queue does not reach the cache threshold value, caching the tag data into the first updating queue.
The method of claim 6, wherein the first update queue and the second update queue are located in memory, and wherein prior to the clearing the first tag data from the first update queue, the method further comprises:

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

And storing the first label data to a local disk.
The method according to any one of claims 4-7, further comprising:

acquiring a user identifier and a label name corresponding to the label data;

judging whether second label data exist in the first updating queue or not, wherein the second label data are label data which are the same as the user identification and the label name;

clearing the second tag data in the first update queue if the second tag data exists in the first update queue.
The method according to any one of claims 1-8, wherein the caching the tag data into an update queue corresponding to the type comprises:

judging whether the data updating speed corresponding to the updating queue is greater than a set speed or not;

if the data updating speed corresponding to the updating queue is greater than the set speed, acquiring the residual utilization rate of the processor;

and if the residual utilization rate is higher than the set utilization rate, caching the tag data to an update queue corresponding to the type.
The method of claim 9, further comprising:

and if the residual utilization rate is less than or equal to the set utilization rate, caching the tag data to a target updating queue, wherein the data updating speed corresponding to the updating queue is greater than the data updating speed corresponding to the target updating queue.
The method of any of claims 1-10, wherein the update queue corresponds to multiple types of tag data, and wherein after the buffering the tag data into the update queue corresponding to the type, the method further comprises:

and if the type is a set type, sequencing all the label data according to the type of each label data of all the label data in the update queue.
The method of claim 11, wherein the sorting all the tag data in the update queue according to a type of each tag data comprises:

judging whether other tag data of the set type except the tag data exists in the updating queue;

and if the other tag data of the set type do not exist in the updating queue, the tag data is arranged to the head of the updating queue.
The method of claim 12, further comprising:

and if the other label data exist in the updating queue, the label data is arranged at a position which is behind the other label data and is adjacent to the other label data in the updating queue.
The method of claim 11, wherein the sorting all the tag data in the update queue according to a type of each tag data comprises:

determining the priority corresponding to each label data according to the type of each label data in the update queue;

and sorting the label data with different priorities in all the label data according to the high-low order of the priority corresponding to each label data.
The method according to claim 14, wherein after sorting the tag data with different priorities in all the tag data according to the high-low order of the priority corresponding to each tag data, the method further comprises:

and if the label data with the same priority exist in the updating queue, sorting the label data with the same priority according to the sequence of the time of caching the label data to the updating queue.
An apparatus for updating tag data, the apparatus comprising: a type acquisition module, a data caching module and a data updating module, wherein,

the type obtaining module is used for obtaining the type of the label data when the label data to be updated is obtained, and the real-time levels of different types of label data are different during updating;

the data caching module is used for caching the tag data to the updating queues corresponding to the types, wherein different updating queues correspond to different data updating speeds;

and the data updating module is used for updating the label data in the updating queue according to the data updating speed corresponding to the updating queue.
The apparatus of claim 16, wherein the type obtaining module comprises an identity obtaining unit and a first type determining unit, wherein,

the identification obtaining unit is used for obtaining a type identification in the label data, and the type identification is used for representing the type of the label data;

the first type determining unit is used for determining the type of the tag data according to the type identifier.
The apparatus of claim 16, wherein the type obtaining module comprises a data source obtaining unit and a second type determining unit, wherein,

the data source acquisition unit is used for acquiring a data source of the label data;

the second type determining unit is used for determining the type of the tag data according to the data source.
An electronic device, comprising:

one or more processors;

a memory;

one or more applications, wherein the one or more applications are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method of any of claims 1-15.
A computer-readable storage medium, having stored thereon program code that can be invoked by a processor to perform the method according to any one of claims 1 to 15.