CN106557307B - Service data processing method and system - Google Patents
Service data processing method and system Download PDFInfo
- Publication number
- CN106557307B CN106557307B CN201510632618.4A CN201510632618A CN106557307B CN 106557307 B CN106557307 B CN 106557307B CN 201510632618 A CN201510632618 A CN 201510632618A CN 106557307 B CN106557307 B CN 106557307B
- Authority
- CN
- China
- Prior art keywords
- rule
- service
- data source
- identifier
- business
- 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
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a processing method and a processing system of service data, comprising the following steps: loading a service rule table, wherein the service rule table comprises an identifier of a data source and a corresponding rule flow; acquiring an identifier of a current data source, and reading a corresponding rule stream from the service rule table according to the identifier of the current data source to obtain the rule stream of the current data source; and analyzing rule identifications and the sequence of the rule identifications from the rule flow of the current data source, and sequentially calling the service plug-ins corresponding to the rule identifications. The invention divides the data flow into the service rule table to call the service plug-in, thereby improving the code reuse degree, further improving the coding efficiency and reducing the development and reconstruction cost.
Description
Technical Field
The invention belongs to the technical field of computer networks, and particularly relates to a service data processing method and a service data processing system.
Background
The business plug-in is a program written by an application program interface according to a certain specification. The business processing in many applications is implemented by a plug-in, for example, in a browser, after installing a relevant business plug-in, the browser can directly call the business plug-in to process a specific type of file or data.
Schematic diagram of a business processing architecture is common at present. The service processing flow is as follows:
(1) dividing the service content into different servers according to different service contents, wherein the server 1 is used for realizing data acquisition service, and the server 2 is used for realizing payment service; and
(2) in each server, different service contents are divided into different service logics, for example, in the server 1, the service logics can be divided into: a service logic A, a service logic B, a service logic C and a service logic D; the server 2 can be divided into: business logic A, business logic B, and business logic E.
After the service contents are distributed to different servers, even if different service contents contain the same service logic, such as service logic a and service logic B, the service contents are independently encoded in the server 1 and the server 2 to form a service plug-in.
Therefore, the conventional service processing architecture has the following disadvantages: repeated codes exist among all the service contents, but the reusability and the coupling among the service contents are poor, so that the coding effect of the codes is low, and the cost of code development or reconstruction is high.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a method and a system for processing service data, which can solve the technical problems of low code reuse degree, low coding efficiency, and high development or reconstruction cost in the prior art.
In order to solve the above technical problem, the present invention provides a method for processing service data, including:
loading a service rule table, wherein the service rule table comprises an identifier of a data source and a corresponding rule flow;
acquiring an identifier of a current data source, and reading a corresponding rule stream from the service rule table according to the identifier of the current data source to obtain the rule stream of the current data source; and
and analyzing rule identifications and the sequence of the rule identifications from the rule flow of the current data source, and sequentially calling the service plug-ins corresponding to the rule identifications.
In order to solve the above technical problem, the present invention further provides a system for processing service data, including:
the loading module is used for loading a business rule table, and the business rule table comprises an identifier of a data source and a corresponding rule flow;
the rule flow module is used for acquiring the identifier of the current data source and reading the corresponding rule flow from the service rule table according to the identifier of the current data source to obtain the rule flow of the current data source; and
and the business plug-in module is used for analyzing the rule identification and the sequence of the rule identification from the rule flow of the current data source and calling the business plug-ins corresponding to the rule identification in sequence.
Compared with the prior art, the business data processing method and the business data processing system have the advantages that the data stream is divided into the business rule table to call the business plug-in, so that the code reusability is improved, the coding efficiency is improved, and the development and reconstruction costs are reduced.
Drawings
Fig. 1 is a schematic application environment diagram of a service data processing method and a processing system according to an embodiment of the present invention;
fig. 2 is a schematic basic flow chart of a method for processing service data according to an embodiment of the present invention;
FIG. 3 is a diagram illustrating an example of logic for a business rule table according to an embodiment of the present invention;
fig. 4 is a detailed flowchart of a service data processing method according to a second embodiment of the present invention;
fig. 5 is a schematic block diagram of a service data processing system according to a third embodiment of the present invention;
fig. 6 is a schematic block diagram of a service data processing system according to a fourth embodiment of the present invention.
Detailed Description
Referring to the drawings, wherein like reference numbers refer to like elements throughout, the principles of the present invention are illustrated in a suitable computing environment. The following description is based on illustrated embodiments of the invention and should not be taken as limiting the invention with regard to other embodiments that are not detailed herein.
While the principles of the invention have been described in the foregoing context, which is not intended to be limiting, those of ordinary skill in the art will appreciate that various of the steps and operations described below may also be implemented in hardware. The principles of the present invention are operational with numerous other general purpose or special purpose computing, communication environments or configurations.
Please refer to fig. 1, which is a schematic diagram of an application environment of a processing method and a processing system for service data provided in the present invention. The application environment includes a call server 10, a plug-in server 20, and a communication network 30.
The call server 10 is configured to load a service rule table and a rule engine, where the service rule table is configured to split a data stream into an identifier of a data source and a corresponding rule stream, and the rule engine is configured to split the rule stream into an ordered rule identifier and a corresponding service plug-in; acquiring the identifier of the current data source, and reading the corresponding rule flow from the service rule table; and acquiring a rule identifier in the rule flow and the sequence of the rule identifier, and sequentially calling the service plug-ins corresponding to the rule identifier according to the rule engine.
The plug-in server 20 is configured to connect to the call server 10, and is configured to store various service plug-ins for the call server 10 to call.
The communication network 30 includes a wireless network and a wired network. Wherein the wireless network comprises a combination of one or more of a wireless wide area network, a wireless local area network, a wireless metropolitan area network, and a wireless personal network.
The scheme can be applied to a programming scene of business data processing. Please refer to the following embodiments, a method for processing business data with two sides heavier than business data and a system for processing business data with four sides heavier than business data are provided in the first embodiment. It can be understood that: although the emphasis of each embodiment is different, the design concept is consistent. Moreover, for parts that are not described in detail in a certain embodiment, reference may be made to the detailed description throughout the specification, and further description is omitted.
Example one
Referring to fig. 2, a basic flow chart of a method for processing service data according to an embodiment of the present invention is shown.
The method for processing the service data comprises the following steps:
in step S201, a business rule table is loaded.
The service rule table is a rule for splitting a data stream into an identifier of a data source and a corresponding rule stream and storing a data stream direction. It is to be understood that the rule flow includes one or more rule identifiers and an execution order of the rule identifiers, such as a sequential order or a parallel order.
In step S202, an identifier of the current data source is obtained, and a corresponding rule stream is read from the service rule table according to the identifier of the current data source, so as to obtain the rule stream of the current data source.
In order to facilitate understanding of the data source and the data source identifier, a popular and understandable example is taken, for example, a book of "breeding of common flowers" is borrowed in a bookstore, the current data source is a bookstore database, and the identifier of the data source is: the cultivation of common flowers. Then the book's borrow records, from reader to reader, can be "seen" as its rule flow.
Returning to the mode of processing the service data, as shown in fig. 3, an exemplary diagram of a service rule table provided in an embodiment of the present invention is shown. Taking a certain data source as an example, the identifier appid of the data source is 1, and the rule flows 1001, 1002 and 1004 are executed in sequence; the identification appid of the data source is 2, which in turn executes rule flows 1001, and 1003.
In step S203, a rule identifier and a sequence of the rule identifier are analyzed from the rule stream of the current data source, and the service plug-ins corresponding to the rule identifier are sequentially called.
As shown in fig. 3, where rule flow 1001 calls plug-in a and plug-in B; rule flow 1002 calls plug-in C; rule flow 1003 calls plug-in E; rule flow 1004 calls plug-in D.
According to the business data processing method, the data stream is divided into the business rule table to call the business plug-in, so that the code reuse degree is improved, the coding efficiency is improved, and the development and reconstruction costs are reduced.
Example two
Referring to fig. 4, a detailed flowchart of a method for processing service data according to an embodiment of the present invention is shown.
Fig. 4 is a flowchart optimization of the processing of the service data shown in fig. 2, and the same steps as those in fig. 2 are still started at S20, and the steps different from those in fig. 2 are started at S40, so as to highlight the difference from the basic flowchart.
The method for processing the service data comprises the following steps:
in step S401, the call server obtains a request for changing data through the operation interface.
It is understood that the operation interface includes an operation interface of an application program or an operation interface of a page. The user may select a data source by inputting, clicking, dragging, or the like to generate a request for change of the data. Such as: a sales record for month 7 is generated.
In step S402, the change request is analyzed to obtain an identification of a data source therein.
Still taking the exemplary diagram of the business rule table of fig. 3 as an example, such as the identification of the data source therein: and the appid is 1 and 2.
In step S403, screening and sorting are performed according to the identifier of the data source to generate a business rule table.
It will be appreciated that the generation includes an initial generation of a business rule table and subsequent periodic updates.
Taking the business rule table shown in table 1 as an example, the business rule table is generated according to the identification of the data source in the above step. The step of generating comprises: screening the corresponding rule flow according to the identification of each data source; and forming a business rule table by the data sources and the corresponding rule flows according to a preset rule.
Table 1 service rules table
| Identification of data sources | Regular flow | Remarks for |
| 1 | 1001、1002、1004 | From front to back |
| 2 | 1001、1003 | From front to back |
In step S404, a rule engine is generated, which includes a rule identification and a corresponding business plug-in.
It is to be understood that the rule engine is further configured to define the format and/or content of the rule identifier and the corresponding service plug-in, respectively, to facilitate subsequent invocation. Wherein the rule engine is used for mapping from an access layer to a logic layer. Wherein, the access layer integrates the data stream through Map < string, object > to form a key-value form. The list of the business rule table takes Map interface objects as list objects, Map takes String as a key, and takes Object as a value. Where key is string type and value is Object type, this data can accommodate any data type. The access layer then pushes the data to the logic layer, and the rule engine of the logic layer calls the plug-ins, wherein the logic layer updates the service rule table once every 5 minutes according to a preset update time threshold, corresponding plug-in processing is performed on different data sources according to the setting of the service rule table, each rule has a rule ID, the logic plug-ins executed by the rule and the next rule ID are marked, and each rule ID defines a logic layer.
Wherein the service plug-in is configured to implement service logic through parameter constraint, and the parameter includes: input parameters and output parameters. The input parameter is part or all data of the service data stream Map < string, Object > (the field of the input parameter is configured in the rule), the output field is all merged into the service data stream Map < string, Object >) and automatically sent to the next logic layer, of course, the service plug-in can also output data to the network stream or the file.
The generation of the service plug-in specifically includes: and writing codes for the service plug-in a plug-in server so as to realize pushing of a data source from an access layer to a logic layer. In code writing, the plug-in needs to implement the following interfaces:
public interface Translate
{
public void process(ArrayList<Object>input,
ArrayList<Object[]>output)；
}
it is understood that, referring to fig. 1, the steps S402 to S404 are executed by the plug-in server 20, and the generated business rule table and the rule engine are saved to the plug-in server 20 for being called by a plurality of calling servers 10.
In step S201, the call server loads a business rule table and a rule engine.
Wherein the rules engine comprises: the rules identify and correspond to the business plug-ins. Specifically, the step of loading includes:
(1) setting an updating time threshold;
(2) updating the business rule table according to the identification of the current data source after the updating time threshold value is reached; and
(3) and loading a rule engine according to the identification of the current data source.
In step S202, an identifier of the current data source is obtained, and a corresponding rule stream is read from the service rule table according to the identifier of the current data source, so as to obtain the rule stream of the current data source.
And reading the data sources sequentially according to the identification of the data sources and the corresponding rule flow from the plug-in server.
In step S405, a rule identifier and a sequence of the rule identifier are analyzed from the rule flow of the current data source, and a service plug-in corresponding to the rule identifier is called from the rule engine in sequence.
According to the business data processing method, the data stream is divided into the business rule table to call the business plug-in, so that the code reuse degree is improved, the coding efficiency is improved, and the development and reconstruction costs are reduced.
EXAMPLE III
Referring to fig. 5, a schematic block diagram of a system for processing service data according to an embodiment of the present invention is shown.
A system 500 for processing business data, comprising: a loading module 51, a rule flow module 52, and a business plug-in module 53.
The loading module 51 is configured to load a business rule table and/or a rule engine. The business rule table includes: an identification of a data source and a corresponding rule flow, the rule engine comprising: the rules identify and correspond to the business plug-ins.
Wherein, the loading module 51 includes: a timing submodule 511, a business rule table loading submodule 512, and/or a rules engine loading submodule 513.
The timing submodule 511 is configured to set an update time threshold. And the service rule table loading submodule 512 is connected to the timing submodule, and is configured to update the service rule table every time the update time threshold is reached, and is configured to update the identifier of the current data source. The rule engine loading submodule 513 is configured to load a rule engine.
And the rule flow module 52 is configured to obtain an identifier of the current data source, and read a corresponding rule flow from the service rule table according to the identifier of the current data source to obtain the rule flow of the current data source.
And the service plug-in module 53 is configured to analyze rule identifiers and the sequence of the rule identifiers from the rule stream of the current data source, and sequentially invoke the service plug-ins 531 corresponding to the rule identifiers from the rule engine.
The service plug-in 531 is configured to implement a service logic through a parameter constraint, where the parameter includes: input parameters and output parameters. The input parameter is part or all data of the service data stream Map < string, Object > (the field of the input parameter is configured in the rule), the output field is all merged into the service data stream Map < string, Object >) and automatically sent to the next logic layer, of course, the service plug-in can also output data to the network stream or the file. Specifically, the service plug-in is written by code to realize pushing a data source from an access layer to a logic layer.
The business data processing system of the embodiment of the invention divides the data stream into the business rule table to call the business plug-in, thereby improving the code reuse degree, further improving the coding efficiency and reducing the development and reconstruction costs.
Example four
Referring to fig. 6, a schematic layered diagram of a system for processing service data according to an embodiment of the present invention is shown.
The architecture of the service data processing system 600 includes a user layer 61, an access layer 62, a logical layer 63, and a data layer 64.
The user layer 61 includes an operation interface 54.
The operation interface 54 is used for requesting a change of data acquired according to a user operation. The operation of the user at least includes inputting numbers, dragging graphics, and the like, and the operation is used for specifying an identifier of at least one data source, and the identifier of the data source corresponds to specific data of the data layer 63. The operation interface 54 includes, for example: a Windows operating interface, an iOS operating interface, or an Android operating interface.
The access layer 62 includes an analysis module 55, a rules engine 56, a loading module 51, a rule flow module 52, and a business plug-in module 53.
The analysis module 55 is configured to analyze the change request to obtain an identifier of a data source therein, and generate a service rule table according to the identifier of the data source for subsequent loading.
The analysis module 55 further comprises an update submodule 551 for periodically updating the business rule table.
The rule engine 56 is configured to store the rule identifier and the corresponding service plug-in. In addition, the rule engine is also used for defining the format and/or the content of the rule identification and the corresponding service plug-in so as to be convenient for programs of different sources and interfaces to call.
The loading module 51 is configured to load a business rule table and a rule engine. And the loading business rule table is generated according to the identifier of the data source. The business rule table includes an identification of a data source and a corresponding rule flow, and the rule engine includes: the rules identify and correspond to the business plug-ins.
It will be appreciated that the loading module 51 includes a timing sub-module 511, a business rule table loading sub-module 512, a rules engine loading sub-module 513, and an update sub-module 514.
The timing submodule 511 is configured to set an update time threshold. And the business rule table loading submodule 512 is connected to the timing submodule, and is configured to, after the update time threshold is reached, screen and sort the rule flow according to the identifier of the current data source, so as to generate or update the business rule table. The rule engine loading submodule 513 is configured to load a rule engine according to the identifier of the current data source.
And the rule flow module 52 is configured to obtain an identifier of the current data source, and read a corresponding rule flow from the service rule table according to the identifier of the current data source to obtain the rule flow of the current data source.
And the service plug-in module 53 is configured to obtain the rule identifier and the sequence of the rule identifier in the rule flow of the current data source, and sequentially call the service plug-ins 531 corresponding to the rule identifier from the rule engine.
The service plug-in 531 is configured to implement a service logic through a parameter constraint, where the parameter includes: input parameters and output parameters. The input parameter is part or all data of the service data stream Map < string, Object > (the field of the input parameter is configured in the rule), the output field is all merged into the service data stream Map < string, Object >) and automatically sent to the next logic layer, of course, the service plug-in can also output data to the network stream or the file. Specifically, the service plug-in is written by code to realize pushing a data source from an access layer to a logic layer.
The business data processing system of the embodiment of the invention divides the data stream into the business rule table to call the business plug-in, thereby improving the code reuse degree, further improving the coding efficiency and reducing the development and reconstruction costs.
The method and the system for processing the service data provided by the embodiment of the invention belong to the same concept, and the specific implementation process is described in the whole specification and is not described herein again.
In summary, although the present invention has been described with reference to the preferred embodiments, the above-described preferred embodiments are not intended to limit the present invention, and those skilled in the art can make various changes and modifications without departing from the spirit and scope of the present invention, therefore, the scope of the present invention shall be determined by the appended claims.
Claims (9)
1. A method for processing service data is characterized by comprising the following steps:
acquiring a data change request through an operation interface;
analyzing the change request to acquire the identification of the data source in the change request; and
screening and sequencing the rule flow according to the identifier of the data source to generate a service rule table;
generating a rule engine, wherein the rule engine comprises a rule identifier and a corresponding business plug-in; one rule identification corresponds to at least one service plug-in, and different rule identifications correspond to different service plug-ins;
loading the service rule table and the rule engine, wherein the service rule table comprises an identifier of a data source obtained by splitting a data stream and a corresponding rule stream, and the service rule table is used for storing a rule of a data stream direction; the rule flow comprises one or more rule identifications and an execution order of the rule identifications; the rule flows corresponding to the data sources with at least two different identifications comprise the same rule identification;
acquiring an identifier of a current data source, and reading a corresponding rule stream from the service rule table according to the identifier of the current data source to obtain the rule stream of the current data source; and
analyzing the rule identification and the execution sequence of the rule identification from the rule flow of the current data source, and sequentially calling the business plug-ins corresponding to the rule identification through the rule engine; the method comprises the following steps: when at least two different identifications are processed and the corresponding rule flows comprise the current data sources with the same rule identification, the service plug-ins corresponding to the same rule identification are repeatedly called to process the current data sources with the at least two different identifications.
2. The process of claim 1, wherein loading the business rule table further comprises:
and updating the business rule table periodically.
3. The process of claim 2, wherein said loading a business rule table further comprises:
setting an updating time threshold;
the periodically updating the business rule table includes: and updating the business rule table according to the identification of the current data source after the updating time threshold is reached.
4. The processing method of claim 1, wherein the generating a rule engine specifically comprises:
and generating a service plug-in, wherein the service plug-in is used for realizing service logic through parameter constraint, and the parameters comprise input parameters and output parameters.
5. A system for processing traffic data, comprising:
the operation interface is used for acquiring a change request of data according to the operation of a user;
the analysis module is used for analyzing the change request to acquire the identifier of the data source in the change request; and
the loading module is also used for screening and sequencing the rule flow according to the identifier of the data source so as to generate a service rule table;
the rule engine is used for storing the rule identification and the corresponding business plug-in; one rule identification corresponds to at least one service plug-in, and different rule identifications correspond to different service plug-ins;
the loading module is configured to load the service rule table and the rule engine, where the service rule table includes an identifier of a data source obtained by splitting a data stream and a corresponding rule stream, and the service rule table is used to store a rule of a data flow direction; the rule flow comprises one or more rule identifications and an execution order of the rule identifications; the rule flows corresponding to the data sources with at least two different identifications comprise the same rule identification;
the rule flow module is used for acquiring the identifier of the current data source and reading the corresponding rule flow from the service rule table according to the identifier of the current data source to obtain the rule flow of the current data source; and
the business plug-in module is used for analyzing the rule identification and the execution sequence of the rule identification from the rule flow of the current data source and calling the business plug-ins corresponding to the rule identification in sequence through the rule engine; the method comprises the following steps: when at least two different identifications are processed and the corresponding rule flows comprise the current data sources with the same rule identification, the service plug-ins corresponding to the same rule identification are repeatedly called to process the current data sources with the at least two different identifications.
6. The processing system of claim 5, wherein the load module comprises:
and the updating submodule is used for updating the business rule table periodically.
7. The processing system of claim 6, wherein the load module further comprises:
the timing submodule is used for setting an updating time threshold;
and the business rule table loading submodule is connected with the timing submodule and used for updating the business rule table according to the identifier of the current data source after the updating time threshold is reached and for updating the identifier of the current data source.
8. The processing system of claim 5, wherein the rules engine comprises:
and the service plug-in is used for realizing service logic through parameter constraint, and the parameters comprise input parameters and output parameters.
9. A server, comprising a memory and a processor, the memory having stored thereon a computer program that, when executed by the processor, causes the processor to perform the steps of the method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510632618.4A CN106557307B (en) | 2015-09-29 | 2015-09-29 | Service data processing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510632618.4A CN106557307B (en) | 2015-09-29 | 2015-09-29 | Service data processing method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106557307A CN106557307A (en) | 2017-04-05 |
| CN106557307B true CN106557307B (en) | 2021-06-11 |
Family
ID=58414557
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510632618.4A Active CN106557307B (en) | 2015-09-29 | 2015-09-29 | Service data processing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106557307B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108287708B (en) * | 2017-12-22 | 2021-06-25 | 深圳市云智融科技有限公司 | Data processing method and device, server and computer readable storage medium |
| CN109542428A (en) * | 2018-10-16 | 2019-03-29 | 平安普惠企业管理有限公司 | Method for processing business, device, computer equipment and storage medium |
| CN110704545B (en) * | 2019-09-12 | 2022-06-07 | 上海数禾信息科技有限公司 | Data calling method and device for data source provider |
| CN110928681A (en) * | 2019-11-11 | 2020-03-27 | 北京明略软件***有限公司 | Data processing method and device, storage medium and electronic device |
| CN110909061A (en) * | 2019-11-27 | 2020-03-24 | 恩亿科(北京)数据科技有限公司 | Data source processing method and device, electronic equipment and storage medium |
| CN117251713A (en) * | 2023-10-11 | 2023-12-19 | 易方达基金管理有限公司 | Data processing method, device, terminal equipment and medium for buying quantity service |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102662656A (en) * | 2012-03-15 | 2012-09-12 | 北京神州数码思特奇信息技术股份有限公司 | Plug-in method and system for program structure |
| CN103197950A (en) * | 2013-04-19 | 2013-07-10 | 中国海洋大学 | Plug-in virtual machine implementing method |
| CN103345386A (en) * | 2013-05-31 | 2013-10-09 | 电子科技大学 | Software production method, device and operation system |
| CN103942055A (en) * | 2014-04-30 | 2014-07-23 | 北京邮电大学 | Development system and method for fusion network mixing service process programming language |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101286809A (en) * | 2008-05-07 | 2008-10-15 | 中兴通讯股份有限公司 | Method and device for conditional receiving update of plug-in by multimedia broadcast |
| US20100257539A1 (en) * | 2009-03-31 | 2010-10-07 | Krishnakumar Narayanan | System, method and apparatus for providing functions to applications on a digital electronic device |
| CN103297381B (en) * | 2012-02-22 | 2017-01-18 | 阿里巴巴集团控股有限公司 | Service access method based on plugin and system thereof |
| CN103617508A (en) * | 2013-12-12 | 2014-03-05 | 用友软件股份有限公司 | Configurable business rule plug-in extension apparatus and business rule plug-in extension method |
| CN104317624B (en) * | 2014-11-04 | 2017-06-06 | 南京联创科技集团股份有限公司 | Data assembly method based on plug-in unit treatment |
-
2015
- 2015-09-29 CN CN201510632618.4A patent/CN106557307B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102662656A (en) * | 2012-03-15 | 2012-09-12 | 北京神州数码思特奇信息技术股份有限公司 | Plug-in method and system for program structure |
| CN103197950A (en) * | 2013-04-19 | 2013-07-10 | 中国海洋大学 | Plug-in virtual machine implementing method |
| CN103345386A (en) * | 2013-05-31 | 2013-10-09 | 电子科技大学 | Software production method, device and operation system |
| CN103942055A (en) * | 2014-04-30 | 2014-07-23 | 北京邮电大学 | Development system and method for fusion network mixing service process programming language |
Non-Patent Citations (1)
| Title |
|---|
| 基于JAVA业务规则管理技术的研究;王玉;《科技信息(学术研究)》;20070325;第162-163页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106557307A (en) | 2017-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106557307B (en) | Service data processing method and system | |
| CN108958714B (en) | Business component type development method and device, computer equipment and storage medium | |
| US10108914B2 (en) | Method and system for morphing object types in enterprise content management systems | |
| JP5298117B2 (en) | Data merging in distributed computing | |
| CN109670053B (en) | Data object mapping method, device, equipment and computer readable storage medium | |
| CN110275861B (en) | Data storage method and device, storage medium and electronic device | |
| CN107015853B (en) | Method and device for realizing multi-stage task | |
| CN106991100B (en) | Data import method and device | |
| US11210181B2 (en) | System and method for implementing data manipulation language (DML) on Hadoop | |
| CN102129425B (en) | The access method of big object set table and device in data warehouse | |
| CN111061475B (en) | Software code generating method, device, computer equipment and storage medium | |
| CN110956269A (en) | Data model generation method, device, equipment and computer storage medium | |
| CN111126019A (en) | Report generation method and device based on mode customization and electronic equipment | |
| CN110647322B (en) | List rendering method and device, electronic equipment and computer readable medium | |
| CN112463149B (en) | Software-defined satellite-oriented reusable code library construction method and device | |
| US9747295B1 (en) | Updating a large dataset in an enterprise computer system | |
| CN107766519B (en) | Method for visually configuring data structure | |
| CN112068812B (en) | Micro-service generation method and device, computer equipment and storage medium | |
| CN113076365B (en) | Data synchronization method, device, electronic equipment and storage medium | |
| CN115543428A (en) | Simulated data generation method and device based on strategy template | |
| CN112434004A (en) | Data migration method and device for heterogeneous system, computer equipment and storage medium | |
| CN111737964A (en) | Form dynamic processing method, equipment and medium | |
| CN112506944B (en) | Data standard conversion access method, device, equipment and medium between service systems | |
| KR101638048B1 (en) | Sql query processing method using mapreduce | |
| CN116755684B (en) | OAS Schema generation method, device, equipment and 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 |