CN108874403B - Method, device and equipment for issuing rule file and storage medium - Google Patents
Method, device and equipment for issuing rule file and storage medium Download PDFInfo
- Publication number
- CN108874403B CN108874403B CN201810536491.XA CN201810536491A CN108874403B CN 108874403 B CN108874403 B CN 108874403B CN 201810536491 A CN201810536491 A CN 201810536491A CN 108874403 B CN108874403 B CN 108874403B
- Authority
- CN
- China
- Prior art keywords
- rule file
- field
- target
- container
- snapshot
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention discloses a method, a device, equipment and a storage medium for issuing a rule file. The method comprises the following steps: acquiring a target rule file to be issued and a network address of at least one rule file container, wherein the rule file container is matched with an issuing environment; analyzing the target rule file, generating a target field snapshot corresponding to the target rule file, and pushing the target rule file to the rule file container according to the network address of the rule file container; triggering a field platform to update field information corresponding to the target rule file according to the target field snapshot; and triggering a container server corresponding to the rule file container to load the target rule file. By the method, the automatic release of the rule file and the automatic configuration of the corresponding field of the rule file can be realized, the labor cost is obviously reduced, and the release efficiency of the rule file is also improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a method, a device, equipment and a storage medium for issuing a rule file.
Background
In the internet financial industry, a wind control policy worker needs to analyze risks and develop corresponding countermeasures to form a rule file (hereinafter referred to as a policy package). After the strategy package is developed, the strategy package needs to be deployed online in time, and the deployment process has the characteristics of continuity, timeliness, rollback and the like.
At present, referring to fig. 1, after a wind control policy worker develops a policy package, the policy package and a corresponding field table are sent to a Git (distributed version control system) warehouse, and the developer is notified to perform deployment and online in an email manner. After receiving the notification, the research and development personnel firstly pull the field table from the Git warehouse, manually configure the newly added field for the deployment on the field platform, then deploy the strategy package in an engineering release form through a Pub code release system, and if the field needing to be offline exists on the field platform after the deployment, the research and development personnel also manually perform corresponding processing. Once the policy personnel or the service personnel find that the policy package deployed at this time has a problem, the policy personnel or the service personnel need to inform the research and development personnel to perform the rollback operation of the policy package. When the system resources are insufficient and the capacity needs to be expanded, operation and maintenance personnel are required to intervene to complete the relevant processing of the strategy package.
The above solution has obvious disadvantages: the strategy package deployment flow is too long, each link needs to be manually connected, so that the timeliness is poor, the error probability is high, seamless capacity expansion cannot be supported, and the online problem caused by omission of the strategy package by operation and maintenance personnel is easy to occur in the capacity expansion process.
Disclosure of Invention
The embodiment of the invention provides a method, a device, equipment and a storage medium for releasing a rule file, which are used for improving the releasing efficiency of the rule file and reducing the labor cost in the process of releasing the rule file.
In a first aspect, an embodiment of the present invention provides a method for issuing a rule file, including:
acquiring a target rule file to be issued and a network address of at least one rule file container, wherein the rule file container is matched with an issuing environment;
analyzing the target rule file, generating a target field snapshot corresponding to the target rule file, and pushing the target rule file to the rule file container according to the network address of the rule file container;
triggering a field platform to update field information corresponding to the target rule file according to the target field snapshot;
and triggering a container server corresponding to the rule file container to load the target rule file.
In a second aspect, an embodiment of the present invention further provides a device for issuing a rule file, where the device includes:
the file acquisition module is used for acquiring a target rule file to be issued and a network address of at least one rule file container, and the rule file container is matched with an issuing environment;
the file pushing module is used for analyzing the target rule file, generating a target field snapshot corresponding to the target rule file, and pushing the target rule file to the rule file container according to the network address of the rule file container;
the field updating module is used for triggering a field platform to update the field information corresponding to the target rule file according to the target field snapshot;
and the trigger loading module is used for triggering a container server side corresponding to the rule file container to load the target rule file.
In a third aspect, an embodiment of the present invention further provides an apparatus, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the method for issuing a rule file according to any embodiment of the present invention when executing the program.
In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the method for issuing a rule file according to any embodiment of the present invention.
The method, the device, the equipment and the storage medium for releasing the rule file, provided by the embodiment of the invention, can realize automatic release of the rule file and automatic configuration of the corresponding field of the rule file, and policy personnel can complete one-key release on a system for operating the method for releasing the rule file at any time after developing a new rule file, so that the communication with a research and development personnel mail is not needed and the release of the rule file is completed in a matching manner, the labor cost is obviously reduced, and the release efficiency of the rule file is also improved.
Drawings
FIG. 1 is a schematic flow chart diagram of a policy package deployment method in the prior art;
fig. 2 is a flowchart of a method for issuing a rule file according to a first embodiment of the present invention;
fig. 3 is a flowchart of a method for issuing a rule file according to a second embodiment of the present invention;
FIG. 4 is a flowchart of a method for rolling back a rule file according to a third embodiment of the present invention;
fig. 5 is a schematic structural diagram of a device for issuing a rule file according to a fifth embodiment of the present invention;
fig. 6 is a schematic hardware configuration diagram of an apparatus in the sixth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not to be construed as limiting the invention.
It should be further noted that, for the convenience of description, only some but not all of the relevant aspects of the present invention are shown in the drawings. Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently or simultaneously. In addition, the order of the operations may be re-arranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figure. The processes may correspond to methods, functions, procedures, subroutines, and the like.
Example one
Fig. 2 is a flowchart of a method for issuing a rule file according to an embodiment of the present invention, which is applicable to automatic deployment of the rule file and automatic configuration of field information corresponding to the rule file, and the method may be executed by an apparatus for issuing a rule file according to an embodiment of the present invention, where the apparatus may be implemented in software and/or hardware, and may be generally integrated in a processor.
As shown in fig. 2, the method of this embodiment specifically includes:
s210, acquiring a target rule file to be issued and a network address of at least one rule file container, wherein the rule file container is matched with an issuing environment.
The target rule file to be issued refers to a policy package which is newly developed by policy personnel and needs to be issued to the cloud, and specifically can be a business rule developed aiming at different business scenes and different crowds; the rule file container refers to a container corresponding to the deployment rule file in the cloud, and the network address of the rule file container refers to the IP address of the rule file container registered in the cloud registration center; the issuing environment refers to the operating environment of the rule file, and the cloud end is provided with rule file containers respectively matched with different issuing environments.
Specifically, the publishing environment may include: the system comprises a pre-publishing environment, a gray-scale publishing environment, an OA publishing environment and an online environment, wherein the pre-publishing environment refers to a testing environment before the rule file is online, the gray-scale publishing environment refers to a test operation environment which is only open to a small part of users, the OA publishing environment refers to an internal operation environment which is only open to internal workers, and the online publishing environment refers to a formal operation environment which is open to all users. The cloud end is provided with rule file containers corresponding to the issuing environments respectively so as to issue the target rule files in each issuing environment conveniently.
The overall release flow of the rule file is roughly as follows: exposing the IP address of the rule file container to a registration IP address of a registration center by a container server corresponding to the rule file container; the rule file issuing system acquires the IP address of the corresponding rule file container from the registry, wherein the rule file issuing system operates the issuing method of the rule file provided by the embodiment; based on the obtained IP address of the rule file container, the rule file issuing system automatically executes the operation of issuing the rule file to the rule file container; and after the container server corresponding to the rule file container finishes the loading of the corresponding rule file, returning a confirmation signal to the rule file issuing system. Thus, the operation of deploying the rule file in the set publishing environment is completed.
Specifically, as a specific implementation manner of this embodiment, the obtaining of the target rule file to be issued may specifically be:
acquiring a rule file to be tested, which is uploaded by policy personnel; testing the rule file to be tested according to the set testing rule, and determining the rule file to be tested which passes the test as a target rule file; and generating release version information corresponding to the target rule file, and adding the release version information into the target rule file.
Before the target rule file is issued, the target rule file needs to be tested and verified, and after the target rule file is confirmed to pass the test and verification, subsequent issuing operation can be carried out on the target rule file. Optionally, an upload button is set in the rule file publishing system for operating the method for publishing the rule file provided in this embodiment, after a policy worker develops a rule file, the policy worker clicks the upload button to upload the rule file, and the rule file is the rule file to be tested. And then, testing the rule file to be tested according to the set testing rule, specifically, matching the rule file to be tested with a pre-stored rule file sample, if the matching is successful, determining that the test is passed, or judging an output result output by the rule file to be tested and corresponding to the set input parameters, if the output result meets the preset rule, determining that the test is passed, and the like, taking the rule file to be tested which passes the test as a target rule file which can be published, and generating publishing version information for the target rule file.
Alternatively, the policy personnel may directly click and upload the target rule file that has passed the test, and only need to generate release version information for the target rule file.
In this embodiment, a concept of version management is introduced to the rule file, so as to implement version update of the corresponding rule file in different publishing environments, or implement version rollback of the corresponding rule file when a problem occurs in the currently running rule file.
S220, analyzing the target rule file, generating a target field snapshot corresponding to the target rule file, and pushing the target rule file to the rule file container according to the network address of the rule file container.
The target field snapshot stores field information corresponding to the target rule file, that is, field information that needs to be called when the container service corresponding to the rule file container runs the target rule file.
In the parsing process of the target rule file, the input, output and reason field codes of the target rule file may be parsed, where the reason field codes may specifically refer to interpretation information of some rules in the target rule file. If the unconfigured reason field code exists, the unconfigured reason field code needs to be configured according to the target rule file. And after all the reason field codes are determined to be configured, pushing the target rule file to the rule file container.
After the container service corresponding to the rule file container successfully receives the target rule file, a confirmation signal representing that the pushing is successful can be returned to the rule file issuing system, and then the rule file issuing system can display indication information of the pushing success in the status bar and provide the indication information to a policy staff executing the pushing operation.
And S230, according to the target field snapshot, triggering the field platform to update the field information corresponding to the target rule file.
And pushing the field information corresponding to the target rule file to a field platform according to the target field snapshot, triggering the field platform to load the field information to complete field information updating, and generating the field information corresponding to the target rule file, so that the container service can call the required field information in the field platform when running the target rule file.
And if the original rule file corresponding to the target rule file does not exist, triggering the field platform to newly build field information corresponding to the target rule file.
And S240, triggering a container server corresponding to the rule file container to load the target rule file.
Triggering the container server to load the target rule file, specifically sending an issuing instruction to the container server, so that the container server executes the operation of loading the target rule file, and the container server can run the target rule file after successful loading.
In the method for issuing a rule file provided in this embodiment, a field platform is triggered to update field information corresponding to a target rule file by pushing the target rule file to a matched rule file container, and a container server is triggered to load the target rule file, so that automatic issuing of the rule file is completed. In the whole issuing process of the rule file, only the policy personnel are required to finish the manual operation of uploading the target rule file to be issued or the rule file to be issued, and if no problem occurs, the intervention of research personnel is basically not required, so that the labor cost is obviously reduced, and the issuing efficiency of the rule file is also obviously improved.
It is worth pointing out that the processes of completing the release of the target rule file in various release environments are the same, wherein the policy personnel only needs to execute once to complete the operation of uploading the target rule file to be released or the rule file to be tested, the test of the rule file to be tested only needs to execute once, and then the target rule file is released to the rule file container corresponding to various release environments.
Specifically, push and release buttons may be respectively set for each release environment in the rule file release system, and after the test personnel sequentially click, the flow of the rule file release method may be executed.
On the basis of the above embodiments, after the container server successfully loads the target rule file, a confirmation signal for indicating successful loading or failed loading may be returned, so as to indicate that the target rule file is successfully or unsuccessfully issued. After the container server successfully loads the target rule file, if the user applies for access, the container server will run the target rule file.
If a confirmation signal which is returned by the container server and used for indicating successful loading is received, the operation of the target rule file can be verified, for example, the user ID and the order number are used for accessing the corresponding service, the feedback result of the container server is counted, the calling success frequency and the calling failure frequency are displayed, so that a policy worker can observe the operation state of the target rule file conveniently, and the target rule file is rolled back when the operation of the target rule file has problems.
Example two
Fig. 3 is a flowchart of a method for issuing a rule file according to a second embodiment of the present invention, which is embodied based on the second embodiment, and the triggering of the field platform to update the field information corresponding to the target rule file according to the target field snapshot specifically includes:
if the field platform is determined to store the field information of the original rule file associated with the target rule file, acquiring an original field snapshot corresponding to the original rule file;
comparing the target field snapshot with the original field snapshot to determine a newly added field and an abnormal error-reporting field;
and the field triggering platform configures the abnormal error reporting field, and adds a newly added field into the original field snapshot to obtain the to-be-corrected field snapshot corresponding to the target rule file.
After triggering a container server corresponding to the rule file container to load the target rule file, the method for issuing the rule file further comprises the following steps:
if receiving confirmation information of successfully loading the target rule file, which is sent by a container server corresponding to the rule file container, acquiring a to-be-corrected field snapshot corresponding to the target rule file, comparing the target field snapshot with the to-be-corrected field snapshot, and determining a deleted field and an abnormal error-reporting field;
and triggering the field platform to configure the abnormal error-reporting field, and deleting the deleted field in the to-be-corrected field snapshot to obtain a target field snapshot corresponding to the target rule file.
The method of this embodiment may be applicable to issuing a target rule file in various issuing environments, where the target rule file is a rule file that passes a test and has issuing version information, and the following takes an online issuing environment as an example, and a corresponding rule file container is a rule file container matched with the online issuing environment, and the method of this embodiment specifically includes:
s310, acquiring a target rule file to be issued and a network address of a rule file container matched with an issuing environment.
S320, analyzing the target rule file, judging whether an unconfigured reason code field exists, if so, executing S330, and if not, executing S340.
S330, configuring the unconfigured reason code field according to the target rule file, and executing S340.
S340, generating a target field snapshot corresponding to the target rule file, and pushing the target rule file to the rule file container according to the network address of the rule file container.
And S350, if the field platform is determined to store the field information of the original rule file associated with the target rule file, acquiring the original field snapshot corresponding to the original rule file, and comparing the target field snapshot with the original field snapshot.
If the target rule file is not the first version rule file for the set business scene and the set crowd, namely the container server runs the original rule file (the rule file of the previous version) corresponding to the target rule file, and the original rule file is the rule file of the online version, the field platform stores the field information corresponding to the original rule file, and further the original field snapshot and the target field snapshot can be compared to determine how the field information in the field platform is to be updated.
If the target rule file is the first version rule file aiming at the set service scene and the set crowd, the field platform can be directly triggered to load the target field snapshot, so that the container server can normally call the field information.
And S360, if the newly added field is determined to exist, the field platform is triggered to add the newly added field into the original field snapshot.
And if the newly added fields exist in the target field snapshot after comparison, pushing the newly added fields to the field platform to trigger the field platform to load the newly added fields.
And S370, if the abnormal error-reporting field is determined to exist, triggering the field platform to configure the abnormal error-reporting field so as to obtain the to-be-corrected field snapshot corresponding to the target rule file.
The abnormal error-reporting field may be specifically configured by configuring different attributes for the same field, for example, when a certain field cannot obtain a value, a default value is obtained according to the setting in the target field snapshot, and an error is reported according to the setting in the original field snapshot, so that a configuration conflict is generated, and then the field platform needs to be triggered to reconfigure the abnormal field, so as to obtain the default value and not report an error.
Configuration of the field information can be completed through S370 and S380, and a to-be-corrected field snapshot corresponding to the target rule file is generated on the field platform, wherein the to-be-corrected field snapshot is equivalent to a union of the original field snapshot and the target field snapshot, and may contain some field information only applicable to the original rule file.
And S380, triggering a container server corresponding to the rule file container to load the target rule file.
And S390, judging whether the container server successfully loads the target rule file, if not, executing S3100, and if so, executing S3110.
Whether the container server successfully loads the target rule file is judged specifically by whether a confirmation signal for indicating successful loading returned by the container server can be received, if so, the loading is considered to be successful, and if not, the loading is considered to be unsuccessful.
S3100, determining that the target rule file fails to be released.
And if the container server is judged to be unsuccessfully loaded with the target rule file, determining that the target file fails to be published. It should be noted that, in each of the above steps, there is a possibility of operation failure, for example, operation failure due to network interruption, and the operation failure in any one step may determine that the target rule file fails to be issued. If the network is restored, the above-mentioned flow can be restarted to execute, also can be continuously executed at breakpoint.
S3110, acquiring a to-be-corrected field snapshot corresponding to the target rule file, comparing the target field snapshot with the to-be-corrected field snapshot, and determining a deleted field and an abnormal error-reporting field.
After the container server is judged to have successfully loaded the target rule file, the to-be-corrected field snapshot in the field platform corresponding to the target rule file can be further corrected, so that the field snapshot in the field platform corresponding to the target rule file and the target field snapshot in the rule file release system are kept consistent.
And S3120, if the deleted field exists, triggering the field platform to delete the deleted field in the snapshot of the field to be corrected.
S3130, if the abnormal error-reporting field is determined to exist, triggering the field platform to configure the abnormal error-reporting field so as to obtain a target field snapshot corresponding to the target rule file.
Specifically, the field information only applicable to the original rule file can be deleted; and re-judging whether the abnormal error field exists or not, and if not, directly determining that the target file is successfully issued.
S3140, determining that the target rule file is successfully issued.
In the technical scheme, policy personnel can complete the deployment of the rule file at any time by one key, so that the automatic release of the rule file and the automatic configuration of the field information are realized. After receiving a confirmation signal of successful release returned by the container server, the configuration of the field information in the field platform is continuously triggered, so that the consistency of the field information in the rule file release system and the field platform can be further maintained.
EXAMPLE III
On the basis of the foregoing embodiments, the method for issuing a rule file further includes:
if the fact that the target rule file is operated by the container server side is determined to be in a problem and the rollback rule file associated with the target rule file exists, obtaining a rollback field snapshot of the rollback rule file of the latest version;
comparing the rollback field snapshot with the target field snapshot to determine a newly added field and an abnormal error reporting field;
the method comprises the steps that a field platform is triggered to configure abnormal error reporting fields, and newly added fields are added into target field snapshots to obtain rollback field snapshots to be corrected corresponding to rollback rule files of the latest version;
and controlling the container server to load the rollback rule file of the latest version.
Further, the method for issuing the rule file further includes:
if the confirmation information of the rollback rule file of the latest version which is successfully rolled back and sent by the container server side is received, comparing the rollback field snapshot to be corrected with the target field snapshot to determine a deleted field and an abnormal error reporting field;
and the field platform is triggered to configure the abnormal error reporting field, and the deleted field is deleted in the rollback field snapshot to be corrected so as to obtain the rollback field snapshot corresponding to the rollback rule file of the latest version.
The rollback rule file specifically refers to a rule file corresponding to a version that can be rolled back. For example, the container server normally runs the rule file of the version a currently, then the rule file issuing system issues a matched rule file of the version B, if the rule file of the version B is found to have a problem after commissioning, the rule file is rolled back to the rule file of the version a if rollback is required, and meanwhile, a rolled-back label is marked on the rule file of the version B, that is, the rule file of the version B is identified to be incapable of being rolled back, and then the rule file issuing system issues a matched rule file of the version C, so that the rolled-back rule file associated with the rule file of the version C is the rule file of the version a and is also the rolled-back rule file of the latest version.
Specifically, the service personnel and the policy personnel can observe online to find whether the target rule file operated by the container server has a problem, and can also determine whether rollback is required through the number of call success times and the number of call failure times counted on the rule file issuing system, when rollback operation needs to be performed on the target rule file, the policy personnel only need to send a rollback instruction, for example, a rollback button is arranged on the rule file issuing system to send the rollback instruction to indicate that the target rule file operated by the container server has a problem, and then the rule file issuing system executes the following rollback flow.
It is worth noting that if the target rule file is published only in the pre-publication environment and the gray scale publication environment, but not in the OA publication environment and the on-line publication environment, the rollback operation on the target rule file is only directed to the rule file container corresponding to the pre-publication environment and the gray scale publication environment, and is not directed to the rule file container corresponding to the pre-publication environment and the gray scale publication environment.
Fig. 4 is a flowchart of a method for rolling back a rule file according to a third embodiment of the present invention, and as shown in fig. 4, the method specifically includes:
s410, if it is determined that the target rule file operated by the container server has a problem and the rollback rule file associated with the target rule file exists, obtaining a rollback field snapshot of the rollback rule file of the latest version.
The target rule file is a rule file corresponding to the version running on the line, and the rollback rule file of the latest version is a rule file which can be rolled back and is closest to the release version information associated with the target rule file.
And S420, comparing the rollback field snapshot with the target field snapshot to determine the newly added field and the abnormal error-reporting field.
And S430, if the newly added field exists, the field platform is triggered to add the newly added field into the target field snapshot.
S440, if the abnormal error-reporting field exists, the field platform is triggered to configure the abnormal error-reporting field so as to obtain the rollback field snapshot to be corrected, which corresponds to the rollback rule file of the latest version.
For the detailed description of the foregoing embodiments, the description of triggering the field platform to complete the automatic configuration of the field information is omitted here.
And S450, controlling the container server to load the rollback rule file of the latest version.
Specifically, if the rule file container matched with the target rule file stores the rollback rule file of the latest version, a trigger loading instruction can be directly sent to the container server to control the container server to complete the loading operation of the rollback rule file of the latest version; if the rollback rule file of the latest version is not stored in the rule file container matched with the target rule file, the rollback rule file of the latest version needs to be pushed to the matched rule file container so as to control the container server to complete the loading operation of the rollback rule file of the latest version.
And S460, judging whether the container server successfully loads the rollback rule file of the latest version, if not, executing S470, and if so, executing S480.
Whether the container server successfully loads the rollback rule file of the latest version is judged specifically by whether a confirmation signal for indicating that rollback is successful, returned by the container server, can be received, and if not, the loading is considered to be successful, and if not, the loading is considered to be unsuccessful.
S470, determining that the target rule file fails to roll back.
And if the container server is judged not to successfully load the rollback rule file of the latest version, determining that the rollback of the target file fails. It should be further noted that, in each of the above steps, there is a possibility of operation failure, for example, operation failure due to network interruption, and operation failure in any one step may determine that the target rule file has a rollback failure. If the network is restored, the above-mentioned flow can be restarted to execute, also can be continuously executed at breakpoint.
S480, a rollback field snapshot to be corrected corresponding to the rollback rule file of the latest version is obtained, the target field snapshot is compared with the rollback field snapshot to be corrected, and the deleted field and the abnormal error reporting field are determined.
After the container server is judged to have successfully loaded the rollback rule file of the latest version, the to-be-modified rollback field snapshot in the field platform corresponding to the rollback rule file of the latest version may be further modified, so that the field snapshot in the field platform corresponding to the rollback rule file of the latest version and the rollback field snapshot in the rule file release system are kept consistent.
And S490, if the deleted field exists, triggering the field platform to delete the deleted field in the rollback field snapshot to be modified.
S4100, if the abnormal error-reporting field is determined to exist, triggering the field platform to configure the abnormal error-reporting field so as to obtain a rollback field snapshot corresponding to the rollback rule file of the latest version.
S4110, determining that the target rule file is rolled back successfully.
In the technical scheme, the policy personnel can complete the rollback operation of the rule file at any time by one key, so that the automatic rollback of the rule file and the automatic configuration of the field information are realized. After receiving a confirmation signal of successful rollback returned by the container server, the configuration of the field information in the field platform is continuously triggered, so that the consistency of the field information in the rule file issuing system and the field platform can be further maintained.
Example four
On the basis of the foregoing embodiments, the method for issuing a rule file further includes:
if the network address of the new rule file container matched with the set issuing environment is determined to be obtained, pushing all rule files in the current rule file container matched with the set issuing environment to the new rule file container according to the network address of the new rule file container;
and triggering a container server corresponding to the new rule file container to load all the rule files.
Under the condition that system resources are insufficient and expansion is needed, new rule file containers which are matched with the issuing environment respectively are added, and then the container server exposes the IP addresses of the new rule file containers to be registered in the registration center, so that the rule file issuing system can obtain the IP addresses of the new rule file containers matched with the set issuing environment, and all online versions of rule files can be pushed to the new rule file containers according to the IP addresses of the new rule file containers.
For example, expanding a new rule file container matching the online publishing environment, all rule files in the existing rule file container matching the online publishing environment need to be pushed to the new rule file container, and a container server corresponding to the new rule file container is triggered to load the rule files, so that the expansion operation is completed.
Further, before any rule file of an online version is pushed to the new rule file container according to the IP address of the new rule file container, field information corresponding to the rule file can be reconfigured, so that problems when a container server side calls the rule file are avoided; and after receiving a confirmation signal which is returned by the container server and used for indicating that the rule file is loaded successfully, the configuration of the field information in the field platform can be triggered again, so that the consistency of the rule file issuing system and the field information in the field platform is further maintained. For a detailed explanation of the field information configuration, please refer to the foregoing embodiments, which are not described herein.
If a capacity expansion confirmation signal which is returned by the container server and used for indicating that all the rule files are loaded successfully is received, the successful capacity expansion of the current time can be confirmed. If operation abnormity occurs in the middle of capacity expansion, for example, operation abnormity caused by network interruption, the capacity expansion breakpoint is recorded so as to continue capacity expansion operation from the capacity expansion breakpoint in network recovery.
In the technical scheme, whether a new rule file container is expanded or not is judged in a mode of refreshing the IP address of the rule file container, so that seamless expansion operation can be automatically executed, manual copying of the rule file is not needed, and the problem of call failure caused by manual missing operation is avoided.
EXAMPLE five
Fig. 5 is a schematic structural diagram of a rule file publishing device according to a fifth embodiment of the present invention, which is applicable to automatic deployment of a rule file and automatic configuration of field information corresponding to the rule file, and the device can be implemented in software and/or hardware and can be generally integrated in a processor. As shown in fig. 5, the apparatus for issuing a rule file specifically includes: a file acquisition module 510, a file push module 520, a field update module 530, and a trigger load module 540. Wherein the content of the first and second substances,
a file obtaining module 510, configured to obtain a target rule file to be published, and a network address of at least one rule file container, where the rule file container is matched with a publishing environment;
a file pushing module 520, configured to parse the target rule file, generate a target field snapshot corresponding to the target rule file, and push the target rule file to the rule file container according to the network address of the rule file container;
a field updating module 530, configured to trigger a field platform to update field information corresponding to the target rule file according to the target field snapshot;
and a triggering and loading module 540, configured to trigger a container server corresponding to the rule file container to load the target rule file.
The apparatus for issuing a rule file according to this embodiment completes automatic issuing of a rule file by pushing a target rule file to a matched rule file container, triggering a field platform to update field information corresponding to the target rule file, and triggering a container server to load the target rule file. In the whole issuing process of the rule file, only the policy personnel are required to finish the manual operation of uploading the target rule file to be issued or the rule file to be issued, and if no problem occurs, the intervention of research personnel is basically not required, so that the labor cost is obviously reduced, and the issuing efficiency of the rule file is also obviously improved.
Further, the field updating module 530 specifically includes: an original field snapshot acquiring unit, a field snapshot comparing unit and a field configuring unit, wherein,
an original field snapshot obtaining unit, configured to obtain an original field snapshot corresponding to the original rule file if it is determined that field information of the original rule file associated with the target rule file is stored in the field platform;
a field snapshot comparison unit, configured to compare the target field snapshot with the original field snapshot, and determine a newly added field and an abnormal error-reporting field;
and the field configuration unit is used for triggering the field platform to configure the abnormal error-reporting field, and adding the newly added field into the original field snapshot to obtain the to-be-corrected field snapshot corresponding to the target rule file.
Further, the apparatus for issuing the rule file further includes:
a field re-comparison module, configured to, after triggering a container server corresponding to the rule file container to load the target rule file, if receiving confirmation information that the target rule file is successfully loaded and sent by the container server corresponding to the rule file container, obtain a to-be-corrected field snapshot corresponding to the target rule file, compare the target field snapshot with the to-be-corrected field snapshot, and determine a deleted field and an abnormal error-reporting field;
and the field reconfiguration module is used for triggering the field platform to configure the abnormal error-reporting field and deleting the deleted field in the to-be-corrected field snapshot so as to obtain a target field snapshot corresponding to the target rule file.
Further, the file obtaining module 510 specifically includes: a rule file to be tested obtaining unit, a target rule file determining unit and a release version information generating unit, wherein,
the device comprises a to-be-tested rule file acquisition unit, a to-be-tested rule file acquisition unit and a to-be-tested rule file acquisition unit, wherein the to-be-tested rule file acquisition unit is used for acquiring a rule file to be tested, which is uploaded by policy personnel;
the target rule file determining unit is used for testing the rule file to be tested according to a set testing rule and determining the rule file to be tested which passes the test as the target rule file;
and the release version information generating unit is used for generating release version information corresponding to the target rule file and adding the release version information into the target rule file.
On the basis of the above technical solution, the apparatus for issuing a rule file further includes: a rollback field snapshot obtaining module, a rollback field comparison module, a rollback field configuration module and a rollback rule file loading module, wherein,
a rollback field snapshot obtaining module, configured to obtain a rollback field snapshot of a rollback rule file of a latest version if it is determined that the container server has a problem in running the target rule file and a rollback rule file associated with the target rule file exists;
the rollback field comparison module is used for comparing the rollback field snapshot with the target field snapshot and determining a newly added field and an abnormal error reporting field;
a rollback field configuration module, configured to trigger the field platform to configure the abnormal error-reporting field, and add the newly added field to the target field snapshot to obtain a rollback field snapshot to be corrected, which corresponds to the rollback rule file of the latest version;
and the rollback rule file loading module is used for controlling the container server to load the rollback rule file of the latest version.
Further, the apparatus for issuing the rule file further includes:
a rollback field re-comparison module, configured to, if receiving confirmation information that the container server successfully rolls back the latest version of the rollback rule file, compare the rollback field snapshot to be corrected, which corresponds to the latest version of the rollback rule file, with the target field snapshot, and determine a deleted field and an abnormal error-reporting field;
and the rollback field reconfiguration module is used for triggering the field platform to configure the abnormal error reporting field, and deleting the deleted field in the rollback field snapshot to be corrected so as to obtain the rollback field snapshot corresponding to the rollback rule file of the latest version.
On the basis of the above technical solution, the apparatus for issuing a rule file further includes:
the expansion pushing module is used for pushing all rule files in a current rule file container matched with a set issuing environment to the new rule file container according to the network address of the new rule file container if the network address of the new rule file container matched with the set issuing environment is determined to be acquired;
and the capacity expansion loading module is used for triggering a container server corresponding to the new rule file container to load all the rule files.
The device for issuing the rule file can execute the method for issuing the rule file provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method for issuing the rule file.
EXAMPLE six
Fig. 6 is a schematic diagram of a hardware structure of an apparatus according to a sixth embodiment of the present invention, and as shown in fig. 5, the apparatus includes:
one or more processors 610, one processor 610 being exemplified in fig. 6;
a memory 620;
the apparatus may further include: an input device 630 and an output device 640.
The processor 610, the memory 620, the input device 630 and the output device 640 of the apparatus may be connected by a bus or other means, and fig. 6 illustrates the example of connection by a bus.
The memory 620, as a non-transitory computer-readable storage medium, may be used to store software programs, computer-executable programs, and modules, such as program instructions/modules corresponding to a method for issuing a rule file in an embodiment of the present invention (for example, the file acquiring module 510, the file pushing module 520, the field updating module 530, and the trigger loading module 540 shown in fig. 5). The processor 610 executes various functional applications and data processing of the computer device by running software programs, instructions and modules stored in the memory 620, that is, implements a rule file distribution method of the above-described method embodiment.
The memory 620 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function; the storage data area may store data created according to use of the computer device, and the like. Further, the memory 620 may include high speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid state storage device. In some embodiments, the memory 620 may optionally include memory located remotely from the processor 610, which may be connected to the terminal device via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The input means 630 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the computer apparatus. The output device 640 may include a display device such as a display screen.
EXAMPLE seven
An embodiment of the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, perform a method for issuing a rule file, the method including:
acquiring a target rule file to be issued and a network address of at least one rule file container, wherein the rule file container is matched with an issuing environment;
analyzing the target rule file, generating a target field snapshot corresponding to the target rule file, and pushing the target rule file to the rule file container according to the network address of the rule file container;
triggering a field platform to update field information corresponding to the target rule file according to the target field snapshot;
and triggering a container server corresponding to the rule file container to load the target rule file.
Optionally, the computer-executable instruction, when executed by a computer processor, may be further configured to implement a technical solution of a method for issuing a rule file according to any embodiment of the present invention.
From the above description of the embodiments, it is obvious for those skilled in the art that the present invention can be implemented by software and necessary general hardware, and certainly, can also be implemented by hardware, but the former is a better embodiment in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which can be stored in a computer-readable storage medium, such as a floppy disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a FLASH Memory (FLASH), a hard disk or an optical disk of a computer, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device) to execute the methods according to the embodiments of the present invention.
It should be noted that, in the embodiment of the apparatus for issuing a rule file, each unit and each module included in the embodiment are only divided according to functional logic, but are not limited to the above division as long as the corresponding function can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present invention.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (8)
1. A method for issuing a rule file, comprising:
acquiring a target rule file to be issued and a network address of at least one rule file container, wherein the rule file container is matched with an issuing environment;
analyzing the target rule file, generating a target field snapshot corresponding to the target rule file, and pushing the target rule file to the rule file container according to the network address of the rule file container;
triggering a field platform to update field information corresponding to the target rule file according to the target field snapshot;
triggering a container server corresponding to the rule file container to load the target rule file;
wherein, the triggering a field platform to update the field information corresponding to the target rule file according to the target field snapshot includes:
if it is determined that the field platform stores the field information of the original rule file associated with the target rule file, acquiring an original field snapshot corresponding to the original rule file;
comparing the target field snapshot with the original field snapshot to determine newly added fields and abnormal error reporting fields;
triggering the field platform to configure the abnormal error-reporting field, and adding the newly added field into the original field snapshot to obtain a to-be-corrected field snapshot corresponding to the target rule file;
after triggering a container server corresponding to the rule file container to load the target rule file, the method further comprises:
if receiving confirmation information of successfully loading the target rule file, which is sent by a container server corresponding to the rule file container, acquiring a to-be-corrected field snapshot corresponding to the target rule file, comparing the target field snapshot with the to-be-corrected field snapshot, and determining a deleted field and an abnormal error-reporting field;
and triggering the field platform to configure the abnormal error-reporting field, and deleting the deleted field in the to-be-corrected field snapshot to obtain a target field snapshot corresponding to the target rule file.
2. The method of claim 1, wherein obtaining the target rule file to be published comprises:
acquiring a rule file to be tested, which is uploaded by policy personnel;
testing the rule file to be tested according to a set testing rule, and determining the rule file to be tested which passes the test as the target rule file;
and generating release version information corresponding to the target rule file, and adding the release version information into the target rule file.
3. The method of claim 2, further comprising:
if the fact that the target rule file is operated by the container server side is determined to be in a problem and a rollback rule file associated with the target rule file exists, obtaining a rollback field snapshot of the rollback rule file of the latest version;
comparing the rollback field snapshot with the target field snapshot to determine a newly added field and an abnormal error reporting field;
triggering the field platform to configure the abnormal error-reporting field, and adding the newly added field into the target field snapshot to obtain a rollback field snapshot to be corrected, which corresponds to the rollback rule file of the latest version;
and controlling the container server to load the rollback rule file of the latest version.
4. The method of claim 3, further comprising:
if confirmation information of successfully rolling back the rolling back rule file of the latest version sent by the container server side is received, comparing the rolling back field snapshot to be corrected corresponding to the rolling back rule file of the latest version with the target field snapshot, and determining a deleted field and an abnormal error reporting field;
and triggering the field platform to configure the abnormal error reporting field, and deleting the deleted field in the rollback field snapshot to be corrected to obtain the rollback field snapshot corresponding to the rollback rule file of the latest version.
5. The method of claim 1, further comprising:
if the network address of the new rule file container matched with the set issuing environment is determined to be obtained, pushing all rule files in the current rule file container matched with the set issuing environment to the new rule file container according to the network address of the new rule file container;
and triggering a container server corresponding to the new rule file container to load all the rule files.
6. An apparatus for issuing a rule file, comprising:
the file acquisition module is used for acquiring a target rule file to be issued and a network address of at least one rule file container, and the rule file container is matched with an issuing environment;
the file pushing module is used for analyzing the target rule file, generating a target field snapshot corresponding to the target rule file, and pushing the target rule file to the rule file container according to the network address of the rule file container;
the field updating module is used for triggering a field platform to update the field information corresponding to the target rule file according to the target field snapshot;
the trigger loading module is used for triggering a container server side corresponding to the rule file container to load the target rule file;
wherein the field updating module comprises:
an original field snapshot obtaining unit, configured to obtain an original field snapshot corresponding to the original rule file if it is determined that field information of the original rule file associated with the target rule file is stored in the field platform;
a field snapshot comparison unit, configured to compare the target field snapshot with the original field snapshot, and determine a newly added field and an abnormal error-reporting field;
a field configuration unit, configured to trigger the field platform to configure the abnormal error-reporting field, and add the newly added field to the original field snapshot to obtain a to-be-corrected field snapshot corresponding to the target rule file;
the apparatus for issuing the rule file further includes:
a field re-comparison module, configured to, after triggering a container server corresponding to the rule file container to load the target rule file, if receiving confirmation information that the target rule file is successfully loaded and sent by the container server corresponding to the rule file container, obtain a to-be-corrected field snapshot corresponding to the target rule file, compare the target field snapshot with the to-be-corrected field snapshot, and determine a deleted field and an abnormal error-reporting field;
and the field reconfiguration module is used for triggering the field platform to configure the abnormal error-reporting field and deleting the deleted field in the to-be-corrected field snapshot so as to obtain a target field snapshot corresponding to the target rule file.
7. An apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1-5 when executing the program.
8. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810536491.XA CN108874403B (en) | 2018-05-30 | 2018-05-30 | Method, device and equipment for issuing rule file and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810536491.XA CN108874403B (en) | 2018-05-30 | 2018-05-30 | Method, device and equipment for issuing rule file and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108874403A CN108874403A (en) | 2018-11-23 |
| CN108874403B true CN108874403B (en) | 2022-07-12 |
Family
ID=64335596
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810536491.XA Active CN108874403B (en) | 2018-05-30 | 2018-05-30 | Method, device and equipment for issuing rule file and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108874403B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110045964B (en) * | 2019-04-09 | 2022-10-28 | 厦门网宿有限公司 | Software gray level release method, proxy server, configuration center and system |
| CN111078263A (en) * | 2019-12-13 | 2020-04-28 | 深圳市随手科技有限公司 | Hot deployment method, system, server and storage medium based on Drools rule engine |
| CN111290768B (en) * | 2020-01-22 | 2023-10-20 | 北京百度网讯科技有限公司 | Updating method, device, equipment and medium of containerized application system |
| CN111382121B (en) * | 2020-03-04 | 2023-08-25 | 深圳乐信软件技术有限公司 | Information management system and storage medium |
| CN111897548B (en) * | 2020-07-24 | 2023-11-10 | 平安证券股份有限公司 | Front-end resource issuing method and device, electronic equipment and computer storage medium |
| CN112988661B (en) * | 2021-02-19 | 2024-03-19 | 金蝶软件（中国）有限公司 | Balance table updating method and related equipment thereof |
| CN113159740B (en) * | 2021-03-11 | 2024-05-17 | 深圳市分期乐网络科技有限公司 | Payment channel determination method and device, electronic equipment and storage medium |
| CN113205312A (en) * | 2021-05-13 | 2021-08-03 | 深圳供电局有限公司 | Power consumer profile management method and system, computer device and storage medium |
| CN113360454B (en) * | 2021-06-30 | 2024-03-01 | 广州虎牙科技有限公司 | Memory snapshot file compression and decompression method and related device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102073534A (en) * | 2011-02-24 | 2011-05-25 | 深圳市同洲电子股份有限公司 | Data analysis method and device |
| CN105373469A (en) * | 2014-08-25 | 2016-03-02 | 广东金赋信息科技有限公司 | Interface based software automation test method |
| CN106034054A (en) * | 2015-03-17 | 2016-10-19 | 阿里巴巴集团控股有限公司 | Redundant access control list ACL rule file detection method and apparatus thereof |
| CN106548288A (en) * | 2016-11-04 | 2017-03-29 | 环球大数据科技有限公司 | The polymorphic instance management system and method for many scenes of electric power |
| CN106571940A (en) * | 2015-10-08 | 2017-04-19 | ***通信集团广东有限公司 | Method and device of fusing network management data and resource data |
| CN107291779A (en) * | 2016-04-12 | 2017-10-24 | 百度在线网络技术（北京）有限公司 | Data cached management method and device |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8650320B1 (en) * | 1998-03-23 | 2014-02-11 | Software Ag | Integration server supporting multiple receiving channels |
| CN104166544A (en) * | 2014-07-24 | 2014-11-26 | 小米科技有限责任公司 | File merging method and device |
| CN105335657B (en) * | 2015-12-07 | 2019-04-05 | 珠海豹趣科技有限公司 | A kind of program bug detection method and device |
| US10237118B2 (en) * | 2016-11-18 | 2019-03-19 | Sap Se | Efficient application build/deployment for distributed container cloud platform |
| CN106777398A (en) * | 2017-03-02 | 2017-05-31 | 北京微影时代科技有限公司 | The generation method and device of a kind of csv file |
| CN107678756A (en) * | 2017-09-29 | 2018-02-09 | 千寻位置网络有限公司 | A kind of Web based on Docker applies a key dissemination method |
-
2018
- 2018-05-30 CN CN201810536491.XA patent/CN108874403B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102073534A (en) * | 2011-02-24 | 2011-05-25 | 深圳市同洲电子股份有限公司 | Data analysis method and device |
| CN105373469A (en) * | 2014-08-25 | 2016-03-02 | 广东金赋信息科技有限公司 | Interface based software automation test method |
| CN106034054A (en) * | 2015-03-17 | 2016-10-19 | 阿里巴巴集团控股有限公司 | Redundant access control list ACL rule file detection method and apparatus thereof |
| CN106571940A (en) * | 2015-10-08 | 2017-04-19 | ***通信集团广东有限公司 | Method and device of fusing network management data and resource data |
| CN107291779A (en) * | 2016-04-12 | 2017-10-24 | 百度在线网络技术（北京）有限公司 | Data cached management method and device |
| CN106548288A (en) * | 2016-11-04 | 2017-03-29 | 环球大数据科技有限公司 | The polymorphic instance management system and method for many scenes of electric power |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108874403A (en) | 2018-11-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108874403B (en) | Method, device and equipment for issuing rule file and storage medium | |
| CN108108297B (en) | Method and device for automatic testing | |
| US11016878B2 (en) | System and method for data collection and analysis of information relating to mobile applications | |
| US9672137B1 (en) | Shadow test replay service | |
| CN108804618B (en) | Database configuration method, device, computer equipment and storage medium | |
| CN107660289B (en) | Automatic network control | |
| CN112199355B (en) | Data migration method and device, electronic equipment and storage medium | |
| CN115454869A (en) | Interface automation test method, device, equipment and storage medium | |
| CN112256593B (en) | Program processing method and device, computer equipment and readable storage medium | |
| CN111831567B (en) | Application test environment configuration method, device, system and medium | |
| CN110795332A (en) | Automatic testing method and device | |
| CN113238935A (en) | Application testing method, system, device, medium, and computer program product | |
| CN112579330A (en) | Method, device and equipment for processing abnormal data of operating system | |
| CN111385613B (en) | Television system repairing method, storage medium and application server | |
| CN115269424A (en) | Automatic regression testing method, device, equipment and storage medium for production flow | |
| EP4204964A1 (en) | Candidate program release evaluation | |
| CN105630637A (en) | Software backup method, software backup terminal, software recovery method and software recovery terminal | |
| CN112328267A (en) | Multi-server installation method and device, terminal and storage medium | |
| CN113079059A (en) | Network state monitoring method and device, electronic equipment and readable storage medium | |
| CN113127027A (en) | Version updating method and device based on distributed version control system | |
| US11797388B1 (en) | Systems and methods for lossless network restoration and syncing | |
| CN115048244B (en) | Hardware repairing method, system, computer equipment and medium of server | |
| CN112383609B (en) | Processing method, device, equipment and storage medium for high concurrency data | |
| CN114363168A (en) | Method and device for modifying service configuration in container, electronic equipment and storage medium | |
| CN115469882A (en) | Software project management method and device, electronic equipment and storage medium |
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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230404 Address after: Floor 24, China energy storage building, 3099 Keyuan South Road, Yuehai street, Nanshan District, Shenzhen, Guangdong 518000 Patentee after: SHENZHEN LEXIN SOFTWARE TECHNOLOGY Co.,Ltd. Address before: 518000 23-27 / F, China energy storage building, 3099 Keyuan South Road, Yuehai street, Nanshan District, Shenzhen City, Guangdong Province Patentee before: SHENZHEN FENQILE NETWORK TECHNOLOGY Co.,Ltd. |