User tagging system, method, apparatus, and storage medium

Abstract

The application provides a user label system, method, device and storage medium, wherein the system comprises: a data source module configured to collect first user data of a vehicle, and perform standardization processing to obtain second user data meeting a preset standard; a label model module configured to process the second user data in a data warehouse by using natural language processing, determine the association relationship between each entity, obtain label data of the second user data based on the association relationship, and store the label data and the logical structure and physical structure associated with the label data; and a label management module configured to process the label data according to a business scenario, a logical structure and a physical structure of the label data, obtain user labels, and manage the user labels. The label data is labeled by using multiple user label generation modes, the diversification of user label generation is realized, the effective use of user data is improved, and precise marketing is realized by enterprises.

Description

Technical Field

[0001] This application relates to the field of user tag technology, specifically to a user tag system, method, device, and storage medium. Background Technology

[0002] With the rapid development of automotive intelligence and connectivity technologies, real-world vehicles offer users a wealth of in-cabin application systems. Users can enjoy in-cabin services such as music and movies through vehicle connectivity, providing a more convenient and comfortable experience. While enhancing the user experience, intelligent connected vehicles also provide automakers with a wealth of user data. Tagging this data to obtain user tags enables precise and rapid analysis of user preferences and consumption behaviors, allowing user data to guide automakers' user operations and digital marketing efforts. Therefore, how to better tag user data and utilize these tags has become a major research issue for various automakers.

[0003] In related technologies, user data tagging systems primarily employ stream processing to receive new data in real time, automatically analyze user tags within the new data, and update them accordingly. However, for automakers, all tags in this system are automatically derived from algorithmic analysis, making it impossible to flexibly create tags using methods such as Structured Query Language (SQL). This results in a lack of diversity in tag creation methods, and the tag management also lacks a complete system, failing to achieve closed-loop tag management. Summary of the Invention

[0004] In view of the shortcomings of the prior art described above, this application provides a user tagging system, method, device and storage medium to solve the technical problem that the user tagging system in the prior art cannot flexibly create tags, resulting in a lack of diversity in the tag creation methods.

[0005] Firstly, this application provides a user tagging system, the system comprising:

[0006] The data source module is used to collect first user data about vehicles, standardize the first user data to obtain second user data with preset standards, and store it in the data warehouse.

[0007] The tag model module is used to process the second user data in the data warehouse using natural language processing, determine the relationship between entities, obtain tag data of the second user data based on the relationship, and store the tag data and the logical and physical structures associated with the tag data accordingly. The tag data includes at least vehicle component actions, user behavior and user vehicle usage scenarios.

[0008] The tag management module is used to process the tag data according to the business scenario, logical structure and physical structure of the tag data to obtain user tags, and to manage the user tags.

[0009] In one embodiment of the present invention, the system further includes:

[0010] The tag service module is used to encapsulate the user tags, generate external service interfaces that provide the user tags to external applications, and receive and process call requests from the external applications; or / and

[0011] The tag application module is used to push the user tags so that the user tags can be applied.

[0012] In one embodiment of the present invention, the tag management module includes:

[0013] The management unit is used to manage the services of the user tagging system, the services including basic services, which include at least one of entity management, tag catalog, data configuration and model management;

[0014] The tag processing unit is used to process the tag data to obtain the user tag, and synchronize the user tag to the management unit and the tag lifecycle management unit for online management;

[0015] The tag lifecycle management unit is used to provide the user tags with tag list, tag query, tag task operation monitoring, tag rating, tag popularity assessment, tag ranking and tag application analysis services.

[0016] In one embodiment of the present invention, the management unit includes at least one of the following:

[0017] The entity management subunit is used to acquire entity information, create entities based on the entity information, and manage the entities.

[0018] The tag directory subunit is used to generate a tag directory based on the user tag type and provide a query service for the user tags;

[0019] The data configuration subunit is used to synchronize the second user data and input the second user data into the configuration table to obtain configuration data for use when generating rule tags.

[0020] The model management subunit is used to manage the data tags, which are then processed by the tag processing unit.

