WO2018196686A1

WO2018196686A1 - Service response method and middleware thereof

Info

Publication number: WO2018196686A1
Application number: PCT/CN2018/083860
Authority: WO
Inventors: 鲜丹
Original assignee: 威富通科技有限公司
Priority date: 2017-04-27
Filing date: 2018-04-20
Publication date: 2018-11-01
Also published as: CN107196917B; CN107196917A

Abstract

The present solution applies to the field of network technology and provides a service response method and middleware thereof. The method comprises: receiving registration information sent by a user; adding, according to an identifier and log-in information, an additional service to a corresponding responsive service list for the user on a third party service platform, wherein the additional service is a service in addition to those on the responsive service list; receiving a service request sent by the user, and determining whether the service type corresponding to the service request is the additional service; and if so, responding to the service request via middleware. According to the present invention, a user can register with middleware, obtain an additional service permission for a third party platform, and issue a respective additional service request using the third party service platform. The third party service platform receives the additional service request, and then assigns the same to the middleware to respond to. In this way, the present invention provides more services to a user, and solves problems of current third party service platforms such as failure to satisfy a large number of service requests from a user and poor user experience.

Description

Service response method and middleware thereof

Technical field

The invention belongs to the technical field of networks, and in particular relates to a service response method and a middleware thereof.

Background technique

With the increasing variety of network services, users often need to obtain corresponding network services through third-party service platforms. However, due to the long development cycle of the third-party service platform and the large update cost, it is impossible to update the service types of the platform in time.

For example, when the third-party service platform is the WeChat public number platform, the user can only select the required services in the service buttons provided by the platform, such as group messaging information, answering fan questions, and the like, but for personalization. Additional services such as services or special services will not be able to respond. For example, the number of fans of users is gradually increasing. Fans in the WeChat public account need to be managed and relevant fan analysis is performed. Users can only manually obtain fan data and manually or otherwise The software is completed and cannot be directly operated through the WeChat service platform. It can be seen that the existing third-party service platform cannot satisfy the user's multiple types of service requests, and the user experience is low.

technical problem

The purpose of the embodiments of the present invention is to provide a middleware-based service response method and a middleware thereof, which are intended to solve the problem that the existing third-party service platform cannot satisfy a large number of service requests of the user and has low user experience.

Technical solution

An embodiment of the present invention provides a service response method, where the service response method includes:

Receiving registration information sent by the user, where the registration information includes an identifier of the third-party service platform and login information of the user logging in to the third-party service platform;

Adding, according to the identifier and the login information, an additional service to the list of respondable services corresponding to the user on the third-party service platform; wherein the additional service is another service outside the list of respondable services;

Receiving a service request sent by the user, and determining whether the service type corresponding to the service request is the additional service;

If the service type is an additional service, the service request is responded to by the middleware.

Beneficial effect

A service response method and an intermediate piece thereof provided by embodiments of the present invention have the following beneficial effects:

In the embodiment of the present invention, the user obtains additional service rights of the third-party platform by registering in the middleware, and uses the third-party service platform to initiate a corresponding additional service request, and the third-party service platform will hand over the additional service request after receiving the additional service request. The middleware responds to provide more services to the user. It can be seen that, in the embodiment of the present invention, the user does not need to install or use a new third-party service platform, and only needs to perform related registration operations, and then can perform various service requests through the original third-party service platform, thereby improving user experience. On the other hand, because the middleware performs service update and the addition is more flexible, the user's service demand can be used in time, and the update efficiency and user experience of the third-party service platform are improved.

DRAWINGS

FIG. 1 is a flowchart of a service response method according to an embodiment of the present invention;

2 is a flowchart of a service response method according to another embodiment of the present invention;

FIG. 3 is a schematic diagram of a specific implementation of S207 in a service response method according to another embodiment of the present invention;

FIG. 3b is a flow chart of interaction of a middleware response interactive service request in a service response method according to another embodiment of the present invention; FIG.

