Disclosure of Invention
The application provides a service processing method, device, equipment and storage medium, which are used for solving the problem of token information resource waste caused by carrying token information corresponding to a service in a service request sent to a server.
In a first aspect, the present application provides a service processing method, including:
sending an authentication request to a service server;
receiving token information returned by the service server according to the authentication request;
in a preset period, at least two service requests are sent to a service server, wherein the at least two service requests comprise token information;
and respectively receiving service processing results corresponding to at least two service requests returned by the service server.
In some embodiments, sending at least two service requests to a service server includes:
acquiring respective service identifiers of at least two to-be-processed services;
determining whether the at least two to-be-processed services are the services of the service server according to the respective service identifiers of the at least two to-be-processed services;
and if the at least two to-be-processed services are the services of the service server, sending at least two service requests to the service server.
In some embodiments, sending at least two service requests to a service server includes:
acquiring token information corresponding to a service server;
and sending at least two service requests to a service server according to the token information and the service identifiers of at least two services to be processed.
In some embodiments, sending at least two service requests to the service server according to the token information and the service identifier of each of the at least two services to be processed includes:
determining configuration parameters corresponding to each service to be processed according to the service identifiers of at least two services to be processed;
generating service requests corresponding to the services to be processed according to the configuration parameters and token information corresponding to the services to be processed;
at least two service requests are sent to a service server.
In some embodiments, the method further comprises:
if the service processing result is invalid content, sending an authentication request to the service server again to acquire new token information.
In some embodiments, resending the authentication request to the business server to obtain new token information includes:
and re-sending an authentication request to the service server according to a preset control flow so as to acquire new token information, wherein the control flow is set on the basis of a visualized low-code development platform LCDP.
In a second aspect, the present application provides a service processing method, including:
receiving an authentication request sent by a terminal device;
according to the authentication request, transmitting token information to the terminal equipment;
receiving at least two service requests sent by terminal equipment, wherein the at least two service requests comprise token information;
and processing at least two service requests respectively to obtain service processing results corresponding to the service requests, and sending the service processing results corresponding to the service requests to the terminal equipment.
In some embodiments, processing at least two service requests respectively to obtain service processing results corresponding to the service requests includes:
judging whether at least two service requests are received within a preset period of time;
and if the at least two service requests are received in the preset period, respectively processing the at least two service requests to obtain service processing results corresponding to the service requests.
In some embodiments, the method further comprises:
and receiving the authentication request sent by the terminal equipment again, and sending new token information to the terminal equipment again according to the authentication request, wherein the authentication request received again is sent by the terminal equipment when the service processing result is determined to be invalid content.
In a third aspect, the present application provides a service processing apparatus, including:
the sending module is used for sending an authentication request to the service server;
the receiving module is used for receiving token information returned by the service server according to the authentication request;
the sending module is further used for sending at least two service requests to the service server in a preset period, wherein the at least two service requests comprise token information;
and the receiving module is also used for respectively receiving service processing results corresponding to the at least two service requests returned by the service server.
In some embodiments, the sending module is further specifically configured to:
acquiring respective service identifiers of at least two to-be-processed services;
determining whether the at least two to-be-processed services are the services of the service server according to the respective service identifiers of the at least two to-be-processed services;
and if the at least two to-be-processed services are the services of the service server, sending at least two service requests to the service server.
In some embodiments, the sending module is further specifically configured to:
acquiring token information corresponding to a service server;
and sending at least two service requests to a service server according to the token information and the service identifiers of at least two services to be processed.
In some embodiments, the sending module is further specifically configured to:
determining configuration parameters corresponding to each service to be processed according to the service identifiers of at least two services to be processed;
generating service requests corresponding to the services to be processed according to the configuration parameters and token information corresponding to the services to be processed;
at least two service requests are sent to a service server.
In some embodiments, the sending module is further specifically configured to:
if the service processing result is invalid content, sending an authentication request to the service server again to acquire new token information.
In some embodiments, the sending module is further specifically configured to:
and re-sending an authentication request to the service server according to a preset control flow so as to acquire new token information, wherein the control flow is set on the basis of a visualized low-code development platform LCDP.
In a fourth aspect, the present application provides a service processing apparatus, including:
the receiving module is used for receiving an authentication request sent by the terminal equipment;
the sending module is used for sending token information to the terminal equipment according to the authentication request;
the receiving module is used for receiving at least two service requests sent by the terminal equipment, wherein the at least two service requests comprise token information;
the processing module is used for respectively processing at least two service requests to obtain service processing results corresponding to the service requests;
and the sending module is used for sending the service processing results corresponding to the service requests to the terminal equipment.
In some embodiments, the processing module is specifically configured to:
judging whether at least two service requests are received within a preset period of time;
and if the at least two service requests are received in the preset period, respectively processing the at least two service requests to obtain service processing results corresponding to the service requests.
In some embodiments, the receiving module is further configured to receive, again, an authentication request sent by the terminal device;
and the sending module is also used for sending new token information to the terminal equipment again according to the authentication request, wherein the received authentication request is sent by the terminal equipment when the service processing result is determined to be invalid content.
In a fifth aspect, the present application provides a terminal device, including: a processor, a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the method as in any of the first aspects.
In a sixth aspect, the present application provides a server, comprising: a processor, a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored in the memory to implement the method as in any of the second aspects.
In a seventh aspect, the present application provides a computer-readable storage medium having stored therein computer-executable instructions which, when executed by a processor, are adapted to carry out the method of any one of the first or second aspects.
In an eighth aspect, the present application provides a computer program product comprising a computer program which, when executed by a processor, implements the method of any one of the first or second aspects.
The embodiment of the application provides a service processing method, device, equipment and storage medium, comprising the following steps: sending an authentication request to a service server; receiving token information returned by the service server according to the authentication request; in a preset period, at least two service requests are sent to a service server, wherein the at least two service requests comprise token information; and respectively receiving service processing results corresponding to at least two service requests returned by the service server. In the method, the service server sends the token information to the terminal equipment according to the authentication request, and the terminal equipment sends at least two service requests to the service server within a preset period, wherein the at least two service requests comprise the token information, so that the waste of token information resources is avoided, and the token information resources are saved.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the accompanying claims.
In the related art, a third party server transmits token information corresponding to a service to an application, and when the application requests the service to the third party server, the token information corresponding to the service needs to be carried in a service request transmitted to the server. Therefore, the third party server can generally provide a plurality of different services, and if an application program requests different services, different token information needs to be carried in the service request, so that token information resources are wasted.
In the present application, in order to save token information resources, the inventor wants to set the token information corresponding to all services provided by the third party server to be the same for each third party server, so that the token information resources are saved.
A specific application scenario of the present application is described below with reference to fig. 1.
Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application. As shown in fig. 1, includes: an application, a plurality of business servers (i.e., third party servers). For example, the plurality of service servers includes a service server 1 and a service server 2.
Each service server is used for providing different services to the application program. For example, service server 1 provides service 1 (e.g., word recognition) and service 2 (e.g., fingerprint recognition) to an application, and service 2 provides service 3, service 4, and service 5 to an application.
And in a preset period, at least two service requests sent to each service server by the application program comprise token information corresponding to the server.
For example, in a preset period, at least two service requests sent by the application program to the service server 1 include token-1 information corresponding to the service server 1.
For example, in the preset period, at least two service requests sent by the application program to the service server 2 include token-2 information corresponding to the service server 2.
In the application, in the preset period, at least two service requests sent by the application program to each server include token information corresponding to the server, so that token information resources can be saved.
The following describes the technical solutions of the present application and how the technical solutions of the present application solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 2 is a flowchart of a service processing method according to an embodiment of the present application. As shown in fig. 2, the method includes:
s201, the terminal equipment sends an authentication request to the service server.
Optionally, the terminal device comprises an application developed by a Low code development platform (Low-Code Development Platform, LCDP).
The terminal device can be, for example, a smart phone, a tablet computer, an intelligent attendance checking device and the like.
External services may be integrated in the application.
The external service is a service provided by a business server.
Optionally, after receiving a triggering operation of the user on at least two pending services, the terminal device sends an authentication request to the service server.
Optionally, the authentication request may include a user name, a password, and the like. For example, the user name and password are determined for installing the above application in the terminal device according to the setting operation of the user.
S202, the service server sends token information to the terminal equipment according to the authentication request.
Optionally, after receiving the authentication request, the service server may verify the authentication request, and if the authentication is passed, send token information to the terminal device.
S203, the terminal equipment sends at least two service requests to the service server within a preset period, wherein the at least two service requests comprise token information.
Optionally, after receiving the token information, the terminal device may store a mapping relationship between the service server and the token information in a preset storage location, where the mapping relationship includes a server identifier of the service server and the token information.
Alternatively, the preset period may be 10 hours, 24 hours, or the like, and the preset period is not limited herein.
Alternatively, at least two service requests may be used to request a different service, or may be used to request the same service.
The token information included in at least two service requests is the same.
S204, the service server processes at least two service requests respectively to obtain service processing results corresponding to the service requests.
S205, the service server sends service processing results corresponding to the service requests to the terminal equipment.
Alternatively, the service processing result may be valid content or invalid content.
For example, the valid content may be a request result corresponding to the service request. For example, when the service request includes a picture, the service request is used for requesting a service for identifying the text in the picture, the effective content may be the text obtained after identifying the text in the picture.
For example, the invalid content may be a preset string (e.g., NULL), or may be other.
Optionally, after receiving the service request, the service server may determine whether the token information in the service request is valid, if the token information is valid, the obtained service processing result is valid content, and if the token information is invalid, the obtained service processing result is invalid content.
Optionally, determining whether the token information in the service request is valid may include: judging whether the service request is received within a preset period of time; if yes, determining that token information in the service request is valid.
Optionally, determining whether the token information in the service request is valid may further include: judging whether the token information is sent to the terminal equipment by the service server or not; if yes, determining that token information in the service request is valid.
In the service processing method provided in the embodiment of fig. 2, the service server sends token information to the terminal device according to the authentication request, and in a preset period, the terminal device sends at least two service requests to the service server, wherein the at least two service requests include token information, so that token information resource waste is avoided, and token information resource is saved.
On the basis of the foregoing embodiment, the service processing method provided in the present application is further described in detail below with reference to fig. 3, and specifically please refer to the embodiment of fig. 3.
Fig. 3 is a second flowchart of a service processing method provided in an embodiment of the present application. As shown in fig. 3, the method includes:
s301, the terminal equipment sends an authentication request to the service server.
Specifically, the execution method of S301 is the same as that of S201, and the execution process of S301 is not described here again.
S302, the service server sends token information to the terminal equipment according to the authentication request.
Specifically, the execution method of S302 is the same as the execution method of S202, and the execution process of S301 is not described here again.
S303, the terminal equipment acquires the service identifiers of at least two to-be-processed services.
In some embodiments, after the terminal device receives the triggering operation on the at least two pending services, the service identifiers of the at least two pending services may be directly obtained.
S304, the terminal equipment determines whether the at least two to-be-processed services are the services of the service server according to the service identifiers of the at least two to-be-processed services.
In some embodiments, a server identifier corresponding to each service identifier may be determined according to respective service identifiers of at least two to-be-processed services and a first preset corresponding relationship;
if the server identifiers corresponding to the service identifiers are the same, determining that at least two to-be-processed services are the services of the service server indicated by the server identifier.
The first preset corresponding relation comprises a plurality of service identifiers and server identifiers corresponding to the service identifiers.
S305, if the terminal equipment determines that at least two to-be-processed services are the services of the service server, at least two service requests are sent to the service server within a preset period, and the at least two service requests comprise token information.
In some embodiments, sending at least two service requests to a service server includes: acquiring token information corresponding to a service server; and sending at least two service requests to a service server according to the token information and the service identifiers of at least two services to be processed.
In some embodiments, obtaining token information corresponding to a business server includes: and acquiring token information corresponding to the service server from a prestored mapping relation according to the server identification.
Optionally, the server identifier may be a server identifier corresponding to each service identifier determined according to respective service identifiers of at least two to-be-processed services and a first preset corresponding relationship.
For an explanation of the mapping relation stored in advance, please refer to S203.
In some embodiments, sending at least two service requests to the service server according to the token information and the service identifier of each of the at least two services to be processed includes:
determining configuration parameters corresponding to each service to be processed according to the service identifiers of at least two services to be processed;
generating service requests corresponding to the services to be processed according to the configuration parameters and token information corresponding to the services to be processed;
at least two service requests are sent to a service server.
In some embodiments, if one of the at least two to-be-processed services is a service of the service server and the other to-be-processed service is not a service of the service server, the service request sent to each service server includes token information corresponding to the service server.
Optionally, the configuration parameters include a request name, a request path (URL), a request header parameter, a request body parameter, a return parameter, and a request description corresponding to the service to be processed.
Optionally, after determining the configuration parameters corresponding to the service to be processed, token information may be added to the request header parameters or the request body parameters, so as to generate a service request corresponding to the service to be processed.
S306, the service server judges whether at least two service requests are received in a preset period.
S307, if the service server determines that at least two service requests are received in the preset period, the service server processes the at least two service requests respectively to obtain service processing results corresponding to the service requests.
In some embodiments, if it is determined that at least two service requests are not received within the preset period, the preset information is determined as a service processing result corresponding to each service request.
S308, the service server sends service processing results corresponding to the service requests to the terminal equipment.
Specifically, the execution method of S308 is the same as that of S205, and the execution process of S308 is not described here again.
S309, the terminal equipment judges whether the service processing result is invalid content.
And S310, if the terminal equipment determines that the service processing result is invalid content, the terminal equipment sends an authentication request to the service server again.
In some embodiments, if the service processing result is a preset string NULL, it is determined that the service processing result is invalid content.
In some embodiments, if the terminal device determines that the service processing result is valid content, the flow is ended.
S311, the service server sends new token information to the terminal equipment again according to the resent authentication request.
The re-received authentication request is sent by the terminal equipment when the service processing result is determined to be invalid content.
Optionally, the process flow after the new token information is sent to the terminal device is referred to in S303-S3011, which will not be described herein.
In the service processing method provided in the embodiment of fig. 3, the terminal device obtains the service identifiers of at least two to-be-processed services, and determines whether the at least two to-be-processed services are the services of the service server according to the service identifiers of the at least two to-be-processed services, if the terminal device determines that the at least two to-be-processed services are the services of the service server, at least two service requests are sent to the service server within a preset period, and the at least two service requests include the same token information, so that token information resources are saved.
In some embodiments, a method of obtaining new token information includes:
and re-sending an authentication request to the service server according to a preset control flow so as to acquire new token information, wherein the control flow is set on the basis of a visualized low-code development platform LCDP.
Fig. 4 is an exemplary interface schematic diagram of a visual configuration control flow provided in this embodiment. As shown in fig. 4, includes: a control flow composed of a plurality of nodes.
For example, the plurality of nodes includes nodes 41-45. Multiple nodes of a node can be obtained by dragging components included in the LCDP
Optionally, lines with directions exist between the nodes, and a circulation condition corresponding to the lines can be set. Wherein the circulation condition is used for indicating that the next step is executed after the previous step meets the corresponding condition.
Optionally, the setting of the circulation condition may be set according to a status code parameter in the service server return parameters, or a relevant logic judgment condition may be added.
Optionally, in the step of acquiring token information, the return parameter obtained after the previous node is executed may be provided to the next node. Alternatively, the return parameter may be encrypted, and the encrypted return parameter may be provided to a subsequent node. The encryption processing may be implemented by an encryption algorithm function of the external service integration platform in the LCDP.
Optionally, service packet configuration may also be performed prior to configuring the control flow.
Fig. 5 is an exemplary interface schematic diagram of a service packet configuration provided in an embodiment of the present application. As shown in fig. 5, the service packet configuration includes: the system comprises a plurality of service groups, a configuration control flow control corresponding to each service group and a configuration service node control.
For example, the plurality of service packets includes service packets 1-4.
Alternatively, the name of each service packet, the location of the token information corresponding to the service packet in the service request (e.g., the request body and the request header), the actual parameter name of the token information, the packet description, and the like may be configured in the service packet configuration.
It should be noted that each service packet corresponds to one service server. The service grouping configuration can be completed through a service grouping management function of an external service integration platform in the LCDP.
Optionally, the external service integration platform further has a service request management function, and a configuration service invocation workflow function (for implementing configuration of control flows).
Optionally, an external service workflow engine and an external service storage module may also be included in the LCDP.
The external service workflow engine is used for monitoring service request call, automatically touching and finding out related judgment, namely processing authentication, updating token information after successful authentication, calling the service request again, and the like.
The external service storage module is used for storing external service analysis and service requests and flow information of external service call.
Alternatively, the interface shown in FIG. 4 may be displayed after receiving a selected operation on the "configure control flow" control of FIG. 5.
In the application, after the positions of the token information corresponding to the service packets in the service requests are configured in the service packet configuration, the positions of the token information in the service requests are directly increased according to the configured positions in the process of generating the service requests corresponding to the services to be processed according to the configuration parameters and the token information corresponding to the services to be processed, so that the service requests can be obtained without repeatedly configuring the positions of the token information in the service requests for each service request. Further, after receiving the token information sent by the service server, the service request can be automatically updated according to the configuration parameters.
Alternatively, after receiving a selection operation corresponding to a certain service group by the user, the interface shown in fig. 6 may be displayed.
Fig. 6 is a schematic diagram of a service function setting interface provided in an embodiment of the present application. As shown in fig. 6, includes: and a plurality of nodes are obtained by clicking the 'add' control. For example, the plurality of nodes includes 41-45.
Optionally, after receiving the selected operation on a certain node, clicking on the "delete" control to implement deletion on the certain node.
Alternatively, after receiving a selection operation of "edit setting" corresponding to a node, a node configuration interface may be displayed in which a request name, a request path, a request header parameter, a request body parameter, a return parameter, a request description, and the like are configured.
The method is characterized in that the addition and deletion of the nodes are realized through a service request management function, and request names, request paths, request header parameters, request body parameters, return parameters, request descriptions and the like are configured.
In the application, the control flow can be set through the visual interface shown in fig. 4-6, so that the flexibility of acquiring the token information is improved, and the token information is automatically updated.
Fig. 7 is a schematic structural diagram of a service processing device according to an embodiment of the present application. The service processing device 10 is applied to a terminal device. As shown in fig. 7, the service processing apparatus 10 includes:
a sending module 101, configured to send an authentication request to a service server;
a receiving module 102, configured to receive token information returned by the service server according to the authentication request;
the sending module 101 is further configured to send at least two service requests to the service server in a preset period, where the at least two service requests include token information;
the receiving module 102 is further configured to receive service processing results corresponding to the at least two service requests, which are returned by the service server, respectively.
The service processing apparatus 10 provided in the embodiment of the present application may execute the service processing method executed by the terminal device, and its implementation principle and beneficial effects are similar, and will not be described herein again.
In some embodiments, the sending module 101 is further specifically configured to:
acquiring respective service identifiers of at least two to-be-processed services;
determining whether the at least two to-be-processed services are the services of the service server according to the respective service identifiers of the at least two to-be-processed services;
and if the at least two to-be-processed services are the services of the service server, sending at least two service requests to the service server.
In some embodiments, the sending module 101 is further specifically configured to:
acquiring token information corresponding to a service server;
and sending at least two service requests to a service server according to the token information and the service identifiers of at least two services to be processed.
In some embodiments, the sending module 101 is further specifically configured to:
determining configuration parameters corresponding to each service to be processed according to the service identifiers of at least two services to be processed;
generating service requests corresponding to the services to be processed according to the configuration parameters and token information corresponding to the services to be processed;
at least two service requests are sent to a service server.
In some embodiments, the sending module is further specifically configured to:
if the service processing result is invalid content, sending an authentication request to the service server again to acquire new token information.
In some embodiments, the sending module 101 is further specifically configured to:
and re-sending an authentication request to the service server according to a preset control flow so as to acquire new token information, wherein the control flow is set on the basis of a visualized low-code development platform LCDP.
The service processing apparatus 10 provided in the embodiment of the present application may execute the service processing method executed by the terminal device, and its implementation principle and beneficial effects are similar, and will not be described herein again.
Fig. 8 is a schematic structural diagram of another service processing apparatus according to an embodiment of the present application. The service processing device 20 is applied to a server. As shown in fig. 8, the service processing apparatus 20 includes:
a receiving module 201, configured to receive an authentication request sent by a terminal device;
a sending module 202, configured to send token information to a terminal device according to an authentication request;
a receiving module 201, configured to receive at least two service requests sent by a terminal device, where the at least two service requests each include token information;
the processing module 203 is configured to process at least two service requests respectively, so as to obtain a service processing result corresponding to each service request;
and the sending module 202 is configured to send a service processing result corresponding to each service request to the terminal device.
The service processing device 20 provided in the embodiment of the present application may execute the service processing method executed by the server, and its implementation principle and beneficial effects are similar, and will not be described herein again.
In some embodiments, the processing module 203 is specifically configured to:
judging whether at least two service requests are received within a preset period of time;
and if the at least two service requests are received in the preset period, respectively processing the at least two service requests to obtain service processing results corresponding to the service requests.
In some embodiments, the receiving module 201 is further configured to receive the authentication request sent by the terminal device again;
the sending module 202 is further configured to resend the new token information to the terminal device according to the authentication request, where the received authentication request is sent by the terminal device when it is determined that the service processing result is invalid content.
The service processing device 20 provided in the embodiment of the present application may execute the service processing method executed by the server, and its implementation principle and beneficial effects are similar, and will not be described herein again.
Fig. 9 is a hardware schematic diagram of a terminal device provided in an embodiment of the present application. As shown in fig. 9, the terminal device 30 may include: a transceiver 301, a memory 302 and a processor 303.
Among other things, transceiver 301 may include: a transmitter and/or a receiver. A transmitter may also be referred to as a transmitter, transmit port, transmit interface, or the like. A receiver may also be referred to as a receiver, receiving port, receiving interface, or the like.
Illustratively, the transceiver 301, the memory 302, and the processor 303 are interconnected by a bus 304.
Memory 302 is used to store computer-executable instructions.
The processor 303 is configured to execute computer-executable instructions stored in the memory 302, so that the processor 303 executes the service processing method executed by the terminal device.
Fig. 10 is a hardware schematic of a server according to an embodiment of the present application. As shown in fig. 10, the server 40 may include: a transceiver 401, a memory 402, and a processor 403.
Wherein the transceiver 401 may include: a transmitter and/or a receiver. A transmitter may also be referred to as a transmitter, transmit port, transmit interface, or the like. A receiver may also be referred to as a receiver, receiving port, receiving interface, or the like.
The transceiver 401, the memory 402, and the processor 403 are illustratively interconnected by a bus 404.
Memory 402 is used to store computer-executable instructions.
The processor 403 is configured to execute the computer-executable instructions stored in the memory 402, so that the processor 403 executes the service processing method executed by the server.
The embodiment of the application provides a computer readable storage medium, wherein computer executable instructions are stored in the computer readable storage medium, and when the computer executable instructions are executed by a processor, the service processing method executed by the terminal device or the server is realized.
The embodiment of the application also provides a computer program product, which comprises a computer program, and the computer program can realize the service processing method executed by the terminal equipment or the server when being executed by a processor.
All or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a readable memory. The program, when executed, performs steps including the method embodiments described above; and the aforementioned memory (storage medium) includes: read-only memory (ROM), RAM, flash memory, hard disk, solid state disk, magnetic tape, floppy disk, optical disk (optical disc), and any combination thereof.
Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various modifications and variations can be made to the embodiments of the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the embodiments of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to encompass such modifications and variations.
In the present application, the term "include" and variations thereof may refer to non-limiting inclusion; the term "or" and variations thereof may refer to "and/or". The terms "first," "second," and the like in this application are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. In the present application, "plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the present application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.