CN113596958A - Terminal equipment data interaction method, system, equipment and storage medium - Google Patents

Terminal equipment data interaction method, system, equipment and storage medium Download PDF

Info

Publication number
CN113596958A
CN113596958A CN202110860463.5A CN202110860463A CN113596958A CN 113596958 A CN113596958 A CN 113596958A CN 202110860463 A CN202110860463 A CN 202110860463A CN 113596958 A CN113596958 A CN 113596958A
Authority
CN
China
Prior art keywords
equipment
application
data interaction
terminal device
terminal
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202110860463.5A
Other languages
Chinese (zh)
Other versions
CN113596958B (en
Inventor
王犇
廖德甫
梁露文
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Mobile Communications Group Co Ltd
China Mobile Hangzhou Information Technology Co Ltd
Original Assignee
China Mobile Communications Group Co Ltd
China Mobile Hangzhou Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Mobile Communications Group Co Ltd, China Mobile Hangzhou Information Technology Co Ltd filed Critical China Mobile Communications Group Co Ltd
Priority to CN202110860463.5A priority Critical patent/CN113596958B/en
Publication of CN113596958A publication Critical patent/CN113596958A/en
Application granted granted Critical
Publication of CN113596958B publication Critical patent/CN113596958B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/16Discovering, processing access restriction or access information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup

Abstract

The invention belongs to the technical field of computers, and discloses a data interaction method, a data interaction system, data interaction equipment and a storage medium for terminal equipment. The method comprises the steps that when the edge node equipment detects that the terminal equipment is accessed, operation environment information required by the operation of the terminal equipment is obtained; acquiring a drive installation package corresponding to the operating environment information from a management center; installing a device driver and an instruction set corresponding to the terminal device based on the driver installation package; and performing data interaction with the terminal equipment through the equipment driver and the instruction set. When the access of the terminal equipment is detected, the drive installation package is quickly obtained from the management center, and the equipment drive and the instruction set which are won by the terminal equipment are installed according to the drive installation package, so that the edge node equipment can perform data interaction with the terminal equipment according to the installed equipment drive and the instruction set, and the quick connection with the accessed terminal equipment is ensured.

Description

Terminal equipment data interaction method, system, equipment and storage medium
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a method, a system, a device, and a storage medium for data interaction in a terminal device.
Background
With the advent of the 5G internet of everything era, the data volume generated by various services such as internet of vehicles, industrial control, 4K/8K high-definition video, virtual reality/augmented reality (VR/AR) and the like is increased explosively, requirements on real-time performance, network dependency, safety and the like are brought to infrastructure, and in order to solve the problems, edge computing related technologies are brought forward.
The edge computing is implemented by placing resources such as computing, storage, bandwidth and application on the edge side of the network, computing through edge nodes close to a data source, and fusing the core capabilities of the network, the computing, the storage and the application on the edge side of the network close to an object or the data source, so as to provide open edge intelligent service nearby. Compared with cloud computing, edge computing is deployed nearby and belongs to an extension of the cloud computing concept. Under the service scene facing mass connection and ultra-large bandwidth, in order to meet the requirements of wider connection, lower time delay and better control, cloud computing is evolved from centralization to overall distributed node combination, and edge computing is a new antenna which is expanded towards edge side in a distributed mode. Cloud-edge cooperation is a very important characteristic in edge computing, and the problems of resource shortage and incapability of unified management of mass equipment in the edge computing landing process can be solved through the cloud-edge cooperation.
However, under the cloud edge collaboration scene, the management and application between the edge application and the terminal device lack linkage. In a complex scenario, a dynamically deployed edge application and a terminal device accessing an edge node cannot quickly establish a corresponding control and data channel, which is not favorable for quick online and use of the edge application.
The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.
Disclosure of Invention
The invention mainly aims to provide a data interaction method, a data interaction system, a data interaction device and a data interaction storage medium for a terminal device, and aims to solve the technical problem that connection cannot be quickly established with the terminal device in a cloud edge collaboration scene in the prior art.
In order to achieve the above object, the present invention provides a data interaction method for a terminal device, the method comprising the following steps:
the method comprises the steps that when an edge node detects that a terminal device is accessed, operation environment information required by operation of the terminal device is obtained;
acquiring a drive installation package corresponding to the operating environment information from a management center;
installing a device driver and an instruction set corresponding to the terminal device based on the driver installation package;
and performing data interaction with the terminal equipment through the equipment driver and the instruction set.
Optionally, the step of obtaining, by the edge node, the operating environment information required by the operation of the terminal device when detecting that the terminal device is accessed includes:
the method comprises the steps that when an edge node detects that a terminal device is accessed, the device model information of the terminal device is obtained;
acquiring an edge application corresponding to the equipment model information;
and determining the running environment information required by the running of the terminal equipment according to the edge application and the equipment model information.
Optionally, the step of determining, according to the edge application and the device model information, operating environment information required by the operation of the terminal device includes:
acquiring application identification information of the edge application;
searching a corresponding driving model and an instruction set identifier in a management center according to the application identifier information and the equipment model information;
and constructing operating environment information according to the driving model and the instruction set identification.
Optionally, the step of obtaining the driver installation package corresponding to the operating environment information from the management center includes:
generating a drive installation request according to the operating environment information;
and sending the drive installation request to a management center so that the management center feeds back a drive installation package corresponding to the operating environment information according to the drive installation request.
Optionally, when the edge node detects that the terminal device is accessed, before the step of obtaining the operating environment information required by the operation of the terminal device, the method further includes:
the method comprises the steps that edge node equipment receives application binding configuration sent by a management center, and a plurality of edge applications to be operated and equipment requirement information corresponding to the edge applications to be operated are determined according to the application binding configuration;
creating a corresponding operation container for each edge application to be operated;
creating simulation equipment for each edge application to be operated according to the equipment requirement information, and loading each edge application to be operated into a corresponding operation container for operation;
and when the loading is finished, starting the equipment access monitor, and detecting whether the terminal equipment is accessed in real time.
Optionally, after the step of performing data interaction with the terminal device through the device driver and the instruction set, the method further includes:
receiving a device unloading request issued by the management center, and determining an application to be unloaded according to the device unloading request;
and unloading the application to be unloaded.
Optionally, after the step of unloading the application to be unloaded, the method further includes:
when the uninstallation is finished, detecting whether terminal equipment without application binding exists;
when the terminal equipment exists, the terminal equipment without application binding is taken as target terminal equipment;
and unloading the device driver and the instruction set corresponding to the target terminal device.
In addition, in order to achieve the above object, the present invention further provides a terminal device data interaction system, where the terminal device data interaction system includes:
the terminal equipment comprises a connection management module, a connection management module and a connection management module, wherein the connection management module is used for acquiring running environment information required by the running of the terminal equipment when the access of the terminal equipment is detected;
the data acquisition module is used for acquiring the drive installation package corresponding to the operating environment information from a management center;
the driver installation module is used for installing the device driver and the instruction set corresponding to the terminal device based on the driver installation package;
and the equipment control module is used for carrying out data interaction with the terminal equipment through the equipment driver and the instruction set.
In addition, to achieve the above object, the present invention further provides an edge node device, where the edge node device includes: the data interaction method comprises a processor, a memory and a terminal device data interaction program which is stored on the memory and can run on the processor, wherein the terminal device data interaction program realizes the steps of the terminal device data interaction method when being executed by the processor.
In addition, in order to achieve the above object, the present invention further provides a computer-readable storage medium, where a terminal device data interaction program is stored, and when the terminal device data interaction program is executed, the steps of the terminal device data interaction method described above are implemented.
The method comprises the steps that when the edge node detects that the terminal equipment is accessed, operation environment information required by the operation of the terminal equipment is obtained; acquiring a drive installation package corresponding to the operating environment information from a management center; installing a device driver and an instruction set corresponding to the terminal device based on the driver installation package; and performing data interaction with the terminal equipment through the equipment driver and the instruction set. When the access of the terminal equipment is detected, the drive installation package is quickly obtained from the management center, and the equipment drive and the instruction set which are won by the terminal equipment are installed according to the drive installation package, so that the edge node can perform data interaction with the terminal equipment according to the installed equipment drive and the instruction set, and the connection with the accessed terminal equipment can be quickly established.
Drawings
Fig. 1 is a schematic structural diagram of an electronic device in a hardware operating environment according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of a first embodiment of a data interaction method for a terminal device according to the present invention;
fig. 3 is a flowchart illustrating a data interaction method for a terminal device according to a second embodiment of the present invention;
fig. 4 is a schematic view of an access flow of a terminal device according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a data interaction method for a terminal device according to a third embodiment of the present invention;
FIG. 6 is a flow diagram illustrating a terminal application offloading process according to one embodiment;
fig. 7 is a block diagram of a first embodiment of a data interaction system of a terminal device according to the present invention.
The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.
Detailed Description
It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of an edge node device in a hardware operating environment according to an embodiment of the present invention.
As shown in fig. 1, the electronic device may include: a processor 1001, such as a Central Processing Unit (CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a Wireless interface (e.g., a Wireless-Fidelity (WI-FI) interface). The Memory 1005 may be a Random Access Memory (RAM) or a Non-Volatile Memory (NVM), such as a disk Memory. The memory 1005 may alternatively be a storage device separate from the processor 1001.
Those skilled in the art will appreciate that the configuration shown in fig. 1 does not constitute a limitation of the electronic device and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.
As shown in fig. 1, a memory 1005, which is a storage medium, may include therein an operating system, a network communication module, a user interface module, and a terminal device data interaction program.
In the electronic apparatus shown in fig. 1, the network interface 1004 is mainly used for data communication with a network server; the user interface 1003 is mainly used for data interaction with a user; the processor 1001 and the memory 1005 in the electronic device of the present invention may be disposed in an edge node device, and the electronic device invokes a terminal device data interaction program stored in the memory 1005 through the processor 1001 and executes the terminal device data interaction method provided by the embodiment of the present invention.
An embodiment of the present invention provides a terminal device data interaction method, and referring to fig. 2, fig. 2 is a schematic flow diagram of a first embodiment of a terminal device data interaction method according to the present invention.
In this embodiment, the terminal device data interaction method includes the following steps:
step S10: and when detecting the access of the terminal equipment, the edge node acquires the running environment information required by the running of the terminal equipment.
It should be noted that the execution main body of this embodiment may be an edge node device, and the edge node device may be a device installed on the user side as an edge node, for example: the device such as the home gateway or the smart terminal box may also be other devices that can implement the same or similar functions, which is not limited in this embodiment. In this embodiment and the following embodiments, the data interaction method of the terminal device of the present invention is described by taking an edge node device as an example.
It should be noted that the terminal device may be a device that the user currently needs to use, for example: VR body sensing equipment or other intelligent terminal equipment. The operating environment information may include information such as a drive model and an instruction set identifier of the terminal device. When the edge node device detects that the terminal device is accessed, the operation environment information required by the operation of the terminal device can be obtained by the edge node device monitoring whether the existing interface and the extended interface which are provided by the edge node device in real time are connected with the terminal device or not, the device model of the terminal device is obtained when the terminal device is connected, and the operation environment information corresponding to the device model is searched in an environment information table, so that the operation environment information required by the operation of the accessed terminal device is determined. The environment information table may include a mapping relationship between the device model and the operating environment information, and the mapping information in the environment information table may be preset by a user or preset by an administrator of the edge node device, which is not limited in this embodiment.
Further, in an actual usage scenario, there may be a difference between device drivers and control instructions required by different edge application control terminal devices when running, and in order to save resources of the edge node device, step S10 in this embodiment may include:
the method comprises the steps that when edge node equipment detects that terminal equipment is accessed, equipment model information of the terminal equipment is obtained; acquiring an edge application corresponding to the equipment model information; and determining the running environment information required by the running of the terminal equipment according to the edge application and the equipment model information.
It should be noted that the edge application may be an application installed in the edge node device. One edge application may correspond to a plurality of different terminal devices, and one terminal device may correspond to a plurality of different edge applications. The device model information may include information such as a device model identification, a device model name, and a device manufacturer. When the edge node device detects the access of the terminal device, the device model information of the terminal device may be obtained by reading the device model information of the terminal device through a device access interface when the edge node device detects the access of the terminal device. The obtaining of the edge application corresponding to the device model information may be searching for the edge application corresponding to the device model information in a preset model application mapping table, where the preset model application mapping table may include a corresponding relationship between the device model and the edge application, and a mapping relationship in the preset model application mapping table may be set when the edge application is installed.
In actual use, determining the operating environment information required by the operation of the terminal device according to the edge application and the device model information may be to search the operating environment information required by the operation of the terminal device in a preset operating information table according to the edge application and the device model information, where the preset operating information table may store a corresponding relationship between the operating environment information and the edge application and device model information, and may be preset by a user or a manager. The preset operation information table may be stored in a storage space of the edge solution point, or may be stored in the management center.
Further, since the types and the number of manufacturers of the terminal device are extremely large, if the preset information table is stored in the edge node device, the performance consumption of the edge node device is extremely large, which is not beneficial to practical use, and therefore, the preset information table can be stored in the management center, and when the preset information table is stored in the management center, the step of determining the operation environment information required by the operation of the terminal device according to the edge application and the device type information in this embodiment includes:
acquiring application identification information of the edge application; searching a corresponding driving model and an instruction set identifier in a management center according to the application identifier information and the equipment model information; and constructing operating environment information according to the driving model and the instruction set identification.
It should be noted that the application identification information may include information such as an application identification and an application version number. The step of searching for the winning drive model and the instruction set identifier in the management center according to the application identifier information and the device model information may be to search for the corresponding drive model and the instruction set identifier in a preset information table stored in the management center according to the application identifier information and the device model information. The constructing of the operating environment information according to the drive model and the instruction set identifier may be converting the drive model and the instruction set identifier into data in a preset format, so as to obtain the operating environment information, and the preset format may be preset by a manager of the edge node device.
Step S20: and acquiring the drive installation package corresponding to the operating environment information from a management center.
It should be noted that the management center may be a cloud center in cloud edge collaboration. In a cloud edge coordination scene, the performance and resources of edge node equipment are limited, and the edge node equipment cannot store all the driver installation packages, so that after the operation environment information required by the operation of the terminal equipment is obtained, the driver installation packages corresponding to the operation environment information can be obtained from a management center.
Further, in order to obtain the driver installation package corresponding to the operating environment information from the management center quickly, step S20 in this embodiment may include:
generating a drive installation request according to the operating environment information; and sending the drive installation request to a management center so that the management center feeds back a drive installation package corresponding to the operating environment information according to the drive installation request.
The driver installation request may be generated based on the operating environment information, or may be generated using the operating environment information as a request parameter.
It can be understood that, when the management center receives the driver installation request, the management center may parse the driver installation request to obtain the operating environment information, then search for a driver installation package corresponding to the operating environment information in the installation package storage center according to the operating environment information, and send the driver installation package to the edge node device.
Step S30: and installing the equipment driver and the instruction set corresponding to the terminal equipment based on the driver installation package.
It can be understood that the device driver and the instruction set required by the terminal device during operation can be obtained by installing the obtained driver installation package, where the instruction set may include various control instructions required for controlling the terminal device to operate.
Step S40: and performing data interaction with the terminal equipment through the equipment driver and the instruction set.
It can be understood that after the device driver and the instruction set of the terminal device are obtained, the edge node device can perform device control and data acquisition on the terminal device according to the device driver and the instruction set, so as to implement data interaction with the terminal device.
In this embodiment, when detecting that a terminal device is accessed, an edge node device acquires operating environment information required by the operation of the terminal device; acquiring a drive installation package corresponding to the operating environment information from a management center; installing a device driver and an instruction set corresponding to the terminal device based on the driver installation package; and performing data interaction with the terminal equipment through the equipment driver and the instruction set. When the access of the terminal equipment is detected, the drive installation package is quickly obtained from the management center, and the equipment drive and the instruction set which are won by the terminal equipment are installed according to the drive installation package, so that the edge node equipment can perform data interaction with the terminal equipment according to the installed equipment drive and the instruction set, and the quick connection with the accessed terminal equipment is ensured.
Referring to fig. 3, fig. 3 is a flowchart illustrating a data interaction method for a terminal device according to a second embodiment of the present invention.
Based on the first embodiment, before the step S10, the data interaction method for terminal equipment in this embodiment further includes:
step S01: the edge node equipment receives application binding configuration sent by a management center, and determines a plurality of edge applications to be operated and equipment requirement information corresponding to each edge application to be operated according to the application binding configuration.
It should be noted that, in order to ensure the security of the edge node device, the edge node device may only communicate with the management center, so that a user may send an application installation request to the management center when needing to install an application, and the management center may determine, according to the application installation request sent by the user, the edge application and the corresponding relationship between the edge application and the terminal device, generate an application binding configuration, and send the application binding configuration to the edge node device.
In actual use, when receiving the application binding configuration sent by the management center, the edge application can read data of the application binding configuration, and determine the edge application to be run and the device requirement information corresponding to each edge application to be run according to the read data. The edge application to be run may be an application that a user wishes to install, and the device requirement information may include information such as a device model identifier.
Step S02: and creating a corresponding running container for each edge application to be run.
It should be noted that, in order to ensure that edge applications in the edge node device do not affect each other, a container may be used in the edge node device to run the edge applications, and the container is used to isolate the edge applications, so as to avoid the edge applications from affecting each other. Accordingly, a corresponding run container may be created for each to-be-run edge application when determining the to-be-run edge application.
Step S03: and creating simulation equipment for each edge application to be operated according to the equipment requirement information, and loading each edge application to be operated into a corresponding operation container for operation.
It should be noted that, if part of the edge applications do not interact with the device, the edge applications cannot normally run, and in order to ensure that such edge applications can normally run, simulation devices may be created for each edge application to be run according to the device requirement information, and then the edge applications to be run are loaded into the corresponding running containers, so that each edge application to be run can normally run.
Step S04: and when the loading is finished, starting the equipment access monitor, and detecting whether the terminal equipment is accessed in real time.
It can be understood that after each to-be-run edge application is loaded, the edge node device may start the device access monitor to detect whether a terminal device is accessed in real time.
For convenience of understanding, reference is made to fig. 4 for description, but the present solution is not limited thereto, and fig. 4 is a schematic diagram of an access flow of a terminal device in this embodiment. The process can be divided into 7 steps according to the label: 1. a user submits an application installation request to a management center; 2. the management center issues application binding configuration to the edge node equipment; 3. the edge node device constructs an operation container according to the application binding configuration, loads the edge application into the container for operation, and informs the device management system to start the device access monitor; 4. accessing terminal equipment; 5. the edge node equipment sends a drive installation request to a management center; 6. the management center feeds back a drive installation package; 7. and the edge node equipment installs the driver installation package so that the edge application in the running container can perform data interaction with the terminal equipment.
The device management system may be installed in an edge node device, and may include: the functions of equipment connection management, equipment service management, equipment controller management, external API gateway and the like.
And (3) equipment connection management: the method is used for connection management of terminal equipment, is based on an equipment drive service core framework, supports expansion to realize various different connection protocols, adopts a plug-and-play mode, and acquires a drive and an instruction set from a central cloud to perform equipment connection intercommunication and control management after detecting a newly-added equipment connection or edge side application connection request. Meanwhile, the authority management of the connected equipment is required to be supported, the on-demand use of the equipment by the edge application is supported, the authority control of the equipment after the virtualization of the edge node equipment is controlled, and the use minimization of the system is ensured. And realizing state management on the online equipment, unloading the drive and the instruction set of the equipment after the equipment is connected and the dependent edge application is offline, and releasing the disk space of the effective infrastructure of the edge node equipment.
Equipment service management: the method is used for service management between the edge application and the terminal equipment, provides the function of edge application equipment simulation based on an event-driven mode, simulates required equipment for online application and automatically binds with the connected equipment, realizes operation decoupling between the edge application and real equipment, and ensures that the equipment is plugged and used without influencing the online and offline of the edge application. In addition, edge application data and control service are provided, and decoupling of the edge application on terminal equipment operation and data acquisition is realized through metaplasia on terminal equipment protocol drive conversion and data format conversion.
Equipment controller management: and providing the device control function with the same life cycle as the containerized deployment edge application, and providing the device control function as the SDK for the edge application to call. The system mainly comprises a virtual device controller and a universal device controller, wherein the virtual device controller is used for controlling complex commands of a device terminal, and comprises position information interaction, capability combination interaction and the like; the universal equipment controller is used for controlling universal commands such as equipment starting, closing, resetting and the like. And finally, the edge application calls the related services in the related equipment service management module through the equipment controller SDK to realize the management of the equipment.
External API gateway: the unified message processing inlet provided by the gateway is provided for each service room in the system and the interaction inlet between the outside of the system and the cloud.
In this embodiment, the edge node device only communicates with the management center, so that the possibility of being attacked by the edge node device is reduced, the security of the edge node device is improved, and the edge node device also creates an operation container for each edge application to be operated when receiving the application binding configuration issued by the management center, tries each edge application to operate in a container, avoids mutual interference of each edge application, improves the stability of the edge node device, and creates a simulation device for the edge application before loading the edge application into the corresponding operation container to operate, thereby avoiding the situation that the edge application cannot operate normally because no corresponding entity device exists.
Referring to fig. 5, fig. 5 is a flowchart illustrating a data interaction method for a terminal device according to a third embodiment of the present invention.
Based on the first embodiment, after step S40, the data interaction method for the terminal device in this embodiment further includes:
step S50: and receiving a device unloading request issued by the management center, and determining the application to be unloaded according to the device unloading request.
It should be noted that, in order to ensure the security of the edge node device, the edge node device may only communicate with the management center, so that a user may send an application uninstalling request to the management center when needing to uninstall an edge application, the management center may issue the application uninstalling request to the edge node device when receiving the application uninstalling request, and the edge node device may read parameters included in the application uninstalling request when receiving the application uninstalling request, obtain application identification information, and then search for an application to be uninstalled according to the application identification information.
Step S60: and unloading the application to be unloaded.
It should be noted that the applications in the edge node device are all operated in a containerization manner, and therefore, unloading the application to be unloaded may be to destroy the container in which the application to be unloaded is located.
Further, since the resources of the edge node device are limited, in order to reduce unnecessary performance consumption as much as possible, after step S60, the method may further include:
when the uninstallation is finished, detecting whether terminal equipment without application binding exists; when the terminal equipment exists, the terminal equipment without application binding is taken as target terminal equipment; and unloading the device driver and the instruction set corresponding to the target terminal device.
It should be noted that the determining whether the terminal device has application binding may be detecting whether a terminal device currently accessing the edge node device has a corresponding relationship with an edge application that is not currently unloaded, and if one terminal device does not have a corresponding relationship with an edge application that is not currently unloaded, determining that the terminal device is a terminal device that has no application binding.
It can be understood that, if a terminal device is not bound by an application, it may indicate that the terminal device is in an unused state, and the device driver and the instruction set thereof are not used at this time, so that the terminal device may be used as a target terminal device, and the device driver and the instruction set corresponding to the terminal device are unloaded, thereby saving the space of the edge node device and reducing unnecessary performance consumption.
For convenience of understanding, refer to fig. 6 for explanation, but not limiting the present solution, fig. 6 is a schematic diagram of an uninstalling process of the terminal application in this embodiment, and the uninstalling process may be divided into 5 steps according to reference numbers: 1. a user submits an application uninstalling request to a management center; 2. the management center issues an application unloading request to the edge node equipment; 3. the edge node equipment finds the corresponding application to be unloaded, destroys the application container to be unloaded and informs the equipment management system when destroying; 4. the equipment management system detects whether the terminal equipment without application binding exists or not, and unloads the equipment drive and the instruction set of the terminal equipment without application binding; 5. notifying the management center edge application that the offload is complete.
In this embodiment, the edge node device only communicates with the management center, so that the possibility of the edge node device being attacked is reduced, the security of the edge node device is improved, and the edge node device destroys the running container corresponding to the application to be uninstalled when receiving the application uninstalling request, thereby saving resources, further scanning the terminal device without application binding, taking the terminal device without application binding as the target terminal device, and uninstalling the device driver and the instruction set corresponding to the target terminal device, and further reducing unnecessary performance consumption of the edge node device.
In addition, an embodiment of the present invention further provides a storage medium, where a terminal device data interaction program is stored on the storage medium, and the terminal device data interaction program, when executed by a processor, implements the steps of the terminal device data interaction method described above.
Referring to fig. 7, fig. 7 is a block diagram of a first embodiment of a data interaction system of a terminal device according to the present invention.
As shown in fig. 7, a terminal device data interaction system provided in the embodiment of the present invention includes:
the connection management module 10 is configured to, when detecting that a terminal device is accessed, obtain operation environment information required by operation of the terminal device;
the data acquisition module 20 is configured to acquire a driver installation package corresponding to the operating environment information from a management center;
the driver installation module 30 is configured to install the device driver and the instruction set corresponding to the terminal device based on the driver installation package;
and the device control module 40 is configured to perform data interaction with the terminal device through the device driver and the instruction set.
In this embodiment, when detecting that a terminal device is accessed, an edge node device acquires operating environment information required by the operation of the terminal device; acquiring a drive installation package corresponding to the operating environment information from a management center; installing a device driver and an instruction set corresponding to the terminal device based on the driver installation package; and performing data interaction with the terminal equipment through the equipment driver and the instruction set. When the access of the terminal equipment is detected, the drive installation package is quickly obtained from the management center, and the equipment drive and the instruction set which are won by the terminal equipment are installed according to the drive installation package, so that the edge node equipment can perform data interaction with the terminal equipment according to the installed equipment drive and the instruction set, and the quick connection with the accessed terminal equipment is ensured.
Further, the connection management module 10 is further configured to obtain device model information of the terminal device when detecting that the terminal device is accessed; acquiring an edge application corresponding to the equipment model information; and determining the running environment information required by the running of the terminal equipment according to the edge application and the equipment model information.
Further, the connection management module 10 is further configured to obtain application identification information of the edge application; searching a corresponding driving model and an instruction set identifier in a management center according to the application identifier information and the equipment model information; and constructing operating environment information according to the driving model and the instruction set identification.
Further, the data obtaining module 20 is further configured to generate a driver installation request according to the operating environment information; and sending the drive installation request to a management center so that the management center feeds back a drive installation package corresponding to the operating environment information according to the drive installation request.
Further, the connection management module 10 is further configured to receive an application binding configuration sent by a management center, and determine a plurality of to-be-operated edge applications and device requirement information corresponding to each to-be-operated edge application according to the application binding configuration; creating a corresponding operation container for each edge application to be operated; creating simulation equipment for each edge application to be operated according to the equipment requirement information, and loading each edge application to be operated into a corresponding operation container for operation; and when the loading is finished, starting the equipment access monitor, and detecting whether the terminal equipment is accessed in real time.
Further, the device control module 40 is further configured to receive a device uninstalling request issued by the management center, and determine an application to be uninstalled according to the device uninstalling request; and unloading the application to be unloaded.
Further, the device control module 40 is further configured to detect whether there is a terminal device without application binding when the uninstallation is completed; when the terminal equipment exists, the terminal equipment without application binding is taken as target terminal equipment; and unloading the device driver and the instruction set corresponding to the target terminal device.
It should be understood that the above is only an example, and the technical solution of the present invention is not limited in any way, and in a specific application, a person skilled in the art may set the technical solution as needed, and the present invention is not limited thereto.
It should be noted that the above-described work flows are only exemplary, and do not limit the scope of the present invention, and in practical applications, a person skilled in the art may select some or all of them to achieve the purpose of the solution of the embodiment according to actual needs, and the present invention is not limited herein.
In addition, technical details that are not described in detail in this embodiment may refer to a terminal device data interaction method provided in any embodiment of the present invention, and are not described herein again.
Further, it is to be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention or portions thereof that contribute to the prior art may be embodied in the form of a software product, where the computer software product is stored in a storage medium (e.g. Read Only Memory (ROM)/RAM, magnetic disk, optical disk), and includes several instructions for enabling a terminal device (e.g. a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims (10)

1. A data interaction method for terminal equipment is characterized by comprising the following steps:
the method comprises the steps that when edge node equipment detects that terminal equipment is accessed, operation environment information required by operation of the terminal equipment is obtained;
acquiring a drive installation package corresponding to the operating environment information from a management center;
installing a device driver and an instruction set corresponding to the terminal device based on the driver installation package;
and performing data interaction with the terminal equipment through the equipment driver and the instruction set.
2. The method for data interaction of terminal equipment according to claim 1, wherein the step of acquiring the operating environment information required by the terminal equipment to operate when the edge node equipment detects the access of the terminal equipment comprises:
the method comprises the steps that when edge node equipment detects that terminal equipment is accessed, equipment model information of the terminal equipment is obtained;
acquiring an edge application corresponding to the equipment model information;
and determining the running environment information required by the running of the terminal equipment according to the edge application and the equipment model information.
3. The method for terminal device data interaction according to claim 2, wherein the step of determining the operating environment information required by the terminal device to operate according to the edge application and the device model information includes:
acquiring application identification information of the edge application;
searching a corresponding driving model and an instruction set identifier in a management center according to the application identifier information and the equipment model information;
and constructing operating environment information according to the driving model and the instruction set identification.
4. The method for data interaction of terminal equipment according to claim 1, wherein the step of obtaining the driver installation package corresponding to the operating environment information from the management center includes:
generating a drive installation request according to the operating environment information;
and sending the drive installation request to a management center so that the management center feeds back a drive installation package corresponding to the operating environment information according to the drive installation request.
5. The terminal device data interaction method according to any one of claims 1 to 4, wherein before the step of acquiring, by the edge node device, the operating environment information required for the operation of the terminal device when detecting the access of the terminal device, the method further includes:
the method comprises the steps that edge node equipment receives application binding configuration sent by a management center, and a plurality of edge applications to be operated and equipment requirement information corresponding to the edge applications to be operated are determined according to the application binding configuration;
creating a corresponding operation container for each edge application to be operated;
creating simulation equipment for each edge application to be operated according to the equipment requirement information, and loading each edge application to be operated into a corresponding operation container for operation;
and when the loading is finished, starting the equipment access monitor, and detecting whether the terminal equipment is accessed in real time.
6. The terminal device data interaction method of any one of claims 1-4, wherein after the step of performing data interaction with the terminal device through the device driver and the instruction set, the method further comprises:
receiving a device unloading request issued by the management center, and determining an application to be unloaded according to the device unloading request;
and unloading the application to be unloaded.
7. The terminal device data interaction method of claim 6, wherein after the step of uninstalling the application to be uninstalled, the method further comprises:
when the uninstallation is finished, detecting whether terminal equipment without application binding exists;
when the terminal equipment exists, the terminal equipment without application binding is taken as target terminal equipment;
and unloading the device driver and the instruction set corresponding to the target terminal device.
8. A terminal device data interaction system is characterized in that the terminal device data interaction system comprises:
the terminal equipment comprises a connection management module, a connection management module and a connection management module, wherein the connection management module is used for acquiring running environment information required by the running of the terminal equipment when the access of the terminal equipment is detected;
the data acquisition module is used for acquiring the drive installation package corresponding to the operating environment information from a management center;
the driver installation module is used for installing the device driver and the instruction set corresponding to the terminal device based on the driver installation package;
and the equipment control module is used for carrying out data interaction with the terminal equipment through the equipment driver and the instruction set.
9. An edge node apparatus, characterized in that the edge node apparatus comprises: processor, memory and terminal device data interaction program stored on the memory and operable on the processor, the terminal device data interaction program when executed by the processor implementing the steps of the terminal device data interaction method according to any one of claims 1-7.
10. A computer-readable storage medium, wherein the computer-readable storage medium has a terminal device data interaction program stored thereon, and when the terminal device data interaction program is executed, the steps of the terminal device data interaction method according to any one of claims 1 to 7 are implemented.
CN202110860463.5A 2021-07-28 2021-07-28 Terminal equipment data interaction method, system, equipment and storage medium Active CN113596958B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110860463.5A CN113596958B (en) 2021-07-28 2021-07-28 Terminal equipment data interaction method, system, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110860463.5A CN113596958B (en) 2021-07-28 2021-07-28 Terminal equipment data interaction method, system, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN113596958A true CN113596958A (en) 2021-11-02
CN113596958B CN113596958B (en) 2023-04-28

Family

ID=78251394

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110860463.5A Active CN113596958B (en) 2021-07-28 2021-07-28 Terminal equipment data interaction method, system, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN113596958B (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110083366A (en) * 2018-01-24 2019-08-02 腾讯科技(深圳)有限公司 The generation method of application runtime environment, calculates equipment and storage medium at device
US20190319863A1 (en) * 2018-04-12 2019-10-17 Cisco Technology, Inc. Anomaly detection and correction in wireless networks
CN110377590A (en) * 2018-04-11 2019-10-25 深圳富桂精密工业有限公司 Data collection system, method and computer readable storage medium based on Internet of Things
CN110708346A (en) * 2018-07-09 2020-01-17 北京高绎信息技术有限公司 Information processing system and method
CN111083671A (en) * 2020-01-14 2020-04-28 中国电子科技集团公司电子科学研究院 Deterministic network architecture-based vehicle road cloud collaborative networking architecture and method
CN113179325A (en) * 2021-04-30 2021-07-27 招商局金融科技有限公司 Multi-terminal collaborative interaction method and device, gateway box and medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110083366A (en) * 2018-01-24 2019-08-02 腾讯科技(深圳)有限公司 The generation method of application runtime environment, calculates equipment and storage medium at device
CN110377590A (en) * 2018-04-11 2019-10-25 深圳富桂精密工业有限公司 Data collection system, method and computer readable storage medium based on Internet of Things
US20190319863A1 (en) * 2018-04-12 2019-10-17 Cisco Technology, Inc. Anomaly detection and correction in wireless networks
CN110708346A (en) * 2018-07-09 2020-01-17 北京高绎信息技术有限公司 Information processing system and method
CN111083671A (en) * 2020-01-14 2020-04-28 中国电子科技集团公司电子科学研究院 Deterministic network architecture-based vehicle road cloud collaborative networking architecture and method
CN113179325A (en) * 2021-04-30 2021-07-27 招商局金融科技有限公司 Multi-terminal collaborative interaction method and device, gateway box and medium

Also Published As

Publication number Publication date
CN113596958B (en) 2023-04-28

Similar Documents

Publication Publication Date Title
EP1528751B1 (en) Simple and dynamic configuration of network devices
CN107203419B (en) Method, device and system for calling among modules in application program
CN109451472B (en) Dynamic management method for multiple Bluetooth chips on Android intelligent device
CN112506617B (en) Mirror image updating method and device for side car containers in Kubernetes cluster
EP2608585B1 (en) Method, device and system for triggering terminal operation
CN113157339B (en) Application service extension method, system, storage medium and device based on OSB
CN114422618B (en) Cloud-protogenesis-based IOT platform protocol adaptation method, device, equipment and medium
CN113448756B (en) Inter-process communication system and method and computing device
US20070106770A1 (en) Managing a remote device by a communication element that does not specify an identifier for the management object
CN113190282A (en) Android operating environment construction method and device
WO2014169619A1 (en) Systems and methods for installing applications
EP3629160B1 (en) Method and device for managing vnf instantiation
CN112698839A (en) Data center node deployment method, device and system and computer storage medium
CN113254075B (en) Instruction execution method, instruction execution device, electronic device, and storage medium
US20240045657A1 (en) System architecture for implementing dds communication based on autosar, communication method, and device
CN108234174B (en) Management method and device of virtual network function
CN108712298B (en) Network equipment upgrading method and device, network equipment and storage medium
WO2007123025A1 (en) Technique of controlling communication of installed apparatus with outside by means of proxy server
CN113596958A (en) Terminal equipment data interaction method, system, equipment and storage medium
CN114726905B (en) Method, device, equipment and storage medium for accessing Tbox network into Android system
CN112367362B (en) Data processing method, device, equipment and computer storage medium
CN107783837B (en) Method and device for performing storage expansion and electronic equipment
CN113076128B (en) Method, device, electronic equipment and storage medium for robot configuration
CN110943968B (en) Equipment access control method and equipment access assembly
CN109901826B (en) Data processing method and device for Java program and electronic equipment

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant