WO2021087990A1 - 标签更新方法、装置、电子设备及存储介质 - Google Patents

标签更新方法、装置、电子设备及存储介质 Download PDF

Info

Publication number
WO2021087990A1
WO2021087990A1 PCT/CN2019/116729 CN2019116729W WO2021087990A1 WO 2021087990 A1 WO2021087990 A1 WO 2021087990A1 CN 2019116729 W CN2019116729 W CN 2019116729W WO 2021087990 A1 WO2021087990 A1 WO 2021087990A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
tag data
buffer queue
tag
designated buffer
Prior art date
Application number
PCT/CN2019/116729
Other languages
English (en)
French (fr)
Inventor
黄江伟
Original Assignee
深圳市欢太科技有限公司
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳市欢太科技有限公司, Oppo广东移动通信有限公司 filed Critical 深圳市欢太科技有限公司
Priority to PCT/CN2019/116729 priority Critical patent/WO2021087990A1/zh
Priority to CN201980100120.XA priority patent/CN114402313A/zh
Publication of WO2021087990A1 publication Critical patent/WO2021087990A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/23—Updating

Definitions

  • This application relates to the field of data processing technology, and more specifically, to a label update method, device, electronic equipment, and storage medium.
  • this application proposes a label updating method, device, electronic device, and storage medium.
  • an embodiment of the present application provides a label updating method.
  • the method includes: obtaining label data to be updated from a plurality of different data sources; buffering the obtained label data in a designated buffer queue, and The designated buffer queue is used for buffering tag data to be updated; the buffered tag data is read from the designated buffer queue, and the read tag data is updated.
  • an embodiment of the present application provides a label update device, the device includes: a data acquisition module, a data cache module, and a data update module, wherein the data acquisition module is used to acquire data from multiple different data sources. Label data to be updated; the data buffer module is used to buffer the acquired label data to a designated buffer queue, the designated buffer queue is used to buffer the label data to be updated; the data update module is used to download The specified buffer queue reads the cached tag data and updates the read tag data.
  • 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 label update method provided in the above-mentioned first 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. Update method.
  • the tag data to be updated is obtained from multiple different data sources, and the obtained tag data is cached to a designated buffer queue.
  • the designated buffer queue is used to buffer the tag data to be updated, and then retrieve the Specify the buffer queue to read the cached tag data, and update the read tag data, so as to realize the update processing of the tag data of multiple different data sources, and by specifying the buffer queue to cache the tag data, the tag data can be realized Management during update.
  • Fig. 1 shows a flowchart of a label updating method according to an embodiment of the present application.
  • Fig. 2 shows a flowchart of a label updating method according to another embodiment of the present application.
  • Fig. 3 shows a flowchart of a label updating method according to another embodiment of the present application.
  • FIG. 4 shows a flowchart of step S320 in the label update method provided by another embodiment of the present application.
  • FIG. 5 shows another flowchart of step S320 in the label update method provided by another embodiment of the present application.
  • Fig. 6 shows a flowchart of a label updating method according to still another embodiment of the present application.
  • Fig. 7 shows a flowchart of a label updating method according to still another embodiment of the present application.
  • FIG. 8 shows a schematic block diagram of the principle of a label update method provided by an embodiment of the present application.
  • Fig. 9 shows a block diagram of a label updating device according to an embodiment of the present application.
  • FIG. 10 is a block diagram of an electronic device for executing the label updating method according to the embodiment of the present application according to an embodiment of the present application.
  • FIG. 11 is a storage unit for storing or carrying program code for implementing the label updating method according to the embodiment of the present application according to an embodiment of the present application.
  • information recommendation technology based on big data technology can recommend content that people need, which can better meet the needs of users.
  • 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.
  • 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.
  • tag data is mainly stored in a database
  • 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 is usually written directly into the tag database to achieve unified management and use of tag data assets, and finally form a user tag system, which is convenient for subsequent secondary analysis and processing on the basis of this tag system.
  • the tag data comes from multiple data sources, an update program is constructed according to each data source, and multiple data sources are written into the tag storage at the same time.
  • tag data is stored in a tag database, and multiple update programs write tag data at the same time, which will cause problems in management during update, for example, tag data from multiple data sources are updated at the same time At that time, the carrying capacity of the label database was exceeded.
  • the inventor proposes the label update method, device, electronic device, and storage medium provided by the embodiments of the present application.
  • the label data to be updated is obtained from multiple different data sources, and then the obtained label data is unified.
  • Cache to the designated buffer queue then read the cached tag data from the designated buffer queue, and update the read tag data, so as to realize the update processing of the tag data of multiple different data sources, and cache through the designated buffer queue Tag data can realize the management when tag data is updated.
  • the specific label update method will be described in detail in the subsequent embodiments.
  • FIG. 1 shows a schematic flowchart of a label update method provided by an embodiment of the present application.
  • the tag update method is used to implement update processing of tag data of multiple different data sources, and manage the tag data of multiple data sources when updating.
  • the label updating method is applied to the label updating apparatus 400 as shown in FIG. 9 and the electronic device 100 equipped with the label updating apparatus 400 (FIG. 10).
  • the following will take an electronic device as an example to describe the specific process of this embodiment.
  • 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. 1 will be described in detail below, and the label update method may specifically include the following steps:
  • Step S110 Obtain tag data to be updated from multiple different data sources.
  • the electronic device can manage the user's tag data, and the tag data managed by the electronic device can come from multiple different data sources.
  • the data source may be a server or a user's mobile terminal, which is not limited here.
  • the label data refers to data corresponding to the label, and specifically may be user data corresponding to the label.
  • the occupation of user A at the first moment is a student
  • the occupation at the second moment is a teacher.
  • the data corresponding to the occupation in the label of user A is student.
  • the label of user A The data corresponding to the middle occupation is teachers.
  • the user’s label data 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.
  • the above label data is only an example, and does not represent a limitation on the specific label data.
  • the electronic device may receive tag data to be updated sent by different data sources, and the electronic device may also actively obtain the tag data to be updated from 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.
  • the electronic device may obtain the tag data to be updated from multiple different data sources regularly or irregularly.
  • the electronic device may obtain tag data to be updated from multiple data sources at preset intervals.
  • the electronic device may receive tag data to be updated from multiple data sources in real time.
  • Step S120 Buffer the acquired tag data to a designated buffer queue, and the designated buffer queue is used to buffer the tag data to be updated.
  • the electronic device after the electronic device obtains the tag data to be updated, it can buffer the obtained tag data in a designated buffer queue, and the designated buffer queue is used to buffer the tag data to be updated, so as to realize the
  • the label data of multiple data sources is cached in the designated buffer queue, and the designated buffer queue can be used to manage the label data of multiple data sources.
  • the electronic device may buffer the label data in the designated buffer queue every time it acquires the label data to be updated, so as to read the label data from the designated buffer queue for updating. That is, when the electronic device obtains the tag data to be updated from any one of the multiple data sources, it buffers the obtained tag data in the designated buffer queue.
  • the electronic device can periodically update the tag data.
  • the electronic device can also obtain the tag data to be updated from the data source, and then store the tag data locally.
  • the tag data is updated, the stored tag data is cached in the designated buffer queue, and the tag data can be successively taken out from the designated buffer queue and the tag data can be updated.
  • the designated buffer queue can adopt the principle of first-in first-out and last-in-last-out, so that the sequence of tag data entering the designated buffer queue when it is subsequently taken out for update can be cached in the designated buffer queue. Corresponds to the order of priority.
  • Step S130 Read the cached tag data from the designated buffer queue, and update the read tag data.
  • the electronic device can read each tag data in turn according to the arrangement order of the tag data in the designated buffer queue, and update each tag data, that is, the buffer queue is first-in-first-out,
  • the last-in-last-out principle is to take out the label data in sequence according to the arrangement order of the label data in the designated buffer queue, and update the label data.
  • the electronic device can start to fetch the tag data and update the tag data when it caches the tag data in the designated buffer queue. For example, when the electronic device updates the tag data in real-time, It can be updated in this way; the electronic device can also start to fetch the label data and update the label data after buffering the label data in the designated buffer queue for a preset period of time. For example, the electronic device can update the label data. When the update method is non-real-time update, you can update in this way.
  • the electronic device when the electronic device updates the tag data, it can compare the tag data with all tag data corresponding to the user identification currently stored according to the user identification corresponding to the tag data, so as to determine to write the tag data.
  • the tag data Into the label data corresponding to the user identification, or when writing the label data into the label data corresponding to the user identification, part of the label data is deleted, that is, the label data is replaced with part of the label data.
  • the label update method obtained by the embodiment of the present application obtains the label data to be updated from multiple different data sources, and buffers the obtained label data to a designated buffer queue, and the designated buffer queue is used to buffer the label to be updated. Data, and then read the cached tag data from the designated buffer queue, and update the read tag data, so as to realize that the tag data can be cached by the designated buffer queue, and the management of tag data update can be realized, and the management of the tag data can be realized.
  • the label data of different data sources are updated without using multiple software programs to update the label data of different data sources, which reduces the development time of the staff on the software program and improves the control effect when the label data is updated. .
  • FIG. 2 shows a schematic flowchart of a label update method provided by another embodiment of the present application.
  • the process shown in FIG. 2 will be described in detail below, and the label update method may specifically include the following steps:
  • Step S210 Obtain tag data to be updated from multiple different data sources.
  • the electronic device when the electronic device actively obtains the tag data to be updated from the data source, the electronic device can obtain the tag data to be updated from multiple data sources according to a preset interval, and different data sources The corresponding preset interval duration is different.
  • multiple data sources include data source 1, data source 2, and data source 3.
  • the label data of data source 1 can be obtained at a preset interval of 24 hours, and the label data of data source 2 can be obtained at a preset interval of 12 hours.
  • Time length acquisition, the tag data of data source 3 can be acquired according to a preset interval of 36 hours. Therefore, the preset interval length can be set according to the frequency with which the tag data of the data source needs to be updated to meet different update requirements.
  • the data source can send the tag data in the above manner.
  • the electronic device when the electronic device actively obtains the tag data to be updated from the data source, the electronic device may also obtain the tag data at the same preset interval. In this way, the electronic device can divide the acquisition of the tag data to be updated from multiple data sources into acquisition at multiple times for different data sources, that is to say, acquire different data sources in batches at multiple times The label data to be updated.
  • multiple data sources include data source 1, data source 2, data source 3, data source 4, data source 5, and data source 6.
  • the preset interval is 24 hours, that is, the electronic device obtains the waiting time of these data sources once a day.
  • the electronic device obtains the label data of data source 1 and data source 2 at 10 o'clock every day, obtains the label data of data source 3 and data source 4 at 14:00 every day, and obtains data source 5 and data at 17:00 every day.
  • label data can be obtained for different data sources, so that the label data of different data sources can be obtained at different times, avoiding electronic devices from obtaining label data from a large number of data sources at the same time, resulting in a large amount of processing in the same time period .
  • the electronic device receives the tag data from the data source, the data source can send the tag data in the above manner.
  • the data source can be registered in the electronic device in advance, and the electronic device stores the configuration information of the registered data source (such as the data source type, address, etc.), so that the registered data source can be electronically registered.
  • Device identification such as the data source type, address, etc.
  • Step S220 When the label data to be updated from multiple data sources is obtained at the same time, the first priority of each data source in the multiple data sources is obtained, and the first priority is based on the label of the data source. The real-time level of the data when it is updated is determined.
  • the electronic device when the electronic device obtains tag data to be updated from multiple data sources at the same time, there is a case where the electronic device obtains tag data to be updated from multiple data sources at the same time.
  • the electronic device obtains tag data to be updated from multiple data sources at the same time, it can cache the tag data in a designated buffer queue according to different data sources.
  • the first priority corresponding to each data source in the multiple data sources may be determined, so as to follow the priority of the data source.
  • the first priority corresponding to each data source may be determined according to the real-time level of the tag data of the data source when it is updated, and the tag data of different data sources may have different real-time levels when it is updated.
  • the real-time level of the label data of the data source when it is updated can refer to the level of real-time demand for the label data of the data source when it is updated. The higher the real-time level, the more real-time the label data of the data source needs to be updated. . It is understandable that the electronic device can identify the real-time level of the tag data of the data source when it is updated to determine the first priority corresponding to the data source.
  • the real-time level of the tag data of the data source when it is updated is proportional to the first priority corresponding to the data source, that is, the higher the real-time level of the tag data of the data source when it is updated ,
  • the first priority corresponding to the data source is higher.
  • the label data of data source 1 is updated with a real-time level of level 1
  • the label data of data source 2 is updated with a real-time level of level 2
  • the label data of data source 3 is updated with a real-time level of Level 3
  • the real-time level of level 1, level 2, and level 3 are sequentially reduced.
  • the first priority includes priority 1, priority 2, and priority 3.
  • Priority 1, priority 2, and priority 3 are priorities in order In descending order, level 1 corresponds to priority 1, level 2 corresponds to priority 2, and level 3 corresponds to priority 3.
  • level 1 corresponds to priority 1
  • level 2 corresponds to priority 2
  • level 3 corresponds to priority 3.
  • the above are only examples, and do not represent a limitation on the relationship between the specific real-time level and the first priority.
  • the real-time level of tag data of different data sources when it is updated can be stored in the electronic device in advance.
  • the electronic device can identify the type and identification of the data source to determine the tag data of different data sources when it is updated.
  • the real-time level can be stored in the electronic device in advance.
  • the electronic device determines the real-time level of the tag data of different data sources when it is updated, it can determine the first priority corresponding to each data source, so as to cache the tag data of different data sources to the designated buffer.
  • the sequence of the queues is determined, so that the real-time requirements for tag data update of different data sources can be met, and the sequence of buffering tag data of different data sources to the designated buffer queue can be different.
  • Step S230 According to the first priority of each data source, obtain the cache order corresponding to the tag data of each data source in the multiple data sources, and the cache order is that the tag data is cached to the designated The order of the buffer queue.
  • the electronic device can determine the buffering sequence of the tag data of the data source to the designated buffer queue according to the first priority of the data source.
  • step S230 may include: according to the first priority of each data source, determining the order of the first priority corresponding to the multiple data sources; and determining the order of the first priority according to the order of high and low
  • the caching sequence corresponding to the tag data of each data source in the multiple data sources It is understandable that the electronic device can sequentially sort the tag data of each data source in the order of the first priority from high to low, so as to obtain the update sequence of the tag data of multiple data sources when they are updated. It can be understood that the higher the first priority of the data source, the higher the label data of the data source in the update sequence. For example, the first priority of data source 1 is higher than that of data source 2. First priority, the label data of data source 1 is before the label data of data source 2 in the update sequence.
  • Step S240 According to the buffer sequence, the tag data of each data source is sequentially buffered to the designated buffer queue.
  • the electronic device when the electronic device buffers the tag data of multiple data sources in the designated buffer queue, it can sequentially buffer the tag data of each data source to the designated buffer queue according to the determined buffer sequence. It is understandable that the principle of first-in, first-out and last-in-last-out is adopted in the designated buffer queue, so that the sequence of tag data entering the designated buffer queue when it is subsequently taken out for update can be cached in the designated buffer queue. (That is, the order of update) corresponds.
  • Step S250 Read the cached tag data from the designated buffer queue, and update the read tag data.
  • the electronic device can read each tag data in turn according to the arrangement order of the tag data in the designated buffer queue, and update each tag data, that is to say, the designated buffer queue is the principle of first-in first-out, last-in-last-out.
  • the tag data is taken out in turn, and the tag data is updated, so that the update sequence can correspond to the cache sequence, so as to ensure that the tag data of different data sources are updated in different orders, and
  • the update order can correspond to the first priority of the data source.
  • step S210, step S220, and step S230 in the embodiment of the present application can also be applied to other embodiments.
  • the label data to be updated is obtained from multiple different data sources.
  • the different data sources are compared according to the first priority of the data source.
  • the buffer sequence of the label data in the designated buffer queue is determined, and then according to the buffer sequence, the label data corresponding to each data source is sequentially buffered to the designated buffer queue, and then the buffered data is read from the designated buffer queue.
  • Tag data and update the read tag data so that the tag data can be cached by the designated buffer queue, the management of tag data update can be realized, and the tag data of multiple different data sources can be updated without the need
  • Multiple software programs are used to update label data of different data sources, which reduces the staff's development time for software programs, and also improves the management and control effect when label data is updated.
  • the tag data of different data sources are updated in different order, and the update order can correspond to the first priority of the data source, that is, correspond to the real-time level when the tag data of the data source is updated.
  • FIG. 3 shows a schematic flowchart of a label update method provided by another embodiment of the present application.
  • the process shown in FIG. 3 will be described in detail below, and the label update method may specifically include the following steps:
  • Step S310 Obtain tag data to be updated from multiple different data sources.
  • step S310 can refer to the content of the foregoing embodiment, which will not be repeated here.
  • Step S320 When the acquired tag data includes multiple tag data from the same data source, acquire a second priority corresponding to each tag data in the multiple tag data, and the second priority is based on different The real-time level of tag data is determined when it is updated.
  • the tag data that may be obtained includes multiple tag data from the same data source, that is to say, the same data source is obtained at the same time Of multiple label data.
  • the buffer sequence of the tag data to the designated buffer queue can be determined.
  • the electronic device can obtain the second priority corresponding to each tag data, and according to the second priority, determine the buffering sequence of each tag data to the designated buffer queue.
  • step S320 may include:
  • Step S321A Obtain the type of each tag data in the plurality of tag data, and different types of tag data have different real-time levels when they are updated.
  • the real-time level of the tag data when it is updated may correspond to the type of the tag data, and the real-time level of the tag data when it is updated may also correspond to the user identification.
  • the electronic device determines the second priority corresponding to the tag data, since the second priority corresponding to the tag data is determined by the real-time level when the tag data is updated, it can be determined according to the type of the tag data or the user identification corresponding to the tag data.
  • step S321A may include:
  • the tag data may include a type identification, and the type identification is in a 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 tag data, it can determine the type of the tag data according to the type identification.
  • Step S322A Determine the second priority corresponding to each tag data according to the type of each tag data.
  • the electronic device can determine the second priority corresponding to the tag data according to the type of the tag data.
  • the types of tag data include type 1 and type 2.
  • the real-time level of tag data of type 1 when updated is higher than the real-time level of tag data of type 2 when updated, then type 1 corresponds to priority 1, type 2 Corresponds to priority 2, and priority 1 is higher than priority 2.
  • step S320 may include:
  • Step S321B Obtain a user identifier corresponding to each tag data in the plurality of tag data.
  • the real-time level of tag data corresponding to different users can be different when it is updated.
  • a newly registered user needs a large amount of user data as the basis for constructing user tags in order to serve users, so it needs to be timely.
  • the identity level of different users is different, and the real-time level of the tag data corresponding to the user is also different when it is updated.
  • the identity information corresponding to the user may be in the tag data in the form of user identification, and the electronic device may obtain the user identification corresponding to the tag data.
  • the user identifier may be International Mobile Equipment Identity (IMEI), user account OPENID, etc., which are not limited here.
  • Step S322B Determine the second priority corresponding to each tag data according to the user identifier corresponding to each tag data.
  • step S22B may include: according to the user identification corresponding to each tag data, determining the real-time level of tag update corresponding to the user identification; and determining the real-time level according to the real-time level The second priority corresponding to each tag data.
  • the second priority level corresponding to the tag data is determined by the user identification, so that when the real-time level of the tag data when the tag data is updated is related to the user identity, the obtained priority level accuracy is high.
  • Step S330 Determine the buffering sequence of the multiple label data according to the second priority corresponding to each label data, and the buffering sequence is the sequence of buffering the label data to the designated buffer queue.
  • the order of the first priority corresponding to the multiple tag data is determined, and then the cache order corresponding to each tag data is determined according to the order of high and low.
  • Step S340 According to the buffering sequence, sequentially buffer each tag data to the designated buffer queue.
  • Step S350 Read the cached tag data from the designated buffer queue, and update the read tag data.
  • step S340 and step S350 can refer to the content of the foregoing embodiment, and will not be repeated here.
  • step S320 and step S330 in the embodiment of the present application can also be applied to other embodiments.
  • the tag data to be updated is obtained from multiple different data sources.
  • the buffer sequence of different label data to the designated buffer queue is determined, and then according to the buffer sequence, each label data is sequentially buffered to the designated buffer queue, and then the buffered label data is read from the designated buffer queue. And update the read tag data, so that the tag data can be cached by the designated buffer queue, the management of tag data update can be realized, and the tag data of multiple different data sources can be updated without using multiple
  • the software program updates the label data of different data sources separately, which reduces the staff's development time for the software program, and also improves the control effect when the label data is updated. And it is ensured that the sequence of multiple tag data updates of the same data source is different, and the update sequence can correspond to the second priority of the tag data, that is, it corresponds to the real-time level when the tag data is updated.
  • FIG. 6 shows a schematic flowchart of a label update method provided by still another embodiment of the present application.
  • the process shown in FIG. 6 will be described in detail below, and the label update method may specifically include the following steps:
  • Step S410 Obtain tag data to be updated from multiple different data sources.
  • step S410 may refer to the content of the foregoing embodiment, which will not be repeated here.
  • Step S420 When the acquired tag data meets a preset condition, the acquired tag data is buffered in the designated buffer queue and inserted into the target position in the designated buffer queue.
  • the target position Is one of the positions before the set position in the designated buffer queue.
  • the electronic device when the electronic device buffers the acquired tag data into the designated buffer queue, it can also insert one or more tag data into a specific position in the designated buffer queue, so that the currently buffered tag data Be updated as soon as possible.
  • the electronic device may insert tag data that meets a preset condition into a target position in the designated buffer queue, and the target position is located at one of the positions before the set position in the designated buffer queue.
  • the preset condition may be that the real-time level of the label data is greater than the set level.
  • step S420 may include:
  • the target location to which the tag data needs to be inserted can be determined.
  • the electronic device may obtain the target position in the designated buffer queue according to the real-time level corresponding to the acquired tag data and the real-time level corresponding to each tag data in the cache queue. , The real-time level corresponding to the tag data at the position after the target position and adjacent to the target position is lower than the real-time level corresponding to the obtained tag data.
  • the real-time level of the label data that is adjacent to the target position and after the target position is just less than the real-time level of the label data inserted this time, so that the label data inserted this time does not affect the real-time level of the same or higher The order in which the tag data is updated.
  • Step S430 Read the cached tag data from the designated buffer queue, and update the read tag data.
  • step S430 can refer to the content of the foregoing embodiment, and will not be repeated here.
  • step S420 in the embodiment of the present application can also be applied to other embodiments.
  • the label update method obtained by the embodiment of the present application obtains the label data to be updated from different data sources.
  • the label data is inserted into the designated buffer queue.
  • the tag data is read from the designated buffer queue for update, so that the tag data can be updated as soon as possible.
  • FIG. 7 shows a schematic flowchart of a label update method provided by yet another embodiment of the present application.
  • the process shown in FIG. 7 will be described in detail below, and the label update method may specifically include the following steps:
  • Step S510 Obtain tag data to be updated from multiple different data sources.
  • Step S520 Determine whether the current data volume in the designated buffer queue reaches a first set threshold.
  • the electronic device may also determine whether the current amount of data in the designated buffer queue reaches the first set threshold before buffering the acquired tag data to be updated in the designated buffer queue.
  • the first set threshold may be the size of the data volume that the designated buffer queue can hold, or it can be a value smaller than the size of the data volume that the designated buffer queue can hold, which is not limited here.
  • Step S530 If the current data volume does not reach the first set threshold, buffer the acquired tag data to the designated buffer queue.
  • the designated buffer queue can also accommodate other tag data, so the acquired tag data can be cached in the designated buffer queue.
  • step S530 may include: if the current amount of data in the designated buffer queue does not reach the first set threshold, judging whether the current amount of data reaches a second set threshold, and the second The set threshold is less than the first set threshold; if the current data volume does not reach the second set threshold, buffer the acquired tag data to the designated buffer queue.
  • the second set threshold is a threshold smaller than the first set threshold. If the current amount of data in the designated buffer queue reaches the second set threshold, it means that the amount of data in the designated buffer queue is large, and the update processing task is relatively busy, which may cause the update task to crash. Therefore, when the amount of previous data does not reach the second set threshold, the acquired tag data can be buffered to the designated buffer queue.
  • the tag update method may further include: if the current data volume reaches the second set threshold, after releasing the idle resources currently in an idle state, buffering the obtained tag data to the Specify the buffer queue. It is understandable that because the current data volume in the designated buffer queue reaches the second set threshold, it may cause too much processing volume and cause the update task to crash. Therefore, the electronic device can release idle resources in the idle state, and then reset the tag The data is cached in the designated buffer queue, so that more resources are allocated to the update task of the tag data, and the update task is prevented from crashing.
  • the idle resource can be a resource occupied by a process that is in the background for more than a set duration and is not used, or it can refer to a resource occupied by another process that is not currently being used, which is not limited here.
  • Step S540 If the current data volume reaches a first set threshold, determine the buffering duration corresponding to each tag data in the designated buffer queue.
  • the designated buffer queue if the current amount of data in the designated buffer queue reaches the first set threshold, it means that the designated buffer queue cannot accommodate other tag data. Therefore, it is possible to clarify the label data that has lost timeliness in the designated buffer queue, and it is convenient for the current label data to be buffered in the designated buffer queue.
  • the electronic device may determine the buffer duration corresponding to each tag data in the designated buffer queue, and the buffer duration refers to the length of time the tag time exists in the designated buffer queue after the tag time is buffered in the designated buffer queue.
  • Step S550 Obtain the first tag data in the designated buffer queue, and the buffer duration corresponding to the first tag data is greater than the set duration.
  • the electronic device after the electronic device determines the cache duration corresponding to each tag data in the designated buffer queue, it can determine the tag data whose cache duration is greater than the set duration according to the cache duration of each tag data, and cache the duration Tag data that is longer than the set duration is taken as the first tag data, and the first tag data is the tag data that has lost timeliness.
  • Step S560 After clearing the first tag data from the designated buffer queue, if the current amount of data in the designated buffer queue does not reach the first set threshold, buffer the acquired tag data to the Specify the buffer queue.
  • the electronic device can clear the first tag data from the designated buffer queue. And after the first tag data is cleared, it is determined whether the current data volume in the designated buffer queue reaches the first set threshold. If the first set threshold is not reached, it means that after the first tag data is cleared, the designated buffer queue can accommodate Other tag data, so the acquired tag data can be cached to the designated buffer queue.
  • Step S570 Read the cached tag data from the designated buffer queue, and update the read tag data.
  • step S570 can refer to the content of the foregoing embodiment, and will not be repeated here.
  • step S520 to step S560 are also applicable to other embodiments.
  • the tag update method may further include: real-time monitoring of the update speed of the tag data; if the update speed is lower than the set speed, releasing idle resources that are currently in an idle state.
  • the electronic device can determine the update speed of the tag data according to the number of tag data updated by the electronic device within the preset time period. If the update speed is lower than the set speed, it means that the update of the tag data is slow, so the idle resources currently in the idle state can be released, so that more resources can be allocated to the update task of the tag data, and the update of the tag data can be improved. speed.
  • the label update method may further include: acquiring the repeated label data in the designated buffer queue; and deleting the repeated label data.
  • the electronic device after the electronic device buffers the label data in the designated buffer queue, it can also determine the repeated label data in the designated buffer queue, and clear the repeated label data, so as to reduce the time when the electronic device updates the label data. ⁇ The processing capacity.
  • the schematic diagram of the label update method provided by the embodiment of the present application may be as shown in FIG. 8, in which the unified task management service 701 is the central part, because the data sources are diverse, in order to maximize and maximize resource utilization. Minimize the cost of tag data source access, establish a unified unified task management service 701, perform resource allocation management for existing data sources, and when new data sources arrive, you only need to register and configure with the task management service to access , To achieve high scalability.
  • the unified task management service 701 manages each module in the entire solution, and plays a role in scheduling and monitoring the cooperation and maintenance of each module.
  • the designated buffer queue 702 can be an MQ (message queue) queue, which is used to cache tag data of multiple different data sources and ensure data consistency, so that the data source does not need to consider electronic when sending tag data to be updated.
  • the processing speed of the tag data by the device as soon as possible to write the tag data to the electronic device into the designated buffer queue, without having to suspend tasks for a long time in order to take into account the speed of the tag storage system, and release the resources to other data sources after the data is written , Improve the utilization rate of resources.
  • the pre-established unified update program 703 can read tag data from the designated buffer queue in real time and write tag data into the tag storage system 704 (tag database).
  • the unified update program 703 can also clean and clean the tag data uniformly. Processing, for some abnormal data and duplicate data, here can be managed, you can also target compressed data.
  • the label update method obtaineds the label data to be updated from multiple different data sources.
  • the electronic device buffers the obtained label data in the designated buffer queue
  • the data volume in the designated buffer queue is processed.
  • the obtained tag data is buffered to the designated buffer queue
  • the buffered tag data is read from the designated buffer queue
  • the read tag The data is updated, so that the label data can be cached by the designated buffer queue, which can realize the management of the label data update, and realize the update processing of the label data of multiple different data sources, without the need to use multiple software programs to separate different data
  • the tag data of the source is updated, which reduces the staff's development time for software programs, and also improves the control effect when tag data is updated.
  • the label updating device 400 includes: a data acquisition module 410, a data cache module 420, and a data update module 430.
  • the data acquisition module 410 is configured to acquire tag data to be updated from multiple different data sources;
  • the data buffer module 420 is configured to cache the acquired tag data to a designated buffer queue, the designated buffer queue It is used to cache tag data to be updated;
  • the data update module 430 is used to read the cached tag data from the designated buffer queue and update the read tag data.
  • the data caching module 420 may include: a first priority determining unit, a first order determining unit, and a first caching unit.
  • the first priority determining unit is configured to obtain the first priority of each data source in the multiple data sources when the tag data to be updated from multiple data sources is obtained at the same time, and the first priority is Determined according to the real-time level of the tag data of the data source when it is updated;
  • the first order determining unit is configured to obtain the tag data of each data source in the multiple data sources according to the first priority of each data source
  • the caching sequence is the sequence in which tag data is cached to the designated buffer queue;
  • the first caching unit is configured to sequentially cache the label data of each data source according to the caching sequence To the designated buffer queue.
  • the first priority determining unit may be specifically configured to: according to the first priority of each data source, determine the order of the first priority corresponding to the multiple data sources; The high and low order determines the cache order corresponding to the tag data of each data source in the multiple data sources.
  • the data caching module 420 may include: a second priority determining unit, a second order determining unit, and a second caching unit.
  • the second priority determining unit is used for obtaining a second priority corresponding to each tag data in the plurality of tag data when the obtained tag data includes multiple tag data from the same data source, and the second priority The priority is determined according to the real-time level of different tag data when it is updated; the second order determining unit is used to determine the cache order of the multiple tag data according to the second priority corresponding to each tag data, so
  • the buffer sequence is the sequence in which the tag data is buffered to the designated buffer queue; the second buffer unit is configured to sequentially buffer each of the label data to the designated buffer queue according to the buffer sequence.
  • the second priority determining unit may be specifically configured to: obtain the type of each tag data in the plurality of tag data, and different types of tag data have different real-time levels when they are updated; The type of each tag data determines the second priority corresponding to each tag data.
  • acquiring the type of each tag data in the plurality of tag data by the second priority determining unit may include: acquiring the type identification of each tag data in the plurality of tag data; The type identification of each tag data determines the type of each tag data.
  • the second priority determining unit may also be specifically configured to: obtain the user identification corresponding to each tag data in the plurality of tag data; determine the user identification corresponding to each tag data; Describe the second priority corresponding to each tag data.
  • the second priority determining unit determines the second priority corresponding to each tag data according to the user identifier corresponding to each tag data, including: according to the user corresponding to each tag data
  • the identifier determines the real-time level of tag update corresponding to the user identifier; and determines the second priority corresponding to each tag data according to the real-time level.
  • the data caching module 420 may be specifically configured to: when the obtained tag data meets a preset condition, cache the obtained tag data in the designated buffer queue and insert it into the designated buffer queue. At the target position in the buffer queue, the target position is one of the positions before the set position in the designated buffer queue.
  • the data caching module 420 may be specifically configured to: determine the real-time level of the obtained tag data when it is updated; determine whether the real-time level is greater than the set level; if it is greater than the set level Buffer the obtained tag data into the designated buffer queue and insert it into the target position in the designated buffer queue.
  • the data caching module 420 may also be used to cache the acquired tag data in the designated buffer queue and insert it into the target position in the designated buffer queue, according to the acquired tag data.
  • the real-time performance level corresponding to the tag data and the real-time performance level corresponding to each tag data in the buffer queue to obtain the target position in the designated buffer queue, and the label at the position after the target position and adjacent to the target position
  • the real-time level corresponding to the data is lower than the real-time level corresponding to the obtained tag data.
  • the data caching module 420 may include: a data amount judging unit and a third caching unit.
  • the data amount judging unit is used to judge whether the current data amount in the designated buffer queue reaches the first set threshold; the third buffer unit is used to change the obtained label if the current data amount does not reach the first set threshold The data is buffered to the designated buffer queue.
  • the data caching module 420 may further include: a caching duration determining unit and a tag acquiring unit.
  • the buffer duration determining unit is configured to determine the buffer duration corresponding to each tag data in the designated buffer queue if the current data volume reaches a first set threshold;
  • the tag acquiring unit is configured to acquire the first buffer queue in the designated buffer queue.
  • Tag data, the buffer duration corresponding to the first tag data is greater than the set duration;
  • the third buffer unit may also be used to clear the first tag data from the designated buffer queue, if the buffer in the designated buffer queue The current data volume does not reach the first set threshold, and the acquired tag data is buffered in the designated buffer queue.
  • the third buffer unit may be specifically configured to: if the current amount of data in the designated buffer queue does not reach the first set threshold, determine whether the current amount of data reaches the second set threshold, The second set threshold is less than the first set threshold; if the current data volume does not reach the second set threshold, buffer the acquired tag data to the designated buffer queue.
  • the data caching module 420 may also be used to: if the current data volume reaches the second set threshold, after releasing the idle resources currently in the idle state, cache the obtained tag data to all Describe the designated buffer queue.
  • the label updating device 400 may further include a speed monitoring module and a resource release module.
  • the speed monitoring module is used to monitor the update speed of tag data in real time; the resource release module is used to release idle resources that are currently in an idle state if the update speed is lower than the set speed.
  • the label updating device 400 may further include: a repeated data acquisition module and a data deletion module.
  • the repeated data acquisition module is used to acquire the repeated label data in the designated buffer queue; the data deletion module is used to delete the repeated label data.
  • the coupling between the modules may be electrical, mechanical or other forms of coupling.
  • 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.
  • the solution provided by this application obtains the tag data to be updated from multiple different data sources, and caches the obtained tag data to a designated buffer queue, which is used to buffer the updated tag data.
  • Tag data then read the cached tag data from the designated buffer queue, and update the read tag data, so as to update the tag data of multiple different data sources, and cache the tag data through the designated buffer queue. It can realize the management when tag data is updated.
  • the electronic device 100 may be an electronic device capable of running application programs, such as a server, a PC computer, or a mobile terminal.
  • the electronic device 100 in this application may include one or more of the following components: a processor 110, a memory 120, a touch screen 130, and one or more application programs, of which one or more application programs may be stored in the memory 120 and configured To be executed by one or more processors 110, one or more programs are configured to execute the methods described in the foregoing method embodiments.
  • 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 may adopt at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA).
  • DSP Digital Signal Processing
  • FPGA Field-Programmable Gate Array
  • PDA Programmable Logic Array
  • the processor 110 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a modem, and the like.
  • 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.
  • FIG. 11 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Memory System Of A Hierarchy Structure (AREA)

Abstract

一种标签更新方法、装置、电子设备及存储介质，该标签更新方法包括：从多个不同的数据源获取待进行更新的标签数据（S110）；将获取到的标签数据缓存至指定缓冲队列，所述指定缓冲队列用于缓存待进行更新的标签数据（S120）；从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新（S130）。上述方法可以实现多种数据源的标签数据的更新以及标签数据更新时的管理。

Description

标签更新方法、装置、电子设备及存储介质 技术领域
本申请涉及数据处理技术领域，更具体地，涉及一种标签更新方法、装置、电子设备及存储介质。
背景技术
随着网络信息技术的快速发展，基于大数据技术的信息推荐技术也应运而生。由于通常是根据用户标签对相关信息进行推荐，因此用户标签在信息推荐技术中起着至关重要的作用，从而用户标签的更新也成为了信息推荐技术中的关键。
发明内容
鉴于上述问题，本申请提出了一种标签更新方法、装置、电子设备及存储介质。
第一方面，本申请实施例提供了一种标签更新方法，所述方法包括：从多个不同的数据源获取待进行更新的标签数据；将获取到的标签数据缓存至指定缓冲队列，所述指定缓冲队列用于缓存待进行更新的标签数据；从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新。
第二方面，本申请实施例提供了一种标签更新装置，所述装置包括：数据获取模块、数据缓存模块以及数据更新模块，其中，所述数据获取模块用于从多个不同的数据源获取待进行更新的标签数据；所述数据缓存模块用于将获取到的标签数据缓存至指定缓冲队列，所述指定缓冲队列用于缓存待进行更新的标签数据；所述数据更新模块用于从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新。
第三方面，本申请实施例提供了一种电子设备，包括：一个或多个处理器；存储器；一个或多个应用程序，其中所述一个或多个应用程序被存储在所述存储器中并被配置为由所述一个或多个处理器执行，所述一个或多个程序配置用于执行上述第一方面提供的标签更新方法。
第四方面，本申请实施例提供了一种计算机可读取存储介质，所述计算机可读取存储介质中存储有程序代码，所述程序代码可被处理器调用执行上述第一方面提供的标签更新方法。
本申请提供的方案，通过从多个不同的数据源获取待进行更新的标签数据，将获取到的标签数据缓存至指定缓冲队列，该指定缓冲队列用于缓存待进行更新的标签数据，然后从指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新，从而实现对多个不同数据源的标签数据进行更新处理，并且通过指定缓冲队列缓存标签数据，可以实现对标签数据更新时的管理。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1示出了根据本申请一个实施例的标签更新方法流程图。
图2示出了根据本申请另一个实施例的标签更新方法流程图。
图3示出了根据本申请又一个实施例的标签更新方法流程图。
图4示出了本申请又一个实施例提供的标签更新方法中步骤S320的一种流程图。
图5示出了本申请又一个实施例提供的标签更新方法中步骤S320的另一种流程图。
图6示出了根据本申请再一个实施例的标签更新方法流程图。
图7示出了根据本申请又再一个实施例的标签更新方法流程图。
图8示出了本申请实施例提供的标签更新方法的原理示意框图。
图9示出了根据本申请一个实施例的标签更新装置的一种框图。
图10是本申请实施例的用于执行根据本申请实施例的标签更新方法的电子设备的框图。
图11是本申请实施例的用于保存或者携带实现根据本申请实施例的标签更新方法的程序代码的存储单元。
具体实施方式
为了使本技术领域的人员更好地理解本申请方案，下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
随着信息技术的快速发展，互联网给人们的生活和工作带来了越来越多的便利。其中，基于大数据技术的信息推荐技术能推荐人们需求的内容，可以较好的满足用的需求。例如，人们可以通过互联网进行购物、娱乐以及发布个人状态信息(例如，发微博)等，商家通过互联网可获取到人们的消费、娱乐以及个人状态信息等内容，可以更为全面的了解大众的需求，进而根据大众的需求为人们提供推荐服务。在商家为人们提供推荐服务的同时，商家也得到了盈利。
在信息推荐的技术中，其主要应用了用户标签，使推荐内容能满足用户的需求。用户标签主要为用于反映用户的社会属性、生活习惯和消费行为等信息的数据，用户标签为通过对用户信息进行分析而得到的特征标识。用户标签通过不断进行更新标签数据，从而使用户标签能保证精准性。
在传统的技术中，标签数据主要存储在数据库中，对用户标签进行管理的电子设备通常收集来自不同数据源的标签数据，并将标签数据写入到标签数据库中。数据源可以为服务器、移动终端等，在此不做限定。
传统技术中的标签数据的更新，通常为直接向标签数据库中写入，达到标签数据资产的统一管理和使用，最终形成用户标签体系，便于后续在此标签体系基础上进行二次分析和处理。在标签数据来自多种数据源的情况下，根据每个数据源构建一个更新程序，多个数据源同时向标签存储中写入。
发明人经过长期研究发现，目前由于存在多种多样的数据来源，未来可能也会新增多种标签来源，每次接入一次数据源，就得根据数据源特征和技术原理建立一套更新程序，复用性较差。其次，为了构建完整的用户标签体系，标签数据存储在一个标签数据库中，多个更新程序同时将标签数据写入，会使得更新时的管理出现问题，例如，多个数据源的标签数据同时更新时，出现超过了标签数据库的承载能力的情况。
针对上述问题，发明人提出了本申请实施例提供的标签更新方法、装置、电子设备以及存储介质，通过从多个不同的数据源获取待进行更新的标签数据，然后将获取到的标签数据统一缓存至指定缓冲队列，再从指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新，从而实现对多个不同数据源的标签数据进行更新处理，并且通过指定缓冲队列缓存标签数据，可以实现对标签数据更新时的管理。其中，具体的标签更新方法在后续的实施例中进行详细的说明。
请参阅图1，图1示出了本申请一个实施例提供的标签更新方法的流程示意图。所述标签更新方法用于实现对多个不同数据源的标签数据进行更新处理，并且在更新时对多个数据源的标签数据进行管理。在具体的实施例中，所述标签更新方法应用于如图9所示的标签更新装置400以及配置有所述标签更新装置400的电子设备100(图 10)。下面将以电子设备为例，说明本实施例的具体流程，当然，可以理解的，本实施例所应用的电子设备可以为服务器、移动终端等，在此不做限定。下面将针对图1所示的流程进行详细的阐述，所述标签更新方法具体可以包括以下步骤：
步骤S110：从多个不同的数据源获取待进行更新的标签数据。
在本申请实施例中，电子设备可以对用户的标签数据进行管理，电子设备管理的标签数据可以来源多个不同的数据源。其中，数据源可以为服务器，也可以为用户的移动终端，在此不做限定。标签数据指标签对应的数据，具体可以为标签对应的用户数据。例如，用户A在第一时刻的职业为学生，在第二时刻的职业为教师，则在第一时刻，用户A的标签中职业对应的数据则为学生，在第二时刻，用户A的标签中职业对应的数据为教师。由于用户的标签数据随着时间推移是在发生变化的，因此需要对用户的标签数据不断进行更新，以使用户的标签数据能与用户最新的状态匹配，从而能根据标签数据为用户提供满足需求的服务，当然，以上标签数据仅为举例，并不代表对具体的标签数据的限定。
在一些实施方式中，电子设备可以接收不同的数据源发送的待进行更新的标签数据，电子设备也可以主动向数据源获取待进行更新的标签数据。待进行更新的标签数据指获得的需要写入到标签数据的数据库中的标签数据，也可以理解为用于对用户标签进行更新的标签数据。
在一些实施方式中，电子设备可以定时或者不定时的从多个不同的数据源获取待进行更新的标签数据。例如，电子设备可以按照预设间隔从多个数据源获取待进行更新的标签数据，又例如，电子设备可以实时的从多个数据源接收待进行更新的标签数据。
步骤S120：将获取到的标签数据缓存至指定缓冲队列，所述指定缓冲队列用于缓存待进行更新的标签数据。
在本申请实施例中，电子设备在获取到待进行更新的标签数据后，可以将获取到的标签数据缓存至指定缓冲队列，该指定缓冲队列用于缓存待进行更新的标签数据，从而实现将多个数据源的标签数据缓存到指定缓冲队列，并且可以利用指定缓冲队列对多个数据源的标签数据进行管理。
在一些实施方式中，电子设备可以每获取到待进行更新的标签数据时，将标签数据缓存至指定缓冲队列中，以便从指定缓冲队列中读取标签数据进行更新。也就是说，电子设备从多个数据源中任一数据源获取到了待进行更新的标签数据，则将获取到的标签数据缓存至指定缓冲队列中。
在另一些实施方式中，电子设备可以定时的对标签数据进行更新，该情况下，电子设备也可以从数据源获取到待进行更新的标签数据后，将标签数据存储到本地，待电子设备需要对标签数据进行更新时，再将存储的标签数据缓存至指定缓冲队列中，后续则可以从指定缓冲队列陆续取出标签数据，并对标签数据进行更新。
在本申请实施例中，指定缓冲队列可以采用先进先出、后进后出的原则，从而进入到指定缓冲队列的标签数据在被后续取出进行更新时的先后顺序，能与缓存至指定缓冲队列中的先后顺序对应。
步骤S130：从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新。
在本申请实施例中，电子设备可以根据指定缓冲队列中标签数据的排布顺序，依次读取每个标签数据，并对每个标签数据进行更新，也就是说，缓冲队列为先进先出、后进后出的原则，按照指定缓冲队列中标签数据的排布顺序依次取出标签数据，并对标签数据进行更新。
在一些实施方式中，电子设备可以在有将标签数据缓存至指定缓冲队列中，即开始取出标签数据，并对标签数据进行更新，例如电子设备对标签数据的更新方式为实 时更新的方式时，即可按照此方式进行更新；电子设备也可以是在将标签数据缓存到指定缓冲队列并达到预设时长后，才开始取出标签数据，并对标签数据进行更新，例如，电子设备对标签数据的更新方式为非实时更新的方式时，即可按照此方式进行更新。
在一些实施方式中，电子设备在对标签数据进行更新时，可以根据标签数据对应的用户标识，将标签数据与当前存储的该用户标识对应的所有标签数据进行比较，从而确定将该标签数据写入到该用户标识对应的标签数据中，或者将该标签数据写入到该用户标识对应的标签数据中的同时，将部分标签数据删除，即将该标签数据替换部分标签数据。
本申请实施例提供的标签更新方法，通过从多个不同的数据源获取待进行更新的标签数据，将获取到的标签数据缓存至指定缓冲队列，该指定缓冲队列用于缓存待进行更新的标签数据，然后从指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新，从而实现通过指定缓冲队列缓存标签数据，可以实现对标签数据更新时的管理，并且实现对多个不同数据源的标签数据进行更新处理，而无需利用多个软件程序分别对不同数据源的标签数据进行更新处理，减少了工作人员对软件程序的开发时间，也提升了标签数据更新时的管控效果。
请参阅图2，图2示出了本申请另一个实施例提供的标签更新方法的流程示意图。下面将针对图2所示的流程进行详细的阐述，所述标签更新方法具体可以包括以下步骤：
步骤S210：从多个不同的数据源获取待进行更新的标签数据。
在一些实施方式中，电子设备主动的从数据源获取待进行更新的标签数据时，电子设备可以按照预设间隔时长，从多个数据源获取待进行更新的标签数据，并且，不同的数据源对应的预设间隔时长不同。例如，多个数据源包括数据源1、数据源2以及数据源3，数据源1的标签数据可以按照24小时的预设间隔时长获取，数据源2的标签数据可以按照12小时的预设间隔时长获取，数据源3的标签数据可以按照36小时的预设间隔时长获取。从而可以根据数据源的标签数据需要被更新的频率，而设置预设间隔时长，满足不同的更新需求。当然，对于电子设备从数据源接收标签数据的情况下，则数据源可以按照以上方式对发送标签数据。
在另一些实施方式中，电子设备主动的从数据源获取待进行更新的标签数据时，电子设备也可以按照相同预设间隔时长获取标签数据。该方式下，电子设备可以针对不同的数据源，而将多个数据源的待进行更新的标签数据的获取分为在多个时刻获取，也就是说，在多个时刻分批获取不同数据源的待进行更新的标签数据。例如，多个数据源包括数据源1、数据源2、数据源3、数据源4、数据源5以及数据源6，预设间隔时长为24小时，即电子设备每天获取一次这些数据源的待进行更新的标签数据，则电子设备在每天10点获取数据源1和数据源2的标签数据，在每天14点获取数据源3和数据源4的标签数据，在每天17点获取数据源5和数据源6的标签数据。从而可以针对不同的数据源而进行标签数据的获取，使不同数据源的标签数据在不同时间被获取，避免电子设备同时对大量数据源的标签数据获取，而导致同一时间段的处理量较大。当然，对于电子设备从数据源接收标签数据的情况下，则数据源可以按照以上方式对发送标签数据。
当然，电子设备从多个不同的数据源获取标签数据的方式并不局限于以上实施方式。
在本申请实施例中，数据源可以预先在电子设备中注册，并且电子设备中存储有注册过的数据源的配置信息(例如数据源类型、地址等)，从而被注册的数据源可以被电子设备识别。
步骤S220：当同时获取到来自多个数据源的待进行更新的标签数据时，获取所述 多个数据源中每个数据源的第一优先级，所述第一优先级根据数据源的标签数据在更新时的实时性级别确定。
在本申请实施例中，电子设备在同时获取多个数据源的待进行更新的标签数据时，存在电子设备同时获取到来自多个数据源的待进行更新的标签数据的情况。当电子设备同时获取到来自多个数据源的待进行更新的标签数据时，可以根据不同的数据源，而将标签数据缓存至指定缓冲队列。
在一些实施方式中，当电子设备同时获取到来自多个数据源的标签数据时，可以对多个数据源中每个数据源对应的第一优先级进行确定，以便后续根据数据源的优先级，对不同数据源的标签数据进入指定缓冲队列的先后顺序进行确定。其中，每个数据源对应的第一优先级可以根据该数据源的标签数据在更新时的实时性级别确定，不同数据源的标签数据在更新时的实时性级别可以不同。数据源的标签数据在更新时的实时性级别，可以指该数据源的标签数据在更新时对于实时性的需求级别，实时性级别越高，则该数据源的标签数据则越需要实时的更新。可以理解的，电子设备可以识别数据源的标签数据在更新时的实时性级别，以确定数据源对应的第一优先级。
作为一种具体的实施方式，数据源的标签数据在更新时的实时性级别与数据源对应的第一优先级成正比，也就是说，数据源的标签数据在更新时的实时性级别越高，则该数据源对应的第一优先级越高。例如，数据源1的标签数据在更新时的实时性级别为级别1，数据源2的标签数据在更新时的实时性级别为级别2，数据源3的标签数据在更新时的实时性级别为级别3，级别1、级别2以及级别3的实时性级别依次降低，第一优先级包括优先级1、优先级2以及优先级3，优先级1、优先级2以及优先级3为优先级依次降低的顺序，则级别1对应优先级1，级别2对应优先级2，级别3对应优先级3。当然，以上仅为举例，并不代表对具体的实时性级别与第一优先级的关系的限定。
在一些实施方式中，不同数据源的标签数据在更新时的实时性级别可以预先存储于电子设备，电子设备可以通过识别数据源的类型、标识等，以确定不同数据源的标签数据在更新时的实时性级别。
进一步的，电子设备在确定不同数据源的标签数据在更新时的实时性级别后，则可以根据确定出每个数据源对应的第一优先级，以便对不同数据源的标签数据缓存至指定缓冲队列的先后顺序进行确定，从而可以针对不同数据源对标签数据更新的实时性的需求，而使不同数据源的标签数据缓存到指定缓冲队列的先后顺序不同。
步骤S230：根据所述每个数据源的第一优先级，获取所述多个数据源中每个数据源的标签数据对应的缓存先后顺序，所述缓存先后顺序为标签数据缓存至所述指定缓冲队列的先后顺序。
在本申请实施例中，电子设备在获得每个数据源的第一优先级后，则可以根据数据源的第一优先级，确定数据源的标签数据缓存至指定缓冲队列中的缓冲先后顺序。
在一些实施方式中，步骤S230可以包括：根据所述每个数据源的第一优先级，确定所述多个数据源对应的第一优先级的高低顺序；根据所述高低顺序，确定所述多个数据源中每个数据源的标签数据对应的缓存先后顺序。可以理解的，电子设备可以按照第一优先级从高到低的顺序，依次对每个数据源的标签数据进行排序，从而获得多个数据源的标签数据在进行更新时的更新先后顺序。可以理解的，数据源的第一优先级越靠前，则该数据源的标签数据在更新先后顺序中处于越靠前的位置，例如，数据源1的第一优先级高于数据源2的第一优先级，则数据源1的标签数据在更新先后顺序中处于数据源2的标签数据之前。
步骤S240：根据所述缓存先后顺序，依次将所述每个数据源的标签数据缓存至所述指定缓冲队列。
在本申请实施例中，电子设备在将多个数据源的标签数据缓存至指定缓冲队列中 时，可以按照确定的缓存先后顺序，将每个数据源的标签数据依次缓存至该指定缓冲队列。可以理解的，指定缓冲队列中采用先进先出、后进后出的原则，从而进入到指定缓冲队列的标签数据在被后续取出进行更新时的先后顺序，能与缓存至指定缓冲队列中的先后顺序(即更新先后顺序)对应。
步骤S250：从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新。
电子设备可以根据指定缓冲队列中标签数据的排布顺序，依次读取每个标签数据，并对每个标签数据进行更新，也就是说，指定缓冲队列为先进先出、后进后出的原则，按照指定缓冲队列中标签数据的排布顺序依次取出标签数据，并对标签数据进行更新，即可使得更新顺序能与缓存先后顺序对应，从而保证不同数据源的标签数据更新时的顺序不同，并且更新顺序能与数据源的第一优先级对应。
需要说明的是，本申请实施例中步骤S210、步骤S220以及步骤S230中的方式也可以适用于其他实施例中。
在本申请实施例中，通过从多个不同的数据源获取待进行更新的标签数据，当同时获取到来自多个数据源的标签数据时，根据数据源的第一优先级，对不同数据源的标签数据的缓存至指定缓冲队列中的缓存先后顺序确定，再根据该缓存先后顺序，依次将每个数据源对应的标签数据依次缓存到指定缓冲队列，再从指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新，从而实现通过指定缓冲队列缓存标签数据，可以实现对标签数据更新时的管理，并且实现对多个不同数据源的标签数据进行更新处理，而无需利用多个软件程序分别对不同数据源的标签数据进行更新处理，减少了工作人员对软件程序的开发时间，也提升了标签数据更新时的管控效果。并且保证不同数据源的标签数据更新时的顺序不同，并且更新顺序能与数据源的第一优先级对应，即与数据源的标签数据更新时的实时性级别对应。
请参阅图3，图3示出了本申请又一个实施例提供的标签更新方法的流程示意图。下面将针对图3所示的流程进行详细的阐述，所述标签更新方法具体可以包括以下步骤：
步骤S310：从多个不同的数据源获取待进行更新的标签数据。
在本申请实施例中，步骤S310可以参阅前述实施例的内容，在此不再赘述。
步骤S320：当获取到的标签数据中包括来自同一数据源的多个标签数据时，获取所述多个标签数据中每个标签数据对应的第二优先级，所述第二优先级根据不同的标签数据在更新时的实时性级别确定。
在本申请实施例中，电子设备从多个不同的数据源获取待进行更新标签数据时，可能获得的标签数据中包括来自同一数据源的多个标签数据，也就是说同时获取到同一数据源的多个标签数据。当电子设备获取到的标签数据中包括来自同一数据源的多个标签数据时，则可以对标签数据缓存至指定缓冲队列的缓存先后顺序进行确定。其中，电子设备可以获取每个标签数据对应的第二优先级，并根据第二优先级，确定每个标签数据缓存至指定缓冲队列的缓存先后顺序。
在一些实施方式中，请参阅图4，步骤S320可以包括：
步骤S321A：获取所述多个标签数据中每个标签数据的类型，不同类型的标签数据在更新时的实时性级别不同。
在一些实施方式中，标签数据在更新时的实时性级别可以与标签数据的类型对应，标签数据在更新时的实时性级别也可以与用户标识对应。电子设备在确定标签数据对应的第二优先级时，由于标签数据对应的第二优先级由标签数据更新时的实时性级别确定，因此可以根据标签数据的类型或者标签数据对应的用户标识确定。
作为一种具体的实施方式，步骤S321A可以包括：
获取所述多个标签数据中每个标签数据的类型标识；根据所述每个标签数据的类 型标识，确定所述每个标签数据的类型。
可以理解的，标签数据中可以包括类型标识，类型标识处于标签数据的设定字段，电子设备可以通过获取标签数据中设定字段的数据，从而获得标签数据的类型标识。电子设备在获取到标签数据的类型标识后，则可以根据类型标识，确定标签数据的类型。
步骤S322A：根据所述每个标签数据的类型，确定所述每个标签数据对应的第二优先级。
电子设备在获取到每个标签数据的类型后，则可以根据标签数据的类型，确定标签数据对应的第二优先级。例如，标签数据的类型包括类型1和类型2，类型1的标签数据在更新时的实时性级别高于类型2的标签数据在更新时的实时性级别，则类型1对应优先级1，类型2对应优先级2，且优先级1高于优先级2。通过确定标签数据的类型，
在另一些实施方式中，请参阅图5，步骤S320可以包括：
步骤S321B：获取所述多个标签数据中每个标签数据对应的用户标识。
在该实施方式下，不同用户对应的标签数据在更新时的实时性级别可以不同，例如，刚注册的用户由于需要大量的用户数据作为构建用户标签的基础，以便对用户进行服务，所以需要及时的更新标签数据，又例如，不同用户的身份级别不同，用户对应的标签数据在更新时的实时性级别也不同。用户对应的身份信息可以以用户标识的形式处于标签数据中，电子设备可以获取标签数据对应的用户标识。其中，用户标识可以为国际移动设备识别码(International Mobile Equipment Identity，IMEI)、用户帐号OPENID等，在此不做限定。
步骤S322B：根据所述每个标签数据对应的用户标识，确定所述每个标签数据对应的第二优先级。
电子设备在获取到每个标签数据对应的用户标识后，则可以根据用户标识获取每个标签数据对应的用户标识，确定每个标签数据对应的第二优先级。作为一种具体的实施方式，步骤S22B可以包括：根据所述每个标签数据对应的用户标识，确定所述用户标识对应的对标签更新的实时性级别；根据所述实时性级别，确定所述每个标签数据对应的第二优先级。通过用户标识确定标签数据对应的第二优先级，可以使得标签数据在更新时的实时性级别与用户身份相关时，获得的优先级准确性高。
当然，获取来自同一数据源的多个标签数据中每个标签数据对应的第二优先级的具体方式可以不作为限定。
步骤S330：根据所述每个标签数据对应的第二优先级，确定所述多个标签数据的缓存先后顺序，所述缓存先后顺序为标签数据缓存至所述指定缓冲队列的先后顺序。
在一些实施方式中，根据每个标签数据的第二优先级，确定多个标签数据对应的第一优先级的高低顺序，然后根据高低顺序，确定每个标签数据对应的缓存先后顺序。
步骤S340：按照所述缓存先后顺序，依次将所述每个标签数据缓存至所述指定缓冲队列。
步骤S350：从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新。
在本申请实施例中，步骤S340以及步骤S350可以参阅前述实施例的内容，在此不再赘述。
需要说明的是，本申请实施例中步骤S320以及步骤S330中的方式也可以适用于其他实施例中。
在本申请实施例中，通过从多个不同的数据源获取待进行更新的标签数据，当同时获取到来自同一数据源的多个标签数据时，根据每个标签数据的第二优先级，对不同的标签数据的缓存至指定缓冲队列中的缓存先后顺序确定，再根据该缓存先后顺序， 依次将每个标签数据依次缓存到指定缓冲队列，再从指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新，从而实现通过指定缓冲队列缓存标签数据，可以实现对标签数据更新时的管理，并且实现对多个不同数据源的标签数据进行更新处理，而无需利用多个软件程序分别对不同数据源的标签数据进行更新处理，减少了工作人员对软件程序的开发时间，也提升了标签数据更新时的管控效果。并且保证同一数据源的多个标签数据更新时的顺序不同，并且更新顺序能与标签数据的第二优先级对应，即与标签数据更新时的实时性级别对应。
请参阅图6，图6示出了本申请再一个实施例提供的标签更新方法的流程示意图。下面将针对图6所示的流程进行详细的阐述，所述标签更新方法具体可以包括以下步骤：
步骤S410：从多个不同的数据源获取待进行更新的标签数据。
在本申请实施例中，步骤S410可以参阅前述实施例的内容，在此不再赘述。
步骤S420：当所述获取到的标签数据满足预设条件时，将所述获取到的标签数据缓存至所述指定缓冲队列并插入至所述指定缓冲队列中的目标位置处，所述目标位置为所述指定缓冲队列中设定位置之前的其中一个位置。
在本申请实施例中，电子设备在将获取到的标签数据缓存至指定缓冲队列时，还可以将一个或者多个标签数据插入到指定缓冲队列中的特定位置处，使本次缓存的标签数据尽早的被更新。
在一些实施方式中，电子设备可以将满足预设条件的标签数据，插入至指定缓冲队列中的目标位置处，该目标位置位于指定缓冲队列中设定位置之前的其中一个位置。其中，预设条件可以为标签数据的实时性级别大于设定级别。
作为一种具体的实施方式，步骤S420可以包括：
确定所述获取到的标签数据在更新时的实时性级别；判断所述实时性级别是否大于设定级别；如果大于所述设定级别，将所述获取到的标签数据缓存至所述指定缓冲队列并插入至所述指定缓冲队列中的目标位置处。可以理解的，如果标签数据在更新时的实时性级别大于设定级别，则表示该标签数据满足预设条件，如果标签数据在更新时的实时性级别小于或者等于设定级别，则表示标签数据不满足预设条件。
在一些实施方式中，当确定出标签数据满足预设条件时，则可以确定标签数据需要插入至的目标位置。作为一种具体的实施方式，电子设备可以根据所述获取到的标签数据对应的实时性级别以及所述缓存队列中每个标签数据对应的实时性级别，获取所述指定缓冲队列中的目标位置，所述目标位置之后且邻近所述目标位置的位置处的标签数据对应的实时性级别低于所述获取到的标签数据对应的实时性级别。可以理解的，邻近目标位置且处于目标位置之后的标签数据的实时性级别恰好小于该本次插入的标签数据的实时性级别，从而使得本次插入的标签数据不影响实时性级别相同或者更高的标签数据的更新先后顺序。
步骤S430：从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新。
在本申请实施例中，步骤S430可以参阅前述实施例的内容，在此不再赘述。
需要说明的是，本申请实施例中步骤S420的方式也可以适用于其他实施例中。
本申请实施例提供的标签更新方法，通过从不同的数据源获取待进行更新的标签数据，当获取到的标签数据的实时性级别大于设定级别时，将标签数据插入至指定缓冲队列中的目标位置，后续从指定缓冲队列中读取标签数据进行更新，从而使得标签数据能尽早被更新。
请参阅图7，图7示出了本申请又再一个实施例提供的标签更新方法的流程示意图。下面将针对图7所示的流程进行详细的阐述，所述标签更新方法具体可以包括以下步骤：
步骤S510：从多个不同的数据源获取待进行更新的标签数据。
步骤S520：判断所述指定缓冲队列中的当前数据量是否达到第一设定阈值。
在本申请实施例中，电子设备在将获取的待进行更新的标签数据缓存至指定缓冲队列之前，还可以确定指定缓冲队列中的当前数据量是否达到第一设定阈值。其中，第一设定阈值可以为指定缓冲队列可容纳的数据量大小，也可以为小于指定缓冲队列可容纳的数据量大小的数值，在此不做限定。
步骤S530：如果所述当前数据量未达到第一设定阈值，将获取到的标签数据缓存至指定缓冲队列。
在本申请实施例中，如果指定缓冲队列中的当前数据量未达到第一设定阈值，则表示指定缓冲队列还可以容纳其他的标签数据，因此可以将获取到的标签数据缓存至该指定缓冲队列。
在一些实施方式中，步骤S530可以包括：如果所述指定缓冲队列中的当前数据量未达到所述第一设定阈值，判断所述当前数据量是否达到第二设定阈值，所述第二设定阈值小于所述第一设定阈值；如果所述当前数据量未达到所述第二设定阈值，将获取到的标签数据缓存至所述指定缓冲队列。
其中，第二设定阈值为小于第一设定阈值的阈值。如果指定缓冲队列中的当前数据量达到第二设定阈值，则表示指定缓冲队列中的数据量较多，更新处理任务比较繁忙，可能导致更新任务崩溃。因此，可以在前数据量未达到所述第二设定阈值时，将获取到的标签数据缓存至所述指定缓冲队列。
在该实施方式下，该标签更新方法还可以包括：如果所述当前数据量达到所述第二设定阈值，在释放当前处于空闲状态的空闲资源之后，将获取到的标签数据缓存至所述指定缓冲队列。可以理解的，由于指定缓冲队列中的当前数据量达到第二设定阈值，可能导致处理量过多，而使得更新任务崩溃，因此电子设备可以释放掉处于空闲状态的空闲资源，然后再将标签数据缓存至指定缓冲队列中，以使更多的资源分配至标签数据的更新任务，避免更新任务崩溃。其中，空闲资源可以为处于后台超过设定时长并且未被使用的进程所占有的资源，也可以指其他当前未被使用的进程所占有的资源，在此不做限定。
步骤S540：如果所述当前数据量达到第一设定阈值，确定所述指定缓冲队列中每个标签数据对应的缓存时长。
在本申请实施例中，如果指定缓冲队列中的当前数据量达到第一设定阈值时，则表示指定缓冲队列不能容纳其他的标签数据。因此，可以对指定缓冲队列中失去时效性的标签数据进行清楚，方便当前的标签数据缓存至指定缓冲队列中。
在一些实施方式中，电子设备可以确定指定缓冲队列中每个标签数据对应的缓存时长，该缓存时长指标签时间缓存至指定缓冲队列后，存在于指定缓冲队列中的时长。
步骤S550：获取所述指定缓冲队列中的第一标签数据，所述第一标签数据对应的缓存时长大于设定时长。
在一些实施方式中，电子设备在确定指定缓冲队列中每个标签数据对应的缓存时长之后，则可以根据每个标签数据的缓存时长，确定缓存时长大于设定时长的标签数据，并将缓存时长大于设定时长的标签数据作为第一标签数据，第一标签数据即为失去时效性的标签数据。
步骤S560：从所述指定缓冲队列中清除所述第一标签数据后，如果所述指定缓冲队列中的当前数据量未达到所述第一设定阈值，将获取到的标签数据缓存至所述指定缓冲队列。
在本申请实施例中，电子设备在获取到第一标签数据之后，则可以从指定缓冲队列中清除第一标签数据。并在清除第一标签数据之后，确定指定缓冲队列中的当前数据量是否达到第一设定阈值，如果未达到第一设定阈值，则表示在清除第一标签数据 之后，指定缓冲队列可以容纳其他标签数据，因此可以将获取到的标签数据缓存至该指定缓冲队列。
步骤S570：从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新。
在本申请实施例中，步骤S570可以参阅前述实施例的内容，在此不再赘述。
需要说明的是，步骤S520至步骤S560的处理方式也适用于其他实施例中。
在一些实施方式中，该标签更新方法还可以包括：实时监测对标签数据的更新速度；如果所述更新速度低于设定速度，释放当前处于空闲状态的空闲资源。
可以理解的，电子设备可以根据预设时长内电子设备更新的标签数据的数量，确定出对标签数据的更新速度。如果更新速度低于设定速度，则表示对标签数据的更新较慢，因此可以释放当前处于空闲状态的空闲资源，以使更多的资源分配至标签数据的更新任务，提升对标签数据的更新速度。
在一些实施方式中，该标签更新方法还可以包括：获取所述指定缓冲队列中重复存在的标签数据；将所述重复存在的标签数据进行删除。
在一些实施方式中，电子设备在将标签数据缓存至指定缓冲队列之后，还可以确定指定缓冲队列中重复存在的标签数据，并对重复存在的标签数据进行清除，以减少电子设备更新标签数据时的处理量。
在一种实例中，本申请实施例提供的标签更新方法的原理示意图可以如图8所示，其中，统一任务管理服务701为中枢部分，因为数据源多种多样，为了资源利用的最大化和标签数据源接入的成本最小化，建立统一的统一任务管理服务701对已有的数据源进行资源调配管理和对新数据源到来时，只需向任务管理服务进行注册配置，即可接入，实现高扩展性。并且统一任务管理服务701管理整个方案中的各个模块，对于各个模块的协作和维护起到调度和监控作用。指定缓冲队列702可以为MQ(message queue)队列，用于缓存多个不同的数据源的标签数据，并保证数据的一致性，使得数据源在发送待进行更新的标签数据时，可以不用考虑电子设备对标签数据的处理速度，尽可能快的将标签数据给到电子设备写入指定缓冲队列，不用为了兼顾标签存储系统的速度而长期挂起任务，数据写入完就释放资源给其他数据源，提高了资源的利用率。预先建立的统一更新程序703可以实时的从指定缓冲队列读取标签数据，并向标签存储系统704(标签数据库)中写入标签数据，统一更新程序703还可以统一对标签数据进行相应的清洗和处理，针对一些异常数据和重复数据，在此处可进行治理，也可以针对性的压缩数据。
本申请实施例提供的标签更新方法，通过从多个不同的数据源获取待进行更新的标签数据，当电子设备将获取的标签数据缓存至指定缓冲队列时，对指定缓冲队列中的数据量进行确定后，在指定缓冲队列的当前数据量未达到第一数据量时，才将获取到的标签数据缓存至指定缓冲队列，从指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新，从而实现通过指定缓冲队列缓存标签数据，可以实现对标签数据更新时的管理，并且实现对多个不同数据源的标签数据进行更新处理，而无需利用多个软件程序分别对不同数据源的标签数据进行更新处理，减少了工作人员对软件程序的开发时间，也提升了标签数据更新时的管控效果。
请参阅图9，其示出了本申请实施例提供的一种标签更新装置400的结构框图。该标签更新装置400包括：数据获取模块410、数据缓存模块420以及数据更新模块430。其中，所述数据获取模块410用于从多个不同的数据源获取待进行更新的标签数据；所述数据缓存模块420用于将获取到的标签数据缓存至指定缓冲队列，所述指定缓冲队列用于缓存待进行更新的标签数据；所述数据更新模块430用于从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新。
在一些实施方式中，数据缓存模块420可以包括：第一优先级确定单元、第一顺 序确定单元以及第一缓存单元。第一优先级确定单元用于当同时获取到来自多个数据源的待进行更新的标签数据时，获取所述多个数据源中每个数据源的第一优先级，所述第一优先级根据数据源的标签数据在更新时的实时性级别确定；第一顺序确定单元用于根据所述每个数据源的第一优先级，获取所述多个数据源中每个数据源的标签数据对应的缓存先后顺序，所述缓存先后顺序为标签数据缓存至所述指定缓冲队列的先后顺序；第一缓存单元用于根据所述缓存先后顺序，依次将所述每个数据源的标签数据缓存至所述指定缓冲队列。
在该实施方式下，第一优先级确定单元可以具体用于：根据所述每个数据源的第一优先级，确定所述多个数据源对应的第一优先级的高低顺序；根据所述高低顺序，确定所述多个数据源中每个数据源的标签数据对应的缓存先后顺序。
在一些实施方式中，数据缓存模块420可以包括：第二优先级确定单元、第二顺序确定单元以及第二缓存单元。第二优先级确定单元用于当获取到的标签数据中包括来自同一数据源的多个标签数据时，获取所述多个标签数据中每个标签数据对应的第二优先级，所述第二优先级根据不同的标签数据在更新时的实时性级别确定；第二顺序确定单元用于根据所述每个标签数据对应的第二优先级，确定所述多个标签数据的缓存先后顺序，所述缓存先后顺序为标签数据缓存至所述指定缓冲队列的先后顺序；第二缓存单元用于按照所述缓存先后顺序，依次将所述每个标签数据缓存至所述指定缓冲队列。
在一些实施方式中，第二优先级确定单元可以具体用于：获取所述多个标签数据中每个标签数据的类型，不同类型的标签数据在更新时的实时性级别不同；根据所述每个标签数据的类型，确定所述每个标签数据对应的第二优先级。
在该实施方式下，第二优先级确定单元获取所述多个标签数据中每个标签数据的类型，可以包括：获取所述多个标签数据中每个标签数据的类型标识；根据所述每个标签数据的类型标识，确定所述每个标签数据的类型。
在另一些实施方式中，第二优先级确定单元也可以具体用于：获取所述多个标签数据中每个标签数据对应的用户标识；根据所述每个标签数据对应的用户标识，确定所述每个标签数据对应的第二优先级。
在该实施方式下，第二优先级确定单元根据所述每个标签数据对应的用户标识，确定所述每个标签数据对应的第二优先级，包括：根据所述每个标签数据对应的用户标识，确定所述用户标识对应的对标签更新的实时性级别；根据所述实时性级别，确定所述每个标签数据对应的第二优先级。
在一些实施方式中，数据缓存模块420可以具体用于：当所述获取到的标签数据满足预设条件时，将所述获取到的标签数据缓存至所述指定缓冲队列并插入至所述指定缓冲队列中的目标位置处，所述目标位置为所述指定缓冲队列中设定位置之前的其中一个位置。
在该实施方式下，数据缓存模块420可以具体用于：确定所述获取到的标签数据在更新时的实时性级别；判断所述实时性级别是否大于设定级别；如果大于所述设定级别，将所述获取到的标签数据缓存至所述指定缓冲队列并插入至所述指定缓冲队列中的目标位置处。
进一步的，数据缓存模块420还可以用于在所述将所述获取到的标签数据缓存至所述指定缓冲队列并插入至所述指定缓冲队列中的目标位置处之前，根据所述获取到的标签数据对应的实时性级别以及所述缓存队列中每个标签数据对应的实时性级别，获取所述指定缓冲队列中的目标位置，所述目标位置之后且邻近所述目标位置的位置处的标签数据对应的实时性级别低于所述获取到的标签数据对应的实时性级别。
在一些实施方式中，该数据缓存模块420可以包括：数据量判断单元以及第三缓存单元。数据量判断单元用于判断所述指定缓冲队列中的当前数据量是否达到第一设 定阈值；第三缓存单元用于如果所述当前数据量未达到第一设定阈值，将获取到的标签数据缓存至指定缓冲队列。
作为一种实施方式，该数据缓存模块420还可以包括：缓存时长确定单元以及标签获取单元。缓存时长确定单元用于如果所述当前数据量达到第一设定阈值，确定所述指定缓冲队列中每个标签数据对应的缓存时长；标签获取单元用于获取所述指定缓冲队列中的第一标签数据，所述第一标签数据对应的缓存时长大于设定时长；第三缓存单元还可以用于从所述指定缓冲队列中清除所述第一标签数据后，如果所述指定缓冲队列中的当前数据量未达到所述第一设定阈值，将获取到的标签数据缓存至所述指定缓冲队列。
在一些实施方式中，第三缓存单元可以具体用于：如果所述指定缓冲队列中的当前数据量未达到所述第一设定阈值，判断所述当前数据量是否达到第二设定阈值，所述第二设定阈值小于所述第一设定阈值；如果所述当前数据量未达到所述第二设定阈值，将获取到的标签数据缓存至所述指定缓冲队列。
在一些实施方式中，数据缓存模块420还可以用于：如果所述当前数据量达到所述第二设定阈值，在释放当前处于空闲状态的空闲资源之后，将获取到的标签数据缓存至所述指定缓冲队列。
在一些实施方式中，该标签更新装置400还可以包括：速度监测模块以及资源释放模块。速度监测模块用于实时监测对标签数据的更新速度；资源释放模块用于如果所述更新速度低于设定速度，释放当前处于空闲状态的空闲资源。
在一些实施方式中，该标签更新装置400还可以包括：重复数据获取模块以及数据删除模块。重复数据获取模块用于获取所述指定缓冲队列中重复存在的标签数据；数据删除模块用于将所述重复存在的标签数据进行删除。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述装置和模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，模块相互之间的耦合可以是电性，机械或其它形式的耦合。
另外，在本申请各个实施例中的各功能模块可以集成在一个处理模块中，也可以是各个模块单独物理存在，也可以两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。
综上所述，本申请提供的方案，通过从多个不同的数据源获取待进行更新的标签数据，将获取到的标签数据缓存至指定缓冲队列，该指定缓冲队列用于缓存待进行更新的标签数据，然后从指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新，从而实现对多个不同数据源的标签数据进行更新处理，并且通过指定缓冲队列缓存标签数据，可以实现对标签数据更新时的管理。
请参考图11，其示出了本申请实施例提供的一种电子设备的结构框图。该电子设备100可以是服务器、PC电脑、移动终端等能够运行应用程序的电子设备。本申请中的电子设备100可以包括一个或多个如下部件：处理器110、存储器120、触摸屏130以及一个或多个应用程序，其中一个或多个应用程序可以被存储在存储器120中并被配置为由一个或多个处理器110执行，一个或多个程序配置用于执行如前述方法实施例所描述的方法。
处理器110可以包括一个或者多个处理核。处理器110利用各种接口和线路连接整个电子设备100内的各个部分，通过运行或执行存储在存储器120内的指令、程序、代码集或指令集，以及调用存储在存储器120内的数据，执行电子设备100的各种功能和处理数据。可选地，处理器110可以采用数字信号处理(Digital Signal Processing，DSP)、现场可编程门阵列(Field－Programmable Gate Array，FPGA)、可编程逻辑阵列(Programmable Logic Array，PLA)中的至少一种硬件形式来实现。处理器110 可集成中央处理器(Central Processing Unit，CPU)、图像处理器(Graphics Processing Unit，GPU)和调制解调器等中的一种或几种的组合。其中，CPU主要处理操作系统、用户界面和应用程序等；GPU用于负责显示内容的渲染和绘制；调制解调器用于处理无线通信。可以理解的是，上述调制解调器也可以不集成到处理器110中，单独通过一块通信芯片进行实现。
存储器120可以包括随机存储器(Random Access Memory，RAM)，也可以包括只读存储器(Read-Only Memory)。存储器120可用于存储指令、程序、代码、代码集或指令集。存储器120可包括存储程序区和存储数据区，其中，存储程序区可存储用于实现操作系统的指令、用于实现至少一个功能的指令(比如触控功能、声音播放功能、图像播放功能等)、用于实现下述各个方法实施例的指令等。存储数据区还可以存储终端100在使用中所创建的数据(比如电话本、音视频数据、聊天记录数据)等。
请参考图11，其示出了本申请实施例提供的一种计算机可读存储介质的结构框图。该计算机可读介质800中存储有程序代码，所述程序代码可被处理器调用执行上述方法实施例中所描述的方法。
计算机可读存储介质800可以是诸如闪存、EEPROM(电可擦除可编程只读存储器)、EPROM、硬盘或者ROM之类的电子存储器。可选地，计算机可读存储介质800包括非易失性计算机可读介质(non-transitory computer-readable storage medium)。计算机可读存储介质800具有执行上述方法中的任何方法步骤的程序代码810的存储空间。这些程序代码可以从一个或者多个计算机程序产品中读出或者写入到这一个或者多个计算机程序产品中。程序代码810可以例如以适当形式进行压缩。
最后应说明的是：以上实施例仅用以说明本申请的技术方案，而非对其限制；尽管参照前述实施例对本申请进行了详细的说明，本领域的普通技术人员当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分技术特征进行等同替换；而这些修改或者替换，并不驱使相应技术方案的本质脱离本申请各实施例技术方案的精神和范围。

Claims (20)

  1. 一种标签更新方法，其特征在于，所述方法包括：
    从多个不同的数据源获取待进行更新的标签数据；
    将获取到的标签数据缓存至指定缓冲队列，所述指定缓冲队列用于缓存待进行更新的标签数据；
    从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新。
  2. 根据权利要求1所述的方法，其特征在于，所述将获取到的标签数据缓存至指定缓冲队列，包括：
    当同时获取到来自多个数据源的待进行更新的标签数据时，获取所述多个数据源中每个数据源的第一优先级，所述第一优先级根据数据源的标签数据在更新时的实时性级别确定；
    根据所述每个数据源的第一优先级，获取所述多个数据源中每个数据源的标签数据对应的缓存先后顺序，所述缓存先后顺序为标签数据缓存至所述指定缓冲队列的先后顺序；
    根据所述缓存先后顺序，依次将所述每个数据源的标签数据缓存至所述指定缓冲队列。
  3. 根据权利要求2所述的方法，其特征在于，所述根据所述每个数据源的第一优先级，获取所述多个数据源中每个数据源的标签数据对应的缓存先后顺序，包括：
    根据所述每个数据源的第一优先级，确定所述多个数据源对应的第一优先级的高低顺序；
    根据所述高低顺序，确定所述多个数据源中每个数据源的标签数据对应的缓存先后顺序。
  4. 根据权利要求1-3任一项所述的方法，其特征在于，所述将获取到的标签数据缓存至指定缓冲队列，包括：
    当获取到的标签数据中包括来自同一数据源的多个标签数据时，获取所述多个标签数据中每个标签数据对应的第二优先级，所述第二优先级根据不同的标签数据在更新时的实时性级别确定；
    根据所述每个标签数据对应的第二优先级，确定所述多个标签数据的缓存先后顺序，所述缓存先后顺序为标签数据缓存至所述指定缓冲队列的先后顺序；
    按照所述缓存先后顺序，依次将所述每个标签数据缓存至所述指定缓冲队列。
  5. 根据权利要求4所述的方法，其特征在于，所述获取所述多个标签数据中每个标签数据对应的第二优先级，包括：
    获取所述多个标签数据中每个标签数据的类型，不同类型的标签数据在更新时的实时性级别不同；
    根据所述每个标签数据的类型，确定所述每个标签数据对应的第二优先级。
  6. 根据权利要求5所述的方法，其特征在于，所述获取所述多个标签数据中每个标签数据的类型，包括：
    获取所述多个标签数据中每个标签数据的类型标识；
    根据所述每个标签数据的类型标识，确定所述每个标签数据的类型。
  7. 根据权利要求4所述的方法，其特征在于，所述获取所述多个标签数据中每个标签数据对应的第二优先级，包括：
    获取所述多个标签数据中每个标签数据对应的用户标识；
    根据所述每个标签数据对应的用户标识，确定所述每个标签数据对应的第二优先 级。
  8. 根据权利要求7所述的方法，其特征在于，所述根据所述每个标签数据对应的用户标识，确定所述每个标签数据对应的第二优先级，包括：
    根据所述每个标签数据对应的用户标识，确定所述用户标识对应的对标签更新的实时性级别；
    根据所述实时性级别，确定所述每个标签数据对应的第二优先级。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述将获取到的标签数据缓存至指定缓冲队列，包括：
    当所述获取到的标签数据满足预设条件时，将所述获取到的标签数据缓存至所述指定缓冲队列并插入至所述指定缓冲队列中的目标位置处，所述目标位置为所述指定缓冲队列中设定位置之前的其中一个位置。
  10. 根据权利要求9所述的方法，其特征在于，所述当所述获取到的标签数据满足预设条件时，将所述获取到的标签数据缓存至所述指定缓冲队列并插入至所述指定缓冲队列中的目标位置处，包括：
    确定所述获取到的标签数据在更新时的实时性级别；
    判断所述实时性级别是否大于设定级别；
    如果大于所述设定级别，将所述获取到的标签数据缓存至所述指定缓冲队列并插入至所述指定缓冲队列中的目标位置处。
  11. 根据权利要求10所述的方法，其特征在于，在所述将所述获取到的标签数据缓存至所述指定缓冲队列并插入至所述指定缓冲队列中的目标位置处之前，所述方法还包括：
    根据所述获取到的标签数据对应的实时性级别以及所述缓存队列中每个标签数据对应的实时性级别，获取所述指定缓冲队列中的目标位置，所述目标位置之后且邻近所述目标位置的位置处的标签数据对应的实时性级别低于所述获取到的标签数据对应的实时性级别。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，所述将获取到的标签数据缓存至指定缓冲队列，包括：
    判断所述指定缓冲队列中的当前数据量是否达到第一设定阈值；
    如果所述当前数据量未达到第一设定阈值，将获取到的标签数据缓存至指定缓冲队列。
  13. 根据权利要求12所述的方法，其特征在于，所述方法还包括：
    如果所述当前数据量达到第一设定阈值，确定所述指定缓冲队列中每个标签数据对应的缓存时长；
    获取所述指定缓冲队列中的第一标签数据，所述第一标签数据对应的缓存时长大于设定时长；
    从所述指定缓冲队列中清除所述第一标签数据后，如果所述指定缓冲队列中的当前数据量未达到所述第一设定阈值，将获取到的标签数据缓存至所述指定缓冲队列。
  14. 根据权利要求12所述的方法，其特征在于，所述如果所述指定缓冲队列中的当前数据量未达到所述第一设定阈值，将获取到的标签数据缓存至所述指定缓冲队列，包括：
    如果所述指定缓冲队列中的当前数据量未达到所述第一设定阈值，判断所述当前数据量是否达到第二设定阈值，所述第二设定阈值小于所述第一设定阈值；
    如果所述当前数据量未达到所述第二设定阈值，将获取到的标签数据缓存至所述指定缓冲队列。
  15. 根据权利要求14所述的方法，其特征在于，所述方法还包括：
    如果所述当前数据量达到所述第二设定阈值，在释放当前处于空闲状态的空闲资 源之后，将获取到的标签数据缓存至所述指定缓冲队列。
  16. 根据权利要求1-15所述的方法，其特征在于，所述方法还包括：
    实时监测对标签数据的更新速度；
    如果所述更新速度低于设定速度，释放当前处于空闲状态的空闲资源。
  17. 根据权利要求1-16所述的方法，其特征在于，所述方法还包括：
    获取所述指定缓冲队列中重复存在的标签数据；
    将所述重复存在的标签数据进行删除。
  18. 一种标签更新装置，其特征在于，所述装置包括：数据获取模块、数据缓存模块以及数据更新模块，其中，
    所述数据获取模块用于从多个不同的数据源获取待进行更新的标签数据；
    所述数据缓存模块用于将获取到的标签数据缓存至指定缓冲队列，所述指定缓冲队列用于缓存待进行更新的标签数据；
    所述数据更新模块用于从所述指定缓冲队列中读取缓存的标签数据，并对读取的标签数据进行更新。
  19. 一种电子设备，其特征在于，包括：
    一个或多个处理器；
    存储器；
    一个或多个应用程序，其中所述一个或多个应用程序被存储在所述存储器中并被配置为由所述一个或多个处理器执行，所述一个或多个程序配置用于执行如权利要求1-17任一项所述的方法。
  20. 一种计算机可读取存储介质，其特征在于，所述计算机可读取存储介质中存储有程序代码，所述程序代码可被处理器调用执行如权利要求1-17任一项所述的方法。
PCT/CN2019/116729 2019-11-08 2019-11-08 标签更新方法、装置、电子设备及存储介质 WO2021087990A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2019/116729 WO2021087990A1 (zh) 2019-11-08 2019-11-08 标签更新方法、装置、电子设备及存储介质
CN201980100120.XA CN114402313A (zh) 2019-11-08 2019-11-08 标签更新方法、装置、电子设备及存储介质

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/116729 WO2021087990A1 (zh) 2019-11-08 2019-11-08 标签更新方法、装置、电子设备及存储介质

Publications (1)

Publication Number Publication Date
WO2021087990A1 true WO2021087990A1 (zh) 2021-05-14

Family

ID=75849251

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/116729 WO2021087990A1 (zh) 2019-11-08 2019-11-08 标签更新方法、装置、电子设备及存储介质

Country Status (2)

Country Link
CN (1) CN114402313A (zh)
WO (1) WO2021087990A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220417169A1 (en) * 2019-12-09 2022-12-29 Lynxi Technologies Co., Ltd. Data processing method, data processing apparatus, electronic device, storage medium, and program product
CN116033491A (zh) * 2023-03-29 2023-04-28 至控科技(湖州)创新研究院有限公司 实时定位系统中的数据压缩缓存上传方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100023535A1 (en) * 2008-07-23 2010-01-28 Institute For Information Industry Apparatus, method, and computer program product thereof for storing a data and data storage system comprising the same
CN105005617A (zh) * 2015-07-21 2015-10-28 领航动力信息系统有限公司 一种时间序列数据的存储方法及装置
CN106469158A (zh) * 2015-08-17 2017-03-01 杭州海康威视系统技术有限公司 数据同步方法和装置
CN107562804A (zh) * 2017-08-08 2018-01-09 上海数据交易中心有限公司 数据缓存服务系统及方法、终端

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100023535A1 (en) * 2008-07-23 2010-01-28 Institute For Information Industry Apparatus, method, and computer program product thereof for storing a data and data storage system comprising the same
CN105005617A (zh) * 2015-07-21 2015-10-28 领航动力信息系统有限公司 一种时间序列数据的存储方法及装置
CN106469158A (zh) * 2015-08-17 2017-03-01 杭州海康威视系统技术有限公司 数据同步方法和装置
CN107562804A (zh) * 2017-08-08 2018-01-09 上海数据交易中心有限公司 数据缓存服务系统及方法、终端

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220417169A1 (en) * 2019-12-09 2022-12-29 Lynxi Technologies Co., Ltd. Data processing method, data processing apparatus, electronic device, storage medium, and program product
US11863461B2 (en) * 2019-12-09 2024-01-02 Lynxi Technologies Co., Ltd. Data processing method, data processing apparatus, electronic device, storage medium, and program product
CN116033491A (zh) * 2023-03-29 2023-04-28 至控科技(湖州)创新研究院有限公司 实时定位系统中的数据压缩缓存上传方法和装置
CN116033491B (zh) * 2023-03-29 2023-07-04 至控科技(湖州)创新研究院有限公司 实时定位系统中的数据压缩缓存上传方法和装置

Also Published As

Publication number Publication date
CN114402313A (zh) 2022-04-26

Similar Documents

Publication Publication Date Title
CN109815028B (zh) 数据同步的系统、方法、装置和计算机存储介质
CN109947668B (zh) 存储数据的方法和装置
CN111159436B (zh) 一种推荐多媒体内容的方法、装置及计算设备
CN110598138A (zh) 基于缓存的处理方法和装置
CN109951538A (zh) 数据处理方法、装置、系统、电子设备及存储介质
US11487571B2 (en) Method and system for efficient utilization of resources in containers
CN109343902A (zh) 音频处理组件的运行方法、装置、终端及存储介质
WO2021087990A1 (zh) 标签更新方法、装置、电子设备及存储介质
CN105577772A (zh) 素材接收方法、素材上传方法及装置
CN110704400A (zh) 实时数据同步方法以及装置、服务器
CN111930706A (zh) 基于远程调用的分布式网络文件存储系统和方法
WO2021068113A1 (zh) 时长统计方法、装置、电子设备和计算机可读介质
CN104135429A (zh) 一种信息推送方法和装置
CN111813573A (zh) 管理平台与机器人软件的通信方法及其相关设备
CN113590437B (zh) 一种告警信息处理方法、装置、设备和介质
CN110247963A (zh) 一种数据推送方法及系统
CN107943581B (zh) 应用清理方法、装置、存储介质及电子设备
CN113783913A (zh) 一种消息推送管理方法和装置
WO2021179170A1 (zh) 数据推送方法、装置、服务器及存储介质
CN112860513A (zh) 应用无响应监测方法、装置、设备及存储介质
US20150249625A1 (en) Using analytics to optimize performance of a messaging system via topic migration to alternate delivery methods
WO2021087981A1 (zh) 标签数据的更新方法、装置、电子设备及存储介质
WO2022111733A1 (zh) 消息处理方法、装置及电子设备
WO2021087970A1 (zh) 标签数据的更新方法、装置、电子设备及存储介质
CN113709214A (zh) 消息处理方法及装置、电子设备及存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19951829

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19951829

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 28/10/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 19951829

Country of ref document: EP

Kind code of ref document: A1