[0021] In one embodiment of the present invention, the user tags include atomic tags, model tags, rule tags, custom tags, SQL tags, algorithm tags, real-time tags, and combined tags:

[0022] The atomic tags are generated in the data warehouse and synchronized from the data warehouse to the tag processing unit for processing.

[0023] The model tags are generated in the model management subunit and are synchronized by the model management subunit to the tag processing unit for processing.

[0024] The rule tags and the custom tags are created and generated by business users according to the configuration rules, and are obtained by the tag processing unit.

[0025] The SQL tag is generated and processed in the tag processing unit and is used to supplement the rule tag;

[0026] The algorithmic tags are generated using a machine learning model on the algorithm platform and then synchronized to the tag processing unit for processing.

[0027] The real-time tags are generated by the streaming computing platform and then synchronized to the tag processing unit for processing.

[0028] The combined label is obtained by the label processing unit based on any combination of the atomic label, the model label, the rule label, the custom label, the SQL label, the algorithm label, and the real-time label.

[0029] In one embodiment of the present invention, the tag lifecycle management unit is further configured to:

[0030] Review rule tags and custom tags to obtain review results, including approval and rejection.

[0031] The approved rule tags and custom tags are put into and taken out of service. Putting a tag into service triggers the tag task to run, while taking a tag out of service stops the tag service from running.

[0032] Secondly, embodiments of this application provide a user tagging method, the method comprising:

[0033] Collect first user data about the vehicle, standardize the first user data to obtain second user data with preset standards, and store it in a data warehouse;

[0034] The second user data in the data warehouse is processed using natural language processing to determine the relationship between entities. Based on the relationship, the tag data of the second user data is obtained. The tag data and the logical and physical structures associated with the tag data are stored accordingly. The tag data includes at least vehicle component actions, user behavior and user vehicle usage scenarios.

[0035] Based on the business scenario, logical structure, and physical structure of the tag data, the tag data is processed to obtain user tags, and the user tags are managed.

[0036] Thirdly, this application provides a vehicle device in which the vehicle uses the user tagging method as described in the second aspect.

[0037] Fourthly, this application provides an electronic device, comprising:

[0038] One or more processors;

[0039] A storage device for storing one or more programs that, when executed by one or more processors, cause the electronic device to implement the user tagging method described in the second aspect.

[0040] Fifthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a computer's processor, causes the computer to perform the user tagging method described in the second aspect.

[0041] As described above, the user tagging system, method, device, and storage medium provided by the embodiments of the present invention have the following beneficial effects:

[0042] The first user data is standardized through the data source module, tag model module, and tag management module to obtain the second user data. Then, the relationships between entities in the second user data are determined to obtain tag data. The tag data is then tagged in various ways to obtain various user tags and manage them. By generating user tags in multiple ways, the tag data is tagged to achieve user tag diversification, improve the effective use of user data, and enable enterprises to achieve precision marketing.

[0043] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0044] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0045] Figure 1 This is a schematic diagram illustrating the implementation environment of a user tagging system as shown in an exemplary embodiment of this application;

[0046] Figure 2 This is a block diagram illustrating a user tagging system as shown in an exemplary embodiment of this application;

[0047] Figure 3 This is a block diagram illustrating a specific user tagging system as shown in an exemplary embodiment of this application;

[0048] Figure 4 This is a schematic diagram illustrating a user tagging system service architecture as an exemplary embodiment of this application;

[0049] Figure 5 This is a flowchart illustrating a user tagging method in an exemplary embodiment of this application;

[0050] Figure 6 This is a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of this application. Detailed Implementation

[0051] The embodiments of this application will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of this application from the content disclosed in this specification. This application can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of this application. It should be understood that the preferred embodiments are only for illustrating this application and are not intended to limit the scope of protection of this application.

[0052] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of this application. Therefore, the drawings only show the components related to this application and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.

[0053] In the following description, numerous details are explored to provide a more thorough explanation of embodiments of the present application. However, it will be apparent to those skilled in the art that embodiments of the present application may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring embodiments of the present application.

[0054] Tagging user data yields user tags that can accurately and quickly analyze user preferences and consumption behaviors, guiding automakers' user operations and digital marketing efforts. Currently, systems for user tagging primarily employ stream processing technology, receiving new data in real time, automatically analyzing it to obtain and update user tags. Because all user tags are automatically derived by algorithms, the system lacks flexibility in tag creation, resulting in a lack of diversity in tag creation methods. Furthermore, the management of user tags lacks a complete system, failing to achieve closed-loop management.

[0055] To address the aforementioned issues, this application provides a user tagging system. Please refer to [link to relevant documentation]. Figure 1 , Figure 1 This is a schematic diagram illustrating the implementation environment of a user tagging system as shown in an exemplary embodiment of this application. Figure 1 As shown, the implementation environment includes vehicle 101 and cloud 102, which are connected via a network. The specific connection method is not limited; for example, it can be connected via wireless networks such as 3G (third-generation mobile information technology), 4G (fourth-generation mobile information technology), and 5G (fifth-generation mobile information technology). During the human-vehicle-cloud interaction process, vehicle 101 and cloud 102 generate a large amount of user data. This user tagging system collects user data, processes it, and tags it in various ways to obtain user tags, thereby diversifying user tags, improving the effective utilization of user data, and enabling enterprises to achieve precise marketing.

[0056] Please continue reading Figure 1 The cloud 102 is hosted by a server, which can be an independent physical server, a server cluster or distributed device composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as big data and artificial intelligence platforms.

[0057] Please see Figure 2 , Figure 2This is a block diagram illustrating a user tagging system as shown in an exemplary embodiment of this application. The system can be applied to... Figure 1 The implementation environment shown is specifically executed by the association resolution module within that implementation environment. It should be understood that this system can also be applied to other exemplary implementation environments and executed by devices in other implementation environments; this embodiment does not limit the implementation environment used for the method. To solve the above problems, embodiments of this application propose a user tagging system, a user tagging method, a vehicle device, an electronic device, and a computer-readable storage medium, which will be described in detail below.

[0058] like Figure 2 As shown, in an exemplary embodiment, the user tagging system includes at least a data source module 201, a tag model module 202, and a tag management module 203, which are described in detail below:

[0059] The data source module 201 is used to collect first user data about vehicles, standardize the first user data to obtain second user data with preset standards, and store it in the data warehouse.

[0060] During the human-vehicle-cloud interaction process, a large amount of primary user data is generated on both the vehicle and cloud sides. This primary user data includes data such as vehicle signals, vehicle-side events, event files, human-machine interaction (HU / APP) data, and OTA (Over-the-Air Technology) data. After collecting the aforementioned primary user data, the data source module 201 performs standardization processing on the primary user data to obtain secondary user data with preset standards. This standardization processing standardizes the primary user data according to pre-set data formats and processing rules, and then stores the obtained secondary data in a data warehouse. It should be noted that the data warehouse is independent of the user tagging system; that is, the data source module 201 stores the obtained secondary user data in a data warehouse outside of the user tagging system.

[0061] The tag model module 202 is used to process the second user data in the data warehouse using natural language processing, determine the relationship between entities, obtain the tag data of the second user data based on the relationship, and store the tag data and the logical and physical structures associated with the tag data accordingly. The tag data includes at least vehicle component actions, user behavior and user vehicle usage scenarios.

[0062] The data warehouse comprises an Operational Data Store (ODS), Data Warehouse Details (DWD), Data Warehouse Service (DWS), Data Warehouse Topic (DWT), and Application Data Service (ADS). The data processing within each layer of the data warehouse utilizes mature existing technologies and will not be elaborated upon here. The tagging model module 302 processes the second user data in the data warehouse using Natural Language Processing (NLP) to determine the relationships between entities, i.e., the inherent connections between entities. Based on these relationships, it obtains tag data for the second user data. For example, NLP determines that the second user data contains entities 1, 2, and 3, as well as the relationships between entities 1, 2, and 3. Based on these relationships, the second user data is initially tagged to obtain tag data, thus initially dividing the second user data into various tag data categories. These data tags include tags for vehicle component actions, user behavior, and user vehicle usage scenarios. After obtaining the data tags, the tag model module 302 also needs to store the obtained data tags and the logical and physical structures associated with the tag data, that is, the field structure of the data tag itself and the relationship structure between the data tags.

[0063] The tag management module 203 is used to process tag data according to the business scenario, logical structure and physical structure of the tag data, obtain user tags, and manage user tags.

[0064] The tag management module 203 obtains tag data and the physical and logical structures associated with the tag data from the tag model module 202. It then processes the data tags based on the business scenario requirements and the logical and physical structures of the data tags. Specifically, it further tags the tag data according to the business scenario, logical structure, and physical structure to obtain user tags that can accurately locate user preferences, behaviors, habits, etc., and manages the user tags.

[0065] Specifically, user tags include atomic tags, model tags, rule tags, custom tags, SQL tags, algorithm tags, real-time tags, and combined tags. Atomic tags are generated in the data warehouse and synchronized to the tag processing unit for processing. Model tags are generated in the model management subunit and synchronized to the tag processing unit for processing. Rule tags and custom tags are created by business users according to configuration rules and processed by the tag processing unit. SQL tags are generated and processed in the tag processing unit to supplement rule tags. Algorithm tags are generated using machine learning models on the algorithm platform and synchronized to the tag processing unit for processing. Real-time tags are generated on the stream computing platform and synchronized to the tag processing unit for processing. Combined tags are generated by the tag processing unit based on any combination of atomic tags, model tags, rule tags, custom tags, SQL tags, algorithm tags, and real-time tags.

[0066] It should be noted that the generation of the various user tags mentioned above involves different units, platforms, and different generation methods. These tags are then uniformly processed by the tag processing unit. For example, based on the character type of the fields in the tag data, functions and operators are selected and configured into tags. Tag processing is completed online through rule-based online configuration by setting statistical periods, data filtering conditions, and aggregation functions. For instance, in the generation of SQL tags, various aggregation functions, multi-table joins, subqueries, and other operations are supported, as well as tag data display and querying, SQL editing canvas, and data tag preview. In the generation of algorithm tags, the algorithm platform uses machine learning models to store the calculated tags in a Hive Table. After processing by the tag processing unit, the tags are registered online using their Chinese and English names. In the generation of real-time tags, the stream computing platform calculates and generates tags from real-time behavioral data, and FlinkSQL consumes the real-time behavioral data and outputs it to Kafka. This diversification of user tag generation methods improves the effective utilization of user data.

[0067] In one embodiment, the tag management module 203 includes:

[0068] The management unit is used to manage the services of the user tagging system. The services include basic services, which include at least one of entity management, tag catalog, data configuration, and model management.

[0069] The tag processing unit is used to process tag data, obtain user tags, and synchronize user tags to the management unit and tag lifecycle management unit for online management;

[0070] The tag lifecycle management unit provides services such as tag listing, tag query, tag task operation monitoring, tag scoring, tag popularity assessment, tag ranking, and tag application analysis for user tags.

[0071] The tag management module 203 specifically includes a management unit, a tag processing unit, and a tag lifecycle management unit. The management unit manages the services of the user tag system, including basic services, which in turn include at least one of entity management, tag catalog, data configuration, and model management services. The tag processing unit processes tag data to obtain user tags and synchronizes them to the management unit, specifically to the tag catalog sub-unit for online management and to the tag lifecycle management unit for online management. The tag lifecycle management unit provides user tags with tag lists, tag queries, tag task monitoring, tag scoring, tag popularity assessment, tag ranking, and tag application analysis services.

[0072] It should be noted that the tag list service displays the Chinese and English names, tag types, online status, public status, and update time of various user tags. It also allows for editing, viewing details, adding, removing, and deleting user tags. The tag query service allows users to search for user tags based on entity name, tag type, Chinese tag name, English tag name, tag status, and update method. The task execution monitoring service monitors the running status, start time, and end time of user tag generation tasks. The tag rating service scores user tags based on their quality and frequency of application, with tag quality evaluated by accuracy, coverage, and stability. The tag popularity service assesses the popularity of user tags based on the number of users and the frequency of use. The tag ranking service ranks specific user tags, including rankings by usability, attention, and quality. The tag application analysis service analyzes user tag applications from the perspective of business systems, enabling them to better utilize user tags.

[0073] In one embodiment, the tag lifecycle management unit is further configured to:

[0074] Review rule tags and custom tags to obtain review results, including approval and rejection.

[0075] Approved rule tags and custom tags can be added or removed from the service. Adding a tag to the service triggers the tag task to run, while removing a tag from the service stops the tag service from running.

[0076] The tag lifecycle management unit also provides tag review and tag deactivation / activation services for rule tags and custom tags within user tags. Specifically, it reviews custom tags and rule tags created by business users, obtaining review results, including approval and rejection. Rejection indicates that the custom or rule tag does not meet specific tag requirements and cannot be deactivated / activated. For approved custom or rule tags, further deactivation / activation operations are performed. Tag activation triggers a tag generation task, while tag deactivation stops the tag task. It should be noted that among the various services provided by the tag lifecycle management unit, tag list, tag query, tag task monitoring, tag scoring, tag popularity assessment, tag ranking, and tag application analysis services are applicable to all types of user tags, while tag review and tag deactivation / activation services are only for custom and rule tags within user tags.

[0077] In one embodiment, the management unit includes at least one of the following: an entity management subunit, used to acquire entity information, create entities based on the entity information, and manage the entities; a tag directory subunit, used to generate a tag directory based on user tag types, providing query services for user tags; a data configuration subunit, used to synchronize second user data, input the second user data into a configuration table, obtain configuration data, and use it when generating rule tags; and a model management subunit, used to manage data tags, which are then processed by the tag processing unit. The entity management subunit, tag directory subunit, data configuration subunit, and model management subunit respectively perform entity management, tag directory, data configuration, and model management in the basic services.

[0078] In one embodiment, the system further includes:

[0079] The tag service module 204 is used to encapsulate user tags, generate external service interfaces for providing user tags to external applications, and receive and process call requests from external applications; or / and

[0080] The tag application module 205 is used to push user tags for application.

[0081] Please see Figure 3 , Figure 3This is a block diagram illustrating a specific user tagging system as shown in an exemplary embodiment of this application. As shown, in the user tagging system 200, in addition to the data source module 201, tag model module 202, and tag management module 203, it may also include a tag service module 204 and / or a tag application module 205. The tag service module 204 encapsulates user tags, generates external service interfaces for providing user tags to external applications, and receives and processes call requests from external applications. The tag application module 205 pushes user tags for application. It should be understood that the tag service module 204 provides user tags to external systems, while the tag application module 205 provides user tags to cloud-based or in-vehicle application systems. This allows internal application systems, such as intelligent recommendation systems and data analysis systems, that need to use user tags to combine their collected data with user tags for business modules such as user insights, precision marketing, or user profiling.

[0082] The user tagging system provided in the above embodiments obtains second user data by standardizing the first user data through a data source module, a tag model module, and a tag management module in sequence. It then determines the relationship between entities in the second user data to obtain tag data and performs tagging processing on the tag data in various ways to obtain various user tags and manage the user tags. By tagging each tag data through multiple user tag generation methods, it achieves the diversification of user tags, improves the effective utilization of user data, and enables enterprises to achieve precision marketing.

