Network sharing methods and display devices

Abstract

This application discloses a network sharing method and a display device. The method is based on a USB master-slave hardware connection. After device information verification and matching, the first virtual network interface is enabled, which breaks through the technical bottleneck of traditional USB master-slave technology, which can only perform basic data transmission and cannot build network links. At the same time, the interface is set as a gateway and the second system is assigned an IP address in the same network segment through the DHCP protocol. A dedicated network link is built based on the USB physical link, realizing the collaborative networking of multiple display device systems based on a single USB interface, as well as the network collaborative sharing between multiple systems.

Description

Technical Field

[0001] This application relates to the field of display, and more particularly to a network sharing method and display device. Background Technology

[0002] As the functional requirements of display devices (such as televisions and electronic whiteboards) continue to expand, a single operating system can no longer meet the demands of diverse scenarios, and their internal architecture is gradually evolving towards a multi-system integrated form. Taking television as an example, its multi-system integrated architecture includes two core modules: the television system is built on Android and is mainly responsible for interactive operation, basic business and peripheral access management; the computing power system runs on Linux or a customized Android system, equipped with independent hardware, and undertakes high-performance computing power requirements.

[0003] Both types of systems need to form a complete business loop through high-frequency data interaction. To ensure network access stability, security, and ease of management, the overall device must present a single network interface, requiring network sharing between multiple systems. However, this is constrained by the limitations of USB master-slave interaction technology: when the TV system or computing system acts as the master device, the Android system's built-in UsbHostManager can only perform basic management and control such as peripheral access and identification, lacking network layer protocol adaptation and communication link establishment capabilities. This makes it impossible to support collaborative sharing of network resources between the two systems, ultimately hindering the device from achieving collaborative networking of multiple systems under a single network interface. Summary of the Invention

[0004] This application provides a network sharing method and display device, which can solve the problem that the host device lacks network layer protocol adaptation and communication link establishment capabilities during USB network sharing, and therefore cannot support the collaborative sharing of network resources between two systems.

[0005] In a first aspect, a network sharing method is provided, applied to a display device, the display device including a first system and a second system, the first system and the second system being connected via USB cable communication; when the first system is configured in host mode and the second system is configured in slave mode, the first system is configured to: receive device information from the second system and create a first virtual network interface when establishing a USB communication connection with the second system, the first virtual network interface being in a closed state; if the device information of the second system matches the information in a preset device library, the state of the first virtual network interface is adjusted from closed state to enabled state; when the first virtual network interface is in the enabled state, the first virtual network interface is identified as a gateway, and an IP address within the same network segment as the gateway is assigned to the second system according to the DHCP protocol, and a USB network link is established with the second system.

[0006] The display device analyzes whether the device information of the second system matches the information in the preset device library. If the device information of the second system matches the information in the preset device library, the first system adjusts the state of the first virtual network interface from the closed state to the enabled state, that is, from Down to Up. This application, through the legality verification of the preset device library, enables the first virtual network interface (from Down to Up) only for the matching second system, establishing a stable link layer connectivity foundation for subsequent IP communication and data interaction between multiple systems.

[0007] Among them, the device information of the second system includes the manufacturer information of the second system, which identifies the hardware identity of the second system.

[0008] The first system can be a computing system using Linux / Android, or a TV system using Android; the second system is another type of system that is paired with the display device.

[0009] This method relies on the USB master-slave hardware connection, with the first system in the display system as the master and the second system as the slave. Through a device information verification mechanism during USB communication connection establishment, the legitimacy and compatibility of the second system are determined. The first virtual network interface is activated only when the device information matches the preset device library, overcoming the technical bottleneck of traditional USB master-slave systems which can only achieve basic data transmission and cannot build stable network links. Simultaneously, the activated first virtual network interface is set as a gateway, and an IP address in the same network segment is assigned to the second system using the DHCP protocol. A dedicated USB network link is built using the USB physical link, allowing multiple systems to form a unified network segment environment. This achieves network collaboration and sharing among multiple systems, realizing the transformation of USB master-slave interaction from data transmission to network link construction.

[0010] In one possible implementation, with the first system configured in host mode and the second system configured in slave mode, the second system is configured as follows: simulating a USB virtual network adapter; creating a second virtual network interface when establishing a USB communication connection with the first system, with the second virtual network interface in a closed state; receiving a USB device enumeration request initiated by the first system and sending the device information of the second system to the first system; after detecting that the USB network link with the first system has been initialized, changing the state of the second virtual network interface from closed to enabled; obtaining an IP address from the first system according to the DHCP protocol, configuring an IP address for the second virtual network interface, and establishing a USB network link with the first system.

[0011] In this application, the second system simulates the hardware transmission foundation for the USB virtual network card; then, by creating and enabling the second virtual network interface as needed, a usable logical entry point is prepared for network interaction; USB enumeration is completed to enable normal communication at the protocol layer; and with the precise matching of the roles of the master and slave system DHCP server / client, it is ensured that the IP can be properly allocated and configured to the enabled virtual interface, ultimately enabling the USB physical link to have network layer communication capabilities, realizing a stable network connection between the two systems based on the USB link. At the same time, relying on the physical characteristics of USB and standard protocols, it also achieves the extended effects of highly stable data interaction and automated configuration.

[0012] In one possible implementation, the second system includes a device manager and an Ethernet service; when establishing a USB communication connection with the first system, a second virtual network interface is created, namely: when establishing a USB communication connection with the first system, the device manager creates a second virtual network interface.

[0013] After detecting that the USB network link with the first system has been initialized, the state of the second virtual network interface is changed from the closed state to the enabled state; after the Ethernet service detects that the USB network link with the first system has been initialized, the state of the second virtual network interface is changed from the closed state to the enabled state.

[0014] The second system also includes a DHCP client; after the Ethernet service detects that the USB network link with the first system has been initialized, the state of the second virtual network interface is changed from the closed state to the enabled state, and the DHCP client is started.

[0015] In this application, when the Ethernet service detects that the second virtual network interface is enabled in the second system of the slave device, the second system, acting as a DHCP client, initiates an IP address request to the first system, which is the DHCP server, through the enabled second virtual network interface. This logic replaces the original logic of the slave device. The original startTethering logic shares the local network with external devices, while in this application embodiment, the second system, as the slave device, only acts as the network being shared, completing network access as a DHCP client.

[0016] In one possible implementation, the first system includes a host manager and a shared network service; when establishing a USB communication connection with the second system, it receives device information from the second system and creates a first virtual network interface, specifically: when establishing a USB communication connection with the second system, the host manager receives device information from the second system and creates a first virtual network interface; the host manager broadcasts the device information from the second system. If the device information of the second system matches the information in the preset device library, the state of the first virtual network interface is changed from the closed state to the enabled state. The shared network service receives the device information of the second system. If the device information of the second system matches the information in the preset device library, the shared network service changes the state of the first virtual network interface from the closed state to the enabled state.

[0017] In this application, the preset manufacturer database contains only all device information that the second system may involve. Through matching and verification, unauthorized USB devices can be directly filtered out to prevent these devices from triggering incorrect network sharing logic, prevent unauthorized devices from accessing the system network, and ensure the security of communication between multiple systems in the display device.

[0018] In one possible implementation, the USB cable can be a USB-C cable or a USB-C dual-role cable to improve the stability, flexibility, and compatibility of data transmission between systems, while also adapting to the interaction requirements of the first and second systems. In one possible implementation, the display device also includes a third system configured as a slave, wherein the hardware of the first system is connected to the hardware of the third system via a USB cable.

[0019] The first system is a television system, while the second and third systems are computing power systems. The hardware of the first system communicates directly with the hardware of the second and third systems via independent USB cables.

[0020] In a second aspect, a display device is provided, including a display, a memory, a controller, and a computer program stored in the memory and executable on the controller, wherein the controller executes the computer program to implement the network sharing method of any of the first aspects.

[0021] Thirdly, a network sharing device is provided, including a unit for performing any of the methods in the first aspect. This device may be a terminal device or a chip within a terminal device.

[0022] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when run by a network sharing device, causes the network sharing device to perform any of the network sharing methods described in the first aspect.

[0023] Fifthly, a computer program product is provided, comprising: a computer program that, when run by a network sharing device, causes the network sharing device to perform any of the network sharing methods described in the first aspect.

[0024] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

[0025] Figure 1 A schematic diagram illustrating an application scenario for USB network sharing is shown; Figure 2 A configuration block diagram of a display device provided in an embodiment of this application is shown; Figure 3 This application provides a schematic diagram of a multi-system architecture within a display device. Figure 4 This application provides a schematic diagram of a multi-system architecture within a display device. Figure 5 A block diagram of a first system in a display device according to an embodiment of this application is shown; Figure 6 A flowchart of a network sharing method provided in an embodiment of this application is shown; Figure 7 A flowchart of yet another network sharing method provided by some embodiments of this application is shown; Figure 8 This application illustrates a schematic diagram of the overall architecture of multiple systems within a display device according to some embodiments; Figure 9 A flowchart of yet another network sharing method provided by some embodiments of this application is shown; Figure 10 A flowchart of yet another network sharing method provided by some embodiments of this application is shown; Figure 11 A schematic diagram of a network sharing device provided in some embodiments of this application is shown. Detailed Implementation

[0026] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0027] To better understand the embodiments of this application, the terms or concepts that may be involved in the embodiments are explained below.

[0028] (1) USB Tethering USB tethering is a technology that uses a USB cable to share the internet (mobile data or Wi-Fi) connection of one device with another device, based on protocols such as RNDIS or NCM.

[0029] In the communication architecture of USB network sharing, the two connected devices are clearly divided into two roles, with clear division of labor, and work together to complete the transmission and sharing of network data.

[0030] The first role is that of a slave device (USB Device, or simply Device), also known as a device end. It is a passive device that provides functions or data and may require power and control from the host to function. This device initiates device enumeration, configuration, and data transfer requests from the master device, and only responds to the master device's instructions. It cannot actively initiate communication. Mobile phones, USB flash drives, keyboards, mice, etc., used when sharing a network all belong to this type of device.

[0031] The second role is the master device (USB Host), also known as the host unit. It actively controls and manages the entire USB bus, responsible for powering slave devices, identifying devices, and loading corresponding drivers. This device can proactively initiate device enumeration, obtain device function descriptors, and lead the initiation and scheduling of data transmission. It is the core controller in the USB communication link. Personal computers (PCs), laptops, and mobile phones or tablets acting as master devices all fall into this category.

[0032] (2) Remote Network Driver Interface Specification (RNDIS) RNDIS is a protocol spearheaded by Microsoft that simulates Ethernet devices on the USB bus. By building a TCP / IP over USB transmission channel, it enables USB devices with network sharing capabilities (such as mobile phones and tablets) to be recognized as a standard Ethernet network card when connected to a host device, thereby achieving network data transmission between devices.

[0033] The significant advantage of this protocol is that Windows systems natively support it, requiring no additional driver installation. Therefore, it is widely used in scenarios where mobile phones and tablets share mobile data or Wi-Fi connections with Windows PCs.

[0034] (3) Network Control Model (NCM) NCM is a standardized protocol developed by USB-IF (USB Implementers Forum) specifically for implementing network data transmission on the USB bus. As a lightweight protocol designed for USB network devices, its core objective is to enable USB devices to be recognized by the host device as a standard network interface, thereby completing network sharing or data communication between devices.

[0035] This protocol is natively supported in Linux and Android systems and does not require additional driver installation. Therefore, it is widely used in scenarios where 4G / 5G mobile data terminals (4G / 5G Dongles) share the network with industrial equipment, tablets and other terminals.

[0036] Before providing a detailed explanation of the network sharing method and display device provided in the embodiments of this application, the application scenarios and related technologies of the network sharing method and display device will be explained first.

[0037] Figure 1 The diagram illustrates application scenarios for USB network sharing, covering both classic and extended scenarios. Its core technical logic provides a basic reference for addressing network interaction issues among multiple system display devices.

[0038] like Figure 1 As shown in (a), in the classic mobile phone (Device) → PC (Host) USB network sharing solution, the Android phone acts as the slave device, managing the underlying USB physical connection through the system's built-in UsbDeviceManager, and the network sharing function is implemented by the TetheringService core service. Based on protocols such as RNDIS, the Android phone virtualizes itself as a USB network adapter, providing network sharing services and state synchronization capabilities to the PC, which acts as the master device. This solution is a basic function natively supported by Android devices, possessing mature protocol adaptation and system compatibility.

[0039] UsbDeviceManager is a core service in the Android system responsible for managing the functions of slave devices. Its main responsibilities are to handle connection enumeration, function configuration, and data channel management after an Android device switches to slave mode.

[0040] TetheringService is a core service in the Android system responsible for managing network sharing functions. It can realize network link reuse, bandwidth allocation, connection status monitoring and abnormal recovery; it can support various network sharing scenarios such as USB, Wi-Fi hotspot, and Bluetooth.

[0041] With the improvement of Android device hardware performance and the rapid popularization of scenarios such as the Internet of Things (IoT) and edge computing, the mode of Android devices as slave devices can no longer meet diverse needs. The demand for Android devices to assume the role of master devices, connect to various peripherals and realize functional expansion has increased significantly, thus giving rise to the role reversal scenario of USB network sharing.

[0042] like Figure 1As shown in (b) of the diagram, in the extended scenario, the solution implements a USB master-slave role reversal: the Android phone acts as the master device, running in conjunction with the system's built-in UsbHostManager and TetheringService, connecting to peripherals supporting NCM / RNDIS, such as 4G / 5G Dongles and other Android devices, via USB cables, thereby enabling the reuse of peripheral network resources or network access for peripherals. UsbHostManager is a core service in the Android system responsible for managing the master device's functions. It primarily handles the connection, identification, permission allocation, and basic communication management between the Android device as the master and peripherals (such as USB flash drives, mice, keyboards, cameras, virtual USB network adapters, and other Android devices).

[0043] However, this role-reversal mode has obvious technical limitations: UsbHostManager's functional boundaries only cover peripheral access identification, basic permission control, and driver adaptation, lacking network layer protocol adaptation and link scheduling capabilities. Even if it successfully identifies a peripheral that has been virtualized as a USB network card (such as other Android devices or USB virtual network cards), it can only complete the physical layer connection initialization and cannot directly establish a network layer communication link.

[0044] The aforementioned technical logic of USB master-slave interaction and network sharing is highly similar in the multi-system integration architecture of display devices such as TVs, electronic whiteboards, and smart conference screens. Currently, the functional requirements of these display devices are becoming increasingly diverse. They need to possess basic business capabilities such as smooth human-computer interaction, audio and video playback, and screen projection collaboration, while also supporting high-performance computing demands such as high-definition video encoding and decoding, AI image recognition, and multi-device collaborative computing. A single operating system can no longer meet these needs, therefore, the internal architecture is generally evolving towards multi-system integration.

[0045] Taking television as an example, the multi-system integration architecture includes two core modules: one is the television system, which mostly uses the Android system and is mainly responsible for realizing human-computer interaction (such as touch control and remote control response), basic business functions (such as live broadcast, on-demand, and screen casting), and peripheral device access (such as USB and HDMI devices), with good compatibility and interactive experience; the other is the computing power system, which mostly uses the Linux system or the Android system and is equipped with an independent processor and memory module, specifically to support high-performance computing power requirements, such as high-definition video processing, AI algorithm operation, and big data caching, providing computing power support for the complex functions of the device.

[0046] The two systems do not operate independently but have high-frequency data interaction needs. For example, the television system needs to transmit screen projection data, touch commands, and peripheral access information to the computing system for processing. The computing system, in turn, needs to feed back the processed video signal and calculation results to the television system for display output, forming a complete business loop. Meanwhile, to ensure the stability, security, and ease of management of device network access, the overall system needs to present a single internet connection interface to the outside world. This avoids problems such as network conflicts, data synchronization disorder, and bandwidth waste caused by independent networking of the two systems. This requires achieving network sharing between the two systems, that is, enabling collaborative networking of the two systems through a single network entry point, while ensuring that data interaction between the systems and external network access do not interfere with each other.

[0047] However, considering the bottlenecks in USB master-slave interaction technology mentioned earlier, the network sharing needs of multi-system display devices like televisions also face similar technical challenges. In multi-system network sharing scenarios, either the television system or the computing system can act as the master device and provide network sharing services. Taking the Android system (with a similar logic to the Linux system) as an example, its built-in UsbHostManager has clear functional boundaries. It can only complete external device access detection, type identification, basic permission management, and driver adaptation, lacking network layer protocol adaptation, link establishment, and dynamic scheduling capabilities. Even if UsbHostManager successfully identifies the virtual USB network card device of the other system, it can only complete the physical layer connection initialization, unable to establish an effective network layer communication link, let alone support the collaborative sharing of network resources between the two systems, directly hindering the realization of the goal of multi-system collaborative networking under a single network interface.

[0048] In view of this, this application provides a network sharing method and display device. This method relies on a USB master-slave hardware connection, with the first system in the display system as the master and the second system as the slave. Through a device information verification mechanism when establishing a USB communication connection, the legitimacy and compatibility of the second system are determined. The first virtual network interface is only activated when the device information matches a preset device library, overcoming the technical bottleneck of traditional USB master-slave systems which can only achieve basic data transmission and cannot build stable network links. Simultaneously, the activated first virtual network interface is set as a gateway, and a DHCP protocol is used to allocate IP addresses in the same network segment to the second system. A dedicated USB network link is built using the USB physical link. This achieves collaborative networking between the first and second systems in the display device based on a single USB interface, and through the configuration of the gateway and IP addresses in the same network segment, multiple systems form a unified network segment environment, achieving network collaborative sharing between multiple systems. This realizes the technology of USB master-slave interaction from data transmission to network link construction, ensuring the stability of multi-system network collaborative sharing and the convenience of single-interface networking.

[0049] The display device provided in this application can have various implementation forms, such as a television, a smart television, a laser projection device, a monitor, an electronic bulletin board, an electronic table, etc.

[0050] Figure 2 A configuration block diagram of a display device provided in an embodiment of this application is shown, such as... Figure 2 As shown, the display device 200 includes at least one of the following: a tuner 210, a communicator 220, a detector 230, an external device interface 240, a controller 250, a display 260, an audio output interface, a memory, a power supply, and a user interface.

[0051] In some embodiments, the controller includes a processor, a video processor, an audio processor, a graphics processor, RAM, ROM, and a first interface to an nth interface for input / output.

[0052] The display 260 includes a display screen assembly for presenting images, a driving assembly for driving image display, a component for receiving image signals output from a controller, and a user interface (UI) for displaying video content, image content, and a menu control interface. The display 260 can be a liquid crystal display, an OLED display, or a projection display, and can also be a projection device and a projection screen.

[0053] The communicator 220 is a component used to communicate with external devices or servers according to various communication protocol types. For example, the communicator may include at least one of the following: a Wi-Fi module, a Bluetooth module, a wired Ethernet module, other network communication protocol chips or near-field communication protocol chips, and an infrared receiver.

[0054] The communicator 200 also includes components for enabling communication between systems within the device according to the USB communication protocol type. For example, the communicator may include a USB module with a USB input interface (USB), and the display device 200 can use the communicator 220 to enable data transfer and network sharing between systems within the device.

[0055] Detector 230 is used to collect signals from the external environment or to interact with the outside world. For example, detector 230 includes a sound collector, such as a microphone, for receiving external sounds.

[0056] External device interface 240 may include, but is not limited to, one or more interfaces such as: High Definition Multimedia Interface (HDMI), USB input interface, RGB port, etc.

[0057] The controller 250 controls the operation of the display device and responds to user operations through various software control programs stored in memory. The controller may include at least one of a central processing unit (CPU), a video processor, an audio processor, a graphics processing unit (GPU), random access memory (RAM), read-only memory (ROM), a first to nth interface for input / output, a communication bus, etc.

[0058] In some embodiments, the controller 250 and the tuner 210 may be located in different separate devices, that is, the tuner 210 may also be located in an external device of the main device where the controller 250 is located, such as an external set-top box.

[0059] Users can input commands through a graphical user interface (GUI) displayed on the monitor 260, and the user input interface receives the user input commands through the GUI. Alternatively, users can input commands by entering specific sounds or gestures, and the user input interface receives the user input commands by recognizing the sounds or gestures through sensors.

[0060] Figure 3 This application provides a schematic diagram of a multi-system architecture within a display device, as illustrated in an embodiment. Figure 3 As shown, the display device 300 may include a first system 310 and a second system 320. The two systems do not operate independently and have a high frequency of data interaction requirements. The hardware of the first system 310 and the hardware of the second system 320 are directly connected via USB cable, without relying on Wi-Fi or network cable for communication, thus improving the stability of the interaction between the systems.

[0061] In some embodiments, a plurality of second systems may be configured in the display device, such as second system A and second system B.

[0062] In some embodiments, the display device includes a first system, a second system, and a third system. For example, the first system is a television system, and the second and third systems are both computing systems. The hardware of the first system is directly and independently connected to the hardware of the second system and the hardware of the third system via USB cables.

[0063] In some embodiments, the USB cable used may be a USB-C cable or a USB-C dual-role cable to improve the stability, flexibility and compatibility of data transmission between systems, while adapting to the interaction requirements of the first system and the second system.

[0064] Among them, the USB-C cable is a universal serial bus transmission cable designed based on the USB Type-C interface standard. With its features of no reversible insertion, high-speed transmission (compatible with USB 3.0 and above protocols), and simple wiring, this cable can meet the data and command interaction needs between the first and second systems, ensuring stable transmission in normal scenarios. The USB-C dual-role cable is based on the USB Type-C Dual Role Port (DRP) specification, supporting dynamic switching of master / slave roles and bidirectional data transmission between the two devices (first and second systems). It can adapt to scenarios where the first and second systems interact flexibly. When there is a need for bidirectional command interaction between the first and second systems, transmission efficiency and system compatibility can be further optimized.

[0065] To ensure the stability, security, and ease of management of device network access, the overall system adopts a single network egress architecture, presenting only one internet access channel to the outside world. This channel can be provided by either the first or second system, thereby enabling the two systems to network collaboratively through a single network entry point, while ensuring that data interaction between the systems and external network access links are isolated from each other and do not interfere with each other.

[0066] For example, Figure 4 This illustration shows a schematic diagram of a multi-system architecture within a display device according to an embodiment of this application, using a television as an example. The television includes a television system (Android system) and a computing system (Linux system or Android system). Because the system type of the computing system (Linux / Android) is combined with the Android system of the television system, they are not compatible. Figure 1 The classic USB network sharing scenario shown in Figure (a) involves an Android device operating as a Device, sharing its mobile network or Ethernet link with the host device via the USB bus. Therefore, the roles and network architectures of each system need to be adapted and adjusted. The TV system or computing system can be configured as a host system and used as the system's sole internet connection entry point.

[0067] like Figure 4 As shown in (a), in the television 410, the television system 411 is configured as the host mode, making it the only external Internet connection entry point; the computing system 412 is configured as the slave (Device) mode, sharing the Internet connection of the television system 411 through the USB direct connection link with the television system 411, and finally completing the network sharing and status synchronization between the systems.

[0068] like Figure 4As shown in (b), in the television 420, the computing system 422 is configured as the host mode, making it the only external Internet connection entry point; the television system 421 is configured as the slave (Device) mode, sharing the Internet connection of the computing system 422 through a USB direct connection link with the computing system 422, and finally completing the network sharing and status synchronization between the systems.

[0069] It should be noted that Android and Linux are basically the same in terms of underlying architecture and core logic for USB network sharing. Figure 5 A block diagram of a first system in a display device according to an embodiment of this application is shown, with Android as an example for illustration.

[0070] like Figure 5 As shown, the first system is divided into four layers, from top to bottom: the Applications layer (referred to as the "Application Layer"), the Application Framework layer (referred to as the "Framework Layer"), the Android runtime and system library layer (referred to as the "System Runtime Library Layer"), and the kernel layer.

[0071] In some embodiments, at least one application runs in the application layer. These applications may be Windows programs, system settings programs, or clock programs that come with the operating system; they may also be applications developed by third-party developers. In specific implementations, the application packages in the application layer are not limited to the examples above.

[0072] The framework layer provides application programming interfaces (APIs) and a programming framework for applications. The application framework layer includes predefined functions. It acts as a central processing unit, determining the actions taken by applications within the application layer. Through the API, applications can access system resources and obtain system services during execution.

[0073] The Activity Manager manages the lifecycle of individual applications and common navigation and back functions, such as controlling application exit, opening, and navigating back. The Window Manager manages all windowed applications, such as obtaining screen size, determining if a status bar is present, locking the screen, capturing the screen, and controlling display window changes (e.g., shrinking the display window, shaking the display, distorting the display, etc.).

[0074] The system runtime library layer provides support for the upper layer, namely the framework layer. When the framework layer is used, the Android operating system will run the C / C++ libraries contained in the system runtime library layer to implement the functions that the framework layer needs to achieve.

[0075] The kernel layer is the layer between hardware and software. For example... Figure 5 As shown, the kernel layer includes at least one of the following drivers: audio driver, display driver, Bluetooth driver, USB driver, camera driver, Wi-Fi driver, HDMI driver, sensor driver, and power driver.

[0076] To facilitate a further understanding of the technical solutions in some embodiments of this application, the technical solutions of the network sharing method and how these solutions solve the aforementioned technical problems are described in detail below with reference to specific embodiments and accompanying drawings. The embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of this application.

[0077] Based on the hardware structure and system architecture of the display device provided in the above embodiments, the network sharing method provided in the embodiments of this application will be specifically described below with reference to the accompanying drawings.

[0078] Figure 6 A flowchart of a network sharing method provided in an embodiment of this application is shown, which is applied to the above. Figure 2 , Figure 3 , Figure 4 The display device shown includes a first system and a second system, which are connected via a USB cable for communication. Figure 6 As shown, when the first system is configured in master mode and the second system is configured in slave mode, the first system is configured to execute the following steps S610~S630: S610. When the first system establishes a USB communication connection with the second system, it receives device information from the second system and creates a first virtual network interface, which is in a closed state.

[0079] It should be noted that the hardware of the first system and the hardware of the second system are physically connected via a USB cable. After the display device is powered on, the first system and the second system will automatically establish a USB communication link and complete the link initialization. Subsequently, the first system and the second system send their own device information (i.e., the device information of the second system).

[0080] It should be noted that the device information of the second system is used to identify the hardware identity of the second system, such as the manufacturer information, device name, device identifier, hardware model, device serial number, hardware configuration parameters, and USB device identifier.

[0081] It should also be noted that the first virtual network interface created is in a down state.

[0082] Among them, the first virtual network interface (such as This is a dedicated channel for transmitting network data between the first system and the second system via a USB cable, and a logical entry point for processing USB network data within the first system. When this first virtual network interface is in the Down state, the channel is only physically connected but logically disconnected; it can only recognize that a USB device is connected, but cannot transmit any IP layer data (such as DHCP requests or network packets).

[0083] In this embodiment of the application, the first system may be a computing system using a Linux system / Android system, or a TV system using an Android system; the second system is another type of system that is paired with the display device.

[0084] S620. If the device information of the second system matches the information in the preset device library, the first system will change the status of the first virtual network interface from the closed state to the enabled state.

[0085] The display device can have a pre-stored preset device library, or it can obtain the preset device library from a server. The preset device library stores device information of each second system that can be shared with the first system via USB network, such as device information X, device information Y, and device information Z.

[0086] It should be noted that the USB port in the first system can be connected to other USB devices (such as USB flash drives), while in this embodiment, the preset manufacturer library only contains information on all devices that may be involved in the second system. Through matching and verification, unauthorized USB devices (such as USB flash drives) can be directly filtered out, preventing these devices from triggering incorrect network sharing logic, preventing unauthorized devices from accessing the system network, and ensuring the security of communication between multiple systems in the display device.

[0087] In some embodiments, during the use of the display device, a preset device library version verification request can be sent to the server according to a preset period to achieve regular updates of the preset device library.

[0088] The display device analyzes whether the device information of the second system matches the information in the preset device library. If the device information of the second system matches the information in the preset device library, the first system adjusts the status of the first virtual network interface from the closed state to the enabled state, that is, from Down to Up.

[0089] S630. When the first virtual network interface is enabled, the first system identifies the first virtual network interface as the gateway and assigns an IP address in the same network segment as the gateway to the second system according to the DHCP protocol, and establishes a USB network link with the second system.

[0090] When the first virtual network interface is set to the Up state, the channel is activated. The system can designate the first virtual network interface as the gateway (e.g., by configuring a static IP address) and assign an IP address within the same network segment as the gateway to the second system according to the DHCP protocol; load routing rules and enable data forwarding function, thereby realizing network data interconnection between multiple systems.

[0091] This application provides a network sharing method based on USB master-slave hardware connection. The method uses a first system in the display system as the master and a second system in the display system as the slave. By establishing a device information verification mechanism during USB communication connection establishment, the legitimacy and compatibility of the second system are determined. The first virtual network interface is only activated when the device information matches a preset device library, overcoming the technical bottleneck of traditional USB master-slave systems which can only achieve basic data transmission and cannot build stable network links. Simultaneously, the activated first virtual network interface is set as a gateway, and a DHCP protocol is used to allocate IP addresses in the same network segment to the second system. A dedicated USB network link is built using the USB physical link, allowing multiple systems to form a unified network segment environment. This achieves network collaborative sharing between multiple systems, realizing the technology of USB master-slave interaction from data transmission to network link construction.

[0092] The network sharing scheme described above was presented from the perspective of the first system. To achieve network sharing between the first and second systems in the display system, adjustments to the second system are also required. The following section will further explain the implementation process of this network sharing from the perspective of the second system.

[0093] Figure 7 A flowchart of yet another network sharing method provided in some embodiments of this application is shown, such as... Figure 7 As shown, when the first system is configured in master mode and the second system is configured in slave mode, the second system is configured to execute the following steps S710~S750: The S710 and the second system are simulated as a USB virtual network card.

[0094] The second system is simulated as a USB virtual network card. This allows the second system in slave mode to use the USB Gadget Framework to simulate its own hardware-level USB Device Controller (UDC) as a USB network card device. This enables the first system (host mode) to recognize it just like a physical network card, thereby achieving network communication between the two systems via the USB port.

[0095] For example, when the second system acts as a slave device, it needs to be configured by executing a series of commands through a run commands (rc) file to switch the device to a USB slave device and enable the NCM function. The specific operation process is as follows: (1) Stop the Android Debug Bridge (ADB) service.

[0096] (2) Enter the system USB Gadget configuration directory / config / usb_gadget, first set the UDC of instance g1 to none, and unbind the current UDC to allow modification of the configuration.

[0097] (3) Configure the string attribute of the b.1 configuration item under the g1 instance, set its configuration name to "NCM", and specify the function type of the USB configuration.

[0098] (4) Clean up the old function configurations in the g1 instance: delete the f1 function link under the b.1 configuration item, and clear all the original function files in the g1 / functions directory.

[0099] (5) Create the NCM function directory g1 / functions / ncm.usb0 and create a symbolic link between this directory and the f1 path under the b.1 configuration item to associate the NCM function with the current USB configuration.

[0100] (6) Write the specified UDC device node into the UDC configuration item of the g1 instance to complete the UDC binding, so that the Android device can officially run as a USB slave device in NCM mode.

[0101] S720: When the second system establishes a USB communication connection with the first system, it creates a second virtual network interface, which is in a closed state.

[0102] The second virtual network interface created by the second system is in a down state.

[0103] Among them, the second virtual network interface (such as This is a dedicated channel for transmitting network data between the first and second systems via a USB cable. It is also the logical entry point for processing USB network data within the second system. All network data packets transmitted via the USB link will enter and exit the second system through this interface.

[0104] The second virtual network interface is in the Down state to prevent it from receiving data before the interface has completed initialization, which could lead to network link abnormalities.

[0105] S730, the second system receives the USB device enumeration request initiated by the first system and sends the device information of the second system to the first system.

[0106] The first system will proactively initiate the USB device enumeration process (a standard procedure defined by the USB protocol). The second system responds to this request by sending its own device information (such as device type being a network device, supported protocol being NCM, manufacturer information / product identifier, etc.) to the first system, allowing the first system to identify and confirm that the second system is a "USB network card device".

[0107] It should be noted that the first system will only load the corresponding network card driver for the second system after the enumeration process of the USB device connection is completed, in order to prepare for the subsequent network link initialization.

[0108] S740: After detecting that the USB network link with the first system has been initialized, the second system changes the state of the second virtual network interface from the off state to the enabled state.

[0109] When the second system detects that the first system has completed initialization operations such as driver loading and link negotiation (e.g., the USB data channel has been established and both parties have confirmed support for the NCM protocol), the second system switches the status of the previously created second virtual network interface from the closed state to the enabled state, that is, from Down to Up. At this time, the second virtual network interface has the ability to send and receive data.

[0110] S750: When the second virtual network interface is enabled, the second system obtains an IP address from the first system according to the DHCP protocol, configures the IP address for the second virtual network interface, and establishes a USB network link with the first system.

[0111] When the second virtual network interface is enabled, the second system, acting as a DHCP client, initiates an IP address request to the first system (which needs to act as a DHCP server) through the enabled virtual network interface. After obtaining the IP address, it configures it on the virtual interface, establishing a network connection between the first and second systems based on a USB link, enabling normal network communication.

[0112] In this embodiment, when the second virtual network interface is enabled, the second system, acting as a DHCP client, initiates an IP address request to the first system, which is the DHCP server, through the enabled second virtual network interface. This logic replaces the native logic of the slave device. The native startTethering logic shares the local network with external devices, while in this embodiment, the second system, acting as the slave device, only acts as the network being shared, completing network access as a DHCP client.

[0113] Among them, startTethering is the core logic of native network sharing in the Android system. Its function is to share the device's own network (such as cellular, Wi-Fi, Ethernet) with external devices. It is the underlying implementation logic for enabling USB network sharing and hotspot sharing from the device.

[0114] The network sharing method provided in this application provides a hardware transmission foundation for a USB virtual network card through a second system simulation. Then, by creating and enabling a second virtual network interface as needed, a usable logical entry point is prepared for network interaction. USB enumeration enables normal communication at the protocol layer. Furthermore, with precise role matching between the master and slave systems' DHCP server / client, IP addresses are properly allocated and configured to the enabled virtual interface. Ultimately, the USB physical link acquires network layer communication capabilities, achieving a stable network connection between the two systems based on the USB link. Simultaneously, relying on the physical characteristics and standard protocols of USB, it achieves extended effects such as highly stable data interaction and automated configuration.

[0115] Based on the network sharing scheme introduced above, this section mainly describes in detail the network sharing between the first and second systems. The first system includes a host manager and a shared network service; the second system includes a device manager and an Ethernet service. The following sections will elaborate on the specific modules within each device. Other details can be found in the previous sections and will not be repeated here.

[0116] Figure 8 This application illustrates a schematic diagram of the overall architecture of multiple systems within a display device according to some embodiments, such as... Figure 8 As shown, the display system 800 includes a master device (first system 810) and a slave device (second system 820).

[0117] The first system 810 includes a host manager 811, a shared network service 812, a network daemon 813, a DHCP server 814, and an internet module 815.

[0118] For example, the host manager 811, namely UsbHostManager, is used to receive hardware events uevent sent by the kernel (such as USB device insertion / removal) and create the first virtual network interface (such as... ), and call the system TetheringService.

[0119] Shared network service 812, or TetheringService, is used for the first virtual network interface (e.g., The status of ) has been adjusted to the start state.

[0120] Network daemon (Netd) 813 is used to... Add to the NATForwarding Table.

[0121] DHCP server 814, or IpServer, assigns a static IP address (such as 192.0.2.1 / 24) to the first virtual network interface to identify it as the gateway, and assigns IP addresses (such as 192.0.2.10 / 24) to the second system in the same network segment as the gateway according to the DHCP protocol.

[0122] The Internet module 815 is a dedicated interface for the overall system at the device level to achieve external Internet connectivity. The first system directly connects to the external Internet through this module, while the second system shares this module with the first system via a USB direct connection link to complete data transmission and interaction. This module is the core entry point for the two types of systems to conduct network communication and data exchange with the external Internet.

[0123] like Figure 8 As shown, the second system 820 includes a device manager 821, an Ethernet service 822, and a DHCP client 823.

[0124] For example, after the device manager 821, namely UsbDeviceManager, detects that the class and subclass protocol of the USB interface match the CDC-NCM / RNDIS specification, it sends a notification to the EthernetService to add a link and creates a second virtual network interface (such as...). ).

[0125] Ethernet Service 822, or EthernetService, switches the status of the second virtual network interface from the off state to the enabled state, i.e., from Down to Up, and initiates a DHCP request through IpClient.

[0126] The DHCP client 823, also known as IpClient, obtains an IP address (such as 192.0.2.10 / 24) from the first system 810, configures the IP address for the second virtual network interface, and establishes a USB network link with the first system 810.

[0127] It should be noted that both the first and second systems have USB drivers. The first system also includes a USBDevice kernel driver, and the second system includes a USB Host kernel driver. The USB driver is used for physical layer communication adaptation and link infrastructure construction of USB cables. It is responsible for handling electrical signal interaction, data frame transmission and reception, and verification after the USB cable is connected, providing a reliable underlying transmission channel for upper-layer USB functions (such as device enumeration and data transmission). On this basis, the USBDevice kernel driver of the first system enables it to act as a USB slave device, which can be simulated as a virtual network card and other peripherals. The USBHost kernel driver of the second system enables it to act as a USB host, which can identify, enumerate, and manage connected USB slave devices.

[0128] Based on the preceding text Figure 6 The network sharing solution introduced can also be based on Figure 8 The modules of the first system in the display device shown interact with each other, and the following is a supplementary explanation.

[0129] Figure 9 A flowchart of yet another network sharing method provided in some embodiments of this application is shown, such as... Figure 9 As shown, when the first system is configured in host mode and the second system is configured in slave mode, each module in the first system (host manager and shared network service) is configured to execute the following steps S901~S910: S901, The first system and the second system establish a USB communication connection.

[0130] S902. When establishing a USB communication connection with the second system, the host manager receives device information from the second system.

[0131] S903, Host Manager creates the first virtual network interface.

[0132] S904, the host manager broadcasts device information from the second system, such as manufacturer information.

[0133] S905: After receiving the device information from the second system, the shared network service parses the device information.

[0134] S906, if the device information of the second system matches the preset device library, the shared network service will change the status of the first virtual network interface from the closed state to the enabled state.

[0135] In some embodiments, if the device information of the second system does not match the preset device library, the second system is ignored.

[0136] In some embodiments, step 906 further includes: if the device information of the second system matches the preset device library, the shared network service will further check whether a first virtual network interface exists; if the first virtual network interface exists, the state of the first virtual network interface will be changed from the closed state to the enabled state; if the first virtual network interface does not exist, an error log will be recorded; so as to improve the accuracy and security of the system.

[0137] S907, Shared network service starts the DHCP server.

[0138] S908, DHCP server allocates IP address pool.

[0139] The S909 and DHCP server assign IP addresses to the second system.

[0140] After receiving notification from the DHCP server that the IP address allocation is complete, the S910 shared network service configures a static IP address (as a gateway) for the usb01 interface, sets routing rules, and establishes a USB network link with the second system.

[0141] In this embodiment of the application, after the display device is powered on, the first system and the second system first establish a USB communication link; the first system completes the identification of the second system through the device identification engine: manufacturer information matching verification; after the verification is passed, the interface monitor performs protocol and function detection on the USB interface, and then the IP service controller completes the network IP address allocation and other related configurations, and finally completes the overall network parameter configuration through the network configuration engine, thereby realizing the network access of the second system based on the USB link.

[0142] This method relies on the USB master-slave hardware connection, with the first system in the display system as the master and the second system as the slave. Through a device information verification mechanism during USB communication connection establishment, the legitimacy and compatibility of the second system are determined. The first virtual network interface is activated only when the device information matches the preset device library, overcoming the technical bottleneck of traditional USB master-slave systems which can only achieve basic data transmission and cannot build stable network links. Simultaneously, the activated first virtual network interface is set as a gateway, and an IP address in the same network segment is assigned to the second system using the DHCP protocol. A dedicated USB network link is built using the USB physical link, allowing multiple systems to form a unified network segment environment. This achieves network collaboration and sharing among multiple systems, realizing the transformation of USB master-slave interaction from data transmission to network link construction.

[0143] Based on the preceding text Figure 7 The network sharing solution introduced can also be based on Figure 8 The modules of the first system in the display device shown interact with each other, and the following is a supplementary explanation.

[0144] Figure 10 A flowchart of yet another network sharing method provided in some embodiments of this application is shown, such as... Figure 10 As shown, when the first system is configured in host mode and the second system is configured in slave mode, each module in the second system (device manager, Ethernet service, and DHCP client) is configured to perform the following steps S1001~S1011: S1001. After the second system is powered on, initialize the RNDIS Gadge configuration, as detailed in step S710 above.

[0145] S1002. The first system and the second system establish a USB communication connection.

[0146] S1003. When the second system establishes a USB communication connection with the first system, the second system sends a configuration command to the device manager.

[0147] S1004. After receiving the instruction, the Device Manager creates a second virtual network interface. At this time, the second system connects as a slave device to the first system, which is the master device.

[0148] S1005. After detecting a device access (USB ATTACH) event, the Device Manager sends a USB_STATE status broadcast to the second system to synchronize the hardware connection status.

[0149] It should be noted that when the USB connection is successful and the first USB device is enumerated by the system, a USB_STATE status broadcast is sent, which contains the information that USB_FUNCTION_RNDIS is activated, i.e., USB_FUNCTION_RNDIS = TRUE.

[0150] S1006. The DHCP client pre-registers to detect the USB_STATE broadcast event of the device manager to ensure that subsequent network configuration processes such as obtaining an IP address can be triggered immediately after receiving the USB access notification.

[0151] S1007. If the USB_STATE status broadcast carries the USB_FUNCTION_RNDIS=TRUE flag (indicating that the RNDIS network function of the second system is ready and the physical connection and basic protocol are matched), the second system sends it to the Ethernet service.

[0152] After the Ethernet service detects that the USB network link with the first system has been initialized, it executes S1008, and the Ethernet service calls setUsbFunction to configure the USB network function.

[0153] S1009, Ethernet service adjusts the status of the second virtual network interface to enabled.

[0154] After the S1010 Ethernet service completes interface activation, it triggers the DHCP client to start.

[0155] S1011, the DHCP client requests an IP address from the first system for the second system.

[0156] S1012, The first system sends the IP address allocated to the second system to complete the final configuration of the network access path for the second system to access the Internet module 815.

[0157] It should be noted that the DHCP client initiates DHCP interaction through the second virtual network interface to obtain network configuration: First, it sends a DHCP Discover broadcast message. After the DHCP server in the first system responds with a DHCP Offer, the DHCP client sends a DHCP Request to request address allocation. After the first system returns a DHCP ACK containing the IP address, subnet mask, gateway, and DNS, the DHCP client configures the above IP and routing information to the second virtual network interface through Netd and adds a default route pointing to the IP of the first virtual network interface in the first system. After the configuration is completed, the second virtual network interface of the second system has network communication capabilities and can access the external network through the first system.

[0158] S1013, the first system and the second system establish network data communication.

[0159] In this network sharing method, the second system simulates and builds the hardware transmission foundation for the USB virtual network card; then, by creating and enabling the second virtual network interface as needed, a usable logical entry point is prepared for network interaction; USB enumeration is completed to enable normal communication at the protocol layer; and with the precise matching of the roles of the master and slave system DHCP server / client, it is ensured that the IP can be properly allocated and configured to the enabled virtual interface, ultimately enabling the USB physical link to have network layer communication capabilities, realizing a stable network connection between the two systems based on the USB link. At the same time, relying on the physical characteristics of USB and standard protocols, it also achieves the extended effects of highly stable data interaction and automated configuration.

[0160] It should be understood that the sequence numbers of the processes in the above embodiments do not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention. The various embodiments described herein can be independent solutions or combinations based on internal logic, and all such solutions fall within the protection scope of this application.

[0161] It should also be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0162] Based on the same concept, as an implementation of the above method, this application provides a network sharing device. This device embodiment corresponds to the aforementioned method embodiment. For ease of reading, this device embodiment will not repeat the details of the aforementioned method embodiment one by one, but it should be clear that the device in this embodiment can implement all the contents of the aforementioned method embodiment.

[0163] Figure 11 A schematic diagram of a network sharing device provided in some embodiments of this application is shown. The network sharing device 1100 includes an initialization unit 1110, a connection unit 1120, and a network link establishment unit 1130. The functions of each unit are detailed below.

[0164] The initial unit 1110 is used to receive device information from the second system and create a first virtual network interface when establishing a USB communication connection with the second system. The first virtual network interface is in a closed state.

[0165] The connection unit 1120 is used to adjust the state of the first virtual network interface from the closed state to the enabled state when the device information of the second system matches the information in the preset device library.

[0166] The network link establishment unit 1130 is used to identify the first virtual network interface as a gateway when the first virtual network interface is in the enabled state, and to allocate an IP address in the same network segment as the gateway to the second system according to the DHCP protocol, and establish a USB network link with the second system.

[0167] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the network sharing methods provided in the above embodiments.

[0168] This application also provides a chip, which includes a processor and a memory. The memory stores a computer program, which, when executed by the processor, implements the network sharing method provided in the above embodiments.

[0169] This application also provides a computer program product, which includes a computer program that, when run by an electronic device, enables the electronic device to implement the network sharing methods provided in the above embodiments.

[0170] It should be understood that the memory mentioned in the embodiments of this application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.

[0171] In the embodiments provided in this application, the division of various frameworks, modules, or units is merely a logical functional division. In actual implementation, there may be other division methods. For example, multiple frameworks, modules, or units may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0172] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0173] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0174] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A network sharing method, characterized in that, The invention is applied to a display device, which includes a first system and a second system, wherein the first system and the second system are connected via a USB cable for communication. With the first system configured in master mode and the second system configured in slave mode, the first system is configured as follows: When establishing a USB communication connection with the second system, the device information of the second system is received, and a first virtual network interface is created, which is in a closed state. If the device information of the second system matches the information in the preset device library, the status of the first virtual network interface is changed from the closed state to the enabled state. When the first virtual network interface is enabled, the first virtual network interface is identified as the gateway, and an IP address within the same network segment as the gateway is assigned to the second system according to the DHCP protocol, and a USB network link is established with the second system.

2. The network sharing method according to claim 1, characterized in that, With the first system configured in master mode and the second system configured in slave mode, the second system is configured as follows: It is simulated as a USB virtual network adapter; When establishing a USB communication connection with the first system, a second virtual network interface is created, and the second virtual network interface is in a closed state; Receives a USB device enumeration request initiated by the first system and sends the device information of the second system to the first system; After detecting that the USB network link with the first system has been initialized, the state of the second virtual network interface is changed from the off state to the enabled state; Obtain the IP address from the first system according to the DHCP protocol, configure the IP address for the second virtual network interface, and establish a USB network link with the first system.

3. The network sharing method according to claim 2, characterized in that, The second system includes a device manager and Ethernet services; When establishing a USB communication connection with the first system, the creation of a second virtual network interface is as follows: When establishing a USB communication connection with the first system, the device manager creates a second virtual network interface; After detecting that the USB network link with the first system has been initialized, the state of the second virtual network interface is changed from the off state to the on state, as follows: After the Ethernet service detects that the USB network link with the first system has been initialized, the state of the second virtual network interface is changed from the off state to the enabled state.

4. The network sharing method according to claim 3, characterized in that, The second system also includes a DHCP client; After the Ethernet service detects that the USB network link with the first system has completed initialization, the state of the second virtual network interface is changed from the off state to the enabled state, as follows: After the Ethernet service detects that the USB network link with the first system has been initialized, it changes the state of the second virtual network interface from the off state to the enabled state and starts the DHCP client.

5. The network sharing method according to any one of claims 1 to 4, characterized in that, The first system includes a host manager and a shared network service; When establishing a USB communication connection with the second system, the device information of the second system is received, and a first virtual network interface is created, as follows: When establishing a USB communication connection with the second system, the host manager receives device information from the second system and creates the first virtual network interface; The host manager broadcasts device information from the second system. If the device information of the second system matches the information in the preset device library, then the state of the first virtual network interface is changed from the closed state to the enabled state. The shared network service receives device information from the second system; If the device information of the second system matches the information in the preset device library, the shared network service will change the status of the first virtual network interface from closed to enabled.

6. The network sharing method according to any one of claims 1 to 4, characterized in that, The device information of the second system is the manufacturer information of the second system.

7. The network sharing method according to any one of claims 1 to 4, characterized in that, The first system is any one of the following: Linux system; Android system.

8. The network sharing method according to any one of claims 1 to 4, characterized in that, The USB cable is a USB-C cable or a USB-C dual-role cable.

9. The network sharing method according to any one of claims 1 to 4, characterized in that, The display device further includes a third system configured as a slave system, wherein the hardware of the first system and the hardware of the third system are connected via a USB cable.

10. A display device, characterized in that, It includes a display, a memory, a controller, and a computer program stored in the memory and executable on the controller, wherein the controller executes the computer program to implement the network sharing method as described in any one of claims 1 to 9.

Images