CN114500635A

CN114500635A - Service processing method and device

Info

Publication number: CN114500635A
Application number: CN202210018421.1A
Authority: CN
Inventors: 党家豪; 边炀凯; 王少龙
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2022-01-07
Filing date: 2022-01-07
Publication date: 2022-05-13

Abstract

An embodiment of the present specification provides a service processing method and device, wherein the service processing method includes: the service container is used for performing equipment login processing and service scene subscription processing of the terminal equipment; the method comprises the following steps: the receiving and sending client receives a service message of a subscription service scene sent by a server through a data link; the transceiver client establishing the data link in response to an initialization call by the device application; transmitting the service message into the device application to expose the service message through the device application; and if the service message is triggered, calling the service container to acquire service detail data corresponding to the service message.

Description

Service processing method and device

Technical Field

The present disclosure relates to the field of data processing technologies, and in particular, to a service processing method and apparatus.

Background

With the development of internet technology and the popularization of mobile terminals, more and more services begin to extend to online scenes, application platform software capable of carrying a plurality of application subprograms appears, the situation that users install different types of application programs on the mobile terminals is avoided, the services are handled by means of the application subprograms carried in the application platform software, and meanwhile, the application subprograms can also fully utilize the sufficient user traffic of the application platform software, so that assistance is provided for the service promotion of the application subprograms.

Disclosure of Invention

One or more embodiments of the present specification provide a service processing method, which is applied to a terminal device, where the terminal device is installed with a device application, a service container, and a transceiving client, and the service container is used to perform device login processing and service scene subscription processing of the terminal device; the method comprises the following steps: and the receiving and sending client receives the service message of the subscription service scene sent by the server through the data link. The transceiving client establishes the data link in response to an initialization call by the device application. And transmitting the service message into the device application so as to show the service message through the device application. And if the service message is triggered, calling the service container to acquire service detail data corresponding to the service message.

One or more embodiments of the present specification provide a second service processing method, which is applied to a service platform, where the service platform is configured to perform, in cooperation with a service container installed in a terminal device, device login processing and service scene subscription processing for the terminal device; the method comprises the following steps: and receiving service data of the service scene synchronized by the service provider. And inquiring user equipment bound by the equipment user to which the service data belongs, and determining the terminal equipment corresponding to the subscription service scene in the inquired user equipment. And generating a service message of the service data and sending the service message to a server so as to send the service message to a receiving and sending client through a data link corresponding to the equipment information of the terminal equipment.

One or more embodiments of the present specification provide a third service processing method, which is applied to a server, where the server is configured to establish a data link in cooperation with a transceiver client installed in a terminal device; the method comprises the following steps: and receiving a service message of the subscription service scene sent by the service platform. And determining a data link of the terminal equipment corresponding to the service message. And sending the service message to a receiving and sending client operated by the terminal equipment through the data link.

One or more embodiments of the present specification provide a service processing apparatus, which operates on a terminal device, where the terminal device is installed with a device application, a service container, and a transceiving client, and the service container is used to perform device login processing and service scene subscription processing on the terminal device; the device comprises: and the service message receiving module is configured to receive the service message of the subscription service scene sent by the server through the data link by the transceiving client. The transceiving client establishes the data link in response to an initialization call by the device application. A service message import module configured to import the service message into the device application to expose the service message by the device application. And the service detail data acquisition module is configured to call the service container to acquire the service detail data corresponding to the service message if the service message is triggered.

One or more embodiments of the present specification provide a second service processing apparatus, running on a service platform, and configured to perform, for a terminal device, device login processing and service scene subscription processing in cooperation with a service container installed in the terminal device; the device comprises: and the service data receiving module is configured to receive service data of the subscription service scene synchronized by the service provider. And the terminal equipment determining module is configured to query the user equipment bound by the equipment user to which the service data belongs, and determine the terminal equipment corresponding to the subscription service scene in the queried user equipment. And the service message sending module is configured to generate a service message of the service data and send the service message to a server so as to send the service message to a transceiving client through a data link corresponding to the device information of the terminal device.

One or more embodiments of the present specification provide a third service processing apparatus, running at a server, for establishing a data link in cooperation with a transceiver client installed in a terminal device, where the apparatus includes: and the service message receiving module is configured to receive the service message of the subscription service scene sent by the service platform. And the data link determining module is configured to determine the data link of the terminal equipment corresponding to the service message. A service message sending module configured to send the service message to a transceiving client operated by the terminal device through the data link.

One or more embodiments of the present specification provide a terminal device, including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and the transceiving client receives a service message of a subscription service scene sent by the server through a data link. The receiving and sending client is installed on the terminal equipment, the terminal equipment is also provided with equipment application and a service container, and the service container is used for performing equipment login processing and service scene subscription processing of the terminal equipment. The transceiving client establishes the data link in response to an initialization call by the device application. And transmitting the service message into the device application so as to show the service message through the device application. And if the service message is triggered, calling the service container to acquire service detail data corresponding to the service message.

