CN105245534A - A call result feedback method, server, terminal, system - Google Patents

Abstract

The invention discloses a call result feedback method, a server, a terminal and a system. The method comprises the steps that a call result list is set, wherein the call result list comprises more than one call result, and the corresponding relationship between a call result ID and a call result content is recorded in each call result; the information recorded by the call result in the call result list is encapsulated through a predetermined rule; and the encapsulated call result is sent to a call request end.

Description

A call result feedback method, server, terminal, system

technical field

The invention relates to a call result feedback technology, in particular to a call result feedback method, server, terminal and system.

Background technique

With the continuous integration of Internet and telecommunication network, data service and traditional voice service, in order to adapt to the rapid development of cloud computing industry, the platform-as-a-service (PaaS, Platform as a Service) trend of traditional telecommunication service enterprises is becoming more and more obvious. PaaS can integrate various existing business capabilities. For example, through the application programming interface (API, Application Programming Interface), the telecommunications call capability is opened to users of large and medium-sized enterprises and individual developers, and personalized and precise services are provided.

Some call capability open platforms, after receiving and completing the call from the call requesting end, fail to feed back the call result in time, so that the call requesting end cannot know the final situation of the call. Especially in some key transactional calls, such as security authentication service and payment confirmation service, when the call fails and there is no timely remedy or reminder, it will affect the user's continued use and reduce the user's experience.

For this reason, there is a way to actively push the call result. The telecom platform sends the successful or failed call result to the data platform, and the data platform sends the call result to the call requesting server through the hypertext transfer protocol (HTTP, HyperTextTransferProtocol) asynchronous communication interface, so that the call requesting end can know And record the call result of each call request, find abnormalities in time and take remedial measures such as chasing the call.

However, the existing call result notification method does not fully consider the three factors of efficiency, standard and completeness. Specifically, 1) for efficiency, the existing call result notification method is to save the call result to a file first after obtaining the call result, and upload it to the call requesting end through a file transfer protocol (FTP, FileTransferProtocol) mode, and another method is to pass an alarm message Notifying the call requesting end of the failed call result, these two methods will not only reduce the timeliness and reliability, but also require the calling requesting end to analyze the result file and the short message. 2) For the standard, the existing call result notification method is to directly transmit the call failure alarm content in the text message. There is no unified standard for how to express the call alarm level, failure type, business category and other information. Accurately parse out each attribute of the alarm, which brings difficulties to function expansion. 3) For integrity, the existing call result notification method is to directly transmit the call failure alarm content in the text message. The organization of the alarm content is uneven, and the length of the text message is limited, and most of them do not contain complete call alarm information, such as alarm identification, alarm level, failure type, business category, etc., resulting in the inability to identify and miss key information at the call requesting end, making subsequent remedial processing impossible.

Contents of the invention

In order to solve the above technical problems, the embodiments of the present invention provide a call result feedback method, server, terminal, and system.

The call result feedback method provided by the embodiment of the present invention includes:

A call result list is set, the call result list includes more than one call result, and each call result record has a corresponding relationship between the call result ID and the call result content;

encapsulating the information recorded in the call result in the call result list through predetermined rules;

Send the encapsulated call result to the call requesting end.

In an embodiment of the present invention, the method further includes:

When setting the calling list, the variation in the content of the calling result is set as a corresponding replacement parameter value.

In the embodiment of the present invention, the encapsulation of the information recorded in the call result in the call result list by predetermined rules includes:

Encapsulate the following information in the message: callback interface, call result ID, call failure level, call failure type, service type, alternative parameter value, custom private data.

The call result feedback method provided by another embodiment of the present invention includes:

receiving the encapsulated call result;

The call result is analyzed to obtain the following information in the call result: callback interface, call result ID, call failure level, call failure type, service type, alternative parameter value, and custom private data.

In an embodiment of the present invention, the method further includes:

According to the service type and call failure level, the call result is filtered and then prompted.

The server provided by the embodiment of the present invention includes:

The setting unit is used to set the call result list, the call result list includes more than one call result, and each call result record has a corresponding relationship between the call result ID and the call result content;

An encapsulating unit, configured to encapsulate the information recorded in the call result in the call result list according to a predetermined rule;

The sending unit is configured to send the encapsulated call result to the call requesting end.

In the embodiment of the present invention, the setting unit is further configured to set the variation in the content of the call result as a corresponding replacement parameter value when setting the call list.

In the embodiment of the present invention, the encapsulation unit is further configured to encapsulate the following information in the message: callback interface, call result ID, call failure level, call failure type, service type, alternative parameter value, and self-defined private data.

The terminal provided by the embodiment of the present invention includes:

a receiving unit, configured to receive the encapsulated call result;

The parsing unit is configured to parse the call result to obtain the following information in the call result: callback interface, call result ID, call failure level, call failure type, service type, alternative parameter value, and custom private data.

In the embodiment of the present invention, the terminal further includes:

The filtering unit is configured to filter the call result according to the service type and call failure level and then give a prompt.

The call result feedback system provided by the embodiment of the present invention includes the above-mentioned server and terminal.

In the technical solution of the embodiment of the present invention, the server first sets the call result list, and the call result list includes more than one call result, and each call result record has a corresponding relationship between the call result ID and the call result content; then, the The information recorded in the call result in the call result list is encapsulated by predetermined rules, specifically, the following information is encapsulated in the message: callback interface, call result ID, call failure level, call failure type, service type, alternative Parameter values, custom private data. Finally, the encapsulated call result will be sent to the call requesting end. This makes up for the shortcomings of the existing call result notification methods, improves the efficiency of call result notification, establishes the standard for call result information transmission, ensures the integrity of call results, especially failure alarm information, and identifies and filters failures for the call requesting end. Extended functions such as alarm data provide support.

Description of drawings

FIG. 1 is a schematic flowchart of a call result feedback method according to Embodiment 1 of the present invention;

FIG. 2 is a schematic flowchart of a call result feedback method according to Embodiment 2 of the present invention;

FIG. 3 is a schematic diagram of the structural composition of a server according to an embodiment of the present invention;

FIG. 4 is a schematic diagram of the structural composition of a terminal according to an embodiment of the present invention;

Fig. 5 is a schematic diagram of the structural composition of the call result feedback system according to the embodiment of the present invention.

detailed description

In order to understand the characteristics and technical contents of the embodiments of the present invention in more detail, the implementation of the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. The attached drawings are only for reference and description, and are not intended to limit the embodiments of the present invention.

FIG. 1 is a schematic flow chart of a call result feedback method in Embodiment 1 of the present invention. The call result feedback method in the embodiment of the present invention is applied to the server side. As shown in FIG. 1 , the call result feedback method includes the following steps:

Step 101: Set up a call result list, the call result list includes more than one call result, and each call result records the corresponding relationship between the call result ID and the call result content.

In the embodiment of the present invention, when the call requesting end initiates a call request to the server, the server processes the call request and obtains a call result, and then stores all the call results in a call result list.

In the embodiment of the present invention, the server is the call capability platform, and the call result list is deployed on the call capability platform. The call result list includes more than one call result, and each call result records the corresponding relationship between the call result ID and the call result content. During specific implementation, the call result list may be recorded through but not limited to the database.

In the embodiment of the present invention, the call requesting end may be a communication electronic device such as a mobile phone or a notebook computer.

When setting the calling list, the variation in the content of the calling result is set as a corresponding replacement parameter value. In this way, the content of the call result can be further simplified.

Step 102: Encapsulate the information recorded in the call result in the call result list according to a predetermined rule.

In the embodiment of the present invention, the predetermined rule is also referred to as the asynchronous transfer protocol of HTTP. Specifically, the following information is encapsulated in the message: callback interface, call result ID, call failure level, call failure type, service type, and alternative parameters value, custom private data.

In the above solution, the type of call failure may be: call does not arrive, the user shuts down, is not in the service area, is in arrears, and the user refuses to answer, etc.

During specific implementation, a certain number of bytes can be allocated to each of the above information, and the specific allocation method can be set in advance, and different bytes can be set according to different specific business scenarios to record each information.

The HTTP asynchronous transmission protocol in the embodiment of the present invention will be described in detail below in conjunction with specific information.

The following are the specific descriptions of the header, request body, and response body:

Baotou:

Contet_Type: text/plain

Request body:

Attributes Types of constraint illustrate action String required Callback interface (voiceCapctha) callId String required The callId of the corresponding interface (the unique identifier of a call) number String required outbound number status String required Outgoing call status 0 Normal call 1 Called unanswered 2 Outgoing call failed...

duration String required Call duration (seconds) userData String optional Custom private data (consistent with the private data of the voice verification code interface)

Table 1

The attributes shown in the above Table 1 can be understood by referring to the corresponding description part, and will not be repeated here. Those skilled in the art should understand that Table 1 only shows part of the information in the call result, and other information can be carried out correspondingly. setting.

An example of encapsulating the information recorded in the request packet according to Table 1 is as follows:

As mentioned above, the request body includes the following information: action, number, callId, status, and duration, where action is set to voiceCapctha, number is set to 13800000000, callId is set to 299uikKMMU890olml999, status is set to 0, and duration is set to 30.

It is worth noting that the above encapsulation only shows part of the information in the call result, and other information can be set accordingly.

Response body:

Table 2

The attributes shown in the above Table 2 can be understood by referring to the corresponding description part, and will not be repeated here. Those skilled in the art should understand that Table 2 only shows part of the information in the call result, and other information can be carried out correspondingly. setting.

An example of encapsulating the information recorded in the response packet according to Table 2 is as follows:

As mentioned above, the response packet body includes the following information: callId and statusCode, wherein the callId is set to 299uikKMMU890olml999, and the statusCode is set to 0000.

It is worth noting that the above encapsulation only shows part of the information in the call result, and other information can be set accordingly.

Step 103: Send the encapsulated call result to the call requesting end.

In the embodiment of the present invention, after the call requesting end receives the call result, it analyzes the call result to obtain the following information in the call result: callback interface, call result ID, call failure level, call failure type, service type , alternative parameter values, custom private data. In addition, the call requesting end filters the call result according to the service type and call failure level, and then prompts.

The technical solutions of the embodiments of the present invention make up for the deficiencies of the existing call result notification methods, improve the efficiency of call result notification, establish the standard for call result information transmission, and ensure the integrity of call results, especially failure alarm information. Provide support for extended functions such as requester identification and filtering failure alarm data.

FIG. 2 is a schematic flowchart of a call result feedback method in Embodiment 2 of the present invention. The call result feedback method in this example is applied to a terminal. As shown in FIG. 2 , the call result feedback method includes the following steps:

Step 201: Receive the encapsulated call result.

In the embodiment of the present invention, the server encapsulates the call result, and then sends it to the terminal.

Step 202: Analyze the call result to obtain the following information in the call result: callback interface, call result ID, call failure level, call failure type, service type, alternative parameter value, custom private data.

In the embodiment of the present invention, the terminal may filter the call result according to the service type and call failure level and then prompt.

Fig. 3 is a schematic diagram of the structural composition of a server according to an embodiment of the present invention. As shown in Fig. 3, the server includes:

The setting unit 31 is used to set the call result list, the call result list includes more than one call result, and each call result record has a corresponding relationship between the call result ID and the call result content;

An encapsulating unit 32, configured to encapsulate the information recorded in the call result in the call result list according to a predetermined rule;

The sending unit 33 is configured to send the encapsulated call result to the call requesting end.

The setting unit 31 is further configured to set the variation in the content of the call result as a corresponding replacement parameter value when setting the call list.

The encapsulation unit 32 is further configured to encapsulate the following information in the message: callback interface, call result ID, call failure level, call failure type, service type, alternative parameter value, and self-defined private data.

Those skilled in the art should understand that the implementation functions of each unit in the server shown in FIG. 3 can be understood with reference to the relevant description of the aforementioned call result feedback method. The functions of each unit in the server shown in FIG. 3 can be realized by programs running on the processor, or by specific logic circuits.

FIG. 4 is a schematic diagram of the structural composition of a terminal according to an embodiment of the present invention. As shown in FIG. 4, the terminal includes:

a receiving unit 41, configured to receive the encapsulated call result;

The parsing unit 42 is configured to parse the call result to obtain the following information in the call result: callback interface, call result ID, call failure level, call failure type, service type, alternative parameter value, custom private data .

The terminal also includes:

