CN113596958B - 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
CN113596958B
CN113596958B CN202110860463.5A CN202110860463A CN113596958B CN 113596958 B CN113596958 B CN 113596958B CN 202110860463 A CN202110860463 A CN 202110860463A CN 113596958 B CN113596958 B CN 113596958B
Authority
CN
China
Prior art keywords
equipment
application
edge
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.)
Active
Application number
CN202110860463.5A
Other languages
Chinese (zh)
Other versions
CN113596958A (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

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The invention belongs to the technical field of computers, and discloses a terminal equipment data interaction method, a system, equipment and a storage medium. According to the method, when the access of the terminal equipment is detected through the edge node equipment, the operation environment information required by the operation of the terminal equipment is acquired; acquiring a drive installation package corresponding to the operation 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 carrying out data interaction with the terminal equipment through the equipment driver and the instruction set. Because the drive installation package is quickly obtained from the management center when the access of the terminal equipment is detected, and the device drive and the instruction set for winning the terminal equipment are installed according to the drive installation package, the edge node equipment can perform data interaction with the terminal equipment according to the installed device drive and the instruction set, thereby ensuring that the connection with the accessed terminal equipment can be quickly established.

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, an apparatus, and a storage medium for terminal device data interaction.
Background
With the advent of the 5G internet of everything age, the amount of data 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 has exploded, and requirements on real-time performance, network dependency, security and the like are brought to the infrastructure, so that in order to solve these problems, related edge computing technologies have arisen.
Edge computing provides open edge intelligence services nearby by placing computing, storage, bandwidth, application, etc. resources on the edge side of the network, computing by edge nodes near the data source, and fusing the core capabilities of the network, computing, storage, and application on the edge side of the network near the object or data source. Compared with cloud computing, edge computing is deployed nearby, belonging to an extension of the cloud computing concept. In a business scene facing massive connection and ultra-large bandwidth, in order to meet the requirements of wider connection, lower time delay and better control, cloud computing evolves from a centralized form to a global distributed node combination, and edge computing is a new antenna for distributed expansion of the cloud computing to an edge side. Cloud edge coordination is an important characteristic in edge computing, and the problem that resources are short and mass equipment cannot be managed uniformly in the process of edge computing landing can be solved through cloud edge coordination.
However, in the cloud-edge collaboration scenario, management and application between the edge application and the terminal device lack linkage. Under a complex scene, the dynamically deployed edge application and the terminal equipment accessing the edge node cannot quickly establish corresponding control and data channels, which is not beneficial to quick online and use of the edge application.
The foregoing is provided merely for the purpose of facilitating understanding of the technical solutions of the present invention and is not intended to represent an admission that the foregoing is prior art.
Disclosure of Invention
The invention mainly aims to provide a terminal equipment data interaction method, a system, equipment and a storage medium, and aims to solve the technical problem that connection with terminal equipment cannot be quickly established in a cloud-edge cooperative scene in the prior art.
In order to achieve the above object, the present invention provides a terminal device data interaction method, which includes the following steps:
when detecting that a terminal device is accessed, an edge node acquires operation environment information required by operation of the terminal device;
acquiring a drive installation package corresponding to the operation 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 carrying out data interaction with the terminal equipment through the equipment driver and the instruction set.
Optionally, when the edge node detects that the terminal device is accessed, the step of acquiring the operation environment information required by the operation of the terminal device includes:
when detecting that a terminal device is accessed, an edge node acquires device model information of the terminal device;
acquiring edge application corresponding to the equipment model information;
and determining the operation environment information required by the operation of the terminal equipment according to the edge application and the equipment model information.
Optionally, the step of determining the operation environment information required by the operation of the terminal device 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 instruction set identification in a management center according to the application identification information and the equipment model information;
and constructing operation environment information according to the driving model and the instruction set identification.
Optionally, the step of obtaining the drive installation package corresponding to the running environment information from the management center includes:
generating a drive installation request according to the running 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 running environment information according to the drive installation request.
Optionally, before the step of acquiring the operation environment information required by the operation of the terminal device when the edge node detects that the terminal device is accessed, the edge node further includes:
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;
creating corresponding operation containers for each edge application to be operated;
creating simulation equipment for each edge application to be operated according to the equipment demand information, and loading each edge application to be operated into a corresponding operation container for operation;
and when loading is finished, starting the equipment access monitor, and detecting whether terminal equipment is accessed or not 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 an equipment unloading request issued by the management center, and determining an application to be unloaded according to the equipment unloading request;
and unloading the application to be unloaded.
Optionally, after the step of unloading the application to be unloaded, the method further includes:
detecting whether a terminal device without application binding exists or not when unloading is completed;
when the terminal equipment exists, the terminal equipment without application binding is used 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 objective, the present invention further provides a terminal device data interaction system, where the terminal device data interaction system includes:
the connection management module is used for acquiring operation environment information required by the operation of the terminal equipment when the access of the terminal equipment is detected;
the data acquisition module is used for acquiring a drive installation package corresponding to the operation environment information from a management center;
the drive installation module is used for installing equipment drive and instruction sets corresponding to the terminal equipment based on the drive 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 also proposes an edge node device, including: the terminal equipment data interaction device comprises a processor, a memory and a terminal equipment data interaction program which is stored in the memory and can run on the processor, wherein the terminal equipment data interaction program realizes the steps of the terminal equipment data interaction method when being executed by the processor.
In addition, in order to achieve the above object, the present invention also proposes a computer readable storage medium having stored thereon a terminal device data interaction program, which when executed implements the steps of the terminal device data interaction method as described above.
According to the method, when the access of the terminal equipment is detected through the edge node, the operation environment information required by the operation of the terminal equipment is acquired; acquiring a drive installation package corresponding to the operation 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 carrying out data interaction with the terminal equipment through the equipment driver and the instruction set. Because the drive installation package is quickly obtained from the management center when the terminal equipment is detected to be accessed, and the device drive and the instruction set for winning the terminal equipment are installed according to the drive installation package, the edge node can perform data interaction with the terminal equipment according to the installed device drive and the instruction set, thereby ensuring that the connection with the accessed terminal equipment can be quickly established.
Drawings
FIG. 1 is a schematic diagram of an electronic device of a hardware operating environment according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a first embodiment of a data interaction method of a terminal device according to the present invention;
FIG. 3 is a flowchart of a second embodiment of a data interaction method of a terminal device according to the present invention;
fig. 4 is a schematic diagram of an access flow of a terminal device according to an embodiment of the present invention;
fig. 5 is a schematic flow chart of a third embodiment of a data interaction method of a terminal device according to the present invention;
FIG. 6 is a schematic diagram of a terminal application uninstallation flow diagram that illustrates one embodiment;
fig. 7 is a block diagram of a first embodiment of a data interaction system for a terminal device according to the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Referring to fig. 1, fig. 1 is a schematic diagram of an edge node device structure of a hardware running 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 (Central Processing Unit, CPU), a communication bus 1002, a user interface 1003, a network interface 1004, a memory 1005. Wherein the communication bus 1002 is used to enable connected communication between these components. The user interface 1003 may include a Display, an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may further 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 high-speed random access Memory (Random Access Memory, RAM) or a stable nonvolatile Memory (NVM), such as a disk Memory. The memory 1005 may also optionally be a storage device separate from the processor 1001 described above.
Those skilled in the art will appreciate that the structure shown in fig. 1 is not limiting of the electronic device and may include more or fewer components than shown, or may combine certain components, or may be arranged in different components.
As shown in fig. 1, an operating system, a network communication module, a user interface module, and a terminal device data interaction program may be included in the memory 1005 as one type of storage medium.
In the electronic device 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 the edge node device, where the electronic device invokes the 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.
The embodiment of the invention provides a terminal equipment data interaction method, referring to fig. 2, fig. 2 is a flow chart of a first embodiment of the terminal equipment data interaction method of the invention.
In this embodiment, the terminal device data interaction method includes the following steps:
step S10: and when the edge node detects that the terminal equipment is accessed, acquiring the operation environment information required by the operation of the terminal equipment.
It should be noted that, the execution body of the embodiment may be an edge node device, and the edge node device may be a device installed on a user side as an edge node, for example: the home gateway, the intelligent terminal box, and other devices 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, an edge node device is taken as an example to describe a data interaction method of a terminal device of the present invention.
It should be noted that the terminal device may be a device that the user needs to use currently, for example: VR somatosensory devices or other intelligent terminal devices. The operation environment information may include information such as a driving model number and an instruction set identification of the terminal device. When the edge node device detects that the terminal device is connected, the operation environment information required by the operation of the terminal device can be obtained by the edge node device, which monitors whether the terminal device is connected with the existing interface and the expansion interface in real time, when the terminal device is connected with the existing interface and the expansion interface, the device model of the terminal device is obtained, and the operation environment information corresponding to the device model is searched in the environment information table, so that the operation environment information required by the operation of the connected terminal device is determined. The mapping relationship between the device model and the operating environment information may be included in the environment information table, and the mapping information in the environment information table may be preset by a user or may be preset by a manager of the edge node device, which is not limited in this embodiment.
Further, in the actual usage scenario, there may be a difference between device driving and control instructions required by different edge application control terminal devices in running, and in order to save resources of the edge node device, step S10 of this embodiment may include:
when detecting that a terminal device is accessed, the edge node device acquires the device model information of the terminal device; acquiring edge application corresponding to the equipment model information; and determining the operation environment information required by the operation 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 program 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, a device manufacturer, and the like. The obtaining of the device model information of the terminal device by the edge node device when the terminal device access is detected may be that the edge node device reads the device model information of the terminal device through an interface of the device access when the terminal device access is detected. The obtaining the edge application corresponding to the equipment model information may be searching for the edge application corresponding to the equipment model information in a preset model application mapping table, where the preset model application mapping table may include a corresponding relationship between the equipment model and the edge application, and the mapping relationship in the preset model application mapping table may be set when the edge application is installed.
In actual use, the determining the operation environment information required by the operation of the terminal device according to the edge application and the device model information may be searching the operation environment information required by the operation of the terminal device in a preset operation information table according to the edge application and the device model information, and the preset operation information table may store the corresponding relationship between the operation environment information and the edge application and the device model information, which 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 number of models and manufacturers of the terminal device is 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, so that 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 model information in this embodiment includes:
acquiring application identification information of the edge application; searching a corresponding driving model and instruction set identification in a management center according to the application identification information and the equipment model information; and constructing operation 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 searching for the winning driving model and instruction set identifier in the management center according to the application identification information and the equipment model information may be searching for the corresponding driving model and instruction set identifier in a preset information table stored in the management center according to the application identification information and the equipment model information. The operation environment information is constructed according to the drive model and the instruction set identification, and the drive model and the instruction set identification are converted into data in a preset format, so that the operation environment information is obtained, and the preset format can be preset by a manager of the edge node equipment.
Step S20: and acquiring a drive installation package corresponding to the running environment information from a management center.
It should be noted that the management center may be a cloud center in cloud-edge collaboration. In the cloud edge cooperative scene, the edge node equipment has limited performance and resources, and cannot store all the drive installation packages, so that after the operation environment information required by the operation of the terminal equipment is acquired, the drive installation package corresponding to the operation environment information can be acquired from the management center.
Further, in order to quickly obtain the driver installation package corresponding to the running environment information from the management center, step S20 of this embodiment may include:
generating a drive installation request according to the running 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 running environment information according to the drive installation request.
The drive installation request may be generated based on the operation environment information, and the drive installation request may be generated using the operation environment information as a request parameter.
It can be understood that when the management center receives the drive installation request, the management center can analyze the drive installation request to obtain operation environment information, then find a drive installation package corresponding to the operation environment information in the installation package storage center according to the operation environment information, and send the drive installation package to the edge node device.
Step S30: and installing the device driver and the instruction set corresponding to the terminal device based on the driver installation package.
It can be understood that the device driver and the instruction set required by the terminal device in operation can be obtained by installing the obtained driver installation package, wherein the instruction set can include various control instructions required by controlling the terminal device in operation.
Step S40: and carrying out 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 acquired, 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 realize data interaction with the terminal device.
According to the embodiment, when the edge node equipment detects that the terminal equipment is accessed, the operation environment information required by the operation of the terminal equipment is acquired; acquiring a drive installation package corresponding to the operation 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 carrying out data interaction with the terminal equipment through the equipment driver and the instruction set. Because the drive installation package is quickly obtained from the management center when the access of the terminal equipment is detected, and the device drive and the instruction set for winning the terminal equipment are installed according to the drive installation package, the edge node equipment can perform data interaction with the terminal equipment according to the installed device drive and the instruction set, thereby ensuring that the connection with the accessed terminal equipment can be quickly established.
Referring to fig. 3, fig. 3 is a flowchart of a second embodiment of a data interaction method for a terminal device according to the present invention.
Based on the above first embodiment, the method for data interaction between terminal devices in this embodiment further includes, before the step S10:
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 the edge applications to be operated according to the application binding configuration.
In order to ensure the security of the edge node device, the edge node device may only communicate with the management center, so that when the user needs to install the application, the user may send an application installation request to the management center, and when the management center receives the application installation request sent by the user, the corresponding relationship between the edge application and the terminal device is determined according to the application installation request, and an application binding configuration is generated and sent to the edge node device.
In actual use, when the edge application receives the application binding configuration sent by the management center, the edge application can read the data of the application binding configuration, and determine the edge application to be operated and the equipment requirement information corresponding to each edge application to be operated according to the read data. The to-be-operated edge application can be an application which the user wants to install, and the equipment requirement information can comprise information such as equipment model identification and the like.
Step S02: and creating a corresponding running container for each edge application to be run.
In order to ensure that the edge applications in the edge node device do not affect each other, a container may be used to run the edge applications in the edge node device, and the edge applications may be isolated by using the container, so as to avoid the mutual influence of the edge applications. Thus, when determining the edge applications to be run, a corresponding run container may be created for each edge application to be run.
Step S03: and creating simulation equipment for each edge application to be operated according to the equipment demand information, and loading each edge application to be operated into a corresponding operation container for operation.
It should be noted that, if a part of the edge applications do not interact with the device, the edge applications cannot normally operate, but in order to ensure that the edge applications can normally operate, simulation devices can be created for each edge application to be operated according to the device requirement information, and then the edge applications to be operated are loaded into corresponding operation containers, so that the edge applications to be operated can be ensured to normally operate.
Step S04: and when loading is finished, starting the equipment access monitor, and detecting whether terminal equipment is accessed or not in real time.
It can be understood that after loading the edge applications to be run, the edge node device can start the device access monitor to detect whether the terminal device is accessed in real time.
For easy understanding, the description is given with reference to fig. 4, but the present scheme is not limited thereto, and fig. 4 is a schematic view of an access flow of the terminal device in this embodiment. The flow can be divided into 7 steps according to the labels: 1. the 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 equipment constructs an operation container according to the application binding configuration, loads the edge application into the container for operation, and informs the equipment management system to start the equipment to access the 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. the edge node device installs a driver installation package so that the edge application in the running container can interact data with the terminal device.
Wherein the device management system may be installed in the edge node device, and may include: device connection management, device service management, device controller management, and external API gateway.
Device connection management: the method is used for connection management of terminal equipment, is based on an equipment driving service core framework, supports expansion to realize various different connection protocols, adopts a plug-and-play mode, and acquires a driving and instruction set from a central cloud to carry out equipment connection intercommunication and control management after detecting a new equipment connection or an edge side application connection request. Meanwhile, the authority management of the connected equipment is required to be supported, the use of the edge application on the equipment as required is supported, the authority control of the equipment after the virtualization of the edge node equipment is controlled, and the use of the system is ensured to be minimized. And (3) for realizing state management of the online equipment, unloading the drive and instruction set of the equipment after the equipment connection is lost and the dependent edge application is offline, and releasing the disk space of the effective infrastructure of the edge node equipment.
Device service management: the method is used for service management between the edge application and the terminal equipment, provides the function of simulating the edge application equipment based on an event-driven mode, simulates needed equipment for the online application and automatically binds the equipment with the connected equipment, realizes operation decoupling between the edge application and the real equipment, and ensures that the plug and play of the equipment does not influence the online and offline of the edge application. In addition, edge application data and control services are provided, and decoupling of edge application on terminal equipment operation and data acquisition is achieved through protocol driving conversion and data format conversion of the terminal equipment through tuple.
Device controller management: the device control function of the same life cycle of the containerized deployment edge application is provided as the SDK for the edge application call. The system mainly comprises a virtual device controller and a general 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 device controller is used for controlling universal commands such as device start-up, shutdown, reset and the like. And the final edge application invokes related services in a related device service management module through the device controller SDK to realize the management of the device.
External API gateway: and the gateway is used as a unified message processing inlet provided by the gateway, and provides an inlet for interaction between each service in the system and outside the system and the cloud.
In this embodiment, the edge node device only communicates with the management center, so that the possibility that the edge node device is attacked is reduced, the security of the edge node device is improved, and when the edge node device receives the application binding configuration issued by the management center, an operation container is created for each edge application to be operated, each edge application is operated in a trial container mode, mutual interference of each edge application is avoided, the stability of the edge node device is improved, and simulation equipment is created for the edge application before the edge application is loaded into the corresponding operation container to operate, so that the situation that the edge application cannot normally operate due to the fact that the corresponding entity equipment does not exist is avoided.
Referring to fig. 5, fig. 5 is a flowchart of a third embodiment of a data interaction method for a terminal device according to the present invention.
Based on the above first embodiment, the method for data interaction between terminal devices in this embodiment further includes, after the step S40:
step S50: and receiving an equipment unloading request issued by the management center, and determining an application to be unloaded according to the equipment 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 when a user needs to uninstall the edge application, the user may send an application uninstall request to the management center, when receiving the application uninstall request, the management center will issue the application uninstall request to the edge node device, when receiving the application uninstall request, the edge node device may read the parameters included in the application uninstall request, obtain application identification information, and then search for the 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 devices are all running in a containerized manner, so that the unloading of the application to be unloaded may be the destruction of 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 the unnecessary performance consumption as much as possible, after step S60 of this embodiment, the method may further include:
detecting whether a terminal device without application binding exists or not when unloading is completed; when the terminal equipment exists, the terminal equipment without application binding is used as target terminal equipment; and unloading the device driver and the instruction set corresponding to the target terminal device.
It should be noted that, determining whether the terminal device has an application binding may be to detect whether the terminal device of the current access edge node device has a correspondence with an edge application that is not currently unloaded, and if one terminal device does not have a correspondence with an edge application that is not currently unloaded, then it may be determined that the terminal device is a terminal device without application binding.
It can be understood that if one terminal device has no application binding, it can be stated that the terminal device is in an unused state, and the device driver and instruction set thereof will not be used at this time, so that the terminal device can be used as a target terminal device, and the device driver and instruction set corresponding to the terminal device can be unloaded, thereby saving the space of the edge node device and reducing unnecessary performance consumption.
For easy understanding, the description is given with reference to fig. 6, but the scheme is not limited thereto, fig. 6 is a schematic diagram of an unloading flow of the terminal application in this embodiment, and the unloading flow may be divided into 5 steps according to the reference numerals: 1. a user submits an application uninstallation request to a management center; 2. the management center issues an application unloading request to the edge node equipment; 3. the edge node equipment searches the corresponding application to be unloaded, destroys the application container to be unloaded, and notifies the equipment management system when destroying the application container to be unloaded; 4. the device management system detects whether the terminal device without application binding exists or not, and uninstalls a device driver and an instruction set of the terminal device without application binding; 5. informing the management center that the edge application has been offloaded.
In this embodiment, the edge node device only communicates with the management center, so that the possibility that the edge node device is 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 unloaded when receiving the application unloading request, so as to save resources, further scan the terminal device without application binding, take the terminal device without application binding as the target terminal device, unload the device driver and the instruction set corresponding to the target terminal device, and further reduce unnecessary performance consumption of the edge node device.
In addition, the embodiment of the invention also provides a storage medium, wherein the storage medium stores a terminal equipment data interaction program, and the terminal equipment data interaction program realizes the steps of the terminal equipment data interaction method when being executed by a processor.
Referring to fig. 7, fig. 7 is a block diagram illustrating a first embodiment of a data interaction system for a terminal device according to the present invention.
As shown in fig. 7, a terminal device data interaction system according to an embodiment of the present invention includes:
the connection management module 10 is used for acquiring operation environment information required by the operation of the terminal equipment when the access of the terminal equipment is detected;
the data acquisition module 20 is configured to acquire a driver installation package corresponding to the operation environment information from a management center;
a driver installation module 30, configured to install a device driver and an instruction set corresponding to the terminal device based on the driver installation package;
and the device control module 40 is used for performing data interaction with the terminal device through the device driver and the instruction set.
According to the embodiment, when the edge node equipment detects that the terminal equipment is accessed, the operation environment information required by the operation of the terminal equipment is acquired; acquiring a drive installation package corresponding to the operation 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 carrying out data interaction with the terminal equipment through the equipment driver and the instruction set. Because the drive installation package is quickly obtained from the management center when the access of the terminal equipment is detected, and the device drive and the instruction set for winning the terminal equipment are installed according to the drive installation package, the edge node equipment can perform data interaction with the terminal equipment according to the installed device drive and the instruction set, thereby ensuring that the connection with the accessed terminal equipment can be quickly established.
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 edge application corresponding to the equipment model information; and determining the operation environment information required by the operation 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 instruction set identification in a management center according to the application identification information and the equipment model information; and constructing operation environment information according to the driving model and the instruction set identification.
Further, the data acquisition module 20 is further configured to generate a drive installation request according to the running 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 running 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 edge applications to be run and device requirement information corresponding to each edge application to be run according to the application binding configuration; creating corresponding operation containers for each edge application to be operated; creating simulation equipment for each edge application to be operated according to the equipment demand information, and loading each edge application to be operated into a corresponding operation container for operation; and when loading is finished, starting the equipment access monitor, and detecting whether terminal equipment is accessed or not in real time.
Further, the device control module 40 is further configured to receive a device uninstallation request issued by the management center, and determine an application to be uninstalled according to the device uninstallation 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 used 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 foregoing is illustrative only and is not limiting, and that in specific applications, those skilled in the art may set the invention as desired, and the invention is not limited thereto.
It should be noted that the above-described working procedure is merely illustrative, and does not limit the scope of the present invention, and in practical application, a person skilled in the art may select part or all of them according to actual needs to achieve the purpose of the embodiment, which is not limited herein.
In addition, technical details not described in detail in this embodiment may refer to the terminal device data interaction method provided in any embodiment of the present invention, which is not described herein again.
Furthermore, it should 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 one … …" does not exclude the presence of other like elements in a process, method, article, or system that comprises the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. Read Only Memory)/RAM, magnetic disk, optical disk) and including several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.

Claims (9)

1. The terminal equipment data interaction method is characterized by comprising the following steps of:
when detecting that a terminal device is accessed, the edge node device acquires operation environment information required by the operation of the terminal device;
acquiring a drive installation package corresponding to the operation 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;
performing data interaction with the terminal equipment through the equipment driver and the instruction set;
the method comprises the steps that when the edge node equipment detects that the terminal equipment is accessed, the edge node equipment further comprises the following steps:
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;
creating corresponding operation containers for each edge application to be operated;
creating simulation equipment for each edge application to be operated according to the equipment demand information, and loading each edge application to be operated into a corresponding operation container for operation;
and when loading is finished, starting the equipment access monitor, and detecting whether terminal equipment is accessed or not in real time.
2. The method for data interaction between terminal devices according to claim 1, wherein the step of obtaining, by the edge node device, operation environment information required for operation of the terminal device when detecting access to the terminal device, comprises:
when detecting that a terminal device is accessed, the edge node device acquires the device model information of the terminal device;
acquiring edge application corresponding to the equipment model information;
and determining the operation environment information required by the operation of the terminal equipment according to the edge application and the equipment model information.
3. The terminal device data interaction method according to claim 2, wherein the step of determining operation environment information required for the operation of the terminal device according to the edge application and the device model information comprises:
acquiring application identification information of the edge application;
searching a corresponding driving model and instruction set identification in a management center according to the application identification information and the equipment model information;
and constructing operation environment information according to the driving model and the instruction set identification.
4. The terminal device data interaction method according to claim 1, wherein the step of acquiring the drive installation package corresponding to the operation environment information from the management center comprises:
generating a drive installation request according to the running 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 running environment information according to the drive installation request.
5. The method for data interaction between a terminal device according to any one of claims 1-4, further comprising, after said step of data interaction with said terminal device via said device driver and said instruction set:
receiving an equipment unloading request issued by the management center, and determining an application to be unloaded according to the equipment unloading request;
and unloading the application to be unloaded.
6. The method for data interaction between terminal devices according to claim 5, wherein after the step of uninstalling the application to be uninstalled, the method further comprises:
detecting whether a terminal device without application binding exists or not when unloading is completed;
when the terminal equipment exists, the terminal equipment without application binding is used as target terminal equipment;
and unloading the device driver and the instruction set corresponding to the target terminal device.
7. A terminal device data interaction system, the terminal device data interaction system comprising:
the connection management module is used for acquiring operation environment information required by the operation of the terminal equipment when the access of the terminal equipment is detected;
the data acquisition module is used for acquiring a drive installation package corresponding to the operation environment information from a management center;
the drive installation module is used for installing equipment drive and instruction sets corresponding to the terminal equipment based on the drive installation package;
the device control module is used for carrying out data interaction with the terminal device through the device driver and the instruction set;
the connection management module is also used for receiving application binding configuration sent by the management center by the edge node equipment, and determining a plurality of edge applications to be operated and equipment requirement information corresponding to the edge applications to be operated according to the application binding configuration; creating corresponding operation containers for each edge application to be operated; creating simulation equipment for each edge application to be operated according to the equipment demand information, and loading each edge application to be operated into a corresponding operation container for operation; and when loading is finished, starting the equipment access monitor, and detecting whether terminal equipment is accessed or not in real time.
8. An edge node device, the edge node device comprising: a processor, a memory and a terminal device data interaction program stored on the memory and operable on the processor, which when executed by the processor, carries out the steps of the terminal device data interaction method of any of claims 1-6.
9. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a terminal device data interaction program, which when executed implements the steps of the terminal device data interaction method according to any of claims 1-6.
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 CN113596958A (en) 2021-11-02
CN113596958B true 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 (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111083671A (en) * 2020-01-14 2020-04-28 中国电子科技集团公司电子科学研究院 Deterministic network architecture-based vehicle road cloud collaborative networking architecture and method

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110083366B (en) * 2018-01-24 2021-06-18 腾讯科技(深圳)有限公司 Application running environment generation method and device, computing equipment and storage medium
CN110377590B (en) * 2018-04-11 2021-01-19 深圳富桂精密工业有限公司 Data acquisition system and method based on Internet of things and computer readable storage medium
US10574547B2 (en) * 2018-04-12 2020-02-25 Cisco Technology, Inc. Anomaly detection and correction in wireless networks
CN110708346B (en) * 2018-07-09 2023-03-21 北京高绎信息技术有限公司 Information processing system and method
CN113179325B (en) * 2021-04-30 2022-08-02 招商局金融科技有限公司 Multi-terminal collaborative interaction method and device, gateway box and medium

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111083671A (en) * 2020-01-14 2020-04-28 中国电子科技集团公司电子科学研究院 Deterministic network architecture-based vehicle road cloud collaborative networking architecture and method

Also Published As

Publication number Publication date
CN113596958A (en) 2021-11-02

Similar Documents

Publication Publication Date Title
US11388228B2 (en) Methods, systems and computer readable media for self-replicating cluster appliances
US7823023B2 (en) Test framework for testing an application
CN110908753B (en) Intelligent fusion cloud desktop server, client and system
US20110126193A1 (en) System and Method for Imaging and Provisioning of Information Handling System
EP2701059A1 (en) Method and apparatus for loading application program
CN113157339B (en) Application service extension method, system, storage medium and device based on OSB
CN113190282A (en) Android operating environment construction method and device
WO2024002229A1 (en) Application management method and related device
CN112333017A (en) Service configuration method, device, equipment and storage medium
CN116800616B (en) Management method and related device of virtualized network equipment
CN114489701A (en) Configuration method and device of artificial intelligence software deployment environment and electronic equipment
CN113596958B (en) Terminal equipment data interaction method, system, equipment and storage medium
CN117519972A (en) GPU resource management method and device
CN113179269A (en) Internet of things-based protocol data analysis method, system, medium, and program product
CN113821220A (en) Installation method and device of linux operating system
CN108259895A (en) set-top box test method, system and terminal device
CN114726905B (en) Method, device, equipment and storage medium for accessing Tbox network into Android system
CN111459510A (en) Cross-network operating system installation method and device, electronic equipment and medium
CN115442913A (en) Protocol access method, communication method, development device, gateway and storage medium
CN100386726C (en) Method and system for renewing long-distance operation and control of computer platform system programe
CN115202820A (en) Method, device and equipment for creating Pod unit and storage medium
CN113342461A (en) Equipment mounting method and device, computer equipment and readable storage medium
CN111008043A (en) Server starting method of cloud platform and terminal
CN109901826B (en) Data processing method and device for Java program and electronic equipment
CN111026505B (en) Network equipment virtualization method and device

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