CN115412585A

CN115412585A - Service access point calling method, device, equipment and readable storage medium

Info

Publication number: CN115412585A
Application number: CN202110576503.3A
Authority: CN
Inventors: 魏华
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Communications Ltd Research Institute
Priority date: 2021-05-26
Filing date: 2021-05-26
Publication date: 2022-11-29

Abstract

The application discloses a calling method, a calling device, a calling equipment and a readable storage medium of a service access point, and belongs to the technical field of communication. The specific implementation scheme comprises the following steps: acquiring the name of a service access point to be called; determining a destination IP address meeting the requirement according to the name; and scheduling the service access point by using the destination IP address meeting the requirement. According to the scheme in the application, the service access point can be dispatched without a fixed domain name address, but the destination IP address meeting the requirement can be automatically selected according to the name of the service access point, and the destination IP address meeting the requirement is utilized to dispatch the service access point, so that the corresponding communication link can meet the requirement.

Description

Service access point calling method, device, equipment and readable storage medium

Technical Field

The application belongs to the technical field of communication, and particularly relates to a method, a device, equipment and a readable storage medium for calling a service access point.

Background

In the development of the existing serverless architecture, a service access point such as an Application Programming Interface (API) is fixed to a certain domain name address, and after the service access point is resolved into an IP address by a domain name system, data transmission and API call are performed. The fixed domain name addresses allow developers to identify all subsequent API service providers at the beginning of programming and are not easily changed. In this case, since the developer cannot ensure that the communication link from the program running location to the API called by the developer is unchanged and the communication delay is always kept in a low state, after the API service provider adjusts the IP address corresponding to the domain name resolution, the communication link may not meet the requirement.

Disclosure of Invention

The embodiment of the application aims to provide a method, a device, equipment and a readable storage medium for calling a service access point, so as to solve the problem that a communication link cannot meet requirements when the service access point is scheduled through a fixed domain name address at present.

In order to solve the technical problem, the present application is implemented as follows:

in a first aspect, a method for calling a service access point is provided, which is applied to a terminal and includes:

acquiring the name of a service access point to be called;

determining a destination IP address meeting the requirement according to the name;

and scheduling the service access point by using the destination IP address meeting the requirement.

In a second aspect, a method for calling a service access point is provided, which is applied to an ingress route, and includes:

receiving a parsing request from a terminal; the analysis request comprises a first parameter, wherein the first parameter is used for indicating the name of a service access point to be called by the terminal;

and sending the destination IP address meeting the requirement to the terminal, and scheduling the service access point by using the destination IP address meeting the requirement by the terminal.

In a third aspect, an apparatus for invoking a service access point is provided, which is applied to a terminal, and includes:

the obtaining module is used for obtaining the name of the service access point to be called;

the first determining module is used for determining a destination IP address meeting the requirement according to the name;

and the scheduling module is used for scheduling the service access point by using the destination IP address meeting the requirement.

In a fourth aspect, an invoking device for a service access point is provided, which is applied to an ingress route, and includes:

a receiving module, configured to receive an analysis request from a terminal; the analysis request comprises a first parameter, and the first parameter is used for indicating the name of a service access point to be called by the terminal;

the second determining module is used for determining a destination IP address meeting the requirement according to the name;

and the second sending module is used for sending the destination IP address meeting the requirement to the terminal, and the terminal utilizes the destination IP address meeting the requirement to schedule the service access point.

In a fifth aspect, embodiments of the present application provide a communication device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method according to the first aspect or implement the steps of the method according to the second aspect.

In a sixth aspect, the present embodiments provide a computer-readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method according to the first aspect, or implement the steps of the method according to the second aspect.

In the embodiment of the application, the terminal can obtain the name of the service access point to be called, determine the destination IP address meeting the requirement according to the name, and schedule the service access point by using the destination IP address meeting the requirement. Therefore, the terminal can automatically select a destination IP address meeting the requirement according to the name of the service access point without scheduling the service access point through a fixed domain name address, and schedule the service access point by using the destination IP address meeting the requirement, thereby ensuring that a corresponding communication link meets the requirement.

Drawings

Fig. 1 is a flowchart of a method for invoking a service access point according to an embodiment of the present disclosure;

fig. 2 is a flowchart of another service access point invoking method according to an embodiment of the present disclosure;

fig. 3 is a schematic structural diagram of an invoking device of a service access point according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of another service access point invoking device provided in an embodiment of the present application;

fig. 5 is a schematic structural diagram of a communication device 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 some, but not all, of the embodiments of the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without making any creative effort belong to the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that embodiments of the application may be practiced in sequences other than those illustrated or described herein, and that the terms "first," "second," and the like are generally used herein in a generic sense and do not limit the number of terms, e.g., the first term can be one or more than one. In addition, "and/or" in the specification and claims means at least one of connected objects, a character "/", and generally means that the former and latter related objects are in an "or" relationship.

In order to solve the problem that a communication link cannot meet requirements when service access point scheduling is performed through a fixed domain name address at present, the embodiment of the present application provides a method for calling a distributed service access point, which can enable a service access point in server less architecture development to be not fixed as a certain domain name address, but can automatically select a destination IP address meeting requirements according to the name of the service access point, and perform scheduling on the service access point by using the destination IP address meeting requirements, thereby ensuring that a corresponding communication link meets requirements.

Optionally, a scenario applicable to the embodiment of the present application includes, but is not limited to, a server architecture. The serverless architecture is an architecture that provides back-end services on demand, with service providers allowing users to write and deploy code without worrying about the underlying infrastructure. The program of the serverless architecture can obtain the backend services from the service provider by means of API calls, from which the service provider will calculate its costs without having to reserve and pay for a fixed amount of bandwidth or servers. The serverless architecture still uses physical servers, but developers do not need to know them.

The method for invoking a service access point provided in the embodiments of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios thereof.

Referring to fig. 1, fig. 1 is a flowchart of a method for invoking a service access point according to an embodiment of the present application, where the method is applied to a terminal, and as shown in fig. 1, the method includes the following steps:

step 11: and acquiring the name of the service access point to be called.

Optionally, the service access point in the embodiment of the present application includes, but is not limited to, an API and the like.

Step 12: and determining the destination IP address meeting the requirement according to the name.

In this step, when determining the destination IP address that meets the requirement, the terminal may directly determine the destination IP address that meets the requirement corresponding to the name according to the pre-stored information, or may obtain the destination IP address that meets the requirement corresponding to the name through the ingress route.

Step 13: and scheduling the service access point by using the destination IP address meeting the requirement.

Optionally, after determining the destination IP address meeting the requirement, the terminal may initiate a scheduling request of the service access point by using the destination IP address meeting the requirement, so as to perform scheduling of the service access point. For example, taking the service access point as the API, the terminal may initiate an API scheduling request by using a destination IP address meeting requirements, so as to perform API scheduling.

In the method for calling the service access point, the terminal can obtain the name of the service access point to be called, determine the destination IP address meeting the requirement according to the name, and schedule the service access point by using the destination IP address meeting the requirement. Therefore, the terminal can automatically select the destination IP address meeting the requirement according to the name of the service access point without scheduling the service access point through the fixed domain name address, and schedule the service access point by using the destination IP address meeting the requirement, thereby ensuring that the corresponding communication link meets the requirement.

In the embodiment of the present application, in order to implement scheduling of service access points according to names of the service access points, all service access points capable of providing a public service need to be uniformly registered and named, that is, the service access points providing the same service have the same name. The registration and naming can be completed by a unified name resolution system, and the name resolution system is responsible for completing the registration, resolution, related query modification and other works of the service access point. If the terminal wants to use the uniform service access point to route and call, the terminal also needs to register an account number with the name resolution system in advance for identity recording.

Optionally, the terminal may obtain a destination IP address meeting the requirement with the aid of the ingress route. In this case, the process of the terminal determining the destination IP address meeting the requirement may include:

the terminal sends an analysis request to the entry route; wherein, the analysis request includes a first parameter for indicating the name;

the terminal receives a destination IP address from the ingress route that meets the requirements.

The destination IP address meeting the requirement may be a destination IP address corresponding to the name, which is determined by the ingress route according to a pre-stored routing table. The pre-stored routing table records a correspondence between the name of the service access point and the destination IP address, and may be obtained by querying the entry route from the name resolution system. In this way, the pre-stored routing table can make the ingress route quickly select the destination IP address meeting the requirement.

Alternatively, the satisfactory destination IP address may be an ingress route requested from a name resolution system according to the name. For example, the ingress route may request a destination IP address that meets the requirements from the name resolution system if the destination IP address that meets the requirements is not obtained from a pre-stored routing table. Further, after the destination IP address meeting the requirement is requested from the name resolution system, the pre-stored routing table may be updated accordingly, that is, the corresponding relationship between the destination IP address meeting the requirement and the corresponding name is newly added.

For example, taking the service access point as an API, the parsing request may be an API parsing request based on Hyper Text Transfer Protocol (HTTP)/HTTPs. Also, the API resolution request no longer specifies a domain name address, but adds a parameter indicating the API name, such as an APIname.

Optionally, in this embodiment of the application, the parsing request may further include a second parameter, where the second parameter is used to indicate an upper cost limit for scheduling of a single access point. For example, the second parameter may be Cost. And the pre-stored routing table also records the corresponding relation between the destination IP address and the cost scheduled by the single access point. Further, the destination IP address meeting the requirement is a destination IP address which is determined by the ingress route according to the pre-stored routing table, corresponds to the name, and meets the requirement of the upper limit of the cost. Therefore, the service access point meeting the user requirement can be controllably selected through the condition of the upper limit of the cost.

Optionally, since there are cases where multiple service providers provide the same service access point, in the pre-stored routing table, the name of the same service access point may correspond to multiple destination IP addresses, that is, the correspondence between the name of the service access point and the destination IP address may be one-to-one or one-to-many. Further, when the ingress route determines that there are a plurality of destination IP addresses corresponding to the name and satisfying the requirement of the upper cost limit, the qualified destination IP address may be one of the plurality of destination IP addresses with the smallest access point response time, or the qualified destination IP address may be one of the plurality of destination IP addresses with the smallest invocation cost. Therefore, under the condition of allowing the upper limit of the cost, the minimum access point response time can be dynamically selected according to the requirement of a user, so that the response time of the service access point is reduced; or, the service access point with the least calling expense can be dynamically selected according to the user requirement, so that the calling cost is reduced.

Optionally, after the destination IP address meeting the requirement is used for scheduling the service access point, when the terminal cannot obtain a response of the corresponding service access point, that is, when the condition that the destination IP address is invalid or the corresponding communication link is not reachable is found, the terminal may send report information to the ingress route, where the report information is used to indicate that the destination IP address meeting the requirement cannot be used for scheduling the corresponding service access point, so that the ingress route updates the pre-stored routing table according to the received report information. For example, a record or flag corresponding to the IP address is deleted from a pre-stored routing table or marked as unreachable, and/or a request is sent to the name resolution system to update the routing table.

For example, taking a service access point as an API, the precondition for scheduling the API by using the present scheme is: all APIs that can provide common services are uniformly registered and named, that is, the APIs that provide the same service have the same name. Registration and naming are completed by a uniform interface Name analysis System (ANS), and the ANS is responsible for completing registration, analysis, related query and modification and the like of the API. The terminal wants to use a unified API to route calls, and also needs to register an account number with the ANS in advance for identity recording.

Optionally, an optional embodiment of the API parsing request in the present application is:

http(s)://APIname&Cost＝XX/？Action＝xx&Parameters

where APIname specifies the API called, identified uniformly by the ANS. Cost indicates the upper limit of the Cost which the call is supposed to use, namely the upper limit of the Cost which can be borne by calling the API once. For example, the parameter value of Cost may be negative, such as-XX, which indicates that the API with the lowest Cost needs to be used, and the maximum value does not exceed XX, and the parameter value of 0 indicates that no Cost is required. The Action represents the operation that the current request needs to perform. Parameters refers to request Parameters, which are composed of common request Parameters and API self-defining Parameters, and the Parameters are separated by using "&".

That is, compared to the existing API request, the API resolution request of the embodiment of the present application cancels Endpoint used for representing the address of the domain name of the calling API, and adds Parameters APIname and Cost, while the meaning and content of Action and Parameters are unchanged.

Optionally, in order to record the API routing information, an API routing table (ARB) may be pre-stored on the ingress route for recording the API name and the corresponding destination IP address. Since there are cases where multiple service providers provide the same API, the same API name may correspond to multiple destination IP addresses. In addition, as shown in table 1 below, a Cost field and a Time field may be included in the API routing table for recording the Cost of a single API call and the API response Time. When all the records meet the user request, the address with the minimum Time is preferentially selected.

TABLE 1 API routing tables

Field(s)	Means of
		APIname	Recording API names
IP	Record the corresponding destination IP address
		Cost	Recording cost of a single API call
Time	Recording API response times

Optionally, the API calling process in this embodiment may include the following steps:

s1: and the terminal acquires the name of the API to be called and sends an API analysis request to the entry route, wherein the API analysis request comprises parameters APIname and Cost. The specific meanings of parameters APIname and Cost are as described above, and are not described herein again.

S2: and the inlet route returns a destination IP address and Cost meeting the requirements to the terminal by inquiring the API routing table stored in advance locally so that the terminal can call the API through the returned destination IP address.

S3: if the local part of the ingress route does not have the destination IP address meeting the requirement, the ingress route can initiate a request to the ANS to obtain the destination IP address meeting the requirement, and the obtained result is returned to the terminal, so that the terminal can call the API through the returned destination IP address. In addition, the ingress route can also update the API routing table stored in advance locally according to the obtained result.

S4: after the terminal calls the API, if finding that the target IP address is invalid or the link is unreachable and the like, the terminal cannot obtain the API response, then reporting to the entry route, deleting the record corresponding to the target IP address or marking the record as unreachable by the entry route, and updating the record corresponding to the APIname by sending a request to the ANS, so that the subsequent API call can be used.

Referring to fig. 2, fig. 2 is a flowchart of a method for invoking a service access point according to an embodiment of the present application, where the method is applied to ingress routing, and as shown in fig. 2, the method includes the following steps:

step 21: a parsing request is received from a terminal.

The analysis request comprises a first parameter, and the first parameter is used for indicating the name of a service access point to be called by the terminal. The service access point includes, but is not limited to, an API or the like.

Step 22: and determining the destination IP address meeting the requirement according to the name.

Step 23: and sending the destination IP address meeting the requirement to the terminal, and scheduling the service access point by using the destination IP address meeting the requirement by the terminal.

It should be noted that, in order to implement scheduling of service access points according to names of the service access points, all service access points that can provide a common service need to be uniformly registered and named, that is, the service access points that provide the same service have the same name. The registration and naming can be completed by a unified name resolution system, and the name resolution system is responsible for completing the registration, resolution, related query and modification and the like of the service access point. If the terminal wants to use the uniform service access point to route and call, the terminal also needs to register an account number with the name resolution system in advance for identity recording.

In the method for calling the service access point, the entry route may receive an analysis request from the terminal, where the analysis request includes a first parameter, the first parameter is used to indicate a name of the service access point that the terminal needs to call, determine a destination IP address meeting requirements according to the name, send the destination IP address meeting the requirements to the terminal, and the terminal schedules the service access point by using the destination IP address meeting the requirements. Therefore, the terminal can automatically select a destination IP address meeting the requirement according to the name of the service access point without scheduling the service access point through a fixed domain name address, and schedule the service access point by using the destination IP address meeting the requirement, thereby ensuring that a corresponding communication link meets the requirement.

Optionally, the determining a destination IP address meeting the requirement according to the name may include at least one of the following:

1) The entry route determines a destination IP address corresponding to the name according to a pre-stored routing table; the pre-stored routing table records a correspondence between the name of the service access point and the destination IP address, which may be obtained by querying the ingress route from the name resolution system. In this way, the pre-stored routing table can make the ingress route quickly select the destination IP address meeting the requirement.

2) The ingress route sends a service request including the name to the name resolution system and receives a destination IP address from the name resolution system that meets the requirements. For example, the ingress route may request a destination IP address that meets the requirements from the name resolution system if the destination IP address that meets the requirements is not obtained from a pre-stored routing table. Further, after the destination IP address meeting the requirement is requested from the name resolution system, the routing table stored in advance may be updated accordingly, that is, the corresponding relationship between the destination IP address meeting the requirement and the corresponding name is newly added.

Optionally, the parsing request further includes a second parameter, where the second parameter is used to indicate an upper limit of a cost for scheduling a single service access point. And the pre-stored routing table also records the corresponding relation between the destination IP address and the expense scheduled by the single access point. The determining the destination IP address corresponding to the name may include: and the entry route determines a destination IP address which corresponds to the name and meets the requirement of the upper limit of the cost according to the prestored routing table. Therefore, the service access point meeting the user requirement can be controllably selected through the condition of the upper limit of the cost.

Optionally, when there are a plurality of destination IP addresses corresponding to the name and satisfying the requirement of the upper cost limit, the satisfactory destination IP address is one of the destination IP addresses with the smallest response time of the access point, or the satisfactory destination IP address is one of the destination IP addresses with the smallest invocation cost. Therefore, under the condition of allowing the upper limit of the cost, the minimum access point response time can be dynamically selected according to the requirement of a user, so that the response time of the service access point is reduced; or, the service access point with the least calling expense can be dynamically selected according to the user requirement, so that the calling cost is reduced.

Alternatively, the ingress route may receive the report information from the terminal; the report information is used for indicating that the dispatching of the corresponding service access point can not be carried out by using the destination IP address meeting the requirement; and updating the pre-stored routing table according to the report information. For example, a record or flag corresponding to the IP address is deleted from a pre-stored routing table or marked as unreachable, and/or a request is sent to the name resolution system to update the routing table.

It should be noted that, in the method for invoking a service access point provided in the embodiment of the present application, the execution subject may be an invoking device of the service access point, or a control module in the invoking device, which is used for executing the method for invoking the service access point. In the embodiment of the present application, a method for executing a service access point by using a calling device is taken as an example to describe a calling device for a service access point provided in the embodiment of the present application.

Referring to fig. 3, fig. 3 is a schematic structural diagram of an invoking device of a service access point according to an embodiment of the present application, where the device is applied to a terminal, and as shown in fig. 3, the invoking device 30 of the service access point includes:

an obtaining module 31, configured to obtain a name of a service access point to be called;

a first determining module 32, configured to determine, according to the name, a destination IP address that meets requirements;

and a scheduling module 32, configured to schedule the service access point by using the destination IP address meeting the requirement.

Optionally, the first determining module 32 includes:

a first sending unit, configured to send an analysis request to the ingress route; wherein, the analysis request includes a first parameter for indicating the name;

a first receiving unit, configured to receive the destination IP address meeting the requirement from the ingress route;

the destination IP address meeting the requirement is the destination IP address corresponding to the name, which is determined by the entry route according to a pre-stored routing table; the pre-stored routing table records the corresponding relation between the name of the service access point and the destination IP address;

or the destination IP address meeting the requirement is obtained by the entry route requested from the name resolution system according to the name.

Optionally, the parsing request further includes a second parameter, where the second parameter is used to indicate an upper limit of a cost for scheduling by a single access point; the pre-stored routing table also records the corresponding relation between the destination IP address and the cost scheduled by the single access point;

the destination IP address meeting the requirement is the destination IP address which is determined by the ingress route according to the pre-stored routing table, corresponds to the name, and meets the requirement of the upper limit of the cost.

Optionally, when there are a plurality of destination IP addresses corresponding to the name and satisfying the requirement of the upper cost limit, the satisfactory destination IP address is one of the destination IP addresses with the smallest response time of the access point, or the satisfactory destination IP address is one of the destination IP addresses with the smallest invocation cost.

Optionally, the invoking device 30 for the service access point further includes:

a first sending module, configured to send report information to the ingress route after scheduling a service access point by using the destination IP address meeting the requirement and when a response of a corresponding service access point cannot be obtained; wherein the report information is used for indicating that the scheduling of the corresponding service access point can not be carried out by using the destination IP address meeting the requirement.

It can be understood that, the calling device 30 of the service access point according to the embodiment of the present application can implement each process of the method embodiment shown in fig. 1, and can achieve the same technical effect, and for avoiding repetition, details are not repeated here.

Referring to fig. 4, fig. 4 is a schematic structural diagram of an invoking device of a service access point according to an embodiment of the present application, the invoking device is applied to an ingress route, and as shown in fig. 4, an invoking device 40 of a service access point includes:

a receiving module 41, configured to receive a parsing request from a terminal; the analysis request comprises a first parameter, and the first parameter is used for indicating the name of a service access point to be called by the terminal;

a second determining module 42, configured to determine, according to the name, a destination IP address that meets the requirement;

a second sending module 43, configured to send the destination IP address meeting the requirement to the terminal, and the terminal performs scheduling of the service access point by using the destination IP address meeting the requirement.

Optionally, the second determining module 42 is specifically configured to: determining a destination IP address corresponding to the name according to a pre-stored routing table; wherein, the pre-stored routing table records the corresponding relationship between the name of the service access point and the destination IP address.

Optionally, the second determining module 42 includes:

a second sending unit, configured to send a service request including the name to a name resolution system;

a second receiving unit, configured to receive the destination IP address meeting the requirement from the name resolution system.

Optionally, the analysis request further includes a second parameter, where the second parameter is used to indicate an upper limit of a cost for scheduling a single service access point; the pre-stored routing table also records the corresponding relation between the destination IP address and the cost scheduled by the single access point; the second determining module 42 is specifically configured to: and determining a destination IP address which corresponds to the name and meets the requirement of the upper limit of the cost according to the pre-stored routing table.

Optionally, when there are a plurality of destination IP addresses corresponding to the name and satisfying the requirement of the upper cost limit, the destination IP address meeting the requirement is the one with the smallest response time of the access point in the plurality of destination IP addresses, or the destination IP address meeting the requirement is the one with the smallest call cost in the plurality of destination IP addresses.

Optionally, the receiving module 41 is further configured to receive report information from the terminal; the report information is used for indicating that the dispatching of the corresponding service access point can not be carried out by utilizing the destination IP address which meets the requirement;

the invoking means 40 of the service access point further comprise: and the updating module is used for updating the pre-stored routing table according to the report information.

It can be understood that the calling device 40 of the service access point in the embodiment of the present application can implement the processes of the method embodiment shown in fig. 2, and can achieve the same technical effect, and for avoiding repetition, details are not described here again.

Optionally, as shown in fig. 5, an embodiment of the present application further provides a communication device 50, which includes a processor 51, a memory 52, and a program or an instruction stored in the memory 52 and executable on the processor 51, for example, when the communication device 50 is a terminal, the program or the instruction is executed by the processor 51 to implement the processes of the embodiment of the method in fig. 1, and the same technical effect can be achieved. When the communication device 50 is an ingress router, the program or the instructions are executed by the processor 51 to implement the processes of the method embodiment shown in fig. 2, and the same technical effect can be achieved.

The embodiment of the present application further provides a computer-readable storage medium, where a program or an instruction is stored, and when the program or the instruction is executed by a processor, the process of the embodiment of the method shown in fig. 1 may be implemented, or the process of the embodiment of the method shown in fig. 2 may be implemented, and the same technical effect may be achieved, and in order to avoid repetition, details are not repeated here.

Computer-readable media include permanent and non-permanent, removable and non-removable media and 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 Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

It should be noted that, in this document, 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 one of 8230, and" comprising 8230does not exclude the presence of additional like elements in a process, method, article, or apparatus comprising the element.

The above-mentioned serial numbers of the embodiments of the present application are merely for description, and do not represent the advantages and disadvantages of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application or portions thereof that contribute to the prior art may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a service classification device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the method according to the embodiments of the present application.

The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.

Claims

1. A calling method of a service access point is applied to a terminal, and is characterized by comprising the following steps:

acquiring the name of a service access point to be called;

2. The method of claim 1, wherein determining a satisfactory destination IP address from the name comprises:

sending an analysis request to an ingress route; the analysis request comprises a first parameter used for indicating the name;

receiving the satisfactory destination IP address from the ingress route;

the destination IP address meeting the requirement is the destination IP address corresponding to the name, which is determined by the entry router according to a pre-stored routing table; the pre-stored routing table records the corresponding relation between the name of the service access point and the destination IP address;

or, the destination IP address meeting the requirement is requested by the ingress route from the name resolution system according to the name.

3. The method of claim 2, wherein the parsing request further includes a second parameter, and the second parameter is used to indicate an upper cost limit for single access point scheduling; the pre-stored routing table also records the corresponding relation between the destination IP address and the cost scheduled by the single access point;

4. The method of claim 3, wherein when there are a plurality of destination IP addresses corresponding to the name and satisfying the requirement of the upper cost limit, the qualified destination IP address is one of the plurality of destination IP addresses with a minimum response time of the access point, or the qualified destination IP address is one of the plurality of destination IP addresses with a minimum call cost.