[0083] Please see Figure 4 , Figure 4 This is a schematic diagram illustrating a user tagging system service architecture, as shown in an exemplary embodiment of this application. Figure 4As shown, the user tagging system service architecture includes a data source module, a tag model module, a tag management module, a tag service module, and a tag application module. The data source module collects first-user data about vehicles, standardizes this data to obtain second-user data with preset standards, and stores it in a data warehouse. The tag model module uses natural language processing to process the second-user data in the ODS, DWD, DWS, and ADS layers of the data warehouse, determines the relationships between entities, obtains tag data based on these relationships, and stores the tag data along with its associated logical and physical structures. Tag data includes standardized vehicle signal data, component actions, user behavior, and user vehicle usage. The tag management module processes the tag data according to its business scenario, logical structure, and physical structure to obtain user tags and manage them. Specifically, it includes a management unit, a tag processing unit, and a tag lifecycle management unit. The management unit manages the services of the user tagging system, including basic services such as entity management, tag catalog, data configuration, and model management (at least one of these). The system comprises three sub-units: Entity Management, Tag Directory, Data Configuration, and Model Management. Specifically, the Entity Management sub-unit acquires entity information to create and manage entities; the Tag Directory sub-unit generates a tag directory based on user tag types, providing a query service for user tags; the Data Configuration sub-unit synchronizes second-user data and inputs it into a configuration table to obtain configuration data for use when generating rule tags; and the Model Management sub-unit manages data tags for the tag processing unit to process. The Tag Processing unit processes tag data to obtain user tags and synchronizes them to the Management Unit and Tag Lifecycle Management Unit for online management. User tags include atomic tags, model tags, rule tags, custom tags, SQL tags, algorithm tags, real-time tags, and combined tags. The Tag Lifecycle Management unit provides services such as tag listing, tag query, tag task monitoring, tag scoring, tag popularity assessment, tag ranking, tag application analysis, tag review, and tag registration / deactivation. The tag service module encapsulates user tags, creating a tag API. It generates external service interfaces for providing user tags to external applications, receives and processes call requests from these applications, and handles API authorization and calls. The tag application module pushes user tags for various applications, such as user insights, targeted marketing, and user sketching. It provides full lifecycle management from tag definition, generation, management, and application.

[0084] Please see Figure 5 , Figure 5 This is a flowchart illustrating a user tagging method in an exemplary embodiment of this application, as shown below. Figure 5 As shown, this embodiment provides a user tagging method, which includes at least steps S501 to S503:

[0085] Step S501: Collect first user data about the vehicle, standardize the first user data to obtain second user data with preset standards, and store it in the data warehouse;

[0086] Step S502: Use natural language processing to process the second user data in the data warehouse, determine the relationship between each entity, obtain the tag data of the second user data based on the relationship, and store the tag data and the logical and physical structures associated with the tag data accordingly. The tag data includes at least vehicle component actions, user behavior and user vehicle usage scenarios.

[0087] Step S503: Based on the business scenario, logical structure and physical structure of the tag data, process the tag data to obtain user tags and manage the user tags.

[0088] It should be noted that the user tagging method provided in the above embodiments and the user tagging system provided in the above embodiments belong to the same concept. The specific way of performing each step has been described in detail in the system embodiments, and will not be repeated here.

[0089] Embodiments of this application also provide a vehicle device that is applied to the user tagging method provided in the above embodiments.

[0090] Embodiments of this application also provide an electronic device, including:

[0091] One or more processors;

[0092] A storage device for storing one or more programs that, when executed by one or more processors, cause an electronic device to implement the user tagging method provided in the above embodiments.

[0093] Please see Figure 6 , Figure 6 This is a schematic diagram illustrating the structure of an electronic device suitable for implementing the embodiments of this application. It should be noted that... Figure 6 The electronic device 600 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0094] like Figure 6As shown, the electronic device 600 includes a Central Processing Unit (CPU) 601, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on a program stored in Read-Only Memory (ROM) 602 or a program loaded from Storage Section 608 into Random Access Memory (RAM) 603. The RAM 603 also stores various programs and data required for system operation. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An Input / Output (I / O) interface 605 is also connected to the bus 604.

[0095] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0096] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit (CPU) 601, it performs various functions defined in the system of this application.

[0097] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0098] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0099] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0100] Another aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a computer's processor, causes the computer to perform the user tagging method as described above. This computer-readable storage medium may be included in the electronic device described in the above embodiments, or it may exist independently and not assembled into the electronic device.

[0101] The above embodiments are merely illustrative of the principles and effects of this application and are not intended to limit this application. Any person skilled in the art can modify or alter the above embodiments without departing from the spirit and scope of this application. Therefore, all equivalent modifications or alterations made by those skilled in the art without departing from the spirit and technical concept disclosed in this application should still be covered by the claims of this application.

Claims

1. A user tagging system, characterized in that, The system includes: The data source module is used to collect first user data about vehicles, standardize the first user data to obtain second user data with preset standards, and store it in the data warehouse. The tag model module is used to process the second user data in the data warehouse using natural language processing, determine the relationship between entities, obtain tag data of the second user data based on the relationship, and store the tag data and the logical and physical structures associated with the tag data accordingly. The tag data includes at least vehicle component actions, user behavior and user vehicle usage scenarios. The tag management module is used to process the tag data according to the business scenario, logical structure and physical structure of the tag data to obtain user tags, and to manage the user tags. The tag management module includes: a management unit for managing the services of the user tag system, the services including basic services, at least one of which is entity management, tag catalog, data configuration, and model management; a tag processing unit for processing the tag data to obtain the user tags, and synchronizing the user tags to the management unit and the tag lifecycle management unit for online management; the tag lifecycle management unit for providing the user tags with tag list, tag query, tag task operation monitoring, tag scoring, tag popularity assessment, tag ranking, and tag application analysis services, and also for reviewing rule tags and custom tags, obtaining review results, the review results including approval and rejection, and for reviewing approved rule tags and custom tags, tag going online is used to trigger tag task operation, and tag going offline is used to stop tag service operation; The user tags include atomic tags, model tags, rule tags, custom tags, SQL tags, algorithm tags, real-time tags, and combined tags. Atomic tags are generated in the data warehouse and synchronized to the tag processing unit for processing. Model tags are generated in the model management subunit and synchronized to the tag processing unit for processing; the management unit includes at least the model management subunit. Rule tags and custom tags are created by business users according to configuration rules and processed by the tag processing unit. SQL tags are generated and processed in the tag processing unit to supplement rule tags. Algorithm tags are generated using machine learning models on the algorithm platform and synchronized to the tag processing unit for processing. Real-time tags are generated on the stream computing platform and synchronized to the tag processing unit for processing. Combined tags are obtained by the tag processing unit based on any combination of atomic tags, model tags, rule tags, custom tags, SQL tags, algorithm tags, and real-time tags. The tag service module is used to encapsulate the user tags, generate external service interfaces that provide the user tags to external applications, and receive and process call requests from the external applications; or / and The tag application module is used to push the user tags so that the user tags can be applied.

2. The user tagging system according to claim 1, characterized in that, The management unit includes at least one of the following: The entity management subunit is used to acquire entity information, create entities based on the entity information, and manage the entities. The tag directory subunit is used to generate a tag directory based on the user tag type and provide a query service for the user tags; The data configuration subunit is used to synchronize the second user data and input the second user data into the configuration table to obtain configuration data for use when generating rule tags. The model management subunit is used to manage the label data, which is then processed by the label processing unit.

3. A user tagging method, characterized in that, The method, applied to the user tagging system according to any one of claims 1 to 2, comprises: Collect first user data about the vehicle, standardize the first user data to obtain second user data with preset standards, and store it in a data warehouse; The second user data in the data warehouse is processed using natural language processing to determine the relationship between entities. Based on the relationship, the tag data of the second user data is obtained. The tag data and the logical and physical structures associated with the tag data are stored accordingly. The tag data includes at least vehicle component actions, user behavior and user vehicle usage scenarios. Based on the business scenario, logical structure, and physical structure of the tag data, the tag data is processed to obtain user tags, and the user tags are managed.

4. A vehicle device, characterized in that, The vehicle uses the user tagging method as described in claim 3.

5. An electronic device, characterized in that, The electronic device includes: One or more processors; A storage device for storing one or more programs that, when executed by one or more processors, cause the electronic device to implement the user tagging method as described in claim 3.

6. A computer-readable storage medium, characterized in that, It stores a computer program that, when executed by the computer's processor, causes the computer to perform the user tagging method of claim 3.

Images