CN113641354A - Service data processing method and device, electronic equipment and storage medium - Google Patents
Service data processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN113641354A CN113641354A CN202110885462.6A CN202110885462A CN113641354A CN 113641354 A CN113641354 A CN 113641354A CN 202110885462 A CN202110885462 A CN 202110885462A CN 113641354 A CN113641354 A CN 113641354A
- Authority
- CN
- China
- Prior art keywords
- service
- target
- processing request
- file
- interface parameter
- 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.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title claims description 16
- 238000012545 processing Methods 0.000 claims abstract description 124
- 238000000034 method Methods 0.000 claims abstract description 60
- 230000008569 process Effects 0.000 claims abstract description 22
- 238000004806 packaging method and process Methods 0.000 claims description 16
- 238000005516 engineering process Methods 0.000 claims description 11
- 238000005538 encapsulation Methods 0.000 claims description 10
- 238000006243 chemical reaction Methods 0.000 claims description 5
- 238000011161 development Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 6
- 238000010606 normalization Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 239000000284 extract Substances 0.000 description 3
- 230000004069 differentiation Effects 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000003491 array Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- JEIPFZHSYJVQDO-UHFFFAOYSA-N iron(III) oxide Inorganic materials O=[Fe]O[Fe]=O JEIPFZHSYJVQDO-UHFFFAOYSA-N 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/36—Software reuse
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the invention discloses a method and a device for processing service data, electronic equipment and a storage medium, wherein the method comprises the following steps: when a service processing request is received, acquiring a target service identifier carried by the service processing request; determining at least one called target interface parameter according to the target service identifier, and carrying out standardization processing on the at least one target interface parameter to obtain an executable file corresponding to the service processing request; and sending the executable file to a web front end so that the web front end processes the service processing request to obtain target feedback data, and sending the target feedback data to a client. According to the technical scheme of the embodiment of the invention, the client sides of the medical insurance bureaus of all the places provide uniform method names and interface parameters for the web front end, web end developers do not need to perform on-site joint debugging, and the multiplexing of web end codes is realized.
Description
Technical Field
The embodiment of the invention relates to the technical field of data processing, in particular to a business data processing method and device, electronic equipment and a storage medium.
Background
With the continuous improvement of the digitalization degree of the medical insurance system, medical insurance offices in different places can install clients in units to provide various services for the public, and therefore, the transmission of service data between each client and the web system serving as the server becomes the key for the stable operation of the medical insurance system.
In the prior art, in the process of implementing data transmission between a local medical insurance system and a server, a web system serving as the server is directly embedded in a client corresponding to each local medical insurance bureau, and when a certain local medical insurance bureau transmits service data to the web system, the client needs to call a C + + method corresponding to the service and return the C + + method to the web system. However, for each service, the C + + method provided by each local medical insurance office is not the same, and at the same time, the interfaces provided by each local medical insurance office to the web system are also different. Therefore, in order to adapt the client of each local medical insurance bureau to the web system, the web developer not only needs to go to each local medical insurance bureau for on-site development joint debugging, but also needs to continuously iterate the codes of the web end and upgrade the client of the local medical insurance bureau.
Therefore, in the scheme provided by the related technology, in the process of adapting each local medical insurance bureau with the web system, the development cost is increased in a way that web developers go to joint debugging on site, the code of the web end cannot be reused, and meanwhile, the client needs to be continuously upgraded, so that the user experience is reduced.
Disclosure of Invention
The invention provides a business data processing method, a business data processing device, electronic equipment and a storage medium, which enable each local medical insurance bureau client to provide uniform method names and interface parameters for a web front end, do not need web end developers to perform on-site joint debugging, and realize the reuse of web end codes.
In a first aspect, an embodiment of the present invention provides a method for processing service data, where the method includes:
when a service processing request is received, acquiring a target service identifier carried by the service processing request;
determining at least one called target interface parameter according to the target service identifier, and carrying out standardization processing on the at least one target interface parameter to obtain an executable file corresponding to the service processing request;
and sending the executable file to a web front end so that the web front end processes the service processing request to obtain target feedback data, and sending the target feedback data to a client.
In a second aspect, an embodiment of the present invention further provides a service data processing apparatus, where the apparatus includes:
the target service identification acquisition module is used for acquiring a target service identification carried by a service processing request when the service processing request is received;
the standardization processing module is used for determining at least one called target interface parameter according to the target service identifier and carrying out standardization processing on the at least one target interface parameter to obtain an executable file corresponding to the service processing request;
and the target feedback data generation module is used for sending the executable file to a web front end so that the web front end processes the service processing request to obtain target feedback data and sending the target feedback data to a client.
In a third aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors implement the service data processing method according to any of the embodiments of the present invention.
In a fourth aspect, the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform the service data processing method according to any one of the embodiments of the present invention.
The technical scheme of the embodiment of the invention obtains the target service identification carried by the service processing request when receiving the service processing request so as to determine the specific service, determines at least one called target interface parameter according to the target service identification, carries out standardized processing on the at least one target interface parameter so as to obtain an executable file corresponding to the service processing request, then sends the executable file to the web front end so that the web front end processes the service processing request to obtain target feedback data, and sends the target feedback data to the client so that the client of each side medical insurance bureau provides uniform method names and interface parameters for the web front end, web developers are not required to carry out on-site development joint debugging on the basis of the difference of the method names and the interface parameters, thereby not only saving the development cost, but also realizing the multiplexing of web end codes and further, the client sides of the medical insurance offices in all the places do not need to be frequently upgraded, and the user experience is improved.
Drawings
In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, a brief description is given below of the drawings used in describing the embodiments. It should be clear that the described figures are only views of some of the embodiments of the invention to be described, not all, and that for a person skilled in the art, other figures can be derived from these figures without inventive effort.
Fig. 1 is a schematic flowchart of a service data processing method according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a service data processing method according to a second embodiment of the present invention;
fig. 3 is a block diagram of a service data processing apparatus according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of an electronic device according to a fourth 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 limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a schematic flow diagram of a service data processing method according to an embodiment of the present invention, where the embodiment is applicable to a situation where a client receives a service request and a web front-end processes corresponding data, and is particularly applicable to a scenario where a local medical insurance office transfers a method related to medical insurance services to the web front-end by using a medical insurance office interface and the web front-end processes the data.
As shown in fig. 1, the method specifically includes the following steps:
s110, when receiving the service processing request, obtaining the target service identification carried by the service processing request.
The service processing request may be a processing request for a specific service received by a client, and it should be understood by those skilled in the art that a client is a client corresponding to a server (web front end) and is an application program capable of providing multiple services for a client. In this embodiment, when the client is an application installed in each medical insurance department, the service processing request includes a request associated with medical insurance service. For example, the local medical insurance bureau client receives a medical insurance card payment request, a medical insurance card balance inquiry request, a medical insurance card password modification request and the like.
In this embodiment, when the client receives the service processing request, the client may extract specific information carried in the request, specifically, extract a target service identifier in the service processing request. The service identification characterizes which service of the medical insurance office the current request is associated with. For example, when the client extracts the target service identification "ZF" from the received service processing request, it may be determined that the current request is a medical insurance card payment request.
It should be noted that different clients are adapted to each local medical insurance bureau, so for the same type of service, even if the service identifiers in the service processing requests of different local medical insurance bureaus are different, the adapted client can still determine which service the current request is associated with.
S120, determining at least one called target interface parameter according to the target service identifier, and carrying out standardization processing on the at least one target interface parameter to obtain an executable file corresponding to the service processing request.
After the target service identifier is determined, a target interface parameter associated with the target service identifier may be further determined. When the client is installed in the local medical insurance bureau, the interface to be called can be determined for the medical insurance business through the target business identifier, and the target interface parameters include but are not limited to various parameters such as the ID of the local medical insurance bureau, the business name, the payment mode, the data format of the data transmitted by the interface, the code set used by the data, the signature algorithm adopted by the current business and the like.
In the stage of determining the target interface parameter, optionally, a target service executing party corresponding to the target service identifier is determined, and a target interface parameter corresponding to the service processing request in the target service executing party is called based on a preset language.
The service executing party comprises a medical insurance system, and it can be understood that when the service executing party is the medical insurance system, the local medical insurance bureau corresponding to the current client can be determined through the target service identifier. Further, interfaces provided by medical insurance offices in various places are different, and therefore, the interface parameters need to be called based on a preset language, in this embodiment, target interface parameters corresponding to the service processing request may be called based on C + +, and it can be understood that one or more target interface parameters may be called.
Furthermore, after the target interface parameters are called based on C + +, the called target interface parameters also need to be standardized, so that after the service data is transmitted from the client to the web front end, the web front end can directly process the service request without adapting to a local medical insurance office system. Those skilled in the art should understand that there are many ways of standardizing processing, for example, normalization processing of data formats, normalization processing of Application Programming Interface (API) return values, etc., and a specific standardization manner may be selected according to actual situations, and the embodiment of the present disclosure is not limited specifically herein.
Optionally, at the stage of performing standardized processing on at least one target interface parameter, determining a differentiated encapsulation mode corresponding to a target service executor; standardizing at least one target interface parameter based on a differential packaging mode and a preset language to obtain a file to be processed corresponding to the preset language; and converting the file to be processed into an executable file based on the target conversion technology.
In this embodiment, when the client is a client installed in a local medical insurance office, a corresponding differentiated encapsulation manner may be determined in the current client according to the target service identifier, for example, a configuration and encapsulation form of one interface information may be determined for a request of a payment type of a medical insurance card received by the client, and another configuration and encapsulation form of the interface information may be determined for a request of a balance inquiry type of the medical insurance card received by the client.
Further, after the differentiated packaging mode of the interface parameters corresponding to the current request is determined, the interface parameters can be subjected to standardized processing based on a preset language, and for a medical insurance system of a local medical insurance office, the preset language can be a C + + language. After the target interface parameters are standardized based on C + +, the corresponding file to be processed can be obtained, and it can be understood that the file to be processed is a C + + file generated in the local medical insurance bureau client.
Illustratively, each local medical insurance office relates to 1000 parameters, for the local medical insurance office marked as a, only five parameters are related in the process of transmitting service data according to the current request, after the target interface parameters are packaged based on a differentiated packaging mode to obtain a C + + file, the five parameters in the file are endowed with parameter values corresponding to the current interface, and other interfaces irrelevant to the current request can be assigned values or directly set to zero according to preset fields; for the local medical insurance office marked as B, only three parameters are involved in the service data transmission process according to the current request, after the target interface parameters are packaged based on a differentiated packaging mode to obtain a C + + file, the three parameters in the file can be endowed with parameter values corresponding to the current interface, and other interfaces irrelevant to the current request can be assigned values or directly set to zero according to preset fields.
Through the process of carrying out standardized processing on the target interface parameters (namely packaging the interface parameters into a C + + file in a differentiated mode), the client side can conveniently and directly transmit the C + + method corresponding to the current request to the web front end.
After the file to be processed is generated, the client may also convert the file to be processed in order to enable the web front end to directly execute the file after receiving the file. Optionally, the file to be processed is converted into an executable file based on the WebAssembly technology.
The WebAssembly technology is a technical scheme that codes are written by using a non-JavaScript language and run on a browser, the codes can be C, C + + or Rust language codes, an executable file obtained by using the WebAssembly technology is a wap file, and the wap file is a binary file. After the codes are compiled in a browser by using a WebAssembly technology, corresponding byte codes can be obtained, and then the program runs on a CPU at a speed close to the native speed.
In this embodiment, the client may convert the C + + file into a wasm file by using a specific tool, for example, the client calls an emscript compiler to compile codes in the C + + file, so as to obtain a corresponding wasm file.
Under the condition that interface parameters of various local medical insurance offices are different, the files to be processed in the form of C + + are converted into the wasm files which can be directly executed by the browser, so that web end developers do not need to go to the local medical insurance offices for development joint debugging, development cost is saved, and the web end codes are reused.
S130, the executable file is sent to the web front end so that the web front end can process the service processing request to obtain target feedback data, and the target feedback data is sent to the client.
In this embodiment, after receiving the executable file in the wasm format, the web front end serving as the server may process the service processing request, and after the processing is completed, corresponding feedback data may be obtained, where it can be understood that the feedback data represents a processing result of the request. For example, for a medical insurance card payment request, after the web front end processes the request based on executable bytecode in the wasm file, the amount of the medical insurance card consumption can be determined, and further, based on preset configuration items and configuration fields, the "amount of the current consumption: the feedback data in the form of X element is fed back to the local medical insurance bureau, and the specific processing mode of the medical insurance card balance inquiry request, the medical insurance card password modification request and the like is similar to that of the medical insurance card payment request, and the details of the embodiment of the disclosure are omitted here.
In this embodiment, after the web front end processes the request based on the executable bytecode in the wasm file and obtains the corresponding feedback data, the request can also be transmitted to the web back end as a processing result, so as to store and backup the processing result in the corresponding server.
It should be noted that before the service processing request is received, the differentiated encapsulation method corresponding to each service executing party is determined according to at least one interface parameter corresponding to each service executing party, so that when the service processing request is received, the to-be-processed file is obtained based on the differentiated encapsulation method corresponding to the service processing request.
In this embodiment, the interface parameters corresponding to each local medical insurance bureau are different, and therefore, in order to perform standardized processing on the interface parameters of different local medical insurance bureaus when receiving a service processing request, it is further necessary to determine, in advance, a correspondence between one or more interfaces and a differentiated encapsulation manner in a client of the local medical insurance bureau for each medical insurance service, and store the correspondence in the form of a mapping table. Based on the method, after a service processing request is received and at least one target interface parameter is determined based on a target service identifier, a differentiated packaging mode corresponding to the interfaces can be determined in a table look-up mode, and then a corresponding C + + file is obtained.
According to the technical scheme of the embodiment, when a service processing request is received, a target service identifier carried by the service processing request is obtained, so that a specific service is determined, at least one called target interface parameter is determined according to the target service identifier, at least one target interface parameter is subjected to standardized processing to obtain an executable file corresponding to the service processing request, the executable file is sent to the web front end, the web front end is enabled to process the service processing request to obtain target feedback data, the target feedback data is sent to the client, so that the client of each medical insurance bureau provides a uniform method name and interface parameters for the web front end, web developers are not required to go to the site for development joint debugging due to the difference between the method name and the interface parameters, development cost is saved, multiplexing of web end codes is realized, and further, the client of each medical insurance bureau is not required to be frequently upgraded, the user experience is improved.
Example two
As an alternative embodiment of the foregoing embodiment, fig. 2 is a schematic flow chart of a service data processing method according to a second embodiment of the present invention. For the purpose of clearly describing the technical scheme of the embodiment, the application scenario that the local medical insurance office transmits the method related to the medical insurance card payment service to the web front end by using the medical insurance office interface and the front end performs processing is taken as an example for description, but the application scenario is not limited to the above scenario and can be applied to various scenarios requiring processing of service data.
Referring to fig. 2, corresponding clients are installed in each local medical insurance office to provide a plurality of medical insurance services, and each local medical insurance office has a corresponding C + + method for a specific service. When the client receives a payment request of the medical insurance card related to payment, the information carried in the request can be extracted, and then the payment service identification corresponding to the request is determined.
With continued reference to fig. 2, the interface parameters provided by each local medical insurance bureau are different (for example, in the relevant interfaces for medical insurance payment, different local medical insurance bureaus are different in various parameters such as medical insurance bureau ID, service name, payment method, data format of data transmitted by the interface, code set used by the data, signature algorithm adopted by the current service, and the like), so that, in order to enable the service data to be transmitted to the web front end, the web front end can directly process the service request without adapting to the local medical insurance bureau system, and at least one target interface parameter of the local medical insurance bureau needs to be standardized. Specifically, target interface parameters corresponding to the service processing request can be called based on C + +, then a corresponding differentiated encapsulation mode is determined according to the identifier of the medical insurance payment service, and finally the target interface parameters of the interface used by the local medical insurance bureau in the payment service are encapsulated based on C + + language to obtain a corresponding C + + file.
With reference to fig. 2, after the C + + file is obtained, in order to enable the web front end to directly execute after receiving the file, the client further needs to convert the file to be processed based on the WebAssembly technology to obtain an executable file in the wasm format. After the Web front end receives the wasm file, the medical insurance card payment request can be processed based on the byte codes in the file. After the processing is finished, the amount of the medical insurance card consumption can be determined, and based on the preset configuration items and the configuration fields, the 'amount of the consumption at this time' can be generated: and feeding back the feedback data in the form of X-element to the local medical insurance bureau. Meanwhile, the web front end can also transmit the processing result to the web back end so as to store and backup the processing result in the corresponding server.
The beneficial effects of the above technical scheme are: the method and the system have the advantages that the client sides of the medical insurance bureaus of all the places provide uniform method names and interface parameters for the web front end, web developers are not required to go to the field for development joint debugging due to the difference of the method names and the interface parameters, development cost is saved, the code reuse of the web end is realized, further, the client sides of the medical insurance bureaus of all the places are not required to be frequently upgraded, and user experience is improved.
EXAMPLE III
Fig. 3 is a block diagram of a service data processing apparatus according to a third embodiment of the present invention, which is capable of executing a service data processing method according to any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method. As shown in fig. 3, the apparatus specifically includes: a target service identification obtaining module 310, a normalization processing module 320, and a target feedback data generating module 330.
A target service identifier obtaining module 310, configured to obtain, when a service processing request is received, a target service identifier carried in the service processing request.
The normalization processing module 320 is configured to determine at least one called target interface parameter according to the target service identifier, and perform normalization processing on the at least one target interface parameter to obtain an executable file corresponding to the service processing request.
And the target feedback data generation module 330 is configured to send the executable file to a web front end, so that the web front end processes the service processing request to obtain target feedback data, and sends the target feedback data to a client.
On the basis of the above technical solutions, the standardization processing module 320 includes a target service executor determining unit and a target interface parameter retrieving unit.
And the target service executive party determining unit is used for determining the target service executive party corresponding to the target service identification.
And the target interface parameter calling unit is used for calling a target interface parameter corresponding to the service processing request in the target service execution party based on a preset language.
On the basis of the above technical solutions, the standardization processing module 320 includes a differentiation packaging manner determining unit, a standardization processing unit, and a to-be-processed file converting unit.
And the differential packaging mode determining unit is used for determining the differential packaging mode corresponding to the target service executing party.
And the standardization processing unit is used for carrying out standardization processing on the at least one target interface parameter based on the differentiation packaging mode and a preset language to obtain a file to be processed corresponding to the preset language.
And the file to be processed conversion unit is used for converting the file to be processed into the executable file based on a target conversion technology.
Optionally, the to-be-processed file converting unit is further configured to convert the to-be-processed file into the executable file based on a WebAssembly technology.
On the basis of the technical schemes, the executable file is a wasm file, the service processing request comprises a request associated with medical insurance service, and the service executing party comprises a medical insurance system.
On the basis of the above technical solutions, the service data processing apparatus further includes a differentiated encapsulation mode determining module.
And the differential packaging mode determining module is used for determining the differential packaging mode corresponding to each service executing party according to at least one interface parameter corresponding to each service executing party so as to obtain the file to be processed based on the differential packaging mode corresponding to the service processing request when receiving the service processing request.
In the technical scheme provided by this embodiment, when a service processing request is received, a target service identifier carried by the service processing request is obtained, so as to determine a specific service, at least one called target interface parameter is determined according to the target service identifier, at least one target interface parameter is subjected to standardized processing, an executable file corresponding to the service processing request is obtained, the executable file is sent to the web front end, the web front end processes the service processing request to obtain target feedback data, the target feedback data is sent to the client, so that the client of each local medical insurance bureau provides a uniform method name and interface parameters for the web front end, web developers are not required to perform development joint debugging on site due to the difference between the method name and the interface parameters, development cost is saved, multiplexing of web end codes is also realized, and further, the client sides of the medical insurance offices in all the places do not need to be frequently upgraded, and the user experience is improved.
The service data processing device provided by the embodiment of the invention can execute the service data processing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
It should be noted that, the units and modules included in the apparatus are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions 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 embodiment of the invention.
Example four
Fig. 4 is a schematic structural diagram of an electronic device according to a fourth embodiment of the present invention. FIG. 4 illustrates a block diagram of an exemplary electronic device 40 suitable for use in implementing embodiments of the present invention. The electronic device 40 shown in fig. 4 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.
As shown in fig. 4, electronic device 40 is embodied in the form of a general purpose computing device. The components of electronic device 40 may include, but are not limited to: one or more processors or processing units 401, a system memory 402, and a bus 403 that couples the various system components (including the system memory 402 and the processing unit 401).
The system memory 402 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)404 and/or cache memory 405. The electronic device 40 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 406 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 4, and commonly referred to as a "hard drive"). Although not shown in FIG. 4, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 403 by one or more data media interfaces. Memory 402 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 408 having a set (at least one) of program modules 407 may be stored, for example, in memory 402, such program modules 407 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. Program modules 407 generally perform the functions and/or methods of the described embodiments of the invention.
The electronic device 40 may also communicate with one or more external devices 409 (e.g., keyboard, pointing device, display 410, etc.), with one or more devices that enable a user to interact with the electronic device 40, and/or with any devices (e.g., network card, modem, etc.) that enable the electronic device 40 to communicate with one or more other computing devices. Such communication may be through input/output (I/O) interface 411. Also, the electronic device 40 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 412. As shown, the network adapter 412 communicates with the other modules of the electronic device 40 over the bus 403. It should be appreciated that although not shown in FIG. 4, other hardware and/or software modules may be used in conjunction with electronic device 40, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.
The processing unit 401 executes various functional applications and data processing by executing programs stored in the system memory 402, for example, to implement the service data processing method provided by the embodiment of the present invention.
EXAMPLE five
The fifth embodiment of the present invention further provides a storage medium containing computer-executable instructions, which are used for executing the business data processing method when executed by a computer processor.
The method comprises the following steps:
when a service processing request is received, acquiring a target service identifier carried by the service processing request;
determining at least one called target interface parameter according to the target service identifier, and carrying out standardization processing on the at least one target interface parameter to obtain an executable file corresponding to the service processing request;
and sending the executable file to a web front end so that the web front end processes the service processing request to obtain target feedback data, and sending the target feedback data to a client.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable item code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
The item code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer project code for carrying out operations for embodiments of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The project code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
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 (10)
1. A method for processing service data is characterized by comprising the following steps:
when a service processing request is received, acquiring a target service identifier carried by the service processing request;
determining at least one called target interface parameter according to the target service identifier, and carrying out standardization processing on the at least one target interface parameter to obtain an executable file corresponding to the service processing request;
and sending the executable file to a web front end so that the web front end processes the service processing request to obtain target feedback data, and sending the target feedback data to a client.
2. The method of claim 1, wherein the determining at least one target interface parameter for invocation according to the target service identifier comprises:
determining a target service executive party corresponding to the target service identification;
and calling a target interface parameter corresponding to the service processing request in the target service execution party based on a preset language.
3. The method of claim 1, wherein the normalizing the at least one target interface parameter to obtain an executable file corresponding to the service processing request comprises:
determining a differential encapsulation mode corresponding to the target service executive party;
standardizing the at least one target interface parameter based on the differential packaging mode and a preset language to obtain a file to be processed corresponding to the preset language;
and converting the file to be processed into the executable file based on a target conversion technology.
4. The method of claim 3, wherein converting the pending file to the executable file based on a target conversion technique comprises:
and converting the file to be processed into the executable file based on a WebAssembly technology.
5. The method of any of claims 1-4, wherein the executable file is a wasm file, wherein the service processing request comprises a request associated with a medical insurance service, and wherein the service executor comprises a medical insurance system.
6. The method of claim 1, further comprising:
and determining a differential packaging mode corresponding to each service executing party according to at least one interface parameter corresponding to each service executing party, so as to obtain the file to be processed based on the differential packaging mode corresponding to the service processing request when receiving the service processing request.
7. A service data processing apparatus, comprising:
the target service identification acquisition module is used for acquiring a target service identification carried by a service processing request when the service processing request is received;
the standardization processing module is used for determining at least one called target interface parameter according to the target service identifier and carrying out standardization processing on the at least one target interface parameter to obtain an executable file corresponding to the service processing request;
and the target feedback data generation module is used for sending the executable file to a web front end so that the web front end processes the service processing request to obtain target feedback data and sending the target feedback data to a client.
8. The apparatus of claim 7, wherein the standardized processing module comprises a target service executor determining unit and a target interface parameter retrieving unit; wherein,
the target service executive party determining unit is used for determining a target service executive party corresponding to the target service identifier;
and the target interface parameter calling unit is used for calling a target interface parameter corresponding to the service processing request in the target service executing party based on a preset language.
9. An electronic device, characterized in that the electronic device comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the business data processing method of any one of claims 1-6.
10. A storage medium containing computer executable instructions for performing the business data processing method of any one of claims 1-6 when executed by a computer processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110885462.6A CN113641354A (en) | 2021-08-03 | 2021-08-03 | Service data processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110885462.6A CN113641354A (en) | 2021-08-03 | 2021-08-03 | Service data processing method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113641354A true CN113641354A (en) | 2021-11-12 |
Family
ID=78419443
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110885462.6A Pending CN113641354A (en) | 2021-08-03 | 2021-08-03 | Service data processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113641354A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114840276A (en) * | 2022-04-15 | 2022-08-02 | 北京百度网讯科技有限公司 | Object calling method, device, equipment, storage medium and program product |
| CN114885026A (en) * | 2022-07-07 | 2022-08-09 | 飞狐信息技术（天津）有限公司 | Data interface request processing system, method, equipment and storage medium |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102622718A (en) * | 2012-04-27 | 2012-08-01 | 南京农业大学 | Web Service-based rural informatized assembly library |
| CN110784509A (en) * | 2019-09-16 | 2020-02-11 | 腾讯科技（深圳）有限公司 | Medical information processing method and system and related components |
| CN110995847A (en) * | 2019-12-10 | 2020-04-10 | 南京新贝金服科技有限公司 | Insurance service bus implementation method and system applied to multi-system communication |
| CN111143087A (en) * | 2019-12-18 | 2020-05-12 | 中国平安财产保险股份有限公司 | Interface calling method and device, storage medium and server |
| CN111679810A (en) * | 2020-04-28 | 2020-09-18 | 平安普惠企业管理有限公司 | Method, device, equipment and storage medium for distributing business objects and business standards |
| CN111897527A (en) * | 2020-06-28 | 2020-11-06 | 福建亿能达信息技术股份有限公司 | Hospital equipment budget management system, equipment and medium based on holographic view |
| CN112153152A (en) * | 2020-09-28 | 2020-12-29 | 深圳壹账通智能科技有限公司 | Management method and system of algorithm service interface |
| CN112306585A (en) * | 2020-11-02 | 2021-02-02 | 用友网络科技股份有限公司 | Medical insurance interface data processing method, data processing device and readable storage medium |
| CN112346794A (en) * | 2020-10-21 | 2021-02-09 | 深圳鼎盛电脑科技有限公司 | Interface calling method, device, equipment and medium |
| CN113114646A (en) * | 2021-04-01 | 2021-07-13 | 深圳市腾讯网络信息技术有限公司 | Risk parameter determination method |
-
2021
- 2021-08-03 CN CN202110885462.6A patent/CN113641354A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102622718A (en) * | 2012-04-27 | 2012-08-01 | 南京农业大学 | Web Service-based rural informatized assembly library |
| CN110784509A (en) * | 2019-09-16 | 2020-02-11 | 腾讯科技（深圳）有限公司 | Medical information processing method and system and related components |
| CN110995847A (en) * | 2019-12-10 | 2020-04-10 | 南京新贝金服科技有限公司 | Insurance service bus implementation method and system applied to multi-system communication |
| CN111143087A (en) * | 2019-12-18 | 2020-05-12 | 中国平安财产保险股份有限公司 | Interface calling method and device, storage medium and server |
| CN111679810A (en) * | 2020-04-28 | 2020-09-18 | 平安普惠企业管理有限公司 | Method, device, equipment and storage medium for distributing business objects and business standards |
| CN111897527A (en) * | 2020-06-28 | 2020-11-06 | 福建亿能达信息技术股份有限公司 | Hospital equipment budget management system, equipment and medium based on holographic view |
| CN112153152A (en) * | 2020-09-28 | 2020-12-29 | 深圳壹账通智能科技有限公司 | Management method and system of algorithm service interface |
| CN112346794A (en) * | 2020-10-21 | 2021-02-09 | 深圳鼎盛电脑科技有限公司 | Interface calling method, device, equipment and medium |
| CN112306585A (en) * | 2020-11-02 | 2021-02-02 | 用友网络科技股份有限公司 | Medical insurance interface data processing method, data processing device and readable storage medium |
| CN113114646A (en) * | 2021-04-01 | 2021-07-13 | 深圳市腾讯网络信息技术有限公司 | Risk parameter determination method |
Non-Patent Citations (1)
| Title |
|---|
| 王伟: "基于SOA的居民医保系统设计", 中国优秀硕士学位论文全文数据库, 15 December 2011 (2011-12-15), pages 138 - 545 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114840276A (en) * | 2022-04-15 | 2022-08-02 | 北京百度网讯科技有限公司 | Object calling method, device, equipment, storage medium and program product |
| CN114885026A (en) * | 2022-07-07 | 2022-08-09 | 飞狐信息技术（天津）有限公司 | Data interface request processing system, method, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109213611B (en) | Cross-process communication method, device, terminal and storage medium | |
| CN113641354A (en) | Service data processing method and device, electronic equipment and storage medium | |
| CN109766148B (en) | Method and apparatus for processing interface method calls | |
| CN110727581B (en) | Crash positioning method and electronic equipment | |
| CN110688096B (en) | Method and device for constructing application program containing plug-in, medium and electronic equipment | |
| CN113515271B (en) | Service code generation method and device, electronic equipment and readable storage medium | |
| US7441249B2 (en) | Activity monitoring without accessing a process object | |
| CN112181542A (en) | Function calling method and device, electronic equipment and storage medium | |
| CN113626223A (en) | Interface calling method and device | |
| CN112364109B (en) | Event business association method, system, device, electronic equipment and storage medium | |
| US20090222586A1 (en) | Systems and methods for universal protocol for case management systems | |
| CN111324645B (en) | Block chain data processing method and device | |
| CN114219643A (en) | Transaction calling method, device, equipment and storage medium | |
| CN112261072B (en) | Service calling method, device, equipment and storage medium | |
| CN114579334A (en) | Communication method, communication device, electronic equipment and storage medium | |
| CN113919310A (en) | Short message content determination method and device, electronic equipment and storage medium | |
| CN111930478A (en) | Service calling method and device based on dynamic bytecode | |
| CN111797337A (en) | Method and device for generating export page | |
| US9471341B1 (en) | Optimizing latest user defined class loader | |
| CN109376023B (en) | Method and equipment for generating calling information and issuing return code group | |
| CN112214540B (en) | Data processing method, device, equipment and storage medium | |
| CN114900549A (en) | Message sending method and device, electronic equipment and storage medium | |
| CN118193087A (en) | Interface configuration method, interface configuration device, electronic equipment and storage medium | |
| CN117749780A (en) | Service data reporting method and related equipment | |
| CN117348884A (en) | Data processing method and device, electronic equipment and computer readable 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 |