5. The method of claim 2, wherein after scheduling the serving access points using the satisfactory destination IP addresses, when the terminal cannot obtain a response of the corresponding serving access point, the method further comprises:

sending report information to the ingress route; wherein the report information is used for indicating that the dispatching of the corresponding service access point can not be carried out by using the destination IP address meeting the requirement.

6. A method for calling a service access point, applied to an ingress route, comprising:

determining a destination IP address meeting the requirements according to the name;

7. The method of claim 6, wherein determining a satisfactory destination IP address based on the name comprises at least one of:

determining a destination IP address corresponding to the name according to a pre-stored routing table; wherein, the pre-stored routing table records the corresponding relation between the name of the service access point and the destination IP address;

sending a service request including the name to a name resolution system and receiving the qualified destination IP address from the name resolution system.

8. The method of claim 6,

the analysis request also comprises a second parameter, and the second parameter is used for indicating the upper limit of the cost scheduled by the single service access point; the pre-stored routing table also records the corresponding relation between the destination IP address and the cost scheduled by the single access point; the determining, according to a pre-stored routing table, a destination IP address corresponding to the name includes:

and determining a destination IP address which corresponds to the name and meets the requirement of the upper limit of the expense according to the pre-stored routing table.

9. The method of claim 8, wherein when there are a plurality of destination IP addresses corresponding to the name and satisfying the requirement of the upper cost limit, the qualified destination IP address is one of the plurality of destination IP addresses with a minimum response time of the access point, or the qualified destination IP address is one of the plurality of destination IP addresses with a minimum call cost.

10. The method of claim 7, further comprising:

receiving report information from the terminal; wherein, the report information is used for indicating that the dispatching of the corresponding service access point can not be carried out by using the destination IP address which meets the requirement;

and updating the pre-stored routing table according to the report information.

11. A calling device of a service access point is applied to a terminal, and is characterized by comprising:

12. The apparatus of claim 11, wherein the first determining module comprises:

a first sending unit, configured to send an analysis request to an ingress route; the analysis request comprises a first parameter used for indicating the name;

13. The apparatus of claim 12, wherein the parsing request further comprises a second parameter indicating an upper cost limit for single access point scheduling; the pre-stored routing table also records the corresponding relation between the destination IP address and the cost scheduled by the single access point;

14. The apparatus of claim 13, wherein when there are a plurality of destination IP addresses corresponding to the name and satisfying the requirement of the upper cost limit, the qualified destination IP address is one of the plurality of destination IP addresses with a minimum response time of the access point, or the qualified destination IP address is one of the plurality of destination IP addresses with a minimum call cost.

15. The apparatus of claim 12, further comprising:

a first sending module, configured to send report information to the ingress route after scheduling of the service access point by using the destination IP address meeting the requirement and when a response of the corresponding service access point cannot be obtained; wherein the report information is used for indicating that the dispatching of the corresponding service access point can not be carried out by using the destination IP address meeting the requirement.

16. A service access point invoking device for an ingress route, comprising:

17. The apparatus of claim 16,

the second determining module is specifically configured to: determining a destination IP address corresponding to the name according to a pre-stored routing table; wherein, the pre-stored routing table records the corresponding relation between the name of the service access point and the destination IP address;

alternatively, the first and second electrodes may be,

the second determining module comprises:

18. The apparatus of claim 16,

the analysis request also comprises a second parameter, and the second parameter is used for indicating the upper limit of the cost scheduled by the single service access point; the pre-stored routing table also records the corresponding relation between the destination IP address and the cost scheduled by the single access point;

the second determining module is specifically configured to: and determining a destination IP address which corresponds to the name and meets the requirement of the upper limit of the cost according to the pre-stored routing table.

19. A communications device comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions when executed by the processor implementing the steps of the method for invoking a service access point according to any one of claims 1-5 or the steps of the method for invoking a service access point according to any one of claims 6-10.

20. A computer readable storage medium, characterized in that a program or instructions are stored on the computer readable storage medium, which program or instructions, when executed by a processor, implement the steps of the method of invoking of a service access point according to any of claims 1-5 or the steps of the method of invoking of a service access point according to any of claims 6-10.