The filtering unit 43 is configured to filter the call result according to the service type and call failure level and then give a prompt.

Those skilled in the art should understand that the functions implemented by each unit in the terminal shown in FIG. 4 can be understood with reference to the relevant description of the aforementioned call result feedback method. The functions of each unit in the terminal shown in FIG. 4 can be realized by a program running on the processor, or can be realized by a specific logic circuit.

Fig. 5 is a schematic diagram of the structural composition of the call result feedback system according to the embodiment of the present invention. As shown in Fig. 5, the call result feedback system includes:

Server 51 is used to set the call result list, and the call result list includes more than one call result, and each call result record has a corresponding relationship between the call result ID and the call result content; the call result in the call result list is recorded The information is packaged according to predetermined rules; the packaged call result is sent to the terminal 52.

Terminal 52, configured to receive the encapsulated call result; analyze the call result to obtain the following information in the call result: callback interface, call result ID, call failure level, call failure type, service type, alternative parameters value, custom private data.

The technical solutions described in the embodiments of the present invention may be combined arbitrarily if there is no conflict.

In the several embodiments provided by the present invention, it should be understood that the disclosed methods and smart devices can be implemented in other ways. The device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods, such as: multiple units or components can be combined, or May be integrated into another system, or some features may be ignored, or not implemented. In addition, the coupling, or direct coupling, or communication connection between the components shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be electrical, mechanical or other forms of.

The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed to multiple network units; Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present invention may be fully integrated into a second processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; The above-mentioned integrated units can be implemented in the form of hardware, or in the form of hardware plus software functional units.

The above is only a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Anyone skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present invention. Should be covered within the protection scope of the present invention.

Claims (11)

1. call out a result feedback method, it is characterized in that, described method comprises:

Arrange calling the results list, described calling the results list comprises one or more calling result, and every bar calling outcome record has calling result ID and the corresponding relation calling out resultant content;

By the information that the calling result in described calling the results list records, encapsulated by predetermined rule;

Calling result after encapsulation is sent to call request end.

2. calling result feedback method according to claim 1, it is characterized in that, described method also comprises:

When described call list is set, the variable quantity in described calling resultant content is set to corresponding alternate parameter value.

3. calling result feedback method according to claim 2, is characterized in that, described information calling result in described calling the results list recorded, is encapsulated by predetermined rule, comprising:

By following Information encapsulation in message: callback interface, calling result ID, call failure rank, call failure type, type of service, alternate parameter value, self-defined private data.

4. call out a result feedback method, it is characterized in that, described method comprises:

Receive the calling result through encapsulation;

Described calling result is resolved, obtains the following information in described calling result: callback interface, calling result ID, call failure rank, call failure type, type of service, alternate parameter value, self-defined private data.

5. calling result feedback method according to claim 4, it is characterized in that, described method also comprises:

According to described type of service, call failure rank, point out after described calling result is filtered.

6. a server, is characterized in that, described server comprises:

Setting unit, for arranging calling the results list, described calling the results list comprises one or more calling result, and every bar calling outcome record has calling result ID and the corresponding relation calling out resultant content;

Encapsulation unit, for the information calling result in described calling the results list recorded, is encapsulated by predetermined rule;

Transmitting element, for sending to call request end by the calling result after encapsulation.

7. server according to claim 6, is characterized in that, described setting unit, time also for arranging described call list, the variable quantity in described calling resultant content is set to corresponding alternate parameter value.

8. server according to claim 7, it is characterized in that, described encapsulation unit, also for by following Information encapsulation in message: callback interface, calling result ID, call failure rank, call failure type, type of service, alternate parameter value, self-defined private data.

9. a terminal, is characterized in that, described terminal comprises:

Receiving element, for receiving the calling result through encapsulation;

Resolution unit, for resolving described calling result, obtains the following information in described calling result: callback interface, calling result ID, call failure rank, call failure type, type of service, alternate parameter value, self-defined private data.

10. terminal according to claim 9, is characterized in that, described terminal also comprises:

Filter element, for according to described type of service, call failure rank, points out after filtering to described calling result.

11. 1 kinds of calling result feedback systems, it is characterized in that, described system comprises the server described in any one of claim 6 to 8, and the terminal described in claim 9 or 10.