One or more embodiments of the present specification provide a service processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: and receiving service data of the service scene synchronized by the service provider. The service processing equipment is applied to a service platform, and the service platform is used for matching a service container installed on the terminal equipment to perform equipment login processing and service scene subscription processing on the terminal equipment. And inquiring user equipment bound by the equipment user to which the service data belongs, and determining the terminal equipment corresponding to the subscription service scene in the inquired user equipment. And generating a service message of the service data and sending the service message to a server so as to send the service message to a receiving and sending client through a data link corresponding to the equipment information of the terminal equipment.

One or more embodiments of the present specification provide a second service processing apparatus, including: a processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: and receiving a service message of the subscription service scene sent by the service platform. The service processing equipment runs through a server, and the server is used for establishing a data link in cooperation with a receiving and sending client installed on the terminal equipment. And determining a data link of the terminal equipment corresponding to the service message. And sending the service message to a receiving and sending client operated by the terminal equipment through the data link.

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed by a processor, implement the following: and the transceiving client receives a service message of a subscription service scene sent by the server through a data link. The transceiving client establishes the data link in response to an initialization call by the device application. And transmitting the service message into a device application so as to show the service message through the device application. And if the service message is triggered, calling a service container to acquire service detail data corresponding to the service message. The service container is used for performing equipment login processing and service scene subscription processing of the terminal equipment.

One or more embodiments of the present specification provide a second storage medium storing computer-executable instructions that, when executed by a processor, implement the following: and receiving service data of the service scene synchronized by the service provider. And inquiring user equipment bound by the equipment user to which the service data belongs, and determining the terminal equipment corresponding to the subscription service scene in the inquired user equipment. And generating a service message of the service data and sending the service message to a server so as to send the service message to a receiving and sending client through a data link corresponding to the equipment information of the terminal equipment.

One or more embodiments of the present specification provide a third storage medium storing computer-executable instructions that, when executed by a processor, implement the following flow: and receiving a service message of the subscription service scene sent by the service platform. And determining a data link of the terminal equipment corresponding to the service message. And sending the service message to a receiving and sending client operated by the terminal equipment through the data link.

Drawings

In order to more clearly illustrate one or more embodiments or technical solutions in the prior art in the present specification, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without inventive exercise;

fig. 1 is a processing flow diagram of a service processing method according to one or more embodiments of the present disclosure;

fig. 2 is a timing diagram of a service processing method applied to an actual device scenario according to one or more embodiments of the present disclosure;

FIG. 3 is a flow diagram of a second method for processing services according to one or more embodiments of the present disclosure;

FIG. 4 is a flow diagram of a third method for processing services according to one or more embodiments of the present disclosure;

FIG. 5 is a schematic diagram of a service processing device according to one or more embodiments of the present disclosure;

FIG. 6 is a schematic diagram of a second service processing device according to one or more embodiments of the present disclosure;

FIG. 7 is a schematic diagram of a third service processing apparatus provided in one or more embodiments of the present disclosure;

fig. 8 is a schematic structural diagram of a terminal device according to one or more embodiments of the present disclosure;

fig. 9 is a schematic structural diagram of a service processing device according to one or more embodiments of the present disclosure;

fig. 10 is a schematic structural diagram of a second service processing device according to one or more embodiments of the present specification.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments that can be derived by a person skilled in the art from one or more of the embodiments described herein without making any inventive step shall fall within the scope of protection of this document.

An embodiment of a service processing method provided in this specification:

referring to fig. 1, the service processing method provided in this embodiment is applied to a terminal device, where the terminal device is installed with a device application, a service container and a transceiving client, and the service container is used to perform device login processing and service scene subscription processing on the terminal device;

the method specifically includes steps S102 to S106.

Step S102, the receiving and sending client receives the service message of the subscription service scene sent by the server through the data link.

The service processing method provided by the application starts from the actual application scene of the terminal equipment, accesses the corresponding service scene for the terminal equipment, performs service access of the service scene by installing a service container on the terminal equipment and taking the service container as a carrier, establishes a data link for service information of the service scene by installing a transceiving client on the terminal equipment, and pushes the service information by using the transceiving client according to the service information, and calls the service container to perform corresponding service information access processing under the condition that the service information displayed by equipment application is triggered, so that the operating pressure of the terminal equipment in the service use process is reduced by the transceiving client, the development cost of the equipment provider for providing service access capability for the terminal equipment is reduced, the flexibility and diversity of the use of the terminal equipment are improved, and the adaptability of the terminal equipment to the actual use scene is improved by an open service subscription mode, the diversified requirements of the user in the process of using the terminal equipment are met.

The terminal device in this embodiment includes, but is not limited to, at least one of the following: the car machine terminal of vehicle installation, the external terminal equipment of vehicle, intelligent audio amplifier, unmanned machine of selling, independently the radio, interactive advertising screen, POS equipment to and intelligent household electrical appliances products such as intelligent TV, intelligent refrigerator.

The device application refers to a system application program on which the terminal device runs. The service container is an operation framework or an operation engine provided for the terminal equipment, and service access can be realized on the terminal equipment by installing the service container on the terminal equipment.

The receiving and sending client is a client installed on the terminal device and used for receiving and sending service data, the independent client for receiving and sending the service data is installed on the terminal device, the service receiving of the terminal device can be guaranteed only by keeping the working state of the receiving and sending client in the operation process of the terminal device, a service container does not need to be operated on the background of the terminal device, the receiving and sending client occupies fewer operation resources of the terminal device in the operation process relative to the service container, the occupation of the operation resources of the terminal device is effectively reduced, and therefore under the condition that the operation resources of the terminal device are limited, the occupation of the operation resources of the receiving and sending client is reduced, and the improvement of the operation efficiency of the terminal device is facilitated.

In an actual application, a service container and a transceiving client are installed and configured by a device provider, after the installation and configuration are completed, a terminal device can perform service access through the installed service container and the transceiving client after being started, optionally, the terminal device runs the device application when being started, the device application starts initialization call to the transceiving client when running, the transceiving client establishes a data link with the service end in response to the initialization call of the device application, and the transceiving client maintains a running state after receiving the initialization call, and in the case that the transceiving client maintains the running state after establishing the data link, the data link is maintained in a long connection state after being established. The device provider comprises a terminal device producer, a terminal device seller and/or a terminal device service operation and maintenance party.

Specifically, in an optional implementation manner provided in this embodiment, the process of establishing the data link by the transceiver client in response to the initialization call of the device application is implemented in the following manner: registering and calling back the equipment application based on the initialization call to obtain equipment information of the terminal equipment; and establishing a data link with the server based on the equipment information.

After the terminal device installs the service container, the device user of the terminal device may perform device login processing and service scenario subscription processing of the terminal device based on the service container, so that the corresponding service of the service scenario can be used after the device login processing and the service scenario subscription processing are completed. The service scenario described in this embodiment includes a service policy or a service domain determined from a service related in an actual usage scenario of the terminal device, and each service scenario is associated with a plurality of subroutines related to the service scenario or within a service range of the service scenario.

In the above-mentioned embodiment, after the terminal device installs the service container and the transceiving client, the terminal device has the capability of providing the service, but the operation of the user is not confirmed, and the terminal device has not yet provided the service to the user. Optionally, the device login processing includes: and establishing a binding relationship between the terminal equipment and the equipment user according to an application account of the equipment user in a target application, which is carried in a service request submitted by the service container, and recording the login state of the terminal equipment.

As described above, in this embodiment, the service container and the transceiving client are installed in the terminal device, so that the terminal device has a capability of providing a service, but in an actual use process, a device user needs to subscribe to a service scenario and perform corresponding authorization processing on the subscribed service scenario to the terminal device, so as to perform service access based on the service scenario subscription and the authorization processing, in an optional implementation manner provided in this embodiment, the service scenario subscription processing specifically includes: acquiring a subscription service scene subscribed by a device user in a service scene set of the terminal device, and generating a registration record of the terminal device for the subscription service scene; and carrying out authorization processing on the terminal equipment aiming at the subscription service scene according to the authorization configuration information submitted aiming at the subscription service scene.

It should be noted that, in this embodiment, service scenarios subscribed by the device user for the terminal device are configured and accessed by the device provider in advance, for example, a plurality of service scenarios are configured and accessed for the terminal device before the terminal device leaves a factory, based on which, after the terminal device is circulated to the device user, the device user may subscribe one or more service scenarios in the service scenarios pre-accessed by the device provider, and the one or more service scenarios subscribed by the device user are referred to as subscription service scenarios. In an optional implementation manner provided by this embodiment, the terminal device performs service scenario configuration access before starting; specifically, the service scenario configuration access includes:

the service platform determines a service scene set formed by at least one service scene selected by a device provider in a service scene pool aiming at the terminal device; the service pool is composed of a plurality of service scenes pre-configured by a service platform;

issuing a list of subprograms associated with each service scene in the service scene set to the equipment provider;

and associating the target subprogram to a service scene according to the target subprogram selected by the device provider in the list of each service in the service scene set.

The sub program refers to a package or an application component that is installed on or loaded by an application platform (or an application program), and has a capability of independently providing a self-closed loop service from a service perspective, for example, a sub program that operates in the application program and provides a self-closed loop capability of a vehicle-related service or a ticketing service. Optionally, the subprograms in the list include subprograms in the target application, and the service container is configured with an access entry of the subprogram in the target application.

In specific implementation, after the device login processing and the service scene subscription processing of the terminal device are completed through a service container installed on the terminal device and the establishment of the data link is completed through a transceiving client installed on the terminal device, a service platform receives service data of a subscription service scene synchronized by a service provider, inquires user equipment bound by a user to which the service data belongs, determines terminal devices corresponding to the subscription service scene in the inquired user equipment, generates a service message of the service data and sends the service message to a server of the transceiving client; after receiving a service message sent by a service platform, a service end of a transceiving client determines a data link of terminal equipment corresponding to the service message, and sends the service message to the transceiving client through the determined data link; accordingly, the service message of the subscription service scenario sent by the server via the data link is received by the transceiver client.

And step S104, transmitting the service message into the equipment application so as to display the service message through the equipment application.

In specific implementation, after receiving the service message, the transceiving client installed in the terminal device transmits the service message to the device application, so as to display the service message through the device application, for example, the device application installed in the terminal device calls a display interface of the terminal device to display the service message, and further, for example, the device application installed in the terminal device calls a voice playing interface of the terminal device to play the service message.

In addition, in order to improve the display efficiency of the service message, the receiving and sending client can call a corresponding interface of the terminal equipment to display the service message according to the message type of the service message; or, in order to improve the interactivity of service message display, in the case that a service container installed on the terminal device is detected to be in an operating state, the service message is transmitted to the service container, the service container displays the service message, and a device user can perform interactive operation on the service message by means of an access interface provided by the service container.

Step S106, if the service message is triggered, the service container is called to obtain the service detail data corresponding to the service message.

After the service message is displayed, if the service message is triggered, the service container is called to perform response processing on the service message, where the response processing includes obtaining service detail data corresponding to the service message and displaying the service detail data. In particular, the service application presenting the service message may initiate the call to the service container after detecting the trigger instruction of the service message, or the transceiver client receiving the service message may initiate the call to the service container after detecting the trigger instruction of the service message.

In an optional implementation manner provided by this embodiment, invoking the service container to obtain the service detail data corresponding to the service message includes:

sending a calling instruction to the service container so as to start and run a target subprogram corresponding to the service message based on the service container;

and acquiring and displaying the service detail data of the service message based on the target subprogram.

As described above, the transceiving client installed on the terminal device is configured to receive and send service data, and specifically includes receiving a service message pushed by the server and uploading the service data of one side of the terminal device to the server, and in the using process of the terminal device, in many cases, a corresponding service request needs to be made to a service provider or a service platform, so as to improve the processing efficiency of the service request process, and to avoid starting the service container and using the service container to perform the service request to occupy the operating resource of the terminal device, the transceiving client may also be configured to perform service request processing, and optionally, the transceiving client is further configured to acquire device service data of the terminal device and upload the device service data to the server through the data link; the server side forwards the equipment service data to a service platform of the service container, acquires a service data response returned by the service platform after the service processing is carried out on the equipment service data, and returns the service data response to the transceiving client side;

wherein, the device data of the terminal device comprises: the terminal equipment acquires user data and/or service request data input by equipment users and received by the terminal equipment.

The following takes an application of the service processing method provided in this embodiment in an actual device scenario as an example, and further describes the service processing method provided in this embodiment, referring to fig. 2, the service processing method applied to the terminal device specifically includes the following steps. The terminal device is provided with a device application, a transceiving client and a service container.

Step S202, the receiving and sending client receives the initialization call initiated by the device application when starting.

And step S204, the receiving and sending client performs registration call-back on the equipment application to obtain the equipment information of the terminal equipment.

Step S206, a data link with the service end is established based on the equipment information, and the long connection state of the data link is kept.

And step S208, the service container receives the activation instruction submitted by the device user aiming at the terminal device and forwards the activation instruction to the service platform.

Step S212, the service container generates a login request carrying an application account of the device user in the target application and submits the login request to the service platform.

Step S218, the service container obtains the subscribed service scenario subscribed by the device user in the service scenario set accessed by the terminal device and submits the subscribed service scenario to the service platform.

Step S234, the transceiving client receives the service message sent by the server through the data link.

Step S236, the service message is transmitted to the device application, so that the service message is displayed by the device application.

Step S238, if the device application detects that the service message is triggered, the service container is invoked to obtain service detail data corresponding to the service message.

A second service processing method embodiment provided in this specification:

the service processing method applied to the service platform provided in this embodiment is matched with the service processing method applied to the terminal device provided in the above embodiment in the execution process, and is matched with the service processing method applied to the service end provided in the following embodiment in the execution process, so that please refer to the corresponding contents of the above embodiment and the following embodiment in this embodiment.

Referring to fig. 3, the service processing method provided in this embodiment is applied to a service platform, where the service platform is used to perform device login processing and service scene subscription processing on a terminal device in cooperation with a service container installed in the terminal device; the method specifically includes steps S302 to S306.

Step S302, receiving the service data of the subscription service scene synchronized by the service provider.

The service scenario described in this embodiment includes a service policy or a service domain determined from a service related in an actual usage scenario of the terminal device, and each service scenario is associated with a plurality of subroutines related to the service scenario or within a service range of the service scenario. The subscription service scene refers to a service scene subscribed by the device user in the service scene set of the terminal device.

Optionally, the device login processing includes: and establishing a binding relationship between the terminal equipment and the equipment user according to an application account number of the equipment user in a target application carried in a service request submitted by the service container, and recording the login state of the terminal equipment.

It should be noted that the service scene subscription performed by the terminal device is implemented by a service container installed in the terminal device, where the service container is an operation framework or an operation engine provided for the terminal device, and the service access can be implemented in the terminal device by installing the service container in the terminal device. In an optional implementation manner provided by this embodiment, the service scenario subscription processing specifically includes: acquiring a subscription service scene subscribed by a device user in a service scene set of the terminal device, and generating a registration record of the terminal device for the subscription service scene; and carrying out authorization processing on the terminal equipment aiming at the subscription service scene according to the authorization configuration information submitted aiming at the subscription service scene.

In this embodiment, the service scenarios subscribed by the device user for the terminal device are configured and accessed by the device provider in advance, for example, a plurality of service scenarios are configured and accessed for the terminal device before the terminal device leaves a factory, based on which, after the terminal device is circulated to the device user, the device user may subscribe one or more service scenarios in the service scenarios pre-accessed by the device provider, and the one or more service scenarios subscribed by the device user are referred to as subscription service scenarios. In an optional implementation manner provided by this embodiment, the terminal device performs service scenario configuration access before starting; specifically, the service scenario configuration access includes:

Step S304, inquiring the user equipment bound by the equipment user to which the service data belongs, and determining the terminal equipment corresponding to the subscription service scene in the inquired user equipment.

Step S306, generating a service message of the service data and sending the service message to a server, so as to send the service message to a transceiver client through a data link corresponding to the device information of the terminal device.

The terminal equipment is also provided with equipment application and the transceiving client; the device application refers to a system application program on which the terminal device runs. The receiving and sending client is a client installed on the terminal device and used for receiving and sending service data, the independent client for receiving and sending the service data is installed on the terminal device, the service receiving of the terminal device can be guaranteed only by keeping the working state of the receiving and sending client in the operation process of the terminal device, a service container does not need to be operated on the background of the terminal device, the receiving and sending client occupies fewer operation resources of the terminal device in the operation process relative to the service container, the occupation of the operation resources of the terminal device is effectively reduced, and therefore under the condition that the operation resources of the terminal device are limited, the occupation of the operation resources of the receiving and sending client is reduced, and the improvement of the operation efficiency of the terminal device is facilitated.

In an actual application, a service container and a transceiving client are installed and configured by a device provider, after the installation and configuration are completed, a terminal device can perform service access through the installed service container and the transceiving client after being started, optionally, the terminal device runs the device application when being started, the device application starts initialization call to the transceiving client when running, the transceiving client establishes a data link with the service end in response to the initialization call of the device application, and the transceiving client maintains a running state after receiving the initialization call, and in a case that the transceiving client maintains the running state after establishing the data link, the data link is maintained in a long connection state after being established. The device provider comprises a producer and a seller of the terminal device and/or a service operation and maintenance party of the terminal device.

The following takes an application of the service processing method provided in this embodiment in an actual device scenario as an example, and further describes the service processing method provided in this embodiment, referring to fig. 2, the service processing method applied to the service platform specifically includes the following steps.

Step S210, the service platform activates the terminal device according to the activation instruction of the terminal device submitted by the service container.

Step S214, the service platform establishes a binding relationship between the terminal device and the device user according to the application account number of the device user in the target application carried in the service request submitted by the service container, and records the login state of the terminal device.

Step S216, the service platform sends the service scene set accessed by the device provider aiming at the terminal device to the service container.

Step S220, the service platform receives the subscription service scenario submitted by the service container, and generates a subscription service scenario registration record.

Step S222, the service platform performs authorization processing on the subprogram associated with the subscription service scenario.

Step S224, the service platform receives the service data of the subscription service scenario synchronized by the service provider.

The service provider refers to a service provider for providing corresponding services for the subprogram associated with the subscription service scenario.

Step S226, the service platform queries the user equipment bound to the device user to which the service data belongs, and determines the terminal equipment corresponding to the subscription service scenario in the queried user equipment.

Step S228, the service platform generates a service message of the service data and sends the service message to the server.

The third service processing method embodiment provided in this specification:

referring to fig. 4, the service processing method provided in this embodiment is applied to a server, where the server is used to establish a data link in cooperation with a transceiver client installed in a terminal device; the method specifically includes steps S402 to S406.

The service processing method applied to the service platform provided in this embodiment is mutually matched with the service processing method applied to the terminal device provided in the above embodiment in the execution process, and is mutually matched with the service processing method applied to the service platform provided in the above embodiment in the execution process, so that please refer to the corresponding contents of the above embodiment in this embodiment, which is not described herein again.

Step S402, receiving a service message of a subscription service scene sent by a service platform;

step S404, determining a data link of the terminal device corresponding to the service message;

step S406, sending the service message to the transceiving client operated by the terminal device through the data link.