FIG. 4 is a schematic diagram of a specific implementation of S207 in a service response method according to another embodiment of the present invention;

4b is a flow chart of interaction of a middleware in response to an external link access service request in a service response method according to another embodiment of the present invention;

FIG. 5 is a schematic diagram of a specific implementation of S104 in a service response method according to another embodiment of the present invention;

FIG. 5b is a flow chart of interaction of a middleware response message push service request in a service response method according to another embodiment of the present invention;

FIG. 6 is a schematic structural diagram of an intermediate member according to an embodiment of the present invention.

Embodiments of the invention

FIG. 1 is a flowchart of an implementation of a service response method according to an embodiment of the present invention, which is described in detail as follows:

In S101, the registration information sent by the user is received; wherein the registration information includes an identifier of the third-party service platform and login information of the user logging in to the third-party service platform.

In this embodiment, the user sends a registration message to the middleware through the communication network. After receiving the registration message, the middleware extracts the identifier of the third-party service platform included in the registration information and the login information of the user to the third-party service platform.

In this embodiment, since the middleware needs to provide an additional service for the user in the third-party service platform, it is necessary to first determine the third-party service platform that the user needs to add the service according to the identifier of the third-party service platform, and according to the user. The related service addition operation is performed on the login information corresponding to the third service platform. For example, if the middleware can provide additional services on three third-party service platforms: WeChat, Alipay, and Weibo, the registration information sent by the user indicates a third-party service platform that needs to perform service extension, such as WeChat, and provides login WeChat. Login information.

Optionally, in this embodiment, the middleware's memory stores an extensible service list, and the extensible service list records the identifier of the third-party service platform that the middleware has been authorized to add additional services to. After receiving the registration information sent by the user, the middleware extracts the identifier of the third-party service platform included in the registration information, and queries whether the identifier in the registration information is included in the extensible service list. If the identifier is included in the extensible service list, the relevant step of S102 is performed; otherwise, if the identifier is not included in the extensible service list, the unsupported information is returned to the user or forwarded to other third-party services that can support the identifier. The middleware of the platform can also directly ignore the registration information and not respond.

In this embodiment, the middleware can be connected to a third-party server or a user's terminal device. If the middleware is deployed in the third-party server, the user sends the registration information to the middleware server, and the middleware server sends the registration information to the middleware in the corresponding third-party server according to the third-party server platform identifier in the registration information. The middleware receives the registration information sent by the user through the middleware server, and performs related service response operations. If the middleware is deployed in the terminal device of the user, the registration information sent by the user is directly received through the communication channel inside the user terminal device.

In this embodiment, if the middleware is deployed in a communication network between the user and the third-party server, the user may directly send registration information to the user based on the network address of the middleware or the registration platform of the middleware; The three-party service platform is forwarded to the corresponding middleware through the third-party service platform. Optionally, in this case, the user does not need to input the identifier of the third-party service platform when generating the registration information, and the third-party service platform receives the registration. After the information, the corresponding identifier is added to the registration information sent by the user, and the information is forwarded to the middleware.

In S102, adding, according to the identifier and the login information, an additional service to the list of respondable services corresponding to the user on the third-party service platform; wherein the additional service is other than the list of respondable services service.

In this embodiment, after obtaining the registration information sent by the user, the middleware extracts the identifier of the third-party service platform in the registration information and the corresponding login information, and determines the third-party service platform of the extended service according to the identifier. And determining, according to the login information of the user, the account information corresponding to the user in the third-party platform.

In this embodiment, the middleware determines a list of respondable services of the user on the third-party service platform according to the identifier of the third-party platform, and determines a corresponding additional service item according to the list of respondable services.

In this embodiment, the user needs to use a third-party service platform to perform related service operations, and should have a corresponding personal account, and each account will correspond to a list of respondable services, wherein the respondable service list is used to indicate the third party. The type of service request that the service platform can respond to.

In this embodiment, since the middleware is used to provide additional service content for the third-party service platform, and the additional service content is that the user cannot operate within the corresponding account authority, in order to enable the third-party service platform to process The related service request, and the corresponding service request is handed over to the middleware for response operation, so the additional service is added to the user's list of respondable services.

In S103, a service request sent by the user is received, and it is determined whether the service type corresponding to the service request is the additional service.

In this embodiment, after obtaining the usage rights of the additional service, the user may perform corresponding additional service operations in the third-party service platform. Therefore, the types of services initiated by the user in the third-party service platform include two types of services that are originally responsive to the service list and additional services that are added, and it should be noted that the normal service is specifically that the user is not working on the middleware. Services that have been enjoyed before registration.

In this embodiment, after receiving the service request sent by the user, the middleware determines whether the service request belongs to the additional service, and if yes, performs the related operation of S104, if not, does not respond, and is handed over to the third party. The service platform directly performs related service responses. The user may initiate a related service request through a third-party service platform, or may send a service request to the middleware through other means, such as directly communicating to the middleware or through other third-party service platforms.

In S104, if the service type is an additional service, the service request is responded to by the middleware.

In this embodiment, the middleware has determined that the service request is an additional service according to the service type of the service request, and then performs a corresponding service flow operation according to different service types, thereby responding to the user's service request.

It can be seen that the service response method provided by the embodiment of the present invention obtains the additional service authority of the third-party platform by registering in the middleware, and initiates the corresponding additional service request by using the third-party service platform, and the third-party service platform. After receiving an additional service request, it will be handed over to the middleware to respond, thus providing more services to the user. It can be seen that, in the embodiment of the present invention, the user does not need to install or use a new third-party service platform, and only needs to perform related registration operations, and then can perform various service requests through the original third-party service platform, thereby improving user experience. On the other hand, because the middleware performs service update and the addition is more flexible, the user's service demand can be used in time, and the update efficiency and user experience of the third-party service platform are improved.

FIG. 2 is a flowchart of a specific implementation of a service response method according to another embodiment of the present invention. Referring to FIG. 2, with respect to the previous embodiment, a middleware-based service response method provided by this embodiment includes the following steps, which are described in detail as follows: Further, as another embodiment of the present invention, the login information is used. The user identification information and the user password information are included; before the middleware responds to the service request, the method further includes:

In S204, user identification information and user password information included in the service request are extracted.

In this embodiment, the registration information sent by the user when the middleware is registered will include login information of the third-party service platform, wherein the login information will include the user identification information and the user password information. The user identification information includes, but is not limited to, a user name, a user identity number (identity, ID number), an associated mobile phone number, a mailbox, and the like. The user password information includes, but is not limited to, user login password information, public key information of the user communicating with the third party service platform, and private key information.

In this embodiment, since the user initiates the service request through the third-party service platform, it belongs to an interactive content between the user and the third-party service platform. Therefore, the service request will contain the user's identification information and the user's password information in order to indicate the account of the user corresponding to the service request.

In this embodiment, the middleware will extract the user identification information and the user password information from the service request by using a preset user parameter extraction rule. The preset user parameter extraction rule may be: directly reading the corresponding field content in the service request, and using the content of the field as the user identification information or the user password information; if the service request has been encrypted, the middleware may The service request is decrypted by a preset decryption key, and then the related information is read, the decryption key being a middleware and a key agreed by the third party service platform for decrypting the information.

In S205, the user identification information included in the service request is matched with the user identification information of the login information, and the user password information included in the service request is matched with the user password information included in the login information.

In this embodiment, the middleware matches the user identifier included in the service request with the user identifier information of the login information, and matches the user password information included in the service request and the user password information of the login information, if both match successfully. If the matching request is unsuccessful, that is, if the user identification information does not match or the user password information does not match, it is determined that the service request is incorrect or illegal.

In this embodiment, the matching manner includes, but is not limited to, directly comparing whether the two information are consistent, or mapping the information through the corresponding mapping rule, and whether the obtained result is consistent.

In S206, it is determined whether to respond to the service request by the middleware according to the matching result.

In this embodiment, if the user identification information and the user password information included in the service request are all successfully matched, the service request is responded; otherwise, if the user identification information or the user password information included in the service request is unsuccessful, the identity information is returned. There is a misinformation to inform the user that the correct service request needs to be regenerated, or the service request is directly discarded, and no related processing is performed.

In the embodiment of the present invention, the middleware matches the user identification information and the user password information in the service request to match the registered corresponding information, thereby determining whether the service request is legal, and improving the security of the middleware response service. Sexuality, to avoid criminals posing as legitimate users to initiate related service operations.

It should be noted that, in this embodiment, since the related operations of S201 and S101 are completed identically, the related operations of S202 and S102 are completely the same. The related operations of S203 and S103 are exactly the same, and the related operations of S207 and S104 are completely the same. Therefore, the related content of S201, S202, S203, and S207 can be referred to the related descriptions of S101 to S104, and details are not described herein again.

FIG. 3a is a flowchart showing a specific implementation of S207 in a service response method according to another embodiment of the present invention. Referring to FIG. 3a, in the service response method provided by this embodiment, S207 includes the following multiple steps, which are described in detail as follows: Further, as another embodiment of the present invention, the service request Requesting for an interactive service; the responding to the service request by the middleware includes:

In S301, the interactive content and the interactive object identifier included in the interactive service request are obtained.

In this embodiment, the service request is an interactive service request. Since the interactive service request requires the user and the interactive party to perform information interaction, the interactive service request includes an interactive object identifier for indicating the corresponding interactive object.

In this embodiment, the user will extract the interactive content and the interactive object identifier included in the interactive service request information. The interactive object identifier includes, but is not limited to, a network address of the interactive object, a user identifier information of the interactive object, or a third-party service platform identifier.

In this embodiment, the user's interactive object may be multiple users, wherein multiple users may interact based on the same third-party service platform, or may be multiple users of different third-party service platforms.

In this embodiment, the interactive object of the user may also be a third-party service platform, that is, the user may perform corresponding interaction operations with the third-party service platform, wherein the third-party service platform that requests the interaction may be related to the third-party service operated by the user. The platform is consistent or different.

In S302, the interactive content is sent to the interactive device corresponding to the interactive object identifier according to the interaction object identifier.

In this embodiment, the middleware determines the interactive device corresponding to the interactive object according to the interaction object identifier, and forwards the interactive content in the interactive service request to the interactive device. Wherein, if the interactive object comprises more than one, the interactive devices corresponding to the different interactive pairs of the star identifiers are respectively determined, and the interactive content is simultaneously sent to the plurality of interactive devices.

In S303, an interaction result returned by the interactive device according to the interactive content is received, and the interaction result is returned to the user through the third-party service platform.

In this embodiment, after receiving the interactive content sent by the middleware, the interactive device performs corresponding operations according to the interactive content, obtains an interaction result corresponding to the interactive content, and returns the result to the middleware. After receiving the interaction result, the middleware will return the interaction result to the user through the third-party service platform.

In this embodiment, the interaction result corresponds to the interactive content. For example, if the user only needs to send a file to the interactive device, the interactive device directly returns a successful receiving instruction after receiving the file; if the user needs to send a certain data to the interactive device for arithmetic processing After receiving the data, the interactive device will perform corresponding operations to obtain a corresponding calculation result, and the interaction result will include the calculation result.

In this embodiment, if the user's interaction request involves multiple interaction objects, the middleware may summarize the interaction results of the interactions of the interaction objects, and then uniformly send the results to the user; or may receive the interaction result of any interactive device feedback. Forward directly.

For example, FIG. 3b is a flow chart of interaction of a middleware response interactive service request in a service response method according to an embodiment of the present invention. Referring to FIG. 3b, the interaction process of the middleware response interactive service request is as follows:

In S31, the user will generate an interactive service request through the third-party service platform, where the interactive service request includes the interactive object identifier and the interactive content.

In S32, the third party service platform sends the interactive service request to the middleware.

In S33, the middleware determines whether the interactive service request belongs to an additional service, and if so, extracts the user login information and the user password information in the interactive service request, and matches the two pieces of information with the user registration information, if the matching is successful. , in response to the interactive service request.

In S34, the middleware determines the corresponding interactive device according to the interactive object identifier included in the interactive service request information, and sends the interactive content to the interactive device.

In S35, the interactive device performs an interaction result based on the interactive content, and sends the interaction result to the middleware.

In S36, after receiving the interaction result, the middleware will return the interaction result to the user through the third party service platform.

In the embodiment of the present invention, the user initiates an interactive service request through the middleware, thereby implementing a request for the user to interact with other users or devices. Because some third-party service platforms can only transfer information in one direction, they can't realize the interactive function, and users can get additional services through the middleware, that is, the function of interactive services. On the other hand, the middleware also expands the interactive objects. In general, the user's interactive objects can only be used by users in the third-party service platform, but not with other third-party service platforms or other third-party service platforms. It can be seen that the embodiment of the invention improves the user experience and the convenience of operation.

FIG. 4a is a flowchart showing a specific implementation of S207 in a service response method according to another embodiment of the present invention. Referring to FIG. 4a, in the service response method provided by this embodiment, S207 includes the following multiple steps, which are described in detail as follows: Further, as another embodiment of the present invention, the service request Accessing a service request for an external link; the responding to the service request by the middleware includes:

In S401, the authorization information corresponding to the user is obtained from the third-party server, and an authorization confirmation instruction is returned to the user by the third-party server; wherein the authorization confirmation instruction includes the authorization information.

In this embodiment, when the third-party service platform is used, if the user needs to open the corresponding external link, an external link access service request is generated, and the service request is sent to the middleware, and the middleware receives the service. After the request, the related operations of S401 will be performed.

In this embodiment, before responding to the user's access service request, the middleware first determines the user information required to respond to the external link according to the address pointed to by the external link, and according to the user information required to be used. The corresponding authorization information is generated, and after receiving the authorization information, the user may determine whether the corresponding user information is applied to the external link.

In this embodiment, since the middleware does not record the user information required in the authorization information, the middleware will obtain the user information required by the external link through the third-party service platform, and according to the user in the third-party service platform. The registered information is obtained with the corresponding authorization information.

In this embodiment, after generating the corresponding authorization information, the middleware returns the authorization information to the user through the third-party service platform, and waits for the user to perform authorization confirmation. If the user determines that the relevant user information can be applied to the external link, the confirmation command is sent to the middleware, and the middleware performs the related operation of S402; otherwise, if the user does not agree to apply the related user information to the external link. In the middle, the service abort instruction is returned to the middleware, and after receiving the service abort instruction, the middleware will stop responding to the external link access service request, thereby protecting the privacy of the user.

In S402, a confirmation instruction returned by the user according to the authorization confirmation instruction is received.

In this embodiment, when the user confirms that the authorization information is applied to the external link access operation, an acknowledgement instruction is returned to the middleware, and after receiving the confirmation instruction, the middleware performs the related operation of S403; If the middleware does not receive the confirmation command sent by the user within the preset time, it is judged that the user does not agree to perform the authorization operation, and the response process of the external link access service request is suspended.

In S403, an external link page is generated based on the authorization information and the external link access service request, so that the user interacts through the external link page.

In this embodiment, the middleware confirms that the user agrees to apply the authorization information to the external link, extracts the user information in the authorization information, and uses the user information as the identity identifier of the user to access the external link, and generates the corresponding external link. page.

In this embodiment, the user can interact in response to the external link page of the production. For example, the external link is a web game, so the user's avatar information and the user's nickname information are needed, so the above information is generated to generate an authorization information for asking the user whether to apply the avatar information and the nickname information to the webpage. in the game. If the user agrees to authorize after receiving the authorization confirmation command, a confirmation command will be returned to the middleware. After receiving the confirmation command, the middleware will open the corresponding external link and produce a web game page, wherein the game player of the web game is a new game player produced according to the user's nickname and the user's avatar.

For example, FIG. 4b is a flowchart of interaction of a middleware response interactive service request in a service response method according to an embodiment of the present invention. Referring to FIG. 4b, the interaction process of the middleware response interactive service request is as follows:

In S41, the user sends an external link access service request to the middleware, and the external link access service request will contain the external link address that the user needs to access.

In S42, the middleware determines the authorization information required to access the external link according to the access request, and acquires the corresponding authorization information from the third-party service platform.

In S43, the middleware returns an authorization confirmation instruction to the user through the third party service platform.

In S44, after receiving the authorization confirmation command, the user will judge whether to perform the authorization operation, and if the authorization is confirmed, return the confirmation command to the middleware.

In S45, after receiving the confirmation instruction, the middleware generates an external link page according to the authorization information and the external link access service request.

In S46, the user can perform corresponding interaction operations in the external link page.

In the embodiment of the present invention, the user can access the external link through the middleware, and generate a corresponding external link page, and interact in the page, enriching the service type of the user using the third-party service platform, thereby improving the user. The experience of using it.

FIG. 5a is a flowchart showing a specific implementation of S104 in a service response method according to another embodiment of the present invention. Referring to FIG. 5a, in the service response method provided by this embodiment, S104 includes the following multiple steps, which are described in detail as follows: Further, as another embodiment of the present invention, the service request Pushing a service request for the message; the responding to the service request by the middleware includes:

In S501, the push setting information sent by the user is received; wherein the push setting information includes a push content, a push timing, and a push object.

In this embodiment, the user can implement the function of message push through the middleware. It should be noted that the user may be a registered user of a third-party service platform, or may be a non-natural user such as a micro store, a Taobao mall, or a WeChat public account.

In this embodiment, the user sends the push setting information to the middleware, wherein the push setting information will include push content, push timing, and push object. The push content is specifically the information related to the message content, such as the specific content, format, and push template of the message when the message is pushed; the push timing specifically refers to the time or trigger condition for pushing, that is, when a certain time is reached or a trigger is satisfied. The condition is then pushed by the message.

In this embodiment, after receiving the push setting information, the middleware stores the information and monitors whether the corresponding push timing is satisfied in real time. If yes, the related operation of S502 is performed; otherwise, the monitoring is continued.

In S502, when the push timing is satisfied, the push content is sent to the push object through the third-party service platform, and the transmission result is returned to the user.

In this embodiment, when the middleware detects that the corresponding push timing is satisfied, the related operation of S502 is performed, the push content in the push setting information is retrieved, a corresponding push message is generated, and the third party service platform is used to The push message is sent to the push object corresponding to the push setting information. After the push is completed, the middleware will summarize the sending situation. For example, the sending situation includes information such as the delivery rate, the delivery time, and the viewing status. After the related transmission conditions are summarized, a corresponding transmission result is generated, and the transmission result is returned to the user.

For example, FIG. 5b is an interaction flowchart of a middleware response message push service request according to an embodiment of the present invention. Referring to FIG. 5b, the interaction process of the middleware response interactive service request is as follows:

In S51, the user transmits push setting information to the middleware.

In S52, the middleware is monitored to meet the push timing.

In S53, if the middleware determines that the push timing has been met, the push content is sent to the third-party service platform, and the target object that the third-party service platform needs to forward is notified.

In S54, after receiving the pushed content, the third-party service platform forwards the content to the corresponding target object, that is, the above-mentioned push object.

In S55, after the middleware summarizes the push situation returned by the third-party service platform, the middleware returns the result to the user.

In the embodiment of the present invention, the user can implement the function of message pushing through the middleware, thereby facilitating the timing transmission of information and one-time transmission for multiple objects, reducing the operation steps of the user and improving the operation efficiency of the user.

FIG. 6 is a schematic structural diagram of an intermediate member according to an embodiment of the present invention. The intermediate unit includes units for performing the steps in the corresponding embodiment of FIG. 1. For details, please refer to the related description in the embodiment corresponding to FIG. 1 and FIG. For the convenience of explanation, only the parts related to the present embodiment are shown. Referring to Figure 6, the middleware includes:

The registration information receiving unit 61 is configured to receive the registration information sent by the user, where the registration information includes an identifier of the third-party service platform and login information of the user logging in to the third-party service platform;

An additional service adding unit 62, configured to add, according to the identifier and the login information, an additional service to the list of respondable services corresponding to the user on the third-party service platform; wherein the additional service is the respondable service Other services outside the list;

The service receiving unit 63 is configured to receive a service request sent by the user, and determine whether the service type corresponding to the service request is the additional service;

The service response unit 64 is configured to respond to the service request by using a middleware if the service type is an additional service.

Optionally, the login information includes user identification information and user password information; the middleware further includes:

a user parameter extraction unit, configured to extract user identification information and user password information included in the service request;

a user parameter matching unit, configured to match user identification information included in the service request with user identification information of the login information, and user password information included in the service request and user password information included in the login information Matching;

And a response determining unit, configured to determine, according to the matching result, whether to respond to the service request by the middleware.

Optionally, the service request is an interactive service request; the service response unit 64 includes:

An interaction parameter obtaining unit, configured to acquire an interaction content and an interaction object identifier included in the interaction service request;

The interactive content sending unit is configured to send the interactive content to the interactive device corresponding to the interactive object identifier according to the interaction object identifier;

The interaction result returning unit is configured to receive an interaction result returned by the interactive device according to the interactive content, and return the interaction result to the user through the third-party service platform.

Optionally, the service request is an external link access service request; the service response unit 64 includes:

An authorization information obtaining unit, configured to acquire authorization information corresponding to the user from the third-party server, and return an authorization confirmation instruction to the user by using the third-party server; wherein the authorization confirmation instruction includes the authorization information ;

a confirmation instruction receiving unit, configured to receive a confirmation instruction returned by the user according to the authorization confirmation instruction;

And a page generating unit, configured to generate an external link page based on the authorization information and the external link access service request, so that the user interacts through the external link page.

Optionally, the service request is a message push service request; the service response unit 64 includes:

a push setting unit, configured to receive push setting information sent by the user, where the push setting information includes a push content, a push timing, and a push object;

An information pushing unit, configured to send the pushed content to the push object through the third-party service platform when the push timing is satisfied, and return the sending result to the user

Therefore, the middleware user provided by the embodiment of the present invention can also obtain the additional service authority of the third-party platform by registering in the middleware, and use the third-party service platform to initiate the corresponding additional service request, and the third-party service platform receives the additional service. After the service request, it will be handed over to the middleware to respond, thus providing more services to the user. It can be seen that, in the embodiment of the present invention, the user does not need to install or use a new third-party service platform, and only needs to perform related registration operations, and then can perform various service requests through the original third-party service platform, thereby improving user experience. On the other hand, because the middleware performs service update and the addition is more flexible, the user's service demand can be used in time, and the update efficiency and user experience of the third-party service platform are improved.

The embodiments described above are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art will understand that The technical solutions described in the examples are modified, or some of the technical features are equivalently replaced; and the modifications or substitutions do not deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should be included in Within the scope of protection of the present invention.

Claims

A service response method, comprising:

Receiving registration information sent by the user, where the registration information includes an identifier of the third-party service platform and login information of the user logging in to the third-party service platform;

Adding, according to the identifier and the login information, an additional service to the list of respondable services corresponding to the user on the third-party service platform; wherein the additional service is another service outside the list of respondable services;

Receiving a service request sent by the user, and determining whether the service type corresponding to the service request is the additional service;

If the service type is an additional service, the service request is responded to by the middleware.
The service response method according to claim 1, wherein the login information comprises user identification information and user password information;

Before the middleware responds to the service request, the method further includes:

Extracting user identification information and user password information included in the service request;

Matching user identification information included in the service request with user identification information of the login information, and matching user password information included in the service request with user password information included in the login information;

Whether to respond to the service request by the middleware is determined according to the matching result.
The service response method according to claim 2, wherein the service request is an interactive service request;

The responding to the service request by using the middleware includes:

Obtaining the interactive content and the interactive object identifier included in the interactive service request;

Sending the interactive content to the interactive device corresponding to the interactive object identifier according to the interaction object identifier;

Receiving an interaction result returned by the interactive device according to the interactive content, and returning the interaction result to the user through the third-party service platform.
The service response method according to claim 2, wherein the service request is an external link access service request;

The responding to the service request by using the middleware includes:

Acquiring the authorization information corresponding to the user from the third-party server, and returning an authorization confirmation instruction to the user by using the third-party server; wherein the authorization confirmation instruction includes the authorization information;

Receiving a confirmation instruction returned by the user according to the authorization confirmation instruction;

An external link page is generated based on the authorization information and the external link access service request, so that the user interacts through the external link page.
The service response method according to claim 1, wherein the service request is a message push service request;

The responding to the service request by using the middleware includes:

Receiving, by the user, the push setting information, where the push setting information includes a push content, a push timing, and a push object;

When the push timing is satisfied, the push content is sent to the push object through the third-party service platform, and the transmission result is returned to the user.
A middleware, comprising:

a registration information receiving unit, configured to receive registration information sent by the user, where the registration information includes an identifier of the third-party service platform and login information of the user logging in to the third-party service platform;

An additional service adding unit, configured to add, according to the identifier and the login information, an additional service to the list of respondable services corresponding to the user on the third-party service platform; wherein the additional service is the list of the respondable services Other services;

a service receiving unit, configured to receive a service request sent by the user, and determine whether the service type corresponding to the service request is the additional service;

The service response unit is configured to respond to the service request by using a middleware if the service type is an additional service.
The middleware according to claim 6, wherein the login information includes user identification information and user password information;

The middleware further includes:

a user parameter extraction unit, configured to extract user identification information and user password information included in the service request;

a user parameter matching unit, configured to match user identification information included in the service request with user identification information of the login information, and user password information included in the service request and user password information included in the login information Matching;

And a response determining unit, configured to determine, according to the matching result, whether to respond to the service request by the middleware.
The middleware according to claim 7, wherein the service request is an interactive service request;

The service response unit includes:

An interaction parameter obtaining unit, configured to acquire an interaction content and an interaction object identifier included in the interaction service request;

The interactive content sending unit is configured to send the interactive content to the interactive device corresponding to the interactive object identifier according to the interaction object identifier;

The interaction result returning unit is configured to receive an interaction result returned by the interactive device according to the interactive content, and return the interaction result to the user through the third-party service platform.
The middleware according to claim 7, wherein the service request is an external link access service request;

The service response unit includes:

An authorization information obtaining unit, configured to acquire authorization information corresponding to the user from the third-party server, and return an authorization confirmation instruction to the user by using the third-party server; wherein the authorization confirmation instruction includes the authorization information ;

a confirmation instruction receiving unit, configured to receive a confirmation instruction returned by the user according to the authorization confirmation instruction;

And a page generating unit, configured to generate an external link page based on the authorization information and the external link access service request, so that the user interacts through the external link page.
The middleware according to claim 6, wherein the service request is a message push service request;

The service response unit includes:

a push setting unit, configured to receive push setting information sent by the user, where the push setting information includes a push content, a push timing, and a push object;

The information pushing unit is configured to send the pushed content to the push object through the third-party service platform when the push timing is satisfied, and return the sending result to the user.