CN108600326B

CN108600326B - Communication method, device and equipment

Info

Publication number: CN108600326B
Application number: CN201810268830.0A
Authority: CN
Inventors: 崔晓旻; 岳明亮; 王磊
Original assignee: Advanced New Technologies Co Ltd
Current assignee: Advanced New Technologies Co Ltd; Advantageous New Technologies Co Ltd
Priority date: 2018-03-29
Filing date: 2018-03-29
Publication date: 2021-06-25
Anticipated expiration: 2038-03-29
Also published as: CN108600326A

Abstract

The embodiment of the specification discloses a communication method, a communication device and communication equipment. The method comprises the steps that a calling party agent terminal issues cross-domain agent service to a calling party configuration center, registers an address of the calling party agent terminal, and a calling party subscribes the cross-domain agent service to obtain the address of the calling party agent terminal; the provider registers cross-domain proxy service to a provider configuration center, and the provider proxy subscribes the address of the provider configuration center; and the caller agent end and the provider agent end establish connection in a specified mode. When the caller agent side and the provider agent side receive the request or the response, the received request and the received response are not analyzed. Only forwarding according to a customized communication protocol.

Description

Communication method, device and equipment

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a communication method, apparatus, and device.

Background

Due to the business needs, cross-domain communication is often required between business departments.

In current system architecture, each Business Unit (BU) architecture is typically deployed independently. A common way of cross-domain communication is to use an Application Programming Interface (API) to go through a gateway based on a certain protocol (e.g., HTTP protocol). Therefore, the service unit needs to convert the communication message based on the own technology stack into the format supported by the protocol.

Based on this, a more convenient communication scheme is needed.

Disclosure of Invention

The embodiment of the specification provides a communication method, a communication device and communication equipment, which are used for solving the following problems: to provide a more convenient communication scheme.

Based on this, this specification embodiment provides a communication method, including:

receiving a business service calling request initiated by a calling party, wherein the business service calling request comprises a business type and a service name;

screening the corresponding relation between the service type prestored in the local area and the address of the agent end of the provider according to the service type, and determining the address of the agent end of the provider;

routing the service calling request to the address of the provider agent so that the provider agent can transmit the service calling request to a provider;

and receiving a service result returned by the provider agent end, and sending the service result to the caller.

Meanwhile, an embodiment of the present specification further provides another communication method, including:

receiving a service calling request routed by a calling party proxy end, wherein the service calling request is initiated by a calling party and comprises a service type and a service name;

inquiring the corresponding relation between a locally pre-stored service name and a provider address, and determining the provider address;

transparently transmitting the business service calling request to the determined provider address;

and receiving a service result returned by the provider and sending the service result to the caller agent.

Correspondingly, embodiments of the present specification further provide a communication apparatus, including:

the receiving module is used for receiving a business service calling request initiated by a calling party, wherein the business service calling request comprises a business type, a service name and a service result returned by a provider agent end;

the screening module screens the corresponding relation between the service type prestored in the local and the address of the provider agent end according to the service type, and determines the address of the provider agent end;

the routing module is used for routing the service calling request to the address of the provider agent so that the provider agent can transmit the service calling request to the provider;

and the sending module is used for sending the received service result to the calling party.

Meanwhile, an embodiment of the present specification also provides another communication apparatus, including:

the receiving module is used for receiving a service calling request routed by a calling party proxy end, wherein the service calling request is initiated by a calling party and comprises a service type and a service name;

the query module is used for querying the corresponding relation between the service name and the provider address which are locally prestored and determining the provider address;

the transparent transmission module is used for transmitting the service calling request to the determined provider address;

the receiving module is also used for receiving a service result returned by the provider;

and the sending module is used for sending the service result to the calling party agent terminal.

Correspondingly, an embodiment of the present specification further provides a communication device, including:

a memory having a communication program accessed;

the processor calls the communication program in the memory and executes:

Meanwhile, an embodiment of the present specification further provides another communication device, including:

a memory having a communication program accessed;

the processor calls the communication program in the memory and executes:

Correspondingly, embodiments of the present specification also provide a non-volatile computer storage medium storing computer-executable instructions configured to:

Meanwhile, embodiments of the present specification also provide another non-volatile computer storage medium storing computer-executable instructions configured to:

The embodiment of the specification adopts at least one technical scheme which can achieve the following beneficial effects:

the method comprises the steps that a calling party agent terminal issues cross-domain agent service to a calling party configuration center, registers an address of the calling party agent terminal, and a calling party subscribes the cross-domain agent service to obtain the address of the calling party agent terminal; the provider registers cross-domain proxy service to a provider configuration center, and the provider proxy subscribes the address of the provider configuration center; and the caller agent end and the provider agent end establish connection in a specified mode. When the caller agent side and the provider agent side receive the request or the response, the received request and the received response are not analyzed. The method and the device only forward according to the customized communication protocol, and the communication packet cannot be processed in the whole process, so that the communication transparent transmission among a plurality of different BUs is realized, the steps of service reconstruction or communication message conversion required before communication among different BUs is omitted, and the workload is reduced.

Drawings

FIG. 1 is a schematic diagram of a system architecture according to an embodiment of the present disclosure;

FIG. 2 is a schematic diagram illustrating an execution flow of an aspect of a caller agent provided in an embodiment of the present disclosure;

FIG. 3 is a system architecture diagram in an exemplary scenario provided by an embodiment of the present disclosure;

FIG. 4 is a flow chart illustrating the execution of the calling agent side aspect provided by the embodiments of the present disclosure;

FIG. 5 is a logic diagram of the common execution of a caller and a provider provided by embodiments of the present description;

FIG. 6 is a schematic diagram of a bidirectional call of service units in practical application according to an embodiment of the present disclosure;

fig. 7 is a schematic structural diagram of a device at a caller agent end according to an embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of an apparatus at a provider agent end according to an embodiment of the present disclosure.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step are within the scope of the present application.

In the current business processing mode, a plurality of respective closed Business Units (BU) often exist in the same system, each BU architecture is independently deployed, and a lot of demands for cross-room communication (for example, calling services, requesting resources, etc.) arise. Common cross-room communication is an open api manner based on http protocol. In this way, each service system needs to perform some additional protocol conversion work correspondingly, for example, converting an internal RPC communication message or a message communication message into a message supported by an http protocol, and then sending an http request to request a gateway, which is cumbersome.

In fact, the technology stacks used are mostly the same between BUs of the same system. Based on this, the embodiments of this specification provide a communication scheme, when performing cross-domain communication, through a communication routing process in which a proxy automatically adapts to a source system, a caller request and a provider response are transparently transmitted according to a communication protocol, and a service system does not need to make any code modification, thereby implementing cross-domain communication.

Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present disclosure. In this architecture, the caller agent or the provider agent may be in the form of hardware of a separate device, server, or hardware module, or may be in the form of software such as an executable program or a client on the caller/provider machine. Furthermore, it is easy to understand that when services are jointly developed between different BUs, both BUs can be a caller or a provider. In other words, in the architecture, the provider agent and the caller agent act as proxy middleware that performs two corresponding functions, which may also be integrated into the same hardware or software.

The following describes in detail an implementation procedure of the communication method provided by the embodiment of the present specification, based on the architecture shown in fig. 1, and the implementation procedure specifically includes two aspects, namely, a caller agent side and a provider agent side. Fig. 2 is a schematic diagram of an execution flow of an aspect of a caller agent provided in an embodiment of the present specification, as shown in fig. 2, including the following steps:

s201, receiving a service calling request initiated by a calling party, wherein the service calling request comprises a service type and a service name.

The caller can be a BU or a certain machine or application in a machine room where the caller is located. The service type and the service name are both related to the actually applied service and the respective actual processing mode, for example, the service type may include service types related to "payment", "credit", "insurance", "credit", "bank", "wind control", and the like, and the agent end of the caller may determine the machine room where the called service is located according to the service type; the traffic type may also be an actual name directly corresponding to each BU. For the service name, for example, the member query service provided by "xxxpay. cif. userquery" for a certain payment application may query whether a certain user is a registered user under the payment application.

In an exemplary application scenario, if a user of "XXXpay" wants to log into the insurance system to purchase insurance, the machine room of the insurance needs to invoke a member information query service of "XXXpay" to verify whether the user is a user of the XXXpay application. At this time, the machine room in which the insurance is located sends a request for calling the service name "xxxpay.cif.userquery" to the agent in the insurance machine room.

S203, screening the corresponding relation between the service type prestored in the local and the provider agent terminal address according to the service type, and determining the provider agent terminal address.

In the local of the caller, the corresponding relation between each service type and the provider agent terminal is prestored. The corresponding relationship may be stored in a memory, a cache, or a configuration file in various storage media such as a local hard disk. The pre-stored mode can be obtained by the local calling party through user input and storage in advance, or can be obtained by subscribing or scanning to a third-party server. The correspondence may be in a form such as a relational database, key-value pairs, and the like.

Taking the example that the insurance computer room calls the information query to the payment computer room, at this time, the insurance computer room may locally store a plurality of corresponding relationships, such as (payment application, computer room address 1), (credit application, computer room address 2), (loan, computer room address 3), and the like. When the insurance computer room initiates a service call containing "XXXpay" to the calling agent, at this time, the computer room corresponding to the service is determined to be the computer room address 1. As shown in fig. 3, fig. 3 is a schematic diagram of a system architecture in an exemplary scenario provided by an embodiment of the present specification. The solid lines in the figure represent connections that are implemented in this scenario, and the dashed lines with arrows represent connections that are not implemented in this scenario, but are possible in other scenarios.

S205, the service invoking request is routed to the address of the provider agent, so that the provider agent can transmit the service request to the provider.

In this process, for communication such as Remote Procedure Call (RPC) for internal communication or message communication sent by a caller, the provider proxy may pass through the communication packet to the provider proxy based on a customized protocol during routing.

And S207, receiving the service result returned by the provider agent end, and sending the service result to the caller.

After the caller agent end, the provider agent end, the other party, the caller and the provider in respective machine rooms establish connection, the established connection can be stored locally, so that when a service result returned by the provider is received, the caller can be returned to the provider according to a correct original path of the stored result.

As a specific implementation manner, before a caller initiates a service invocation request, it needs to know the actual address of the caller agent, where the actual address may be pre-entered on the caller local machine, or may be obtained by the caller agent registering with a local configuration center: the service type provided locally and the local address are registered with the caller configuration center so as to call the caller to subscribe, and therefore the caller can subscribe with the caller configuration center to obtain the actual address of the caller proxy and the service type provided by the caller proxy. Thus, the receiving of the service invocation request initiated by the caller comprises: and receiving a service calling request initiated by a calling party according to the service type and the address obtained by subscription.

When the caller agent and the provider agent establish a connection, it may communicate across the computer room in a general manner through products such as openapi, netflix zuul, IBM websphere MQ, or other manners. In this manner, the connection to the communication node is made directly by the application. The connection can also be established by adopting a mode of dynamically sensing the address of the other side, which comprises the following steps: and scanning the address server, acquiring the corresponding relation between the service type prestored in the server and the address of the provider agent, and storing the corresponding relation to the local.

Specifically, the address server has previously determined an area (e.g., a designated address, a file directory or a database) in which each BU can register its own service type and its own address, and the address server publishes the registered information so that each BU (i.e., including both the caller agent and the provider agent) can scan and store the relevant information. Each BU can dynamically establish connection according to the corresponding relation obtained and stored by scanning from the server side, once the address of the opposite side is changed, the address service layer can be rescanned to obtain the changed address, and new connection is automatically established again.

The above describes the execution flow of the caller agent side, and the execution flow of the provider agent side is as shown in fig. 4. Fig. 4 is a schematic diagram of an execution flow of an aspect of a caller agent provided in an embodiment of the present specification, including the following steps:

s401, receiving a service calling request routed by a calling party proxy end, wherein the service calling request is initiated by a calling party and comprises a service type and a service name.

S403, inquiring the corresponding relation between the service name and the provider address pre-stored locally, and determining the provider address.

S405, the service calling request is transmitted to the determined provider address;

and S407, receiving the service result returned by the provider, and sending the service result to the agent side of the caller.

The service type and the service name, and the corresponding transparent transmission mode have already been described in detail in the foregoing, and are not described again here. For the correspondence between the locally pre-stored service name and the provider address in S403, the provider may also register with the provider configuration center, and the provider agent subscribes to the configuration center, which includes the following steps: and the corresponding relation between the service name and the provider address published by the subscription provider configuration center is stored to the local. The method can dynamically acquire the registered corresponding relation of the service and the address through the registration and subscription of the configuration center by the configuration center no matter a caller or a provider, so that the address of the provider or the address of a caller agent can be conveniently and dynamically acquired from the configuration center when the address of the provider or the address of the caller agent changes due to various reasons.

Still taking the example of the prior insurance computer room calling the query service to the payment computer room, when the provider agent receives the request of the service name "xxxpay. cif. user query", it queries the provider IP address subscribed from the configuration center, and then transfers the request to the IP address obtained by the query. Finally, after the provider processes the request, the provider forwards the service result obtained by the response back intact according to the link from which the request comes. As shown in fig. 5, fig. 5 is a schematic diagram of logic executed by a caller and a provider together according to an embodiment of the present disclosure.

As a specific implementation manner, the provider agent may further register a local correspondence between a service type and an address to the address server, which includes the following manners: initiating an address registration request to an address server; and receiving an instruction input by a user, registering the corresponding relation between the service type and the local address, and sending the corresponding relation to the address server so that the address server can store and issue the corresponding relation.

In the application scenario illustrated in fig. 3, an example is given in which the insurance computer room makes a service call to the payment computer room. It will be readily appreciated that it is also possible for the payment bureau to call services to the insurance bureau in return. In practical applications, it is not limited to the insurance BU and the payment BU, as shown in fig. 6, fig. 6 is a schematic diagram of two-way call of each service unit in practical applications provided by the embodiments of the present disclosure. It can implement service invocation of bidirectional transparent transmission between a plurality of different BUs, such as "credit", "international payment", "micro-credit", "wind control", etc. And further, each relevant service unit in other systems can also make similar transparent transmission service calls. For example, business departments such as "electronic shopping", "logistics", "storage in warehouse", and the like in the e-commerce system; the internal transparent communication can be carried out among related business departments such as instant messaging, hand-trip, page-trip, payment and the like in the social system. It is not shown here, and the idea adopted in the cross-domain communication is within the scope of the present application as long as the idea provided by the embodiments of the present disclosure is in compliance with the spirit.

In the solution provided in the embodiment of the present specification, a cross-domain proxy service is issued to a caller configuration center through a caller proxy, an address of the caller is registered, and the caller subscribes to the cross-domain proxy service to obtain the address of the caller proxy; the provider registers cross-domain proxy service to a provider configuration center, and the provider proxy subscribes the address of the provider configuration center; and the caller agent end and the provider agent end establish connection in a specified mode. When the caller agent side and the provider agent side receive the request or the response, the received request and the received response are not analyzed. The method and the device only forward according to the customized communication protocol, and the communication packet cannot be processed in the whole process, so that the communication transparent transmission among a plurality of different BUs is realized, the steps of service reconstruction or communication message conversion required before communication among different BUs is omitted, and the workload is reduced.

Based on the same idea, the present specification further provides a communication device, as shown in fig. 7, where fig. 7 is a schematic structural diagram of a device at a caller agent end provided in an embodiment of the present specification, and includes:

the receiving module 701 receives a service invocation request initiated by an invoker, wherein the service invocation request includes a service type and a service name, and receives a service result returned by a provider agent;

the screening module 703 is configured to screen a correspondence between the service type pre-stored locally and the provider agent address according to the service type, and determine the provider agent address;

the routing module 705 is used for routing the service invoking request to the address of the provider proxy so that the provider proxy can transparently transmit the service request to the provider;

the sending module 707 sends the received service result to the caller.

Further, the apparatus further includes a registration module 709, configured to register a service type provided locally and a local address with the caller configuration center, so that the caller subscribes; the receiving module 701 is further configured to receive a service invocation request initiated by the invoker according to the subscribed service type and address.

Further, the device also comprises a scanning module 711, which scans the address server and obtains the corresponding relation between the service type prestored in the server and the address of the provider agent; and a storage module 713, which stores the corresponding relationship to the local.

Meanwhile, the present specification further provides a communication device, as shown in fig. 8, fig. 8 is a schematic structural diagram of a device at a provider agent end provided in an embodiment of the present specification, and the device includes:

a receiving module 801, configured to receive a service invocation request routed by an agent of an invoking party, where the service invocation request is initiated by the invoking party and includes a service type and a service name;

the query module 803 queries the corresponding relationship between the locally pre-stored service name and the provider address, and determines the provider address;

the transparent transmission module 805 is used for transmitting the service calling request to the determined provider address;

the receiving module 801 is further configured to receive a service result returned by a provider;

the sending module 807 sends the service result to the caller agent.

Further, the apparatus further includes a subscription module 809 for subscribing the corresponding relationship between the service name and the provider address published by the provider configuration center, and a storage module 811 for storing the corresponding relationship locally.

Further, the apparatus further includes a registration module 813, which initiates an address registration request to the address server; and receiving an instruction input by a user, registering the corresponding relation between the service type and the local address, and sending the corresponding relation to the address server so that the address server can store and issue the corresponding relation.

Correspondingly, an embodiment of the present application further provides a communication device, including:

a memory having a communication program accessed;

the processor calls the communication program in the memory and executes:

a memory having a communication program accessed;

the processor calls the communication program in the memory and executes:

Based on the same inventive concept, embodiments of the present application further provide a corresponding non-volatile computer storage medium, in which computer-executable instructions are stored, where the computer-executable instructions are configured to:

Meanwhile, the embodiment of the application also provides another corresponding nonvolatile computer storage medium, which stores computer executable instructions, and the computer executable instructions are set as:

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. Especially, as for the device, apparatus and medium type embodiments, since they are basically similar to the method embodiments, the description is simple, and the related points may refer to part of the description of the method embodiments, which is not repeated here.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps or modules recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the units may be implemented in the same software and/or hardware or in one or more pieces of software and/or hardware when implementing the embodiments of the present description.

As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention 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, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. 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.

In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include transitory computer readable media (transient media) such as modulated data signal numbers and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

As will be appreciated by one skilled in the art, one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present description 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, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.

Embodiments of the present description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular transactions or implement particular abstract data types. Embodiments of the present description may also be practiced in distributed computing environments where transactions are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

Claims

1. A communication method is applied to a calling party agent end and comprises the following steps:

receiving a service calling request initiated by a service unit where a calling party is located, wherein the service calling request comprises a service type and a service name;

the service invoking request is transmitted to the address of the provider agent end in a routing way according to a self-defined communication protocol, so that the provider agent end transmits the service invoking request to a service unit of the provider, and the service unit of the provider and the service unit of the caller belong to the same system;

2. The method of claim 1, further comprising:

registering the service type provided locally and the local address to a caller configuration center so as to facilitate the caller to subscribe;

the receiving of the service invocation request initiated by the caller comprises:

and receiving a service calling request initiated by a calling party according to the service type and the address obtained by subscription.

3. The method of claim 1, wherein the correspondence between the pre-stored local business service and the address of the provider agent is obtained by:

and scanning the address server, acquiring the corresponding relation between the service type prestored in the server and the address of the provider agent, and storing the corresponding relation to the local.

4. A communication method is applied to a provider agent side and comprises the following steps:

receiving a service calling request routed by a calling party proxy end, wherein the service calling request is initiated by a service unit where a calling party is located and comprises a service type and a service name;

inquiring the corresponding relation between a locally pre-stored service name and the address of a service unit where a provider is located, and determining the address of the provider, wherein the service unit where the provider is located and the service unit where a caller is located belong to the same system;

and receiving a service result returned by the provider, and transmitting the service result to the calling party agent according to the customized communication protocol.

5. The method of claim 4, wherein the correspondence between the locally pre-stored service name and the provider address is obtained by:

and the corresponding relation between the service name and the provider address published by the subscription provider configuration center is stored to the local.

6. The method of claim 4, further comprising:

initiating an address registration request to an address server;

and receiving an instruction input by a user, registering the corresponding relation between the service type and the local address, and sending the corresponding relation to the address server so that the address server can store and issue the corresponding relation.

7. A communication device is applied to a calling party agent side and comprises:

the receiving module is used for receiving a service calling request initiated by a service unit where a calling party is located, wherein the service calling request comprises a service type and a service name, and receiving a service result returned by a provider agent end;

the routing module is used for transmitting the service calling request to the address of the provider agent end in a routing way according to a self-defined communication protocol so that the provider agent end can transmit the service request to a service unit where the provider is located, and the service unit where the provider is located and the service unit where the caller is located belong to the same system;

8. The apparatus of claim 7, further comprising a registration module for registering a type of service provided locally and an address of the local with the caller configuration center for the caller to subscribe; the receiving module is also used for receiving a service calling request initiated by the calling party according to the service type and the address obtained by subscription.

9. The device of claim 7, further comprising a scanning module for scanning the address server and obtaining the corresponding relationship between the service type pre-stored in the server and the address of the provider agent; and the storage module stores the corresponding relation to the local.

10. A communication apparatus applied to a provider agent, comprising:

the receiving module is used for receiving a service calling request routed by a calling party proxy end, wherein the service calling request is initiated by a service unit where a calling party is located and comprises a service type and a service name;

the query module is used for querying the corresponding relation between a locally pre-stored service name and the address of the service unit where the provider is located and determining the address of the provider, wherein the service unit where the provider is located and the service unit where the caller is located belong to the same system;

and the sending module is used for transmitting and sending the service result to the calling party agent end according to the customized communication protocol.

11. The apparatus of claim 10, further comprising a subscription module for subscribing to the correspondence between the service name and the provider address published by the provider configuration center and storing the correspondence locally.

12. The apparatus of claim 10, further comprising a registration module that initiates an address registration request to the address server; and receiving an instruction input by a user, registering the corresponding relation between the service type and the local address, and sending the corresponding relation to the address server so that the address server can store and issue the corresponding relation.

13. A communication device applied to a calling party agent side comprises:

a memory having a communication program accessed;

the processor calls the communication program in the memory and executes:

14. A communication device applied to a provider agent, comprising:

a memory having a communication program accessed;

the processor calls the communication program in the memory and executes: