Service processing method and device

Abstract

The embodiment of the invention provides a service processing method and device.The service processing method comprises the steps that the method is applied to terminal equipment, the terminal equipment is provided with an equipment application, a service container and a receiving and sending client side, and the service container is used for carrying out equipment login processing and service scene subscription processing of the terminal equipment; the method comprises the following steps: the transceiving client receives a service message of a subscription service scene sent by a server through a data link; the transmit-receive client establishes the data link in response to the initialization call of the device application; transmitting the service message to the equipment application so as to display the service message through the equipment application; and if the service message is triggered, calling the service container to obtain service detail data corresponding to the service message.

Description

[0001] This application is a divisional application of the Chinese invention patent application with the application date of January 7, 2022, application number CN202210018421.1, and name “Service Processing Method and Device”. Technical Field

[0002] This document relates to the field of data processing technology, and in particular to a service processing method and device. Background Art

[0003] With the development of Internet technology and the popularization of mobile terminals, more and more services have begun to extend to online scenarios, and application platform software that can carry multiple application sub-programs has emerged, avoiding users from installing different types of applications on mobile terminals. Instead, services are handled with the help of application sub-programs installed in the application platform software. At the same time, application sub-programs can also make full use of the abundant user traffic of the application platform software to provide support for the service improvement of application sub-programs. Summary of the invention

[0004] One or more embodiments of this specification provide a service processing method, which is applied to a terminal device, wherein the terminal device is installed with a device application, a service container, and a transceiver client, wherein the service container is used to perform device login processing and service scenario subscription processing of the terminal device; the method comprises: the transceiver client receives a service message of a subscription service scenario sent by a server via a data link. The transceiver client establishes the data link in response to an initialization call of the device application. The service message is passed to the device application so as to display the service message through the device application. If the service message is triggered, the service container is called to obtain the service detail data corresponding to the service message.

[0005] One or more embodiments of this specification provide a second service processing method, which is applied to a service platform, and the service platform is used to cooperate with the service container installed on the terminal device to perform device login processing and service scenario subscription processing for the terminal device; the method includes: receiving service data of the subscription service scenario synchronized by the service provider. Query the user device bound to the device user to which the service data belongs, and determine the terminal device corresponding to the subscription service scenario in the queried user device. Generate a service message for the service data and send it to the server, so as to send the service message to the transceiver client through the data link corresponding to the device information of the terminal device.

[0006] One or more embodiments of this specification provide a third service processing method, which is applied to a server, and the server is used to cooperate with a transceiver client installed on a terminal device to establish a data link; the method includes: receiving a service message of a subscription service scenario sent by a service platform. Determining a data link of a terminal device corresponding to the service message. Sending the service message to the transceiver client running on the terminal device through the data link.

[0007] One or more embodiments of the present specification provide a service processing device, which runs on a terminal device, wherein the terminal device is installed with a device application, a service container and a transceiver client, wherein the service container is used to perform device login processing and service scenario subscription processing of the terminal device; the device includes: a service message receiving module, which is configured for the transceiver client to receive a service message of a subscription service scenario sent by a server via a data link. The transceiver client establishes the data link in response to an initialization call of the device application. A service message incoming module, which is configured to pass the service message into the device application so as to display the service message through the device application. A service details data acquisition module, which is configured to call the service container to obtain service details data corresponding to the service message if the service message is triggered.

[0008] One or more embodiments of the present specification provide a second service processing device, which runs on a service platform and is used to cooperate with a service container installed on a terminal device to perform device login processing and service scenario subscription processing for the terminal device; the device includes: a service data receiving module, which is configured to receive service data of a subscription service scenario synchronized by a service provider. A terminal device determination module, which is configured to query the user device bound to the device user to which the service data belongs, and determine the terminal device corresponding to the subscription service scenario in the queried user device. A service message sending module, which is configured to generate a service message for the service data and send it to the server, so as to send the service message to the transceiver client through the data link corresponding to the device information of the terminal device.

[0009] One or more embodiments of this specification provide a third service processing device, which runs on the server side and is used to establish a data link with a transceiver client installed on a terminal device, and the device includes: a service message receiving module, which is configured to receive a service message of a subscription service scenario sent by a service platform. A data link determination module, which is configured to determine the data link of the terminal device corresponding to the service message. A service message sending module, which is configured to send the service message to the transceiver client running on the terminal device through the data link.

[0010] One or more embodiments of the present specification provide a terminal device, comprising: a processor; and a memory configured to store computer executable instructions, wherein when the computer executable instructions are executed, the processor: a transceiver client receives a service message of a subscription service scenario sent by a server via a data link. The transceiver client is installed on the terminal device, and the terminal device is also installed with a device application and a service container, and the service container is used to perform device login processing and service scenario subscription processing of the terminal device. The transceiver client establishes the data link in response to the initialization call of the device application. The service message is passed to the device application to display the service message through the device application. If the service message is triggered, the service container is called to obtain the service detail data corresponding to the service message.

[0011] One or more embodiments of the present specification provide a service processing device, including: a processor; and a memory configured to store computer executable instructions, which, when executed, cause the processor to: receive service data of a subscription service scenario synchronized by a service provider. The service processing device is applied to a service platform, and the service platform is used to cooperate with a service container installed on a terminal device to perform device login processing and service scenario subscription processing on the terminal device. Query the user device bound to the device user to which the service data belongs, and determine the terminal device corresponding to the subscription service scenario in the queried user device. Generate a service message for the service data and send it to the server, so as to send the service message to the transceiver client through the data link corresponding to the device information of the terminal device.

[0012] One or more embodiments of this specification provide a second service processing device, including: a processor; and a memory configured to store computer executable instructions, which, when executed, cause the processor to: receive a service message for a subscription service scenario sent by a service platform. The service processing device is operated by a server, and the server is used to establish a data link with a transceiver client installed on a terminal device. Determine the data link of the terminal device corresponding to the service message. Send the service message to the transceiver client running on the terminal device via the data link.

[0013] One or more embodiments of the present specification provide a storage medium for storing computer executable instructions, which implement the following process when executed by a processor: a transceiver client receives a service message for a subscription service scenario sent by a server via a data link. The transceiver client establishes the data link in response to an initialization call of the device application. The service message is passed to the device application to display the service message through the device application. If the service message is triggered, a service container is called to obtain service detail data corresponding to the service message. The service container is used to perform device login processing of a terminal device and service scenario subscription processing.

[0014] One or more embodiments of the present specification provide a second storage medium for storing computer executable instructions, which implement the following process when executed by a processor: receiving service data of a subscription service scenario synchronized by a service provider. Querying the user device bound to the device user to which the service data belongs, and determining the terminal device corresponding to the subscription service scenario in the queried user device. Generate a service message for the service data and send it to the server, so as to send the service message to the transceiver client through the data link corresponding to the device information of the terminal device.

[0015] One or more embodiments of this specification provide a third storage medium for storing computer executable instructions, which implement the following process when executed by a processor: receiving a service message of a subscription service scenario sent by a service platform. Determining a data link of a terminal device corresponding to the service message. Sending the service message to a transceiver client running on the terminal device through the data link. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate one or more embodiments of the present specification or the technical solutions in the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present specification. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative labor. Figure 1 A process flow chart of a service processing method provided for one or more embodiments of this specification; Figure 2 A timing diagram of a service processing method applied to an actual device scenario provided by one or more embodiments of this specification; Figure 3 A processing flow chart of a second service processing method provided for one or more embodiments of this specification; Figure 4A processing flow chart of a third service processing method provided for one or more embodiments of this specification; Figure 5 A schematic diagram of a service processing device provided for one or more embodiments of this specification; Figure 6 A schematic diagram of a second service processing device provided for one or more embodiments of this specification; Figure 7 A schematic diagram of a third service processing device provided for one or more embodiments of this specification; Figure 8 A schematic diagram of the structure of a terminal device provided for one or more embodiments of this specification; Fig. 9 A schematic diagram of the structure of a service processing device provided for one or more embodiments of this specification; Fig.10 A schematic diagram of the structure of a second service processing device provided in one or more embodiments of this specification. DETAILED DESCRIPTION

[0017] In order to enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below in conjunction with the drawings in one or more embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of them. Based on one or more embodiments of this specification, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this document.

[0018] This specification provides a service processing method embodiment: Reference Figure 1 The service processing method provided in this embodiment is applied to a terminal device, wherein the terminal device is installed with a device application, a service container, and a transceiver client, and the service container is used to perform device login processing and service scenario subscription processing of the terminal device; The method specifically includes steps S102 to S106.

[0019] Step S102: the transceiver client receives a service message of a subscription service scenario sent by the server through a data link.

[0020] The service processing method provided by the present application starts from the actual application scenario of the terminal device, accesses the corresponding service scenario for the terminal device, and accesses the service scenario by installing a service container on the terminal device using the service container as a carrier, and establishes a data link for the service message of the service scenario through the transceiver client for service message push by the terminal device, and calls the service container for corresponding service message access processing when the service message displayed by the device application is triggered, thereby reducing the operating pressure of the terminal device during the service use process through the transceiver client, reducing the development cost of the device provider for providing service access capabilities for the terminal device, and at the same time improving the flexibility and diversity of the use of the terminal device, and improving the adaptability of the terminal device to the actual use scenario by opening service subscription, so as to meet the diverse needs of users in the process of using the terminal device.

[0021] The terminal device described in this embodiment includes but is not limited to at least one of the following: a vehicle terminal installed in the vehicle, a terminal device external to the vehicle, a smart speaker, an unmanned vending machine, an autonomous radio, an interactive advertising screen, a POS device, and smart home appliances such as smart TVs and smart refrigerators.

[0022] The device application refers to the system application that the terminal device itself relies on to run. The service container refers to the running framework or running engine provided for the terminal device. By installing the service container on the terminal device, service access can be achieved on the terminal device.

[0023] The transceiver client refers to a client installed on the terminal device for receiving and sending service data. In this embodiment, a separate client for receiving and sending service data is installed on the terminal device. During the operation of the terminal device, it is only necessary to keep the transceiver client in a working state to ensure the service reception of the terminal device, without running a service container in the background of the terminal device. Compared with the service container, the transceiver client occupies less operating resources of the terminal device during operation, effectively reducing the occupation of the operating resources of the terminal device. Therefore, when the operating resources of the terminal device are limited, the transceiver client reduces the occupation of operating resources, which helps to improve the operating efficiency of the terminal device.

[0024] In actual applications, the service container and the transceiver client are installed and configured by the device provider. After the installation and configuration are completed, the terminal device can access the service through the installed service container and the transceiver client after startup. Optionally, the terminal device runs the device application at startup, and the device application initiates an initialization call to the transceiver client when running. The transceiver client establishes a data link with the server in response to the initialization call of the device application, and the transceiver client remains in operation after receiving the initialization call. When the transceiver client remains in operation after establishing the data link, the data link is maintained in a long connection state after establishment. The device provider includes the manufacturer, seller and / or service operator of the terminal device.

[0025] Specifically, in an optional implementation manner provided by this embodiment, the process of the transceiver client establishing the data link in response to the initialization call of the device application is implemented in the following manner: based on the initialization call, a registration callback is performed on the device application to obtain the device information of the terminal device; based on the device information, a data link is established with the server.

[0026] After the terminal device installs the service container, the device user of the terminal device can 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 completing the device login processing and service scenario subscription processing. The service scenario described in this embodiment includes a service strategy or service domain determined based on the services involved in the actual use scenario of the terminal device, and each service scenario is associated with a number of subroutines related to the service scenario or within the service scope of the service scenario.

[0027] After the service container and the transceiver client are installed on the terminal device, although the terminal device has the ability to provide services, it cannot provide services to the user without the user's operation confirmation. The device login process described in this embodiment refers to the process in which the user confirms to enable the service capability of the terminal device by logging in. Optionally, the device login process includes: establishing a binding relationship between the terminal device and the device user according to the application account of the device user in the target application carried in the service request submitted by the service container, and recording the login status of the terminal device.

[0028] As described above, this embodiment installs the service container and the transceiver client on the terminal device so that the terminal device has the ability to provide services. However, in actual use, the device user is required to subscribe to the service scenario and perform corresponding authorization processing on the terminal device for the subscribed service scenario, so as to access the service based on the service scenario subscription and authorization processing. In an optional implementation manner provided by this embodiment, the service scenario subscription processing specifically includes: obtaining the subscription service scenario subscribed by the device user in the service scenario set of the terminal device, and generating a registration record of the terminal device for the subscription service scenario; and performing authorization processing of the terminal device for the subscription service scenario according to the authorization configuration information submitted for the subscription service scenario.

[0029] It should be noted that in this embodiment, the service scenarios subscribed by the device user for the terminal device are pre-configured and accessed by the device provider. For example, before the terminal device leaves the factory, several service scenarios are configured and accessed for the terminal device. Based on this, after the terminal device is transferred to the device user, the device user can subscribe to one or more service scenarios in the service scenarios pre-accessed by the device provider. The one or more service scenarios subscribed by the device user are called subscription service scenarios. In an optional implementation manner provided by this embodiment, the terminal device performs service scenario configuration access before startup; specifically, the service scenario configuration access includes: The service platform determines a service scenario set consisting of at least one service scenario selected by the device provider in a service scenario pool for the terminal device; the service pool consists of multiple service scenarios pre-configured by the service platform; Sending a list of subroutines associated with each service scenario in the service scenario set to the device provider; According to the target subprogram selected by the device provider in the list of each service in the service scenario set, the target subprogram is associated with the service scenario.

[0030] The subprogram refers to a program package or application component that is installed on an application platform (or application) or loaded and installed by an application platform. From a service perspective, the subprogram has the ability to independently provide self-closed-loop services, such as a subprogram that runs in an application and provides self-closed-loop capabilities for vehicle-related services or ordering services. Optionally, the subprograms in the list include subprograms in the target application, and the service container is configured with an access entry for the subprogram in the target application.

[0031] In specific implementation, after the service container installed on the terminal device completes the device login processing and service scenario subscription processing of the terminal device, and the transceiver client installed on the terminal device completes the establishment of the data link, the service platform receives the service data of the subscription service scenario synchronized by the service provider, queries the user device bound to the user to which the service data belongs, and determines the terminal device corresponding to the subscription service scenario among the queried user devices, generates a service message for the service data and sends it to the server of the transceiver client; after receiving the service message sent by the service platform, the server of the transceiver client 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; correspondingly, here the transceiver client receives the service message of the subscription service scenario sent by the server through the data link.

[0032] Step S104: transferring the service message to the device application so as to display the service message through the device application.

[0033] In specific implementation, after receiving the service message, the transceiver client installed in the terminal device transmits the service message to the device application to display the service message through the device application. For example, the device application installed in the terminal device calls the display interface of the terminal device to display the service message. For another example, the device application installed in the terminal device calls the voice playback interface of the terminal device to play the service message.

[0034] In addition, in order to improve the display efficiency of the service message, the sending and receiving client can also call the corresponding interface of the terminal device to display the service message according to the message type of the service message; or, in order to improve the interactivity of the service message display, when it is detected that the service container installed on the terminal device is in a running state, the service message is passed to the service container, and the service container displays the service message. The device user can use the access interface provided by the service container to perform interactive operations on the service message.

[0035] Step S106: If the service message is triggered, the service container is called to obtain service detail data corresponding to the service message.

[0036] After the service message is displayed, if the service message is triggered, the service container is called to perform response processing of the service message, and the response processing includes obtaining service detail data corresponding to the service message and displaying the service detail data. Specifically, the service application that displays the service message may initiate a call to the service container after detecting a trigger instruction of the service message, or the transceiver client that receives the service message may initiate a call to the service container after detecting a trigger instruction of the service message.

[0037] In an optional implementation manner provided by this embodiment, calling the service container to obtain service detail data corresponding to the service message includes: Sending a call instruction to the service container to start and run a target subroutine corresponding to the service message based on the service container; The service details data of the service message are obtained and displayed based on the target subprogram.

[0038] As described above, the transceiver client installed on the terminal device is used to receive and send service data, specifically including receiving service messages pushed by the server, uploading the service data of the terminal device to the server, and on this basis, in the process of using the terminal device, in many cases it is necessary to make corresponding service requests to the service provider or the service platform. In order to improve the processing efficiency of the service request process, and also to avoid starting the service container and using the service container to make service requests to occupy the operating resources of the terminal device, the service request processing can also be performed through the transceiver client. Optionally, the transceiver client is also used to collect the device service data of the terminal device and upload it to the server through the data link; the server forwards the device service data to the service platform of the service container, and obtains the service data response returned by the service platform after the service processing of the device service data and transmits it back to the transceiver client; The device data of the terminal device includes: user data collected by the terminal device, and / or service request data input by a device user and received by the terminal device.

[0039] The following uses the application of a service processing method provided in this embodiment in an actual device scenario as an example to further illustrate the service processing method provided in this embodiment. Figure 2 The service processing method applied to the terminal device specifically includes the following steps: The terminal device is installed with a device application, a transceiver client and a service container.

[0040] Step S202: the transceiver client receives an initialization call initiated by the device application when it is started.

[0041] Step S204: the sending and receiving client performs a registration callback on the device application to obtain device information of the terminal device.

[0042] Step S206: Establish a data link with the server based on the device information, and maintain a long connection state of the data link.

[0043] Step S208: The service container receives the activation instruction submitted by the device user for the terminal device and forwards it to the service platform.

[0044] Step S212: the service container generates a login request for the application account of the carrying device user in the target application and forwards it to the service platform.

[0045] Step S218: The service container obtains the subscription service scenario subscribed by the device user from the service scenario set accessed by the terminal device and submits it to the service platform.

[0046] Step S234, the transceiver client receives the service message sent by the server through the data link.

[0047] Step S236: transferring the service message to the device application so as to display the service message through the device application.

[0048] Step S238: If the device application detects that the service message is triggered, the service container is called to obtain service detail data corresponding to the service message.

[0049] The second service processing method embodiment provided in this specification is as follows: The service processing method applied to the service platform provided in this embodiment cooperates with the service processing method applied to the terminal device provided in the above embodiment during execution, and cooperates with the service processing method applied to the server provided in the following embodiment during execution. Therefore, please refer to the corresponding contents of the above embodiment and the following embodiment when reading this embodiment.

[0050] Reference Figure 3 The service processing method provided in this embodiment is applied to a service platform, and the service platform is used to cooperate with the service container installed in the terminal device to perform device login processing and service scenario subscription processing for the terminal device; the method specifically includes steps S302 to S306.

[0051] Step S302: receiving service data of the subscription service scenario synchronized by the service provider.

[0052] The service scenario described in this embodiment includes a service strategy or service domain determined based on the services involved in the actual use scenario of the terminal device, and each service scenario is associated with a number of subprograms related to the service scenario or within the service scope of the service scenario. The subscription service scenario refers to the service scenario subscribed by the device user in the service scenario set of the terminal device.

[0053] Optionally, the device login processing includes: establishing a binding relationship between the terminal device and the device user according to the application account of the device user in the target application carried in the service request submitted by the service container, and recording the login status of the terminal device.

[0054] It should be noted that the service scenario subscription performed by the terminal device is implemented by the service container installed on the terminal device. The service container refers to the operating framework or operating engine provided for the terminal device. By installing the service container on the terminal device, service access can be achieved on the terminal device. In an optional implementation provided by this embodiment, the service scenario subscription processing specifically includes: obtaining the subscription service scenario subscribed by the device user in the service scenario set of the terminal device, and generating a registration record of the terminal device for the subscription service scenario; performing authorization processing of the terminal device for the subscription service scenario according to the authorization configuration information submitted for the subscription service scenario.

[0055] In this embodiment, the service scenarios subscribed by the device user for the terminal device are pre-configured and accessed by the device provider. For example, before the terminal device leaves the factory, several service scenarios are configured and accessed for the terminal device. Based on this, after the terminal device is transferred to the device user, the device user can subscribe to one or more service scenarios in the service scenarios pre-accessed by the device provider. The one or more service scenarios subscribed by the device user are called subscription service scenarios. In an optional implementation manner provided by this embodiment, the terminal device performs service scenario configuration access before startup; specifically, the service scenario configuration access includes: The service platform determines a service scenario set consisting of at least one service scenario selected by the device provider in a service scenario pool for the terminal device; the service pool consists of multiple service scenarios pre-configured by the service platform; Sending a list of subroutines associated with each service scenario in the service scenario set to the device provider; According to the target subprogram selected by the device provider in the list of each service in the service scenario set, the target subprogram is associated with the service scenario.

[0056] The subprogram refers to a program package or application component that is installed on an application platform (or application) or loaded and installed by an application platform. From a service perspective, the subprogram has the ability to independently provide self-closed-loop services, such as a subprogram that runs in an application and provides self-closed-loop capabilities for vehicle-related services or ordering services. Optionally, the subprograms in the list include subprograms in the target application, and the service container is configured with an access entry for the subprogram in the target application.

[0057] Step S304, querying the user devices bound to the device user to which the service data belongs, and determining the terminal device corresponding to the subscription service scenario among the queried user devices.

[0058] The terminal device described in this embodiment includes but is not limited to at least one of the following: a vehicle terminal installed in the vehicle, a terminal device external to the vehicle, a smart speaker, an unmanned vending machine, an autonomous radio, an interactive advertising screen, a POS device, and smart home appliances such as smart TVs and smart refrigerators.

[0059] Step S306: Generate a service message of the service data and send it to the server, so as to send the service message to the transceiver client through the data link corresponding to the device information of the terminal device.

[0060] The terminal device is also installed with a device application and the transceiver client; the device application refers to the system application that the terminal device itself relies on for operation. The transceiver client refers to the client installed by the terminal device for receiving and sending service data. In this embodiment, by installing a separate client for receiving and sending service data on the terminal device, during the operation of the terminal device, it is only necessary to keep the transceiver client in working state to ensure the service reception of the terminal device, without running the service container in the background of the terminal device. Compared with the service container, the transceiver client occupies less operating resources of the terminal device during operation, which effectively reduces the occupation of the operating resources of the terminal device. Therefore, when the operating resources of the terminal device are limited, the transceiver client reduces the occupation of operating resources, which helps to improve the operating efficiency of the terminal device.

[0061] In actual applications, the service container and the transceiver client are installed and configured by the device provider. After the installation and configuration are completed, the terminal device can access the service through the installed service container and the transceiver client after startup. Optionally, the terminal device runs the device application at startup, and the device application initiates an initialization call to the transceiver client when running. The transceiver client establishes a data link with the server in response to the initialization call of the device application, and the transceiver client remains in operation after receiving the initialization call. When the transceiver client remains in operation after establishing the data link, the data link is maintained in a long connection state after establishment. The device provider includes the manufacturer, seller and / or service operator of the terminal device.

[0062] The following uses the application of a service processing method provided in this embodiment in an actual device scenario as an example to further illustrate the service processing method provided in this embodiment. Figure 2 , a service processing method applied to a service platform specifically includes the following steps.

[0063] Step S210: The service platform performs activation processing of the terminal device according to the activation instruction of the terminal device submitted by the service container.

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

[0065] Step S216: The service platform sends a set of service scenarios for access of the terminal device by the device provider to the service container.

[0066] Step S220: The service platform receives the subscription service scenario submitted by the service container and generates a subscription service scenario registration record.

[0067] Step S222: The service platform performs authorization processing on the subprogram associated with the subscription service scenario.

[0068] Step S224: the service platform receives the service data of the subscription service scenario synchronized by the service provider.

[0069] The service provider refers to a service provider that provides corresponding services for the subprogram associated with the subscription service scenario.

[0070] Step S226, the service platform queries the user devices bound to the device user to which the service data belongs, and determines the terminal devices corresponding to the subscription service scenario among the queried user devices.

[0071] Step S228: The service platform generates a service message of the service data and sends it to the server.

[0072] The third service processing method embodiment provided in this specification is as follows: Reference Figure 4 The service processing method provided in this embodiment is applied to the server, and the server is used to cooperate with the transceiver client installed in the terminal device to establish a data link; the method specifically includes steps S402 to S406.

[0073] The service processing method applied to the service platform provided in this embodiment cooperates with the service processing method applied to the terminal device provided in the above embodiment during execution, and cooperates with the service processing method applied to the service platform provided in the above embodiment during execution. Therefore, please refer to the corresponding content of the above embodiment when reading this embodiment, and this embodiment will not be repeated here.

[0074] Step S402, receiving a service message of a subscription service scenario sent by a service platform; Step S404, determining a data link of a terminal device corresponding to the service message; Step S406: Send the service message to the transceiver client running on the terminal device through the data link.

[0075] In this embodiment, the terminal device is installed with a device application, a service container and the transceiver client, and the service container is used to perform device login processing and service scenario subscription processing of the terminal device; the transceiver client establishes the data link in response to the initialization call of the device application.

[0076] The transceiver client refers to a client installed on the terminal device for receiving and sending service data. In this embodiment, a separate client for receiving and sending service data is installed on the terminal device. During the operation of the terminal device, it is only necessary to keep the transceiver client in a working state to ensure the service reception of the terminal device, without running a service container in the background of the terminal device. Compared with the service container, the transceiver client occupies less operating resources of the terminal device during operation, effectively reducing the occupation of the operating resources of the terminal device. Therefore, when the operating resources of the terminal device are limited, the transceiver client reduces the occupation of operating resources, which helps to improve the operating efficiency of the terminal device.

[0077] In actual applications, the service container and the transceiver client are installed and configured by the device provider. After the installation and configuration are completed, the terminal device can access the service through the installed service container and the transceiver client after startup. Optionally, the terminal device runs the device application at startup, and the device application initiates an initialization call to the transceiver client when running. The transceiver client establishes a data link with the server in response to the initialization call of the device application, and the transceiver client remains in operation after receiving the initialization call. When the transceiver client remains in operation after establishing the data link, the data link is maintained in a long connection state after establishment. The device provider includes the manufacturer, seller and / or service operator of the terminal device.

[0078] Specifically, in an optional implementation manner provided by this embodiment, the process of the transceiver client establishing the data link in response to the initialization call of the device application is implemented in the following manner: based on the initialization call, a registration callback is performed on the device application to obtain the device information of the terminal device; based on the device information, a data link is established with the server.

[0079] The following uses the application of a service processing method provided in this embodiment in an actual device scenario as an example to further illustrate the service processing method provided in this embodiment. Figure 2 , a service processing method applied to the server side specifically includes the following steps.

[0080] Step S230: the server receives a service message sent by the service platform.

[0081] 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.

[0082] An embodiment of a service processing device provided in this specification is as follows: In the above-mentioned embodiment, a service processing method applied to a terminal device is provided, and correspondingly, a service processing device running on the terminal device is also provided, which will be described below with reference to the accompanying drawings.

[0083] Reference Figure 5 , which shows a schematic diagram of a service processing device provided in this embodiment.

[0084] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0085] This embodiment provides a service processing device, which runs on a terminal device. The terminal device is installed with a device application, a service container, and a transceiver client. The service container is used to perform device login processing and service scenario subscription processing of the terminal device. The device includes: The service message receiving module 502 is configured for the transceiver client to receive a service message of a subscription service scenario sent by the server through a data link; the transceiver client establishes the data link in response to the initialization call of the device application; A service message input module 504 is configured to input the service message into the device application so as to display the service message through the device application; The service detail data acquisition module 506 is configured to call the service container to acquire the service detail data corresponding to the service message if the service message is triggered.

[0086] The second service processing device embodiment provided in this specification is as follows: In the above-mentioned embodiment, a service processing method applied to a service platform is provided, and correspondingly, a service processing device running on the service platform is also provided, which will be described below with reference to the accompanying drawings.

[0087] Reference Figure 6 , which shows a schematic diagram of a service processing device provided in this embodiment.

[0088] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0089] This embodiment provides a service processing device, which runs on a service platform and is used to cooperate with a service container installed on a terminal device to perform device login processing and service scenario subscription processing on the terminal device; the device includes: A service data receiving module 602 is configured to receive service data of a subscription service scenario synchronized by a service provider; The terminal device determination module 604 is configured to query the user device bound to the device user to which the service data belongs, and determine the terminal device corresponding to the subscription service scenario among the queried user devices; The service message sending module 606 is configured to generate a service message of the service data and send it to the server, so as to send the service message to the transceiver client through the data link corresponding to the device information of the terminal device.

[0090] The third service processing device embodiment provided in this specification is as follows: In the above-mentioned embodiment, a service processing method applied to a server is provided, and correspondingly, a service processing device running on the server is also provided, which will be described below with reference to the accompanying drawings.

[0091] Reference Figure 7 , which shows a schematic diagram of a service processing device provided in this embodiment.

[0092] Since the device embodiment corresponds to the method embodiment, the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above. The device embodiment described below is only illustrative.

[0093] This embodiment provides a service processing device, which runs on a server and is used to cooperate with a transceiver client installed on a terminal device to establish a data link. The device includes: The service message receiving module 702 is configured to receive a service message of a subscription service scenario sent by a service platform; A data link determination module 704 is configured to determine a data link of a terminal device corresponding to the service message; The service message sending module 706 is configured to send the service message to the transceiver client running on the terminal device through the data link.

[0094] An embodiment of a terminal device provided in this specification is as follows: Corresponding to the service processing method applied to a terminal device described above, based on the same technical concept, one or more embodiments of this specification also provide a terminal device, which is used to execute the service processing method provided above. Figure 8 A schematic diagram of the structure of a terminal device provided for one or more embodiments of this specification.

[0095] This embodiment provides a terminal device, including: like Figure 8As shown, the terminal device may have relatively large differences due to different configurations or performances, and may include one or more processors 801 and memory 802, and the memory 802 may store one or more storage applications or data. Among them, the memory 802 may be a temporary storage or a permanent storage. The application stored in the memory 802 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the terminal device. Furthermore, 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 device 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, etc.

[0096] In a specific embodiment, the 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 in the terminal device, and the one or more programs are configured to be executed by one or more processors, including computer executable instructions for performing the following: The transceiver client receives a service message of a subscription service scenario sent by the server through a data link; the transceiver client is installed on the terminal device, and the terminal device is also installed with a device application and a service container, and the service container is used to perform device login processing and service scenario subscription processing of the terminal device; the transceiver client establishes the data link in response to the initialization call of the device application; transferring the service message to the device application so as to display the service message through the device application; If the service message is triggered, the service container is called to obtain service detail data corresponding to the service message.

[0097] 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 this specification also provide a service processing device, which is used to execute the service processing method provided above. Fig. 9 A schematic diagram of the structure of a service processing device provided in one or more embodiments of this specification.

[0098] This embodiment provides a service processing device, including: like Fig. 9As shown, the service processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 901 and memory 902, and the memory 902 may store one or more storage applications or data. Among them, the memory 902 may be a short-term storage or a persistent storage. The application stored in the memory 902 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the service processing device. Furthermore, the processor 901 may be configured to communicate with the memory 902 and execute a series of computer executable instructions in the memory 902 on the service processing device. The service processing device 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, etc.

[0099] In a specific embodiment, the service processing 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 in the service processing device, and the one or more programs are configured to be executed by one or more processors, including computer executable instructions for performing the following: Receiving service data of a subscription service scenario synchronized by a service provider; the service processing device is applied to a service platform, and the service platform is used to cooperate with a service container installed on a terminal device to perform device login processing and service scenario subscription processing on the terminal device; Querying the user device bound to the device user to which the service data belongs, and determining the terminal device corresponding to the subscription service scenario among the queried user devices; A service message of the service data is generated and sent to the service end, so as to send the service message to the transceiver client through the data link corresponding to the device information of the terminal device.

[0100] The second service processing device 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 this specification also provide a service processing device, which is used to execute the service processing method provided above. Fig.10 A schematic diagram of the structure of a service processing device provided in one or more embodiments of this specification.

[0101] This embodiment provides a service processing device, including: like Fig.10As shown, the service processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 1001 and memory 1002, and the memory 1002 may store one or more storage applications or data. Among them, the memory 1002 may be a short-term storage or a persistent storage. The application stored in the memory 1002 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the service processing device. Furthermore, the processor 1001 may be configured to communicate with the memory 1002 and execute a series of computer executable instructions in the memory 1002 on the service processing device. The service processing device 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.

[0102] In a specific embodiment, the service processing 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 in the service processing device, and the one or more programs are configured to be executed by one or more processors, including computer executable instructions for performing the following: Receiving a service message of a subscription service scenario sent by a service platform; the service processing device is operated by a server, and the server is used to cooperate with a transceiver client installed on a terminal device to establish a data link; Determine a data link of a terminal device corresponding to the service message; The service message is sent to a transceiver client running on the terminal device via the data link.

[0103] An embodiment of a storage medium provided in this specification is as follows: Corresponding to the above-described service processing method applied to a terminal device, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0104] The storage medium provided in this embodiment is used to store computer executable instructions, and the computer executable instructions implement the following process when executed by a processor: The transceiver client receives a service message of a subscription service scenario sent by the server through a data link; the transceiver client establishes the data link in response to an initialization call of the device application; transferring the service message to a device application so as to display the service message through the device application; If the service message is triggered, the service container is called to obtain the service detail data corresponding to the service message; the service container is used to perform device login processing and service scenario subscription processing of the terminal device.

[0105] It should be noted that the embodiments of the storage medium in this specification and the embodiments of the service processing method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding method mentioned above, and the repeated parts will not be repeated.

[0106] The second storage medium 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 this specification also provide a storage medium.

[0107] The storage medium provided in this embodiment is used to store computer executable instructions, and the computer executable instructions implement the following process when executed by a processor: Receive service data of the subscription service scenario synchronized by the service provider; Querying the user device bound to the device user to which the service data belongs, and determining the terminal device corresponding to the subscription service scenario among the queried user devices; A service message of the service data is generated and sent to the service end, so as to send the service message to the transceiver client through the data link corresponding to the device information of the terminal device.

[0108] It should be noted that the embodiments of the storage medium in this specification and the embodiments of the service processing method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding method mentioned above, and the repeated parts will not be repeated.

[0109] The third storage medium embodiment provided in this specification is as follows: Corresponding to the service processing method applied to the server described above, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0110] The storage medium provided in this embodiment is used to store computer executable instructions, and the computer executable instructions implement the following process when executed by a processor: Receive service messages for subscription service scenarios sent by the service platform; Determine a data link of a terminal device corresponding to the service message; The service message is sent to a transceiver client running on the terminal device via the data link.

[0111] It should be noted that the embodiments of the storage medium in this specification and the embodiments of the service processing method in this specification are based on the same inventive concept, so the specific implementation of this embodiment can refer to the implementation of the corresponding method mentioned above, and the repeated parts will not be repeated.

[0112] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0113] In the 1930s, improvements to a technology could be clearly distinguished as hardware improvements (for example, improvements to circuit structures such as diodes, transistors, switches, etc.) or software improvements (improvements to method flows). However, with the development of technology, many of today's method flow improvements can be regarded as direct improvements to hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that an improvement in a method flow cannot be implemented using hardware entity modules. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask chip manufacturers to design and produce dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0114] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0115] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, 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.

[0116] For the convenience of description, the above devices are described in terms of functions and are divided into various units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0117] It should be understood by those skilled in the art that one or more embodiments of the present specification may be provided as a method, system or computer program product. Therefore, one or more embodiments of the present specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0118] This specification is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of this specification. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0119] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0120] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

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

[0122] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0123] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules 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 disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0124] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

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

[0126] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0127] The above description is only an embodiment of this document and is not intended to limit this document. For those skilled in the art, this document may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this document should be included in the scope of the claims of this document.

Claims

1. A service processing method, applied to a terminal device, wherein the terminal device is installed with a device application, a service container, and a transceiver client; the method comprises: The transceiver client receives a service message of a subscription service scenario sent by the server through a data link; The transceiver client establishes the data link in response to the initialization call of the device application; transferring the service message to the device application so as to display the service message through the device application; If the service message is triggered, the service container is called to obtain service detail data corresponding to the service message.

2. The service processing method according to claim 1, wherein the terminal device runs the device application when it is started, and the transceiver client remains in the running state after receiving the initialization call initiated when the device application is running; Furthermore, the data link is maintained in a long connection state after being established.

3. The service processing method according to claim 1, wherein establishing the data link in response to the initialization call of the device application comprises: Performing a registration callback on the device application based on the initialization call to obtain device information of the terminal device; A data link with the server is established based on the device information.

4. The service processing method according to claim 1, wherein the service container is used to perform device login processing and service scenario subscription processing of the terminal device; The device login process includes: According to the application account of the device user in the target application carried in the service request submitted by the service container, a binding relationship between the terminal device and the device user is established, and the login status of the terminal device is recorded.

5. The service processing method according to claim 1, wherein the transceiver client is further used to collect device service data of the terminal device and upload it to the server through the data link; The server forwards the device service data to the service platform of the service container, and obtains a service data response returned by the service platform after performing service processing on the device service data and transmits it back to the transceiver client; in, The device data of the terminal device includes: user data collected by the terminal device, and / or service request data input by a device user and received by the terminal device.

6. The service processing method according to claim 4, wherein the service scenario subscription processing comprises: Acquire a subscription service scenario subscribed by a device user from a service scenario set of the terminal device, and generate a registration record of the terminal device for the subscription service scenario; The terminal device performs authorization processing for the subscription service scenario according to the authorization configuration information submitted for the subscription service scenario.

7. The service processing method according to claim 1, wherein the terminal device performs service scenario configuration access before startup; The service scenario configuration access includes: The service platform determines a service scenario set consisting of at least one service scenario selected by the device provider from the service scenario pool for the terminal device; Sending a list of subroutines associated with each service scenario in the service scenario set to the device provider; According to the target subprogram selected by the device provider in the list of each service in the service scenario set, the target subprogram is associated with the service scenario.

8. The service processing method according to claim 7, wherein the subprograms in the list include subprograms within a target application, and the service container is configured with an access entry for the subprograms within the target application.

9. The service processing method according to claim 7, wherein the calling of the service container to obtain service detail data corresponding to the service message comprises: Sending a call instruction to the service container to start and run a target subroutine corresponding to the service message based on the service container; The service details data of the service message are obtained and displayed based on the target subprogram.

10. A service processing method, applied to a service platform, comprising: Receive service data of the subscription service scenario synchronized by the service provider; Querying the user device bound to the device user to which the service data belongs, and determining the terminal device corresponding to the subscription service scenario among the queried user devices; Generate a service message for the service data and send it to the server, so as to send the service message to the transceiver client installed on the terminal device through the data link corresponding to the device information of the terminal device; the data link is established by the transceiver client in response to the initialization call of the device application installed on the terminal device.

11. The service processing method according to claim 10, wherein the service platform is used to cooperate with the service container installed on the terminal device to perform device login processing on the terminal device; The device login process includes: According to the application account of the device user in the target application carried in the service request submitted by the service container, a binding relationship between the terminal device and the device user is established, and the login status of the terminal device is recorded.

12. The service processing method according to claim 10, wherein the service platform is used to cooperate with the service container installed on the terminal device to perform service scenario subscription processing on the terminal device; The service scenario subscription process includes: Acquire the subscription service scenario subscribed by the device user from the service scenario set of the terminal device, and generate a registration record of the terminal device for the subscription service scenario; The terminal device performs authorization processing for the subscription service scenario according to the authorization configuration information submitted for the subscription service scenario.

13. The service processing method according to claim 10, wherein the terminal device performs service scenario configuration access before startup; The service scenario configuration access includes: Determine a service scenario set consisting of at least one service scenario selected by the device provider for the terminal device in a service scenario pool; Sending a list of subroutines associated with each service scenario in the service scenario set to the device provider; According to the target subprogram selected by the device provider in the list of each service in the service scenario set, the target subprogram is associated with the service scenario.

14. The service processing method according to claim 13, wherein the subprograms in the list include subprograms in a target application, and the service container is configured with an access entry for the subprograms in the target application.

15. A service processing method, applied to a server, the server being used to cooperate with a transceiver client installed in a terminal device to establish a data link in response to an initialization call of a device application; The transceiver client, the device application and the service container are installed on the terminal device; the method comprises: Receive service messages for subscription service scenarios sent by the service platform; Determine a data link of the terminal device corresponding to the service message; The service message is sent to the transceiver client running on the terminal device via the data link.

16. A service processing device, running on a terminal device, wherein the terminal device is installed with a device application, a service container, and a transceiver client; 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 the server via a data link; The transceiver client establishes the data link in response to the initialization call of the device application; a service message input module, configured to input the service message into the device application so as to display the service message through the device application; 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, running on a service platform, comprising: A service data receiving module, configured to receive service data of a subscription service scenario synchronized by a service provider; A terminal device determination module is configured to query the user device bound to the device user to which the service data belongs, and determine the terminal device corresponding to the subscription service scenario among the queried user devices; A service message sending module is configured to generate a service message of the service data and send it to the server, so as to send the service message to the transceiver client installed on the terminal device through the data link corresponding to the device information of the terminal device; the data link is established by the transceiver client in response to the initialization call of the device application installed on the terminal device.

18. A service processing device, running on a server, for cooperating with a transceiver client installed on a terminal device to establish a data link in response to an initialization call of a device application; The transceiver client, the device application and the service container are installed on the terminal device; the apparatus comprises: A service message receiving module, configured to receive a service message of a subscription service scenario sent by a service platform; A data link determination module, configured to determine a data link of the terminal device corresponding to the service message; The service message sending module is configured to send the service message to the transceiver client running on the terminal device through the data link.

19. A terminal device, comprising: processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: The transceiver client receives a service message of a subscription service scenario sent by the server through a data link; the transceiver client is installed in the terminal device, and the terminal device is also installed with a device application and a service container; The transceiver client establishes the data link in response to the initialization call of the device application; transferring the service message to the device application so as to display the service message through the device application; If the service message is triggered, the service container is called to obtain service detail data corresponding to the service message.

20. A service processing device, comprising: processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: Receiving service data of a subscription service scenario synchronized by a service provider; the service processing device is applied to a service platform; Querying the user device bound to the device user to which the service data belongs, and determining the terminal device corresponding to the subscription service scenario among the queried user devices; Generate a service message for the service data and send it to the server, so as to send the service message to the transceiver client installed on the terminal device through the data link corresponding to the device information of the terminal device; the data link is established by the transceiver client in response to the initialization call of the device application installed on the terminal device.

21. A service processing device, comprising: processor; and a memory configured to store computer executable instructions that, when executed, cause the processor to: Receiving a service message of a subscription service scenario sent by a service platform; the service processing device runs on a server, and the server is used to cooperate with a transceiver client installed on a terminal device to establish a data link in response to an initialization call of a device application; the transceiver client, the device application and the service container are installed on the terminal device; Determine a data link of the terminal device corresponding to the service message; The service message is sent to the transceiver client running on the terminal device via the data link.

22. A storage medium for storing computer executable instructions, wherein the computer executable instructions, when executed by a processor, implement the following process: The transceiver client installed in the terminal device receives the service message of the subscription service scenario sent by the server through the data link; the transceiver client establishes the data link in response to the initialization call of the device application installed in the terminal device; transferring the service message to a device application so as to display the service message through the device application; If the service message is triggered, the service container installed in the terminal device is called to obtain service detail data corresponding to the service message.

23. A storage medium for storing computer executable instructions, wherein the computer executable instructions, when executed by a processor, implement the following process: Receive service data of the subscription service scenario synchronized by the service provider; Querying the user device bound to the device user to which the service data belongs, and determining the terminal device corresponding to the subscription service scenario among the queried user devices; Generate a service message for the service data and send it to the server, so as to send the service message to the transceiver client installed on the terminal device through the data link corresponding to the device information of the terminal device; the data link is established by the transceiver client in response to the initialization call of the device application installed on the terminal device.

24. A storage medium for storing computer executable instructions, wherein the computer executable instructions, when executed by a processor, implement the following process: Receiving a service message of a subscription service scenario sent by a service platform; the storage medium is used on the server side, and the server side is used to cooperate with a transceiver client installed on a terminal device to establish a data link in response to an initialization call of a device application; the transceiver client, the device application and the service container are installed on the terminal device; Determine a data link of the terminal device corresponding to the service message; The service message is sent to the transceiver client running on the terminal device via the data link.

Images