In this embodiment, the terminal device is provided with a device application, a service container and the transceiving client, where the service container is used to perform device login processing and service scene subscription processing of the terminal device; the transceiving client establishes the data link in response to an initialization call by the device application.

In an actual application, a service container and a transceiving client are installed and configured by a device provider, after the installation and configuration are completed, a terminal device can perform service access through the installed service container and the transceiving client after being started, optionally, the terminal device runs the device application when being started, the device application starts initialization call to the transceiving client when running, the transceiving client establishes a data link with the service end in response to the initialization call of the device application, and the transceiving client maintains a running state after receiving the initialization call, and in a case that the transceiving client maintains the running state after establishing the data link, the data link is maintained in a long connection state after being established. The device provider comprises a terminal device producer, a terminal device seller and/or a terminal device service operation and maintenance party.

The following takes an application of the service processing method provided in this embodiment in an actual device scenario as an example, and further describes the service processing method provided in this embodiment, referring to fig. 2, the service processing method applied to the server specifically includes the following steps.

In step S230, the service end receives the service message sent by the service platform.

Step S232, the server determines the data link of the terminal device corresponding to the service message, and sends the service message to the transceiver client through the determined data link.

An embodiment of a service processing apparatus provided in this specification is as follows:

in the foregoing embodiment, a service processing method applied to a terminal device is provided, and correspondingly, a service processing apparatus operating on the terminal device is also provided, which is described below with reference to the accompanying drawings.

Referring to fig. 5, a schematic diagram of a service processing apparatus provided in this embodiment is shown.

Since the device embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions may refer to the corresponding description of the method embodiments provided above. The device embodiments described below are merely illustrative.

The embodiment provides a service processing apparatus, which operates on a terminal device, where the terminal device is provided with a device application, a service container and a transceiving client, and the service container is used for performing device login processing and service scene subscription processing on the terminal device; the device comprises:

a service message receiving module 502 configured to receive, by the transceiver client, a service message of a subscription service scenario sent by a server over a data link; the transceiver client establishing the data link in response to an initialization call by the device application;

a service message import module 504 configured to import the service message into the device application to expose the service message by the device application;

a service detail data obtaining module 506, configured to invoke the service container to obtain the service detail data corresponding to the service message if the service message is triggered.

The second service processing apparatus provided in this specification includes the following embodiments:

in the foregoing embodiment, a service processing method applied to a service platform is provided, and correspondingly, a service processing apparatus running on the service platform is also provided, which is described below with reference to the accompanying drawings.

Referring to fig. 6, a schematic diagram of a service processing apparatus provided in this embodiment is shown.

The embodiment provides a service processing apparatus, running on a service platform, for performing device login processing and service scene subscription processing on a terminal device in cooperation with a service container installed on the terminal device; the device comprises:

a service data receiving module 602 configured to receive service data of a subscription service scenario synchronized by a service provider;

a terminal device determining module 604, configured to query a user device bound to a device user to which the service data belongs, and determine a terminal device corresponding to the subscription service scenario in the queried user device;

a service message sending module 606 configured to generate a service message of the service data and send the service message to a server, so as to send the service message to a transceiver client through a data link corresponding to the device information of the terminal device.

The third embodiment of the service processing apparatus provided in this specification is as follows:

in the foregoing embodiment, a service processing method applied to a server is provided, and correspondingly, a service processing apparatus operating in the server is also provided, which is described below with reference to the accompanying drawings.

Referring to fig. 7, a schematic diagram of a service processing apparatus provided in this embodiment is shown.

The embodiment provides a service processing apparatus, operating at a server, for establishing a data link in cooperation with a transceiver client installed in a terminal device, the apparatus including:

a service message receiving module 702 configured to receive a service message subscribing to a service scenario sent by a service platform;

a data link determining module 704 configured to determine a data link of a terminal device corresponding to the service message;

a service message sending module 706 configured to send the service message to a transceiving client running on the terminal device over the data link.

The embodiment of the terminal device provided by the specification is as follows:

corresponding to the service processing method applied to the terminal device described above, based on the same technical concept, one or more embodiments of the present specification further provide a terminal device, where the terminal device is configured to execute the service processing method provided above, and fig. 8 is a schematic structural diagram of a terminal device provided in one or more embodiments of the present specification.

The present embodiment provides a terminal device, including:

as shown in fig. 8, the terminal devices may have a large difference due to different configurations or performances, and may include one or more processors 801 and a memory 802, where the memory 802 may store one or more stored applications or data. Wherein the memory 802 may be a transient storage or a persistent storage. The application program stored in memory 802 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in the terminal device. Still further, the processor 801 may be configured to communicate with the memory 802 to execute a series of computer-executable instructions in the memory 802 on the terminal device. The terminal apparatus may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input/output interfaces 805, one or more keyboards 806, and the like.

In a particular embodiment, a terminal device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the terminal device, and the one or more programs configured to be executed by the one or more processors include computer-executable instructions for:

a receiving and sending client receives a service message of a subscription service scene sent by a server through a data link; the receiving and sending client is installed on the terminal equipment, the terminal equipment is also provided with an equipment application and a service container, and the service container is used for performing equipment login processing and service scene subscription processing of the terminal equipment; the transceiver client establishing the data link in response to an initialization call by the device application;

transmitting the service message into the device application to expose the service message through the device application;

and if the service message is triggered, calling the service container to acquire service detail data corresponding to the service message.

An embodiment of a service processing device provided in this specification is as follows:

corresponding to the service processing method applied to the service platform described above, based on the same technical concept, one or more embodiments of the present specification further provide a service processing device, where the service processing device is configured to execute the service processing method provided above, and fig. 9 is a schematic structural diagram of a service processing device provided in one or more embodiments of the present specification.

The service processing device provided by the embodiment includes:

as shown in fig. 9, the service processing device may have a relatively large difference due to different configurations or performances, and may include one or more processors 901 and a memory 902, where one or more stored applications or data may be stored in the memory 902. Memory 902 may be, among other things, transient storage or persistent storage. The application program stored in memory 902 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a service processing device. Still further, processor 901 may be configured to communicate with memory 902 to execute a series of computer-executable instructions in memory 902 on a service processing device. The service processing apparatus may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input/output interfaces 905, one or more keyboards 906, and the like.

In one particular embodiment, a service processing apparatus includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the service processing apparatus, and configured for execution by the one or more processors the one or more programs include computer-executable instructions for:

receiving service data of a subscription service scene synchronized by a service provider; the service processing equipment is applied to a service platform, and the service platform is used for matching a service container installed on the terminal equipment to perform equipment login processing and service scene subscription processing on the terminal equipment;

inquiring user equipment bound by the equipment user to which the service data belongs, and determining terminal equipment corresponding to the subscription service scene in the inquired user equipment;

and generating a service message of the service data and sending the service message to a server so as to send the service message to a receiving and sending client through a data link corresponding to the equipment information of the terminal equipment.

The second service processing apparatus embodiment provided in this specification is as follows:

corresponding to the service processing method applied to the service platform described above, based on the same technical concept, one or more embodiments of the present specification further provide a service processing device, where the service processing device is configured to execute the service processing method provided above, and fig. 10 is a schematic structural diagram of a service processing device provided in one or more embodiments of the present specification.

The service processing device provided by the embodiment includes:

as shown in fig. 10, the service processing device may have a large difference due to different configurations or performances, and may include one or more processors 1001 and a memory 1002, and one or more stored applications or data may be stored in the memory 1002. Memory 1002 may be, among other things, transient storage or persistent storage. The application programs stored in memory 1002 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in a service processing device. Still further, the processor 1001 may be configured to communicate with the memory 1002 to execute a series of computer-executable instructions in the memory 1002 on the service processing device. The service processing apparatus may also include one or more power supplies 1003, one or more wired or wireless network interfaces 1004, one or more input/output interfaces 1005, one or more keyboards 1006, etc.

receiving a service message for subscribing a service scene sent by a service platform; the service processing equipment runs through a server, and the server is used for establishing a data link in cooperation with a receiving and sending client installed on the terminal equipment;

determining a data link of the terminal equipment corresponding to the service message;

and sending the service message to a receiving and sending client operated by the terminal equipment through the data link.

An embodiment of a storage medium provided in this specification is as follows:

on the basis of the same technical concept, corresponding to the service processing method applied to the terminal device described above, one or more embodiments of the present specification further provide a storage medium.

The storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed by the processor, the following processes are implemented:

a receiving and sending client receives a service message of a subscription service scene sent by a server through a data link; the transceiver client establishing the data link in response to an initialization call by the device application;

transmitting the service message into a device application to expose the service message through the device application;

if the service message is triggered, calling a service container to acquire service detail data corresponding to the service message; the service container is used for performing equipment login processing and service scene subscription processing of the terminal equipment.

It should be noted that the embodiment related to the storage medium in this specification and the embodiment related to the service processing method in this specification are based on the same inventive concept, and therefore, specific implementation of this embodiment may refer to implementation of the foregoing corresponding method, and repeated details are not described here.

The second storage medium example provided in this specification is as follows:

on the basis of the same technical concept, corresponding to the service processing method applied to the service platform described above, one or more embodiments of the present specification further provide a storage medium.

receiving service data of a subscription service scene synchronized by a service provider;

The third storage medium embodiment provided in this specification is as follows:

on the basis of the same technical concept, corresponding to the service processing method applied to the server described above, one or more embodiments of the present specification further provide a storage medium.

receiving a service message for subscribing a service scene sent by a service platform;

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

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

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

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

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

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

The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

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

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

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

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

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

The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

The above description is only an example of this document and is not intended to limit this document. Various modifications and changes may occur to those skilled in the art from this document. Any modifications, equivalents, improvements, etc. which come within the spirit and principle of the disclosure are intended to be included within the scope of the claims of this document.

Claims

