An application service device and a terminal device

Abstract

The application provides an application service device and a terminal device, the application service device comprises: at least one function module; each function module of the at least one function module is respectively connected with a terminal device; each function module is used for providing a target function for the terminal device, and the function module receives indication information sent by the terminal device, the indication information is used for controlling whether the function module needs to start the corresponding target function; when the indication information indicates that the corresponding target function needs to be started, the terminal device is communicated and transmitted with the data corresponding to the target function. The application can control the start of the target function corresponding to the application service device when the terminal device needs, and solve the problem of waste of hardware resources of the embedded real-time operating system in the prior art.

Description

Technical Field

[0001] This invention relates to the field of Internet of Things (IoT) technology, and in particular to an application service device and a terminal device. Background Technology

[0002] The development of domestically produced embedded real-time operating systems (RTOS) ecosystems has been hampered by the fact that foreign ROS entered the Chinese market earlier, enjoy higher acceptance, and are widely compatible. Therefore, a dedicated ecosystem development platform for ROS is needed to help domestic manufacturers quickly promote their brands. Unlike operating systems for mobile phones or personal computers (PCs), embedded ROS often lack the concept of processes at the application software level. They cannot be downloaded directly from an app store and run; instead, they must be compiled along with the system code. At the service level, devices equipped with embedded ROS may require remote firmware upgrades, system security monitoring, battery monitoring, traffic monitoring, and location monitoring. Currently, there is an urgent need to design a comprehensive service platform specifically for embedded ROS to help domestic operating system manufacturers develop their own ecosystems and disrupt the existing market structure.

[0003] Currently, domestic embedded real-time operating system (RTOS) vendors, such as Alibaba and Huawei, integrate over-the-air (OTA) remote upgrade functionality with their respective IoT cloud platforms. However, due to the numerous functions of these cloud platforms, many of which involve long-lived connections, terminal hardware resources are wasted if the terminal doesn't require other functions. Furthermore, the application services offered by these cloud platforms lack specificity and fail to consider the scenario-specific needs of devices running embedded ROS, such as system security monitoring, battery monitoring, traffic monitoring, and location monitoring. Additionally, these platforms lack platforms for third-party application distribution and dedicated application stores for the operating system. This necessitates developers handling the OS adaptation of third-party software development kits (SDKs) when deploying them to products, hindering the development of the embedded ROS ecosystem. Currently, there is a lack of dedicated service platforms for embedded ROS, especially integrated platforms combining services and application stores.

[0004] In summary, existing IoT cloud platform application services lack specificity, fail to support the ecosystem development of operating systems, and do not consider the scenario requirements of devices equipped with embedded real-time operating systems. Furthermore, the device-side software development kits (SDKs) released by cloud platforms often include redundant functions, easily leading to a waste of device-side hardware resources and failing to meet the needs of low-cost hardware terminals. In addition, IoT cloud platforms lack third-party application distribution platforms specifically for operating systems, thus failing to effectively promote the ecosystem development of operating systems. Summary of the Invention

[0005] This invention provides an application service device and a terminal device to solve the problem of wasted hardware resources caused by existing embedded real-time operating systems.

[0006] To solve the above-mentioned technical problems, the present invention adopts the following technical solution:

[0007] This invention provides an application service device, comprising:

[0008] At least one functional module;

[0009] Each of the at least one functional module is communicatively connected to the terminal device.

[0010] Each of the aforementioned functional modules is used to provide a target function to the terminal device, and the functional module receives an indication information sent by the terminal device. The indication information is used to control whether the functional module needs to enable the corresponding target function. When the indication information indicates that the corresponding target function needs to be enabled, the functional module communicates and transmits data corresponding to the target function with the terminal device.

[0011] Optionally, the application service device further includes:

[0012] Device access management module;

[0013] The device access management module is connected to the terminal device and is used to send a device token to the terminal device according to the registration information of the terminal device. The device token is generated by the device access management module based on the product authentication information and device identifier in the registration information.

[0014] Optionally, the functional module includes:

[0015] The device defense module is used to provide defense monitoring functions for terminal devices. When the indication information passes, it receives configuration information sent by the terminal device and enables the defense monitoring function of the terminal device.

[0016] The defense monitoring function includes at least one of the following: application service device security monitoring, battery monitoring, traffic monitoring, location monitoring, and network monitoring.

[0017] Optionally, the functional module includes:

[0018] Equipment upgrade agent module;

[0019] The device upgrade agent module is used to generate a preset upgrade package based on a preset upgrade file; or, it is used to provide upgrade services to the terminal device when the instruction information passes.

[0020] Optionally, the functional module further includes:

[0021] Application enable module;

[0022] The application enabling module is communicatively connected to both the device access management module and the terminal device.

[0023] The application enabling module is used to send access authentication information to the device access management module for authentication, and to determine whether to enable the communication connection between the application enabling module and the terminal device.

[0024] Optionally, the application service device further includes:

[0025] A third-party application publishing module, which is communicatively connected to the terminal device to exchange information;

[0026] The third-party application publishing module is used to upload to the terminal device the application software development kit adapted to the terminal device, the application information adapted to the terminal device, and the hardware information that the terminal device needs to access.

[0027] Optionally, the access authentication information between the application enabling module and the terminal device uses device tokens and product authentication information.

[0028] Optionally, the device defense module is used to configure the defense indicators of the device according to a preset requirements file.

[0029] This invention also provides a terminal device, including:

[0030] Embedded operating module;

[0031] System integrated service component; the system integrated service component is connected to the embedded operation module;

[0032] Processor; the processor is connected to the system integrated service component;

[0033] The processor is used to send instruction information to the functional modules of the application service device; the instruction information is used to control whether the functional modules need to enable the corresponding target function.

[0034] Optionally, the processor is used to send registration information to the application service device; the registration information includes product authentication information and device identifier;

[0035] Alternatively, it can be used to receive a device token generated by the application service device based on the registration information of the terminal device.

[0036] Optionally, the terminal device is used to receive the configuration information of the application service device after the target application is enabled, and update the configuration information to the system integrated service component.

[0037] The beneficial effects of this invention are:

[0038] In the above technical solution, the present invention provides at least one functional module, each of which is communicatively connected to a terminal device. The functional module can control the opening / closing of the functional module according to the instruction information sent by the terminal device. When the terminal device requires it, the corresponding target function can be controlled to be opened, thus solving the problem of wasted hardware resources on the device side caused by the embedded real-time operating system in the prior art. Attached Figure Description

[0039] Figure 1 This is a schematic diagram of the structure of an application service device provided in an embodiment of the present invention;

[0040] Figure 2 This is the second schematic diagram illustrating the structure of the application service device provided in this embodiment of the invention.

[0041] Figure 3 This diagram illustrates the access method of the application service device provided in this embodiment of the invention.

[0042] Figure 4 This diagram illustrates the access methods for non-basic service modules provided in this embodiment of the invention.

[0043] Figure 5 This is a schematic diagram of the structure of the terminal device provided in an embodiment of the present invention. Detailed Implementation

[0044] To make the technical problems, technical solutions, and advantages of this invention clearer, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments. In the following description, specific details such as particular configurations and components are provided merely to aid in a comprehensive understanding of the embodiments of this invention. Therefore, those skilled in the art should understand that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this invention. Furthermore, for clarity and brevity, descriptions of known functions and structures have been omitted.

[0045] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the invention. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0046] In various embodiments of the present invention, it should be understood that the sequence number of each process described below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0047] This invention addresses the problem of wasted hardware resources on the device side caused by existing embedded real-time operating systems by providing an application service device and a terminal device.

[0048] like Figure 1 As shown, an embodiment of the present invention provides an application service device 1, comprising:

[0049] At least one functional module 10;

[0050] Each of the at least one functional module 10 is communicatively connected to the terminal device 2;

[0051] Each of the functional modules 10 is used to provide a target function to the terminal device 2, and the functional module 10 receives the indication information sent by the terminal device 2. The indication information is used to control whether the functional module 10 needs to enable the corresponding target function. When the indication information indicates that the corresponding target function needs to be enabled, the functional module 10 communicates and transmits data corresponding to the target function with the terminal device 2.

[0052] In this embodiment, if the terminal device 2 needs to use the service capabilities provided by the application service device 1, then a functional module 10 providing a certain service from the application service device 1 is accessed on the terminal device 2. The terminal device 2 is configured on demand. Even if some target functions in the functional module 10 are enabled by default on both the terminal device 2 and the application service device 1, they can still be deconfigured if the terminal device 2 does not need a particular functional module 10, thus saving hardware resources. Similarly, when a target function of another functional module 10 provided by the application service device 1 is needed, the target application of the application service device 1 needs to be enabled, and corresponding configurations need to be made on the terminal device 2.

[0053] The embodiments of the present invention can control the activation of corresponding target functions when the terminal device has a need, thereby solving the problem of wasted hardware resources on the device side caused by the existing embedded real-time operating system.

[0054] like Figure 2 As shown in the specific embodiment of the present invention, the application service device 1 further includes:

[0055] Device access management module 20;

[0056] Here, the device access management module 20 is responsible for user information and product information management, product authentication information generation, device registration, device token distribution, device access authentication, and device log management;

[0057] The device access management module 20 is connected to the terminal device 2 and is used to send a device token to the terminal device 2 according to the registration information of the terminal device 2. The device token is generated by the device access management module 20 based on the product authentication information and device identifier in the registration information.

[0058] In this embodiment, the device access management module 20 generally has the following two device registration methods: The first device registration is initiated by the terminal device 2, that is, the user has not registered the device for the terminal device 2 in the device access management module 20, and the terminal device 2 only stores product authentication information (generated by the application service device 1 after the user creates the product). The terminal device 2 registers itself by accessing the device access management module 20 with the registration information (i.e., product authentication information and device identifier). The device access management module 20 sends a device token to the terminal device 2 according to the registration information of the terminal device 2. The terminal device 2 saves the device token on its side. The device token is used to connect to the application service device 1.

[0059] Here, the device access management module 20 supports repeated registration of the same terminal device 2, but always transmits the device token issued by the device access management module 20 to the terminal device 2 when it first registers. Therefore, the terminal device 2 may not store the device token on its side, but instead register once to obtain the device token each time it needs to use it, and then establish a subsequent connection with the application service device 1.

[0060] The second method of device registration is as follows: users manually register terminal devices in batches through the device access management module 20. This involves the terminal devices burning the product authentication information and device token assigned by the application service device 1 during the production phase. These terminal devices do not need to connect to the device access management module 20; the locally stored product authentication information and device token serve as the authentication information for accessing the functional module 10 of the application service device 1. When a terminal device initiates access, the application service device 1 accesses the device access management module 20 to query the access authentication result based on the information reported by the device.

[0061] Optionally, the functional module 10 includes:

[0062] The device defense module 11 is used to provide the defense monitoring function of the terminal device 2. When the indication information passes, it receives the configuration information sent by the terminal device 2 and enables the defense monitoring function of the terminal device 2.

[0063] The defense monitoring function includes at least one of the following: application service device security monitoring, battery monitoring, traffic monitoring, location monitoring, and network monitoring. This embodiment is not limited to these functions.

[0064] In this embodiment, the device defense module 11 is a module with functions such as application service device security monitoring, battery monitoring, traffic monitoring, location monitoring and network monitoring; the device defense module 11 is the basic service capability provided by the application service device 1, and is a basic application that is enabled by default on the application service device 1 side.

[0065] Specifically, the device defense module 11 is used to configure the defense indicators of the device according to a preset requirement file.

[0066] In this embodiment, the specific defense indicators of the device defense module 11 are configured by the user on the application service device 1 as needed. The terminal device 2 collects and reports the indicator information. When the indicators are abnormal, the device defense module 11 notifies the device or sends an SMS notification to the user. Here, the specific method for judging the defense indicators is not limited.

[0067] For example, device traffic monitoring does not require collecting the Integrated Circuit Card Identifier (ICCID) of the device's IoT card every time. After a single collection, the device defense module 11 can periodically query the data and issue warnings based on thresholds. Some indicator information can be collected and reported periodically by the terminal device, or collected and reported to the device defense module 11 by service triggers.

[0068] Here, the connection protocol between the device defense module 11 and the terminal device 2 is a short connection type.

[0069] Optionally, the functional module 10 includes:

[0070] Equipment upgrade agent module 12;

[0071] The device upgrade agent module 12 is used to generate a preset upgrade package according to a preset upgrade file; or, it is used to provide upgrade services to the terminal device 2 when the instruction information passes.

[0072] In this embodiment, the step of generating a preset upgrade package based on a preset upgrade file refers to the device upgrade proxy module 12 being responsible for uploading the user's upgrade file, generating the upgrade package required for remote upgrades of the terminal device, and providing upgrade services when the terminal device initiates access and upgrade. The device upgrade proxy module 12 provides basic service capabilities for the application service device 1, and is a basic application enabled by default on the application service device 1 side. Here, the preset upgrade package is a differential upgrade package generated by the device upgrade proxy module 12 based on the upgrade file uploaded by the user.

[0073] The remote upgrade of terminal device 2 can be triggered by a service. Terminal device 2 accesses the device upgrade agent module 12 using a device token and product authentication information to begin the device upgrade. Similarly, the connection protocol between the device upgrade agent module 12 and terminal device 2 is a short connection type, and the connection is disconnected after the upgrade is completed.

[0074] Optionally, the functional module 10 further includes:

[0075] Application enable module 13;

[0076] The application enabling module 13 is communicatively connected to the device access management module and the terminal device 2, respectively.

[0077] The application enabling module 13 is used to send access authentication information to the device access management module for authentication, and to determine whether to enable the communication connection between the application enabling module 13 and the terminal device 2.

[0078] In this embodiment, the application enabling module 13 is responsible for displaying and enabling non-basic service applications. For example, for location services, users enable the location service in the application enabling module 13 according to product requirements. When the terminal device accesses the application enabling module 13, the application enabling module 13 sends access authentication information to the device access management module for authentication to determine whether to open the communication connection between the application enabling module 13 and the terminal device 2. If the authentication is successful, the application enabling module 13 will begin access permission; otherwise, if the authentication fails, the application enabling module 13 considers that there is no permission and will refuse the access connection. That is, the terminal device can only enjoy the provided services after the application enabling module 13 is enabled.

[0079] Specifically, the access authentication information between the application enabling module 13 and the terminal device 2 uses device tokens and product authentication information.

[0080] Here, if the application enabling module 13 frequently makes incorrect or unauthorized access, the application enabling module 13 may also inform the device defense module 11 of the access authentication information of the terminal device 2.

[0081] Optionally, the application service device 1 further includes:

[0082] A third-party application publishing module 30 is communicatively connected to the terminal device 2 to exchange information.

[0083] The third-party application publishing module 30 is used to upload to the terminal device 2 the application software development kit adapted to the terminal device 2, the application information adapted to the terminal device 2, and the hardware information that the terminal device 2 needs to access.

[0084] In this embodiment, the third-party application publishing module 30 provides a platform for manufacturers to upload application software development kits (SDKs), operating system manufacturers to publish information, and for displaying, searching, and downloading application information. Developers can use the third-party application publishing module 30 to learn about the applications currently supported by the terminal device 2, and quickly search for and download SDKs. The applications in the third-party application publishing module 30 are independent of the applications in the application service device 1; the terminal device 2 can connect only to the applications published by the third-party application publishing module 30 without connecting to the functional module 10.

[0085] Specifically, the third-party application publishing process is as follows: the third party uploads an application SDK that is compatible with the operating system, application-related information, and information on the hardware that needs to be accessed; the operating system provider conducts testing and information review; after the operating system provider passes the test and the application information submitted by the third party is verified to be correct, the operating system provider publishes the application on the third-party application publishing platform.

[0086] It should be noted that the device defense module 11 and device upgrade agent module 12 mentioned above are basic service modules, while the application enablement module 13 is a non-basic service module. The device access authentication information of the basic service module and the non-basic service module is unified and comes from the distribution of the device access management module 20, i.e., the device token.

[0087] It should also be noted that the functions of the device defense module 11, device upgrade agent module 12, application enable module 13, and third-party application publishing module 30 in this invention can be enabled / disabled by setting the terminal device 2, and the device access management module 20, device defense module 11, device upgrade agent module 12, application enable module 13, and third-party application publishing module 30 are independent of each other when establishing a communication link with the terminal device 2.

[0088] In another specific embodiment, such as Figure 3 As shown, Figure 3 This diagram illustrates one of the various application module access methods provided in an embodiment of the present invention.

[0089] Terminal device 2 uses a self-registration method to connect to device access management module 20. Device access management module 20 generates a device token based on the product authentication information and device identifier provided by terminal device 2 and transmits it to terminal device 2. Terminal device 2 stores the device token locally.

[0090] When terminal device 2 requires device defense, upgrade proxy, positioning, and third-party application functions (such as an artificial intelligence platform), it connects to the device defense module 11 at a 1-hour interval based on the device token and product authentication information to collect and report local defense indicator information. At a 24-hour interval, it connects to the device upgrade proxy module 12 based on the device token and product authentication information to query the firmware version; if a newer firmware version exists, it initiates a device upgrade. When terminal device 2 requires positioning, it connects to the application enabling module 13 based on the device token and product authentication information (the user has already enabled the positioning application in the application enabling module 13), maintaining a long connection and transmitting the device's Global Positioning System (GPS) information and base station information. When terminal device 2 requires artificial intelligence services, it connects to the third-party application publishing module 30 according to the authentication methods set by each platform for data interaction.

[0091] In another specific embodiment, the non-basic service application enabling process provided by the embodiments of the present invention.

[0092] Specifically, the user logs into the device access management module 20 of the application service device 1 using their user identity information. The user selects the product for which they want to enable the application, selects the configuration item in the product information, and begins the application enabling operation. The application enabling configuration item in the product configuration can jump to the application enabling module 13, where the user browses the currently supported non-basic applications and their features, and selects the application they want to enable as needed. The configuration after application enabling is saved in the device access management module 20. The terminal device 2 modifies its configuration based on the application configuration already enabled by the application service device 1. For example, if the application service device 1 has enabled location services, the terminal device 2 must also enable location functions.

[0093] In another specific embodiment, such as Figure 4 As shown, Figure 4 This invention provides an access process for a non-basic service application module, such as a location service module (i.e., the application enablement module 13). The device access process is as follows:

[0094] Terminal device 2 connects to the device access management module 20 of application service device 1 based on product authentication information and device identifier (device unique identification code); after application service device 1 performs access authentication...

[0095] Based on the information provided by terminal device 2, a new target unit of terminal device 2 is registered under the product of device access management module 20. The platform transmits device token and other information to the target unit. Terminal device 2 disconnects from device access management module 20, and the target unit saves the information locally.

[0096] The target unit connects to the location service module (i.e., the application enablement module 13) based on the product information and device token.

[0097] The location service module (i.e., the application enablement module 13) accesses the device access management module 20 to perform device access authentication and service permission query (whether the location application has been enabled).

[0098] The device access management module 20 transmits the identity authentication result and application enable result to the location service module.

[0099] The location service module (i.e., the application enabling module 13) will refuse access to the terminal device 2 if the product does not enable location services or if identity authentication fails. Otherwise, access will be successful and location services will begin to be provided.

[0100] like Figure 5 As shown, this embodiment of the invention also provides a terminal device 2, including:

[0101] Embedded operating module 21;

[0102] System integrated service component 22; the system integrated service component 22 is connected to the embedded operation module 21;

[0103] Here, the system integrated service component 22 can be flexibly configured on the terminal device 2 side. If the service capabilities provided by the application service device 1 are not needed, the terminal device 2 side can turn off this component. If the service capabilities provided by the application service device 1 are needed, the terminal device 2 turns on this component and configures the system integrated service component 22 on the terminal device 2 side according to the applications enabled by the user on the application service device 1 side.

[0104] Processor 23; the processor 23 is connected to the system integrated service component 22;

[0105] The processor is used to send instruction information to the functional module 10 of the application service device 1; the instruction information is used to control whether the functional module 10 needs to enable the corresponding target function.

[0106] In this embodiment, the system integrated service component 22 is a software package running on the embedded operating module 21 for terminal devices to access the application service device 1 and enjoy corresponding services. The system integrated service component 22 can be flexibly configured on the terminal device side. If the service capabilities of the application service device 1 are not needed, the terminal device side can disable this component (system integrated service component 22) to minimize hardware resources. For the system integrated service component 22, developers only need to focus on the product's own business logic. If the service capabilities provided by the application service device 1 are needed, the terminal device side must enable the system integrated service component 22 and configure it according to the applications enabled by the user on the platform side. This on-demand configuration method can save terminal hardware resources.

[0107] Specifically, the processor 23 is used to send registration information to the application service device 1; the registration information includes product authentication information and device identifier;

[0108] Alternatively, it can be used to receive a device token generated by the application service device 1 based on the registration information of the terminal device 2.

[0109] In this embodiment, the processor 23 is used to receive a device token generated by the device access management module 20 of the application service device 1 based on the registration information of the terminal device 2. The processor 23 can store the device token in the terminal device 2, and when it needs to connect with the functional module 10 of the application service device 1 and the terminal device 2, it uses the product authentication information and the device token as authentication standards.

[0110] Specifically, the difference between basic service modules and non-basic service modules in terms of access to terminal device 2 is as follows: When terminal device 2 accesses a non-basic service module, it must also verify its application service permissions through the device access management module of the application service device 1. If the user has not enabled the application, terminal device 2 will be denied access. Basic service modules use short connections in their access protocol, disconnecting immediately after data interaction is complete. Non-basic service modules can choose between long or short connection protocols depending on application needs. The application SDK downloaded by the third-party application publishing module is a third-party application module when it involves application modules. The access method of third-party application modules is entirely defined by the third-party service provider and is independent of application service device 1 and system integrated service component 22.

[0111] Specifically, the terminal device 2 is used to receive the configuration information of the application service device 1 after the target application is enabled, and update the configuration information to the system integrated service component 22.

[0112] Here, after receiving the configuration information sent by the application enable module of the application service device 1 after authenticating the target application, the terminal device 2 controls the system integrated service component 22 to modify the configuration of the system integrated service component on the terminal side according to the configuration of the enabled application, so as to maintain the consistency between the terminal device 2 and the application service device 1 and avoid resource waste caused by enabling one side.

[0113] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0114] The above describes the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications are also within the scope of protection of the present invention.

Claims

1. An application service device, characterized by include: At least one functional module; Each of the at least one functional module is communicatively connected to the terminal device. Each of the aforementioned functional modules is used to provide a target function for the terminal device, and the functional module receives an indication information sent by the terminal device, the indication information being used to control whether the functional module needs to enable the corresponding target function; when the indication information indicates that the corresponding target function needs to be enabled, the functional module communicates and transmits data corresponding to the target function with the terminal device. The application service device further includes: a device access management module; the device access management module is connected to the terminal device and is used to send a device token to the terminal device according to the registration information of the terminal device, the device token being generated by the device access management module based on the product authentication information and device identifier in the registration information; The functional modules include: The device defense module is used to provide defense monitoring functions for terminal devices. When the indication information passes, it receives configuration information sent by the terminal device and enables the defense monitoring function of the terminal device. The defense monitoring function includes at least one of the following: application service device security monitoring, battery monitoring, traffic monitoring, location monitoring, and network monitoring. The device upgrade agent module is used to generate a preset upgrade package based on a preset upgrade file; or, it is used to provide upgrade services to the terminal device when the instruction information is passed. The application enable module is communicatively connected to both the device access management module and the terminal device. The application enable module is used to send access authentication information to the device access management module for authentication and to determine whether to enable the communication connection between the application enable module and the terminal device.

2. The application service device according to claim 1, characterized by The application service equipment also includes: A third-party application publishing module, which is communicatively connected to the terminal device to exchange information; The third-party application publishing module is used to upload to the terminal device the application software development kit adapted to the terminal device, the application information adapted to the terminal device, and the hardware information that the terminal device needs to access.

3. The application service device according to claim 2, wherein The access authentication information between the application enabling module and the terminal device uses device tokens and product authentication information.

4. The application service device according to claim 1, characterized in that, The device defense module is used to configure the defense indicators of the device defense module according to a preset requirement file.

5. A terminal device, characterized by, include: Embedded operating module; System integrated service components; The system integrated service component is connected to the embedded operation module; processor; The processor is connected to the system integrated service component; The processor is used to send instruction information to the functional modules of the application service device; the instruction information is used to control whether the functional modules need to enable the corresponding target function. The processor is used to send registration information to the application service device; the registration information includes product authentication information and device identifier; or, it is used to receive a device token generated by the application service device based on the registration information of the terminal device. The terminal device is configured to receive configuration information of the application service device after the target application is enabled, and update the configuration information to the system integrated service component.

Images