CN115858491B - Method for realizing semi-automatic operation management of user based on user tag management center - Google Patents
Method for realizing semi-automatic operation management of user based on user tag management center Download PDFInfo
- Publication number
- CN115858491B CN115858491B CN202211509979.6A CN202211509979A CN115858491B CN 115858491 B CN115858491 B CN 115858491B CN 202211509979 A CN202211509979 A CN 202211509979A CN 115858491 B CN115858491 B CN 115858491B
- Authority
- CN
- China
- Prior art keywords
- center
- rule
- cleaning
- data
- user tag
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Selective Calling Equipment (AREA)
- Stored Programmes (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a method for realizing semi-automatic operation management of a user based on a user tag management center, which comprises the steps of creating a database table; setting up a data cleaning center and a user tag management center and registering in the set up micro-service registration center and configuration center; the user tag management center operates the database table; the operator inputs the rules and pushes the rules to the data cleaning center and modifies the state in real time; the gateway engineering obtains the data in the database table; the user tag management center receives the request forwarded by the gateway engineering and returns a result to the data cleaning center in a streaming mode; the application service is registered in a micro-service registration and configuration center, and is manually registered in a user tag management center; and the accessed application service is forwarded to a data cleaning center to acquire data after being checked through gateway engineering. The invention only needs to manually register the application to the user tag management center during initialization, and personnel code and other intervention are not needed in the follow-up process.
Description
Technical Field
The invention relates to the technical field of internet cloud systems, in particular to a method for realizing semi-automatic operation management of a user based on a user tag management center.
Background
In the case that the micro-servitization system application and the single application coexist, the application services need to be refined by acquiring user tag data, and no method capable of uniformly managing and compatible with the two services and realizing semi-automatic management of the applications exists in the prior art.
Disclosure of Invention
The invention aims to provide a method for realizing semi-automatic operation management of a user based on a user tag management center, which is used for solving the problem that the prior art can not uniformly manage and compatible micro-service system applications and single applications and realize semi-automatic management of the applications.
The invention solves the problems by the following technical proposal:
a method for realizing semi-automatic operation management of users based on a user tag management center comprises the following steps:
step S100, constructing a persistence database MYSQL, and creating a database table system_manager and a database table rule_manager, wherein the database table rule_manager is used for storing management rule configuration, and the database table system_manager is used for storing data related to business system registration;
step S200, a micro-service registration and configuration center is built, a data cleaning center is built, a user tag management center is built based on a SpringCloud distributed micro-service framework, and the user tag management center is used for manually registering and managing an operation rule configuration and accessed service system, and manually initializing input rules and access application information;
step S300, registering the user tag management center and the data cleaning center to a service registration center of a micro service registration and configuration center, and managing configuration files through the configuration center of the micro service registration and configuration center;
step S400, a functional module is developed in a user tag management center and is used for carrying out data addition, modification and deletion operations on a database table system_manager and a database table rule_manager; after the user tag management center inputs the rules and the approval passes, the operator actively pushes the rules and related information to the data cleaning center in an HTTP request mode to process data and modify the state corresponding to the current rule data in MYSQL to be 'sent', and meanwhile, the user tag management center actively inquires the data cleaning center to obtain a result, and the state is modified to be 'in cleaning' when the user tag management center actively inquires the data cleaning center for the first time that the feedback information is normal;
step S500, constructing a distributed gateway service based on a SpringCloudGateway framework, developing a global filter on gateway engineering to realize a Global Filter interface and an Ordered interface, and acquiring data in a database table system_manager and a database table rule_manager in MYSQL according to the value of a service system which is currently requested to be accessed; the method comprises the steps of pushing a user label management center, acquiring relevant configuration information of the user label management center from MYSQL after pushing, storing the relevant configuration information into a memory, filling the memory into a set uri, and forwarding load balancing and requests between services to the user label management center through gateway engineering; the user tag management center returns a result to the data cleaning center in a streaming mode through an asynchronous notification interface based on the development of HTTP mode communication;
step S600, after the user tag management center obtains a cleaning result through active inquiry or asynchronous callback notification, modifying the state in MySQL into 'cleaning completion', and simultaneously using break to terminate cyclic inquiry, returning a success field indicating that the notification is correctly received through an asynchronous interface, wherein the data cleaning center does not need to notify any more;
step S700, in order to acquire user tag data, an application service developed based on a distributed micro service mode is registered in a micro service registration and configuration center, and input information is input to a user tag management center for manual registration control, and a single application service only needs to input information to the user tag management center for manual registration control, wherein the input information is the information content of a core field in a system_manager table and a rule_manager table;
step S800, the accessed application service acquires the current user tag data and needs to pass the verification of gateway engineering, the fact that the current requested spring.application.name exists in the database is verified, the state is that the cleaning is finished, the current request time is considered to pass the verification within the time range of the rule starting and ending, and the current request time is forwarded to the corresponding data cleaning center to acquire the data according to the configuration information after the current request time passes the verification.
The core field of the database table system_manager comprises a business system and a label; the core fields of the database table rule_manager comprise a system_manager table primary key ID, a matching rule, a rule effective time start_time, a rule dead time end_time, a state status and a user classification type; the state is used for recording the state of the current rule and the tag, wherein the state status is classified as:
newly-built: label rule data of the new input system;
in the auditing: submitting the newly-built tag rule data to a state in the upper-level audit;
the auditing is as follows: finishing the auditing and passing the auditing;
checking and rejecting: the rule which needs to be readjusted can initiate the audit again;
transmitted: the user label is in the rule of passing the audit and is sent to the label result cleaning center to start the user label cleaning;
in the cleaning process: inquiring a cleaning result feedback of a label result cleaning center through a user label management center, and if the current rule is still in cleaning, putting the rule in a cleaning state;
and (3) cleaning: and (3) obtaining a state of returning the current rule to be cleaned by asynchronously calling back a notice or actively inquiring the label result through the label result cleaning center.
Compared with the prior art, the invention has the following advantages:
the invention builds the user tag management center and the gateway service to jointly manage the micro-service system application and the single application, only the accessed applications are manually registered in the user tag management center during initialization, and the subsequent intervention such as personnel code and the like is not needed. Compatible and unified management of the two services and semi-automatic management of the applications are achieved.
Drawings
FIG. 1 is a schematic block diagram of the present invention;
FIG. 2 is a flow chart of data entry and processing of a user tag management center according to the present invention;
fig. 3 is a flow chart of the access of the application service to the data acquisition in the present invention.
Detailed Description
The present invention will be described in further detail with reference to examples, but embodiments of the present invention are not limited thereto.
Examples:
referring to fig. 1, a method for implementing semi-automatic operation management of a user based on a user tag management center includes:
step S100, constructing a persistence database MYSQL, and creating a database table system_manager and a database table rule_manager, wherein the database table rule_manager is used for storing management rule configuration, and the database table system_manager is used for storing data related to business system registration;
the core fields of the system_manager are:
the service system, the value of which is used for uniquely identifying the current service system in the user tag management center, the value is in one-to-one correspondence with the service system, and if the value is the value of spring. Application. Name of the application based on the setting value of the distributed micro-service architecture and starts with lb:// head; if the service is independent service, setting a value as specific service address connection and starting with http;
and the label is used for identifying user classification, and a plurality of labels can be configured under one system. For example: the user tag may be an old person tag, a female tag, a male tag, a Sichuan province region tag, or the like.
The core fields of rule_manager are:
system_manager table primary key ID;
the matching rule is used for matching key information of the current tag of the data cleaning center, the key information and the tag label belong to a one-to-many relationship, the key information is recorded in a text mode, analysis can be any text format according to data characteristics, the key information and the tag label are agreed under a data cleaning center line, and unified management and control are carried out through input of a user tag management center. For example: regional labels of Sichuan province can request an IP section through an interface of log parameters to distinguish which region the requested television is in; the old people tag can be distinguished by the type duty ratio of listening to songs, the television class duty ratio and the like. The rule value contains information such as a corresponding keyword or the like extracted by analyzing the data core, or intelligent AI algorithm rule configuration is used for matching rule effective time start_time and rule dead time end_time, the rule effective time start_time can be used for automatically starting the current rule at fixed time, and the rule dead time end_time can be used for automatically ending the current rule data transmission at fixed time;
status for recording the status of the current rule and tag, the status is classified as:
newly-built: label rule data of the new input system;
in the auditing: submitting the newly-built tag rule data to a state in the upper-level audit;
the auditing is as follows: finishing the auditing and passing the auditing;
checking and rejecting: the rule which needs to be readjusted can initiate the audit again;
transmitted: the user label is in the rule of passing the audit and is sent to the label result cleaning center to start the user label cleaning;
in the cleaning process: inquiring a cleaning result feedback of a label result cleaning center through a user label management center, and if the current rule is in cleaning, putting the label result cleaning center in a cleaning state;
and (3) cleaning: the tag result is notified by an asynchronous callback of the tag result cleaning center or actively inquired to obtain a state of returning to the completion of cleaning of the current rule;
user classification type, two kinds of users exist in the accessed system users: device users and system users, so the service system acquisition labels can be processed in three categories: the unique identification number mac of the machine user equipment, the unique identification primary key of the user of each application access system of the system user, and the comprehensive user comprising the machine user and the system user.
Step S200, a micro-service registration and configuration center is built, a data cleaning center is built, a user tag management center is built based on a SpringCloud distributed micro-service framework, and the user tag management center is used for manually registering and managing an operation rule configuration and accessed service system, and manually initializing input rules and access application information;
step S300, registering the user tag management center and the data cleaning center to a service registration center of a micro service registration and configuration center, and managing configuration files through the configuration center of the micro service registration and configuration center;
step S400, a functional module is developed in a user tag management center and is used for carrying out data addition, modification and deletion operations on a database table system_manager and a database table rule_manager; after the rule is input by the user tag management center and the approval passes, the operator actively pushes the rule and related information to the data cleaning center in an HTTP request mode to process the data, as shown in fig. 2, after the pushing is finished, the state corresponding to the current rule data in MYSQL is modified to be 'sent', meanwhile, the cyclic query is executed, the cyclic query frequency is 10 seconds for one time, the Sleep (10) is used for reducing the service CPU pressure, the user tag management center actively queries the data cleaning center to obtain a result, and the first active query data cleaning center obtains feedback information normally and changes the state into a 'cleaning-in' state;
step S500, constructing a distributed gateway service based on a SpringCloudgateway framework, developing a global filter on gateway engineering to realize a Global Filter interface and an Ordered interface,
public class CustomFilter implements GlobalFilter,Ordered{
@Override
public Mono<Void>filter(ServerWebExchange exchange,GatewayFilterChain chain){
particular business implementation
Obtaining core rule data content in MYSQL database according to the system spring. Application. Name value of the current request access, namely system_manager table and rule_manager data
}
}；
The method comprises the steps of acquiring data in a database table system_manager and a database table rule_manager in MYSQL according to a value of a service system which is currently requested to be accessed; the method comprises the steps of obtaining relevant configuration information of a user tag management center from MYSQL after pushing, storing the relevant configuration information into a memory, filling the relevant configuration information into a url of a builder.routes (). Route ("application name", r- > r.uri ("xxx")), and forwarding load balancing and a request between services to the user tag management center through gateway engineering; the user tag management center returns a result to the data cleaning center in a streaming mode through an asynchronous notification interface based on the development of HTTP mode communication;
@PostMapping("/data/notice")
Public void hwMonthcountNotice(HttpServletRequest request,HttpServletResponse response){
the business logic code of the data cleaning center indicates that the notification is received correctly, and the data cleaning center does not send the notification any more
response.getOutputStream().print("success")；
response.getOutputStream().flush()；
}
Step S600, after the user tag management center obtains a cleaning result through active inquiry or asynchronous callback notification, modifying the state in MySQL into 'cleaning completion', and simultaneously using break to terminate cyclic inquiry, returning a success field indicating that the notification is correctly received through an asynchronous interface, wherein the data cleaning center does not need to notify any more;
step S700, in order to acquire user tag data, an application service developed based on a distributed micro service mode is registered in a micro service registration and configuration center, and input information is input to a user tag management center for manual registration control, and a single application service only needs to input information to the user tag management center for manual registration control, wherein the input information is the information content of a core field in a system_manager table and a rule_manager table;
in step S800, the accessed application service needs to pass the verification of gateway engineering to verify that the current requested spring. Application. Name exists in the database, the state is "cleaning complete", and the current request time is considered to pass the verification within the time range of rule start and end, and after passing the verification, the current request time is forwarded to the corresponding data cleaning center according to the configuration information to obtain data, as shown in fig. 3.
Although the invention has been described herein with reference to the above-described illustrative embodiments thereof, the above-described embodiments are merely preferred embodiments of the present invention, and the embodiments of the present invention are not limited by the above-described embodiments, it should be understood that numerous other modifications and embodiments can be devised by those skilled in the art that will fall within the scope and spirit of the principles of this disclosure.
Claims (2)
1. The method for realizing semi-automatic operation management of the user based on the user tag management center is characterized by comprising the following steps:
step S100, constructing a persistence database MYSQL, and creating a database table system_manager and a database table rule_manager, wherein the database table rule_manager is used for storing management rule configuration, and the database table system_manager is used for storing data related to business system registration;
step S200, a micro-service registration center and a configuration center are built, a data cleaning center is built, a user tag management center is built based on a SpringCloud distributed micro-service framework, and the user tag management center is used for manually registering and managing an operation rule configuration and accessed service system, and manually initializing input rules and access application information;
step S300, registering a user tag management center and a data cleaning center to a service registration center of a micro service registration center and a configuration center, and managing configuration files through the configuration centers of the micro service registration center and the configuration center;
step S400, a functional module is developed in a user tag management center and is used for carrying out data addition, modification and deletion operations on a database table system_manager and a database table rule_manager; after the user tag management center inputs the rules and the approval passes, the operator actively pushes the rules and related information to the data cleaning center in an HTTP request mode to process data and modify the state corresponding to the current rule data in MYSQL to be 'sent', and meanwhile, the user tag management center actively inquires the data cleaning center to obtain a result, and the state is modified to be 'in cleaning' when the user tag management center actively inquires the data cleaning center for the first time that the feedback information is normal;
step S500, constructing a distributed gateway service based on a SpringCloudGateway framework, developing a global filter on gateway engineering to realize a Global Filter interface and an Ordered interface, and acquiring data in a database table system_manager and a database table rule_manager in MYSQL according to the value of a service system which is currently requested to be accessed; the method comprises the steps of obtaining relevant configuration information of a user tag management center from MYSQL after pushing, storing the relevant configuration information into a memory, filling the memory into a set uri, and forwarding a load balancing request between services to the user tag management center through gateway engineering; the user tag management center returns a result to the data cleaning center in a streaming mode through an asynchronous notification interface based on the development of HTTP mode communication;
step S600, after the user tag management center obtains a cleaning result through active inquiry or asynchronous callback notification, modifying the state in MySQL into 'cleaning completion', and simultaneously using break to terminate cyclic inquiry, returning a success field indicating that the notification is correctly received through an asynchronous interface, wherein the data cleaning center does not need to notify any more;
step S700, in order to acquire user tag data, an application service developed based on a distributed micro service mode is registered to a micro service registration center and a configuration center, and input information to a user tag management center for manual registration control, and a single application service only needs to input information to the user tag management center for manual registration control, wherein the input information is the information content of a core field in a system_manager table and a rule_manager table;
step S800, the accessed application service acquires the current user tag data and needs to pass the verification of gateway engineering, the fact that the current requested spring.application.name exists in the database is verified, the state is that the cleaning is finished, the current request time is considered to pass the verification within the time range of the rule starting and ending, and the current request time is forwarded to the corresponding data cleaning center to acquire the data according to the configuration information after the current request time passes the verification.
2. The method for realizing semi-automatic operation management of users based on the user tag management center according to claim 1, wherein the core fields of the database table system_manager comprise a business system and a tag label; the core fields of the database table rule_manager comprise a system_manager table primary key ID, a matching rule, a rule effective time start_time, a rule dead time end_time, a state status and a user classification type; the state is used for recording the state of the current rule and the tag, wherein the state status is classified as:
newly-built: the state of label rule data of the new input system;
in the auditing: submitting the newly-built tag rule data to a state in the upper-level audit;
the auditing is as follows: checking the passing state;
checking and rejecting: the status of the rule that needs to be readjusted can initiate the audit again;
transmitted: the user label is in a state of passing the auditing rule and is sent to a label result cleaning center to prepare for starting user label cleaning;
in the cleaning process: inquiring a cleaning result feedback of a label result cleaning center through a user label management center, and if the current rule is still in cleaning, putting the rule in a cleaning state;
and (3) cleaning: and (3) obtaining a state of returning the current rule to be cleaned by asynchronously calling back a notice or actively inquiring the label result through the label result cleaning center.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211509979.6A CN115858491B (en) | 2022-11-29 | 2022-11-29 | Method for realizing semi-automatic operation management of user based on user tag management center |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211509979.6A CN115858491B (en) | 2022-11-29 | 2022-11-29 | Method for realizing semi-automatic operation management of user based on user tag management center |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115858491A CN115858491A (en) | 2023-03-28 |
| CN115858491B true CN115858491B (en) | 2023-07-28 |
Family
ID=85667644
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211509979.6A Active CN115858491B (en) | 2022-11-29 | 2022-11-29 | Method for realizing semi-automatic operation management of user based on user tag management center |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115858491B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109862051A (en) * | 2017-11-30 | 2019-06-07 | 亿阳信通股份有限公司 | The realization method and system of multi-tenant under a kind of micro services framework |
| CN112379653A (en) * | 2020-12-01 | 2021-02-19 | 国能信控互联技术有限公司 | Smart power plant management and control system based on micro-service architecture |
| CN113783929A (en) * | 2021-07-27 | 2021-12-10 | 武汉光庭信息技术股份有限公司 | Method for realizing Web front-end micro-service architecture and architecture thereof |
| CN114401098A (en) * | 2021-12-28 | 2022-04-26 | 智昌科技集团股份有限公司 | Application system and method for quickly constructing microservice |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8856246B2 (en) * | 2011-08-10 | 2014-10-07 | Clarizen Ltd. | System and method for project management system operation using electronic messaging |
| US10326650B2 (en) * | 2015-04-06 | 2019-06-18 | Illumio, Inc. | Enforcing rules for bound services in a distributed network management system that uses a label-based policy model |
| CN107895253A (en) * | 2017-10-25 | 2018-04-10 | 北京科东电力控制系统有限责任公司 | A kind of method that electricity transaction function carries out micro services transformation |
-
2022
- 2022-11-29 CN CN202211509979.6A patent/CN115858491B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109862051A (en) * | 2017-11-30 | 2019-06-07 | 亿阳信通股份有限公司 | The realization method and system of multi-tenant under a kind of micro services framework |
| CN112379653A (en) * | 2020-12-01 | 2021-02-19 | 国能信控互联技术有限公司 | Smart power plant management and control system based on micro-service architecture |
| CN113783929A (en) * | 2021-07-27 | 2021-12-10 | 武汉光庭信息技术股份有限公司 | Method for realizing Web front-end micro-service architecture and architecture thereof |
| CN114401098A (en) * | 2021-12-28 | 2022-04-26 | 智昌科技集团股份有限公司 | Application system and method for quickly constructing microservice |
Non-Patent Citations (2)
| Title |
|---|
| 基于微服务化的智能电视足迹模块运营系统设计与开发;宋舰等;电视技术;第46卷(第04期);全文 * |
| 基于微服务的电子标签拣选系统设计与实现;程茂上;项前;余玉风;黄曦;吕志军;;制造业自动化(12);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115858491A (en) | 2023-03-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8086717B2 (en) | Presence information management system and presence information management server | |
| CN110708322A (en) | Method for realizing proxy service of industrial internet identification analysis system | |
| US6665674B1 (en) | Framework for open directory operation extensibility | |
| EP2106647B1 (en) | Web services and telecom network management unification | |
| JP2005518114A (en) | Presence tracking and namespace interconnect technology | |
| WO2012041388A1 (en) | Generation of a query plan for accessing a database | |
| US11726987B2 (en) | Normalizing user identification across disparate systems | |
| CN106230985B (en) | One kind is based on Internet of Things big data processing method, system and service processing end | |
| US20090125803A1 (en) | Method, system, client and server for managing xml document | |
| CN115858491B (en) | Method for realizing semi-automatic operation management of user based on user tag management center | |
| US20020188708A1 (en) | Network management method and apparatus | |
| JP2001256308A (en) | Method and system for exchanging care information | |
| CN109873720A (en) | A kind of cloud center intelligence O&M method and system based on enterprise's public platform | |
| US7779115B2 (en) | Method and apparatus for processing client capability information over a network | |
| CN101836405B (en) | For being issued in voip network system by sip terminal, inquiring about and the method for subscription information, sip terminal, sip application server, SIP information centre and voip network system | |
| EP1384174A2 (en) | System and method for world wide web based mapping of multiple system name spaces | |
| CN111045928A (en) | Interface data testing method, device, terminal and storage medium | |
| CN114172821A (en) | Service state synchronization method and device and server | |
| US20050076135A1 (en) | UDDI web service registry system based on an ebXML registry and management method therefor | |
| CN116095081A (en) | Event processing method and device based on block chain system, equipment and medium | |
| US7339907B2 (en) | System and method for the selection of electronic services from a set of resources using infrared communication | |
| JP5099239B2 (en) | Status information management system, status information management server, and status information management method | |
| US20070174077A1 (en) | Executing system and executing method of intelligent rule base service | |
| KR100748089B1 (en) | Method for providing individual information based on user data management open api | |
| KR100444825B1 (en) | Method on management of frame relay subscriber port in intergrated network |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |