WO2022257604A1 - 一种用户标签的确定方法和装置 - Google Patents
一种用户标签的确定方法和装置 Download PDFInfo
- Publication number
- WO2022257604A1 WO2022257604A1 PCT/CN2022/087295 CN2022087295W WO2022257604A1 WO 2022257604 A1 WO2022257604 A1 WO 2022257604A1 CN 2022087295 W CN2022087295 W CN 2022087295W WO 2022257604 A1 WO2022257604 A1 WO 2022257604A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- tag
- time
- label
- real
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000004044 response Effects 0.000 claims abstract description 40
- 238000004590 computer program Methods 0.000 claims description 9
- 238000004364 calculation method Methods 0.000 abstract description 6
- 230000006399 behavior Effects 0.000 description 98
- 238000010586 diagram Methods 0.000 description 13
- 239000002699 waste material Substances 0.000 description 11
- 238000004891 communication Methods 0.000 description 7
- 238000004904 shortening Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 230000000694 effects Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000002372 labelling Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 4
- 230000003542 behavioural effect Effects 0.000 description 3
- 230000001186 cumulative effect Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
Definitions
- the present disclosure relates to the field of computer technology, in particular to a method and device for determining a user label.
- the embodiments of the present disclosure provide a method and device for determining user tags, which can provide different query methods for different types of user tag query requests, effectively improve the calculation efficiency of user tags, save computing resources, and shorten the Determine the response time of user tags, expand the applicable scenarios, and be able to meet high-concurrency query requests.
- a method for determining a user label including:
- the user label type is an offline label type, then determine the first user label from a plurality of offline labels in the database according to the user number and the time interval, and send the first user label to the requester;
- the user tag type is a real-time tag type
- determine the real-time user behavior data corresponding to the user number in the time interval determine the second user tag according to the real-time user behavior data, and send the second user tag to the requester.
- the generation step of the offline label includes:
- the label value is calculated, and offline labels corresponding to different user numbers are generated according to the label value and label conditions.
- the new user behavior data within the time interval is obtained, and the offline label is updated according to the new user behavior data.
- the real-time user behavior data is cleaned according to the tag value corresponding to the offline tag, and the cleaned real-time user behavior data is placed in the database.
- the user tag types include offline tag types and real-time tag types
- the time interval corresponding to the offline label type determine the first user label corresponding to the user number from the database, and judge whether the first user label satisfies the label condition indicated in the acquisition request;
- determine the real-time user behavior data corresponding to the user number in the time interval corresponding to the real-time tag type, and the first offline data corresponding to the first user tag determine the target user tag according to the real-time user behavior data and the first offline data, and The target user tag is sent to the requester.
- it also includes: if the first user label does not meet the label conditions indicated in the acquisition request,
- an apparatus for determining a user label including:
- a label type determination module configured to determine the user label type according to the time interval indicated in the acquisition request in response to the acquisition request for the user label
- Label determination module if the user label type is an offline label type, it is used to determine the first user label from a plurality of offline labels in the database according to the user number and time interval, and send the first user label to the requester; if the user label type It is a real-time tag type, used to determine the real-time user behavior data corresponding to the user number in the time interval, determine the second user tag according to the real-time user behavior data, and send the second user tag to the requester.
- an electronic device including:
- processors one or more processors
- the one or more processors When the one or more programs are executed by the one or more processors, the one or more processors implement any one of the methods for determining the user label described above.
- a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any method for determining a user label as described above is implemented.
- FIG. 1 is a schematic diagram of the main flow of a method for determining a user label according to a first embodiment of the present disclosure
- FIG. 2 is a schematic diagram of the main flow of a method for determining a user label according to a second embodiment of the present disclosure
- Fig. 3 is a schematic diagram of main modules of an apparatus for determining a user label provided according to an embodiment of the present disclosure
- FIG. 4 is an exemplary system architecture diagram to which embodiments of the present disclosure can be applied;
- Fig. 5 is a schematic structural diagram of a computer system suitable for implementing a terminal device or a server according to an embodiment of the present disclosure.
- Fig. 1 is a schematic diagram of the main flow of a method for determining a user label provided according to a first embodiment of the present disclosure; as shown in Fig. 1 , the method for determining a user label provided by an embodiment of the present disclosure mainly includes:
- Step S101 in response to an acquisition request for a user label, determine a user label type according to a time interval indicated in the acquisition request.
- user behavior data is divided into offline data and real-time data according to time intervals (such as data generated on the current day is real-time data, and data generated before the current day is offline data.
- time intervals such as data generated on the current day is real-time data, and data generated before the current day is offline data.
- the division is just an example
- the offline label is calculated for the offline data; for the real-time label, it needs to be determined by calculating the real-time data.
- the type of the user tag is determined according to the time interval indicated in the acquisition request, and then for different types of user tags, different methods are used to determine and send it to the requesting party.
- Step S102 if the user tag type is an offline tag type, then determine the first user tag from multiple offline tags in the database according to the user number and time interval, and send the first user tag to the requester.
- the acquisition request indicates an offline label type
- the step of generating the above-mentioned offline label includes:
- the label value is calculated, and offline labels corresponding to different user numbers are generated according to the label value and label conditions.
- offline tags are directly generated for offline data, which helps to shorten the response time and meet the high-concurrency query requirements.
- offline tags may also be calculated in advance for offline data of different service types according to service requirements, so as to avoid waste of computing resources.
- the above method further includes:
- the new user behavior data within the time interval is obtained, and the offline label is updated according to the new user behavior data.
- the generated offline label needs to be updated in time as time goes by.
- Step S103 if the user tag type is a real-time tag type, determine the real-time user behavior data corresponding to the user number in the time interval, determine the second user tag according to the real-time user behavior data, and send the second user tag to the requester.
- the user tag type is represented as a real-time tag type
- only the time interval corresponding to the real-time tag type is indicated in the current acquisition request. Therefore, the amount of real-time user behavior data corresponding to this part of the time interval will not be very large.
- the above method further includes:
- the real-time user behavior data is cleaned according to the tag value corresponding to the offline tag, and the cleaned real-time user behavior data is placed in the database.
- the user label only indicates the time interval, and also constrains the label conditions. According to the label value of the offline label, it can be judged whether the corresponding label condition is met. Yuan, there is no need to obtain real-time behavior data. Through the above settings, the amount of data required for calculating and implementing labels is effectively reduced, and computing resources are saved.
- the process of placing the cleaned real-time user behavior data in the database also includes:
- the corresponding relationship between user numbers and real-time user behavior data is recorded in the query engine, which helps users to quickly query the corresponding user real-time tags if the user tag type is a real-time tag when sending a request to the query engine. Behavioral data to further reduce response times for determining user tags.
- it further includes: if the user tag types include offline tag types and real-time tag types,
- the time interval corresponding to the offline label type determine the first user label corresponding to the user number from the database, and judge whether the first user label satisfies the label condition indicated in the acquisition request;
- determine the real-time user behavior data corresponding to the user number in the time interval corresponding to the real-time tag type, and the first offline data corresponding to the first user tag determine the target user tag according to the real-time user behavior data and the first offline data, and The target user tag is sent to the requester.
- time interval indicated in the acquisition request sent by the user covers not only the time interval corresponding to the real-time tag type, but also the time interval corresponding to the offline tag type, at this time, priority is given to judging the time interval corresponding to the first user tag (user tag calculated in advance). Whether the tag value meets the tag conditions indicated in the request; if yes, just send the first user tag to the requester; if not, you need to obtain real-time user behavior data again, combined with the data corresponding to the first user tag to Calculating target user tags satisfies the accuracy of user tags, shortens response time as much as possible, avoids waste of computing resources, and improves user experience.
- it further includes: if the first user label does not meet the label condition indicated in the acquisition request,
- the real-time user behavior data can be directly used to update the first user tag, further shortening the response time and saving computing resources.
- the user label type is determined according to the time interval indicated in the acquisition request; if the user label type is an offline label type, then according to the user number and the time interval from Determine the first user tag among the multiple offline tags in the database, and send the first user tag to the requester; if the user tag type is a real-time tag type, determine the real-time user behavior data corresponding to the user number in the time interval, according to the real-time user behavior The data determines the second user tag and sends the second user tag to the technical means of the requester, so it overcomes the existing methods of low computing efficiency, more waste of computing resources, long response time, and fewer applicable scenarios.
- Fig. 2 is a schematic diagram of the main flow of the method for determining the user label provided according to the second embodiment of the present disclosure; as shown in Fig. 2, the method for determining the user label provided by the embodiment of the present disclosure mainly includes:
- Step S201 acquiring user behavior data corresponding to multiple user numbers, and determining offline data according to the time interval to which the user behavior data belongs.
- offline tags are directly generated for offline data, which helps to shorten the response time and meet the high-concurrency query requirements.
- Step S202 according to the user behavior data corresponding to different user numbers determined from the offline data in the first time interval, calculate tag values, and generate offline tags corresponding to different user numbers according to the tag values and tag conditions.
- offline tags may also be calculated in advance for offline data of different service types according to service requirements, so as to avoid waste of computing resources.
- Step S203 determine the real-time user behavior data according to the time interval to which the user behavior data belongs; clean the real-time user behavior data according to the tag value corresponding to the offline tag, and put the cleaned real-time user behavior data in the database.
- the user label only indicates the time interval, and also constrains the label conditions. According to the label value of the offline label, it can be judged whether the corresponding label condition is met. Yuan, there is no need to obtain real-time behavior data. Through the above settings, the amount of data required for calculating and implementing labels is effectively reduced, and computing resources are saved.
- the process of placing the cleaned real-time user behavior data in the database also includes:
- the corresponding relationship between the user ID and real-time user behavior data is recorded in the query engine, which helps the user to quickly query the corresponding user if the user tag type is a real-time tag type when sending an acquisition request to the query engine Real-time behavioral data to further reduce response time for identifying user tags.
- Step S204 in response to the acquisition request for the user label, determine the user label type according to the time interval indicated in the acquisition request.
- user behavior data is divided into offline data and real-time data according to time intervals (such as data generated on the current day is real-time data, and data generated before the current day is offline data.
- time intervals such as data generated on the current day is real-time data, and data generated before the current day is offline data.
- the division is just an example
- the offline label is calculated for the offline data; for the real-time label, it needs to be determined by calculating the real-time data.
- the type of the user tag is determined according to the time interval indicated in the acquisition request, and then for different types of user tags, different methods are used to determine and send it to the requesting party.
- the above method further includes:
- the new user behavior data within the time interval is obtained, and the offline label is updated according to the new user behavior data.
- the generated offline label needs to be updated in time as time goes by.
- Step S205 if the user tag type is an offline tag type, then determine the first user tag from the database according to the user number and the time interval, and send the first user tag to the requesting party.
- the acquisition request indicates an offline label type
- the response time is significantly shortened Long, expands the applicable scenarios, and can be applied to meet high-concurrency query requirements.
- Step S206 if the user tag type includes offline tag type and real-time tag type, according to the time interval corresponding to the offline tag type, determine the first user tag corresponding to the user number from the database, and determine whether the first user tag meets the requirements indicated in the acquisition request label condition; if so, then send the first user label to the requesting party; if not, determine the real-time user behavior data corresponding to the user number in the time interval corresponding to the real-time label type, and the first offline data corresponding to the first user label, according to The real-time user behavior data and the first offline data determine the target user label, and send the target user label to the requesting party.
- the priority is to determine the tag value corresponding to the first user tag (the user tag calculated in advance) Whether the label conditions indicated in the acquisition request are met; if yes, just send the first user label to the requester; if not, you need to obtain real-time user behavior data again, and combine the data corresponding to the first user label to calculate the target User labeling not only meets the accuracy of user labeling, but also shortens the response time as much as possible, avoids the waste of computing resources, and improves the user experience.
- the user tag type determined according to the acquisition request is only the real-time tag type, it only needs to determine the real-time user behavior data corresponding to the user number in the time interval, and determine the second user tag according to the real-time user behavior data. , and send the second user tag to the requester.
- the above method further includes:
- the real-time user behavior data can be directly used to update the first user tag, further shortening the response time and saving computing resources.
- the user label type is determined according to the time interval indicated in the acquisition request; if the user label type is an offline label type, then according to the user number and the time interval from Determine the first user tag among the multiple offline tags in the database, and send the first user tag to the requester; if the user tag type is a real-time tag type, determine the real-time user behavior data corresponding to the user number in the time interval, according to the real-time user behavior The data determines the second user tag and sends the second user tag to the technical means of the requester, so it overcomes the existing methods of low computing efficiency, more waste of computing resources, long response time, and fewer applicable scenarios.
- Fig. 3 is a schematic diagram of main modules of a device for determining a user label provided according to an embodiment of the present disclosure; as shown in Fig. 3 , the device for determining a user label 300 provided by an embodiment of the present disclosure mainly includes:
- the label type determination module 301 is configured to determine the user label type according to the time interval indicated in the acquisition request in response to the acquisition request for the user label.
- user behavior data is divided into offline data and real-time data according to time intervals (such as data generated on the current day is real-time data, and data generated before the current day is offline data.
- time intervals such as data generated on the current day is real-time data, and data generated before the current day is offline data.
- the division is just an example
- the offline label is calculated for the offline data; for the real-time label, it needs to be determined by calculating the real-time data.
- the type of the user tag is determined according to the time interval indicated in the acquisition request, and then for different types of user tags, different methods are used to determine and send it to the requesting party.
- Label determination module 302 if the user label type is an offline label type, it is used to determine the first user label from a plurality of offline labels in the database according to the user number and time interval, and send the first user label to the requesting party; if the user label The type is a real-time tag type, which is used to determine the real-time user behavior data corresponding to the user number in the time interval, determine the second user tag according to the real-time user behavior data, and send the second user tag to the requester.
- the user label type is an offline label type, it is used to determine the first user label from a plurality of offline labels in the database according to the user number and time interval, and send the first user label to the requesting party; if the user label The type is a real-time tag type, which is used to determine the real-time user behavior data corresponding to the user number in the time interval, determine the second user tag according to the real-time user behavior data, and send the second user tag to the requester.
- the acquisition request indicates an offline label type
- the response time is significantly shortened, and the applicable Scenarios, it can be applied to meet high-concurrency query requirements.
- the user tag type is represented as a real-time tag type, only the time interval corresponding to the real-time tag type is indicated in the current acquisition request. Therefore, the amount of real-time user behavior data corresponding to this part of the time interval will not be very large.
- real-time calculation can be performed to quickly determine the user label (that is, the first Two user tags), and send the corresponding user tags to the requester, while responding quickly, it can also be applied to high-concurrency user tag acquisition requirements.
- the acquisition request indicates an offline label type
- the device 300 for determining a user label further includes an offline label generation module, configured to:
- the label value is calculated, and offline labels corresponding to different user numbers are generated according to the label value and label conditions.
- offline tags are directly generated for offline data, which helps to shorten the response time and meet the high-concurrency query requirements.
- offline tags may also be calculated in advance for offline data of different service types according to service requirements, so as to avoid waste of computing resources.
- the above-mentioned off-line label generation module is also used for:
- the new user behavior data within the time interval is obtained, and the offline label is updated according to the new user behavior data.
- the generated offline label needs to be updated in time as time goes by.
- the above label determination module 302 further includes:
- the real-time user behavior data is cleaned according to the tag value corresponding to the offline tag, and the cleaned real-time user behavior data is placed in the database.
- the user label only indicates the time interval, and also constrains the label conditions. According to the label value of the offline label, it can be judged whether the corresponding label condition is met. Yuan, there is no need to obtain real-time behavior data. Through the above settings, the amount of data required for calculating and implementing labels is effectively reduced, and computing resources are saved.
- the above-mentioned device 300 for determining a user label further includes a recording module, configured to:
- the corresponding relationship between user numbers and real-time user behavior data is recorded in the query engine, which helps users to quickly query the corresponding user real-time tags when they send acquisition requests to the query engine. Behavioral data to further reduce response times for determining user tags.
- the tag determination module 302 is further configured to: if the user tag types include offline tag types and real-time tag types:
- the time interval corresponding to the offline label type determine the first user label corresponding to the user number from the database, and judge whether the first user label satisfies the label condition indicated in the acquisition request;
- determine the real-time user behavior data corresponding to the user number in the time interval corresponding to the real-time tag type, and the first offline data corresponding to the first user tag determine the target user tag according to the real-time user behavior data and the first offline data, and The target user tag is sent to the requester.
- the priority is to determine the tag value corresponding to the first user tag (the user tag calculated in advance) Whether the label conditions indicated in the acquisition request are met; if yes, just send the first user label to the requester; if not, you need to obtain real-time user behavior data again, and combine the data corresponding to the first user label to calculate the target User labeling not only meets the accuracy of user labeling, but also shortens the response time as much as possible, avoids the waste of computing resources, and improves the user experience.
- the tag determination module 302 is further configured to: if the first user tag does not meet the tag condition indicated in the acquisition request:
- the real-time user behavior data can be directly used to update the first user tag, further shortening the response time and saving computing resources.
- the user label type is determined according to the time interval indicated in the acquisition request; if the user label type is an offline label type, then according to the user number and the time interval from Determine the first user tag among the multiple offline tags in the database, and send the first user tag to the requester; if the user tag type is a real-time tag type, determine the real-time user behavior data corresponding to the user number in the time interval, according to the real-time user behavior The data determines the second user tag and sends the second user tag to the technical means of the requester, so it overcomes the existing methods of low computing efficiency, more waste of computing resources, long response time, and fewer applicable scenarios.
- FIG. 4 shows an exemplary system architecture 400 to which the method for determining a user label or the device for determining a user label in an embodiment of the present disclosure can be applied.
- the system architecture 400 may include terminal devices 401, 402, 403, a network 404 and a server 405 (this architecture is only an example, and the components contained in the specific architecture can be adjusted according to the specific conditions of the application).
- the network 404 is used as a medium for providing communication links between the terminal devices 401 , 402 , 403 and the server 405 .
- Network 404 may include various connection types, such as wires, wireless communication links, or fiber optic cables, among others.
- Terminal devices 401 , 402 , 403 Users can use terminal devices 401 , 402 , 403 to interact with server 405 via network 404 to receive or send messages and the like.
- Various communication client applications can be installed on the terminal devices 401, 402, and 403, such as data processing applications, shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. ( example only).
- the terminal devices 401, 402, 403 may be various electronic devices with display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers and the like.
- the server 405 may be a server that provides various services, such as a server (just an example) for users to use terminal devices 401, 402, 403 (determining user tags/performing data processing).
- the server can analyze and process the received data such as the acquisition request, and feed back the processing results (for example, the first user label, the second user label—just an example) to the terminal device.
- the method for determining the user label provided by the embodiment of the present disclosure is generally executed by the server 405 , and correspondingly, the device for determining the user label is generally set in the server 405 .
- terminal devices, networks and servers in Fig. 4 are only illustrative. According to the implementation needs, there can be any number of terminal devices, networks and servers.
- FIG. 5 it shows a schematic structural diagram of a computer system 500 suitable for implementing a terminal device or a server according to an embodiment of the present disclosure.
- the terminal device or server shown in FIG. 5 is only an example, and should not limit the functions and application scope of the embodiments of the present disclosure.
- a computer system 500 includes a central processing unit (CPU) 501 that can be programmed according to a program stored in a read-only memory (ROM) 502 or a program loaded from a storage section 508 into a random-access memory (RAM) 503 Instead, various appropriate actions and processes are performed.
- ROM read-only memory
- RAM random-access memory
- various programs and data required for the operation of the system 500 are also stored.
- the CPU 501, ROM 502, and RAM 503 are connected to each other via a bus 504.
- An input/output (I/O) interface 505 is also connected to the bus 504 .
- the following components are connected to the I/O interface 505: an input section 506 including a keyboard, a mouse, etc.; an output section 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage section 508 including a hard disk, etc. and a communication section 509 including a network interface card such as a LAN card, a modem, or the like.
- the communication section 509 performs communication processing via a network such as the Internet.
- a drive 510 is also connected to the I/O interface 505 as needed.
- a removable medium 511 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is mounted on the drive 510 as necessary so that a computer program read therefrom is installed into the storage section 508 as necessary.
- the processes described above with reference to the flowcharts can be implemented as computer software programs.
- the disclosed embodiments of the present disclosure include a computer program product, which includes a computer program carried on a computer-readable medium, where the computer program includes program codes for executing the methods shown in the flowcharts.
- the computer program may be downloaded and installed from a network via communication portion 509 and/or installed from removable media 511 .
- this computer program is executed by a central processing unit (CPU) 501, the above-described functions defined in the system of the present disclosure are performed.
- CPU central processing unit
- the computer-readable medium shown in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two.
- a computer readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, electrical connections with one or more wires, portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
- a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.
- a computer-readable signal medium may include a data signal in baseband or propagated as part of a carrier wave carrying computer-readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
- a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.
- Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
- each block in a flowchart or block diagram may represent a module, program segment, or portion of code that includes one or more logical functions for implementing specified executable instructions.
- the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or they may sometimes be executed in the reverse order, depending upon the functionality involved.
- each block in the block diagrams or flowchart illustrations, and combinations of blocks in the block diagrams or flowchart illustrations can be implemented by a dedicated hardware-based system that performs the specified function or operation, or can be implemented by a A combination of dedicated hardware and computer instructions.
- the modules involved in the embodiments described in the present disclosure may be implemented by software or by hardware.
- the described modules may also be set in a processor, for example, it may be described as: a processor includes a label type determination module and a label determination module. Wherein, the names of these modules do not constitute a limitation on the unit itself under certain circumstances.
- the label type determination module can also be described as "used to respond to the acquisition request for the user label, according to the The time interval determines the module of the user tag type".
- the present disclosure also provides a computer-readable medium, which may be included in the device described in the above-mentioned embodiments, or may exist independently without being assembled into the device.
- the above-mentioned computer-readable medium carries one or more programs, and when the above-mentioned one or more programs are executed by the device, the device includes: in response to the acquisition request for the user tag, determine according to the time interval indicated in the acquisition request User tag type; if the user tag type is an offline tag type, then determine the first user tag from multiple offline tags in the database according to the user number and time interval, and send the first user tag to the requester; if the user tag type is The real-time label type determines the real-time user behavior data corresponding to the user number in the time interval, determines the second user label according to the real-time user behavior data, and sends the second user label to the requester.
- the user label type is determined according to the time interval indicated in the acquisition request; if the user label type is an offline label type, then according to the user number and the time interval from Determine the first user tag among the multiple offline tags in the database, and send the first user tag to the requester; if the user tag type is a real-time tag type, determine the real-time user behavior data corresponding to the user number in the time interval, according to the real-time user behavior The data determines the second user tag and sends the second user tag to the technical means of the requester, so it overcomes the existing methods of low computing efficiency, more waste of computing resources, long response time, and fewer applicable scenarios.
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
本公开公开了一种用户标签的确定方法和装置，涉及计算机技术领域。该方法的一具体实施方式包括：响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型；若用户标签类型为离线标签类型，则根据用户编号和时间区间从数据库的多个离线标签中确定第一用户标签，并将第一用户标签发送至请求方；若用户标签类型为实时标签类型，确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方。该实施方式提高了用户标签的计算效率，节约了计算资源，缩短了确定用户标签的响应时间，拓展了适用场景，能够满足高并发的查询请求。
Description
相关申请的交叉引用
本申请要求享有2021年6月10日提交的题为“一种用户标签的确定方法和装置”的中国专利申请No.202110649366.1的中国专利申请的优先权，在此全文引用上述中国专利申请公开的内容以作为本申请的一部分或全部。
本公开涉及计算机技术领域，尤其涉及一种用户标签的确定方法和装置。
随着互联网行业的不断发展，互联网平台的用户数量也急剧增加，平台针对用户进行个性化运营的诉求也越来越突出。因此，需要针对用户在一段时间内的行为确定用户标签，以便于进行相应的个性化推荐。
现有技术中至少存在如下问题：
现有方法通过实时计算确定用户标签的方法中，存在计算效率较低、计算资源浪费较多的技术问题；而通过响应查询确定用户标签的方法中，存在响应时间长、适用场景较少，难以满足高并发的查询需求的技术问题。
发明内容
有鉴于此，本公开实施例提供一种用户标签的确定方法和装，能够针对不同类型的用户标签查询请求，提供不同的查询方式，有效提高了用户标签的计算效率，节约了计算资源，缩短了确定用户标签的响应时间，拓展了适用场景，能够满足高并发的查询请求。
为实现上述目的，根据本公开实施例的第一方面，提供了一种用户标签的确定方法，包括：
响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型；
若用户标签类型为离线标签类型，则根据用户编号和时间区间从数据库的多个离线标签中确定第一用户标签，并将第一用户标签发送至请求方；
若用户标签类型为实时标签类型，确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方。
进一步地，离线标签的生成步骤包括：
获取多个用户编号对应的用户行为数据，根据用户行为数据所属的时间区间确定离线数据；
根据从离线数据中确定的不同用户编号在第一时间区间内对应的用户行为数据，计算标签值，并根据标签值和标签条件生成不同用户编号对应的离线标签。
进一步地，还包括：
确定生成离线标签的时刻与当前时刻之间的时间间隔；
若时间间隔大于或等于时长阈值，则获取时间间隔内的新增用户行为数据，根据新增用户行为数据对离线标签进行更新。
进一步地，还包括：
根据用户行为数据所属的时间区间确定实时用户行为数据；
根据离线标签对应的标签值对实时用户行为数据进行清洗处理，并将清洗处理后的实时用户行为数据置于数据库。
进一步地，还包括：
将用户编号以及实时用户行为数据的对应关系在查询引擎中进行 记录。
进一步地，还包括：若用户标签类型包括离线标签类型和实时标签类型，
根据离线标签类型对应的时间区间，从数据库中确定用户编号对应的第一用户标签，判断第一用户标签是否满足获取请求中指示的标签条件；
若是，则将第一用户标签发送至请求方；
若否，确定实时标签类型对应的时间区间内用户编号对应的实时用户行为数据，以及第一用户标签对应的第一离线数据，根据实时用户行为数据和第一离线数据确定目标用户标签，并将目标用户标签发送至请求方。
进一步地，还包括：若第一用户标签不满足获取请求中指示的标签条件，
确定实时标签类型对应的时间区间内，用户编号对应的实时用户行为数据，根据实时用户行为数据对第一用户标签进行更新，并将更新后的第一用户标签发送至请求方。
根据本公开实施例的第二方面，提供了一种用户标签的确定装置，包括：
标签类型确定模块，用于响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型；
标签确定模块，若用户标签类型为离线标签类型，用于根据用户编号和时间区间从数据库的多个离线标签中确定第一用户标签，并将第一用户标签发送至请求方；若用户标签类型为实时标签类型，用于确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方。
根据本公开实施例的第三方面，提供了一种电子设备，包括：
一个或多个处理器；
存储装置，用于存储一个或多个程序，
当一个或多个程序被一个或多个处理器执行，使得一个或多个处理器实现如上述任一种用户标签的确定方法。
根据本公开实施例的第四方面，提供了一种计算机可读介质，其上存储有计算机程序，该程序被处理器执行时实现如上述任一种用户标签的确定方法。
上述的非惯用的可选方式所具有的进一步效果将在下文中结合具体实施方式加以说明。
附图用于更好地理解本公开，不构成对本公开的不当限定。其中：
图1是根据本公开第一实施例提供的用户标签的确定方法的主要流程的示意图；
图2是根据本公开第二实施例提供的用户标签的确定方法的主要流程的示意图；
图3是根据本公开实施例提供的用户标签的确定装置的主要模块的示意图；
图4是本公开实施例可以应用于其中的示例性系统架构图；
图5是适于用来实现本公开实施例的终端设备或服务器的计算机系统的结构示意图。
以下结合附图对本公开的示范性实施例做出说明，其中包括本公开实施例的各种细节以助于理解，应当将它们认为仅仅是示范性的。因此，本领域普通技术人员应当认识到，可以对这里描述的实施例做出各种改变和修改，而不会背离本公开的范围和精神。同样，为了清楚和简明，以下的描述中省略了对公知功能和结构的描述。
图1是根据本公开第一实施例提供的用户标签的确定方法的主要流程的示意图；如图1所示，本公开实施例提供的用户标签的确定方法主要包括：
步骤S101，响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型。
具体地，根据本公开实施例，根据时间区间将用户行为数据划分为离线数据和实时数据(如当天产生的数据为实时数据，当天之前产生的数据为离线数据。需要说明的是上述时间区间的划分仅为示例)，针对离线数据计算得到离线标签；对于实时标签则需要利用实时数据计算来确定。通过上述设置，根据获取请求中指示的时间区间确定用户标签类型，进而针对不同类型的用户标签，采取不同的方式进行确定并将其发送至请求方。
步骤S102，若用户标签类型为离线标签类型，则根据用户编号和时间区间从数据库的多个离线标签中确定第一用户标签，并将第一用户标签发送至请求方。
根据本公开实施例，若获取请求指示的是离线标签类型，则只需根据获取请求对应的用户编号从数据库中确定相应的标签即可，通过上述设置，显著缩短了响应时间长，拓展了适用场景，可以适用满足高并发的查询需求。
具体地，根据本公开实施例，上述离线标签的生成步骤，包括：
获取多个用户编号对应的用户行为数据，根据用户行为数据所属的时间区间确定离线数据；
根据从离线数据中确定的不同用户编号在第一时间区间内对应的用户行为数据，计算标签值，并根据标签值和标签条件生成不同用户编号对应的离线标签。
通过上述设置，针对离线数据直接生成离线标签，有助于后续缩短响应时间，满足高并发的查询需求。根据本公开实施例的一具体实施方式，还可以根据业务需求，针对不同业务类型的离线数据提前计算离线标签，以避免计算资源的浪费。
进一步地，根据本公开实施例，上述方法还包括：
确定生成离线标签的时刻与当前时刻之间的时间间隔；
若时间间隔大于或等于时长阈值，则获取时间间隔内的新增用户行为数据，根据新增用户行为数据对离线标签进行更新。
由于用户标签内指示了相应的时间区间(如高净值用户，表示最近半年内累计消费额度超过5000元，数值仅为示例)，因此，所生成的离线标签随着时间的推移，需要及时更新，通过上述设置，提升了所生成的离线标签的实时性和准确率。
步骤S103，若用户标签类型为实时标签类型，确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方。
若用户标签类型表示为实时标签类型，则当前获取请求中仅仅指示了实时标签类型所对应的时间区间。因此，该部分时间区间对应的实时用户行为数据的数量不会很庞大，通过上述设置，根据用户编号以及相应的时间区间确定实时用户行为数据后，可进行实时计算，快速确定用户标签(即第二用户标签)，并将相应的用户标签发送至请求方，在快速响应的同时，也能适用于高并发的用户标签获取需求。
具体地，根据本公开实施例，上述方法还包括：
根据用户行为数据所属的时间区间确定实时用户行为数据；
根据离线标签对应的标签值对实时用户行为数据进行清洗处理， 并将清洗处理后的实时用户行为数据置于数据库。
用户标签仅仅指示了时间区间，还约束了标签条件，根据离线标签的标签值可以判断出是否满足响应的标签条件，(针对净值用户对应的标签，若标签值显示最近半年内累计消费额度超过5000元，则无需再获取实时行为数据。通过上述设置，有效减少了计算实施标签所需的数据量，节约了计算资源。
进一步地，根据本公开实施例，在将清洗处理后的实时用户行为数据置于数据库的过程中，还包括：
将用户编号以及实时用户行为数据的对应关系在查询引擎中进行记录。
通过上述设置，将用户编号以及实时用户行为数据的对应关系在查询引擎中进行记录，有助于用户向查询引擎发送获取请求时，若用户标签类型为实时标签，可以快速查询到相应的用户实时行为数据，进一步缩短确定用户标签的响应时间。
优选地，根据本公开实施例，还包括：若用户标签类型包括离线标签类型和实时标签类型，
根据离线标签类型对应的时间区间，从数据库中确定用户编号对应的第一用户标签，判断第一用户标签是否满足获取请求中指示的标签条件；
若是，则将第一用户标签发送至请求方；
若否，确定实时标签类型对应的时间区间内用户编号对应的实时用户行为数据，以及第一用户标签对应的第一离线数据，根据实时用户行为数据和第一离线数据确定目标用户标签，并将目标用户标签发送至请求方。
若用户发送的获取请求中指示的时间区间，不仅涵盖实时标签类 型对应的时间区间，还包括离线标签类型对应的时间区间，此时优先判断第一用户标签(提前计算好的用户标签)对应的标签值是否满足获取请求中指示的标签条件；若是，只需将该第一用户标签发送至请求方即可；若否，则需要再次获取实时用户行为数据，结合第一用户标签对应的数据来计算目标用户标签，即满足了用户标签的准确率，又尽量缩短了响应时间，避免了计算资源的浪费，提升了用户体验。
示例性地，根据本公开实施例，还包括：若第一用户标签不满足获取请求中指示的标签条件，
确定实时标签类型对应的时间区间内，用户编号对应的实时用户行为数据，根据实时用户行为数据对第一用户标签进行更新，并将更新后的第一用户标签发送至请求方。
进一步地，根据本公开实施例，可以直接利用实时用户行为数据对第一用户标签进行更新，进一步缩短响应时间，节约计算资源。
根据本公开实施例的技术方案，因为采用响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型；若用户标签类型为离线标签类型，则根据用户编号和时间区间从数据库的多个离线标签中确定第一用户标签，并将第一用户标签发送至请求方；若用户标签类型为实时标签类型，确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方的技术手段，所以克服了现有方法中存在的计算效率较低、计算资源浪费较多、响应时间长、适用场景较少，难以满足高并发的查询需求的技术问题，进而达到提高用户标签的计算效率，节约计算资源，缩短确定用户标签的响应时间，拓展适用场景，以及满足高并发的查询请求的技术效果。
图2是根据本公开第二实施例提供的用户标签的确定方法的主要流程的示意图；如图2所示，本公开实施例提供的用户标签的确定方 法主要包括：
步骤S201，获取多个用户编号对应的用户行为数据，根据用户行为数据所属的时间区间确定离线数据。
通过上述设置，针对离线数据直接生成离线标签，有助于后续缩短响应时间，满足高并发的查询需求。
步骤S202，根据从离线数据中确定的不同用户编号在第一时间区间内对应的用户行为数据，计算标签值，并根据标签值和标签条件生成不同用户编号对应的离线标签。
根据本公开实施例的一具体实施方式，还可以根据业务需求，针对不同业务类型的离线数据提前计算离线标签，以避免计算资源的浪费。
步骤S203，根据用户行为数据所属的时间区间确定实时用户行为数据；根据离线标签对应的标签值对实时用户行为数据进行清洗处理，并将清洗处理后的实时用户行为数据置于数据库。
用户标签仅仅指示了时间区间，还约束了标签条件，根据离线标签的标签值可以判断出是否满足响应的标签条件，(针对净值用户对应的标签，若标签值显示最近半年内累计消费额度超过5000元，则无需再获取实时行为数据。通过上述设置，有效减少了计算实施标签所需的数据量，节约了计算资源。
进一步地，根据本公开实施例，在将清洗处理后的实时用户行为数据置于数据库的过程中，还包括：
将用户编号以及实时用户行为数据的对应关系在查询引擎中进行记录。
通过上述设置，将用户编号以及实时用户行为数据的对应关系在查询引擎中进行记录，有助于用户向查询引擎发送获取请求时，若用户标签类型为实时标签类型，可以快速查询到相应的用户实时行为数据，进一步缩短确定用户标签的响应时间。
步骤S204，响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型。
具体地，根据本公开实施例，根据时间区间将用户行为数据划分为离线数据和实时数据(如当天产生的数据为实时数据，当天之前产生的数据为离线数据。需要说明的是上述时间区间的划分仅为示例)，针对离线数据计算得到离线标签；对于实时标签则需要利用实时数据计算来确定。通过上述设置，根据获取请求中指示的时间区间确定用户标签类型，进而针对不同类型的用户标签，采取不同的方式进行确定并将其发送至请求方。
进一步地，根据本公开实施例，上述方法还包括：
确定生成离线标签的时刻与当前时刻之间的时间间隔；
若时间间隔大于或等于时长阈值，则获取时间间隔内的新增用户行为数据，根据新增用户行为数据对离线标签进行更新。
由于用户标签内指示了相应的时间区间(如高净值用户，表示最近半年内累计消费额度超过5000元，数值仅为示例)，因此，所生成的离线标签随着时间的推移，需要及时更新，通过上述设置，提升了所生成的离线标签的实时性和准确率。
步骤S205，若用户标签类型为离线标签类型，则根据用户编号和时间区间从数据库中确定第一用户标签，并将第一用户标签发送至请求方。
根据本公开实施例，若获取请求指示的是离线标签类型，则只需根据获取请求对应的用户编号从数据库的多个离线标签中确定相应的标签即可，通过上述设置，显著缩短了响应时间长，拓展了适用场景，可以适用满足高并发的查询需求。
步骤S206，若用户标签类型包括离线标签类型和实时标签类型，根据离线标签类型对应的时间区间，从数据库中确定用户编号对应的第一用户标签，判断第一用户标签是否满足获取请求中指示的标签条件；若是，则将第一用户标签发送至请求方；若否，确定实时标签类型对应的时间区间内用户编号对应的实时用户行为数据，以及第一用户标签对应的第一离线数据，根据实时用户行为数据和第一离线数据确定目标用户标签，并将目标用户标签发送至请求方。
若用户发送的获取请求中指示的时间区间，不仅涵盖实时标签对应的时间区间，还包括离线标签对应的时间区间，此时优先判断第一用户标签(提前计算好的用户标签)对应的标签值是否满足获取请求中指示的标签条件；若是，只需将该第一用户标签发送至请求方即可；若否，则需要再次获取实时用户行为数据，结合第一用户标签对应的数据来计算目标用户标签，即满足了用户标签的准确率，又尽量缩短了响应时间，避免了计算资源的浪费，提升了用户体验。
具体地，根据本公开实施例，若根据获取请求确定的用户标签类型仅为实时标签类型，则只需确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方。
进一步地，根据本公开实施例，若第一用户标签不满足获取请求中指示的标签条件，上述方法还包括：
确定实时标签类型对应的时间区间内，用户编号对应的实时用户行为数据，根据实时用户行为数据对第一用户标签进行更新，并将更 新后的第一用户标签发送至请求方。
进一步地，根据本公开实施例，可以直接利用实时用户行为数据对第一用户标签进行更新，进一步缩短响应时间，节约计算资源。
根据本公开实施例的技术方案，因为采用响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型；若用户标签类型为离线标签类型，则根据用户编号和时间区间从数据库的多个离线标签中确定第一用户标签，并将第一用户标签发送至请求方；若用户标签类型为实时标签类型，确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方的技术手段，所以克服了现有方法中存在的计算效率较低、计算资源浪费较多、响应时间长、适用场景较少，难以满足高并发的查询需求的技术问题，进而达到提高用户标签的计算效率，节约计算资源，缩短确定用户标签的响应时间，拓展适用场景，以及满足高并发的查询请求的技术效果。
图3是根据本公开实施例提供的用户标签的确定装置的主要模块的示意图；如图3所示，本公开实施例提供的用户标签的确定装置300主要包括：
标签类型确定模块301，用于响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型。
具体地，根据本公开实施例，根据时间区间将用户行为数据划分为离线数据和实时数据(如当天产生的数据为实时数据，当天之前产生的数据为离线数据。需要说明的是上述时间区间的划分仅为示例)，针对离线数据计算得到离线标签；对于实时标签则需要利用实时数据计算来确定。通过上述设置，根据获取请求中指示的时间区间确定用户标签类型，进而针对不同类型的用户标签，采取不同的方式进行确定并将其发送至请求方。
标签确定模块302，若用户标签类型为离线标签类型，用于根据用户编号和时间区间从数据库的多个离线标签中确定第一用户标签，并将第一用户标签发送至请求方；若用户标签类型为实时标签类型，用于确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方。
根据本公开实施例，若获取请求指示的是离线标签类型，则只需根据获取请求对应的用户编号从数据库中确定相应的标签即可，通过上述设置，显著缩短了响应时间长，拓展了适用场景，可以适用满足高并发的查询需求。若用户标签类型表示为实时标签类型，则当前获取请求中仅仅指示了实时标签类型对应的时间区间。因此，该部分时间区间对应的实时用户行为数据的数量不会很庞大，通过上述设置，根据用户编号以及相应的时间区间确定实时用户行为数据后，可进行实时计算，快速确定用户标签(即第二用户标签)，并将相应的用户标签发送至请求方，在快速响应的同时，也能适用于高并发的用户标签获取需求。
根据本公开实施例，若获取请求指示的是离线标签类型，则只需根据获取请求对应的用户编号从数据库中确定相应的标签即可，通过上述设置，显著缩短了响应时间长，拓展了适用场景，可以适用满足高并发的查询需求。
具体地，根据本公开实施例，上述用户标签的确定装置300还包括离线标签的生成模块，用于：
获取多个用户编号对应的用户行为数据，根据用户行为数据所属的时间区间确定离线数据；
根据从离线数据中确定的不同用户编号在第一时间区间内对应的用户行为数据，计算标签值，并根据标签值和标签条件生成不同用户编号对应的离线标签。
通过上述设置，针对离线数据直接生成离线标签，有助于后续缩短响应时间，满足高并发的查询需求。根据本公开实施例的一具体实施方式，还可以根据业务需求，针对不同业务类型的离线数据提前计算离线标签，以避免计算资源的浪费。
进一步地，根据本公开实施例，上述离线标签的生成模块还用于：
确定生成离线标签的时刻与当前时刻之间的时间间隔；
若时间间隔大于或等于时长阈值，则获取时间间隔内的新增用户行为数据，根据新增用户行为数据对离线标签进行更新。
由于用户标签内指示了相应的时间区间(如高净值用户，表示最近半年内累计消费额度超过5000元，数值仅为示例)，因此，所生成的离线标签随着时间的推移，需要及时更新，通过上述设置，提升了所生成的离线标签的实时性和准确率。
具体地，根据本公开实施例，上述标签确定模块302还包括：
根据用户行为数据所属的时间区间确定实时用户行为数据；
根据离线标签对应的标签值对实时用户行为数据进行清洗处理，并将清洗处理后的实时用户行为数据置于数据库。
用户标签仅仅指示了时间区间，还约束了标签条件，根据离线标签的标签值可以判断出是否满足响应的标签条件，(针对净值用户对应的标签，若标签值显示最近半年内累计消费额度超过5000元，则无需再获取实时行为数据。通过上述设置，有效减少了计算实施标签所需的数据量，节约了计算资源。
进一步地，根据本公开实施例，上述用户标签的确定装置300还包括记录模块，用于：
将用户编号以及实时用户行为数据的对应关系在查询引擎中进行 记录。
通过上述设置，将用户编号以及实时用户行为数据的对应关系在查询引擎中进行记录，有助于用户向查询引擎发送获取请求时，若用户标签类型为实时标签，可以快速查询到相应的用户实时行为数据，进一步缩短确定用户标签的响应时间。
优选地，根据本公开实施例，标签确定模块302还用于：若用户标签类型包括离线标签类型和实时标签类型：
根据离线标签类型对应的时间区间，从数据库中确定用户编号对应的第一用户标签，判断第一用户标签是否满足获取请求中指示的标签条件；
若是，则将第一用户标签发送至请求方；
若否，确定实时标签类型对应的时间区间内用户编号对应的实时用户行为数据，以及第一用户标签对应的第一离线数据，根据实时用户行为数据和第一离线数据确定目标用户标签，并将目标用户标签发送至请求方。
若用户发送的获取请求中指示的时间区间，不仅涵盖实时标签对应的时间区间，还包括离线标签对应的时间区间，此时优先判断第一用户标签(提前计算好的用户标签)对应的标签值是否满足获取请求中指示的标签条件；若是，只需将该第一用户标签发送至请求方即可；若否，则需要再次获取实时用户行为数据，结合第一用户标签对应的数据来计算目标用户标签，即满足了用户标签的准确率，又尽量缩短了响应时间，避免了计算资源的浪费，提升了用户体验。
示例性地，根据本公开实施例，标签确定模块302还用于：若第一用户标签不满足获取请求中指示的标签条件：
确定实时标签类型对应的时间区间内，用户编号对应的实时用户行为数据，根据实时用户行为数据对第一用户标签进行更新，并将更 新后的第一用户标签发送至请求方。
进一步地，根据本公开实施例，可以直接利用实时用户行为数据对第一用户标签进行更新，进一步缩短响应时间，节约计算资源。
根据本公开实施例的技术方案，因为采用响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型；若用户标签类型为离线标签类型，则根据用户编号和时间区间从数据库的多个离线标签中确定第一用户标签，并将第一用户标签发送至请求方；若用户标签类型为实时标签类型，确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方的技术手段，所以克服了现有方法中存在的计算效率较低、计算资源浪费较多、响应时间长、适用场景较少，难以满足高并发的查询需求的技术问题，进而达到提高用户标签的计算效率，节约计算资源，缩短确定用户标签的响应时间，拓展适用场景，以及满足高并发的查询请求的技术效果。
图4示出了可以应用本公开实施例的用户标签的确定方法或用户标签的确定装置的示例性系统架构400。
如图4所示，系统架构400可以包括终端设备401、402、403，网络404和服务器405(此架构仅仅是示例，具体架构中包含的组件可以根据申请具体情况调整)。网络404用以在终端设备401、402、403和服务器405之间提供通信链路的介质。网络404可以包括各种连接类型，例如有线、无线通信链路或者光纤电缆等等。
用户可以使用终端设备401、402、403通过网络404与服务器405交互，以接收或发送消息等。终端设备401、402、403上可以安装有各种通讯客户端应用，例如数据处理类应用、购物类应用、网页浏览器应用、搜索类应用、即时通信工具、邮箱客户端、社交平台软件等 (仅为示例)。
终端设备401、402、403可以是具有显示屏并且支持网页浏览的各种电子设备，包括但不限于智能手机、平板电脑、膝上型便携计算机和台式计算机等等。
服务器405可以是提供各种服务的服务器，例如对用户利用终端设备401、402、403所(进行用户标签的确定/进行数据处理)的服务器(仅为示例)。该服务器可以对接收到的获取请求等数据进行分析等处理，并将处理结果(例如第一用户标签、第二用户标签--仅为示例)反馈给终端设备。
需要说明的是，本公开实施例所提供的用户标签的确定方法一般由服务器405执行，相应地，用户标签的确定装置一般设置于服务器405中。
应该理解，图4中的终端设备、网络和服务器的数目仅仅是示意性的。根据实现需要，可以具有任意数目的终端设备、网络和服务器。
下面参考图5，其示出了适于用来实现本公开实施例的终端设备或服务器的计算机系统500的结构示意图。图5示出的终端设备或服务器仅仅是一个示例，不应对本公开实施例的功能和使用范围带来任何限制。
如图5所示，计算机系统500包括中央处理单元(CPU)501，其可以根据存储在只读存储器(ROM)502中的程序或者从存储部分508加载到随机访问存储器(RAM)503中的程序而执行各种适当的动作和处理。在RAM 503中，还存储有系统500操作所需的各种程序和数据。CPU 501、ROM 502以及RAM 503通过总线504彼此相连。输入/输出(I/O)接口505也连接至总线504。
以下部件连接至I/O接口505：包括键盘、鼠标等的输入部分506；包括诸如阴极射线管(CRT)、液晶显示器(LCD)等以及扬声器等的输出部分507；包括硬盘等的存储部分508；以及包括诸如LAN卡、调制解调器等的网络接口卡的通信部分509。通信部分509经由诸如因特网的网络执行通信处理。驱动器510也根据需要连接至I/O接口505。可拆卸介质511，诸如磁盘、光盘、磁光盘、半导体存储器等等，根据需要安装在驱动器510上，以便于从其上读出的计算机程序根据需要被安装入存储部分508。
特别地，根据本公开公开的实施例，上文参考流程图描述的过程可以被实现为计算机软件程序。例如，本公开公开的实施例包括一种计算机程序产品，其包括承载在计算机可读介质上的计算机程序，该计算机程序包含用于执行流程图所示的方法的程序代码。在这样的实施例中，该计算机程序可以通过通信部分509从网络上被下载和安装，和/或从可拆卸介质511被安装。在该计算机程序被中央处理单元(CPU)501执行时，执行本公开的系统中限定的上述功能。
需要说明的是，本公开所示的计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质或者是上述两者的任意组合。计算机可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。在本公开中，计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。而在本公开中，计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信 号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、电线、光缆、RF等等，或者上述的任意合适的组合。
附图中的流程图和框图，图示了按照本公开各种实施例的系统、方法和计算机程序产品的可能实现的体系架构、功能和操作。在这点上，流程图或框图中的每个方框可以代表一个模块、程序段、或代码的一部分，上述模块、程序段、或代码的一部分包含一个或多个用于实现规定的逻辑功能的可执行指令。也应当注意，在有些作为替换的实现中，方框中所标注的功能也可以以不同于附图中所标注的顺序发生。例如，两个接连地表示的方框实际上可以基本并行地执行，它们有时也可以按相反的顺序执行，这依所涉及的功能而定。也要注意的是，框图或流程图中的每个方框、以及框图或流程图中的方框的组合，可以用执行规定的功能或操作的专用的基于硬件的系统来实现，或者可以用专用硬件与计算机指令的组合来实现。
描述于本公开实施例中所涉及到的模块可以通过软件的方式实现，也可以通过硬件的方式来实现。所描述的模块也可以设置在处理器中，例如，可以描述为：一种处理器包括标签类型确定模块和标签确定模块。其中，这些模块的名称在某种情况下并不构成对该单元本身的限定，例如，标签类型确定模块还可以被描述为“用于响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型的模块”。
作为另一方面，本公开还提供了一种计算机可读介质，该计算机可读介质可以是上述实施例中描述的设备中所包含的；也可以是单独 存在，而未装配入该设备中。上述计算机可读介质承载有一个或者多个程序，当上述一个或者多个程序被一个该设备执行时，使得该设备包括：响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型；若用户标签类型为离线标签类型，则根据用户编号和时间区间从数据库的多个离线标签中确定第一用户标签，并将第一用户标签发送至请求方；若用户标签类型为实时标签类型，确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方。
根据本公开实施例的技术方案，因为采用响应于针对用户标签的获取请求，根据获取请求中指示的时间区间确定用户标签类型；若用户标签类型为离线标签类型，则根据用户编号和时间区间从数据库的多个离线标签中确定第一用户标签，并将第一用户标签发送至请求方；若用户标签类型为实时标签类型，确定时间区间内用户编号对应的实时用户行为数据，根据实时用户行为数据确定第二用户标签，并将第二用户标签发送至请求方的技术手段，所以克服了现有方法中存在的计算效率较低、计算资源浪费较多、响应时间长、适用场景较少，难以满足高并发的查询需求的技术问题，进而达到提高用户标签的计算效率，节约计算资源，缩短确定用户标签的响应时间，拓展适用场景，以及满足高并发的查询请求的技术效果。
上述具体实施方式，并不构成对本公开保护范围的限制。本领域技术人员应该明白的是，取决于设计要求和其他因素，可以发生各种各样的修改、组合、子组合和替代。任何在本公开的精神和原则之内所作的修改、等同替换和改进等，均应包含在本公开保护范围之内。
Claims (10)
- 一种用户标签的确定方法，包括：响应于针对用户标签的获取请求，根据所述获取请求中指示的时间区间确定用户标签类型；若所述用户标签类型为离线标签类型，则根据用户编号和所述时间区间从数据库的多个离线标签中确定第一用户标签，并将所述第一用户标签发送至请求方；若所述用户标签类型为实时标签类型，确定所述时间区间内所述用户编号对应的实时用户行为数据，根据所述实时用户行为数据确定第二用户标签，并将所述第二用户标签发送至所述请求方。
- 根据权利要求1所述的用户标签的确定方法，其中，所述离线标签的生成步骤包括：获取多个用户编号对应的用户行为数据，根据所述用户行为数据所属的时间区间确定离线数据；根据从所述离线数据中确定的不同用户编号在第一时间区间内对应的用户行为数据，计算标签值，并根据所述标签值和标签条件生成不同用户编号对应的所述离线标签。
- 根据权利要求2所述的用户标签的确定方法，进一步包括：确定生成所述离线标签的时刻与当前时刻之间的时间间隔；若所述时间间隔大于或等于时长阈值，则获取所述时间间隔内的新增用户行为数据，根据所述新增用户行为数据对所述离线标签进行更新。
- 根据权利要求2所述的用户标签的确定方法，进一步包括：根据所述用户行为数据所属的时间区间确定实时用户行为数据；根据所述离线标签对应的标签值对所述实时用户行为数据进行清洗处理，并将清洗处理后的实时用户行为数据置于数据库。
- 根据权利要求4所述的用户标签的确定方法，进一步包括：将所述用户编号以及实时用户行为数据的对应关系在查询引擎中进行记录。
- 根据权利要求1所述的用户标签的确定方法，进一步包括：若所述用户标签类型包括离线标签类型和实时标签类型，根据所述离线标签类型对应的时间区间，从数据库中确定所述用户编号对应的第一用户标签，判断所述第一用户标签是否满足所述获取请求中指示的标签条件；若是，则将所述第一用户标签发送至所述请求方；若否，确定所述实时标签类型对应的时间区间内所述用户编号对应的实时用户行为数据，以及所述第一用户标签对应的第一离线数据，根据所述实时用户行为数据和所述第一离线数据确定目标用户标签，并将所述目标用户标签发送至所述请求方。
- 根据权利要求6所述的用户标签的确定方法，进一步包括：若所述第一用户标签不满足所述获取请求中指示的标签条件，确定所述实时标签类型对应的时间区间内，所述用户编号对应的实时用户行为数据，根据所述实时用户行为数据对所述第一用户标签进行更新，并将更新后的第一用户标签发送至请求方。
- 一种用户标签的确定装置，包括：标签类型确定模块，用于响应于针对用户标签的获取请求，根据所述获取请求中指示的时间区间确定用户标签类型；标签确定模块，若所述用户标签类型为离线标签类型，用于根据用户编号和所述时间区间从数据库的多个离线标签中确定第一用户标签，并将所述第一用户标签发送至请求方；若所述用户标签类型为实时标签类型，用于确定所述时间区间内所述用户编号对应的实时用户行为数据，根据所述实时用户行为数据确定第二用户标签，并将所述 第二用户标签发送至所述请求方。
- 一种电子设备，包括：一个或多个处理器；存储装置，用于存储一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-7中任一所述的方法。
- 一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现如权利要求1-7中任一所述的方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110649366.1 | 2021-06-10 | ||
| CN202110649366.1A CN113312553A (zh) | 2021-06-10 | 2021-06-10 | 一种用户标签的确定方法和装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2022257604A1 true WO2022257604A1 (zh) | 2022-12-15 |
Family
ID=77378111
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2022/087295 WO2022257604A1 (zh) | 2021-06-10 | 2022-04-18 | 一种用户标签的确定方法和装置 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113312553A (zh) |
| WO (1) | WO2022257604A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116456496A (zh) * | 2023-06-15 | 2023-07-18 | 阿里巴巴（中国）有限公司 | 资源调度的方法、存储介质及电子设备 |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113312553A (zh) * | 2021-06-10 | 2021-08-27 | 北京沃东天骏信息技术有限公司 | 一种用户标签的确定方法和装置 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180189791A1 (en) * | 2016-12-30 | 2018-07-05 | Qatar University Qstp-B | Methods and system for addressing locations with personalized and user-selected tags |
| CN110866040A (zh) * | 2018-08-27 | 2020-03-06 | 京东数字科技控股有限公司 | 用户画像生成方法、装置和系统 |
| CN111754268A (zh) * | 2020-06-29 | 2020-10-09 | 深圳市酷开软件技术有限公司 | 基于ott大数据的用户标签生成方法、管理系统及存储介质 |
| CN111881221A (zh) * | 2020-07-07 | 2020-11-03 | 上海中通吉网络技术有限公司 | 物流服务里客户画像的方法、装置和设备 |
| CN113312553A (zh) * | 2021-06-10 | 2021-08-27 | 北京沃东天骏信息技术有限公司 | 一种用户标签的确定方法和装置 |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104917733A (zh) * | 2014-03-13 | 2015-09-16 | 张永杰 | 一种时间区间的属性识别方法和系统 |
| CN112668969B (zh) * | 2020-12-25 | 2022-07-08 | 江苏满运物流信息有限公司 | 用户标签处理方法、系统、电子设备和存储介质 |
-
2021
- 2021-06-10 CN CN202110649366.1A patent/CN113312553A/zh active Pending
-
2022
- 2022-04-18 WO PCT/CN2022/087295 patent/WO2022257604A1/zh unknown
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180189791A1 (en) * | 2016-12-30 | 2018-07-05 | Qatar University Qstp-B | Methods and system for addressing locations with personalized and user-selected tags |
| CN110866040A (zh) * | 2018-08-27 | 2020-03-06 | 京东数字科技控股有限公司 | 用户画像生成方法、装置和系统 |
| CN111754268A (zh) * | 2020-06-29 | 2020-10-09 | 深圳市酷开软件技术有限公司 | 基于ott大数据的用户标签生成方法、管理系统及存储介质 |
| CN111881221A (zh) * | 2020-07-07 | 2020-11-03 | 上海中通吉网络技术有限公司 | 物流服务里客户画像的方法、装置和设备 |
| CN113312553A (zh) * | 2021-06-10 | 2021-08-27 | 北京沃东天骏信息技术有限公司 | 一种用户标签的确定方法和装置 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116456496A (zh) * | 2023-06-15 | 2023-07-18 | 阿里巴巴（中国）有限公司 | 资源调度的方法、存储介质及电子设备 |
| CN116456496B (zh) * | 2023-06-15 | 2023-11-14 | 阿里巴巴（中国）有限公司 | 资源调度的方法、存储介质及电子设备 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113312553A (zh) | 2021-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2022257604A1 (zh) | 一种用户标签的确定方法和装置 | |
| CN109298948B (zh) | 分布式计算方法和系统 | |
| CN110866040B (zh) | 用户画像生成方法、装置和系统 | |
| CN112527649A (zh) | 一种测试用例的生成方法和装置 | |
| CN110795315A (zh) | 监控业务的方法和装置 | |
| US11228537B2 (en) | Resource processing method and system, storage medium and electronic device | |
| CN108985805B (zh) | 一种选择性执行推送任务的方法和装置 | |
| CN113190558A (zh) | 一种数据加工方法和系统 | |
| CN110928594A (zh) | 服务开发方法和平台 | |
| CN110705271A (zh) | 一种提供自然语言处理服务的系统及方法 | |
| CN113282489B (zh) | 一种接口测试方法和装置 | |
| CN113760487B (zh) | 一种业务处理方法和装置 | |
| CN113641909A (zh) | 信息推送方法、装置、电子设备和计算机可读介质 | |
| CN113779945A (zh) | 一种文案生成方法和装置 | |
| CN113779018A (zh) | 一种数据处理方法和装置 | |
| CN113672671A (zh) | 一种实现数据加工的方法和装置 | |
| CN112015790A (zh) | 一种数据处理的方法和装置 | |
| CN113434754A (zh) | 确定推荐api服务的方法、装置、电子设备和存储介质 | |
| CN113535768A (zh) | 生产监控方法和装置 | |
| CN112862554A (zh) | 一种订单数据的处理方法和装置 | |
| CN111127077A (zh) | 一种基于流计算的推荐方法和装置 | |
| CN112749204A (zh) | 一种读取数据的方法和装置 | |
| CN113362097B (zh) | 一种用户确定方法和装置 | |
| CN110866002A (zh) | 分表数据处理的方法和装置 | |
| CN108881352B (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: 22819207 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |