Accessing method for device, data exchange method, device, networked device and storage medium

Abstract

This application relates to a device access method, a data exchange method, and related equipment. The device access method configures the network device's configuration information based on a preset generation strategy. The configuration information includes scenario configuration information for the network device in at least one application scenario. The scenario configuration information includes at least one of a first descriptor set and a function instruction set, as well as data source configuration information. By preloading the scenario configuration information, the device functions of the network device can be redefined according to the target configuration information, thus enriching the device's functionality. In this application, the communication data between the network device and the target device does not pass through a computer host, effectively preventing packet capture by the computer host and leakage of the true data source and network communication data, and effectively preventing malicious programs from cracking the network device, ensuring the security of the network device and data.

Description

Data Exchange Method, Device, System, Storage Device, Server and Storage Medium This application relates to the field of communication and data security technologies, and particularly relates to a data exchange method, device, storage device, server and storage medium. Currently, the device functions of some access devices (such as Universal Serial Bus (USB) devices) are fixed at the time of factory shipment and cannot be changed after factory shipment or can only be changed by rewriting software. And when the access device needs to expand its applications, control software such as drivers needs to be installed in the computer host, which is likely to be packet captured by the computer host, thereby exposing the real data source and network communication data, and may also cause the access device to be cracked by malicious programs, posing relatively high security risks. This application provides a data exchange method, device, storage device, server and computer-readable storage medium to solve the technical problems of the current access device having a single function and relatively high security risks. In a first aspect, this application also provides a device access method applied to a networking device. The method includes: when communicating and connecting with a server, preloading target configuration information. The server stores at least one preset configuration information, and the target configuration information is one of the preset configuration information. The target configuration information includes scenario configuration information of the networking device in at least one application scenario. The scenario configuration information includes at least one of a first descriptor set and a descriptor instruction set. The first descriptor set is used to define the device type of the networking device. The scenario configuration information stored in the server is generated based on a preset generation strategy by configuring at least one of the first descriptor set and the descriptor instruction set of the networking device and data source configuration information before preloading the target configuration information. Based on the target scenario configuration information, establish a communication connection with a target device to enable the networking device to access the target device. The target scenario configuration information is one of the scenario configuration information. In some implementation manners of the first aspect, the step of when communicating and connecting with the server, preloading the target configuration information includes: when communicating and connecting with the server, sending a configuration acquisition request to the server. The configuration acquisition request carries the identification information of the networking device. Receiving the target configuration information corresponding to the identification information returned by the server. In some implementation manners of the first aspect, the networking device serves as a host device communicating and connecting with the target device. The descriptor instruction set includes multiple function instruction sets, and the function instruction sets are used to control the data exchange between the networking device and the target device. In some implementations of the first aspect, establishing a communication connection with a target device based on the target scenario descriptor information includes: enumerating various descriptors in a second descriptor set of the target device based on a function instruction set in the descriptor instruction set; if the enumeration is successful, configuring a target data source when the networking device communicates with the target device, where the target data source is provided in the target device. In some implementations of the first aspect, the function instruction set includes an acquisition instruction set and a verification instruction set. Enumerating various descriptors in a second descriptor set of the target device based on the function instruction set in the descriptor instruction set includes: reading the second descriptor set of the target device based on the acquisition instruction set; verifying various descriptors in the second descriptor set based on the verification instruction set; if various descriptors meet a preset device requirement, determining that the enumeration is successful. In some implementations of the first aspect, the function instruction set further includes a data source instruction set, and the target scenario configuration information further includes data source configuration information. Configuring a target data source when the networking device communicates with the target device includes: determining a target data source when the networking device communicates with the target device based on the data source instruction set and according to the data source configuration information. In some implementations of the first aspect, the networking device is a network read / write control device. Establishing a communication connection with a target device based on the target scenario descriptor information includes: enumerating various descriptors in a second descriptor set of the target device based on a function instruction set in the descriptor instruction set; if the enumeration is successful, requesting the server to issue a driver instruction set corresponding to the target device to complete the communication connection, where the driver instruction set is used for data exchange with the target device. In some implementations of the first aspect, the networking device is a network proxy control device. Establishing a communication connection with a target device based on the target scenario descriptor information includes: enumerating various descriptors in a second descriptor set of the target device based on a function instruction set in the descriptor instruction set; if the enumeration is successful, sending the second descriptor set to the server to virtualize the target device at the server to generate a virtual device corresponding to the target device, thereby establishing a communication connection with the target device. In some implementations of the first aspect, the networking device is a slave device communicatively connected to the target device. Establishing a communication connection with the target device based on the target scenario descriptor information includes: receiving an enumeration request sent by the target device; in response to the enumeration request, returning the first descriptor set to the target device, so that the target device enumerates the first descriptor set, and after successful enumeration, configuring a target data source for the networking device and the target device when communicating according to the data source configuration information, and the target data source is set on the server. In some implementations of the first aspect, the data source configuration information includes capacity information of the data source, and the capacity information includes the last logical block address and block capacity of the data source. In some implementations of the first aspect, the descriptor set includes at least one of a device descriptor, a configuration descriptor, an interface descriptor, an endpoint descriptor, a string descriptor, and a preset custom descriptor. In some implementations of the first aspect, the target device includes at least one first target device and at least one second target device. The networking device is a host device communicatively connected to the first target device and a slave device communicatively connected to the second target device. Establishing a communication connection with the target device based on the target scenario descriptor information includes: enumerating various descriptors in the second descriptor set of the first target device based on the function instruction set in the descriptor instruction set; if the enumeration is successful, configuring a first target data source for the networking device and the first target device when communicating to complete the communication connection with the first target device, and the first target data source is set on the first target device; receiving an enumeration request sent by the second target device; in response to the enumeration request, returning the first descriptor set to the second target device, so that the second target device enumerates the first descriptor set, and after successful enumeration, configuring a second target data source for the networking device and the second target device when communicating according to the data source configuration information, and the second target data source is set on the server or the first target device. In a second aspect, the present application further provides a data exchange method applied to a networking device. The networking device establishes a communication connection with a server and a target device based on the above device access method. The method includes: obtaining a data exchange request sent by a first target party; responding to the data exchange request based on a preset processing policy and returning target data to the first target party, where the target data is data sent by a second target party. If the first target party is the server, the second target party is the target device, and if the first target party is the target device, the second target party is the server. In some implementations of the second aspect, the target device includes at least one first target device and at least one second target device. The networking device serves as the host device communicatively connected to the first target device and as the slave device communicatively connected to the second target device. If the first target party is the server, the second target party is the first target device or the second target device. If the first target party is the second target device, the second target party is the server or the first target device. In some implementations of the second aspect, responding to the data exchange request based on a preset processing policy and returning target data to the first target party includes: in response to the data exchange request, forwarding the data exchange request to the second target party; receiving the target data returned by the second target party in response to the data exchange request, and forwarding the target data to the first target party. In some implementations of the second aspect, the networking device is a network USB key device, and the target device is a computer host. Responding to the data exchange request and forwarding the data exchange request to the second target party includes: in response to the data exchange request sent by the computer host, forwarding the data exchange request to the server, where the data exchange request carries the credential information of the network USB key device, so that the server can verify the credential information. In some implementations of the second aspect, responding to the data exchange request based on a preset processing policy and returning target data to the first target party includes: performing data processing on the data exchange request based on a preset processing script to obtain a data processing result; sending a target data acquisition request to the second target party based on the data processing result; receiving the target data corresponding to the data processing result returned by the second target party in response to the target data acquisition request, and returning the target data to the first target party. In a third aspect, the present application further provides a device access method, which is applied to a server. The method includes: when communicating with an Internet-connected device, sending target configuration information to the Internet-connected device, where the target configuration information is used for the Internet-connected device to establish a communication connection with a target device. The server stores at least one preset configuration information, and the target configuration information is one of the preset configuration information. The target configuration information includes scenario configuration information of the Internet-connected device in at least one application scenario, and the scenario configuration information includes at least one of a first descriptor set and a descriptor instruction set. The first descriptor set is used to define the device type of the Internet-connected device; the scenario configuration information stored in the server is generated based on a preset generation strategy by configuring at least one of the first descriptor set and the descriptor instruction set of the Internet-connected device, and data source configuration information before preloading the target configuration information; establishing a communication connection with the target device based on the target scenario configuration information, so that the Internet-connected device is connected to the target device, and the target scenario configuration information is one of the scenario configuration information. In a fourth aspect, the present application further provides a data exchange method, which is applied to a server. The server establishes a communication connection with an Internet-connected device based on the above device access method. The method includes: sending a data exchange request to the Internet-connected device and receiving target data returned by the Internet-connected device, where the data exchange request is used for the Internet-connected device to respond to the data exchange request based on a preset processing strategy, and the target data is data sent by the target device; and / or, sending target data to the Internet-connected device according to the data exchange request responded by the Internet-connected device based on the preset processing strategy, where the target data is returned by the Internet-connected device to the target device, and the data exchange request is initiated by the target device. In a fifth aspect, the present application further provides a device access device, which is applied to an Internet-connected device. The device includes: a preloading module, which is used to preload target configuration information when communicating with a server. The server stores at least one preset configuration information, and the target configuration information is one of the preset configuration information. The target configuration information includes scenario configuration information of the Internet-connected device in at least one application scenario, and the scenario configuration information includes at least one of a first descriptor set and a descriptor instruction set. The descriptor set is used to define the device type of the Internet-connected device; the scenario configuration information stored in the server is generated based on a preset generation strategy by configuring at least one of the first descriptor set and the descriptor instruction set of the Internet-connected device, and data source configuration information before preloading the target configuration information; a first establishing module, which is used to establish a communication connection with a target device based on the target scenario configuration information, so that the Internet-connected device is connected to the target device, and the target scenario configuration information is one of the scenario configuration information. In a sixth aspect, the present application further provides a data exchange device, which is applied to a networking device. The networking device establishes a communication connection with a server and a target device based on the above device access method. The device includes: an acquisition module, configured to acquire a data exchange request sent by a first target party; a response module, configured to respond to the data exchange request based on a preset processing policy and return target data to the first target party. The target data is data sent by a second target party. If the first target party is the server, the second target party is the target device; if the first target party is the target device, the second target party is the server. In a seventh aspect, the present application further provides a networking device, including a processor and a memory. The memory is used to store a computer program, and when the computer program is executed by the processor, the above device access method or the above data exchange method is implemented. In an eighth aspect, the present application further provides a server, which includes a processor and a memory, and the server can implement the above device access method or the above data exchange method. In a ninth aspect, the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the above device access method or the above data exchange method is implemented. In a tenth aspect, the present application provides a device access method, which is applied to a networking device. The method includes: configuring configuration information of the networking device based on a preset generation policy. The configuration information includes scenario configuration information of the networking device in at least one application scenario. The scenario configuration information includes at least one of a first descriptor set and a function instruction set, and data source configuration information. The first descriptor set is used to define the device type of the networking device, and the function instruction set includes a descriptor instruction set; preloading the scenario configuration information; and establishing a communication connection between the networking device and a target device based on the loaded scenario configuration information, so that the networking device is accessed to the target device. In some implementation manners of the tenth aspect, the preloading the scenario configuration information includes: the networking device preloads the scenario configuration information before accessing the target device, and the scenario configuration information is stored in the server or the networking device, where the server represents all electronic devices that are communicatively connected to the networking device and can load the scenario configuration information. It should be noted that the server in this application can be an electronic device terminal using network connection (such as TCP / IP connection using remote communication, etc.) or non-network connection (such as point-to-point connection using WIFI, Bluetooth, LoRA, etc. of near-field communication). For example, when two terminals establish a data interaction relationship, and the first terminal provides scenario configuration information or data source to the second terminal (such as an Internet-connected device, an access device, etc.), then the first terminal can be understood as the server. Of course, the server can also be understood as deployed on a network-side server, virtual server, cloud server, server cluster, or personal computer, embedded computer, mobile phone, tablet computer, smart wearable device, as well as the user side, control side, and so on. In some implementation manners of the tenth aspect, the preloading of the scenario configuration information includes: when the Internet-connected device is started, it sends a scenario information acquisition request to the server, and the scenario information acquisition request includes the identity identifier of the Internet-connected device; the server responds to the scenario information acquisition request, filters out the scenario configuration information that matches the identity identifier of the Internet-connected device from the scenario configuration information as the scenario configuration information; and sends the scenario configuration information to the Internet-connected device. In some implementation manners of the tenth aspect, the configuration of the scenario configuration information of the Internet-connected device includes: by means of a server communicating with the Internet-connected device, or a user side communicating with the server, or the Internet-connected device according to a preset generation strategy, configuring at least one of the first descriptor set and the descriptor instruction set, and the data source configuration information, and then generating the scenario configuration information, and the preset generation strategy includes at least one of a custom creation strategy, a template creation strategy, and an external import creation strategy. In some implementation manners of the tenth aspect, establishing a communication connection with a target device based on the loaded scenario configuration information includes: according to the mode selection information in the scenario configuration information, setting the Internet-connected device to at least one of a host mode, a slave mode, and a peer-to-peer communication mode. In some implementation manners of the tenth aspect, if the Internet-connected device is set to the host mode, establishing a communication connection with a target device based on the descriptor instruction set includes: sending a handshake connection request to the target device; receiving a second descriptor set sent by the target device in response to the handshake connection request; enumerating various descriptors in the second descriptor set based on the descriptor instruction set of the function instruction set; if various descriptors of the second descriptor meet the preset device requirements, determining that the handshake connection is successful; if various descriptors do not meet the preset device requirements, determining that the handshake connection fails, and sending the obtained second descriptor set to the server, downloading a corresponding third descriptor set from the server, and re-enumerating based on the descriptors in the third descriptor set. In some implementations of the tenth aspect, the descriptor instruction set includes an instruction for obtaining a device descriptor, an instruction for obtaining a configuration descriptor, an instruction for obtaining an interface descriptor, an instruction for obtaining an endpoint descriptor, an instruction for obtaining a string descriptor, and an instruction for obtaining a BOS descriptor. In some implementations of the tenth aspect, the method further includes: if the handshake connection based on the descriptors in the third descriptor set is successful, configuring a target data source for the networking device to communicate with the target device, where the target data source is located in the target device, or the server, or a client connected to the server, or any one of the electronic devices communicatively connected to the networking device. In some implementations of the tenth aspect, the function instruction set includes a data source instruction set, and configuring the target data source for the networking device to communicate with the target device includes: based on the data source instruction set, determining the target data source for the networking device to communicate with the target device according to the data source configuration information. In some implementations of the tenth aspect, the target data source includes at least one of a storage medium, a storage space address range (such as a sector address range), a mirrored storage document, a specific folder, a database, and a data stream. In some implementations of the tenth aspect, the data source configuration information includes at least one of the capacity information of the data source, a storage medium, a storage space address range (such as a sector address range), a read / write state, a mirrored storage document, a specific folder, a database, and a data stream, and the capacity information includes at least one of the last logical block address of the data source, the total number of formatable logical blocks, and the block capacity. In some implementations of the tenth aspect, the descriptor instruction set includes at least one of a first standard instruction set, a first special instruction set, and a setting instruction set, where the first standard instruction set is used to send an instruction to the target device to request descriptor data of the target device; the special instruction set is used to obtain data of the device type to which the target device belongs; and the setting instruction set is used to send a setting instruction, where the setting instruction includes at least one of instructions such as setting an address, enabling a configuration, enabling an endpoint, or starting a peripheral module. In some implementations of the tenth aspect, if the networking device is set to the host mode, establishing a communication connection with the target device based on the descriptor instruction set includes: sending a handshake connection request to the target device; obtaining descriptor data of the target device according to the first standard instruction set; obtaining data of the target device according to the special instruction set; obtaining at least one of the status of the setting address of the target device, the status of enabling configuration, the status of enabling endpoints, and the status of starting a peripheral module according to the setting instruction set; if it is determined that at least one of the descriptor data of the target device, the data of the target device, the status of the setting address of the target device, the status of enabling configuration, the status of enabling endpoints, or the status of starting a peripheral module does not meet the conditions specified by the first access status judgment rule, determining that the handshake connection fails and sending the descriptor data of the target device to the server; receiving new scenario configuration information or a new descriptor instruction set sent by the server, where the server determines the new scenario configuration information or the new descriptor instruction set according to the descriptor data of the target device; and establishing a communication connection between the networking device and the target device according to the new scenario configuration information or the new descriptor instruction set. In some implementations of the tenth aspect, if the networking device is set to the slave mode, establishing a communication connection with the target device based on the first descriptor set includes: receiving a handshake connection request sent by the target device; in response to the handshake connection request, returning the first descriptor set to the target device to enable the target device to enumerate the first descriptor set; if the handshake connection request meets the preset device requirements, determining that the handshake connection is successful; if the handshake connection request does not meet the preset device requirements, determining that the handshake connection fails, sending the handshake connection request data to the server, downloading the corresponding fourth descriptor set from the server, and re-enumerating based on the descriptors in the fourth descriptor set. In some implementations of the tenth aspect, the first descriptor set includes at least one of a standard data set, a special data set, and an execution setting instruction. Among them, the standard data set is used to return descriptor data according to the type and parameters of the standard instruction when the target device sends a standard instruction; the special data set is used to return data according to the type and parameters of the special instruction and the type of the networking device when the target device sends a special instruction; and the execution setting instruction is used to set at least one of the networking device address, enabling configuration, enabling endpoints, and starting a peripheral module when the target device sends a setting instruction. In some implementations of the tenth aspect, if the networking device is set to the slave mode, establishing a communication connection with a target device based on the first descriptor set includes: receiving a handshake connection request sent by the target device; receiving at least one of a standard instruction, a special instruction, or a setting instruction sent by the target device; if at least one of the standard instruction, the special instruction, or the setting instruction does not meet the conditions specified by the second access status judgment rule, determining that the handshake connection fails, and sending the descriptor instruction of the target device to the server; receiving new scenario configuration information or a new first descriptor set sent by the server, where the server determines the new scenario configuration information or the new first descriptor set based on the descriptor instruction of the target device; and establishing a communication connection between the networking device and the target device according to the new scenario configuration information or the new first descriptor set. In some implementations of the tenth aspect, the first descriptor set includes at least one of a device descriptor, a configuration descriptor, an interface descriptor, an endpoint descriptor, a string descriptor, a BOS descriptor, and a preset custom descriptor. In some implementations of the tenth aspect, if the networking device is set to the peer-to-peer communication mode, establishing a communication connection with a target device based on the configuration information includes: configuring a first interface of the networking device as a sending end, and sending data to the target device through the first interface; configuring a second interface of the networking device as a receiving end, and receiving data sent by the target device through the second interface. In some implementations of the tenth aspect, the configuration information includes at least one of a third mode, a third interface type, an interaction data set, a third status judgment rule, and a third status response rule, where the third mode is used to set the working mode of the networking device to the peer-to-peer mode; the third interface type is used to set the first interface as the sending end and the second interface as the receiving end; the interaction data set is used to set the data sent by the networking device to the target device; the third status judgment rule is used to judge the access success status or the access failure rule of the networking device by the data sent by the target device; and the third status response rule is used to make a response according to the access status of the networking device. In some implementations of the tenth aspect, the target device includes at least one first target device and at least one second target device. The networking device serves as a host device communicatively connected to the at least one first target device and as a slave device communicatively connected to the at least one second target device. Establishing a communication connection with the target device based on the target scenario descriptor information includes: enumerating various descriptors in the second descriptor set of the at least one first target device based on the descriptor instruction set of the function instruction set; if the handshake connection with various descriptors in the second descriptor set is successful, configuring a first target data source when the networking device communicates with the at least one first target device to complete the communication connection between the networking device and the at least one first target device; receiving a handshake connection request sent by the at least one second target device; in response to the handshake connection request, returning the first descriptor set to the at least one second target device, so that the at least one second target device enumerates the first descriptor set, and after the handshake connection with the first descriptor set is successful, configuring a second target data source when the networking device communicates with the at least one second target device according to the data source configuration information. In an eleventh aspect, the present application provides a data exchange method applied to a networking device. The networking device establishes a communication connection with a server and a target device based on the above device access method. The method includes: obtaining a data exchange request sent by a first target party; responding to the data exchange request based on a preset processing policy and returning target data to the first target party, where the target data is data sent by a second target party. If the first target party is the server, the second target party is the target device; if the first target party is the target device, the second target party is the server. In some implementations of the eleventh aspect, the target device includes at least one first target device and at least one second target device. The networking device serves as a host device communicatively connected to the first target device and as a slave device communicatively connected to the second target device. If the first target party is the server, the second target party is the first target device or the second target device; if the first target party is the second target device, the second target party is the server or the first target device. In some implementations of the eleventh aspect, responding to the data exchange request based on a preset processing policy and returning target data to the first target party includes: in response to the data exchange request, forwarding the data exchange request to the second target party; receiving the target data returned by the second target party in response to the data exchange request and forwarding the target data to the first target party. In a twelfth aspect, the present application provides a data exchange method, which is applied to a networking device. The networking device establishes a communication connection with a target device based on the above device access method. The method includes: determining a target data source according to the data source configuration information in the scenario configuration information; and implementing data interaction between the networking device and the target device based on the target data source. In some implementation manners of the twelfth aspect, the data source configuration information includes capacity information of the data source, a storage medium, and a read / write state. The capacity information includes at least one of a last logical block address of the data source, a total number of formatable logical blocks, or a block capacity. In some implementation manners of the twelfth aspect, the target data source is disposed in the target device, or the networking device, or the server, or a client connected to the server, or any electronic device communicatively connected to the networking device. In some implementation manners of the twelfth aspect, implementing data interaction between the networking device and the target device based on the target data source includes: configuring an automatic running script when the networking device communicates with the target device, where the scenario configuration information includes the automatic running script; sending a first data exchange request to the target device based on the automatic running script, and receiving first data sent by the target device in response to the first data exchange request; or receiving a second data exchange request sent by the target device based on the automatic running script, and sending second data to the target device in response to the second data exchange request, where the first data or the second data is data in the target data source. In some implementation manners of the twelfth aspect, receiving the data sent by the target device in response to the first data exchange request further includes: sending the data sent by the target device to the server, where the server represents all electronic devices communicatively connected to the networking device and capable of configuring the configuration information. In some implementation manners of the twelfth aspect, the method further includes: receiving a first low-level instruction sent by the server, where the first low-level instruction is sent by the client to the server, and the first low-level instruction includes an operation type, an operation storage space, an operation length, and a data packet; sending the first low-level instruction to the target device; if the operation type of the first low-level instruction is a read operation, receiving data at a first sector address returned by the target device in response to the first low-level instruction, where the target device determines the first sector address according to the operation storage space and the operation length; and if the operation type of the first low-level instruction is a write operation, writing the data in the data packet into the first sector address of the target device. In some implementations of the twelfth aspect, the method further includes: receiving a search instruction sent by the server, where the search instruction is sent by the user device to the server and includes document information; according to the search instruction, traversing and reading relevant storage space addresses (such as sector addresses) of the target device or the network device respectively to search for corresponding stored data; sending the stored data to the server so that the server sends the document data to the user device. In some implementations of the twelfth aspect, the automatic running script is an advanced instruction, and the advanced instruction includes an instruction to create a document, an instruction to delete a document, an instruction to modify file attributes, an instruction to read document content, and an instruction to modify document content. In a thirteenth aspect, the present application further provides a device access method applied to a server. The method includes: when communicating and connecting with a network device, sending target configuration information to the network device, where the target configuration information is used for the network device to establish a communication connection with a target device, and the target configuration information includes scenario configuration information of the network device in at least one application scenario, and the scenario configuration information includes at least one of a first descriptor set and a descriptor instruction set, and the first descriptor set is used to define the device type of the network device; the scenario configuration information stored in the server is: before preloading the target configuration information, based on a preset generation strategy, by configuring at least one of the first descriptor set and the descriptor instruction set of the network device, and data source configuration information; based on the target scenario configuration information, establishing a communication connection with the target device so that the network device is connected to the target device, and the target scenario configuration information is one of the scenario configuration information. In some implementations of the thirteenth aspect, the sending the target configuration information to the network device includes: receiving a scenario information acquisition request sent by the network device, in response to the scenario information acquisition request, screening out scenario configuration information that matches the identity identifier of the network device in the scenario information acquisition request from the scenario configuration information; sending the scenario configuration information to the network device. In some implementations of the thirteenth aspect, the method further includes: receiving a descriptor set of the target device sent by the network device, where the descriptor set is received by the network device from the target device; the server determines new scenario configuration information according to the descriptor set of the target device and sends the new scenario configuration information to the network device so that the network device establishes a communication connection between the network device and the target device according to the new scenario configuration information. In a fourteenth aspect, the present application further provides a data exchange method, which is applied to a server. The server establishes a communication connection with an Internet-connected device based on the above device access method. The method includes: sending a data exchange request to the Internet-connected device and receiving target data returned by the Internet-connected device. The data exchange request is used for the Internet-connected device to respond to the data exchange request based on a preset processing strategy, and the target data is data sent by a target device; and / or, sending target data to the Internet-connected device according to the data exchange request responded by the Internet-connected device based on the preset processing strategy. The target data is returned by the Internet-connected device to the target device, and the data exchange request is initiated by the target device. In some implementation manners of the fourteenth aspect, the method further includes: receiving a read operation instruction sent by the Internet-connected device, determining data from a data source of the server according to the read operation instruction, and sending the determined data to the Internet-connected device; or receiving a write operation instruction and a write data packet sent by the Internet-connected device, and writing the write data packet into the data source of the server according to the write operation instruction. In a fifteenth aspect, the present application further provides a server, which includes a processor and a memory. The server can implement the above device access method or the above data exchange method. In a sixteenth aspect, the present application further provides a data exchange device, which is applied to an Internet-connected device. The Internet-connected device establishes a communication connection with a server and a target device based on the above device access method. The device includes: an acquisition module, configured to acquire a data exchange request sent by a first target party; and a response module, configured to respond to the data exchange request based on a preset processing strategy and return target data to the first target party. The target data is data sent by a second target party. If the first target party is the server, the second target party is the target device; if the first target party is the target device, the second target party is the server. In a seventeenth aspect, the present application further provides an Internet-connected device, which includes a processor and a memory. The memory is used to store a computer program, and when the computer program is executed by the processor, the above device access method or the above data exchange method is implemented. In an eighteenth aspect, the present application further provides a computer-readable storage medium, which stores a computer program, and when the computer program is executed by a processor, the above device access method or the above data exchange method is implemented. This application configures the scenario configuration information of the networking device and preloads the scenario configuration information. The scenario configuration information includes at least one of the first descriptor set and the descriptor instruction set. The first descriptor set is used to define the device type of the networking device, so that the device function of the networking device can be redefined according to the target configuration information, making the device function more abundant. In addition, this application also stores the preset configuration information on the server for easy real-time monitoring. When the networking device is lost, the communication connection with the networking device can be disconnected on the server to ensure the security of the data source of the networking device. Finally, based on the scenario configuration information, a communication connection with the target device is established so that the networking device can be connected to the target device. In this way, by obtaining the configuration information from the server and establishing a communication connection with the target device, it can effectively avoid being captured by the computer host and revealing the real data source and network communication data, and effectively avoid being cracked by malicious programs, ensuring the device security of the networking device. The following will clearly and completely describe the technical solutions in the embodiments of the present application with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the scope of protection of the present application. As described in the related art, the device functions of some access devices are fixed at the time of factory production and cannot be changed after leaving the factory or can only be changed by rewriting the software. For example, a USB flash drive is stipulated to be used only as a storage device at the time of factory production. In subsequent applications, the USB flash drive can only store data in the local storage area. Some access devices have multiple device functions that can be switched, but these functions are preset before leaving the factory, so that the access device can only switch between fixed functions and cannot be changed after leaving the factory. In addition, the number of access interfaces of some access devices is relatively small, making it difficult to meet the requirements of multiple functional scenarios. For example, the number of USB communication interfaces of in-vehicle devices is limited (usually 1), and it can generally only be used as a function of reading USB flash drives. In addition, due to the complex actual application situation of the access device, in the case of hardware incompatibility such as the new model of the device not being adapted or the adaptation data of a specific model being omitted at the time of factory production, the target device may not be able to recognize the access information of the access device, resulting in the failure of the access device to access and increasing the error correction cost of the access device. For example, when the access device (at this time, the access device is a slave device) fails to access the host device or the access device (at this time, the access device is the host device) fails to access the slave device, the receiving device needs to be recycled and the hardware needs to be updated again, resulting in resource waste or cost increase. In addition, the data related to the functions or applications of the device is stored locally on the device, which is not conducive to the confidentiality or protection of the data. If the device is lost, the data in the device is also lost. Since the data is stored locally on the device, such as software and drivers with important functions, even under the protection of antivirus software, the data is easily reverse-cracked. And when the device needs to be connected for application expansion, control software such as drivers needs to be installed in the computer host, which makes it easy to be packet-captured by the computer host, thus exposing the real data source and network communication data, and may also cause the connected device to be cracked by malicious programs, posing a relatively high security risk. The above problems lead to the single function of the device on the one hand, the increase in error correction cost on the other hand, and the inability to guarantee the data security of local data when connecting to the computer host on the third hand. Before introducing the embodiments of the present application, some technical terms in this article will be briefly explained. 1. Communication rules between the host and the slave. It is divided into the host mode and the slave mode. The host actively sends data interaction instructions to the slave, and the slave makes a passive response according to the data interaction instructions. Taking the USB communication rules as an example, USB is divided into a host (such as a computer host) and a slave (such as a USB flash drive). The host sends a token packet (or a token packet + a data packet) to the endpoint of the slave, and the slave makes a response according to the token packet (or the token packet + the data packet) received at the endpoint. The token packet includes but is not limited to: SETUP token packet: used for the host to send a data packet request, execute settings, or send a data packet to the slave; IN token packet: used for the host to request a data packet from the slave. The slave returns a data packet and an ACK status packet; if the slave cannot return the corresponding data packet, it returns a NAK status packet; OUT token packet: used for the host to send a data packet to the slave, and the data packet to be sent is attached. The slave device receives the data packet and returns status packets such as ACK and NYET; if the slave device cannot receive the data packet, it returns a NAK status packet or a STALL status packet, etc. In some cases, before the host sends an OUT token packet, it first sends a PING token packet to test whether the slave device has the ability to receive data packets. In addition, taking USB as an example, the token packet also includes SOF token packets, etc., and other status packets will not be elaborated. 2. Regarding the principle of enumeration (or establishing a handshake connection). For a host device, enumeration (or establishing a handshake connection) is a process of reading the communication parameters of a slave device to further achieve data exchange. Taking the USB mass storage device type as an example: First, read basic parameters such as the slave descriptor, including the parameters of the hardware descriptor, configuration descriptor, port descriptor, and endpoint descriptor, and load the driver information according to different parameters to enable the hardware to connect and communicate, such as obtaining relevant information about the endpoint. Second, read the parameters of the removable storage device, such as the capacity size, whether it is read-only, etc.; Third, read the file system information so that it can display the disk drive letter on the computer operating system. However, during the use of this application, it does not necessarily strictly follow the enumeration process of the operating system, but it must read the necessary data for the enumeration of the removable storage device. For this reason, an embodiment of this application provides a device access method, which configures the configuration information of the networking device based on a preset generation strategy. The configuration information includes the scenario configuration information of the networking device in at least one application scenario. The scenario configuration information includes at least one of a first descriptor set and a function instruction set, and data source configuration information. The first descriptor set is used to define the device type of the networking device, and the function instruction set includes a descriptor instruction set; preload the scenario configuration information; based on the loaded scenario configuration information, establish a communication connection between the networking device and the target device, so that the networking device can be accessed to the target device. Optionally, the configuration information is stored in the networking device, or the server, or the user terminal. An embodiment of this application provides a device access method, which configures the target configuration information of the networking device based on a preset generation strategy. The target configuration information includes the scenario configuration information of the networking device in at least one application scenario. The scenario configuration information includes at least one of a first descriptor set and a function instruction set, and data source configuration information. The first descriptor set is used to define the device type of the networking device, and the function instruction set includes a descriptor instruction set. The descriptor instruction set is used to control the data exchange between the networking device and the target device; when the networking device communicates with the server, preload the target configuration information; at the same time, store the target configuration information by the server to facilitate real-time monitoring of the networking device. When the networking device is lost, the communication connection with the networking device can be disconnected at the server to ensure the security of the data source of the networking device; based on at least one of the loaded first descriptor set and function instruction set, and the data source configuration information, establish a communication connection between the networking device and the target device, so that the networking device can be accessed to the target device. An embodiment of the present application provides a device access method. When communicating and connecting with a server, target configuration information is pre-loaded. The server stores multiple preset configuration information, and the target configuration information is one of the multiple preset configuration information. The target configuration information includes scenario configuration information of the network device in at least one application scenario. The scenario configuration information includes at least one of a first descriptor set and a descriptor instruction set. The first descriptor set is used to define the device type of the network device. Based on the target scenario configuration information, a communication connection is established with the target device to enable the network device to access the target device. The target scenario configuration information is one of the scenario configuration information. Please refer to FIG. 1. FIG. 1 is a flowchart of a device access method provided by an embodiment of the present application. The method of the embodiment of the present application can be applied to network devices, including but not limited to devices such as a microcontroller or an embedded device with networking capabilities, terminal devices such as smartphones or laptops, in-vehicle terminal devices, in-vehicle entertainment terminals, network USB key devices (such as bank U shields, digital certificates, dongles, etc.), network proxy control devices (such as multi-port repeaters), remote controllers (including but not limited to network read-write control devices, network controllers (such as routers and smart gateways, etc.)), communication device class devices (Communication Device Class, CDC, such as network cards, modems, ISDN (Integrated Services Digital Network) terminals), human interface device class devices (Human Interface Device, HID, such as keyboards or mice), mass storage device class devices (Mass Storage Device Class, MSC, such as USB flash drives, network USB flash drives, card readers, network card readers), printer device class devices (Printer device, such as a printer with a USB interface), still imaging device class devices, video device class devices, audio / video device class devices, smart card class devices, universal serial bus hub class devices (Universal Serial Bus Hub), and custom class devices, etc. In an embodiment of the present application, the networked device is communicatively connected to the server via a wired or wireless network (such as an Ethernet interface like twisted pair or optical fiber, a WIFI hotspot, ultra-wideband UWB, Bluetooth, a 4G or 5G mobile cellular network, LoRa long-distance radio, etc.). The server includes but is not limited to a personal computer, a mobile phone, a mobile terminal, a laptop computer, an embedded computer, a physical server, a virtual server, a server cluster, and a cloud server. During the networking process between the networked device and the server, a virtual private network can be further set up, or a network dedicated line can be used to enhance network security. In an embodiment of the present application, the server is a control terminal. The control terminal includes the server or the user terminal. The user terminal is communicatively connected to the networked device. For example, the user terminal directly connects to the networked device via a P2P communication method, and the communication data between the user terminal and the networked device does not pass through the server for forwarding, which can improve the transmission efficiency during the data exchange process. In an embodiment of the present application, the control terminal is located locally to the networked device and is connected to the networked device via a near-field communication method such as Bluetooth. In an embodiment of the present application, the control terminal is located locally to the networked device and is connected to the networked device via a near-field communication method such as Bluetooth, and has functions such as creating a scenario, issuing a scenario, and controlling data exchange. In another embodiment of the present application, the control terminal can also be located remotely from the networked device and communicate remotely via a TCP / IP network, etc. In another embodiment of the present application, on the one hand, the control terminal can be used as a user terminal to directly connect to the networked device, and on the other hand, the control terminal has the functions of the server, such as creating a scenario, issuing a scenario, and controlling data exchange. In the embodiment of the present application, a scenario can be created by the server or the networked device. Referring to FIG. 2, it is a schematic structural diagram of a networked device in an embodiment of the present application. The networked device includes but is not limited to a networking unit 201, a storage unit 202, an interaction unit 203, a first interface 204, a second interface 205, and a main control module (not shown in the figure). The networking unit 201 is used to communicate with the server, the interaction unit 203 is used to interact with the user, and the first interface 204 and the second interface 205 are used to establish a communication connection with the target device. The first interface 204 can enable the networked device to be used as a slave device alone to connect to the target device (host), and the second interface can enable the networked device to be used as a host device alone to connect to the target device (slave). The first interface and the second interface can also enable the networked device to be used as both a host device and a slave device to access different target devices respectively. For example, the first interface is communicatively connected to a computer device acting as a host, and the second interface is communicatively connected to a storage device acting as a slave to achieve communication connections among the computer device, the networked device (and the server), and the storage device. In an embodiment of the present application, the networking unit 201 includes, but is not limited to, Ethernet interface units such as twisted pairs or optical fibers for implementing the above-mentioned wired connection, and WIFI units, Bluetooth units, UWB units, 4G or 5G communication units, LoRa long-distance radio communication units, etc. for implementing the above-mentioned wireless connection. The interaction unit 203 includes a display unit, buttons, switches or slide switches. The display unit can be a display screen or a touch screen. The main control module includes at least one of a microcontroller unit (MCU) chip and a host. In an embodiment of the present application, the first interface 204 or the second interface 205 can be at least one of interfaces such as a USB interface, an HDMI interface, a SCSI interface, an IEEE1394 interface, a SATA interface, an eMMC interface, an SDIO interface, an M.2 interface, and a serial communication interface. It should be noted that devices connected to the "networking device" can all be used as "target devices". Both the "networking device" and the "target device" can be a host or a slave, or can be used as peer-to-peer communication devices. A peer-to-peer communication device refers to a communication device that does not distinguish between a host and a slave. When the networking device is used as a peer-to-peer communication device, the networking device receives data sent by the target device at the first interface (the first interface is the receiving endpoint), and sends data to the target device at the second interface (the second interface is the sending endpoint). Similarly, when the target device is used as a peer-to-peer communication device, the target device receives data sent by the networking device at the receiving endpoint and sends data to the networking device at the sending endpoint. In an embodiment of the present application, a user or a device manufacturer can pre-configure the scenario configuration information of the networking device on the server. Before the networking device accesses the target device, it reads the first descriptor set corresponding to the scenario configuration information from the server, sets physical communication interfaces such as the first interface and the second interface of the networking device to the host mode, the slave mode, or the peer-to-peer communication mode according to the first descriptor set, and accesses the target device, thereby establishing a connection relationship with the target device and performing data exchange. In an embodiment of the present application, when the networking device is in the slave mode, data required for communication between the networking device (such as the networking device acting as a USB flash drive) and the computer host can be stored in the server. When the networking device is in the host mode, communication protocols and other data between the networking device and the target device (such as the target device being a USB flash drive) can be stored in the server. After being powered on, the networking device obtains access data such as the required first descriptor set from the server to complete the access to the target device and data exchange. It should be noted that the "host" or "host mode" described in the embodiments of the present application represents a relative identity relationship of a device A as a host when it is relative to another device B, which does not mean that device A can only be the "host" or "host mode". It can also be a "slave" or "slave mode" relative to yet another device C. Similarly, the "slave" or "slave mode" described in the embodiments of the present application represents a relative identity relationship of a device A as a slave when it is relative to another device B, which will not be elaborated here. In an embodiment of the present application, the display unit displays multiple scenarios preset by the user and can provide the user with the option to switch to different device access scenarios, where "*" represents the currently selected scenario. The networked device receives the scenario selected by the user and sends a configuration request to the server or the user terminal communicating with the server, where the configuration request includes the selected scenario. The server or the user terminal obtains the scenario configuration information matching the configuration request and sends the scenario configuration information to the networked device through the server communicating with the networked device or the user terminal communicating with the server. The networked device sets the device functions of the networked device according to the scenario configuration information. For example, when selecting a scenario of USB flash drive - 64G, USB flash drive - 1024G, or USB flash drive - 16G, the networked device is in the form of a network USB flash drive. The available storage spaces of the USB flash drives are 64G, 1024G, and 16G respectively, and the stored data is different. The corresponding formatted file systems are FAT32, ExFat, or CDFS, which are used to store work materials, multimedia materials, or operating system boot loaders respectively. When selecting the digital certificate scenario, the networked device is in the form of a USBkey and can be used for identity authentication. For example, when communicating with a computer host, when the computer host needs to log in to the business system, the computer host is authenticated proximally or remotely through the USBkey. When selecting the proxy mode scenario, the networked device is in the form of a network proxy control and can virtualize the devices connected to the interface to the server or the control end. When selecting the general read-write control mode, the networked device is in the form of a network read-write control device and can perform read-write and other controls on the devices connected to the second interface according to the server instructions or preset rules. When selecting the audio enhancement mode, the networked device is in the form of a network intermediate control device. The first interface is connected to the computer host, and the second interface is connected to the audio playback device. The audio data sent by the computer host can be immediately sent to the server for calculation, or the enhanced script model can be downloaded from the server to process the data on the networked device, and the processed audio data is sent to the audio playback device for audio playback. Specifically, after the user selects a scenario from "USB flash drive - 64G, USB flash drive - 1024G, USB flash drive - 16G, digital certificate, general read / write control mode, proxy mode, general read / write control mode, audio enhancement mode" through the display unit, the networked device receives the scenario selected by the user and sends a configuration request including the scenario to the server or the user terminal communicatively connected to the server. The server or the user terminal obtains the configuration information of the selected scenario, and sends the scenario configuration information of the corresponding scenario to the networked device through the server communicatively connected to the networked device or the user terminal communicatively connected to the server. The networked device sets the device function of the networked device to the function or data source of the selected scenario (such as different data sources in the form of a USB flash drive) according to the scenario configuration information. It should be understood that in other embodiments, the networked device further includes more or fewer components. For example, in the case where the network USB flash drive only has a first interface and no second interface, if the first interface is a male port and is used as the interface when acting as a slave device, then when it is necessary to act as a master device, the male port is converted into a female port through an interface converter to be used as the interface when acting as a master device. Another example is that the networked device includes multiple first interfaces or second interfaces to simultaneously access multiple master devices or slave devices. The networked device may also not require a display unit, and the operation of switching scenarios is completed on the server, or the networked device is controlled by using other terminals through means such as Wi-Fi, Bluetooth, NFC, mobile cellular network (such as 4G, 5G communication) or satellite network. The display unit may also include more or fewer scenarios, which will not be elaborated here. In an embodiment of the present application, the networked device is connected to the control end through the networking unit 201. The control end can be used as a server or a combined device of the server and the user terminal. Exemplarily, FIGS. 3A to 3F show schematic diagrams of the interaction between the networked device and the control end. The control end can be a mobile terminal, a desktop computer or a server (cloud server), etc. The control end pre-creates, edits, configures or imports scenarios (or further selects scenarios) based on the server (such as a cloud server) or the control end itself. The control end can have all permissions or can control permissions. For example, user A (desktop display) has the permission to generate scenarios for scenario creation / configuration / import and can create or edit scenarios; user B (mobile terminal) has the permission to select scenarios and can select according to the scenarios created or edited by user A. When the networked device obtains the scenario information of the cloud server (such as through remote communication) or the control end (such as through near-field communication) (or further obtains the selected scenario information) and enables the access scenario of the corresponding networked device according to the configuration. The networked device can have the permission to select scenarios; it can also not have the permission to select scenarios, and the control end makes a preset selection of scenarios. Exemplarily, FIGS. 3A and 3B show schematic diagrams of the networking device interacting with the control terminal as a portable device. The networking device in FIG. 3A has a display screen and a second interface 205. The scene information obtained through a cloud server (such as remote communication) or the control terminal (such as near-field communication) (or further obtaining the scene corresponding to the selected interface) can enable the selected scene according to the scene list on the display screen; or the networking device in FIG. 3B does not have a display screen but has a second interface 205. By means of a sliding switch, the enabled scene can be selected according to the sequence number of the scene, etc., and different scenes (functions) of a single device can be switched according to the sequence number of the scene. FIG. 3C shows a schematic diagram of the networking device interacting with the control terminal as a mobile terminal, and it can receive or select scene information from the server, or can also create, edit, or import scene information locally on the mobile terminal; FIG. 3D shows a schematic diagram of the networking device interacting with the control terminal as a smart wearable device (such as a smart watch), and it can receive or select scene information from the server. The networking devices shown in FIGS. 3C and 3D include a second interface 205. Further, based on the second interface 205, the networking device realizes the conversion between a mobile phone line (such as a TYPE-C interface) and a USB male port (in slave mode, male head) or a female port (in host mode, female head) through a data line or an interface conversion line. Exemplarily, FIG. 3E shows a schematic diagram of the networking device interacting with the control terminal as a vehicle terminal. The networking device has a display screen and a second interface 205. By obtaining the scene information of a cloud server (such as remote communication) or the control terminal (such as near-field communication) (or further obtaining the scene corresponding to the selected interface), different scene (function) expansions can be selected according to the scene list on the display screen, effectively solving the problem of function expansion in the case of limited interface quantity. For example, the USB interface of the vehicle device can be used as a host device to access devices such as a USB flash drive and a camera, and the data can be stored in the local storage area of the device, the control terminal, or the cloud server; or as a slave device (such as a USB flash drive device, etc.) to connect to a laptop, etc., and the data stored in the interaction can be stored locally on the vehicle device or on the network. Exemplarily, FIG. 3F shows a schematic diagram of the networking device interacting with the control terminal as a multi-peripheral device. The networking device has multiple second interfaces 205, and scenes are respectively pre-created, configured, or imported according to different interfaces, or further selected scenes. The networking device obtains the scene information of a cloud server (such as remote communication) or the control terminal (such as near-field communication), or further obtains the scene corresponding to the selected interface, and enables the scene corresponding to the interface of the networking device according to the configuration. In addition, each interface can also select the enabled scene according to the sequence number of the scene, etc., by means of a sliding switch. Different scenes (functions) of multiple interfaces of a single device can be switched. It should be noted that in the above FIGS. 3A - 3F, there may also be a networking unit 201 as shown in FIG. 2, which will not be elaborated here. As shown in FIG. 1, the device access method of this embodiment includes the following steps. Step S101, configure the target configuration information of the networking device based on a preset generation policy, where the target configuration information includes the scenario configuration information of the networking device in at least one scenario, and the scenario configuration information includes at least one of a first descriptor set and a descriptor instruction set, and data source configuration information. The first descriptor set is used to define the device type of the networking device. In this step, the scenario configuration information is the configuration information that defines the device type (or device function) of the networking device, which includes but is not limited to descriptor sets, descriptor instruction sets, data source configuration information, device roles, etc. Descriptor sets include but are not limited to device descriptors, configuration descriptors, interface descriptors, endpoint descriptors, string descriptors, BOS descriptors, and custom descriptors, etc. The descriptor instruction set is the instruction set for implementing the host function of the networking device, which includes various function instruction sets. The function instruction sets include but are not limited to acquisition instruction sets, verification instruction sets, data source instruction sets, interaction instruction sets, and custom instruction sets. The acquisition instruction set is used to acquire descriptor sets, the verification instruction set is used to verify various descriptors in the descriptor set, the data source instruction set is used to acquire configuration parameters such as data source configuration information, and the interaction instruction set is used to implement data interaction between the networking device and other devices, which includes but is not limited to read instructions, write instructions, create instructions, modify instructions, delete instructions, and set instructions, etc. The custom instruction set is used to define the desired functions of the networking device. Device roles include host roles, slave roles, and / or peer roles. When the networking device is used as a host device, the device role is the host role. When the networking device is used as a slave device, the device role is the slave role. When the networking device is used as a peer communication device, the device role is the peer role. As shown in FIG. 4, it is an architecture diagram for configuring the target configuration information of the networking device in an embodiment of this application. In an embodiment of this application, the scenario configuration information is configured by a server communicatively connected to the networking device and a client communicatively connected to the server. The preset generation policy includes at least one of a custom creation policy, a template creation policy, or an external import creation policy. In an embodiment of this application, when the preset generation policy is a custom creation policy, the client creates the scenario configuration information and sends the scenario configuration information to the server. The networking device determines a scenario and sends a request to obtain the scenario to the server. The server sends the scenario configuration information corresponding to the scenario to the networking device according to the request to obtain the scenario sent by the networking device. Optionally, when the default generation strategy is a custom creation strategy, based on the device role of the network device selected by the user, configure the first descriptor set of the network device and the data source configuration information. Exemplarily, if the device role of the network device is selected as the host role (i.e., the host for communicating and connecting with the target device), configure the function instruction set for host enumeration, such as the acquisition instruction set, verification instruction set, setting instruction set, interaction instruction set, data source instruction set, and custom instruction set, and configure the data source configuration information to bind the data source during the data exchange process between the network device and the target device. The data source includes, but is not limited to, mirror storage documents, specific folders, databases, data flows, etc. If the device role of the network device is selected as the slave role (i.e., the slave for communicating and connecting with the target device), then configure the descriptor parameters, device type parameters, and data source configuration information for replying to the host. If the device role of the network device is selected as the peer role, then configure the device exchange configuration information. Configuring the device exchange configuration information includes configuring the data sending end or data receiving end of the network device. For example, configure interface 1 of the network device as the data sending end and configure interface 2 of the network device as the receiving end. In an embodiment of the present application, when the default generation strategy is a template creation strategy, based on the default scenario template, configure at least one of the first descriptor set and descriptor instruction set of the network device, and the data source configuration information. Exemplarily, if the application scenario is that the network device is a slave device (such as a large storage device, audio-visual, etc.), then based on the default scenario template corresponding to the application scenario, configure the manufacturer, identification information, string information, etc. in the descriptor, and configure the data source configuration information. In an embodiment of the present application, when the default generation strategy is an external import creation strategy, based on the imported scenario template, configure at least one of the first descriptor set and descriptor instruction set of the network device, and the data source configuration information; or based on the imported scenario information, configure the data source configuration information. It should be noted that in this embodiment, by creating configuration information corresponding to different application scenarios or device roles (device modes), the network device can be applied to multiple application scenarios, improving the applicability of the network device. In an embodiment of the present application, the user can select a scenario on the display unit of the network device. The scenarios include, but are not limited to, the USB flash drive scenario, USB key scenario, network proxy control scenario, and network intermediate control scenario. In an embodiment of the present application, the scenario type can be a single device, such as a large storage device scenario like a USB flash drive; or multiple scenarios such as a USB flash drive and a camera can be simultaneously connected to the target device. For example, a combination of multiple scenarios (USB flash drive scenario + camera scenario) is connected. In an embodiment of the present application, the device corresponding to a single scenario can be a single device, such as a single USB flash drive connected to the target device; it can also be a device of a composite device type such as a USB flash drive and a camera connected to the target device at the same time; it can also be a device with multiple functions (such as a USB flash drive and a camera) selectively connected to the target device. In an embodiment of the present application, when creating scenario configuration information, at least one of the first descriptor set and descriptor instruction set of the network device, and data source configuration information can be configured based on the device role of the network device. Exemplarily, if the device role of the network device is a host (for example, a host communicating with the target device), a descriptor instruction set for the host to enumerate slaves is configured, and / or data source configuration information for data exchange between the host and the slave is configured. The data source configuration information is used to bind the data source during the data exchange process between the network device and the target device, and the data source includes but is not limited to storage media, storage space address intervals (such as sector address intervals), mirrored storage documents, specific folders, databases, and data flows, etc. In an embodiment of the present application, the scenario configuration information further includes scenario basic information and scenario switching strategies. The scenario basic information includes one or more of a scenario identifier and a scenario name. The scenario identifier is used to represent the unique identity of the scenario, for example, the unique identity can be the unique ID value of the scenario. The scenario name is used to represent the name of the scenario, for example, the scenario name can be "USB flash drive (work)", "USB flash drive (life)", etc. The scenario switching strategy is used to represent the strategy for the network device to select or switch scenarios. The scenario switching strategy at least includes a manual operation selection strategy, an automatic operation selection strategy, an allowed or prohibited selection strategy, an allowed or prohibited access strategy, and an interface selection strategy. In an embodiment of the present application, the manual operation selection strategy represents that the user selects the scenario of the network device at the user side, or the server side, or the network device, or the control side, or the interactive interface or physical interaction control item of the target device. For example, the user selects the scenario on the interface of the application or the browser of the web page at the user side. Optionally, after the network device establishes a connection with the target device, the network device can transmit scenario information to the target device by means of data exchange, and the target device selects the scenario of the network device. Optionally, after the network device establishes a connection with the target device, the network device can receive the scenario information transmitted by the target device by means of data exchange, and the scenario of the network device is selected by the target device, or the network device, or the server side, or the user side, etc. In another embodiment of the present application, the manual operation selection strategy represents that the user selects a scenario in the interaction space of the network device. For example, the user selects a scenario by means of buttons, switches or slide switches of the network device. Optionally, the scenario can be selected on the display unit of the network device. Exemplarily, the network device is provided with a display unit, and options for the user to select application scenarios are displayed on the display unit. Based on the user's selection operation, the application scenario is determined so that when the network device communicates with the server, the scenario configuration information based on the user's selection is preloaded. Similarly, the selection process on the network device can be an immediate process or a non-immediate process. Optionally, the preset application scenario can also be selected on the physical switch of the network device. Exemplarily, the network device is provided with a physical switch, and the scenario corresponding to the current switch indicator is selected by toggling the physical switch so that when the network device communicates with the server, the scenario configuration information based on the user's selection is preloaded. The automatic operation selection strategy represents the rules for presetting the selected scenario, and the scenario is automatically selected when the user terminal, the server, the network device or the target device meets the preset rules for the selected scenario. The rule for presetting the selected scenario is to select the scenario according to the timing clock. For example, when the local timing clock or the network timing clock of the user terminal, the server or the network device conforms to the preset clock, the corresponding scenario is selected. In an embodiment of the present application, the scenario is selected according to the data of the peripheral module of the user terminal, the server or the network device. For example, when the location information of the location module (such as GPS positioning module, Beidou positioning module) of the network device conforms to the first preset location, or the signals of communication modules such as Wi-Fi and Bluetooth of the network device conform to the first preset conditions (such as the preset MAC address is carried or not carried in the signal), or the data of the sensor module of the network device conforms to the first preset value (for example, the temperature and humidity sensor conforms to the corresponding first preset value), or when the near field communication module (such as NFC communication module) of the network device receives a specific signal, the corresponding scenario is selected. In an embodiment of the present application, the network device automatically selects the corresponding application scenario based on the preset interaction data of the target device (such as descriptor content, descriptor instruction or data communication (or data exchange) content). The selected policy representation for allowing or prohibiting scenarios allows or prohibits scenarios of selected networking devices based on scenario basic information, access configuration, or data exchange configuration. According to the default rules of access configuration information (device descriptor, configuration descriptor, interface descriptor, endpoint descriptor, string descriptor, BOS descriptor, etc.) and data exchange configuration information, scenarios of specific hardware types are prohibited or allowed. For example, scenarios of large-capacity device types (such as USB flash drives) are prohibited. According to the default rules of peripheral module data, specific scenarios are prohibited or allowed. For example, when the location information of the location module (such as GPS, Beidou positioning, etc.) of the networking device meets the second default location, or the signals of communication modules such as Wi-Fi and Bluetooth meet the second default conditions (such as the appearance or non-appearance of a default MAC address), or the data of the sensor module of the networking device meets the second default value (for example, the temperature and humidity sensor meets the corresponding second default value), or when the NFC communication module of the networking device receives a specific signal, the corresponding scenario is allowed or prohibited. In an embodiment of the present application, the networking device allows or prohibits corresponding application scenarios based on the preset interaction data of the target device (such as the descriptor content, descriptor instruction, or data communication (or data exchange) content sent by the target device). The access policy representation for allowing or prohibiting is based on default rules and allows or prohibits the interface of the networking device from accessing the target device according to the data sent by the target device. When at least one of the descriptors (such as the vendor ID, product ID, or device type (used class, subclass, interface command set, endpoint transfer mode), descriptor instruction, or data communication content) sent by the target device meets the preset requirements, access to the target device is allowed or prohibited. For example, if the access policy for allowing or prohibiting is to prohibit large storage devices from accessing, when the networking device is in the host mode and sends a descriptor instruction, and the response data of the target device conforms to the characteristics of a large-capacity device type (such as a USB flash drive), the networking device disconnects to protect the security of the server or control end. Exemplarily, when the networking device is a network proxy control device in the host role, based on a preset script, by reading the descriptor, it determines the vendor ID, product ID, or device type (used class, subclass, interface command set, endpoint transfer mode), etc. of the access device, and only when the accessed target device meets the qualified vendor ID, product ID, or device type is remote mapping allowed to protect the security of the server or control end. The interface selection policy characterization is as follows: When a networking device has only one interface, the selected scenario is enabled by default on the only interface (such as the only interface of a USB flash drive device). When a networking device has multiple interfaces (such as multiple interfaces of a USB hub device), the selected scenario further selects at least one enabled interface from multiple interfaces. For example, if a networking device has 2 interfaces, scenario A can be selected to enable interface 1, scenario B can be selected to enable interface 2, or scenario A can be selected to enable both interface 1 and interface 2 at the same time. It should be understood that in other embodiments, the networking device may also include more or fewer components. For example, in the case where there is only a first interface and no second interface, if the first interface is a male port and is used as the interface when acting as a slave device (such as in the network USB flash drive mode), then when it is necessary to act as a host device (such as in the read / write USB flash drive mode), the male port is converted to a female port through an interface converter (such as an OTG adapter) to serve as the interface when acting as a host device. Another example is that the networking device includes multiple first interfaces or second interfaces to simultaneously access multiple host devices or slave devices. The networking device may also not require a display unit, and the operation of switching scenarios is completed on the server side, or the networking device is controlled by using other terminals through means such as Wifi, Bluetooth, NFC, etc. The display unit may also include more or fewer scenarios, which will not be elaborated here. In an embodiment of the present application, when creating scenario configuration information, if the device role of the networking device is a host role (i.e., acting as a host communicating with a target device), then the first device access configuration information is configured. The first device access configuration information includes a first mode, a first interface category type, a standard instruction set, a special instruction set, a setting instruction set, a first access status judgment rule, and a first status response rule. The first mode sets the networked device to the host mode. The first interface type is used to set the physical interface type of the networked device, such as being set to a USB interface, an HDMI interface, a SCSI interface, an IEEE 1394 interface, a SATA interface, an eMMC interface, an SDIO interface, an M.2 interface, a serial communication interface, etc. The first interface type can further bind the communication protocol instructions corresponding to the interface type, such as binding the token packets in USB (such as SETUP, IN, OUT, PING, etc.), or status packets (such as ACK, NAK, NYET, etc.), or transfer modes (such as control transfer, bulk transfer, interrupt transfer, isochronous transfer, etc.), or standard communication protocols. The first standard instruction set includes a descriptor instruction set for sending instructions to the target device (slave) (such as obtaining a device descriptor, obtaining a configuration descriptor, obtaining an interface descriptor, obtaining an endpoint descriptor, obtaining a string descriptor, obtaining a BOS descriptor, etc.), requesting the corresponding descriptor data of the slave to access the target device. The special instruction set includes an instruction set for obtaining device type data, which is used to obtain data of different device types. It should be noted that the special instruction sets corresponding to different networked devices are different. For example, the special instruction set of a USB-related flash drive (USB Mass Storage Class) includes an instruction for indicating MAXLUN to obtain the maximum logical unit number descriptor, the special instruction set of a keyboard and mouse device (Human Interface Device) includes an instruction for obtaining an HID descriptor, and the special instruction set of a camera (USB Video Class) includes an instruction for indicating GET_RES to obtain the resolution attribute descriptor, etc. The setting instruction set is used to send setting instructions. The setting instructions include at least one or more of instructions such as setting an address, enabling configuration (setting configuration), enabling an endpoint, or starting a peripheral module. The first access status judgment rule is a rule for judging whether the networked device is successfully accessed or failed by means of the data or response status (with response / or without response) returned by the target device. The data returned by the target device includes the data returned by the target device during the access stage or data exchange stage of the networked device. The first status response rule is a rule for making a response according to the access status of the networked device. For example, when it is judged that the networked device is successfully accessed, the networked device sends an access success message to the server, and the server prompts the user side that the next operation can be performed; when it is judged that the networked device access fails, an access failure message is sent to the server, a new instruction set is obtained, and the instruction is sent to the target device again. It should be noted that the above-mentioned instruction set can be at least one data exchange instruction or multiple data exchange instructions. In an embodiment of the present application, multiple preselected scenarios can be preset for automatic selection when access fails. For example, when the selected Scenario A (such as the scenario of accessing a USB flash drive) fails to access, switch to Scenario B (such as the scenario of accessing a camera device) or Scenario C (such as the scenario of accessing a keyboard device) and so on to retry the access until all preselected scenarios are tried or the access is successful. In an embodiment of the present application, the server further retrieves, compares, analyzes, and judges the returned data based on the relevant access data submitted when the networking device fails to access (such as the data returned by the target device to the networking device (such as all or part of the descriptors or relevant handshake data, etc.)), confirms the device type of the target device, and thus sends a new descriptor acquisition instruction set or selects a new scenario to the networking device so that the networking device retries to access the target device. In another embodiment of the present application, when creating scenario configuration information, if the device role of the networking device is a slave role (i.e., acting as a slave for communication connection with the target device), then configure the second device access configuration information. In an embodiment of the present application, the second device access configuration information includes a second mode, a second interface category type, a standard data set, a special data set, an execution setting instruction, a second access status judgment rule, and a second status response rule. The second mode sets the networking device to the slave mode. The second interface category type is used to set the type of the physical communication interface of the networking device, such as USB interface, HDMI interface, SCSI interface, IEEE1394 interface, SATA interface, eMMC interface, SDIO interface, M.2 interface, serial communication interface, etc. The first interface category type can further bind the communication protocol instructions corresponding to the interface category type, such as responding to token packets in USB (such as SETUP, IN, OUT, PING, etc.), or status packets (such as ACK, NAK, NYET), or transfer modes (such as control transfer, bulk transfer, interrupt transfer, isochronous transfer, etc.), or standard communication protocols, etc. The standard dataset includes the first descriptor dataset (such as device descriptor, configuration descriptor, interface descriptor, endpoint descriptor, string descriptor, BOS descriptor, etc.), which is used to return the corresponding descriptor data according to the type and parameters of the instruction sent when the target device (the target device is the host device) sends an instruction, so as to establish a communication connection with the networking device. The special dataset includes the device type special dataset (such as MAXLUN maximum logical unit number, GET_RES resolution attribute, etc.), which is used to return the corresponding data according to the type and parameters of the instruction sent by the target device, and the networking device scenario configuration or device type. The execution setup instruction is used to execute operations such as setting up the networking device, the physical communication interface of the networking device, or the peripheral module, etc. according to the type and parameters of the setup instruction sent by the target device (such as instructions for setting the address, enabling the configuration (setting the configuration), enabling the endpoint, or starting the peripheral module, etc.). The second access status judgment rule is used to judge the rule for the networking device to be successfully / unsuccessfully accessed by means of the data sent by the target device (including the data sent by the target device during the device access stage or data exchange stage), for example, the instructions for requesting a USB flash drive device and a camera device are different. The second status response rule is used to make a response according to the access (i.e., handshake or enumeration) status of the networking device. For example, when it is judged that the networking device is successfully accessed (or the handshake is successful, the enumeration is successful), send the information of successful access to the server, and the server prompts the user side that the next operation can be performed; when it is judged that the networking device is unsuccessfully accessed, send the information of unsuccessful access to the server, obtain a new dataset, and re-send a signal for establishing a connection (such as an enumerable signal) to the target device. It should be noted that the above-mentioned dataset can be the return data of at least one data exchange instruction, or the multiple return data of multiple data exchange instructions. In an embodiment of the present application, multiple preselected scenarios can be preset for automatic selection when the access fails. For example, when the selected scenario A (as a USB flash drive scenario) fails to access, switch to scenario B (as a camera device scenario) or scenario C (as a keyboard device scenario), etc. to retry the access until all the preselected scenarios are tried or the access is successful. In an embodiment of the present application, when the networking device fails to access, the server retrieves, compares, analyzes, and judges the sent instruction data based on the relevant access data submitted (such as the data sent by the target device to the networking device (such as standard instructions, special instructions, setting instructions, etc., instruction data or other relevant handshake data, etc.)), confirms the device type that the target device needs to access, and then sends a new descriptor set or selects a new scenario to the networking device, so that the networking device can retry accessing the target device. It should be noted that the interface of the networking device in the embodiment of the present application can be switched between the host mode and the slave mode after leaving the factory (such as an interface with OTG function), or can be fixed to the host mode or the slave mode (such as an interface without OTG function, designed to be fixed to the host or slave in the hardware circuit). When the interface is fixed to the host or slave mode, the corresponding scenario of the interface can only be different scenarios in the host mode or the slave mode, and there is no need to configure it in the scenario configuration. At the same time, according to the different types of the interface, it can be fixed to a specific communication protocol without configuring it in the scenario configuration. For example, when the interface is a USB interface, it is fixed to the corresponding USB protocol, etc. In another embodiment of the present application, when creating scenario configuration information, if the device role of the networking device is the peer-to-peer communication mode, the third device access configuration information is configured. The third device access configuration information includes a third mode, a third interface type, an interaction data set, a setting instruction set, a third status judgment rule, and a third status response rule. The third mode is used to set the networking device to the peer-to-peer communication mode. The second interface type is used to set the type of the physical communication interface of the networking device. The interaction data set is used to set the data sent to the target device during access. The execution setting instruction is used to execute operations such as setting the networking device, the interface of the networking device, or the peripheral module, etc., according to the type and parameters of the sent setting instruction (such as setting an address or starting a peripheral module, etc.) when the target device sends a setting instruction. The third status judgment rule is used to judge the rule for the networking device to access successfully / fail by the data sent by the target device (including the data sent by the target device during the data exchange stage). The third status response rule is used to make a response according to the access status. For example, when it is judged that the networking device has accessed successfully, send an access success message to the server, and the server prompts the user side that the next operation can be performed; when it is judged that the networking device has accessed failed, while sending an access failure message to the server, further obtain a new data sending instruction or response data set, and re-send the data to the target device / wait to receive data. In an embodiment of the present application, the scenario configuration information further includes data exchange configuration information. If the device role of the networking device is a host (for example, a host communicating with a target device), the data exchange configuration information includes a data source instruction set, a data exchange instruction set, an automatically executed instruction script, a first bound interaction system or a data source strategy, and a first allow / forbid exchange strategy. The data source instruction set is used to send instructions to the target device to obtain or set the data source information of the target device. For example, to obtain the capacity information of the target device (such as the maximum number of logical units, the total number of formatable logical blocks, the last logical block address, the block capacity, the total capacity, the available space capacity, etc.) or the read / write status (such as read-only status, write-only status, read / write status). The data exchange instruction set is used to send instructions to the target device to make the target device execute preset instructions or return data. For example, sending a write instruction and a data packet to the target device to make the target device write the data of the data packet at a specific position in its storage medium; or sending a read instruction to the target device to make the target device return the data at a specific position in its storage medium, or read the specific data of the peripheral module of the target device, or the specific data of the sensor. At least the write instruction and the read instruction include the storage space address (such as the sector address) for operating the storage medium and the quantity of the storage space to be operated (such as the number of sectors). In an embodiment of the present application, the data exchange instruction set may be a low-level instruction. The data exchange instruction includes a USB communication protocol instruction. The USB communication protocol instruction includes: sending an IN token packet to a specific endpoint (such as endpoint 1) of the target device (such as a USB device) to obtain the data returned by the target device (i.e., the IN data instruction to endpoint 1); and / or sending an OUT token packet and a data packet to a specific endpoint (such as endpoint 2) of the target device (USB device) to send data to the target device (i.e., the OUT data instruction to endpoint 2). The data exchange instruction (such as a low-level instruction) includes a Small Computer System Interface (SCSI) transparent command set instruction. The SCSI transparent command set instruction sends a read instruction to the target device (such as a USB storage device) to obtain the data at a specific sector address in the storage space of the target device; and / or sends a write instruction and a data packet to the target device (such as a USB storage device) to write data at a specific sector address in the storage space of the target device. In another embodiment of the present application, the data exchange instruction set includes an automatically executed instruction script. The automatically executed instruction script characterizes automatically sending interaction instructions (including low-level instructions, high-level instructions, etc.) to a target device according to preset script rules to achieve automated operations. The automatically executed instruction script includes an automatically executed document directory reading script. For example, after the target device (such as a storage device) is successfully connected, an automatic execution rule is triggered, and the automatically executed document directory reading script is automatically executed to read document information, convert the data of the read document information, and display it in an interaction system (such as a user interface). Specifically, the automatically executed document directory reading script automatically reads all document directory data according to the file system protocol rules. The reading rules include: first reading the boot sector data (usually the sector address 0x00) to analyze the file system boot sector address; then reading the file system boot sector data to analyze relevant parameters such as the sector address of the root folder (or the first directory) and the cluster (block) size, and then reading the root folder sector address data to analyze the document information; and then based on the document information, subdirectories, sub-documents, etc. can be analyzed. Further, the automatically executed instruction script can also include high-level instructions. The high-level instructions are operation script instructions based on multiple low-level instructions (such as read / write of USB communication protocol and / or SCSI transparent command set instructions), and are executed according to conditions such as user operations or timing. For example, document operation instructions developed for different file system protocols (such as exfat, fat32, etc. file systems), according to the parameters of the high-level instructions (such as document path, file name, etc.), can automatically send multiple interaction instructions (including references between multiple low-level instructions and high-level instructions) to the target device, and according to the context analysis of the read / write data of the interaction instructions, read / or write the storage space data (such as sector address data) specific to the target device file system to achieve specific document operation functions, such as "create document instruction", "delete document instruction", "modify file attribute instruction", "read document content instruction", "modify document content instruction", etc. The high-level instructions can be triggered by an operator to send instructions to the network device through a client, a server, or a networked device; they can also be triggered by a timing device, a GPS and other peripheral modules to send instructions to the network device. The high-level instructions can also reference each other. For example, the "create and generate content high-level instruction" can first execute the create document instruction (the file name is the parameter of the create document instruction), and then execute the modify document content instruction (the file name and the document content are the parameters of the modify document content instruction), such as creating a text document with the file name test.txt and the document data being the string test. In an embodiment of the present application, the high-level instructions can be document operation instructions developed according to different file system protocols, such as create document instructions, delete document instructions, modify file attribute instructions, read document content instructions, modify document content instructions, etc. In an embodiment of the present application, the automatically executed instruction script includes a data monitoring script. The data monitoring script is used to automatically respond to the server and the client when meeting the preset rules. For example, the network device detects whether the target device (such as a USB video source device, a USB camera, etc.) sends a data packet (non-NAK status packet) to the network device through the IN endpoint by sending an IN token packet to the IN endpoint of the target device. When the IN endpoint sends a data packet, the data packet received from the IN endpoint is forwarded to the client or the server. In an embodiment of the present application, the automatically executed instruction script includes: automatically executing a preset script (such as a high-level instruction or a low-level instruction, etc.) according to the data of the peripheral module (such as a positioning module GPS, etc., a sensor, etc.), a timing device or a network module. For example, when the position detected by the GPS positioning device is not at the preset position or the local IP address of the network device is not at a specific address, an instruction to delete document data, start a data monitoring script, etc. is executed. The first binding interaction system or data source strategy is used for the network device to automatically convert the instructions issued by the client and the server into a preset data exchange instruction set (at least one instruction) and send the converted data exchange instruction set to the target device for execution. For example, the issued instruction can be an operation such as the client reading a document / or writing a document, reading / writing a specific sector address, etc. In another embodiment of the present application, the first binding interaction system or data source strategy is also used to automatically store the data after the network device operates on the target device to a storage medium (such as a storage chip, a hard disk, etc.), a storage space (such as a sector interval), a specific database / or folder / or document (such as a mirror document), a storage space or a structured data string, etc. in any of the network device, the client, and the server. The first allow / deny exchange policy indicates allowing / denying the client or the server to issue specific instructions, etc. to the target device through the network device. For example, it prohibits sending an instruction to write data to the target device. In an embodiment of the present application, the first allow / deny exchange policy may include low-level instructions. The first allow / deny exchange policy may be a USB communication protocol instruction. For example, the first allow / deny exchange policy may be an instruction to allow / deny sending an IN / or OUT token packet to a specific endpoint. The first allow / deny exchange policy may also be an SCSI transparent command set instruction. For example, the first allow / deny exchange policy may be an instruction to only allow / deny sending read / write instructions to a specific sector location. In another embodiment of the present application, the first allow / deny exchange policy may include high-level instructions. For example, the first allow / deny exchange policy may be a document operation instruction, such as only allowing / denying sending an instruction to delete a document. The first allow / forbid exchange policy can also characterize controlling based on the data packets corresponding to the instructions, allowing / forbidding the target device to send specific data (such as data packets with specific characteristics) to the network device. For example, it is allowed / forbidden that the data packets attached to the write instruction conform to specific characteristics, and the write instruction is sent to the target device. Or it is allowed / forbidden that the data packets returned by the target device in the read instruction conform to specific characteristics, and the read instruction is sent to the server or the client. The first allow / forbid exchange policy can also characterize the policy of performing allow / forbid data exchange according to the data of peripheral modules (such as positioning modules, sensors, network modules, etc.). In an embodiment of the present application, if the device role of the network device is a slave device (such as a host communicating with the target device), the data exchange configuration information includes an instruction response operation, an automatic execution instruction response operation script, a second bound interaction system or data source policy, and a second allow / forbid exchange policy. The instruction response operation is used to respond to the data exchange instruction sent by the target device, such as performing a preset operation or returning data. In an embodiment of the present application, the data exchange instruction set sent by the target device to the network device can be low-level instructions, such as USB communication protocol instructions. The data exchange instruction set includes: when the target device (such as a USB device host) sends an IN token packet to a specific endpoint (such as endpoint 1) of the network device, a response data packet is returned to endpoint 1; when a specific endpoint (such as endpoint 2) of the target device sends an OUT token packet and a data packet, the data packet sent by the target device to OUT of endpoint 2 is received. In an embodiment of the present application, the data exchange instruction set sent by the target device to the network device can be SCSI transparent command set instructions. The data exchange instruction set includes: when the target device (as a host device) sends a read instruction to read the data of a specific sector address, the data of the specific sector address in the data storage space is returned to the target device; when a write instruction (the write instruction includes a specific sector address and a data packet) is sent to the target device, the data packet is written into the specific sector address in the data storage space. In an embodiment of the present application, the data exchange instruction set sent by the target device to the network device can be high-level instructions, such as document operation instructions developed according to different file system protocols. The data exchange instruction set includes at least one of an instruction to create a document, an instruction to delete a document, an instruction to modify file attributes, an instruction to read document content, and an instruction to modify document content. The data exchange instruction set can also be an operation based on multiple low-level instructions (such as read / write of USB communication protocol and SCSI transparent command set instructions), or can be an automation script that operates according to specific rules. In an embodiment of the present application, the objects of the instruction operations of the data exchange instruction set of the networking device include storage - type objects and peripheral - module - type objects. The storage - type objects include at least one of the local storage chips of the networking device, databases / or folders / or documents (such as mirror documents) / or storage spaces (such as disk sectors) in the client, the server. The peripheral - module - type objects include at least one of the positioning module, the sensor module, the audio - video source module, the human - machine interaction module, and the encryption module. The automatic execution instruction response operation script represents that according to the rules of the preset script, the networking device automatically returns data to the target device, or performs read - write operations related to data, or controls the peripheral module to achieve automated operations. For example, when there is a backup requirement and the data at a specific disk address is preset to be protected, when the target device sends data to be written to a specific disk address, the networking device automatically reads the data at that disk address and writes it to the backup storage space, and then executes the data - writing operation of the target device. In an embodiment of the present application, the automatic execution instruction response operation script of the networking device includes a data monitoring script. The data monitoring script includes low - level instructions. When the preset rules are met, the data monitoring script automatically responds to the server, or the client, or the control terminal, or the electronic device connected to the networking device, etc. For example, when the target device sends an OUT token packet and a data packet to the OUT endpoint of the networking device, when the networking device detects that the endpoint number or the data packet content meets the preset rules, it forwards the data packet to the client or the server or gives a reminder. In an embodiment of the present application, the automatic execution instruction response operation script includes: automatically executing a preset script (such as a high - level instruction or a low - level instruction, etc.) according to the data of the peripheral module (such as the positioning module GPS, etc., the sensor, etc.), the timing device, or the network module. For example, when the position detected by the GPS positioning device is not at the preset position or the local IP address of the networking device is not at a specific address, execute the instruction to delete document data, start the data monitoring script, etc. The second binding interaction system / or data source is used to automatically convert the instructions issued by the target device into preset instruction response operations and execute them. For example, the instructions issued by the target device can be operation instructions such as the target device reads a document / or writes a document, reads / writes a specific disk address, etc. The networking device performs corresponding operations according to the instructions and returns a data packet or a status packet. At the same time, the networking device also responds to capacity information (such as the maximum number of logical units, the total number of formatable logical blocks, the last logical block address, the block capacity, the total capacity, the available space capacity, etc.) or read - write status (such as read - only status, write - only status, read - write status) according to the instructions. In another embodiment of the present application, the second binding interaction system or data source policy is also used to automatically associate the data source of the instruction response operation with a storage medium (such as a storage chip, hard disk, etc.), a storage space (such as a magnetic sector interval), a specific database / or folder / or document (such as a mirror document), a storage space or a structured data string, etc. in any location in the network device, the client, or the server. The second allow / deny data exchange policy characterizes control based on instructions and allows / denies the client, server, or network device to issue specific instructions to the target device for operation (or response), such as prohibiting the operation or response to the write data instruction sent by the target device. In an embodiment of the present application, the second allow / deny data exchange policy includes low-level instructions. The second allow / deny data exchange policy can be a USB communication protocol instruction, for example, an instruction for allowing / denying the operation (or response) to the token packet instruction sent by the target device to the endpoint IN / or OUT of the network device. The second allow / deny exchange policy can also be an SCSI transparent command set instruction, for example, an instruction for allowing / denying the operation (or response) to the read / write instruction sent by the target device to a specific magnetic sector location of the network device. In another embodiment of the present application, the second allow / deny exchange policy can include high-level instructions, for example, the second allow / deny exchange policy can be a document operation instruction, for example, an instruction for allowing / denying the operation (or response) to the document deletion instruction sent by the target device to the network device. The second allow / deny exchange policy can also characterize control of the data packet corresponding to the instruction, allowing / denying the operation (or response) to the specific data sent by the target device to the network device. In another embodiment of the present application, when creating the scenario configuration information, if the device role of the network device is a peer communication device, configure the device exchange configuration information. Configuring the device exchange configuration information includes configuring the data sending end or the data receiving end of the network device. For example, configure interface 1 of the network device as the data sending end and send data to the receiving end of the target device through interface 1; configure interface 2 of the network device as the receiving end and receive the data sent by the target device through interface 2. In an embodiment of the present application, the specific content of configuring the data sending end of the network device can refer to the above-mentioned data exchange configuration information of the configured host, and the specific content of configuring the data receiving end of the network device can refer to the above-mentioned data exchange configuration information of the configured slave. Step S102, preload the target configuration information. Optionally, the scenario configuration information is created locally on the network device, and when the network device starts (or before access), preload the scenario configuration information. Optionally, the scenario configuration information is created on the server, and the network device preloads the scenario configuration information obtained from the server. Optionally, the scene configuration information is preset on the server, and the networking device preloads the scene configuration information obtained from the server. Optionally, step S102 further includes: when communicating with the server, preloading target configuration information. The server stores multiple preset configuration information, and the target configuration information is one of the multiple preset configuration information. The target configuration information includes the scene configuration information of the networking device in at least one application scenario. The scene configuration information includes at least one of a first descriptor set and a descriptor instruction set. The first descriptor set is used to define the device type of the networking device. Optionally, step S102 further includes: the scene configuration information stored by the server is generated based on a preset generation policy by configuring at least one of the first descriptor set and the descriptor instruction set of the networking device, and the data source configuration information before preloading the target configuration information. Optionally, before step S102: configure the first descriptor set and the data source configuration information of the networking device based on a preset generation policy to generate the scene configuration information. The preset generation policy includes at least one of a custom creation policy, a template creation policy, or an external import creation policy. In an embodiment of the present application, when the networking device is started (or before access), the networking device establishes a communication connection with the server and preloads the scene configuration information stored by the server. It can be understood that in other embodiments, the preloading process can be performed at other times after the networking device establishes a communication connection with the server, and the communication establishment process can also be performed at other times after the networking device is started. In an embodiment of the present application, the scene configuration information is associated with the identification information of the networking device. For example, the identification information of the networking device can be S123456. The user or manufacturer pre-associates the scene configuration information of a single scene or the scene configuration information of multiple scenes with the identification information S123456 of the networking device on the server in advance. The networking device sends a connection request to the server, and the connection request carries the identification information of the networking device. The server sends the scene configuration information corresponding to the identification information of the networking device to the networking device according to the connection request sent by the networking device. The identification information of the networking device can be data fixed in the main control chip of the networking device, or data of an external module (such as an encryption chip, etc.) of the networking device, or the identification information of the user. For example, after the user binds the device, the device retains the unique identification information of the user. The identification information of the networking device can be a string, binary data, etc. In addition, the scene configuration information can also be associated through the user identification information. The scene configuration information associated through the user identification information can be used for permission control or multi-user sharing of the scene. In an embodiment of the present application, all scenario configuration information corresponding to the network device stored in the server can be pre-loaded, or the scenario configuration information of the network device in the current application scenario can be pre-loaded. For example, based on a preset application scenario, the scenario configuration information corresponding to the application scenario is pre-loaded to the server. In an embodiment of the present application, the network device pre-sets a fixed scenario configuration template, obtains specific information in the scenario configuration from the server, and then combines the specific information with the pre-set scenario configuration template to generate and load the scenario configuration information. For example, the network device is pre-set with a scenario template for a USB flash drive at the factory. When switching scenarios, the scenario configuration information obtained from the server only includes other configurations related to the data source such as storage capacity information, read / write status, relevant strings, vendor ID, product ID, etc., to switch different data sources of the USB flash drive and achieve a change in function. In an embodiment of the present application, the power supply methods of the network device include but are not limited to: 1. When the network device is connected to a target device, the power of the target device is used to supply power to the network device. For example, when the network device is a slave device, it is connected to a target device (such as a computer host) to obtain the power of the computer host; 2. The network device is built-in with a power supply device to supply power using the built-in power supply; 3. The network device is powered by an external power supply. For example, when the network device is a host device, it accesses a mobile power supply or a charger through a first interface to obtain electrical energy, and a second interface is connected to a target device (such as a slave device). When the network device is a slave device, it accesses a mobile power supply or a charger through the second interface to obtain electrical energy, and the first interface is connected to the host device. Optionally, the process of establishing communication between the network device and the server includes: sending a communication connection request to the server based on preset server configuration information. The preset server configuration information can be stored in the network device, and it includes but is not limited to the communication address (such as IP address or domain name address) of the server, port, username, and access password, etc. Exemplarily, when the network device is powered on and started, it reads the preset server configuration information stored locally, and based on this preset server configuration information, sends a communication connection request to the server to establish a communication connection. Optionally, the network device communicates with the server through a wired or wireless network (such as Ethernet interfaces like twisted pair or optical fiber, Wi-Fi hotspot, ultra-wideband UWB, Bluetooth, mobile cellular network (such as 4G or 5G), satellite communication, and LoRa long-distance radio, etc.). The server includes but is not limited to devices with network service functions such as personal computers, laptops, embedded computers, physical servers, and cloud servers, or electronic products such as mobile phones and mobile terminals. During the networking process, the network security can be enhanced by further setting up a virtual private network, using a network dedicated line, etc. In an embodiment of the present application, the default application scenario can be selected on the server side. Exemplarily, by accessing the server side through a user terminal (such as an application or a web browser, etc.), the user selects the scenario configuration information to be sent to the network device on the user terminal, so that when the network device communicates with the server side, the scenario configuration information based on the user's selection is preloaded. It can be understood that the selection process on the server side can be an immediate process or a non-immediate process, that is, the application scenario corresponding to the scenario configuration information can be immediately selected on the server side when the scenario configuration information needs to be preloaded, or the application scenario corresponding to the scenario configuration information can be preselected. When the scenario configuration information needs to be preloaded, the scenario configuration information is preloaded based on the preselected application scenario. In an embodiment of the present application, the default application scenario can be selected on the interaction module of the network device. Exemplarily, the interaction module of the network device is provided with a display unit, and options for the user to select the application scenario are displayed on the display unit. Based on the user's selection operation, the application scenario is determined, so that when the network device communicates with the server side, the scenario configuration information based on the user's selection is preloaded. Similarly, the selection process on the network device can be an immediate process or a non-immediate process. In an embodiment of the present application, the default application scenario can also be selected on the physical switch of the network device. Exemplarily, the network device is provided with a physical switch, and by toggling the physical switch, the application scenario corresponding to the current switch indicator is selected, so that when the network device communicates with the server side, the scenario configuration information based on the user's selection is preloaded. In an embodiment of the present application, the default application scenario can also be automatically selected by the network device. Exemplarily, the network device automatically selects the corresponding application scenario based on the preset interaction data of the target device (such as descriptor content, descriptor instruction, or data communication content). Or, according to the location information of the GPS module of the network device, the corresponding application scenario is selected at a specific location; or, according to the local timing clock or network timing clock of the network device, the corresponding application scenario is automatically selected. After the network device obtains the scenario information, it can be saved locally and directly used the next time it runs without obtaining it from the server side again. It can also delete the scenario information when the connection between the network device and the server side fails, or when the server side issues a command to clear the scenario data. It should be noted that the target configuration information of the present application can be stored on the server side to prevent malicious reverse cracking after the network device is lost, and at the same time, the server side is beneficial to realizing the immediate hot update of the target configuration information. In an embodiment of the present application, the carrier of the scenario information includes but is not limited to at least one of the following: (1) the transmitted binary data stream, such as a network data stream, which can be a string, a structure, etc., where the network device can directly read and configure the scenario information from the server; (2) the binary file, such as the document "network flash drive.txt" (single scenario) or "USER123456.txt" (user scenario set), etc., where the network device imports and configures the scenario information after downloading the file; (3) the passed library document, such as the dynamic link library "network flash drive.so" (single scenario) or "USER123456.so" (user scenario set), etc., where the network device configures and uses the scenario information by further calling functions, variables, literals, etc. through the program after downloading the library document, or for example, the static link library "network flash drive.a" (single scenario) or "USER123456.a" (user scenario set), etc., where the network device configures and uses the scenario information by further compiling after downloading the library document, or directly calling functions, variables, literals, etc. In an embodiment of the present application, after obtaining the scenario information, the network device enables the scenario information on the first interface or the second interface of the network device. If the network device has only 1 interface, the scenario is preset to enable the only communication interface, such as the first interface or the second interface. If the network device has multiple interfaces (as shown in Figure 4), enable according to the interface number in the scenario configuration information, and the selected enabling method can be selected at the user end or the server end, can be selected on the interaction module of the network device, or can be selected by the data packet sent by the target device. For a network device with more than 2 interfaces, the scenario information can be flexibly enabled on multiple interfaces, and the data sources can be shared and cooperated between the interfaces. The scenarios corresponding to the interfaces of the network device can be as follows. 1. Multiple scenarios or scenario device types can be the same. For example, the interfaces of the same scenario device type (such as the device type of a large storage device is the scenario of multiple flash drives) can be respectively connected to different target devices. 2. Multiple scenarios or scenario device types use the same scenario device type and data source (such as the network device of the large storage device type has the scenario of multiple flash drives, and the multiple flash drives share the same data source), and can be respectively connected to different target devices to achieve data sharing and cooperative operation. 3. Multiple scenarios or scenario device types are different scenario device types. For example, the interface 1 is a scenario device type in slave mode (such as a USB flash drive mode), and the interface 1 can be connected to the target device 1 (the target device 1 is a computer host) in the mode of a USB flash drive. If the interface 2 is a scenario device type in host mode (such as a networking device with an instruction set for reading a large storage device type and can read the target device 2), it can be connected to the target device 2 (the target device 2 is in the mode of a USB flash drive). 4. There is only 1 scenario, but the scenario consists of multiple interfaces, and the data between the interfaces cooperate and collaborate. For example, in the case of a networking device (in the host mode + slave mode scenario), the interface 1 is in the host mode, and the target device connected is a slave device (such as a USB flash drive), and the interface 2 is in the slave mode, and the target device connected is a host device (a computer host). Further, the data sent by the host device (the computer host) through the interface 2 is forwarded by the networking device through the interface 1 to the slave device (such as a USB flash drive), and the data responded by the slave device (such as a USB flash drive) is sent through the interface 1 and then forwarded by the networking device through the interface 2 to the host device (the computer host). Since the data of the computer host and the USB flash drive is controlled by the networking device, a scenario where the networking device serves as an intermediate control device is realized, and the networking device, the server, or the user terminal can control the data interaction instructions between the computer host and the USB flash drive; for another example, in the peer-to-peer communication mode, the interface 1 of the networking device is the sending end (TX), and the interface 1 is connected to the receiving end (RX) of the target device; the interface 2 of the networking device is the receiving end (RX), and the interface 2 is connected to the sending end (TX) of the target device. The data is sent from the interface 1 of the networking device to the target device, and the data sent by the target device is received by the interface 2. 5. There is only 1 scenario, but the scenario consists of multiple networking devices, and the data between the multiple networking devices is divided, coordinated, and collaborated. For example, taking Figure 5A as an example, the user selects scenario A, and scenario A respectively sets the interface 1, the physical communication interface 2 of the networking device A, and the interface 1 and interface 2 of the networking device B, so as to realize the division, coordination, and collaboration of 2 networking devices and 4 interfaces. 6. Multiple scenarios are divided, coordinated, and collaborated. As shown in Figure 5B, data sharing, division, coordination, and collaboration are carried out among multiple networking devices and multiple target devices controlled by multiple scenarios. Step S103, based on the loaded scenario configuration information, establish a communication connection between the networking device and the target device, so that the networking device is connected to the target device. In an embodiment of the present application, the networking device establishes a handshake connection with the target device through an interface according to the scenario configuration information. When the networking device is in the host mode, it is used to identify the type of the accessed target device (at this time, the target device is a slave device) for loading the driver program (such as an instruction set) of the target device and further operating the target device; when the networking device is in the slave mode, according to the instructions sent by the target device, it responds to the target device with data such as descriptors for the target device to load the driver program of the networking device and further operate the networking device. In this step, the target device can be a computer device acting as a host, such as a laptop, a desktop computer, an embedded host, an industrial control device, a vehicle-mounted device, a mobile terminal, and a physical server, etc.; or it can be an electronic device acting as a slave, such as a USB flash drive, a portable hard drive, a hard drive, a flash memory device reader, an SD card, a TF card, and an external optical drive, etc. When the target device acts as a host, the networking device acts as a slave to communicate with the target device; when the target device is a slave, the networking device acts as a host to communicate with the target device. Optionally, when the pre-loaded target configuration information includes the scenario configuration information in all application scenarios, based on the current application scenario selected by the user on the networking device, the target scenario configuration information corresponding to the current application scenario is determined from multiple scenario configuration information; based on the target scenario configuration information, the device functions of the networking device are defined and a communication connection is established with the target device. Optionally, when the pre-loaded target configuration information only includes the scenario configuration information in the current application scenario, based on this scenario configuration information, the device functions of the networking device are defined and a communication connection is established with the target device. Optionally, the communication establishment method between the networking device and the target device can be implemented based on the handshake communication method. Among them, when the target device acts as a host and the networking device acts as a slave, the target device sends a handshake request to the networking device, and the networking device responds to this handshake request and returns the communication parameters (such as descriptors such as device descriptors) in the target scenario configuration information to the target device to achieve the handshake protocol and thus establish a communication connection. When the target device acts as a slave and the networking device acts as a host, the networking device initiates a handshake request. Optionally, during the process of achieving the handshake protocol, the communication parameters can be verified by an enumeration method. It should be noted that in this embodiment, by defining the device type of the networked device, the networked device can be used as a host device or a slave device, which can be applied to more application scenarios, realizing the application expansion of the networked device. The communication data can bypass the computer host, effectively avoiding being captured by the computer host and revealing the real data source and network communication data, and effectively avoiding being cracked by malicious programs on the computer host, ensuring the device security and data security of the networked device; and when the networked device is sold or lost, the communication relationship with the networked device can be authorized or released by the server, further ensuring the security of the data source of the networked device. It should be noted that the process of the networked device establishing a handshake connection with the target device is essentially a kind of data exchange. Different modes of the networked device (such as host mode, slave mode, and peer-to-peer communication mode) result in different ways for the networked device to establish a handshake connection with the target device. In an embodiment of the present application, if the device role of the networked device is selected as the host mode (i.e., acting as the host for communicating with the target device), configure the function instruction set in the descriptor instruction set for host enumeration, such as acquisition instruction set, verification instruction set, setting instruction set, interaction instruction set, data source instruction set, and custom instruction set, and configure the data source configuration information to bind the data source during the data exchange process between the networked device and the target device. The data source includes but is not limited to storage media, storage space address intervals (such as sector address intervals), mirrored storage documents, specific folders, databases, and data flows, etc. If the device role of the networked device is selected as the slave role (i.e., acting as the slave for communicating with the target device), then configure the descriptor parameters, device type parameters, and data source configuration information for replying to the host. In some embodiments, based on the embodiment shown in FIG. 1, step S102 includes: when communicating with the server, sending a configuration acquisition request to the server, where the configuration acquisition request carries the identification information of the networked device; receiving the target configuration information corresponding to the identification information returned by the server. In an embodiment of the present application, since the server may be connected to multiple networked devices simultaneously, the correspondence between the identification information of the networked device and the target configuration information ensures that the networked device accurately obtains the target configuration information. In an embodiment of the present application, the identification information is the identification information representing the networked device, such as the device number of the networked device, the user name (or user number, user session ID) of the user to which the networked device belongs, etc. Optionally, a correspondence between the identification information and the target configuration information is established in advance. This correspondence can be fixedly set when the networked device leaves the factory or can be changed. It can be understood that all the configuration information of the networked device can be accessed by the client to the server for configuration on the page of the client, which will not be elaborated further hereinafter. In an embodiment of the present application, the configuration acquisition request also carries the current application scenario parameters of the networking device, so as to accurately acquire the target scenario configuration information corresponding to the current application scenario parameters according to the identification information and the current application scenario parameters. It should be noted that when a communication connection is established between devices, the device acting as the host performs a timeout determination according to the communication protocol (such as a handshake protocol or a control transfer protocol, etc.) (usually a timeout determination at the millisecond or microsecond level). Therefore, in order to ensure the establishment of the communication connection within the preset time, the function instruction set and the descriptor set are pre-loaded into the networking device. It should be understood that during the data transmission process between devices, the transmission protocol is a bulk transfer protocol or an isochronous transfer protocol or an interrupt transfer protocol, that is, it has a relatively long timeout determination. Therefore, for the data transmission in the device interaction process, the relevant data can be not pre-loaded. In addition, in some access scenarios with a relatively long timeout determination, the function instruction set and the descriptor set can be obtained from the server in real time. In some embodiments, the networking device serves as the host device for communicating with the target device, and the descriptor instruction set includes multiple function instruction sets, and the function instruction sets are used to control the data exchange between the networking device and the target device. Based on the embodiment shown in FIG. 1, the step S103 includes: enumerating multiple descriptors in the second descriptor set of the target device based on the function instruction set in the descriptor instruction set; if the enumeration is successful, configure the target data source when the networking device communicates with the target device, and the target data source is provided in the target device. If the enumeration is unsuccessful, the obtained descriptor set is submitted to the server. After being identified by the server, the corresponding descriptor set or function instruction set, etc. is downloaded from the server, and the enumeration is performed again. In this embodiment, since the networking device needs to initiate a request actively when acting as the host, in order to implement the host function of the networking device, a developed driver program (i.e., the function instruction set) is pre-set and stored in the server to protect the security of the function instruction set data of the networking device, prevent malicious use of the device function or data leakage or reverse cracking after the networking device is lost. In some embodiments, the enumeration process includes: reading the second descriptor set of the target device based on the acquisition instruction set; verifying multiple descriptors in the second descriptor set based on the verification instruction set; if multiple descriptors meet the preset device requirements, determine that the enumeration is successful. In an embodiment of the present application, when the networking device acts as a host mode or a host role, after the networking device is started and a scenario is selected, the first device access configuration information is read from the scenario configuration information. According to the first mode in the first device access configuration information, the interface of the networking device (such as the first interface or the second interface) is set to the host mode; according to the interface type, for example, the communication protocol of the interface is set to the USB communication protocol. When the target device (slave device) sends a telecommunications signal that can be enumerated (accessed), the networking device sends an enumeration request (a request to establish a handshake connection) to the target device. According to the standard instruction set (such as the descriptor data acquisition instruction set), the special instruction set (such as the device type acquisition instruction set), and the setting instruction set in the first device access configuration information, the networking device sends at least one data interaction instruction (such as sending a standard request to the preset endpoint 0 of the target device) to the target device according to the communication protocol (such as the USB communication protocol) of the set (or preset) interface, and receives the data returned by the target device. When the returned data meets the access success conditions specified by the first access status judgment rule, the networking device determines that the handshake connection is successfully established, and sends a connection success data packet to the server according to the first status response rule; when the returned data meets the access failure conditions specified by the first access status judgment rule, the networking device determines that the handshake connection fails, sends a connection failure data packet to the server according to the first status response rule, and requests new instruction set data from the server to reconnect to the target device. The following takes the scenario of the networking device accessing a USB flash drive by reading and writing as an example to illustrate the device access method in this embodiment. The step S101 includes: configuring the first device access configuration information. Specifically, configure the first mode as the host mode, configure the first interface type as the USB interface, configure one or more of the following standard instruction sets: obtain a hardware descriptor; obtain a configuration descriptor; obtain an interface descriptor; obtain an endpoint descriptor; obtain a string descriptor, configure one or more of the following special instruction sets: obtain the total number of formatable logical blocks; obtain the last logical block address, configure one or more of the following setting instruction sets: set the device address; set the device configuration (set the enable configuration); set the Bulk-Only Mass Storage Rese instruction, configure the first access status judgment rule as: judge whether parameters such as the returned interface descriptor, endpoint descriptor data, and capacity information conform to the parameters of the mass storage device type, if they do not conform to the parameters of the mass storage device type, determine that the access fails; if they conform to the parameters of the mass storage device type, determine that the access is successful, and set the first status response rule as: if the access fails, use the "second descriptor set" to re-access (enumerate), if the access still fails, send an access failure status data packet to the server; if the access is successful, send an access success status data packet to the server. The step S102 includes: preloading the access configuration information of the first device shown. The step S103 includes: when the network device interface detects that a device is connected, connect the USB flash drive according to the access configuration information of the first device. Specifically, according to the first mode in the access configuration information of the first device, set the interface of the network device to the host mode; according to the first interface type, set the communication protocol of the interface to the USB communication protocol, and set the communication address of the USB flash drive according to "set device address"; obtain the descriptor of the USB flash drive according to at least one of the instructions "obtain hardware descriptor", "obtain configuration descriptor", "obtain interface descriptor", "obtain endpoint descriptor", "obtain string descriptor", obtain the capacity information of the USB flash drive according to at least one of the instructions "obtain total number of formatable logical blocks", "obtain last logical block address", and start the configuration of the USB flash drive (such as the endpoint for the USB flash drive to start responding) according to the "set device configuration" instruction, and start the large storage area function of the USB flash drive according to the "Bulk-Only Mass Storage Reset" instruction. Based on at least one of the descriptor of the USB flash drive, the capacity information of the USB flash drive, the endpoint information of the USB flash drive, and the large storage area function of the USB flash drive, judge the success status / failure status of the USB flash drive connection according to the first access status judgment rule. If it is determined that the USB flash drive connection fails by the first status response rule, use the second descriptor set for reconnection or reselect the preset alternative scenario and reconnect, such as the scenario of connecting a camera. If the connection still fails, send a status data packet indicating connection failure to the server; if the connection is successful, send a status data packet indicating connection success to the server. It should be noted that the above steps in the process of connecting the USB flash drive according to the access configuration information of the first device do not necessarily correspond one by one or all be required in the actual implementation process. In this optional embodiment, the descriptor set includes but is not limited to device descriptor, configuration descriptor, interface descriptor, endpoint descriptor, string descriptor, BOS descriptor, and preset custom descriptors, etc. The preset device requirements are the protocol requirements in the communication protocol. Exemplarily, Table 1 below shows the descriptors obtained by the network device as the host device through descriptor instructions and the examples of settings through setting instructions. It should be understood that the descriptor acquisition instructions and setting instructions shown in Table 1 below are only used as examples, and in other embodiments, there may be more or fewer descriptors, which will not be elaborated here. Exemplarily, Table 1 below shows the descriptor instructions sent when the network device is the host device or in the host mode. Table 1 Exemplarily, based on the descriptor instruction set, the networking device reads the following information from the device descriptor, configuration descriptor, and string descriptor: 1. Manufacturer, identification information, strings, etc.; 2. The class used by the interface, such as the mass storage class; 3. The transfer endpoints, for example, endpoint 1 represents IN and endpoint 2 represents OUT; 4. The endpoint transfer mode, such as the bulk transfer mode. Based on the verification instruction set, it verifies whether the class used by the interface, the endpoints, and the endpoint transfer mode meet the application scenario requirements of the networking device. If they meet the requirements, it determines that the enumeration is successful (or the handshake connection is established successfully). If they do not meet the requirements, it determines that the enumeration fails (or the handshake connection fails), and returns information indicating the connection failure to the server. Optionally, the function instruction set further includes a setting instruction set for sending setting instructions to the target device. For example, the networking device sends a setting instruction to the slave device, requesting the slave device to enable the corresponding endpoint, set the bus address, enable the configuration, or at least one of them. It should be noted that when the networking device is the host device, it supports accessing multiple slave devices and supports enumerating multiple slave devices. It should be noted that in this embodiment, the networking device is used as the host device to communicate and connect with the target device. For an unknown access device (target device), it can obtain data such as descriptors sent by the target device and submit them to the server for identification, so as to download the corresponding descriptor set or function instruction set from the server, or automatically select an alternative other scenario, thereby fully expanding the access capability of the networking device to different types of target devices. In some embodiments, the configuration process of the target data source includes: Based on the data source instruction set, the target data source of the networking device is determined according to the data source configuration information. In this optional embodiment, based on the application scenario of the networking device, the data source instruction set of the networking device is configured to operate the data source of the target device. For example, in the application scenario where the networking device is connected to a mass storage device, the corresponding data source instruction set of the networking device is configured to operate on the data storage space of the target device. Another example is that in the application scenario where the networking device is connected to a keyboard device, the corresponding data source instruction set of the networking device is configured to read the key values input by the keyboard. The interactive data for operating the data source of the target device above can be synchronized to the server in real time, or can be filtered (or transformed) through a preset script or setting rules and then synchronized to the server. Optionally, for the application scenario where a networked device connects to a large storage device, the data source configuration information includes, but is not limited to, the capacity information of the data source. The capacity information includes the last logical block address of the data source, (last logical block address + 1) × block capacity = capacity information; the total number of formatable logical blocks and the block capacity (total number of formatable logical blocks) × block capacity = capacity information; the data source configuration information further includes the maximum logical unit number, where the maximum logical unit number represents the number of partitions; the maximum logical unit number; and the read / write status (such as read-only status, write-only status, read / write status), etc. Exemplarily, in the host mode, taking the scenario of reading a slave device (such as a USB flash drive device) as an example: Before or after the device is powered on, at the server side or locally on the device, the networked device is set to the network read / write control device mode. Specifically, it includes powering on the networked device, inserting the USB flash drive, the interface of the networked device detecting the access of a target device, enumerating through a preset descriptor instruction. If the enumeration is successful, the device type is obtained, and information indicating successful enumeration (including the device type) is sent to the server to establish a communication connection; if the enumeration fails, the descriptor information that the networked device can read is sent to the server, and the server is requested to send a new function instruction set (such as a descriptor instruction set or a data exchange instruction set) or new scenario information, and the enumeration is performed again after receiving the new descriptor instruction or scenario information. The server loads the corresponding driver or operating software according to the device type. The driver or operating software sends relevant instructions (data source instruction set) to the networked device through the server and performs calculations to obtain the maximum logical unit number, total space capacity, read / write status, available space capacity, relevant strings, vendor ID, product ID, etc. of the target device (such as a USB flash drive), completing the enumeration and operation preparation. The server or the client performs read / write operations through software. The user can operate on the (target device such as a USB flash drive) through application programs such as the server software, the client APP, or a web browser. For example, the user writes the document on the client to the USB flash drive, or reads the document on the USB flash drive and saves it to the client, or reads the data at a specified sector position on the USB flash drive, or writes data to a specified sector position on the USB flash drive. It should be noted that for scenarios where the data in storage device A needs to be copied to storage device B (or the data on the server is downloaded to storage device A or B, or the data in storage device A or B is uploaded to the server), the current technology requires connecting storage device A and storage device B to a computer for data copying (or installing application software in the computer device to connect to the server for operations), resulting in data leakage due to packet capture by the computer device during the data copying process. In this embodiment, using the networked device as the host device to communicate with the target device can well solve the above scenario problems. Since this embodiment does not need to use a computer device (with an operating system), it can prevent data from being stolen by malicious programs during the copying process; the uploaded data is directly stored on the server, preventing data loss or leakage caused by device loss; the networked device directly connects to the server, so that the network traffic data does not need to pass through the computer device and the target device, thereby reducing the possibility of being captured by network data and ensuring data security. In some embodiments, in the scenario where the networked device is a network read / write control device, based on the target scenario descriptor information, establishing a communication connection with the target device includes: Enumerating various descriptors in the second descriptor set of the target device based on the function instruction set in the descriptor instruction set; If the enumeration is successful, request the server to issue a driver instruction set corresponding to the target device to complete the communication connection, and the driver instruction set is used for data exchange with the target device. In this embodiment, the driver instruction set is a driver instruction set developed separately for different devices, including but not limited to an interaction instruction set and a custom instruction set, etc. For the process of obtaining descriptors and enumeration, please refer to the relevant description when the networked device is the host device, and details are not repeated here. In this embodiment, by requesting the server to issue a driver instruction set corresponding to the target device, the device type of the target device can be identified according to the second descriptor set of the target device, so that the corresponding driver instruction set can be loaded from the server for different device types of the target device, and used for data exchange between the networked device and the target device, realizing the access and data exchange of multiple device types. It should be noted that for the network read / write control device, it can configure the target data source according to actual application requirements, or it can not configure the target data source. In some embodiments, in the scenario where the networked device is a network proxy control device, step S103 includes: enumerating various descriptors in the second descriptor set of the target device based on the function instruction set in the descriptor instruction set; if the enumeration is successful, send the second descriptor set to the server to virtualize the target device on the server and generate a virtual device corresponding to the target device, thereby establishing a communication connection with the target device. In this embodiment, for the descriptor enumeration process, please refer to the relevant description when the networking device is the host device, which will not be elaborated here. Optionally, the virtualization process can be executed inside the server or by the computer front-end that controls the server. It should be noted that for the network proxy control device, it can configure the target data source according to actual application requirements, or it can not configure the target data source. As an example rather than a limitation, several application scenarios when the networking device is the host device are provided below. 1. The networking device is used as a remote controller. A custom driver is used to implement the direct control program of the server without the need to virtualize the USB device (it should be understood that the USB device can also be virtualized). The driver program is developed and controlled by means of a custom driver, that is, without using the general driver自带 by the operating system, but re-developing it自行. For example, a network read-write control device set as the host role (which can perform protocol conversion according to custom interaction instructions and scripts) reads and writes handshake protocol data (such as descriptor sets, etc.) of peripheral devices such as USB interfaces, HDMI interfaces, SCSI interfaces, IEEE1394 interfaces, SATA interfaces, eMMC interfaces, SDIO interfaces, M.2 interfaces, and serial communication interfaces, and enumerates the target device based on the above enumeration process to establish a communication connection between the network read-write control device and the storage device. Then, based on the driver instruction set installed on the server for read-write operations, an interaction instruction is sent to the network read-write control device by means of the user terminal controlling the server or in the way of the default instructions of the server. After the network read-write control device converts the interaction instruction, it is sent to the storage device to write the data of the server to the storage device or upload the data of the storage device to the server. Similarly, the network read-write control device can also establish a communication connection with sensor devices such as cameras and microphones, read the data collected by the sensor devices and upload it to the server, or control the camera to adjust the direction and angle, etc., or control the microphone to adjust the power, etc. according to the control instructions (i.e., the instructions in the custom instruction set) sent by the server. 2. The networking device is used as a network proxy control device. By using the networking device as a proxy device in combination with the native driver, the target device is virtualized as a local USB device by software (such as registering the obtained descriptor and other information in the USB bus), so that the server or the computer front-end that controls the server thinks that the target device is a local USB device, so that the target device can be normally recognized and used without re-developing the driver program. Optionally, for the case where the host device accesses multiple target devices at the same time, it is supported to map all the target devices to the computer front-end or the server through the network, so that the target devices are virtualized as local USB devices at the computer front-end or the server. It should be noted that the data implementation of the prior art is USB device - computer host 1 - network sharing - computer host 2 - virtual USB device, which has the following problems: 1. The data has to pass through computer host 1, and there are unknown risks in computer host 1; 2. The data passing through computer host 1 is easily captured by packet sniffing, resulting in the discovery of the data source address and data interaction logic, posing a security risk; 3. Computer host 1 is generally in the form of a PC, personal laptop, etc., and an operating system and software need to be installed; 4. The above data implementation is in the form of pure software. The network proxy control device of the present application can be in the form of an independent hardware, and can reduce the security risk without passing through a computer host. For example, the networking device uses a USB interface as the host interface to read the basic descriptor set from the connected printer (target device), and enumerates the target device based on the above enumeration process. After the enumeration is successful, the networking device sends the printer's descriptor set to the server. The server generates a virtual USB device on the local computer by means of a virtual bus or the like. The native driver of the printer (i.e., the function instruction set) remotely controls the mapped printer to perform printing by operating the virtual USB device. That is, the communication relationship is: server (printer driver - virtual USB device) - networking USB device (host device) - printer. In other embodiments, the server can also be controlled by the computer front end to visualize the virtualization process of the server, as well as the data to be printed and the printing progress of the printer on the computer front end, which will not be elaborated here. It can be understood that after the networking device is inserted into the printer on-site, the remote server communicating with the networking device directly identifies the printer by using the native printer driver to control the printer to perform printing, so as to avoid the leakage of data caused by copying important documents to a computer with unknown risks. It can be understood that the above application scenarios are only used as examples and not as limitations. In other scenarios, it can be a combination of multiple application scenarios. For example, it can be developed and implemented in the ways of scenario 1 and scenario 2 at the same time, which will not be elaborated here. In some embodiments, based on the embodiment shown in FIG. 1, the networking device is a slave device communicating with the target device, and step S103 includes: receiving an enumeration request sent by the target device; in response to the enumeration request, returning the first descriptor set to the target device, so that the target device enumerates the first descriptor set, and after the enumeration is successful, configuring the target data source when the networking device communicates with the target device according to the data source configuration information, and the target data source is set on the server. In this embodiment, similar to the communication connection process when the networking device is the host device, when the networking device in this embodiment is the slave device, the target device is the initiator of the enumeration request, and the networking device is the responder to the enumeration request. The target device performs the enumeration action as when the networking device is the host device, and the networking device replies to the enumeration action of the target device. When the networking device is the slave device, it supports connecting to multiple host devices and responding to the enumeration requests of multiple host devices. For the specific enumeration process, refer to the embodiment when the networking device is the host device, which will not be elaborated here. In an embodiment of the present application, when the networking device is in the slave mode, after the networking device selects a scenario, it reads the second device access configuration information from the scenario configuration information. The networking device sets the interface (such as the first interface or the second interface) of the networking device to the slave mode according to the first mode in the second device access configuration information; and sets the communication protocol of the interface to the USB communication protocol according to the interface type. When the target device (host device) is connected, it responds and sends a telecom signal that can be enumerated (accessed). The networking device receives the data interaction instruction sent by the target device (for example, the target device sends a standard request to endpoint 0 of the networking device) through the set (or default) interface. When the data interaction instruction conforms to at least one of the standard data set (such as the descriptor data set), special data set (such as the device type data set), execution setting instruction set, second access status judgment rule, and second status response rule in the second device access configuration information or meets the matching rule, it returns data to the target device; when the data exchange instruction includes the data content in the execution setting instruction set, the networking device performs the preset operation. When the data sent by the networking device meets the access success conditions specified in the second access status judgment rule, the networking device determines that the handshake connection is successfully established, and sends a connection success packet to the server according to the first status response rule; when the data returned by the target device meets the access failure conditions specified in the first access status judgment rule, the networking device determines that the handshake connection fails, sends a connection failure packet to the server according to the first status response rule, and requests new descriptor data from the server to reconnect to the target device. The following takes the USB flash drive scenario of the networking device as an example to illustrate the device access method in this embodiment. The step S101 includes: configuring the access configuration information of the second device. Specifically, configure the second mode as the slave mode, configure the second interface type as the USB interface, and configure one or more of the following standard data sets: the first hardware descriptor, the second hardware descriptor, the first descriptor, the second descriptor, the first interface descriptor, the second interface descriptor, the first endpoint descriptor, the second endpoint descriptor, the first string descriptor, the second string descriptor, and configure one or more of the following special data sets: the total number of formatable logical blocks, the last logical block address, the maximum number of logical units, the read / write status, etc., and configure one or more of the following execution setting instructions: execute the setting device address, execute the setting device configuration, execute the Bulk-Only Mass Storage Reset instruction, and configure the second access status judgment rule as: judge whether the instructions such as the instruction to obtain the first hardware descriptor, the instruction to obtain the first configuration descriptor, the instruction to obtain the first interface descriptor, the instruction to obtain the first endpoint descriptor, the instruction to obtain the first string descriptor, the instruction to obtain the total number of formatable logical blocks, the instruction to obtain the last logical block address, the instruction to obtain the read / write status, etc. sent by the network device conform to the parameters of the large storage device type. If they do not conform to the parameters of the large-capacity device type, it is determined that the access fails; if they conform to the parameters of the large-capacity device type, it is determined that the access is successful, and set the second status response rule as: when the access fails, use the second hardware descriptor, the second configuration descriptor, the second interface descriptor, the second endpoint descriptor, and the second string descriptor in the descriptor set to re-access (enumerate). If the access still fails, send a status data packet of access failure to the server; when the access is successful, send a status data packet of access success to the server. The step S102 includes: preloading the access configuration information of the second device. Step S103 includes: connecting the network device (USB flash drive scenario) to the target device according to the second device access configuration information. Specifically, send an enumerable electrical signal to the target device through the interface. When receiving the electrical signal for enumeration response from the target device and the returned data interaction instruction, set the interface of the network device to the slave mode according to the second mode in the second device access configuration information; set the communication protocol of the interface to the USB communication protocol according to the second interface type, set the USB communication address of the network device according to the execution of setting the device address; respond according to at least one of the instructions such as the instruction for obtaining the first hardware descriptor, the instruction for obtaining the first configuration descriptor, the instruction for obtaining the first interface descriptor, the instruction for obtaining the first endpoint descriptor, the instruction for obtaining the first string descriptor; enable the endpoints and functions corresponding to the interface of the network device according to the execution of setting the device configuration instruction; perform a self-check on the large storage device class function according to the execution of the Bulk-Only Mass Storage Reset instruction and return the execution status packet; according to the second access status judgment rule, judge whether the instructions such as the instruction for obtaining the first hardware descriptor, the instruction for obtaining the first configuration descriptor, the instruction for obtaining the first interface descriptor, the instruction for obtaining the first endpoint descriptor, the instruction for obtaining the first string descriptor, the instruction for obtaining the total number of formatable logical blocks, the instruction for obtaining the last logical block address, the instruction for obtaining the read / write status conform to the instructions of the large-capacity device type. If they do not conform to the instructions of the large-capacity device type, determine that the access fails; if they conform to the parameters of the large-capacity device type, determine that the access is successful; when the access fails, use the second hardware descriptor, the second configuration descriptor, the second interface descriptor, the second endpoint descriptor, and the second string descriptor in the descriptor set for re-access. If the access fails, send a status data packet indicating access failure to the server, or switch to an alternative scenario, such as the camera scenario, etc. When the access is successful, send a status message indicating successful access to the server. Exemplarily, Table 2 below shows the descriptors replied when the network device is a slave device or in the slave mode. Table 2 In some embodiments, the target device includes at least one first target device and at least one second target device. The network device serves as a host device communicatively connected to the first target device and as a slave device communicatively connected to the second target device. Establishing a communication connection with the target device based on the target scenario descriptor information includes: Enumerating various descriptors in the second descriptor set of the first target device based on the function instruction set in the descriptor instruction set; If the enumeration is successful, configure the first target data source when the networking device communicates with the first target device to complete the communication connection with the first target device. The first target data source is provided in the first target device; receive the enumeration request sent by the second target device; in response to the enumeration request, return the first descriptor set to the second target device, so that the second target device enumerates the first descriptor set, and after the enumeration is successful, configure the second target data source when the networking device communicates with the second target device according to the data source configuration information. The second target data source is provided in the server or the first target device. In this embodiment, for the descriptor enumeration process and the configuration process of the target data source, please refer to the relevant descriptions when the networking device is used as the host device or the slave device, which will not be elaborated here. The networking device in this embodiment has at least two or more physical interfaces and exists as both a "host device + slave device" at the same time. The networking device obtains the second descriptor set of the first target device (slave device) to complete the enumeration of the first target device; when the second target device (host device) initiates an enumeration request, the networking device forwards the first descriptor set to the second target device to complete the enumeration in the second target device, so as to realize multi-device interaction among the first target device, the networking device (and the server), and the second target device. Optionally, the networking device can also directly forward the descriptor instruction sent by the second target device to the first target device and directly forward the response data of the first target device to the second target device to complete the enumeration. Optionally, the server records the logs of the data exchange between the first target device and the second target device for the audit of the first target device and the second target device; in the case of data exchange, the networking device or the server can also perform operations such as modifying and replacing the data to protect the data security of the first target device and the second target device. As an example rather than a limitation, when the networking device is used as a network USB hub (such as a USB HUB), this embodiment can monitor the connected first target device and detect descriptor parameters and communication data. Specifically, when the first target device is connected to the networking device, it uploads the descriptor set of the first target device (such as Vendor ID, Product ID, or device type (used class, subclass, interface command set, endpoint transfer mode)) to the server. Only after the server determines that the first target device meets the qualified Vendor ID, Product ID, or device type can the first target device be allowed to exchange data with the networking device or the second target device. Optionally, when the networking device is a slave device of a large storage device, the data source configuration information includes, but is not limited to, the capacity information of the data source. The capacity information includes the last logical block address and block capacity of the data source, (last logical block address + 1) × block capacity = capacity information. The data source configuration information further includes the maximum number of logical units, where the maximum number of logical units represents the number of partitions. In another embodiment of the present application, the capacity information includes the total number of formatable logical blocks and block capacity of the data source, (total number of formatable logical blocks) × block capacity = capacity information. It should be noted that current access devices are all storage devices or external devices with a single function. And when used as a storage device, they can only store data in the local storage area of the storage device. Their storage capacity is limited by hardware, and the data storage space can be easily recognized by computer devices, resulting in a risk of data theft. In this embodiment, the networking device is used as a slave device to communicate with the target device. Based on the scenario switch, multiple different functional forms of a device can be realized, and the problems of limited storage capacity and easy recognition of the data storage space can be well solved, improving the security of the data source. By way of example and not limitation, the following provides several application scenarios when the networking device is a slave device. 1. The networking device is used as a network flash drive or other storage medium. The networking device is set to the form of a flash drive (such as the type of large storage device, bulk transfer endpoint, etc.), or the form of an SD card, TF card, or hard disk. The computer host obtains the descriptor set of the networking device and enumerates the descriptor set to establish a communication connection between the networking device and the computer host. In one embodiment, the computer host sends a read instruction or a write instruction to the network. The networking device sends the read instruction or write instruction to the server, user terminal, or control terminal. Only the server is taken as an example for illustration below. Based on the mirror file (such as a disk image document of disk.dd or an optical disc image document of disk.ISO) established at the server, user terminal, or control terminal, the networking device establishes an association relationship with the computer host to read or write the target data source of the networking device. In the data writing scenario, when the computer host writes interactive data to the network flash drive, network SD card, network TF card, or network hard disk, the network flash drive, network SD card, network TF card, or network hard disk uploads the interactive data to the server, and the server writes the interactive data to the specified offset position of the mirror document. In the data reading scenario, the data at the specified offset of the mirror document is read out in the server and returned to the computer host. It should be noted that the data of the mirror document is stored in the storage space in sequence. For example, according to the parsing of the file system, the mirror file A.dd is allocated a sector range with sector addresses from 0x1000 to 0x1007. In addition, the sector range with sector addresses from 0x1000 to 0x1007 of the mirror document is only an example, and the sector range of the actual storage medium is larger than the above-mentioned sector range. Taking the FAT32 file system as an example, the document information of the mirror document carries the first cluster address. The FAT32 file system can find all the cluster addresses based on the first cluster address and the FAT (File Allocation Table), and then convert them into all the sector addresses. For example, the A.dd document is converted into the above-mentioned sectors from 0x1000 to 0x1007. The specified offset represents the offset of the mirror document corresponding to the read / write instruction operation address. For example, using the above mirror document A.dd as the data source, if the sector address (i.e., the specified offset) read / written by the target device is 0, it is converted into the 0th sector address (the first sector address) of the mirror document A.dd, which is 0x1000. If the sector address read / written by the target device is 1, it is converted into the (0 + 1)th sector address of the mirror document A.dd, and so on, so as to map the specified offset to a specific sector address. Different data sources correspond to different sector addresses. For example, the sectors where the mirror document A.dd is stored are from 0x1000 to 0x1007, and the sectors where the mirror document B.dd is stored are from 0x2000 to 0x2007. If the data source is switched from the mirror file A.dd to the mirror document B.dd, only the address of the read / write operation needs to be converted to the sectors from 0x2000 to 0x2007. Since the sector addresses corresponding to the data sources are different, the data source has also changed, and the switching of the data source can be realized. Or further, different physical storage media are used as the data sources to achieve physical isolation between different data sources. Table III Referring to Table III, taking the FAT32 file system as an example (the document information of A.txt, and the same for the mirror document): the starting cluster number is 0x1d. According to the calculation of the file system, the first sector (the starting sector address) can be obtained; the corresponding cluster chain can be obtained in the FAT table, and based on the cluster chain calculation, the set of sector addresses of the document content data can be obtained. The data in the set of sector addresses is the content data of the A.txt document. For example, the binary data of the string 123456. If it is a mirror document, it is the corresponding sector data. It can be understood that the capacity information of different data sources (including the last logical block address, the total number of formatable block capacities, block capacity, total space capacity, available space capacity, maximum logical unit number), read / write status (such as read-only status, write-only status, read-write status, etc.), related strings, vendor ID, device ID, etc. can also be different. Therefore, although the device types in multiple different scenarios are the same (such as USB flash drives of the large storage device type), actually modifying the device's function by switching different data source configurations and data sources. In addition, when a network device interacts with a computer host, it can also be managed directly by storage space intervals (sector address intervals) without relying on documents. For example, the sector interval from 0x1000 to 0x1007 mentioned above is the sector interval allocated to a USB flash drive (such as the first USB flash drive), and the sector from 0x2000 to 0x2007 is the sector interval allocated to another USB flash drive (the second USB flash drive). For USB flash drives (USB interfaces), SD cards (emmc etc. interfaces), TF cards (emmc etc. interfaces), or hard drives (SATA, M.2 etc. interfaces), essentially only the data source (sector address) or capacity information (optional) is different. The network device actually acts as a read / write instruction remote mapper (i.e., converting the data on the server side to a USB flash drive with a USB interface, or an SD card or TF card with an eMMC or SDIO interface, or a hard drive with a SATA interface or M.2 etc. interface). In an embodiment of the present application, the data source includes but is not limited to storage media, storage space address intervals (such as sector address intervals), mirror storage documents, specific folders, databases, and data flows. The specific document is a document selected in advance by the user that allows the computer device to read and write, and it can be displayed to the user on the computer device. Mapping the specific document to the target address means mapping the sector address of the specific document in the storage device to the target address. The mirror document can be accessed as a storage data source into the computer host. The network device is communicatively connected to the server through a wired or wireless method, and the server contains multiple mirror documents. Optionally, in the case of distributed storage technology, optimized storage, and CDN network acceleration, the mirror document can be the data of a database, or a combination, splicing, and mapping of multiple documents. In an embodiment of the present application, the network device connects to the server and sends an identification number to the server. The server associates the corresponding image document according to the identification number of the network device. When the computer host sends a data interaction instruction, it forwards the read / write requirements of the data interaction instruction (such as read or write operations, the sector address where the operation starts, and the length of the operation sector) to the server. After receiving the read / write requirements sent by the network device, the server returns the address of the data block of the sector document corresponding to the image document to achieve the expansion of the data space of the network device. In an embodiment of the present application, according to the identification number of the network device, the server switches to control the target image document corresponding to the network device to connect the target image document to the computer host. For example, according to the identification number of the network device (or the identification number of the user (bound by account login)), three image documents "partition 1.dd", "partition 2.dd", and "partition 3.dd" are bound to switch the data source connected to the computer host among these three image documents. In an embodiment of the present application, the target device connects to the server and connects the image document of "partition 1.dd" stored in the server to the computer host. The computer host sends a data interaction instruction in a way that the size of a single sector is 512 bytes. If the data interaction instruction is used to read the data at the 0th sector address and write data to the 1st sector address, a request is sent to the server through the network device. The server converts the 0th sector into the first address of "partition 1.dd" and converts the 1st sector into the 512th byte offset address of "partition 1.dd". According to the converted address, the server returns the data from the 0th byte to the subsequent 511 bytes at the first address of the image file "partition 1.dd". Write data to the data from the 512th byte as the offset address to the subsequent 511 bytes of "partition 1.dd", and then the network device returns the result returned by the server to the computer host. The above-mentioned single-sector size of 512 bytes is only an example and not a limitation on the embodiments of the present application. For example, the single-sector size can also be 1024, 2048, 4096 bytes, etc. In an embodiment of the present application, the network device can switch different storage data sources at will without the computer host installing software tools (such as the USB flash drive read / write driver自带 by the operating system). The real address of the data source is invisible to the computer host, and the data source is stored in the cloud. When the network device is lost, the data source can be remotely cancelled to improve the data security of the data storage device. At the same time, in this embodiment, the data at a specific offset address of the associated document on the server is directly read and written (or the data at the sector address corresponding to the document), and the data is directly forwarded to the server or the computer host in a forwarding manner, so as to be unrestricted by the storage space of the storage device itself, improve efficiency and increase the applicable scenarios. The embodiments of the present application are different from existing network flash drives. In related technologies, documents on the server are first downloaded to the storage device of the network flash drive, and then the computer reads the documents in the file system of the storage device for downloading; or the computer first writes the documents into the file system of the storage device of the flash drive, and then the network flash drive uploads them to the server. In this way, it is necessary to occupy the storage space capacity of the network flash drive itself. For example, a 16G network flash drive cannot transfer a 32G document, or a network flash drive with less than 4G of remaining space cannot transfer a document larger than 4G. In the present invention, data is forwarded in the buffer (such as a single sector of 512 bytes as the buffer), and there is no problem of file limitation. On the other hand, it is impossible to switch the data of the entire storage partition. In the present invention, based on the read and write of the sector address, partition 1.dd can be formatted as the FAT32 file system, and the documents are A.txt and B.txt; partition 2.dd can be formatted as the ExFAT file system, and the documents are C.txt and D.txt, and can be directly connected to the computer for display. Existing network flash drives can only select specific documents for copying. In addition, the mirrored documents such as "partition 1.dd" mapped on the server can be data in the database, or a combination, splicing, mapping, etc. of multiple documents under the conditions of distributed storage technology, optimized storage, and CDN network acceleration. In an embodiment of the present application, when the networking device is an SD card or a TF card, the networking device can send or receive data packets through the Emmc interface or the SDIO interface and the corresponding communication protocol. For example, read and write instructions are sent through the SDIO_CMD line, and the SDIO_D line is used to send or receive data packets. In an embodiment of the present application, when the networking device is a hard disk, the networking device can send or receive data packets through the SATA interface or the M.2 interface and the corresponding communication protocol. 2. The networking device is used as a network USBkey device (such as a bank U shield, digital certificate, dongle, etc.). The networking device is set in the form of a USBkey and connected to the computer host. Among them, the network USBkey device internally includes: 1. PIN password (the password is data input by the user or collected and converted by the sensor), 2. algorithm, 3. key. For the PIN password, the data input by the user or collected and converted by the sensor can be sent to the server through the networking method for PIN verification; for the algorithm, it can be remotely downloaded from the server through the script method, that is, the algorithm can be updated at any time or an algorithm can be selected; for the key, the key or part of the key (such as the encryption method combining the local key and the server key) data can be stored on the server to improve security. Optionally, during the interaction between the networking device and the server, the server records logs and conducts behavior analysis, blocks suspicious behaviors in a timely manner and gives warnings to prevent the abuse of the USBkey. It should be noted that: 1. The USB key itself may not store important data such as PIN, algorithms, and keys. During operation, the important data is downloaded from the server to the memory of the USB key and erased after the USB key is powered off to improve security; 2. Each time the user uses the USB key, the server can record the usage log to prevent abuse. For example, the technology of virtualizing USB devices can share the data of the USB key among multiple computers; 3. For a lost USB key, it can be remotely locked to prevent theft; 4. Satellite positioning modules such as GPS and Beidou can be installed to report the geographical location of the USB key when requesting the server. The USB key is only allowed to be used when the preset geographical location conditions are met; 5. The data source of the USB key is stored on the server, and the network communication link can bypass the host to ensure the data security of the data source; 5. For the USBKEY password, it can be input and verified remotely by the user side or the server only during use. 3. The network device serves as a relay device (such as a storage device with networking capabilities). The computer host sends read / write interaction instructions to the relay device. For example, it sends a command to read the data at address 0 with a read data length of 512 bytes; writes data at address 1 with the written data being 0x1212... (512 bytes) and a written data length of 512 bytes. After receiving the instructions, the relay device calculates by combining the address, the number of bytes per single sector (for example, 512 bytes), and the data length, and converts the data interaction instruction operation sector address into the address corresponding to the server data (or the server converts it according to the forwarded data interaction instructions according to the preset rules). For example, it is converted into read / write operations on the U.dd document data of the server. For example, address 0 is converted into the sector 0 address of the U.dd document data of the server, and address 1 is converted into the sector 1 address of the U.dd document data of the server. After conversion, operations are performed on the U.dd document data of the server, such as returning the data at address 0 of the U.dd document data of the server and writing the data 0x1212... (512 bytes) to the sector address 1 of the U.dd document data of the server. It can be understood that the above application scenarios are only used as examples and not limitations. In other scenarios, it can be other hardware forms, such as input devices like keyboards, etc., which will not be elaborated here. Referring to FIG. 6, it is a flowchart of a device access method provided by an embodiment of the present application. The communication between the network device and the slave device uses the USB communication protocol, and the device access method in this embodiment is described by taking the network device (host mode) reading the data of the slave device (taking a USB flash drive as an example) through the USB interface. It should be noted that this example and related data are not limitations. For example, other target devices (slave devices) can be other device types such as USB cameras, etc., which will not be elaborated here. The client creates (or stores) the scenario configuration information of the "read USB flash drive scenario" through the server, or selects the existing scenario configuration information of the "read USB flash drive scenario". When the Internet-connected device requests from the server, the server sends the scenario configuration information of the "read USB flash drive scenario" to the Internet-connected device. In another embodiment of the present application, the scenario configuration information can also be created in the server. The Internet-connected device sends a configuration acquisition request to the server. The server obtains the scenario configuration information of the read USB flash drive scenario from the server according to the configuration acquisition request, and sends the obtained scenario configuration information of the read USB flash drive scenario to the Internet-connected device. After the target device (i.e., the USB flash drive) is inserted into the interface of the Internet-connected device, the USB flash drive sends an enumeration request (such as an enumerable electrical signal) to the Internet-connected device. The Internet-connected device sends a command to obtain a hardware descriptor to the USB flash drive, and sends an IN token packet to a specific endpoint of the USB flash drive to query data return. For example, the Internet-connected device sends a hardware descriptor command to endpoint 0 of the USB flash drive through a SETUP token packet. It should be noted that in this embodiment, the Internet-connected device, as the host, actively sends data interaction commands to the slave (such as the USB flash drive), and the slave makes a passive response according to the data interaction commands. For example, taking the USB communication rule as an example, when the Internet-connected device sends a token packet (or a token packet + a data packet) to the endpoint of the slave, the slave makes a response according to the token packet (or the token packet + the data packet) received by the endpoint (such as replying a data packet or a status packet to the host). If the Internet-connected device acts as a slave, the Internet-connected device receives the token packet (or the token packet + the data packet) sent by the host, and makes a response according to the received token packet (or the token packet + the data packet). The token packet includes at least one of a SETUP token packet, an IN token packet, an OUT token packet, a PING token packet, and a SOF token packet. The status packet includes at least one of an ACK, a NAK, a NYET, and a STALL status packet. The handshake packet includes the token packet and the status packet. Table 4 is a parameter table of the instruction format of the SETUP token packet. Among them, 0x in the present application represents a hexadecimal encoding value. Table 4 Referring to Table 4, in an embodiment of the present application, the instruction format of the SETUP token packet includes an instruction first type field (SETUP), a first address field (ADDR), a first endpoint field (ENDP), a first data field (DATA), and a first status field (ACK or NAK). The first instruction type field records the SETUP instruction identifier to characterize that the first instruction type is a SETUP token packet, and 0x2D represents the identifier value. The first address field is used to record the address information of the recipient of the SETUP token packet (i.e., the USB flash drive), for example, the USB bus address information of the recorded USB flash drive is 0x25. The first endpoint field is used to record the endpoint information of the recipient of the SETUP token packet. For example, the endpoint information of the recorded USB flash drive is 0x00. The first data field (DATA) is used to record the packet data of the SETUP token packet. For example, the data in the DTAT field is an instruction to obtain a device descriptor. The first status field is used to record the status of the recipient of the SETUP token packet (i.e., the USB flash drive). The status field includes an ACK status packet and a NAK status packet, etc. Among them, the ACK status packet characterizes the successful status of the recipient, and the NAK status packet characterizes the failed status of the recipient. Referring to Tables 5 and 6, in an embodiment of the present application, after the networking device receives the ACK status packet sent by the USB flash drive in response to the SETUP token packet, it continues to send an IN token packet to the USB flash drive. The USB flash drive returns a hardware descriptor packet of the USB flash drive to the networking device according to the IN token packet. It should be noted that if the networking device sends an IN token packet to a specific endpoint of the slave device (USB flash drive) and then receives a NAK status packet (0x5A) returned by the USB flash drive, it means that the slave device (USB flash drive) cannot provide data, as shown in Table 5. The networking device repeatedly sends (within the timeout determination) the IN token packet to the USB flash drive until the USB flash drive returns the first ACK status packet, as shown in Table 6. This application will not elaborate further. Table 5 Table 6 Referring to Table VI, in an embodiment of the present application, the instruction format of the IN token packet includes a second instruction type field (IN), a second address field (ADDR), a second endpoint field (ENDP), a second data field (DATA), and a second status field (ACK or NAK, etc.). The second instruction type field records the IN instruction identifier, and the IN instruction identifier can take a value of 0x69 to represent that the instruction type is an IN token packet. The second address field is used to record the address information of the recipient of the IN token packet. For example, the USB bus address information of the recorded USB flash drive is 0x25. The second endpoint field is used to record the endpoint information of the recipient of the IN token packet. For example, the endpoint information of the recorded USB flash drive is 0x00. The second data field is used to record the data returned by the recipient of the IN token packet (i.e., the USB flash drive). For example, the data in the DTAT field is a device descriptor. The second status field is used to record the status of the recipient of the IN token packet. The second status field includes an ACK status packet and a NAK status packet, etc. Among them, the ACK status packet represents the successful status of the recipient, and the NAK status packet represents the failed status of the recipient. In an embodiment of the present application, the hardware descriptor data of the target device (slave device, such as a USB flash drive, etc.) at least includes: representing the descriptor length (such as 0x12); representing the device descriptor (such as 0x01); representing the USB protocol version used (such as 0x00 0x02); representing the class code (such as 0x00); subclass code (such as 0x00); representing the protocol used by the device (such as 0x00); representing the maximum packet length of endpoint 0 (such as 0x40); representing the vendor ID (such as 0xff 0xff); representing the product ID (such as 0x78 0x56); representing the device version number (such as 0x00 0x02); representing the vendor string index (such as 0x01); representing the product string index (such as 0x02); representing the product serial number string index (such as 0x03); representing the number of configurations (such as 0x01). It should be noted that after the networking device receives the hardware descriptor data sent by the target device (slave device, such as a USB flash drive, etc.), according to the rules corresponding to the SETUP token packet (such as the rules of control transfer), it needs to send an OUT token packet to the target device and attach an empty data packet (refer to Table VII) to notify the target device (slave device) that the data reception is successful. This application will not elaborate further. Table VII Referring to Table VII, the instruction format of the OUT token packet includes a third instruction type field (OUT), a third address field (ADDR), a third endpoint field (ENDP), a third data field (DATA0 or DATA1), and a third status field (ACK, NAK, or NETY). The third instruction type field records the OUT instruction identifier, which can take the value of 0xE1 to indicate that the instruction type is an OUT token packet. The third address field is used to record the address information of the recipient of the OUT token packet. For example, the USB bus address information of the recorded USB flash drive is 0x25. The third endpoint field is used to record the endpoint information of the recipient of the OUT token packet. For example, the endpoint information of the recorded USB flash drive is 0x00. The third data field is used to record the data returned by the recipient of the OUT token packet. For example, the recorded data is empty. The third status field is used to record the status of the recipient of the OUT token packet. The third status field includes an ACK status packet and a NAK status packet, etc. Among them, the ACK status packet indicates the successful status of the recipient, and the NAK status packet indicates the failed status of the recipient. Referring to Table VIII, the networking device sends a set device address instruction to the USB flash drive to assign an address to the slave device (such as the USB flash drive), and sends an IN token packet to a specific endpoint of the slave device (such as the USB flash drive) to query for data return. For example, the networking device sends a set device address instruction to endpoint 0 of the USB flash drive via a SETUP token packet. The USB flash drive returns a first ACK status packet of the USB flash drive to the networking device according to the set device address instruction and the IN token packet. For example, the USB flash drive returns a first ACK status packet to the networking device via endpoint 0. For example, the networking device sends a SETUP token packet to endpoint 0 of the USB flash drive, and the data in the SETUP token packet (the data in the DATA field in Table IX) is used to set the address. The networking device receives the first ACK status packet returned by the USB flash drive to indicate that the address setting of the USB flash drive is successful. Table VIII The networking device sends a get string descriptor instruction to the USB flash drive, and sends an IN token packet to a specific endpoint of the USB flash drive to query for data return. For example, the networking device sends a get string descriptor instruction to endpoint 0 of the USB flash drive via a SETUP token packet. The USB flash drive returns a string descriptor data packet of the USB flash drive to the networking device according to the get string descriptor instruction and the IN token packet. It should be noted that for the example data of the related handshake packets and data packets such as the get descriptor instruction, set instruction, descriptor, token packet, status packet, etc., in addition to referring to the above tables, it can also refer to Table I, Table II, or other examples, etc. This application will not elaborate further. The network device sends a command to obtain a configuration descriptor to the USB flash drive, and sends an IN token packet to a specific endpoint of the USB flash drive to query for data return. For example, the network device sends a command to obtain a configuration descriptor to endpoint 0 of the USB flash drive via a SETUP token packet. The USB flash drive returns a configuration descriptor data packet of the USB flash drive to the network device according to the command to obtain the configuration descriptor and the IN token packet. For example, the USB flash drive returns a configuration descriptor data packet to the network device via endpoint 0 (generally speaking, this configuration descriptor data packet contains a configuration descriptor, an interface descriptor, and an endpoint descriptor). The network device sends a command to set the configuration to the USB flash drive to set the configuration information of the USB flash drive, and sends an IN token packet to a specific endpoint of the USB flash drive to query for data return. For example, the network device sends a command to set the configuration to endpoint 0 of the USB flash drive via a SETUP token packet. The USB flash drive returns a second ACK status packet of the USB flash drive to the network device according to the command to set the configuration and the IN token packet. The network device determines whether the connection (or access) between the network device and the target device is successful according to the descriptor data returned by the above USB flash drive. If the network device determines that the connection of the USB flash drive fails according to the first status response rule and the descriptor data returned by the USB flash drive, it requests a new scenario configuration or a new instruction set from the server for reconnection; if the connection is successful, it enters a special request and performs special requests and data exchanges according to the information obtained from the descriptor. Further, the network device analyzes the descriptor information obtained from the USB flash drive (such as an interface descriptor and an endpoint descriptor, etc.) to obtain the specific endpoint number and transmission method for data transmission of the USB flash drive, and continues to send instructions to the USB flash drive. For example, according to the analysis of the obtained endpoint descriptor, endpoint 1 is an OUT endpoint, and the transmission method of endpoint 1 is bulk transfer. Set endpoint 2 of the network device as an IN endpoint, and the transmission method is bulk transfer. It should be noted that the endpoint number and endpoint function of each device are different, and are generally obtained through the endpoint descriptor. The above endpoint 1 and endpoint 2 are for illustrative purposes and do not constitute a limitation on the target device. It should be noted that for the network device (as the host) and the target device (as the slave) or the network device (as the slave) and the target device (as the host), determining whether the connection (or access, or handshake) is successful can be in the handshake stage (such as obtaining a descriptor command, setting a configuration, etc.), or in the data exchange stage (such as the read / write sector address command conforms to the preset, sending a TEST detection command, etc.). This application will not elaborate further. The network device sends a command to obtain the MAXLUN descriptor (special instruction set) to the USB flash drive, and sends an IN token packet to a specific endpoint of the USB flash drive to query for data return. For example, the network device sends a command to obtain the MAXLUN descriptor to endpoint 0 of the USB flash drive by means of a SETUP token packet. The USB flash drive returns a MAXLUN data packet of the USB flash drive to the network device according to the command to obtain the MAXLUN descriptor and the IN token packet. The USB flash drive returns MAXLUN data, such as 0x00, to the network device according to the IN token packet. For example, the USB flash drive returns MAXLUN data to the network device through endpoint 0, where the MAXLUN data includes the maximum logical unit number. The network device sends a command to obtain device information (INquiry) to the USB flash drive, and sends an IN token packet to a specific endpoint of the USB flash drive to query for data return. For example, the network device sends a command to obtain the device information descriptor to endpoint 1 of the USB flash drive by means of an OUT token packet, and sends an IN token packet to endpoint 2. The USB flash drive returns a device information data packet of the USB flash drive to the network device according to the command to obtain the device information descriptor and the IN token packet. For example, according to the preset scenario configuration, the network device sends a command (such as a SCSI or SATA command, such as a CBW packet) to endpoint 1 of the target device to request to obtain device information (INquiry) data of the target device. The target device responds to the request to read "INquiry" and returns a first data packet (INquiry data packet) and a status packet (such as a CSW packet for SCSI or SATA commands) to the network device. Referring to Table IX, the CBW packet includes the following information: the identifier of the CBW packet, the serial number of the CBW packet, the number of bytes transmitted, the transmission direction, the logical unit of the operation, the command block length, the operation instruction code, and the operation instruction parameters. Among them, when the operation instruction code is 0x12, it represents that the network device (host mode) sends a command to request to obtain "INquiry" data to the target device (slave device). Table IX Referring to Table X, the first data packet (INquiry data) includes the following information: Table X Referring to Table XI, the CSW status includes: the CSW identifier, the serial number of the CBW packet, the remaining number of bytes, and the error code. Table XI It should be noted that the data structures of the above CBW instruction packet and CSW status packet are described based on the SCSI communication protocol, and other related contents of this application will not be elaborated here. The network device sends a request to obtain capacity information (such as the maximum logical unit number, the total number of formatable logical blocks, the last logical block address, block capacity, etc.) or obtain the read / write status (MODESENCE6) instruction to a specific OUT endpoint of the USB flash drive, and sends an IN token packet to a specific IN endpoint of the USB flash drive to query for data return. For example, the network device sends a request to obtain capacity information or obtain the read / write status instruction to endpoint 1 of the USB flash drive via an OUT token packet, and sends an IN token packet to endpoint 2. The USB flash drive returns a data packet of the capacity information or read / write status of the USB flash drive via endpoint 2. In an embodiment of the present application, the network device sends a request to read the "total number of formatable logical blocks" (READ_FORMAT_CAPACITIES) to a specific OUT endpoint of the target device. For example, the network device sends a CBW packet to the target device (such as a USB flash drive), where the operation instruction code is 0x23, to request to obtain the "total number of formatable logical blocks" of the target device (such as a USB flash drive). The target device (such as a USB flash drive) responds to the request to read the "total number of formatable logical blocks" and returns a first data packet (as shown in Table XII) and a CSW status packet to the network device. Referring to Table XII, the first data packet (total number of formatable logical blocks) includes the following information: Table XII In an embodiment of the present application, the network device sends a request to read the "last logical block address" (READ_CAPACITY) to a specific OUT endpoint of the target device. For example, the network device sends a CBW packet to the target device (such as a USB flash drive), and the operation instruction code is 0x25, to request to obtain the "last logical block address" data of the target device (such as a USB flash drive). The target device (such as a USB flash drive) responds to the request to read the "last logical block address" and returns a first data packet (as shown in Table XIII) and a CSW status packet to the network device. Referring to Table XIII, the first data packet (last logical block address) includes the following information: Table XIII It should be noted that the network device (host mode) can calculate the capacity information separately by the "total number of formatable logical blocks" and the "last logical block", and does not need to obtain the data of both at the same time. In an embodiment of the present application, the network device sends a request to read the "read / write status" (MODESENCE6) to a specific OUT endpoint of the target device. For example, the network device sends a CBW packet to the target device (such as a USB flash drive), and the operation instruction code is 0x2A, to request to obtain the "MODESENCE6" data of the target device (such as a USB flash drive). The target device (such as a USB flash drive) responds to the request to read the "MODESENCE6" and returns a first data packet (as shown in Table XIV) and a CSW status packet to the network device. Referring to Table XIV, the first data packet (MODESENCE6) includes the following information: Table XIV The networking device determines whether the connection (or access) to the target device is successful based on at least one of the MAXLUN data packet, device information data packet, capacity information data packet, and read / write status (MODESENCE6) data packet returned by the above USB flash drive. According to the first status response rule, the networking device determines that the connection to the USB flash drive fails and requests a new instruction set from the server for reconnection; if the connection is successful, the networking device sends a status data packet indicating successful connection to the server, and the server sends the status data packet indicating successful connection to the user terminal. Referring to FIG. 7, there is shown a flowchart of a device access method provided by another embodiment of the present application. The communication between the networking device and the slave device uses the USB communication protocol. The networking device (slave mode) takes the USB flash drive scenario as an example to illustrate the device access method in this embodiment. It should be noted that this example and related data are not restrictive. Other networking devices (slave devices, slave mode) can be other device types such as the USB camera scenario, etc., which will not be elaborated here. In addition, the related token packets, CBW packets, CSW packets, operation instructions, data packets, and other data contents in this embodiment are similar to those in the above embodiment of the networking device (host mode) reading the USB flash drive, that is, the roles of the host and the slave and the instruction data and response data are exchanged, and the response configuration is performed in the scenario configuration, which will not be elaborated in this embodiment. The user terminal creates the scenario configuration information of the USB flash drive scenario or selects the existing scenario configuration information of the USB flash drive scenario. The networking device sends a configuration acquisition request to the server, where the configuration acquisition request includes the USB flash drive scenario. The server obtains the scenario configuration information of the USB flash drive scenario from the user terminal according to the configuration acquisition request and sends the obtained scenario configuration information of the USB flash drive scenario to the networking device (i.e., the USB flash drive). The networking device is set to the slave mode according to the scenario configuration information, the preset endpoint 0 is started, and it is set to control transfer. After inserting the target device (host device) into the interface of the networking device (such as a USB flash drive), an enumeration request (such as an enumerable electrical signal) is sent to the target device. The target device sends a command to obtain a hardware descriptor to a specific endpoint of the networked device, and sends an IN token packet to the specific endpoint of the networked device to query for data return. For example, the target device sends a hardware descriptor command to endpoint 0 of the networked device via a SETUP token packet. The networked device returns a hardware descriptor data packet of the USB flash drive to the specific endpoint of the target device according to the command to obtain the hardware descriptor and the IN token packet. For example, the networked device returns a hardware descriptor data packet of the networked device (such as a USB flash drive) to the target device via endpoint 0. The hardware descriptor data packet of the networked device (such as a USB flash drive) includes at least the device type and device function of the USB flash drive. The target device sends a command to set the device address to a specific endpoint of the networked device to allocate an address to the networked device, and sends an IN token packet to the specific endpoint of the networked device to query for data return. For example, the target device sends a command to set the device address to endpoint 0 of the networked device via a SETUP token packet. The networked device performs an address setting operation according to the command to set the device address, and returns a third ACK status packet of the USB flash drive to the target device according to the IN token packet. For example, the networked device returns a first ACK status packet to the target device via endpoint 0. The first ACK status packet is used to indicate whether the address of the networked device is successfully allocated. The target device sends a command to obtain a string descriptor to a specific endpoint of the networked device, and sends an IN token packet to the specific endpoint of the networked device to query for data return. For example, the target device sends a command to obtain a string descriptor to endpoint 0 of the networked device via a SETUP token packet. The networked device returns a string descriptor data packet of the USB flash drive to the target device according to the command to obtain the string descriptor and the IN token packet. For example, the networked device returns a string descriptor data packet to the networked device via endpoint 0. The target device sends a command to obtain a configuration descriptor to a specific endpoint of the networked device, and sends an IN token packet to the specific endpoint of the networked device to query for data return. For example, the target device sends a command to obtain a configuration descriptor to endpoint 0 of the networked device via a SETUP token packet. The networked device returns a configuration descriptor data packet of the USB flash drive to the target device according to the command to obtain the configuration descriptor and the IN token packet. For example, the networked device returns a configuration descriptor data packet to the target device via endpoint 0. The target device sends setup configuration instructions to a specific endpoint of the networked device to set the configuration information of the networked device, and sends an IN token packet to the specific endpoint of the networked device to query data return. For example, the target device sends setup configuration instructions to endpoint 0 of the networked device by means of a SETUP token packet. The networked device performs setup operations according to the setup configuration instructions. For example, according to the descriptor data selected by the setup instructions, it activates the corresponding transport endpoint and returns a second ACK status packet of the USB flash drive to the target device according to the IN token packet. For example, the networked device returns a second ACK status packet to the target device by means of endpoint 0. The networked device performs enabling configuration according to the above instructions or scenario configurations. For example, the networked device activates a specific endpoint (such as endpoint 1) and sets it as an OUT endpoint, and sets the transport mode of OUT endpoint 1 as bulk transfer; the networked device activates a specific endpoint (such as endpoint 2) and sets it as an IN endpoint, and sets the transport mode of IN endpoint 2 as bulk transfer. The networked device determines whether the networked device is successfully connected (or accessed) to the target device according to the instructions returned by the target device and the second status response rule. If the instructions sent by the target device do not meet the preset device requirements specified by the second status response rule, it is determined that the connection of the networked device fails, and a request is sent to the server for a new descriptor set for reconnection; if the instructions returned by the target device meet the preset device requirements specified by the second status response rule, it is determined that the connection is successful, and the data exchange process of special requests is entered. In the data exchange process of special requests, the target device sends a command to obtain the MAXLUN descriptor to a specific endpoint of the networked device, and sends an IN token packet to the specific endpoint of the networked device to query data return. For example, the target device sends a command to obtain the MAXLUN descriptor to endpoint 0 of the networked device by means of a SETUP token packet. The networked device returns a MAXLUN data packet of the networked device (such as a USB flash drive) to the target device according to the MAXLUN descriptor command and the IN token packet. The target device sends a command to obtain the device information descriptor to the networked device, and sends an IN token packet to a specific endpoint of the networked device to query data return. For example, the target device sends a command to obtain the capacity information descriptor to endpoint 1 of the USB flash drive by means of an OUT token packet. The networked device returns a capacity information data packet of the USB flash drive by means of endpoint 2 according to the command to obtain the capacity information descriptor and the IN token packet. The target device sends a command to obtain the capacity information descriptor to a specific endpoint of the networked device, and sends an IN token packet to a specific endpoint (such as endpoint 2) of the networked device to query data return. For example, the target device sends a command to obtain capacity information (obtaining the maximum logical unit number, total number of formatable logical blocks, last logical block address, block capacity, etc.) or read / write status, etc. to endpoint 1 of the USB flash drive by means of an OUT token packet. The networked device returns the capacity information or read / write status data packet of the networked USB flash drive by means of endpoint 2 according to the capacity information command and the IN token packet. The target device sends an instruction to obtain the read / write status (MODESENCE6) to the networked device, and sends an IN token packet to a specific endpoint of the networked device to query for data return. For example, the target device sends an instruction to obtain MODESENCE6 to endpoint 1 of the networked device via an OUT token packet. The networked device returns the MODESENCE6 data packet of the networked device (USB flash drive) via endpoint 2 according to the MODESENCE6 instruction and the IN token packet. The networked device determines whether the connection (or access) between the networked device and the target device is successful according to the instruction sent by the target device and the second interface status rule. The networked device determines that the connection between the target device and the networked device (USB flash drive) fails according to the first status response rule, and requests a new descriptor set from the server for reconnection; if the connection is successful, it sends a status data packet indicating successful connection to the server, and the server sends the status data packet indicating successful connection to the user side. It should be noted that the data such as descriptors, capacity information, and read / write status returned by the above networked device as a slave to the target device (host device) are pre-set through scenario configuration (USB flash drive scenario). In an embodiment of the present application, when the networked device is in peer-to-peer communication mode, after the networked device starts up and selects a scenario, it reads the third device access configuration information from the scenario configuration information. After the networked device starts up and selects a scenario, it obtains the third mode, the third interface type, the interaction data set, the third status judgment rule, and the third status response rule in the third device access configuration information; according to the third mode, it sets the working mode of the networked device to peer-to-peer communication mode; according to the third interface type, it selects 2 physical communication interfaces of the networked device, namely the data sending interface and the data receiving interface. Among them, the data sending interface of the networked device is connected to the data receiving interface of the target device, and the data receiving interface of the networked device is connected to the data sending interface of the target device. The networked device sends data to the target device via the data sending interface (TX) based on the rules of the interaction data set, and receives the data returned by the target device via the data receiving interface. The networked device receives the data sent by the target device via the data receiving interface (RX) based on the rules of the interaction data set, and returns the data to the target device via the data sending interface. When the data sent by the target device meets the preset access success conditions specified in the third access status determination rule, the networking device determines that the handshake connection is successfully established; and sends a connection success packet to the server according to the third status response rule; when the data returned by the target device meets the preset access failure conditions specified in the third access status determination rule, the networking device determines that the handshake connection fails; sends a connection failure packet to the server according to the third status response rule, requests data such as a new interaction dataset, and reconnects / or waits for a connection from the target device. Referring to FIG. 8, it is a flowchart of a device access method provided by an embodiment of the present application. The method of the embodiment of the present application can be applied to a networking device, and the networking device stores scenario configuration information of at least one application scenario. The networking device includes, but is not limited to, devices such as a microcontroller or an embedded device with networking functions, in-vehicle devices, smart phones, tablet computers, or laptop computers, network USB key devices (such as bank U shield digital certificates, dongles, etc.), network proxy control devices (such as multi-port repeaters), remote controllers (including but not limited to network read-write control devices, network controllers (such as routers and smart gateways, etc.)), communication devices (Communication Device Class, CDC, such as network cards, modems, ISDN (Integrated Services Digital Network) terminals), human interface devices (Human Interface Device, HID, such as keyboards or mice), mass storage devices (Mass Storage Device Class, MSC, such as USB flash drives, network USB flash drives, card readers, network card readers), printer devices (Printer device, such as a printer with a USB interface), still imaging devices, video devices, audio / video devices, smart card devices, USB hub devices (Universal Serial Bus Hub), and custom devices, etc. As shown in FIG. 8, the device access method of this embodiment includes the following steps. Step S301, when communicating and connecting with the server, preload the target configuration information. The server stores multiple preset configuration information, and the target configuration information is one of the multiple preset configuration information. The target configuration information includes the scenario configuration information of the networking device in at least one application scenario. The scenario configuration information includes at least one of a first descriptor set and a descriptor instruction set. The first descriptor set is used to define the device type of the networking device. Step S302: Based on the target scenario configuration information, establish a communication connection with the target device to enable the networking device to access the target device. The target scenario configuration information is one type of the scenario configuration information. In an embodiment of the present application, the scenario configuration information is generated by the networking device according to a preset generation strategy by configuring at least one of the first descriptor set and the descriptor instruction set and the data source configuration information. The preset generation strategy includes at least one of a custom creation strategy, a template creation strategy, or an external import creation strategy. Referring to FIG. 9, it is a flowchart of a device access method provided by an embodiment of the present application. As shown in FIG. 9, the device access method of this embodiment includes: Step S701: Based on the target scenario configuration information, establish a communication connection with the target device to enable the networking device to access the target device. The target scenario configuration information is one type of the scenario configuration information. The scenario configuration information includes at least one of a first descriptor set and a descriptor instruction set. The first descriptor set is used to define the device type of the networking device. In this embodiment, similar to the device access process in the embodiment shown in FIG. 1, the step explanations can be referred to the relevant descriptions in the embodiment of FIG. 1 and will not be elaborated here. It should be noted that the target scenario configuration information of this embodiment is stored in the local storage space of the networking device without the need to obtain it from the server, so as to further improve the device access efficiency or limit the function range of the networking device. As shown in FIG. 10, it is a flowchart of a data exchange method provided by an embodiment of the present application. The method of the embodiment of the present application can be applied to networked devices. The networked devices are connected to the server and the target device through the above device access method to establish a communication connection. The networked devices include, but are not limited to, devices such as a microcontroller or an embedded device with networking capabilities, terminal devices such as a smart phone or a laptop computer, a network USB key device (such as a bank U shield, a digital certificate, a dongle, etc.), a network proxy control device (such as a multi-port repeater, etc.), a remote controller (including but not limited to a network read-write control device, a network controller (such as a router and a smart gateway, etc.)), a communication device class (CDC, such as a network card, a modem, an ISDN (Integrated Services Digital Network) terminal), a human interface device class (HID, such as a keyboard or a mouse), a mass storage device class (MSC, such as a USB flash drive, a network USB flash drive, a card reader, a network card reader), a printer device (such as a printer with a USB interface), a still imaging device, a video device, an audio / video device, a smart card device, a USB hub device (Universal Serial Bus Hub), and a custom device, etc. As shown in FIG. 10, the data exchange method of this embodiment includes steps S801 to S802, which are described in detail as follows. Step S801, obtain a data exchange request sent by a first target party. Step S802, based on a preset processing strategy, respond to the data exchange request and return target data to the first target party. The target data is data sent by a second target party. If the first target party is the server, the second target party is the target device. If the first target party is the target device, the second target party is the server. In an embodiment of the present application, the data exchange request is a request when the networked device and the target device perform data interaction, including a first exchange request initiated by the networked device and a second exchange request initiated by the target device. The preset processing strategy is a strategy for processing the data exchange request, which includes but is not limited to a first strategy for processing locally on the networked device and a second strategy for forwarding the data exchange request to the server. In an embodiment of the present application, when the networking device is a host device, it supports accessing multiple slave devices and supports data exchange with multiple slave devices; when the networking device is a slave device, it can also support connecting to multiple host devices and support data exchange with multiple host devices. In this embodiment, the networking device, the server, and the target device are connected by the device access method shown in the embodiments of FIGS. 1, 8, or 9, so that the networking device undertakes different interaction roles and interaction processes in different data exchange scenarios, thereby enabling data exchange of the networking device in multiple application scenarios and improving the scenario applicability of the networking device. In an embodiment of the present application, when the networking device is in host mode, it obtains the endpoint information of the target device (USB slave device) by obtaining a descriptor instruction. For example, endpoint 1 is IN and endpoint 2 is OUT. The networking device发起 an instruction query operation instruction request to the server through the network interface and waits for the server to issue an interaction instruction. When an interaction instruction is queried, the networking device downloads an interaction instruction set for the interaction operation. For example, it is necessary to send data A1 to the target device and receive the return data from the target device. The networking device sends data A1 to endpoint 2 (OUT) of the target device and sends an IN token packet to endpoint 1 (IN) to query for data return. When the networking device receives the DATA packet A2 at endpoint 1, it uploads it to the server. In an embodiment of the present application, when the networking device is in slave mode, according to the endpoint-related information in the scenario configuration (such as interface descriptor, endpoint descriptor, etc.), it enables the endpoint number, transfer direction, and transfer method of the corresponding endpoint (for example, endpoint 1 is an IN endpoint and the bulk transfer method; endpoint 2 is an OUT endpoint and the bulk transfer method, etc.), and waits for the computer host to send interaction instruction data to the above two ports. The networking device receives data A1 sent by the computer host to endpoint 2 (OUT). The networking device uploads data A1 to the server through the network interface. The server parses data A1 and waits for the networking device to download data A2. The networking device downloads data A2 through the network interface. When the computer host sends an IN token packet to endpoint 1 (IN) of the networking device, it returns the DATA packet A2 to the computer host. In an embodiment of the present application, the networking device has both slave mode and host mode at the same time. The target device includes at least one first target device and at least one second target device. The networking device serves as a host device communicatively connected to the first target device and as a slave device communicatively connected to the second target device. If the first target party is the server, then the second target party is the first target device or the second target device. If the first target party is the second target device, then the second target party is the server or the first target device. Specifically, on one hand, the networking device acts as a slave mode (e.g., interface 1). According to the endpoint-related information in the scenario configuration (such as interface descriptors, endpoint descriptors, etc.), it enables the first endpoint (e.g., endpoint 1) to be IN and the second endpoint (e.g., endpoint 2) to be OUT, and waits for the target device 1 (computer host) to send interaction command data to the above two ports through interface 1. On the other hand, as a host mode (e.g., interface 2), it sends a descriptor acquisition command through interface 2 to obtain the endpoint information of the target device 2 (USB device). For example, endpoint 1 is IN and endpoint 2 is OUT. The interface 1 of the networking device receives the A1 data sent by the target device 1 to the endpoint 2 (OUT) of the networking device. The networking device sends the A1 data to the endpoint 2 (OUT) of the target device 2 through interface 2 and sends an IN token packet to endpoint 1 (IN) to query for data return. When the interface 2 of the networking device receives the DATA packet A2 from endpoint 1 of the target device 2, it returns the DATA packet A2 to the target device 1 through endpoint 1 of the interface 1 of the networking device. The networking device downloads preset rules from the server through the network interface to detect the data interactions of A1 and A2 data, and realizes uploading data to the server, or downloading data from the server to replace or modify the A1 or A2 data, or blocking the communication of the target device 1 or the target device 2. It should be noted that the embodiments of the present application can at least solve the following problems. Capacity problem: Taking the scenario of a network USB drive of the networking device as an example (slave), in the existing data exchange, the document on the server (such as the test.avi document with a size of 4GB) is first downloaded to the USB drive in its entirety, and then the computer reads the test.avi data from the USB drive. However, in the data exchange method of the present application, during the download process, the request or corresponding data packet is directly forwarded, and only a small amount of data buffer storage space is required for the data packet. For example, as shown in FIG. 28, in the case of 512 bytes per sector, a 512-byte memory buffer is set. When the computer host wants to read the data of the first sector address of the test.avi document, the networking device forwards the read instruction to the server, downloads the response of the first sector address data from the server and stores it in the memory buffer, and then forwards the data in the memory buffer back to the computer host. Subsequently, when the computer host continues to read the second sector address and even the last sector address of the test.avi document, it continuously updates the memory buffer for the exchange between the server and the computer host, realizing the transmission of a 4GB document with a storage capacity of 512 bytes. The size of the transmitted document is not limited by the storage space of the networking device itself. On the contrary, if the networking device takes the example of reading and writing the test.avi on the USB drive through a network read-write control device, the test.avi can be uploaded to the server through a 512-byte memory buffer. The above examples are only for illustration. In different file systems, the reading and writing methods may vary, and it may also adopt the method of combining multiple sectors into one cluster for management. However, they can all be applied to this basic data exchange principle. In the actual exchange process, in order to improve the transmission efficiency, requests for multiple sectors can also be combined for processing. For example, if the cache space is 128×512 bytes and data exchange is performed with 128 sectors at the same time, etc., which will not be elaborated here. Function expansion problem: Taking a network reading and writing control device (host) as an example, in the prior art, the device acting as the host can only first install the program software with interaction instructions (such as driver programs, parsing programs, etc.) in the device. Only when there is a driver for the local device can the control of the connected device be carried out. Therefore, the driver needs to be installed in advance to control the target device, resulting in difficulty in expanding the functions of the device. However, when using the data exchange technology of the networking device of the present application, the interaction instructions can be downloaded immediately on the server side. For example, taking the connection of a networking device to a standard USB flash drive (with software installed) and a special camera (without software installed) as an example, when the USB flash drive is connected, since the device itself has installed the reading and writing program (function instruction set) of the USB flash drive, the reading and writing of the USB flash drive can be directly carried out; when the camera is connected, since there is no function instruction set for the special camera, the obtained descriptor cannot be recognized and enumeration cannot be completed. Therefore, the obtained descriptor is sent to the server side. After being recognized by the server side, relevant function instruction sets (such as obtaining descriptors, verification instructions, etc.) are sent down. The device re-enumerates the camera according to the function instruction set to establish a connection; the server side directly sends a special camera data reading instruction to the networking device, and the networking device forwards the instruction to the special camera. After the camera returns the data, the networking device can directly display the camera screen or forward the screen data to the server side for storage or sharing by the server side. Security issue: The data buffer area of the networking device and the downloaded function instruction data can be stored in the memory. The device itself does not need to store data, and the data will disappear after power-off. This can protect important data from being stolen. In some embodiments, based on the embodiment shown in FIG. 10, step S802 includes: in response to the data exchange request, forwarding the data exchange request to the second target party; receiving the target data returned by the second target party in response to the data exchange request, and forwarding the target data to the first target party. In an embodiment of the present application, based on the second strategy of forwarding the data exchange request to the server side, the networking device performs forwarding processing on the data exchange request. In an embodiment of the present application, when the networking device receives a data exchange request initiated by the target device, the networking device forwards the data exchange request to the server. The server parses and processes the data exchange request and returns the target data to the networking device, and then the networking device returns the target data to the target device. In an embodiment of the present application, the networking device is a network USBkey device, and the target device is a computer host. Responding to the data exchange request and forwarding the data exchange request to the second target party includes: responding to the data exchange request sent by the computer host and forwarding the data exchange request to the server. The data exchange request carries the certificate information of the USBkey device (the certificate information can be input by the user or obtained by sensor collection and conversion) so that the server can verify the certificate information. The certificate information includes but is not limited to PIN text passwords and biometric information, and the biometric information includes but is not limited to fingerprint information, iris information, face information, and voiceprint information. It can be understood that the relevant implementation principles of the network USBkey device can be referred to the relevant descriptions of the network USBkey device in the above device access method, and will not be elaborated here. In an embodiment of the present application, when the user operates on the networking device and initiates a data exchange request, the data exchange request is first sent to the server for parsing and processing. The server then returns the target data to the networking device, and the networking device returns the target data to the target device. Exemplarily, the networking device acts as a keyboard device. The keyboard device accesses the computer host as a slave device. When the user clicks a certain button (such as button A) on the keyboard device at the computer front end or the server end to input "A" on the computer host, the click of button A triggers the data exchange request to be sent to the server. The server identifies the key value "A" corresponding to button A and returns the key value "A" to the keyboard device. When the target device (computer) scans the keyboard input, the keyboard device then sends the key value "A" to the computer host. Thus, it can be used as a remote keyboard input scenario. For the user to remotely input sensitive strings (such as passwords, etc.) to the computer host, there is no need to tell the on-site personnel to input the sensitive strings, improving security. It should be understood that the above key values are only used as examples and are not limitations. At the same time, the keyboard device is also applicable to scenarios processed using a preset processing script, which will not be elaborated here. In an embodiment of the present application, the networking device acts as a network proxy control device, connects to the printer as a host, receives the print data sent by the computer host. When it is necessary to optimize the print data (for example, enhance the image data to improve the print quality of the image), the print data is sent to the server for optimization processing, the optimized data returned by the server is received, and the optimized data is sent to the printer for printing. It should be understood that the above image data is only used as an example and not a limitation. In other embodiments, it may also be other data. In an embodiment of the present application, data processing is performed on the server by means of request forwarding to reduce the hardware pressure on the networking device, so that high-computing power data processing can be achieved for some networking devices with poor computing power, enabling low-level function networking devices to achieve high-level functions, improving the high-level application expansion of the networking device, and at the same time protecting the programs of high-level functions from being reverse-engineered, cracked, and misused locally. In an embodiment of the present application, based on the embodiment shown in FIG. 10, step S802 includes: performing data processing on the data exchange request based on a preset processing script to obtain a data processing result; sending a target data acquisition request to the second target party based on the data processing result; receiving the target data corresponding to the data processing result returned by the second target party in response to the target data acquisition request, and returning the target data to the first target party. In an embodiment of the present application, the preset processing script is a script program integrating data processing logic, which enables the networking device to process data or run data logic locally without forwarding all data to the server for execution, and only interacts with the server when a certain condition is triggered to improve data processing efficiency. In an embodiment of the present application, the networking device acts as a large storage device (slave role), processes the data exchange request based on a preset processing script. For example, when it is recognized that the data exchange request sent by the computer host indicates that the file name to be read is test.txt (i.e., the data processing result), it requests the server to read the test.txt document data, downloads the test.txt document data (i.e., the target data) sent by the server, and then returns the test.txt document data to the computer host. Similarly, for the data writing process, when the computer host writes to the test.txt document, the networking device can upload the test.txt document to the server for storage, and other documents are normally stored in the local storage area. In an embodiment of the present application, the networking device, as a network read-write control device (host role), has a built-in storage medium, and stores the processing logic of general or open-source interaction instructions in the local storage medium for execution to improve the data exchange speed. The special instructions are stored on the server, and then, according to actual needs, the special instructions are remotely loaded from the server to prevent the interaction logic of the special instructions from being reverse-analyzed at the local end and ensure the security of data exchange. Based on a preset script, data retrieval is performed on the connected large storage devices (such as USB flash drives, etc.), for example, searching for documents with the file name test.txt, searching for documents with the first byte of the first sector of the document being 0xFF, etc., and the retrieved document data is automatically uploaded to the server. In an embodiment of the present application, as a network proxy control device when the networking device acts as the host role, based on a preset script, by reading descriptors, it identifies the vendor ID, product ID, or device type (used class, subclass, interface command set, endpoint transfer mode, etc.) of the connected device. Only when the connected target device meets the qualified vendor ID, product ID, or device type is remote mapping allowed to protect the security of the server or the control end. In an embodiment of the present application, as a network intermediate control device when the networking device acts as the host role, based on a preset script or a downloaded script, the script is various AI models or algorithms. When the device connects an audio device and a computer host, it switches the audio optimization and enhancement algorithm to optimize the audio data sent from the computer host to the audio device to enhance the sound playback effect of the audio device; when the device connects a camera and a computer host, it switches the AI image recognition model to process the image data sent from the camera to the computer host to achieve item marking, etc. In an embodiment of the present application, the above large storage devices, network read-write control devices, network proxy control devices, and network intermediate control devices are also applicable to the request forwarding scenario and are not processed locally using a preset processing script. For the data exchange of other device types, reference can be made to the relevant example descriptions of the above device access method, which will not be elaborated here. Referring to FIG. 11, it is a flowchart of a data interaction method in another embodiment of the present application. The data interaction method includes the following steps. Step S1101, configure the scenario configuration information when the networking device communicates with the target device, and the scenario configuration information includes an automatically running script. Step S1102, based on the automatically running script, send a first data exchange request to the target device and receive the data sent by the target device in response to the first data exchange request; or based on the automatically running script, receive a second data exchange request sent by the target device and send data to the target device in response to the second data exchange request. In an embodiment of the present application, when receiving the data sent by the target device in response to the first data exchange request, the networking device sends the data sent by the target device to the server. In an embodiment of the present application, during the data exchange process between the networking device and the target device, according to the preset configuration of the data exchange configuration information, the networking device can perform data exchange with the target device based on the local data module of the networking device (such as a storage chip module, a camera module), or can perform data exchange with the target device based on the data sources provided by the client and the server. The following introduces the data exchange method in this embodiment with the networking device as the host mode. After the networking device starts and selects a scenario, the networking device is configured according to the data exchange configuration information in the scenario configuration information; if the data exchange configuration information includes an automatic execution instruction script (such as an automatic data interaction instruction script), the networking device automatically sends an instruction to the target device according to the content of the automatic execution instruction script; if the data exchange configuration information includes a data source instruction set and a data exchange instruction set, the networking device sends an instruction to the target device according to the data source instruction set and the data exchange instruction set. After sending an instruction to the target device, wait for and receive the data responded by the target device. In an embodiment of the present application, the data responded by the target device can be a data packet requested by the instruction or a status packet of the instruction execution result. After receiving the data responded by the target device, if it is determined that the instruction has not been completed and the instruction is a high-level instruction, for example, the instruction is a combination of multiple low-level instructions or an automatic execution instruction script (such as an automatic data interaction instruction script), then according to the rules of the high-level instruction, identify the responded data and continue to send the instructions preset in the high-level instruction; if it is determined that the instruction has been completed, according to the preset rules of the instruction, the responded data can be saved in the local storage medium of the networking device (such as a storage chip, a hard disk, etc.), or the data responded by the target device can be sent to the server and the client. In an embodiment of the present application, according to at least one of the data source instruction set, the data exchange instruction set, the bound interaction system or the data source in the data exchange configuration information, the networking device returns data to the server and the client. The data returned by the networking device can be the original data responded by the target device (such as an original data packet), or can be the data processed according to the instruction preset rules in the data exchange configuration information (such as converting the status packet into a specific mark). In an embodiment of the present application, according to the allow / deny data exchange policy in the data exchange configuration information, the networking device can identify the parameter content of the instructions sent by the client and the server. For example, it can identify the operation type (such as read / write type) and operation target (such as a specific sector address) in the instructions sent by the client and the server to the networking device, and restrict the instructions with specific parameter content. For example, it can prohibit instructions for write operations or instructions for operating on sector address 0x00, etc. In an embodiment of the present application, according to the allow / deny data exchange policy, the networking device can identify the content of the received instruction or the data packet of the response instruction. For example, for the write data packet in the write instruction sent by the client or the server, or the data packet returned in response to the read instruction, it can be judged and identified according to the hash value of the data packet or the byte value at a specific position. In another embodiment of the present application, it can be identified and judged according to the data of the peripheral module in combination with the instruction parameters or the data packet content. For example, the data of the peripheral module can be a specific location area of the GPS positioning module or the IP address of the networking module. When the data of the instruction or the response conforms to the preset rules, the networking device operates on the data of the instruction or the response according to the allow / deny exchange policy. For example, the networking device forwards or does not forward the instructions sent by the client and the server, or the networking device forwards or does not forward the data packets responded by the target device to the client and the server. In an embodiment of the present application, it can also be judged and identified by combining the data of the peripheral module with the instruction parameters or the data packet content. For example, when the GPS position of the GPS positioning module is located at a specific position, the instruction to read a specific position sector of the target device is allowed to be executed. The following takes the read and write of a USB flash drive (scenario) by a networking device (host mode) as an example to illustrate the data exchange method in this embodiment. Step S1101 further includes: configuring the data exchange configuration information for the scenario of reading the USB flash drive. Specifically, when configuring the data exchange configuration information, one or more of the following instructions in the data source instruction set are configured: maximum logical unit number, obtaining the number of formatable blocks; obtaining the last logical block address; obtaining the block capacity size; read / write status, etc. One or more of the following data exchange instructions are configured: USB communication protocol instructions; SCSI transparent command set instructions; document operation instructions. One or more of the following instructions for binding the interaction system or data source policy are configured: the binding relationship between the operation instructions of the server and the client and the preset instructions of the networking device. One or more of the following instructions for binding the interaction system or data source policy are configured: for example, when the position data in the positioning module is not located in a specific position area, the client and the server are prohibited from sending an instruction to delete the "test.txt" document under the root directory in the "document operation instruction" to the target device. In an embodiment of the present application, after the networking device and the target device are successfully enumerated, step S1102 includes: the networking device executes a "read document directory script" to automatically read the boot sector data of the target device (usually the sector address 0x00), and analyze the file system boot sector address; read the data of the file system boot sector address, and analyze relevant parameters such as the root folder (or the first directory) sector address and the cluster (block) size; read the root folder sector address data, and analyze the document information. The networking device processes the document information data according to the rules of the "binding interaction system / or data source", and sends the processing result to the user terminal or the server, so that the user terminal or the server can display the corresponding document information on the interaction interface (similar to the root directory display when a USB flash drive is connected to a computer). In an embodiment of the present application, the networking device reads the addresses of multiple sectors according to the file system protocol rules based on the automatic execution instruction script in the interaction instruction set, analyzes the document directory and document data according to the read data, and saves the document directory and document data locally on the networking device, on the server or on the user terminal. For example, as shown in FIGS. 12 and 13, the networking device sends read sector address instruction data to a specific endpoint of the target device, and sends an instruction to obtain specific endpoint data. For example, the networking device sends read sector address instruction data (such as CBW packets of SCSI and SATA) to endpoint 1 of the target device by means of an OUT token packet, and sends an instruction to obtain endpoint data to endpoint 2 of the target device by means of an IN token packet. The target device returns a data packet corresponding to the sector address to the networking device according to the read sector address instruction data and the instruction to obtain endpoint data. The networking device analyzes the document directory and document data according to the read data, where the document directory includes at least one of the file name, file attribute, and document start address. The networking device sends the document directory and document data to the server. The server sends the document directory and document data to the user terminal, so that the user terminal can display the document directory and document data on the interaction interface. In an embodiment of the present application, the networking device is set to the host mode based on the scenario (access) configuration information, and performs data interaction with the target device according to the automatic execution instruction script in the data exchange configuration information. By means of the descriptor instruction for obtaining the scenario (access) configuration information, the data interaction endpoint information of the target device (USB device) is obtained. The networking device发起 an instruction query operation instruction request to the server through the interface and waits for the server to issue an interaction instruction. When an interaction instruction is queried, the networking device downloads the interaction instruction set for the interaction operation. After the networking device receives the interaction instruction set, based on the automatic execution instruction script in the interaction instruction set, according to the USB communication protocol and the large storage device rules, it sends instruction data to the target device (within the timeout determination), and continuously sends token packets to request data from the IN endpoint until the IN endpoint returns data or an ACK status packet. For example, as shown in FIG. 12, the networking device sends command data to the target device and sends a command to obtain endpoint data. For example, the networking device sends command data to endpoint 1 of the target device via an OUT token packet and sends a command to obtain endpoint data to endpoint 2 of the target device via an IN token packet. When there is no data returned or the preparation for returning data is not completed, the target device returns a NAK status packet to the networking device according to the command data and the command to obtain endpoint data, where the NAK status packet indicates no data. The networking device repeats sending the command to obtain endpoint data to the target device according to the NAK status packet until the sector data and the ACK status packet returned by the target device are obtained. In an embodiment of the present application, the networking device and the target device can interact for sector read / write operations. Specifically, the user terminal and the server send sector read / or write operation commands (such as commands for reading or writing specific sector addresses such as SCSI, SATA, etc., such as CBW packets) to the networking device. The networking device parses the sector read / write operation commands sent by the user terminal and the server according to the command rules of "binding the interaction system or data source", and sends sector read / write operation commands to the target device according to the preset commands (such as SCSI transparent command set commands) in the "data exchange instruction set". The sector read / write operation commands include: if a read command (such as reading data of a specific sector) is sent to the target device, the target device returns a data packet and a status packet of the specific sector address of the data storage space; if a write command (write specific sector command and data packet) is sent to the target device, the data packet is written to the specific sector address of the data storage space of the target device, and the target device returns a status packet. After receiving the data in the data packet or the status packet, the networking device responds to the user terminal and the server based on the command rules of "binding the interaction system or data source". Specifically, as shown in FIG. 14A, the commands (including token packets, CBW packets) sent by the networking device (host device) to the target device (slave device, such as a USB flash drive), taking the SCSI protocol as an example, 0x28 represents: READ(10) command, requesting to read sector address data. This command also includes the operation sector address 0x00000000 and the operation sector quantity 0x0001. After receiving the command, the target device (slave device) responds to the host with a data packet (DATA packet) and a status packet (CSW packet). As shown in FIG. 14B, for a multi-sector continuous read command, the operation sector quantity of the networking device (host device) is: 0x0002. After receiving the command, the target device (slave device) responds to the host with 2 data packets (DATA packets) and a status packet (CSW packet). Specifically, as shown in FIG. 14C, the instructions (including the token packet and the CBW packet) sent by the networking device (host device) to the target device (slave device, such as a USB flash drive), taking the SCSI protocol as an example, 0x2A represents: the WRITE(10) instruction, which requests to write data to the sector address. This instruction also contains a data packet (DATA packet). After receiving the instruction and the data packet, the target device (slave device) performs an operation and responds to the host with a status packet (CSW packet). As shown in FIG. 14D, for the multi-sector continuous write instruction, the number of sectors operated by the networking device (host device) is: 0x0002, and the instruction also附带 2 data packets (DATA packets). After receiving the instruction and the 2 data packets, the target device (slave device) performs an operation and responds to the host with a status packet (CSW packet). It should be noted that, to avoid repetition, the relevant parameters of the read and write instructions are simplified in other parts of this application. Referring to FIG. 15, in an embodiment of the present application, the user terminal sends read sector address instruction data to the server. The server sends the received read sector address instruction data to the networking device. The networking device sends the read sector address instruction data (such as the CBW packet in SCSI) to a specific OUT endpoint (such as endpoint 1) of the target device through an OUT token packet, and sends an instruction to obtain endpoint data to a specific IN endpoint (such as endpoint 2) of the target device through an IN token packet. The target device returns a data packet corresponding to the sector address and a status packet for executing the instruction (such as the CSW packet in SCSI) to the networking device according to the read sector address instruction data and the IN token packet. The networking device sends the data packet and the status packet (or status data) to the server, and forwards the sector data packet and the status packet (or status data) to the user terminal through the server. Referring to FIG. 15, in an embodiment of the present application, the user terminal (or control terminal) sends write sector address instruction data and a data packet to the server. The server sends the received write sector address instruction and the data packet to the networking device. The networking device sends the write sector address instruction (such as the CBW packet in SCSI) and the data packet to a specific OUT endpoint (such as endpoint 1) of the target device through an OUT token packet, and sends an IN token packet to a specific IN endpoint (such as endpoint 2) of the target device through an IN token packet. The target device performs an operation according to the write sector address instruction and the data packet, and returns a status packet (such as the CSW packet in SCSI or the ACK, NAK packets in USB, etc.) to the networking device. The networking device sends the status packet (or status data) to the server, and forwards the status packet (or status data) to the user terminal through the server. In an embodiment of the present application, the network device and the target device can interact with document reading and writing operations. Specifically, the user terminal or the server sends a document operation instruction (such as a create document instruction, a delete document instruction, a modify file attribute instruction, a read document content instruction, a modify document content instruction, etc.) to the network device. The network device parses the document operation instructions sent by the user terminal and the server according to the instruction rules of the "bound interaction system or data source", and sends a document operation instruction to the target device according to the instructions preset in the data exchange instruction set. If the document operation instruction is an instruction to write data to the target device, such as a create document instruction, a delete document instruction, a modify file attribute instruction, a modify document content instruction, etc., the document operation instruction is a write instruction for writing a data packet, and the target device returns status packet data according to the document operation instruction. If the document operation instruction is an instruction to read data from the target device, such as a read document content instruction, the document operation instruction is a read instruction, and the target device returns the data of the data packet and the status packet according to the document operation instruction. After receiving the data of the data packet or the status packet, the network device responds to the user terminal and the server based on the instruction rules of the "bound interaction system or data source". As shown in FIG. 16, in another embodiment of the present application, the user terminal sends a create document instruction to the server. The server sends the create document instruction to the network device, and the network device writes the data for creating the document into a specific sector address according to the file system protocol rules and the pre-stored document directory. For example, according to the create document instruction, the network device sends the write sector address instruction data and the create document data to endpoint 1 of the target device by means of an OUT token packet. The target device writes the data for creating the document into a specific sector address according to the write sector address instruction data and the create document data, and returns a sector data packet to the network device. For example, the target device returns a sector data packet to the network device by means of endpoint 2. The network device determines the creation result data from the sector data packet and returns the creation result data to the server. The server returns the creation result data to the user terminal. In an embodiment of the present application, when the user terminal and the server issue instructions or execute an automatic execution instruction script, the network device executes according to the rules of the "permit / deny exchange policy" when sending a data interaction instruction to the target device. For example, according to the above CBW packet instruction, reading / writing of specific sector data is permitted / denied. If it is denied, the CBW instruction is not sent to the target device. As shown in Figure 17, in an embodiment of the present application, the user terminal sends a search document instruction to the server. The server sends the search document instruction to the network device, and the network device automatically reads multiple storage space addresses (such as sector addresses) according to the file system protocol rules, determines the searched document data and analyzes the document directory. For example, according to the search document instruction, the network device sends the read sector address instruction data to endpoint 1 of the target device through the OUT token packet, and sends the obtain endpoint data instruction to endpoint 2 of the target device through the IN token packet. The target device returns a sector data packet (such as document content) or a search result (such as document information) packet to the network device according to the read sector address instruction data and the obtain endpoint data instruction. For example, the target device returns a sector data packet to the network device through endpoint 2. The network device determines the searched document data and analyzes the document directory from the sector data packet or the search result packet, and returns the search result or the document data to the server. The server returns the searched document data to the user terminal. It should be noted that according to different file system protocols, the methods of creating and searching documents are different. In addition, document operations such as deleting documents, modifying file attributes, and modifying document content can be configured in the scenario by means of scripts or high-level instructions according to different file system rules, which will not be elaborated here. The following introduces the data exchange method in this embodiment with the network device in the slave mode. After the network device is started (or before access) and a scenario is selected, the network device is configured according to the data exchange configuration information in the scenario configuration information. For example, the instruction response operation, the automatic execution instruction response operation script, the second binding interaction system or data source policy, and the second allow / deny exchange policy in the data exchange configuration information are configured. The network device receives, processes, and responds to the instructions below the target device according to the configured instruction response operation, the automatic execution instruction response operation script, the second binding interaction system or data source policy, and the second allow / deny exchange policy. The objects for which the network device operates according to the received instructions include at least one of the following: 1. Specific databases or folders or documents (such as mirror documents) or storage spaces (such as sector intervals) in the local storage area chip, user terminal, and server of the network device; 2. Local peripheral modules, such as positioning modules, sensor modules, audio-video source modules, and human-computer interaction modules. In an embodiment of the present application, the network device responds to instructions or data sent by the target device according to instructions such as response operations, second binding interaction systems, or data source policies. For example, the network device responds to the data packet of the data receiving OUT endpoint of the USB token packet sent by the target device, writes the data packet into the storage space, and uploads the data in the storage space at the IN endpoint. It should be noted that the above method for the network device to respond to the instructions or data sent by the target device is an automatic response method. For example, according to the instructions of the target device, it automatically reads and writes the bound data source without manual intervention during the reading and writing process. In another embodiment of the present application, the network device executes the response operation of the instruction at the interaction interface of the client and the server according to instructions such as response operations, second binding interaction systems, or data source policies. For example, when the network device is a keyboard device, when the target device sends a USB token packet for a request (such as an IN token), the user can input the character "A" on the interaction interface of the user side, and the network device returns the data packet of the character "A" to the target device at the IN endpoint, realizing the interaction with the target device through manual operation. The following takes the scenario of a USB flash drive with the network device (slave mode) as an example to illustrate the data exchange method in this embodiment. Step S1101 further includes: configuring the data exchange configuration information of the USB flash drive. Specifically, when configuring the data exchange configuration information, one or more of the following response operation instructions are configured: maximum logical unit number, total number of formatable logical blocks; last logical block address; block capacity size; read / write status; USB communication protocol instruction; SCSI transparent command set instruction; document operation instruction, which is used to respond to the corresponding instruction of the target device. One or more of the following binding interaction systems or data source policy instructions are configured: configuring the binding relationship of the data source. The data source can be located locally on the network device, on the server, on the user side, on the control side, etc. For example, when the data source is bound to the server data source, the read / write sector instruction sent by the target device is mapped to the storage space of the server (such as a specific sector interval or mirror document), so that the data for the target device to perform read / write operations is the data source of the server. The automatic execution instruction response operation script is configured as: a default backup script, which is used to back up the written data. One or more of the following binding interaction systems or data source policy instructions are configured: when the location data in the positioning module is not in a specific location area, the user side and the server are prohibited from sending the data of the read sector address in the "sector read instruction" to the target device. In an embodiment of the present application, after the networking device and the target device are successfully enumerated, step S110...

Claims

1. A device access method, applied to a networked device, the method comprising: When a communication connection is established with the server, a target configuration message is preloaded. The server stores at least one preset configuration message. The target configuration message is used to redefine the function of the network device when it accesses the target device. The target configuration message is one of the preset configuration messages. The target configuration message includes scenario configuration messages of the network device in one or more application scenarios. The scenario configuration message includes a first descriptor set and / or a descriptor instruction set. The first descriptor set or the descriptor instruction set is used to define the device function of the network device. The communication data between the network device and the server does not pass through the target device during the device access phase. Based on the target scenario configuration message, a communication connection is established with the target device to enable the network device to access the target device. The target scenario configuration message is one of the scenario configuration messages. The preloading of the target configuration message includes: sending a configuration acquisition request to the server, the configuration acquisition request carrying the identification message of the network device; and receiving the target configuration message corresponding to the identification message returned by the server. Alternatively, a configuration request data can be sent to the server, and a target scenario configuration message corresponding to the current application scenario parameters can be received from the server in response to the configuration request data. The configuration request data carries the identification information of the network device and the current application scenario parameters. The target scenario configuration message is the scenario configuration message corresponding to the current application scenario parameters in the target configuration messages determined based on the identification information. Alternatively, a configuration request data can be sent to the server, and a target configuration message corresponding to the target device can be received from the server in response to the configuration request data. The target device is a device identified by the server based on a descriptor subset that the network device enumeration fails. The configuration request data carries the descriptor subset of the target device. Alternatively, a configuration request data can be sent to the server, and a target configuration message corresponding to the target device can be received from the server in response to the configuration request data. The target device is an access device of unknown type identified by the server based on a descriptor subset. The configuration request data carries the descriptor subset of the target device. Alternatively, a configuration request data is sent to the server, and a target configuration message corresponding to the target device is received from the server in response to the configuration request data. The target device is the device that the network device enumeration successfully completed, and the target configuration message includes a driver instruction set.

2. The device access method as described in request item 1, wherein establishing a communication connection with the target device based on the target scenario configuration information includes: When the network device acts as a host device communicating with the target device, it enumerates various descriptors in the second descriptor set of the target device based on the function instruction set in the descriptor instruction set. The descriptor instruction set includes various function instruction sets used to control data exchange between the network device and the target device. If the enumeration is successful, the target data source for communication between the network device and the target device is configured, and the target data source is located on the target device. Alternatively, when the network device acts as a slave device communicating with the target device, it receives an enumeration request sent by the target device. In response to the enumeration request, it returns the first descriptor set to the target device so that the target device can enumerate the first descriptor set. After successful enumeration, the target data source for communication between the network device and the target device is configured according to the data source configuration message, and the target data source is located on the server. Alternatively, when the target device includes at least one first target device and at least one second target device, and the network device acts as a host device communicating with the first target device and as a slave device communicating with the second target device, it enumerates multiple descriptors in the second descriptor set of the first target device based on the function instruction set in the descriptor instruction set; if the enumeration is successful, it configures a first target data source when the network device communicates with the first target device to complete the communication connection with the first target device, wherein the first target data source is located in the first target device; it receives an enumeration request sent by the second target device; in response to the enumeration request, it returns the first descriptor set to the second target device so that the second target device can enumerate the first descriptor set, and after successful enumeration, it configures a second target data source when the network device communicates with the second target device according to the data source configuration message, wherein the second target data source is located in the server or the first target device.

3. The device access method as described in claim 2, wherein the functional instruction set includes an acquisition instruction set and a verification instruction set, and the step of enumerating multiple descriptors in the second descriptor set of the target device based on the functional instruction set in the descriptor instruction set includes: Based on the acquisition instruction set, read the second descriptor set of the target device; based on the verification instruction set, verify multiple descriptors in the second descriptor set; if multiple descriptors meet preset device requirements, the enumeration is determined to be successful; or, the function instruction set further includes a data source instruction set, the target scenario configuration message further includes a data source configuration message, and configuring the target data source when the network device communicates with the target device includes: based on the data source instruction set, determine the target data source when the network device communicates with the target device according to the data source configuration message.

4. The device access method as described in request item 2, wherein establishing a communication connection with the target device based on the target scenario configuration information includes: When the networked device is in network read / write control device mode, based on the functional instruction set in the descriptor instruction set, multiple descriptors in the second descriptor set of the target device are enumerated. If the enumeration is successful, a request is sent to the server to send the driver instruction set corresponding to the target device to complete the communication connection. The driver instruction set is used to exchange data with the target device. Alternatively, when the networked device is a network proxy control device, based on the functional instruction set in the descriptor instruction set, multiple descriptors in the second descriptor set of the target device are enumerated. If the enumeration is successful, the second descriptor set is sent to the server so that the target device is virtualized on the server, generating a virtual device corresponding to the target device, thereby establishing a communication connection with the target device.

5. The device access method as described in claim 4, wherein the data source configuration information includes data source capacity information, the capacity information including the last logical block address and block capacity of the data source; and / or, the second descriptor set includes at least one of device descriptor, configuration descriptor, interface descriptor, endpoint descriptor, string descriptor and preset custom descriptor.

6. The device access method as described in claim 1, the method further comprising: Based on at least one of a preset automatic selection strategy and a manual selection operation of an electronic device, a target application scenario is selected. The target configuration information includes target scenario configuration information corresponding to the target application scenario. The electronic device includes the network device, the target device, and / or a terminal device. The terminal device is a device that communicates with the network device through near-field communication or remote communication. The terminal device and the target device are different devices.

7. The device access method as described in claim 6, wherein the step of selecting based on at least one of a preset automatic selection strategy and a manual selection operation of an electronic device includes: In response to a user's selection operation on the display unit of the networked device, the application scenario indicated by the selection operation is taken as the target application scenario; Alternatively, in response to a pointer toggle operation on the physical switch of the networked device, the application scenario indicated by the pointer toggle operation is selected as the target application scenario; or, in response to a scenario selection operation of the terminal device, the application scenario indicated by the scenario selection operation is selected as the target application scenario; or, based on preset interaction data of the target device, the application scenario indicated by the preset interaction data is selected as the target application scenario; or, based on the location information of the networked device, the application scenario corresponding to the location information is selected as the target application scenario; or, based on a preset timer clock, the application scenario corresponding to the preset timer clock is selected as the target application scenario, wherein the preset timer clock includes a network timer clock or the local timer clock of the networked device.

8. The device access method as described in request item 1, wherein the scenario configuration information stored on the server is generated based on a preset generation strategy before preloading the target configuration information, by configuring at least one of the first descriptor set and the descriptor instruction set of the networked device, and the data source configuration information; wherein, If the preset generation strategy is a custom creation strategy and the network device is a host role, then the scene configuration message is generated by configuring the network device's descriptor instruction set and data source configuration message. The descriptor instruction set includes the function instruction set during host role enumeration, and the data source configuration message is used to bind the data source during data exchange between the network device and the target device. The data source includes mirrored storage data, specific folders, databases, and / or data streams. Alternatively, if the preset generation strategy is a custom creation strategy and the network device is a slave role, then the scene configuration message is generated by configuring the network device's first descriptor instruction set and data source configuration message. The first descriptor instruction set includes descriptor parameters and / or device type parameters used to reply to the host role. Alternatively, if the preset generation strategy is a custom creation strategy and the network device is both a host role and a slave role, then the scene configuration message is generated by configuring the network device's first descriptor instruction set, descriptor instruction set, and data source configuration message. Alternatively, if the preset generation strategy is a template creation strategy, then the scene configuration information is generated based on the preset scene template by configuring the descriptor instruction set and data source configuration information of the network device, or by configuring the first descriptor instruction set and data source configuration information of the network device, or by configuring the first descriptor instruction set, descriptor instruction set and data source configuration information of the network device.

9. The device access method as described in claim 1, wherein the power supply method of the networked device includes at least one of the following methods: when the networked device is connected to the target device, the networked device is powered by the power supply of the target device; the networked device is powered by its built-in power supply; or the networked device is powered by an external power supply.

10. The device access method as described in claim 1, further comprising, before preloading the target configuration information when communicating with the server: Based on preset server configuration information, a communication connection request is sent to the server to establish a communication connection. The preset server configuration information is stored in the networked device.

11. A data exchange method applied to a networked device, wherein the networked device establishes a communication connection with a server and a target device based on the device access method described in any one of requests 1 to 10, the method comprising: Obtain the data exchange request sent by the first target party; Based on a preset processing strategy, the data exchange request is responded to, and the target data is returned to the first target party. The target data is data sent by the second target party. If the first target party is the server, then the second target party is the target device. If the first target party is the target device, then the second target party is the server.

12. The data exchange method as described in claim 11, wherein the target device includes at least one first target device and at least one second target device, the network device serves as a host device communicatively connected to the first target device and as a slave device communicatively connected to the second target device, wherein if the first target is the server, then the second target is either the first target device or the second target device, and if the first target is the second target device, then the second target is either the server or the first target device.

13. The data exchange method as described in request item 11, wherein responding to the data exchange request based on a preset processing strategy and returning the target data to the first target party includes: In response to the data exchange request, the data exchange request is forwarded to the second target party; The system receives target data returned by the second target party in response to the data exchange request and forwards the target data to the first target party; or, based on a preset processing script, it processes the data exchange request to obtain a data processing result; based on the data processing result, it sends a target data acquisition request to the second target party; it receives target data corresponding to the data processing result returned by the second target party in response to the target data acquisition request and returns the target data to the first target party.

14. The data exchange method as described in claim 13, wherein forwarding the data exchange request to the second target party in response to the data exchange request includes: If the networked device is a large-capacity storage device and the second target is a server, then the data exchange request sent by the target device is forwarded to the server. The data exchange request is used by the server to identify the target data corresponding to the data name or the first sector address of the data carried in the data exchange request, and to read the target data into the server's memory buffer according to the sector address of the target data, and to return the target data in the memory buffer to the networked device; and / or, if the networked device is a network proxy control device and the second target is a server, then the data exchange request sent by the target device is forwarded to the server. The data exchange request is used to read the target data corresponding to the data exchange request from the virtual device corresponding to the networked device in the server, and to return the target data to the networked device; And / or, if the networked device is a network intermediate control device and the second target is a server, then the data exchange request sent by the target device is forwarded to the server. The data exchange request is used by the server to process the data to be processed carried in the data exchange request and return target data corresponding to the data to be processed to the networked device. The target data is the data calculated by the server on the data to be processed, or the calculation model data corresponding to the data to be processed; and / or, if the networked device is a network USBkey device and the second target is a server, then the data exchange request is forwarded to the server. The data exchange request carries the credential information of the network USBkey device so that the server can verify the credential information.

15. The data exchange method as described in claim 11, wherein the communication data between the network device and the server does not pass through the target device during the data exchange phase.

16. A device access method, applied to a server, wherein the server stores at least one preset configuration message, the method comprising: When communicating with a networked device, a target configuration message is sent to the networked device. The target configuration message is used to redefine the function of the networked device when accessing the target device, and to establish a communication connection between the networked device and the target device, so that the networked device can access the target device. The communication data between the networked device and the server does not pass through the target device during the device access phase. The target configuration message is one of the preset configuration messages. The target configuration message includes scenario configuration messages of the networked device in one or more application scenarios. The scenario configuration message includes a first descriptor set and / or a descriptor instruction set. The first descriptor set or the descriptor instruction set is used to define the device function of the networked device. The step of sending the target configuration message to the networked device includes: responding to a configuration acquisition request sent by the networked device, sending a target configuration message corresponding to the identification message to the networked device. The configuration acquisition request carries the identification message of the networked device. Alternatively, in response to the configuration request data sent by the network device, a target configuration message corresponding to the identification message is determined, and a target scenario configuration message corresponding to the current application scenario parameters in the target configuration message is sent to the network device. The configuration request data carries the identification message of the network device and the current application scenario parameters. Alternatively, in response to the configuration request data sent by the network device, a descriptor subset of the target device is identified, and a target configuration message corresponding to the target device is sent to the network device. The configuration request data carries the descriptor subset of the target device, and the target device is a device that the network device failed to enumerate. Alternatively, in response to the configuration request data sent by the network device, a descriptor subset of the target device is identified, and a target configuration message corresponding to the target device is sent to the network device. The configuration request data carries the descriptor subset of the target device, and the target device is an access device of an unknown type. Alternatively, in response to the configuration request data sent by the network device, a target configuration message corresponding to the target device is sent to the network device. The target device is a device that the network device successfully enumerated, and the target configuration message includes a driver instruction set.

17. The device access method as described in claim 16 further includes at least one of the following methods: authorizing a communication relationship with the networked device; and terminating a communication relationship with the networked device.

18. The device access method as described in claim 16, further comprising, after sending the target configuration message to the networked device: Receive the set of descriptors of the target device sent by the networked device; Based on the virtual bus approach, the received descriptor set is virtualized into a virtual device.

19. The device access method as described in claim 16, further comprising, after sending the target configuration message to the networked device: Receive verification data sent by the networked device, wherein the verification data includes at least one of the descriptive subset of the target device and the device type; If the data to be verified meets the preset conditions, then the target device is determined to be a device that is allowed to exchange data with the networked device.

20. The device access method as described in claim 16, further comprising, before sending the target configuration message to the networked device: In response to a scenario selection instruction sent by a user equipment, the application scenario indicated by the scenario selection instruction is selected as the target application scenario. The target configuration information includes the target scenario configuration information corresponding to the target application scenario. The user equipment is a device that accesses the server.

21. The device access method as described in claim 16, wherein the target configuration information includes target scenario configuration information corresponding to the target application scenario, wherein the target application scenario is selected based on manual selection operation of the electronic device, or selected based on a preset automatic selection strategy, or selected through access to the server by the user device; the electronic device includes the network device, the target device and / or the terminal device, wherein the terminal device is a device that communicates with the network device through near-field communication or remote communication, and the terminal device and the target device are different devices.

22. The device access method as described in request item 16, wherein the scenario configuration information stored on the server is generated based on a preset generation strategy before preloading the target configuration information, by configuring at least one of the first descriptor set and the descriptor instruction set of the networked device, and the data source configuration information; wherein, If the preset generation strategy is a custom creation strategy and the network device is a host role, then the scene configuration message is generated by configuring the network device's descriptor instruction set and data source configuration message. The descriptor instruction set includes the function instruction set during host role enumeration, and the data source configuration message is used to bind the data source during data exchange between the network device and the target device. The data source includes mirrored storage data, specific folders, databases, and / or data streams. Alternatively, if the preset generation strategy is a custom creation strategy and the network device is a slave role, then the scene configuration message is generated by configuring the network device's first descriptor instruction set and data source configuration message. The first descriptor instruction set includes descriptor parameters and / or device type parameters used to reply to the host role. Alternatively, if the preset generation strategy is a custom creation strategy and the network device is both a host role and a slave role, then the scene configuration message is generated by configuring the network device's first descriptor instruction set, descriptor instruction set, and data source configuration message. Alternatively, if the preset generation strategy is a template creation strategy, then the scene configuration information is generated based on the preset scene template by configuring the descriptor instruction set and data source configuration information of the network device, or by configuring the first descriptor instruction set and data source configuration information of the network device, or by configuring the first descriptor instruction set, descriptor instruction set and data source configuration information of the network device.

23. A data exchange method applied to a server, wherein the server establishes a communication connection with a networked device based on the device access method described in any one of requests 16 to 22, the method comprising: Sending a data exchange request to the networked device and receiving target data returned by the networked device, wherein the data exchange request is used by the networked device to respond to the data exchange request based on a preset processing strategy, and the target data is data sent by the target device; and / or, sending target data to the networked device according to the data exchange request responded to by the networked device based on the preset processing strategy, wherein the target data is returned by the networked device to the target device, and the data exchange request is initiated by the target device.

24. The data exchange method as described in claim 23, wherein sending target data to the network device according to the data exchange request responded to by the network device based on a preset processing strategy includes: If the network device is a large-capacity storage device, then in response to the data exchange request forwarded by the network device, the target data corresponding to the data name or the first sector address of the data carried in the data exchange request is identified, and the target data is read into the memory buffer of the server according to the sector address of the target data, and the target data in the memory buffer is returned to the network device; and / or, if the network device is a network proxy control device, then in response to the data exchange request forwarded by the network device, the target data corresponding to the data exchange request is read from the virtual device corresponding to the network device in the server, and the target data is returned to the network device; and / or, if the network device is a network intermediate control device, then in response to the data exchange request forwarded by the network device, the data to be processed carried in the data exchange request is processed, and the target data corresponding to the data to be processed is returned to the network device, wherein the target data is the data calculated by the server on the data to be processed, or the calculation model data corresponding to the data to be processed; And / or, if the networked device is a USBkey device, then in response to the data exchange request forwarded by the networked device, the credential information carried in the data exchange request is verified, and target data regarding the verification result is sent to the networked device, wherein the credential information is the credential information of the networked device.

25. A device access apparatus for use in networked devices, the apparatus comprising: A preloading module is used to preload target configuration information when communicating with a server. The server stores at least one preset configuration message. The target configuration message is used to redefine the function of the network device when accessing a target device. The target configuration message is one of the preset configuration messages. The target configuration message includes scenario configuration information of the network device in one or more application scenarios. The scenario configuration message includes a first descriptor set and / or a descriptor instruction set. The first descriptor set or the descriptor instruction set is used to define the device function of the network device. The communication data between the server and the network device does not pass through the target device during the device access phase. The preloading of the target configuration message includes: sending a configuration acquisition request to the server, the configuration acquisition request carrying the identification information of the network device; and receiving the target configuration message corresponding to the identification information returned by the server. Alternatively, a configuration request data can be sent to the server, and a target scenario configuration message corresponding to the current application scenario parameters can be received from the server in response to the configuration request data. The configuration request data carries the identification information of the network device and the current application scenario parameters. The target scenario configuration message is the scenario configuration message corresponding to the current application scenario parameters in the target configuration messages determined based on the identification information. Alternatively, a configuration request data can be sent to the server, and a target configuration message corresponding to the target device can be received from the server in response to the configuration request data. The target device is a device identified by the server based on a descriptor subset that the network device enumeration fails. The configuration request data carries the descriptor subset of the target device. Alternatively, a configuration request data can be sent to the server, and a target configuration message corresponding to the target device can be received from the server in response to the configuration request data. The target device is an access device of unknown type identified by the server based on a descriptor subset. The configuration request data carries the descriptor subset of the target device. Alternatively, a configuration request data is sent to the server, and a target configuration message corresponding to the target device is received from the server in response to the configuration request data. The target device is a device that has been successfully enumerated by the network device, and the target configuration message includes a driver instruction set. A connection establishment module is used to establish a communication connection with the target device based on the target scenario configuration message, so that the network device can access the target device. The target scenario configuration message is one of the scenario configuration messages.

26. A data exchange apparatus applied to a networked device, the networked device communicating with a server and a target device based on the device access method described in any one of requests 1 to 10, the apparatus comprising: The acquisition module is used to acquire data exchange requests sent by the first target party; The return module is used to respond to the data exchange request based on a preset processing strategy and return the target data to the first target party, wherein the target data is data sent by the second target party, wherein if the first target party is the server, then the second target party is the target device, and if the first target party is the target device, then the second target party is the server.

27. A device access apparatus, applied to a server, the server storing at least one preset configuration message, the apparatus comprising: The distribution module is used to distribute target configuration information to a network device when a communication connection is established. The target configuration information redefines the functionality of the network device when accessing the target device and establishes a communication connection between the network device and the target device, enabling the network device to access the target device. Communication data between the server and the network device does not pass through the target device during the device access phase. Distributing the target configuration information to the network device includes: responding to a configuration retrieval request sent by the network device, distributing a target configuration information corresponding to an identification message to the network device, wherein the configuration retrieval request carries the identification message of the network device; or, responding to configuration request data sent by the network device, determining a target configuration information corresponding to the identification message, and distributing a target scenario configuration information corresponding to the current application scenario parameters from the target configuration information to the network device, wherein the configuration request data carries the identification message of the network device and the current application scenario parameters. Alternatively, in response to configuration request data sent by the network device, a descriptor subset of the target device is identified, and a target configuration message corresponding to the target device is sent to the network device. The configuration request data carries the descriptor subset of the target device, and the target device is a device that the network device failed to enumerate. Alternatively, in response to configuration request data sent by the network device, a descriptor subset of the target device is identified, and a target configuration message corresponding to the target device is sent to the network device. The configuration request data carries the descriptor subset of the target device, and the target device is an access device of an unknown type. Alternatively, in response to configuration request data sent by the network device, a target configuration message corresponding to the target device is sent to the network device. The target device is a device that the network device successfully enumerated, and the target configuration message includes a driver instruction set. The target configuration message is one of the preset configuration messages. The target configuration message includes scenario configuration information for the network device in one or more application scenarios. The scenario configuration message includes a first descriptor subset and / or a descriptor instruction set, and the first descriptor subset or the descriptor instruction set is used to define the device functions of the network device.

28. A data exchange apparatus, applied to a server, wherein the server establishes a communication connection with a networked device based on the device access method described in any one of requests 16 to 22, the apparatus comprising: A transceiver module is configured to send a data exchange request to the networked device and receive target data returned by the networked device. The data exchange request is used by the networked device to respond to the data exchange request based on a preset processing strategy. The target data is data sent by the target device. And / or, a response module is configured to send the target data to the networked device according to the data exchange request responded to by the networked device based on the preset processing strategy. The target data is returned by the networked device to the target device. The data exchange request is initiated by the target device.

29. A networking device, comprising a processor and a memory, the memory for storing a computer program that, when executed by the processor, implements a device access method as described in any one of claims 1 to 10, or a data exchange method as described in any one of claims 11 to 15.

30. A server comprising a processor and a memory, the server being capable of implementing the device access method as described in any one of claims 16 to 22, or the data exchange method as described in any one of claims 23 to 24.

31. A computer-readable storage medium storing a computer program that, when executed by a processor, implements a device access method as described in any one of claims 1 to 10, 16 to 22, or a data exchange method as described in any one of claims 11 to 15, 23 to 24.

Images