WO2019136800A1

WO2019136800A1 - Service processing method, apparatus and device, and computer-readable storage medium

Info

Publication number: WO2019136800A1
Application number: PCT/CN2018/077139
Authority: WO
Inventors: 罗先贤; 龙觉刚; 孙成; 叶俊锋; 赖云辉
Original assignee: 平安科技（深圳）有限公司
Priority date: 2018-01-09
Filing date: 2018-02-24
Publication date: 2019-07-18
Also published as: CN108196879A

Abstract

Provided are a service processing method, apparatus and device, and a computer-readable storage medium. The implementation of the service processing method only requires developing an interface, configuring a corresponding configuration file for the interface, allocating a service ID to each type of services, and after the interface receives a service request, being able to determine, according to a service ID of the service request, which type of services the service request belongs to, such that the processing of the service request is realized by invoking a corresponding processing method according to the configuration content, in the configuration file, of the type of services. By means of the method, apparatus, device and computer-readable storage medium of the present application, processing processes of all types of services are realized in the same interface, and there is no need to allocate different interfaces for different types of services, thereby preventing the redundancy and disorder of interfaces and facilitating the management of the interfaces. Furthermore, for a newly added type of services, only corresponding configuration content needs to be added to a configuration file so as to newly add a corresponding processing method for an interface, thereby facilitating the expansion of the interface.

Description

Business processing method, device, device and computer readable storage medium

The present application claims priority to Chinese Patent Application No. 201810019635.4, filed on Jan. 9, 2018, the entire disclosure of which is incorporated herein by reference. The citations are incorporated herein by reference.

Technical field

The present application relates to the field of computer technologies, and in particular, to a service processing method, apparatus, device, and computer readable storage medium.

Background technique

In order to facilitate the development of the business, many financial companies currently use financial apps to conduct business. Generally, there are many types of business in a company. Therefore, the business to be carried out by financial apps must include various types. For example, the front end of mortgage mortgage APP A variety of business requests can be made, such as: order task exception handling return store submission, location tracking order, get customer service agent list, get message details, get message list, get latest unread messages and tasks, get task details, get affected Task list, login verification, replenishment information, submission appointment time, task assignment, task node step submission, order reassignment, node file information submission, submission file upload, etc.

If a request interface is written for each type of service, and the service parameters are transmitted for different service requests, correspondingly, multiple package objects need to be created, and then each interface is separately processed in response to the corresponding service request, so that each additional service is added. The request needs to increase the development of an interface, increase the workload of interface development, and too many interfaces will make the interface more confusing and inconvenient to manage.

Summary of the invention

The embodiment of the present application provides a service processing method, device, device, and computer readable storage medium, which can process different types of services through the same interface.

In a first aspect, the embodiment of the present application provides a service processing method, where the method includes: receiving, by an interface, a service request initiated by a user, where the data carried by the service request includes a service parameter, a user ID, and a service ID of an identifier type; The content of the latest configuration file corresponding to the interface, the content includes a service ID that identifies a different type of service, and first attribute information and second attribute information of the corresponding type of service; and converts the data carried by the service request into a JSONObject object Obtaining a service ID and a user ID of the service request from the JSONObject object; acquiring corresponding first attribute information from the content according to the service ID, and obtaining the location from the JSONObject object according to the first attribute information; Determining a service parameter that is required to be delivered by the service request; determining whether the user ID that sends the service request has an operation authority for the type of service; and if the user ID has an operation authority for the type of service, according to the service ID The second attribute information invokes a corresponding processing method to process the required delivery of the service parameter.

In a second aspect, the embodiment of the present application further provides a service processing apparatus, where the apparatus includes a unit for executing the foregoing service processing method.

In a third aspect, the embodiment of the present application further provides a service processing device, where the device includes a memory, and a processor connected to the memory, and the memory is configured to store program data for implementing a service processing method; And a processor for executing program data stored in the memory to perform the method as described in the first aspect above.

In a fourth aspect, an embodiment of the present application provides a computer readable storage medium, where the one or more program data is stored, and the one or more program data may be processed by one or more processes. The apparatus is executed to implement the method described in the first aspect above.

The embodiment of the present application provides a service processing method, apparatus, device, and computer readable storage medium. By implementing the service processing method of the present application, only one interface needs to be developed, and a corresponding configuration file is configured for the interface, and each type is configured. The service is assigned a service ID. After receiving the service request, the interface can determine, according to the service ID of the service request, which type of service the service request belongs to, and then invoke the corresponding processing method according to the configuration content of the medium type service in the configuration file. To implement the processing of the service request, the method, the device, the device and the computer readable storage medium of the present application implement the processing of all types of services in the same interface, and do not need to allocate different interfaces for different types of services. To avoid excessive and confusing interfaces, it is convenient to manage the interface. For a new type of service, you only need to add the corresponding configuration content to the configuration file, and add a new processing method for the unified interface to facilitate the expansion of the interface.

DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the description of the embodiments will be briefly described below. Obviously, the drawings in the following description are some embodiments of the present application, For the ordinary technicians, other drawings can be obtained based on these drawings without any creative work.

1 is a schematic flowchart of a service processing method according to an embodiment of the present application;

2 is a schematic diagram of a sub-flow of a service processing method according to an embodiment of the present application;

FIG. 3 is a schematic diagram of another sub-process of a service processing method according to an embodiment of the present application;

4 is a schematic diagram of another sub-process of a service processing method according to an embodiment of the present application;

FIG. 5 is a schematic diagram of another sub-process of a service processing method according to an embodiment of the present disclosure;

FIG. 6 is a schematic block diagram showing a unit structure of a service processing apparatus according to an embodiment of the present disclosure;

7 is a schematic block diagram showing a subunit structure of a service processing apparatus according to an embodiment of the present application;

FIG. 8 is a schematic block diagram showing another subunit structure of a service processing apparatus according to an embodiment of the present application; FIG.

FIG. 9 is a schematic block diagram showing another subunit structure of a service processing apparatus according to an embodiment of the present application; FIG.

FIG. 10 is a schematic block diagram of a service processing device according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments.

FIG. 1 is a schematic flowchart of a service processing method according to an embodiment of the present application. The method can run on smart devices such as tablets, laptops, and smart terminals. As shown in FIG. 1, the steps of the method include S101 to S107.

S101: Receive a service request initiated by a user by using an interface, where the data carried by the service request includes a service parameter, a user ID, and a service ID of the identifier type.

The development staff develops an interface that is associated with the APP front end to implement the service request and processing of the APP front-end user. When the interface is developed, a configuration file is configured for the interface, and the configuration file includes the configuration content of the type of service that can be implemented, and finally the processing of the service request is passed.

S102. Acquire the content of the latest configuration file corresponding to the interface, where the content includes a service ID that identifies different types of services, and first attribute information and second attribute information of the corresponding type of service.

In the configuration file, the data format of the content configured for each type of service is: <entry key=“prefix.businessInterfaceId.businessAttributeKey”>defaultValue</entry>.

The information of the businessInterfaceId field is the service ID of the type of the service, that is, which service is indicated.

The attribute information of the service includes the first attribute information and the second attribute information, which are embodied in the businessAttributeKey field and the defaultValue field.

The businessAttributeKey field indicates the attribute name of each type of attribute of the service. Some attribute names are customized by the developer, and are consistent with the name of the service parameter to be delivered by the service request, and include the required delivery service parameters defining the service type. The name is the first attribute information, and some attribute names are specified with a uniform name, for example, sqlType (operation type), sqlMap (corresponding execution statement) and other attributes with specific functions, database, or implementation of the business request. Class, etc., for the second attribute information, sqlType and sqlMap are respectively for the database (query, delete, add, etc.) specific operation types and specific execution statements, the implementation class is for other relatively complex business operations. Logic implementation, if the attribute information of sqlType, sqlMap, etc. is included in the configuration parameters of a certain service, the attribute information such as the implementation class name is generally not included.

The defaultValue field indicates the attribute value corresponding to the attribute name of the service, such as sqlType, sqlMap corresponding sqlType value, sqlMap value, sqlMap value is an address ID, this address ID reflects the execution statement of the operation database, such as query statement, delete statement , add statements, and so on.

The defaultValue field corresponds to the default value specified by the storage attribute name (if there is a default value), such as sqlType value, sqlMap value, database name, and the name of the specific implementation class. If there is no default value, the data transmission in the later stage is required. The attribute value corresponding to the other attribute name corresponding to the businessAttributeKey field is read, and the part attribute value is generally a service parameter that needs to be delivered in the service request, and these service parameters are also parameters that need to be processed in the service request, and are specified by the specified implementation. Class or operation statement of the operation database to implement processing of business parameters.

In this embodiment, an interface can process different types of services. When a new type of service is added, only the corresponding configuration content needs to be added to the service in the configuration file. Therefore, to prevent the interface. The received service request does not have a new type of service, and the original configuration file does not have a corresponding configuration content. Each time a service request is received, the content of the latest configuration file needs to be obtained. The configuration file is saved in the local area of the terminal. The content of the obtained configuration file is saved in the Map collection of the service processing system. Each time a service request is received, it is determined whether the configuration file saved locally by the terminal is modified after the last service processing. If the file has not been modified since the last business process, you do not need to re-read the contents of the configuration file. If the configuration file has been modified since the last business process, you need to re-read the contents of the configuration file to replace the saved in the Map collection. The contents of the original configuration file.

The data format of each service of the Map collection is:

Map<String business,Map<String attribute,String defaultValue>

The String business field is the service ID read from the configuration file, the String attribute field is the read attribute name, the String defaultValue field is the value of the corresponding attribute name, and some are system default values, such as sqlType value, sqlMap value, and some The non-system default value is the service parameter that is read from the service request when the service request is post-processed. For example, if the name of the service parameter is read from the configuration file, the service parameter corresponding to the parameter name in the service request is obtained. value.

Specifically, as shown in FIG. 2, the step of acquiring the content of the latest configuration file corresponding to the interface in step S102 includes the following sub-steps:

S1021: Determine whether the configuration file corresponding to the interface stored in the terminal is modified after the last service request processing ends.

S1022. If yes, reading the content of the configuration file replaces the original content in the Map set as the content of the latest configuration file corresponding to the interface.

S1023. If no, the content stored in the Map set is read as the content of the latest configuration file corresponding to the interface.

If the configuration file has not been modified, the content of the configuration file saved in the Map collection is the content of the latest configuration file. Otherwise, the content of the modified configuration file needs to be read again to replace the content of the original configuration file.

It is determined whether the content of the configuration file saved in the Map collection needs to be updated by determining whether the configuration file is modified. If the configuration file is not modified, the update is not required, and the content of the Map collection needs to be updated every time the service request is received.

Specifically, as shown in FIG. 3, step S1021 includes the following sub-steps:

S10211: The modification time of the configuration file corresponding to the interface saved locally by the terminal is read.

S10212: Compare the currently read modification time with the modification time of the last read configuration file.

S10213, if the currently read modification time is consistent with the modification time of the last read configuration file, determining that the content of the configuration file is not modified; if the currently read modification time is the last read If the modification time of the configuration file is inconsistent, it is determined that the content of the configuration file has been modified.

Each time the service processing system receives the service request, it needs to read the modification time (that is, the latest modification time) of the configuration file saved locally in the terminal, and the modification time read each time is saved in the service processing system. In the middle, the modification time currently read and the modification time read last time (when the service request was last received), if the two are consistent, the configuration file has not been modified since the last business processing, otherwise Has been modified.

S103. Convert the data carried by the service request into a JSONObject object.

The data of the JSONObject object can be {"key1": value1, "key2", value2....}, and a value (value) corresponds to a key (field). It is very convenient to extract the value of a corresponding field in the JSONObject object. of. The Key corresponds to the name of the service parameter in the service request, and the value corresponds to the specific service parameter.

The key in the JSONObject object must be in the form of a string, so you need to convert the business request to a string and then convert the string to a JSONObject object.

S104. Obtain a service ID and a user ID of the service request from a JSONObject object.

The JSONObject object contains all the parameters of the business request, so the business ID and user ID can be in it.

The user ID is used to indicate the identity of the user, and the service ID is used to identify which type of service the service being requested by the current service is.

S105. Acquire corresponding first attribute information from the content according to the service ID, and obtain, according to the first attribute information, a service parameter that is required to be delivered by the service request from the JSONObject object.

For the service request of each type of service, the service parameters required for the type are defined in the configuration file, and the service parameters that do not need to be transmitted need not be obtained, and the name of the service parameter to be delivered is specified in the configuration file. When processing a service request, the corresponding service parameters are required. Therefore, the corresponding value, that is, the service parameter, is obtained by defining the name of the service parameter to be delivered in the configuration file.

As shown in FIG. 4, step S105 includes the following sub-steps:

S1051: Search for the configuration content of the service ID corresponding type service from the content, and obtain a name of the service parameter to be delivered from the configuration content.

S1052: Obtain a service parameter corresponding to the name of the service parameter from the JSONObject object.

The obtained service parameter is temporarily stored in the information of the String defaultValue field in the Map set, and corresponds to the information of the String attribute field, that is, the Map set includes the service parameters and corresponding processing methods that need to be transmitted by the service ID.

S106. Determine whether the user ID that sends the service request has an operation right for the type of service.

The user ID is used to verify the identity of the user, and only users with operational rights can perform operations of this type of service.

S107. If the user ID has an operation authority for the type of service, the corresponding processing method is invoked according to the second attribute information of the service ID to process the required service parameter.

So far, the attribute information in the Map set corresponding to the service request includes the service parameters to be delivered, the name of the database, and the corresponding processing method.

Specifically, as shown in FIG. 5, step S107 includes the following sub-steps:

S1071: Determine whether the second attribute information includes a sqlType field and an sqlMap field.

S1072, if yes, obtaining a sqlType value corresponding to the service ID and an sqlMap value, where the sqlType value maps an operation type of the database, and the sqlMap value maps an execution statement of the operation type;

S1073. Perform, by using the execution statement, an operation corresponding to the operation type on data matching the service parameter in the database.

S1074. If no, determine whether the implementation class name is included in the second attribute information.

S1075. If the second attribute information includes an implementation class name, obtain a loading object corresponding to the implementation class name, and call a processing method corresponding to the loading object to process the service parameter.

The corresponding type of operation is performed on the database through the corresponding execution statement. For example, the sqlType value is “DEL”, that is, the service parameter in the database is deleted by using the delete statement corresponding to the sqlMap value, or the load object is loaded by loading the implementation class, and the object is loaded. There is a corresponding processing program for processing the business parameter, and the business parameter is processed by executing the processing program. After processing the service request, the service parameters read from the service request and temporarily stored in the Map collection are cleared, and the processing result is returned to the user.

The processing method of the embodiment of the present application also configures an interface, and the processing of the service request for all service types is implemented in the interface through a configuration file, and the corresponding processing method is invoked according to different request services in the configuration file. To achieve different business requests; for a new service request, add the corresponding configuration content in the configuration file, and then add an implementation class or processing method for the interface, which is convenient to expand; It is convenient to see which business requests are implemented by the interface and it is convenient to manage.

FIG. 6 is a schematic block diagram of a service processing apparatus 100 according to an embodiment of the present application. The service processing apparatus 100 includes a receiving unit 101, a first obtaining unit 102, a converting unit 103, a second obtaining unit 104, a third obtaining unit 105, a judging unit 106, and a processing unit 107.

The receiving unit 101 is configured to receive a service request initiated by the user by using an interface, where the data carried by the service request includes a service parameter, a user ID, and a service ID of the identifier type.

The first obtaining unit 102 is configured to acquire the content of the latest configuration file corresponding to the interface, where the content includes a service ID that identifies different types of services, and first attribute information and second attribute information of the corresponding type of service.

The converting unit 103 is configured to convert the data carried by the service request into a JSONObject object.

The second obtaining unit 104 is configured to obtain the service ID and the user ID of the service request from the JSONObject object.

The third obtaining unit 105 is configured to obtain corresponding first attribute information from the content according to the service ID, and obtain, according to the first attribute information, a service parameter that is required to be delivered by the service request from the JSONObject object.

The determining unit 106 is configured to determine whether the user ID that sends the service request has an operation right for the type of service.

The processing unit 107 is configured to: if the user ID has an operation authority for the type of service, invoke a corresponding processing method to process the required service parameter according to the second attribute information of the service ID.

In the embodiment of the present application, the configuration file is saved locally in the terminal, and the content of the obtained configuration file is saved in the Map collection.

As shown in FIG. 7, the first obtaining unit 102 includes:

The first determining sub-unit 1021 is configured to determine whether the configuration file corresponding to the interface stored in the terminal is modified after the last service request processing ends;

The first reading sub-unit 1022 is configured to: if modified, read the content of the configuration file to replace the original content in the Map set as the content of the latest configuration file corresponding to the interface.

The confirmation subunit 1023 is configured to read the content saved in the Map set as the content of the latest configuration file corresponding to the interface if not modified.

The first determining sub-unit 1021 is specifically configured to compare the currently read modification time with the modification time of the last read configuration file; if the currently read modification time is the last read If the modification time of the configuration file is consistent, it is determined that the content of the configuration file is not modified; if the currently modified modification time is inconsistent with the modification time of the last read configuration file, it is determined that the content of the configuration file has been modified.

The first attribute information includes a name of a service parameter to be delivered.

As shown in FIG. 8, the third obtaining unit 105 includes:

Searching for a subunit for searching for configuration content of the service corresponding to the service ID from the content.

The first obtaining subunit 1051 is configured to obtain, from the configuration content, a name of a service parameter that needs to be delivered.

The second obtaining sub-unit 1052 is configured to obtain a service parameter corresponding to the name of the service parameter from the JSONObject object.

The second attribute information includes a name of a database.

As shown in FIG. 9, the processing unit 107 includes:

The second determining sub-unit 1071 is configured to determine whether the second attribute information includes a sqlType field and an sqlMap field.

The third obtaining sub-unit 1072 is configured to: if the second attribute information includes a sqlType field and an sqlMap field, obtain an sqlType value and an sqlMap value corresponding to the service ID, where the sqlType value maps an operation type of the database, The sqlMap value maps an execution statement of the operation type.

The operation subunit 1073 is configured to perform, by using the execution statement, an operation corresponding to the operation type on data matching the service parameter in the database.

The third determining sub-unit 1074 is configured to determine, if the second attribute information does not include the sqlType field and the sqlMap field, whether the second attribute information includes an implementation class name.

The processing sub-unit 1075 is configured to: if the second attribute information includes an implementation class name, acquire a loading object corresponding to the implementation class name, and call a processing method corresponding to the loading object to process the service parameter.

For specific implementations of the foregoing various units, reference may be made to the method embodiments, which are not described herein.

The above business processing apparatus 100 can be implemented in the form of a computer program that can be run on a computer device as shown in FIG.

FIG. 10 is a schematic block diagram of a service processing device according to an embodiment of the present application. The device may be a terminal or a server, wherein the terminal may be a communication-enabled electronic device such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant, and a wearable device. The server can be a standalone server or a server cluster consisting of multiple servers.

The device is a computer device 200 comprising a processor 202 connected by a system bus 201, a non-volatile storage medium 203, an internal memory 204, and a network interface 205. The non-volatile storage medium 203 of the computer device 200 can store an operating system 2031 and a computer program 2032. When the computer program 2032 is executed, the processor 202 can be caused to execute a service processing method. The processor 202 of the computer device 200 is used to provide computing and control capabilities to support the operation of the entire computer device 200. The internal memory 204 provides an environment for the operation of the computer program 2032 in the non-volatile storage medium 203, which when executed by the processor 202, causes the processor 202 to perform a business processing method. The network interface 205 of the computer device 200 is used to perform network communications, such as sending assigned tasks and the like. It will be understood by those skilled in the art that the structure shown in FIG. 10 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied. The specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.

The processor 202 can execute an implementation of all of the above described business processing methods when the computer program 2032 in the non-volatile storage medium 203 is run.

The application further provides a computer readable storage medium storing one or more programs, the one or more programs being executable by one or more processors, when the one or More than one program is executed by one or more processors to implement all of the embodiments of the above described business processing methods.

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any equivalents can be easily conceived by those skilled in the art within the technical scope disclosed in the present application. Modifications or substitutions are intended to be included within the scope of the present application. Therefore, the scope of protection of this application should be determined by the scope of protection of the claims.

Claims

A service processing method, comprising:

Receiving, by the interface, a service request initiated by the user, where the data carried by the service request includes a service parameter, a user ID, and a service ID of the identifier type;

Acquiring the content of the latest configuration file corresponding to the interface, where the content includes a service ID that identifies different types of services, and first attribute information and second attribute information of the corresponding type of service;

Converting data carried by the business request into a JSONObject object;

Obtaining a service ID and a user ID of the service request from a JSONObject object;

Obtaining corresponding first attribute information from the content according to the service ID, and acquiring, according to the first attribute information, a service parameter that is required to be delivered by the service request from the JSONObject object;

Determining whether the user ID that sends the service request has an operation right for the type of service;

If the user ID has an operation authority for the type of service, the corresponding processing method is invoked according to the second attribute information of the service ID to process the required service parameter.
The service processing method according to claim 1, wherein the configuration file is saved locally in the terminal, and the content of the acquired configuration file is saved in the Map collection;

The acquiring the content of the latest configuration file corresponding to the interface includes:

Determining whether the configuration file corresponding to the interface saved in the terminal is modified after the last service request processing ends;

If yes, reading the content of the configuration file replaces the original content in the Map set as the content of the latest configuration file corresponding to the interface;

If not, the content saved in the Map set is read as the content of the latest configuration file corresponding to the interface.
The service processing method according to claim 2, wherein the determining whether the configuration file corresponding to the interface stored in the terminal is modified after the last service request processing ends includes:

Reading the modification time of the configuration file corresponding to the interface saved locally by the terminal;

Comparing the currently read modification time with the modification time of the last read configuration file;

If the currently read modification time is consistent with the modification time of the last read configuration file, it is determined that the content of the configuration file is not modified; if the currently read modification time and the last read configuration If the modification time of the file is inconsistent, it is determined that the content of the configuration file has been modified.
The service processing method according to claim 1, wherein the first attribute information includes a name of a service parameter to be delivered;

Obtaining the corresponding first attribute information from the content according to the service ID, and acquiring the service parameter that is required to be delivered by the service request from the JSONObject object according to the first attribute information, including:

Searching, from the content, the configuration content of the service corresponding to the service ID, and obtaining the name of the service parameter to be delivered from the configuration content;

Obtaining a service parameter corresponding to the name of the service parameter from the JSONObject object.
The service processing method according to claim 1, wherein the second attribute information includes a name of a database;

The invoking the corresponding processing method according to the second attribute information of the service ID to process the required delivery service parameter, including:

Determining whether the second attribute information includes a sqlType field and an sqlMap field;

If the second attribute information includes a sqlType field and an sqlMap field, the sqlType value and the sqlMap value corresponding to the service ID are obtained, the sqlType value mapping operates an operation type of the database, and the sqlMap value maps the operation type Execution statement;

The operation corresponding to the operation type is performed on the data in the database that matches the service parameter by using the execution statement.
The service processing method according to claim 5, wherein the invoking a corresponding processing method according to the second attribute information of the service ID to process the required delivery service parameter further includes:

If the second attribute information does not include the sqlType field and the sqlMap field, determine whether the second attribute information includes an implementation class name;

If the second attribute information includes an implementation class name, the loading object corresponding to the implementation class name is obtained, and the processing method corresponding to the loading object is invoked to process the service parameter.
A service processing device, comprising:

a receiving unit, configured to receive, by using an interface, a service request initiated by a user, where the data carried by the service request includes a service parameter, a user ID, and a service ID of an identifier type;

a first acquiring unit, configured to acquire content of a latest configuration file corresponding to the interface, where the content includes a service ID that identifies a different type of service, and first attribute information and second attribute information of a service of a corresponding type;

a converting unit, configured to convert data carried by the service request into a JSONObject object;

a second obtaining unit, configured to obtain a service ID and a user ID of the service request from the JSONObject object;

a third acquiring unit, configured to acquire corresponding first attribute information from the content according to the service ID, and configured to acquire, according to the first attribute information, a service that is required to be delivered by the service request from the JSONObject object parameter;

a determining unit, configured to determine whether the user ID that sends the service request has an operation right for the type of service;

The processing unit is configured to: if the user ID has an operation authority for the type of service, invoke a corresponding processing method to process the required service parameter according to the second attribute information of the service ID.
The service processing apparatus according to claim 7, wherein the configuration file is saved locally in the terminal, and the content of the acquired configuration file is saved in the Map collection;

The first acquiring unit includes:

a first determining sub-unit, configured to determine whether the configuration file corresponding to the interface saved in the terminal is modified after the last service request processing ends;

a first reading subunit, configured to: if the configuration file corresponding to the interface stored in the terminal is modified after the last service request processing ends, read the content of the configuration file to replace the original in the Map set. The content of the content as the content of the latest configuration file corresponding to the interface;

a confirmation subunit, configured to read, if the configuration file corresponding to the interface stored in the terminal is not modified after the last service request processing ends, read the content saved in the Map set as the latest corresponding to the interface The contents of the configuration file.
The service processing apparatus according to claim 8, wherein the first determining sub-unit is specifically configured to compare the currently read modification time with a modification time of a configuration file read last time; If the modification time currently read is consistent with the modification time of the configuration file read last time, it is determined that the content of the configuration file is not modified; if the modification time currently read and the configuration file read last time If the modification time is inconsistent, it is determined that the content of the configuration file has been modified.
The service processing apparatus according to claim 7, wherein said first attribute information includes a name of a service parameter to be delivered;

The third obtaining unit includes:

Searching a subunit, configured to search, from the content, configuration content of the service corresponding to the service ID;

a first obtaining subunit, configured to obtain, from the configuration content, a name of a service parameter that needs to be delivered;

And a second obtaining subunit, configured to obtain a service parameter corresponding to the name of the service parameter from the JSONObject object.
The service processing apparatus according to claim 7, wherein the second attribute information includes a name of a database;

The processing unit includes:

a second determining subunit, configured to determine whether the second attribute information includes a sqlType field and an sqlMap field;

a third obtaining subunit, configured to: if the second attribute information includes a sqlType field and an sqlMap field, obtain a sqlType value and an sqlMap value corresponding to the service ID, where the sqlType value maps an operation type of the database, The sqlMap value maps the execution statement of the operation type;

An operation subunit, configured to perform, by using the execution statement, an operation corresponding to the operation type on data matching the service parameter in the database;

a third determining subunit, configured to: if the second attribute information does not include the sqlType field and the sqlMap field, determine whether the second attribute information includes an implementation class name;

The processing subunit is configured to: if the second attribute information includes an implementation class name, obtain a loading object corresponding to the implementation class name, and call a processing method corresponding to the loading object to process the service parameter.
A service processing device, characterized in that the device comprises a memory, and a processor connected to the memory;

The memory is configured to store service processor data;

The processor is configured to execute program data stored in the memory to perform: the following steps:

Receiving, by the interface, a service request initiated by the user, where the data carried by the service request includes a service parameter, a user ID, and a service ID of the identifier type;

Acquiring the content of the latest configuration file corresponding to the interface, where the content includes a service ID that identifies different types of services, and first attribute information and second attribute information of the corresponding type of service;

Converting data carried by the business request into a JSONObject object;

Obtaining a service ID and a user ID of the service request from a JSONObject object;

Obtaining corresponding first attribute information from the content according to the service ID, and acquiring, according to the first attribute information, a service parameter that is required to be delivered by the service request from the JSONObject object;

Determining whether the user ID that sends the service request has an operation right for the type of service;

If the user ID has an operation authority for the type of service, the corresponding processing method is invoked according to the second attribute information of the service ID to process the required service parameter.
The service processing device according to claim 12, wherein the configuration file is saved locally in the terminal, and the content of the acquired configuration file is saved in the Map collection;

Performing the following steps in the step of performing the obtaining the content of the latest configuration file corresponding to the interface:

Determining whether the configuration file corresponding to the interface saved in the terminal is modified after the last service request processing ends;

If yes, reading the content of the configuration file replaces the original content in the Map set as the content of the latest configuration file corresponding to the interface;

If not, the content saved in the Map set is read as the content of the latest configuration file corresponding to the interface.
The service processing device according to claim 13, wherein the step of performing the determining whether the configuration file corresponding to the interface stored in the terminal is modified after the last service request processing is completed is performed in the following steps. :

Reading the modification time of the configuration file corresponding to the interface saved locally by the terminal;

Comparing the currently read modification time with the modification time of the last read configuration file;

If the currently read modification time is consistent with the modification time of the last read configuration file, it is determined that the content of the configuration file is not modified; if the currently read modification time and the last read configuration If the modification time of the file is inconsistent, it is determined that the content of the configuration file has been modified.
The service processing device according to claim 12, wherein said first attribute information comprises a name of a service parameter to be delivered;

And executing, in the step of acquiring, according to the service ID, the corresponding first attribute information from the content, and acquiring, according to the first attribute information, a service parameter that is required to be delivered by the service request from the JSONObject object Perform the following steps:

Searching, from the content, the configuration content of the service corresponding to the service ID, and obtaining the name of the service parameter to be delivered from the configuration content;

Obtaining a service parameter corresponding to the name of the service parameter from the JSONObject object.
The service processing device according to claim 12, wherein said second attribute information comprises a name of a database;

And performing the following steps in the step of executing the processing parameter that is required to be processed according to the second attribute information of the service ID to process the required delivery:

Determining whether the second attribute information includes a sqlType field and an sqlMap field;

If the second attribute information includes a sqlType field and an sqlMap field, the sqlType value and the sqlMap value corresponding to the service ID are obtained, the sqlType value mapping operates an operation type of the database, and the sqlMap value maps the operation type Execution statement;

Performing, by using the execution statement, an operation corresponding to the operation type on data matching the service parameter in the database;

If the second attribute information does not include the sqlType field and the sqlMap field, determine whether the second attribute information includes an implementation class name;

If the second attribute information includes an implementation class name, the loading object corresponding to the implementation class name is obtained, and the processing method corresponding to the loading object is invoked to process the service parameter.
A computer readable storage medium, wherein the computer readable storage medium stores one or more program data, the one or more program data being executable by one or more processors to implement the following step:

Receiving, by the interface, a service request initiated by the user, where the data carried by the service request includes a service parameter, a user ID, and a service ID of the identifier type;

Acquiring the content of the latest configuration file corresponding to the interface, where the content includes a service ID that identifies different types of services, and first attribute information and second attribute information of the corresponding type of service;

Converting data carried by the business request into a JSONObject object;

Obtaining a service ID and a user ID of the service request from a JSONObject object;

Obtaining corresponding first attribute information from the content according to the service ID, and acquiring, according to the first attribute information, a service parameter that is required to be delivered by the service request from the JSONObject object;

Determining whether the user ID that sends the service request has an operation right for the type of service;

If the user ID has an operation authority for the type of service, the corresponding processing method is invoked according to the second attribute information of the service ID to process the required service parameter.
The computer readable storage medium according to claim 17, wherein the configuration file is saved locally in the terminal, and the content of the acquired configuration file is saved in the Map collection;

Performing the following steps in the step of implementing the content of acquiring the latest configuration file corresponding to the interface:

Determining whether the configuration file corresponding to the interface saved in the terminal is modified after the last service request processing ends;

If yes, reading the content of the configuration file replaces the original content in the Map set as the content of the latest configuration file corresponding to the interface;

If not, the content saved in the Map set is read as the content of the latest configuration file corresponding to the interface.
The computer readable storage medium of claim 17, wherein the first attribute information comprises a name of a service parameter to be delivered;

Determining, in the step of obtaining the corresponding first attribute information from the content according to the service ID, obtaining the service parameter required to be delivered by the service request from the JSONObject object according to the first attribute information Perform the following steps:

Searching, from the content, the configuration content of the service corresponding to the service ID, and obtaining the name of the service parameter to be delivered from the configuration content;

Obtaining a service parameter corresponding to the name of the service parameter from the JSONObject object.
The service processing device according to claim 17, wherein said second attribute information comprises a name of a database;

Performing the following steps in the step of implementing the processing method that is required to process the required delivery according to the second attribute information of the service ID:

Determining whether the second attribute information includes a sqlType field and an sqlMap field;

If the second attribute information includes a sqlType field and an sqlMap field, the sqlType value and the sqlMap value corresponding to the service ID are obtained, the sqlType value mapping operates an operation type of the database, and the sqlMap value maps the operation type Execution statement;

Performing, by using the execution statement, an operation corresponding to the operation type on data matching the service parameter in the database;

If the second attribute information does not include the sqlType field and the sqlMap field, determine whether the second attribute information includes an implementation class name;

If the second attribute information includes an implementation class name, the loading object corresponding to the implementation class name is obtained, and the processing method corresponding to the loading object is invoked to process the service parameter.