1. A service processing method is applied to terminal equipment, the terminal equipment is provided with equipment application, a service container and a receiving and sending client, and the service container is used for performing equipment login processing and service scene subscription processing of the terminal equipment; the method comprises the following steps:

the receiving and sending client receives a service message of a subscription service scene sent by a server through a data link; the transceiver client establishing the data link in response to an initialization call by the device application;

2. The service processing method according to claim 1, wherein the terminal device runs the device application at startup, and the transceiver client maintains a running state after receiving the initialization call initiated when the device application runs;

and, the data link is maintained in a long connection state after being established.

3. The service processing method of claim 1, the establishing the data link in response to an initialization call by the device application, comprising:

registering and calling back the equipment application based on the initialization call to obtain equipment information of the terminal equipment;

and establishing a data link with the server based on the equipment information.

4. The service processing method of claim 1, the device login process, comprising:

and establishing a binding relationship between the terminal equipment and the equipment user according to an application account number of the equipment user in a target application carried in a service request submitted by the service container, and recording the login state of the terminal equipment.

5. The service processing method according to claim 1, wherein the transceiver client is further configured to collect device service data of the terminal device, and upload the device service data to the server via the data link;

the server side forwards the equipment service data to a service platform of the service container, acquires a service data response returned by the service platform after the service processing is carried out on the equipment service data, and returns the service data response to the transceiving client side;

6. The service processing method of claim 1, the service scenario subscription process, comprising:

acquiring a subscription service scene subscribed by a device user in a service scene set of the terminal device, and generating a registration record of the terminal device for the subscription service scene;

and carrying out authorization processing on the terminal equipment aiming at the subscription service scene according to the authorization configuration information submitted aiming at the subscription service scene.

7. The service processing method according to claim 1, wherein the terminal device performs service scenario configuration access before starting;

the service scene configuration access comprises the following steps:

the service platform determines a service scene set formed by at least one service scene selected by a device provider in a service scene pool aiming at the terminal device;

8. The service processing method of claim 7, wherein the subroutines in the list comprise subroutines within a target application, and wherein the service container is configured with access entries for subroutines within the target application.

9. The service processing method according to claim 7, wherein the invoking the service container to obtain the service detail data corresponding to the service message includes:

10. A service processing method is applied to a service platform, and the service platform is used for matching a service container installed on a terminal device to perform device login processing and service scene subscription processing on the terminal device; the method comprises the following steps:

11. The service processing method of claim 10, the device login process, comprising:

12. The service processing method of claim 10, the service scenario subscription process, comprising:

13. The service processing method according to claim 10, wherein the terminal device performs service scenario configuration access before starting;

the service scene configuration access comprises the following steps:

determining a service scene set formed by at least one service scene selected by a device provider in a service scene pool aiming at the terminal device;

and associating the target subprogram to a service scene according to the target subprogram selected by the equipment provider in the list of each service in the service scene set.

14. The service processing method of claim 13, wherein the subroutines in the list comprise subroutines within a target application, and wherein the service container is configured with access entries for subroutines within the target application.

15. A service processing method is applied to a server, and the server is used for establishing a data link in cooperation with a receiving and sending client installed on terminal equipment; the method comprises the following steps:

16. A service processing device runs on a terminal device, the terminal device is provided with a device application, a service container and a transceiving client, and the service container is used for performing device login processing and service scene subscription processing of the terminal device; the device comprises:

a service message receiving module configured to receive, by the transceiver client, a service message of a subscription service scenario sent by a server over a data link; the transceiver client establishing the data link in response to an initialization call by the device application;

a service message import module configured to import the service message into the device application to expose the service message through the device application;

and the service detail data acquisition module is configured to call the service container to acquire the service detail data corresponding to the service message if the service message is triggered.

17. A service processing device runs on a service platform and is used for matching a service container installed on a terminal device to perform device login processing and service scene subscription processing on the terminal device; the device comprises:

the service data receiving module is configured to receive service data of the subscription service scene synchronized by the service provider;

a terminal device determining module configured to query a user device bound to a device user to which the service data belongs, and determine a terminal device corresponding to the subscription service scenario in the queried user device;

and the service message sending module is configured to generate a service message of the service data and send the service message to a server so as to send the service message to a transceiving client through a data link corresponding to the device information of the terminal device.

18. A service processing apparatus, operating on a server, for establishing a data link in cooperation with a transceiver client installed in a terminal device, the apparatus comprising:

the service message receiving module is configured to receive a service message of a subscription service scene sent by a service platform;

a data link determining module configured to determine a data link of a terminal device corresponding to the service message;

a service message sending module configured to send the service message to a transceiving client operated by the terminal device through the data link.

19. A terminal device, comprising:

a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to:

20. A service processing device, comprising:

21. A service processing device, comprising:

22. A storage medium storing computer-executable instructions that when executed by a processor implement the following:

23. A storage medium storing computer-executable instructions that when executed by a processor implement the following:

24. A storage medium storing computer-executable instructions that when executed by a processor implement the following: