CN114020492A

CN114020492A - Information processing method, system and device

Info

Publication number: CN114020492A
Application number: CN202111317600.7A
Authority: CN
Inventors: 蒋松
Original assignee: China Construction Bank Corp
Current assignee: China Construction Bank Corp
Priority date: 2021-11-09
Filing date: 2021-11-09
Publication date: 2022-02-08

Abstract

The application discloses an information processing method, a system and a device, relates to the technical field of distributed services, and is used for rapidly providing distributed remote procedure call services. At a client, the method provided by the application comprises the following steps: when a service calling request needs to be initiated to a server, acquiring information of the server from a maintained service information list; and sending a service calling request to the server according to the information of the server. At a server, the method provided by the application comprises the following steps: receiving a service calling request sent by a client through a first process, and distributing the service calling request to a second process; the first process corresponds to at least one second process; and processing the service calling request through a second process.

Description

Information processing method, system and device

Technical Field

The present application relates to the field of distributed service technologies, and in particular, to an information processing method, system, and apparatus.

Background

Remote Procedure Call (RPC) communication means refers to calling a Remote method like calling a local method. Remote procedure calls are mainly used as a tool for remotely calling code between different processes of the same machine or different machines.

With the rise of technologies such as big data and machine learning, more and more developers use python (a computer programming language) to develop data analysis and data services.

With the development of the internet, the single application architecture is updated only by physical hardware with smaller and smaller income, which gradually becomes the bottleneck of the system, and the distributed service architecture becomes a necessary trend. The distributed service architecture requires splitting of services, interaction between different services is inevitable, but the prior art does not provide an efficient and reusable distributed RPC service framework.

Disclosure of Invention

The embodiment of the application provides an information processing method and system, which are used for rapidly providing distributed remote procedure call service.

At a server, an information processing method provided by an embodiment of the present application includes:

receiving a service calling request sent by a client through a first process, and distributing the service calling request to a second process; the first process corresponds to at least one second process;

and processing the service calling request through a second process.

The method comprises the steps that a service calling request sent by a client is received through a first process, and the service calling request is distributed to a second process; the first process corresponds to at least one second process; and processing the service calling request through the second process, so that the distributed remote procedure calling service can be rapidly provided to the client at the server.

Optionally, the service invocation request includes service interface information, and the service interface information includes indication information used for searching for a service code corresponding to the service requested by the client.

Optionally, the processing the service invocation request through the second process specifically includes:

and after receiving the service calling request, the second process finds out the service code corresponding to the service requested by the client according to the indication information and executes the service code through at least one coroutine.

Optionally, after the first process is started, the method further includes:

and registering the service information of the server side with the registration center through a third process.

Correspondingly, at a client, an information processing method provided in an embodiment of the present application includes:

when a service calling request needs to be initiated to a server, acquiring information of the server from a maintained service information list;

sending a service calling request to the server according to the information of the server, so that the server receives the service calling request sent by a client through a first process, and distributes the service calling request to a second process; the first process corresponds to at least one second process; and processing the service calling request through a second process.

Optionally, before initiating the service invocation request to the server, the method further includes:

sending a service subscription request to a registration center, wherein the service subscription request comprises the information of the client and the application name of the service requesting subscription;

receiving service information of a service end returned by the registration center, wherein the service information comprises information of the service end providing the service;

and generating the service information list by using the application name and the information of the server, wherein the service information list comprises the corresponding relation between the application name and the information of the server.

Optionally, when a service invocation request needs to be initiated to a server, obtaining information of the server from a maintained service information list, specifically including:

determining service interface information corresponding to the service calling request;

analyzing the application name from the service interface information;

and acquiring information of a service end corresponding to the application name from the service information list according to the application name, wherein the information of the service end comprises address information of the service end.

Optionally, when the application name corresponds to information of multiple service terminals, information of one service terminal is selected from the information of the multiple service terminals through a pre-configured load balancing policy.

Optionally, the service interface information includes an application name and indication information used for the service end to search for a service code corresponding to the application name.

Optionally, the indication information at least includes one or a combination of the following information:

service end name, service class, method name.

Correspondingly, on the registration center side, an information processing method provided by the embodiment of the application includes:

when a service registration request sent by a server is received, acquiring and recording service information of the server from the service registration request; the service information comprises an application name of the service provided by the server and address information of the server;

when a service subscription request sent by a client is received, acquiring an application name of a service which the client requests to subscribe from the service subscription request;

determining service information of a service end capable of providing the service requested to be subscribed by the client according to the application name of the service requested to be subscribed by the client, and providing the service information to the client, so that the client acquires the information of the service end from a maintained service information list when needing to initiate a service call request to the service end; the service information list is generated by the client by using the service information of the service terminal acquired from the registration center; the client sends a service calling request to the server according to the information of the server, so that the server receives the service calling request sent by the client through a first process and distributes the service calling request to a second process; the first process corresponds to at least one second process; and processing the service calling request through a second process.

Optionally, the method further comprises:

and when the service information of the server providing the service for the client is changed, notifying the updated service information of the server providing the service for the client to the client.

An information processing apparatus provided in an embodiment of the present application is applied to a server, and includes:

a memory for storing program instructions;

and the processor is used for calling the program instructions stored in the memory and executing any one of the information processing methods of the server according to the obtained program.

An information processing apparatus provided in an embodiment of the present application is applied to a client, and includes:

a memory for storing program instructions;

and the processor is used for calling the program instructions stored in the memory and executing the information processing method of any one of the clients according to the obtained program.

An information processing apparatus provided in an embodiment of the present application is applied to a registration center, and includes:

a memory for storing program instructions;

and the processor is used for calling the program instructions stored in the memory and executing any one of the information processing methods on the registration center side according to the obtained program.

An information processing system provided in an embodiment of the present application includes: the information processing device of the server side, and/or the information processing device of the client side, and/or the information processing device of the registration center side.

Another embodiment of the present application provides a computing device, which includes a memory and a processor, wherein the memory is used for storing program instructions, and the processor is used for calling the program instructions stored in the memory and executing any one of the above methods according to the obtained program.

Another embodiment of the present application provides a computer-readable storage medium having stored thereon computer-executable instructions for causing a computer to perform any one of the methods described above.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of a system framework provided by an embodiment of the present application;

fig. 2 is a schematic diagram of a framework of a service provider provided in an embodiment of the present application;

FIG. 3 is a schematic diagram illustrating an implementation process of a service consumer according to an embodiment of the present application;

fig. 4 is a schematic diagram of nodes at each level of a registry according to an embodiment of the present disclosure;

fig. 5 is a schematic processing flow diagram of a client and a server according to an embodiment of the present disclosure;

fig. 6 is a flowchart illustrating an information processing method of a server according to an embodiment of the present application;

fig. 7 is a flowchart illustrating an information processing method of a client according to an embodiment of the present application;

fig. 8 is a schematic flowchart of an information processing method at a registry according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an information processing apparatus of a server according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of an information processing apparatus of a client according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of an information processing apparatus on the registration center side according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of another information processing apparatus of a server according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of another information processing apparatus of a client according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of another information processing apparatus on the registration center side according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The embodiment of the application provides an information processing method, system and device, which are used for rapidly providing a distributed RPC service.

The client according to the embodiments of the present application may be a terminal device, such as a computer, or may be a handheld device having a wireless connection function, or another processing device connected to a wireless modem. The names of the terminal devices may also be different in different systems, for example, in a 5G system, the terminal devices may be referred to as User Equipments (UEs). Wireless terminal devices, which may be mobile terminal devices such as mobile telephones (or "cellular" telephones) and computers with mobile terminal devices, e.g., mobile devices that may be portable, pocket, hand-held, computer-included, or vehicle-mounted, communicate with one or more core networks via the RAN. Examples of such devices include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistants (PDAs), and the like. The wireless terminal device may also be referred to as a system, a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile), a remote station (remote station), an access point (access point), a remote terminal device (remote terminal), an access terminal device (access terminal), a user terminal device (user terminal), a user agent (user agent), and a user device (user device), which are not limited in this embodiment of the present application.

The server according to the embodiment of the present application may be a server on a network side, and the embodiment of the present application is not limited thereto.

Various embodiments of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that the display sequence of the embodiment of the present application only represents the sequence of the embodiment, and does not represent the merits of the technical solutions provided by the embodiments.

Interpretation of terms:

python: a computer programming language.

RPC: an RPC is an abbreviated form of Remote Procedure Call (Remote Procedure Call) which is a protocol that requests services from a Remote computer program over a network without knowledge of the underlying network technology, as if a local function were called.

Zookeeper: ZooKeeper is a distributed, open source, distributed application coordination service. It is a software that provides a consistent service for distributed applications, and the functions provided include: configuration maintenance, domain name service, distributed synchronization, group service, etc.

GIL: GIL is short for Global Interpreter Lock, is a Global Interpreter Lock of python, and is a Lock added by python to solve data integrity and state synchronization among multiple threads.

And (3) thick: thrift is an interface description language and binary communication protocol that is used to define and create cross-language services. It is used as a Remote Procedure Call (RPC) framework.

grpc: the RPC is a high-performance, open-source and universal RPC framework and is oriented to a server side and a mobile side (namely a client side). Designed based on http/2 standard, the method has the characteristics of message header compression, bidirectional flow, flow Control, multiplexing of a Transmission Control Protocol (TCP) and the like.

The python can be based on native communication protocols, such as protocols of TCP, http/1, http/2 and the like, or some mature RPC frameworks, such as RPC applications of thrift and grpc development single machines, and in addition, due to the existence of GIL, multi-core CUP cannot be well utilized by multiple threads of python, so that much work needs to be done by python to realize distributed RPC service.

The registration and discovery, load balancing, fault tolerance and the like of the service are functions required by the distributed RPC service, if an efficient and reusable distributed RPC framework is lacked, a python developer needs to develop a program again every time, and the distributed RPC service has high requirements on the bottom layer technology of the developer. According to the technical scheme, the necessary components of the distributed RPC service are extracted, so that the extracted components have a reusable effect, developers do not need to pay attention to the bottom technology of the distributed RPC service, focus on service development and quickly respond to market demands.

Referring to fig. 1, the embodiment of the present application abstracts three components from modules necessary for a distributed RPC service: a service provider (i.e., a server), a service consumer (i.e., a client), and a registry.

The three components are related as follows:

when the service provider starts, the service provider automatically registers the registration service information with the registration center.

The service information includes: the service provider may provide which services (specifically including application names), and meta information of service interfaces (service interfaces), for example, the meta information includes one or more items of information among IP addresses of servers providing the services, service ports, service interface names, and the like. The service port is a port of a server providing a service.

And secondly, when the service consumer starts, subscribing service information to the registration center.

That is to say, a service consumer needs which services, and notifies the registry, for example, a specific application name is sent to the registry, and the registry determines, according to a subscription request (carrying the application name) of the service consumer and service information (including the application name) registered by a service provider, related information of the service provider capable of providing the service requested to be subscribed by the service consumer, that is, one or more items of information among an IP address, a service port, and a service interface name of a server capable of providing the service requested to be subscribed by the service consumer, and provides the service information to the service consumer sending the subscription request.

Thirdly, the registration center sends the service information which the service consumer requests to subscribe to the service consumer on one hand; on the other hand, the change information of the relevant service provider is also notified to the service consumer who has subscribed to the service, for example, the service that has been subscribed by the service consumer a before is provided by the service provider B, and if the service information of the service provider B changes, the service provider B cannot continue to provide the service to the service consumer a, but changes to the service that is subscribed to by the service provider C for the service consumer a, the registration center notifies the service consumer a of the relevant information of the service provider C (for example, information including one or more of an IP address of a server providing the service, a service port, a service interface name, and the like);

and fourthly, the service consumer calls the relevant service to the service provider through the service information issued by the registration center.

For example, a first service subscribed by the service consumer a is provided by the service provider B, and the first service is called to the service provider B according to one or more items of information in the server IP address, the service port, and the service interface name of the service provider B;

for example, the second service subscribed by the service consumer a is provided by the service provider C, and the second service is called to the service provider C according to one or more items of information of the server IP address, the service port, and the service interface name of the service provider C.

Each of the above-mentioned aspects is specifically described below.

Referring to fig. 2, with respect to the service provider:

the service provider described in the embodiments of the present application uses three processes: a first process, a second process, a third process; wherein:

a first process, which may also be referred to as a master process, such as a master process;

a second process, which may also be referred to as a work process, such as a woker process;

the third process, which may also be referred to as a service registration sub-process.

For example:

one master process corresponds to a plurality of browser processes, each browser process corresponds to a plurality of coroutines, and the master process can also call a service registration subprocess.

The master process is mainly used for receiving a service calling request sent by a client and distributing the service calling request sent by the client to the worker process;

the worker process is used for processing a service calling request distributed by the master process, specifically, the worker process is used for finding a service code for providing a service, and the service code is executed through at least one co-process, namely, a service logic code corresponding to the service requested by the client is executed. The coroutine is a smaller execution unit than a thread.

The service registration subprocess registers the service information of the service provider (i.e. the service that can be provided and one or more items of information in the IP address, service port, service interface name of the server that provides the service, etc. described in the foregoing content) with the registry according to the trigger or control of the master process after the master process is started.

The service provider bottom layer supports a variety of RPC protocols, such as thrift, grpc, etc.

Referring to fig. 3, with respect to the service consumer:

when the service consumer starts, the service consumer subscribes the required service information to the registration center through the monitoring thread/process of the registration center (different languages are realized differently), and maintains a local service information list by using the received service information.

The registry monitoring thread/process is a code module of a service consumer, and is used for connecting the registry and monitoring the change of service information.

The service information sent by the registry to the client includes, for example, address information of a server as a server, and further may include information such as a protocol adopted by the server, where the address information of the server includes, for example, an IP address and a service port number of the server.

The service information list includes, for example, a correspondence between an application name and information of a server; one application name may correspond to information of one or more servers, information of the same server, or one or more application names. The application name is the name of the service subscribed by the client; the information of the server includes, for example, a protocol used by a service provider, an IP address, and a service port number. The information of the server may include the same kind of information as the service information of the server provided by the registration center, for example, both include address information of the server, or may include different types of information, for example, information such as a bottom layer protocol used by the server, and may be selectively included.

For example, the service information list includes, for example:

{“xxApp”:[“thrift://192.168.x.x:port1”,“thrift://192.168.x2.x2:port2”]

“xxApp1”:[“thrift://192.168.x.x:port3”,“thrift://192.168.x2.x2:port4”]}。

wherein, "xxApp" represents the application name of a service subscribed by the client, and "thrift:// 192.168.x.x: port 1" represents that the protocol used by a service provider capable of providing the service corresponding to the application name is thrift, the IP address of the protocol is 192.168.x.x, and the service port is port 1; "thrift:// 192.168.x 2: port 2" indicates that the protocol used by another service provider that can provide the service corresponding to the application name is thrift, the IP address is 192.168.x2, and the service port is port 2;

similarly, "xxApp 1" represents the application name of another service subscribed by the client, "thrift:// 192.168.x.x: port 3" represents that the protocol used by one service provider which can provide the service corresponding to the application name is thrift, the IP address is 192.168.x.x, and the service port is port 3; "thrift:// 192.168.x 2: port 4" indicates that another service provider that can provide the service corresponding to the application name uses the protocol of thrift, the IP address of which is 192.168.x2, and the service port of which is port 4.

The load balancer is implemented on a service consumer side, and a load balancing policy can be configured, for example, the load balancing policy obtains a service address (one or more items of information in a server IP address, a service port, a service interface name, and the like) to be requested from a service information list in a random manner, a polling manner, and the like. Thus, the load balancer distributes service requests evenly to multiple servers, rather than all to the same server, resulting in a situation where the server is overloaded.

Referring to fig. 4, with regard to the registry:

the registry uses the ZooKeeper to store metadata information describing the whole distributed service, the Root node of the registry is RPC _ Root, the second-level nodes are names of all APPs, the third-level nodes comprise service providers (providers) and service consumers (consumers), and the fourth-level nodes are leaf nodes.

It can be seen that the whole registry is a tree structure, where the Root node RPC _ Root is the start node, and the APP name of the secondary node, i.e. the application name of the service interface, such as APP1 … … APPn shown in fig. 4; the tertiary nodes include two types of nodes: service providers (providers) and service consumers (consumers); the level four nodes are leaf nodes, wherein the level four nodes under providers store address information of service providers, protocols used, etc., such as the thick: ip1: port and the thick: ip2: port under providers shown in fig. 4; the four-level node under the consumers stores the IP addresses of the service consumers, so that the number of the service consumers can be counted, for example, the IP under the consumers, i.e., the IP address of the client, shown in fig. 4, and the IP addresses of different clients are different, so that there are several IP addresses under the consumers, and there are several clients.

Through this structure, the registry can manage which application can be provided by which server and which clients subscribe to the application, that is, the functions described in the above are realized, which is not described herein again.

In the embodiment of the present application, a set of process models is used to integrate a native or open-source RPC protocol, where zookeeper is used in a registry, and other components may be used instead, for example, etcd, which is not limited in the embodiment of the present application.

The following is a detailed explanation of the information interaction process between the parties.

Referring to fig. 5, regarding routing of service invocation requests sent by clients:

the service interface information described in the embodiment of the present application includes, for example, an application name and indication information used by a service provider to find a service code corresponding to the application name, where the indication information includes, for example: service end name, service class, method name, and at this time, the format of the service interface, for example:

the method comprises the following steps of (1) application name, service end point name, service class and method name;

the application name corresponds to a second-level node name of the registration center and is used for the registration center to search a service provider under the application; and the server is used for searching the address information of the server corresponding to the application name at the client, so that a service call request and the like are initiated by utilizing the address information of the server.

The service end roll name can be understood as first-level information used for the service end to search a service code to be executed, and for example, the service end roll name can be called as a service module name;

the service class may also be referred to as a code module (corresponding to an object-oriented programming class) name under the service module, that is, the service class is used for the server to search the secondary information of the service code to be executed;

the method name refers to the name of the function in the service class, that is, the specific service code in the code module to be executed is indicated, that is, the method name is used for the server to search the three-level information of the service code to be executed.

Through the four layers of information of the application name, the service end roll name, the service class and the method name, the service calling request sent by the client can be routed to the corresponding service code in the server from the client, namely, the code corresponding to the service which can be requested by the client and provided by the server can be found.

The three-level information, namely the service end roll name, the service class and the method name, is used for a service provider to find a code corresponding to an application name, namely a service code capable of providing a service corresponding to the application name.

For example, the service interface information and its format are: xxapp.xxendpoint.xxservice.xxfunction;

the application name xxApp represents the attribution of a service interface, and is used for the client to search for a service address corresponding to the application name xxApp (namely, server address information and the like capable of providing a service corresponding to the application name xxApp); the service end point name xxEndpoint, the service class xxService and the method name xxFunction are used for the server to construct a service instance, namely the service end to find a service code corresponding to the application name xxApp.

The routing process is specifically as follows:

when a client (i.e., a service consumer) wants to initiate a service invocation request, for example, the client may obtain service interface information corresponding to the service invocation request according to a preset interface document. The interface document includes, for example, a correspondence between an application name and service interface information.

For example, the service interface information is: xxapp.xxendpoint.xxservice.xxfunction, the client first resolves the application name: and then, a load balancer in the client acquires a service address corresponding to the application name xxApp from a service information list maintained by the client according to the application name xxApp, wherein the service addresses corresponding to the xxApp can be multiple, the load balancer screens out one service address from a plurality of service addresses corresponding to the xxApp according to a pre-configured load balancing strategy (such as random and polling), and finally, a service calling request is sent to a corresponding service terminal according to the service address.

After receiving a service call request (carrying service interface information) sent by a client, a server (i.e. a service provider) distributes the service call request sent by the client to a router process through a master process, the router process processes a service by using a coroutine (i.e. a lightweight thread) after receiving the service call request, and the coroutine finds a service code corresponding to an application name of the service requested by the client according to the service interface information and executes the service code, namely, the service instance is dynamically constructed. And finally, feeding back the execution result to the client through a bottom layer protocol.

If a service end only provides one service, for example, only provides a service corresponding to xxApp, the service interface information carried in the service invocation request sent by the client may not include an application name, but only include information (e.g., xxend.xxservice.xxfunction) for searching a service code corresponding to the application name. And then, executing the service code, for example, dynamically constructing an xxService object under the xxEndpoint service module, calling an xxFunction method in the xxService object, and finally returning an execution result of the xxFunction method.

In summary, the embodiment of the application provides a model based on a main process, a plurality of working processes and a coroutine, and a python distributed RPC framework supporting multiple protocols, so that the limitation of high concurrency of python GIL is solved, a set of high-efficiency reusable distributed RPC framework based on python is provided, and the process and cost for writing distributed RPC service by python developers are simplified.

The technical solutions provided by the method and the device provided by the embodiments of the present application are summarized from different sides, respectively.

Referring to fig. 6, at a server, an information processing method provided in an embodiment of the present application includes:

s101, receiving a service calling request sent by a client through a first process, and distributing the service calling request to a second process; the first process corresponds to at least one second process;

wherein the first process, such as the master process described above;

the second process, for example, the worker process described above.

The first process is mainly used for receiving a service calling request sent by a client and distributing the service calling request sent by the client.

And S102, processing the service calling request through a second process.

Specifically, the second process is configured to process the service invocation request distributed by the first process, find a corresponding service code, and process the service code through one or more coroutines.

The server may feed back the execution result of the service code to the client through a bottom layer protocol, which may be implemented in the prior art and is not described herein again.

The indication information includes, for example, the name of the service end point, the service class, and the name of the method. Of course, application names may also be included.

For example, the service end respectively uses the service end roll name, the service class and the method name to gradually search the service code corresponding to the application name.

Optionally, after the first process is started, the method further includes:

The third process, for example the service registration subprocess.

The service information of the server includes, for example, an application name of a service provided by the server and address information of the server, and may also include underlying protocol information of the server.

Correspondingly, referring to fig. 7, at the client, an information processing method provided in an embodiment of the present application includes:

s201, when a service calling request needs to be sent to a server, obtaining information of the server from a maintained service information list;

the information of the server may be, for example, service information of the server, or may be only address information of the server.

S202, sending a service calling request to the server according to the information of the server, enabling the server to receive the service calling request sent by a client through a first process, and distributing the service calling request to a second process; the first process corresponds to at least one second process; and processing the service calling request through a second process.

The service call request sent to the server includes, for example, service interface information, where the service interface information includes, for example, an application name and indication information used by the server to search for a service code corresponding to the application name, or only includes the indication information used by the server to search for the service code corresponding to the application name.

receiving service information of a server returned by the registry, where the service information includes information of the server providing the service, for example, address information of the server, and further optionally, bottom layer protocol information adopted by the server;

determining service interface information corresponding to the service calling request; for example, acquiring service interface information corresponding to the service calling request according to a preset interface document;

analyzing the application name from the service interface information;

and acquiring information of a service end corresponding to the application name from the service information list according to the application name analyzed from the service interface information, wherein the information of the service end comprises address information of the service end, and further optionally, bottom layer protocol information of the service end and the like.

For example, the address information (including one or more items of information of server IP address, service port, service interface name, etc.) of one server is obtained from the address information of multiple servers corresponding to the same application name by means of random, polling, etc. Thus, the load balancer distributes service requests evenly to multiple servers, rather than all to the same server, resulting in a situation where the server is overloaded.

service end name, service class, method name. Of course, the embodiment of the present application is not limited to these three layers of information, and only one or two layers of information may be provided.

Correspondingly, referring to fig. 8, in a registration center, an information processing method provided in an embodiment of the present application includes:

s301, when a service registration request sent by a service end is received, acquiring and recording service information of the service end from the service registration request; the service information comprises an application name of the service provided by the server and address information of the server;

s302, when a service subscription request sent by a client is received, acquiring an application name of a service which the client requests to subscribe from the service subscription request;

the registry can form an architecture as shown in fig. 4, for example, through the information carried in the service registration request sent by the server and the service subscription request sent by the client, thereby maintaining the association relationship between the client and the server about the service application.

S303, determining service information of a service terminal capable of providing the service requested to be subscribed by the client according to the application name of the service requested to be subscribed by the client, and providing the service information to the client, so that the client acquires the information of the service terminal from a maintained service information list when needing to initiate a service call request to the service terminal; the service information list is generated by the client by using the service information of the service terminal acquired from the registration center; the client sends a service calling request to the server according to the information of the server, so that the server receives the service calling request sent by the client through a first process and distributes the service calling request to a second process; the first process corresponds to at least one second process; and processing the service calling request through a second process.

Optionally, the method further comprises:

and when the service information of the server providing the service for the client is changed, notifying the updated service information of the server providing the service for the client to the client. For a specific example, refer to the relevant content of the above registration center, and details are not described here.

Referring to fig. 9, at a server, an information processing apparatus provided in an embodiment of the present application includes:

a distribution request unit 11, configured to receive, through a first process, a service invocation request sent by a client, and distribute the service invocation request to a second process; the first process corresponds to at least one second process;

and the request processing unit 12 is configured to process the service invocation request through a second process.

Optionally, the method further comprises:

a registering unit (not shown in fig. 9), configured to register service information of the service end with the registry through a third process after the first process is started.

Correspondingly, referring to fig. 10, at a client, an information processing apparatus provided in an embodiment of the present application includes:

an information determining unit 21, configured to obtain information of a server from a maintained service information list when a service invocation request needs to be initiated to the server;

a sending request unit 22, configured to send a service invocation request to the server according to the information of the server, so that the server receives the service invocation request sent by the client through a first process, and distributes the service invocation request to a second process; the first process corresponds to at least one second process; and processing the service calling request through a second process.

Optionally, the method further comprises:

a subscription unit (not shown in fig. 10) for:

before the sending request unit 22 sends a service call request to the server, sending a service subscription request to the registry, where the service subscription request includes information of the client and an application name of a service requesting subscription;

analyzing the application name from the service interface information;

service end name, service class, method name.

Correspondingly, referring to fig. 11, in a registration center, an information processing apparatus provided in an embodiment of the present application includes:

the service registration unit 31 is configured to, when receiving a service registration request sent by a service end, acquire and record service information of the service end from the service registration request; the service information comprises an application name of the service provided by the server and address information of the server;

the service subscription processing unit 32 is configured to, when receiving a service subscription request sent by a client, obtain an application name of a service to which the client requests subscription from the service subscription request;

a service information providing unit 33, configured to determine, according to an application name of a service to which the client requests subscription, service information of a service end capable of providing the service to which the client requests subscription, and provide the service information to the client, so that the client obtains information of the service end from a maintained service information list when a service invocation request needs to be initiated to the service end; the service information list is generated by the client by using the service information of the service terminal acquired from the registration center; the client sends a service calling request to the server according to the information of the server, so that the server receives the service calling request sent by the client through a first process and distributes the service calling request to a second process; the first process corresponds to at least one second process; and processing the service calling request through a second process.

Optionally, the service information providing unit 33 is further configured to:

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

Referring to fig. 12, at a server, another information processing apparatus provided in an embodiment of the present application includes:

a memory 520 for storing program instructions;

a processor 500 for calling the program instructions stored in the memory, and executing, according to the obtained program:

and processing the service calling request through a second process.

Optionally, the processor 500 is further configured to call the program instruction stored in the memory, and execute, according to the obtained program:

and after the first process is started, registering the service information of the server side to a registration center through a third process.

A transceiver 510 (optional) for receiving and transmitting data under the control of the processor 500.

Where in fig. 12, the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 500 and memory represented by memory 520. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 510 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other apparatus over a transmission medium. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 500 in performing operations.

The processor 500 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or a Complex Programmable Logic Device (CPLD).

Correspondingly, referring to fig. 13, at a client, another information processing apparatus provided in an embodiment of the present application includes:

a memory 620 for storing program instructions;

a processor 600, configured to call the program instructions stored in the memory, and execute, according to the obtained program:

Optionally, the processor 600 is further configured to call the program instruction stored in the memory, and execute, according to the obtained program:

before a service calling request is sent to a server, a service subscription request is sent to a registration center, wherein the service subscription request comprises information of the client and an application name of a service requesting subscription;

analyzing the application name from the service interface information;

service end name, service class, method name.

A transceiver 610 (optional) for receiving and transmitting data under the control of the processor 600.

Where in fig. 13 the bus architecture may include any number of interconnected buses and bridges, with various circuits being linked together, particularly one or more processors represented by processor 600 and memory represented by memory 620. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 610 may be a number of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium. For different user devices, the user interface 630 may also be an interface capable of interfacing with a desired device externally, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 600 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 600 in performing operations.

Alternatively, the processor 600 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

Correspondingly, referring to fig. 14, in a registration center, another information processing apparatus provided in an embodiment of the present application includes:

a memory 505 for storing program instructions;

a processor 504 for calling the program instructions stored in the memory, and executing:

Optionally, the processor 504 is further configured to call the program instruction stored in the memory, and execute, according to the obtained program:

A transceiver 501 (optional) for receiving and transmitting data under the control of the processor 504.

In FIG. 14, a bus architecture (represented by bus 506), the bus 506 may include any number of interconnected buses and bridges, with the bus 506 linking together various circuits including one or more processors, represented by the processor 504, and memory, represented by the memory 505. The bus 500 may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. A bus interface 503 provides an interface between the bus 506 and the transceiver 501. The transceiver 501 may be one element or may be multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other apparatus over a transmission medium. Data processed by processor 504 is transmitted over a wireless medium via antenna 502, and further, antenna 502 receives data and transmits data to processor 504.

The processor 504 is responsible for managing the bus 506 and general processing, and may also provide various functions including timing, peripheral interfaces, voltage regulation, power management, and other control functions. And memory 505 may be used to store data used by processor 504 in performing operations.

Alternatively, the processor 504 may be a CPU (central processing unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a CPLD (Complex Programmable Logic Device).

An information processing system provided in an embodiment of the present application includes: the information processing device of the server side, and/or the information processing device of the client side, and/or the information processing device of the registration center side. The specific structure is shown in fig. 1, for example, and the interaction process between the two structures is not described herein again.

The embodiment of the present application provides a computing device, which may specifically be a desktop computer, a portable computer, a smart phone, a tablet computer, a Personal Digital Assistant (PDA), and the like. The computing device may include a Central Processing Unit (CPU), memory, input/output devices, etc., the input devices may include a keyboard, mouse, touch screen, etc., and the output devices may include a Display device, such as a Liquid Crystal Display (LCD), a Cathode Ray Tube (CRT), etc.

The memory may include Read Only Memory (ROM) and Random Access Memory (RAM), and provides the processor with program instructions and data stored in the memory. In the embodiments of the present application, the memory may be used for storing a program of any one of the methods provided by the embodiments of the present application.

The processor is used for executing any one of the methods provided by the embodiment of the application according to the obtained program instructions by calling the program instructions stored in the memory.

Embodiments of the present application provide a computer-readable storage medium for storing computer program instructions for an apparatus provided in the embodiments of the present application, which includes a program for executing any one of the methods provided in the embodiments of the present application.

The computer-readable storage medium can be any available medium or data storage device that can be accessed by a computer, including but not limited to magnetic memory (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical memory (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor memory (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND FLASH), Solid State Disks (SSDs)), etc.

The above method process flow may be implemented by a software program, which may be stored in a storage medium, and when the stored software program is called, the above method steps are performed.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is 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 flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor 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 processor 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 changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. An information processing method, characterized in that the method comprises:

and processing the service calling request through a second process.

2. The method according to claim 1, wherein the service invocation request includes service interface information, and the service interface information includes indication information for searching for a service code corresponding to the service requested by the client.

3. The method according to claim 2, wherein the processing the service invocation request by the second process specifically includes:

4. The method of claim 1, wherein after the first process is started, the method further comprises:

5. An information processing method, characterized in that the method comprises:

6. The method of claim 5, wherein before initiating the service invocation request to the server, the method further comprises:

7. The method according to claim 5, wherein when a service invocation request needs to be initiated to a server, acquiring information of the server from a maintained service information list specifically comprises:

analyzing the application name from the service interface information;

8. The method according to claim 7, wherein when the application name corresponds to information of a plurality of service terminals, information of one service terminal is selected from the information of the plurality of service terminals through a pre-configured load balancing policy.

9. The method according to claim 7, wherein the service interface information includes an application name and indication information for the service end to search a service code corresponding to the application name.

10. The method according to claim 9, wherein the indication information comprises at least one or a combination of the following information:

service end name, service class, method name.

11. An information processing method, characterized in that the method comprises:

12. The method of claim 11, further comprising:

13. An information processing apparatus, applied to a server, includes:

a memory for storing program instructions;

a processor for calling program instructions stored in said memory to execute the method of any one of claims 1 to 4 in accordance with the obtained program.

14. An information processing apparatus, applied to a client, comprising:

a memory for storing program instructions;

a processor for calling program instructions stored in said memory to execute the method of any one of claims 5 to 10 in accordance with the obtained program.

15. An information processing apparatus, applied to a registry, comprising:

a memory for storing program instructions;

a processor for calling program instructions stored in said memory to execute the method of claim 11 or 12 in accordance with the obtained program.

16. A computer-readable storage medium having stored thereon computer-executable instructions for causing a computer to perform the method of any one of claims 1 to 12.

17. An information processing system, comprising: the device of claim 13, and/or the device of claim 14, and/or the device of claim 15.