AR (Augmented Reality) glasses supporting dynamic expansion image acquisition equipment and implementation method thereof

Abstract

The invention belongs to the technical field of AR (Augmented Reality) equipment, particularly relates to AR glasses supporting dynamic expansion image acquisition equipment and an implementation method thereof, and aims to solve the problem that the existing Android system AR glasses are poor in compatibility when being externally connected with image acquisition equipment and need to depend on an exclusive SDK (Software Development Kit). An Android operating system is built in the AR glasses, and a Camera service module, a driving application program and a video application program are configured in the system. The Camera service module provides a registration interface and a distribution identifier for the external image acquisition equipment, uniformly manages the built-in and registered external image acquisition equipment and generates an equipment identifier list; the driving application program adapts to the registration interface through protocol conversion, and registration of the external image acquisition equipment is completed; and the video application program obtains the identifier list, and calls the corresponding equipment through the system universal interface based on the selected target identifier. According to the invention, the dynamic expansion of the external equipment is realized, the application development cost is reduced, and the adaptation flexibility and use experience of the AR glasses are improved.

Description

Technical Field

[0001] This invention belongs to the field of AR device technology, and in particular relates to an AR glasses that supports dynamically expanded image acquisition devices and its implementation method. Background Technology

[0002] With the rapid iteration and popularization of augmented reality (AR) technology, AR glasses, as typical AR terminal devices, have been widely used in diverse scenarios such as video calls, live streaming, remote collaboration, and equipment inspection. In these application scenarios, users' needs for image acquisition are becoming increasingly diverse. For example, in live streaming scenarios, high-definition external cameras are needed to capture detailed images, while in inspection scenarios, wide-angle external cameras are needed to cover the panoramic field of view. Therefore, the demand for AR glasses to connect to various image acquisition devices (such as cameras) is becoming increasingly urgent.

[0003] Most mainstream AR glasses currently run on the Android operating system, which, thanks to its open-source nature and good ecosystem compatibility, has become one of the preferred operating systems for AR devices. However, Android differs significantly from traditional PC operating systems (such as Windows and Linux) in terms of device expansion mechanisms: on PC operating systems, users can quickly adapt new external devices to the system by installing third-party drivers; but for security and stability reasons, mobile Android operating systems typically do not allow users to install drivers to support external devices, a limitation that directly restricts the expansion capabilities of AR glasses.

[0004] Specifically, in scenarios involving external image acquisition devices for AR glasses, existing technical solutions have significant drawbacks: On the one hand, the native CameraService of the Android system only has the function of managing the built-in image acquisition devices of AR glasses, and cannot include external image acquisition devices in the unified management of the system; on the other hand, if video applications (such as live streaming apps and video call apps) need to use external image acquisition devices, the application developers must customize the development by integrating the software development kit (SDK) provided by each manufacturer for different external image acquisition devices. This approach not only significantly increases the workload and cost of application development (e.g., adapting to devices from N manufacturers requires N SDK integration developments), but also severely reduces application compatibility, resulting in a video application often only supporting external image acquisition devices of a specific brand or model, preventing users from flexibly choosing external devices according to their needs.

[0005] The shortcomings of the existing technologies mentioned above make it difficult to meet the demand for external image acquisition devices for AR glasses. This not only limits the functional expansion of AR glasses in multiple scenarios, but also restricts the market application scope of AR glasses. Therefore, there is an urgent need for a technical solution that can solve the problem of adapting external image acquisition devices for AR glasses on the Android system. Summary of the Invention

[0006] The purpose of this invention is to provide an AR glasses system that supports dynamically expandable image acquisition devices and its implementation method, aiming to solve the problems of poor compatibility of external image acquisition devices for existing Android AR glasses and the need to rely on a dedicated SDK.

[0007] To achieve the above objectives, in a first aspect of the present invention, an AR glasses that supports dynamically expandable image acquisition devices is provided. The AR glasses have a built-in Android operating system, which includes a Camera service module, a driver application, and a video application.

[0008] The Camera service module provides a registration interface and assigns identifiers to external image acquisition devices, and uniformly manages the built-in image acquisition devices and the registered external image acquisition devices, generating a list of device identifiers;

[0009] The driver application is used to adapt the registration interface through protocol conversion to complete the registration of the external image acquisition device to the Camera service module;

[0010] The video application obtains the device identifier list from the Camera service module and, based on the selected target device identifier, calls the corresponding image acquisition device through the system's general interface.

[0011] Furthermore, in the AR glasses, the external image acquisition device includes at least one of a USB image acquisition device and a network image acquisition device.

[0012] Furthermore, in the AR glasses, the driver application is also used to automatically detect the access status of the external image acquisition device, and automatically trigger protocol conversion and registration with the Camera service module after detecting the device access.

[0013] Furthermore, in the AR glasses, the device identifier list is associated with and stores the device identifiers and attribute information of each image acquisition device, including device type, image resolution, data transmission protocol, and connection status.

[0014] Furthermore, in the AR glasses, when the Camera service module detects a change in the connection status of the external image acquisition device, it updates the corresponding status information in the device identifier list in real time and pushes a status change notification to the video application that is calling the external image acquisition device.

[0015] Furthermore, in the AR glasses, the system's general interface is the image acquisition interface of the Android operating system. When the video application calls the system's general interface, it does not need to rely on the software development kit (SDK) specific to the external image acquisition device.

[0016] In a second aspect of the present invention, a method for implementing AR glasses that supports dynamically expanded image acquisition devices is also provided, comprising the following steps:

[0017] Configure the driver application, camera service module, and video application in the Android operating system of the AR glasses. The camera service module has a pre-set registration interface for external image acquisition devices.

[0018] When the external image acquisition device is connected, the driver application converts its communication protocol to adapt to the registration interface, and registers the external image acquisition device to the Camera service module by calling the registration interface;

[0019] The Camera service module assigns a unique identifier to the successfully registered external image acquisition device, manages it in a unified manner with the built-in image acquisition device, and generates a list of device identifiers.

[0020] The video application obtains the device identifier list from the Camera service module and calls the corresponding image acquisition device through the system's general interface based on the selected target device identifier.

[0021] Furthermore, in the implementation method described above, the driver application synchronously uploads the attribute information of the external image acquisition device during the registration process, and the Camera service module performs a validity check on the attribute information. After the check is passed, the registration is completed and a unique identifier is assigned.

[0022] Furthermore, in the aforementioned implementation method, the video application selects the target device identifier in the following ways: by determining the target device identifier through a selection command triggered in the graphical interface, or by automatically matching and selecting the target device identifier according to preset application scenario requirements.

[0023] Furthermore, the implementation method further includes the following steps: when the external image acquisition device is disconnected from the AR glasses, the driver application sends a device disconnection notification to the Camera service module, the Camera service module updates the status information of the external image acquisition device, and pushes a device switching prompt to the video application that is calling the external image acquisition device to guide the calling of other available image acquisition devices.

[0024] Compared with the prior art, the present invention has at least the following technical effects:

[0025] Compared to existing technologies where Android AR glasses lack registration channels for external image acquisition devices, rely on device-specific SDKs leading to poor compatibility and high application development costs, and suffer from fragmented management of internal and external image acquisition devices, this invention addresses these issues by configuring a Camera service module within the Android operating system that provides registration interfaces, assigns identifiers, and manages them uniformly. This module, coupled with a driver application capable of protocol conversion and device registration, and a video application that calls devices through a system-wide interface, not only enables dynamic expansion and access of external image acquisition devices but also achieves compatibility with different types of external image acquisition devices without relying on a dedicated SDK. This reduces application development costs and simultaneously enables unified management and convenient access to internal and external image acquisition devices, significantly improving the device scalability and flexibility of AR glasses and enhancing the user experience. Attached Figure Description

[0026] Figure 1 This is a system architecture diagram of an AR glasses system supporting dynamically expandable image acquisition devices in one embodiment of the present invention;

[0027] Figure 2 This is a flowchart illustrating a method for implementing AR glasses that supports dynamically expanded image acquisition devices, according to an embodiment of the present invention. Detailed Implementation

[0028] The following will describe in more detail, with reference to the schematic diagrams, an AR glasses device supporting dynamically expanded image acquisition and its implementation method according to the present invention. Preferred embodiments of the invention are shown. It should be understood that those skilled in the art can modify the invention described herein while still achieving its advantageous effects. Therefore, the following description should be understood as being of general knowledge to those skilled in the art and is not intended to limit the invention.

[0029] For clarity, not all features of the actual embodiments are described. In the following description, well-known functions and structures are not detailed in detail, as they would obscure the invention with unnecessary detail. It should be understood that in the development of any actual embodiment, numerous implementation details must be made to achieve the developer's specific objectives, such as changes from one embodiment to another according to limitations related to the system or business. Furthermore, it should be understood that such development work may be complex and time-consuming, but is merely routine work for those skilled in the art.

[0030] Based on the teachings of this specification, those skilled in the art can form new technical solutions through cross-combination of different implementation methods without creating technical contradictions. Such variations should all be considered to fall within the protection scope of this invention.

[0031] The invention is described more specifically by way of example in the following paragraphs with reference to the accompanying drawings. The advantages and features of the invention will become clearer from the following description. It should be noted that the drawings are in a very simplified form and use non-precise proportions, and are only used to facilitate and clarify the illustration of the embodiments of the invention.

[0032] With the continuous development of AR technology, AR smart glasses have been widely used in many fields. Most AR smart glasses use the Android operating system. While traditional PC operating systems like Windows or Linux allow users to install drivers to support new devices, Android does not. In many current application scenarios, such as video calls and live streaming, there is a strong demand for AR glasses to connect to various external cameras, but the existing AR glasses system architecture cannot meet this need. In the general Android system, if video applications need to use external cameras, they must be custom-developed using the manufacturer's SDK, which not only increases development costs and workload but also reduces application compatibility.

[0033] Based on this, this embodiment discloses an AR glasses that supports dynamically expandable image acquisition devices. By optimizing the Android operating system, it realizes dynamic expansion and unified management of external image acquisition devices, solving the problems of poor compatibility of external image acquisition devices and high application development costs of existing AR glasses.

[0034] like Figure 1As shown, the AR glasses in this embodiment have a built-in Android operating system, which includes a Camera service module, a driver application, and a video application. The Camera service module provides a registration interface and assigns identifiers to external image acquisition devices, and uniformly manages the built-in image acquisition devices and the registered external image acquisition devices, generating a device identifier list. The driver application is used to adapt the registration interface through protocol conversion to complete the registration of the external image acquisition device with the Camera service module. The video application obtains the device identifier list from the Camera service module and, based on the selected target device identifier, calls the corresponding image acquisition device through a system general interface.

[0035] It's important to note that in the native architecture of the Android system, the unified management of image acquisition devices is handled by the native CameraService. Video applications need to use the interfaces provided by this native CameraService to call the image acquisition devices within the system. However, the existing native CameraService in the Android system has functional limitations; it can only identify and manage the built-in image acquisition devices that come with AR glasses and cannot support the access recognition and scheduling control of external image acquisition devices, resulting in external image acquisition devices lacking an effective channel to access the system.

[0036] The Camera service module in this embodiment modifies the shortcomings of the original CameraService based on its functionality: while retaining the original CameraService's ability to manage built-in image acquisition devices, it adds a function to register image acquisition devices and provides a corresponding external image acquisition device registration interface. This registration interface is compatible with the interface architecture of the original CameraService and can be called by the driver application in this embodiment. Specifically, the registration interface can receive information about external image acquisition devices transmitted by the driver application, thus opening a dedicated entry point for external image acquisition devices to access the Android system, thereby solving the problem of external image acquisition devices being unable to access the system in existing Android systems.

[0037] After receiving the registration request from the driver application, the Camera service module will assign a unique device identifier to each successfully registered external image acquisition device. This device identifier adopts the same encoding rules as the image acquisition devices built into the AR glasses (e.g., Camera ID format), forming a unified identification system for internal and external devices.

[0038] To support the device access requirements of video applications, the Camera service module also generates a device identifier list, including built-in image acquisition devices and registered external image acquisition devices. This device identifier list stores a unique identifier for each image acquisition device along with its attribute information. The attribute information includes device type, image resolution, data transmission protocol, and connection status. This allows video applications to quickly obtain information about all available devices in the system by calling the module's interface, without needing to detect them one by one or rely on vendor-specific tools.

[0039] Meanwhile, the Camera service module also features a status change notification function. When the Camera service module detects a change in the connection status of an external image acquisition device (such as an unexpected disconnection, reconnection, or offline status due to a malfunction), it updates the corresponding status information in the device identifier list in real time, ensuring the real-time nature of the list data. Simultaneously, the Camera service module proactively pushes status change notifications (e.g., "Device disconnected, please switch to another device") to video applications that are using the external image acquisition device, allowing the applications to respond promptly to status changes. For example, after receiving the notification, a live video streaming application can automatically switch to the built-in image acquisition device to continue the live stream, avoiding interruptions. This feature significantly improves the stability and user experience when using external devices with AR glasses.

[0040] In this embodiment, the driver application, as a core adaptation layer component between the external image acquisition device and the Android operating system of the AR glasses, solves the protocol compatibility problem between external devices from different manufacturers and the system, and realizes standardized access and management of external devices. Since external image acquisition devices from different manufacturers often use their own independent proprietary communication protocols, these protocols are not directly compatible with the registration interface provided by the Camera service module. Therefore, the driver application needs to convert the proprietary protocols of the external image acquisition devices into a universal interface format that conforms to the Android system specifications, so that the device information can be correctly recognized by the Camera service module. Ultimately, the external image acquisition device connects to the system, completing the transformation from an unrecognized external device to a system-controlled device.

[0041] To enhance user convenience, the driver application also features an automatic detection function to automatically detect the connection status of external image acquisition devices. In practical applications, when a user connects an external image acquisition device (such as a USB camera plugged into the USB port of the AR glasses), the driver application monitors the external port of the AR glasses in real time. Once a device connection signal is detected, the protocol conversion process is automatically initiated without manual user intervention, and a registration request to the Camera service module is simultaneously triggered, making the expansion process of external devices more efficient.

[0042] At the same time, during the registration process, the driver application will also upload the attribute information of the external image acquisition device to the Camera service module. The Camera service module will then verify the validity of the attribute information. Once the verification is successful, the registration will be completed and a unique identifier will be assigned.

[0043] Furthermore, the driver application also undertakes continuous status monitoring and management functions. After the external image acquisition device completes registration and is put into use, the driver application tracks the device's connection status in real time. Once a device disconnection is detected, it immediately sends a device disconnection notification to the Camera service module. This effectively avoids application crashes or image acquisition interruptions caused by sudden device offline, further ensuring the stability and continuity of the use of external devices for AR glasses.

[0044] The video applications in this embodiment include video calling applications, live streaming applications, and photo-taking applications. They work together with the Camera service module and the driver application to form a complete technical chain, as specifically implemented below:

[0045] In the device list acquisition stage, video applications do not need to individually adapt to the manufacturer interfaces of different external image acquisition devices. They only need to call the Camera ID acquisition interface of the Camera service module to obtain a device identifier list that includes the built-in image acquisition device of AR glasses and all registered external image acquisition devices. This list not only contains the unique identifier of each device, but also carries key information such as device type and current connection status, ensuring that the application can clearly identify all available image acquisition devices.

[0046] During the device selection process, video applications offer a flexible selection mechanism, allowing users to choose the target device identifier in two ways: by triggering a selection command in the graphical interface, or by automatically matching and selecting the target device identifier based on preset application scenario requirements. This satisfies both the flexibility of user choice and the automation needs of professional scenarios, improving operational efficiency.

[0047] During the device invocation phase, video applications only need to call the system's general interface based on the selected target device identifier to trigger image acquisition. This general system interface is the native image acquisition interface of the Android operating system. When video applications call this interface, they do not need to rely on the software development kit (SDK) specific to the external image acquisition device, significantly reducing application development costs and time, while also significantly improving the compatibility of video applications with external image acquisition devices.

[0048] During device switching, video applications exhibit dynamic response capabilities: when an external image acquisition device experiences a connection interruption (e.g., a USB camera is accidentally unplugged) or a status change (e.g., a webcam signal is restored), the Camera service module immediately pushes a status change notification (e.g., "USB HD camera has been disconnected") to the video application currently using that device. Upon receiving the notification, the application can automatically switch to another available device according to preset logic (e.g., immediately switch to the AR glasses' built-in camera to continue capturing images), or prompt the user to manually select a new device via a pop-up window (e.g., "Current device is unavailable, please select another camera"), ensuring uninterrupted image acquisition. This effectively solves the problem of applications crashing or malfunctioning directly after an external device is disconnected in existing technologies, improving the stability and user experience of AR glasses.

[0049] Furthermore, to adapt to the image acquisition needs of AR glasses in diverse scenarios such as video calls, live streaming, and remote inspections, this embodiment supports external image acquisition devices that cover common wired and wireless connection methods, specifically including at least one of USB image acquisition devices and network image acquisition devices.

[0050] The USB image acquisition device physically connects to the AR glasses via a USB Type-C interface. A typical example is a USB high-definition camera. These devices offer advantages such as low data transmission latency and high stability, making them particularly suitable for scenarios requiring close-range, high-definition detail capture. For instance, when AR glasses are used for inspecting precision components, an external USB high-definition camera can clearly capture surface textures or parameter markings without requiring a complex network environment. After connection, these devices can undergo private communication protocol conversion through the driver application in this embodiment, thereby adapting to the Camera service module's registration interface and ultimately being integrated into the system for unified management.

[0051] Network image acquisition devices establish wireless connections with AR glasses via Wi-Fi or Ethernet. Typical devices include home or industrial network cameras. Their core advantage is flexible connection distance, overcoming the limitations of physical interfaces to achieve remote image acquisition. For example, when AR glasses are used for remote collaborative live streaming in a large factory, they can connect via Wi-Fi to network cameras deployed in different areas of the factory to achieve panoramic image acquisition of a large area. Similar to USB image acquisition devices, these devices also require driver applications to complete protocol adaptation and registration, and are ultimately called by video applications through the Android system's general interface, without relying on device-specific software development kits.

[0052] Example 2

[0053] like Figure 2The method for dynamically expanding the image acquisition device using AR glasses in this embodiment includes the following steps:

[0054] S1: Configure the driver application, Camera service module, and video application in the Android operating system of the AR glasses. The Camera service module has a pre-set registration interface for external image acquisition devices.

[0055] S2: When the external image acquisition device is connected, the driver application converts its communication protocol to adapt to the registration interface, and registers the external image acquisition device to the Camera service module by calling the registration interface.

[0056] S3: The Camera service module assigns a unique identifier to the successfully registered external image acquisition device, manages it in a unified manner with the built-in image acquisition device, and generates a list of device identifiers.

[0057] S4: The video application obtains the device identifier list from the Camera service module, and calls the corresponding image acquisition device through the system general interface based on the selected target device identifier.

[0058] Specifically, step S1 involves configuring the driver application, Camera service module, and video applications within the Android operating system of the AR glasses. The Camera service module differs from the Android system's native CameraService, which only manages built-in devices. In this embodiment, the Camera service module pre-configures a dedicated registration interface for external image acquisition devices. This interface provides an access channel for subsequent external devices to connect to the system and also provides a standard entry point for interaction between the driver application and the Camera service module, ensuring that external devices can be recognized and managed by the system.

[0059] Step S2 involves the adaptation and registration of the external image acquisition device after it is connected. When a user connects an external image acquisition device (such as a USB camera or webcam) to the AR glasses, the driver application first initiates a protocol conversion. Specifically, since external image acquisition devices from different manufacturers may use proprietary communication protocols, the driver application converts these proprietary protocols into a standard format compatible with the Camera service module's registration interface, preventing the device from being unrecognized due to protocol differences. After the protocol conversion is complete, the driver application actively calls the pre-set registration interface from step S1 to pass the basic information of the external image acquisition device (such as device type and transmission method) to the Camera service module, ultimately completing the registration of the external image acquisition device in the system and enabling it to be managed by the system.

[0060] Furthermore, during the registration process in step S2, when the registration interface is called to complete the registration, the driver application will also upload the attribute information of the external device simultaneously. The Camera service module will verify the legality of this attribute information. Only after the verification is passed will the registration of the external device be completed and a unique identifier be assigned, so that the access device is compliant.

[0061] Step S3 is implemented by the Camera service module, overcoming the limitation of the native Android system which only manages built-in image acquisition devices. After an external image acquisition device completes registration via step S2, the Camera service module assigns it a unique identifier (such as a Camera ID). This identifier forms a unified system with the identifiers of the AR glasses' built-in image acquisition devices, ensuring that each device can be uniquely distinguished within the system. Simultaneously, the Camera service module integrates both built-in and registered external image acquisition devices into the same management system. It not only associates and stores the unique identifiers and attribute information of the devices (such as resolution and connection status), but also compiles the identifiers of all available devices into a device identifier list. This provides a clear device list for subsequent video applications, achieving integrated management of both internal and external devices.

[0062] In step S4, when video applications (such as live streaming apps and video call apps) need to use image acquisition devices, they no longer need to rely on specific vendor SDKs for customized development. They only need to obtain the device identifier list generated in step S3 from the Camera service module. The application can determine the target device identifier based on user selection or scenario requirements. Specifically, the video application selects the target device identifier in the following ways: by determining the target device identifier through a selection command triggered in the graphical interface, or by automatically matching and selecting the target device identifier according to preset application scenario requirements. Subsequently, the corresponding target device is called through the native general image acquisition interface of the Android system. The entire process fully reuses the general capabilities of the Android system, which reduces the workload of application development and ensures that the application is compatible with different types of external image acquisition devices, ultimately realizing the dynamic expansion of the AR glasses' image acquisition function.

[0063] Furthermore, the method also includes the following steps: when the external image acquisition device is disconnected from the AR glasses, the driver application sends a device disconnection notification to the Camera service module. Upon receiving the notification, the Camera service module immediately updates the status information of the external image acquisition device (e.g., changing "connected" to "disconnected") and pushes a device switching prompt to the video application that is using the external image acquisition device (e.g., displaying a pop-up window in the AR interface prompting "The current camera is disconnected, do you want to switch to the built-in camera?"). Through the above operations, video applications can be guided to quickly switch to other available image acquisition devices, avoiding application function interruption due to device disconnection, and further improving the stability of the method and user experience.

[0064] In summary, compared to existing technologies where Android AR glasses lack registration channels for external image acquisition devices, rely on device-specific SDKs leading to poor compatibility and high application development costs, and suffer from fragmented management of internal and external image acquisition devices, this invention addresses these issues by configuring a Camera service module within the Android operating system that provides registration interfaces, assigns identifiers, and manages them uniformly. This module, coupled with a driver application capable of protocol conversion and device registration, and a video application that calls devices through a system-wide interface, not only enables dynamic expansion and access of external image acquisition devices but also achieves compatibility with different types of external image acquisition devices without relying on a dedicated SDK. This reduces application development costs and simultaneously enables unified management and convenient access to internal and external image acquisition devices, significantly improving the device scalability and flexibility of AR glasses and enhancing the user experience.

[0065] The above are merely preferred embodiments of the present invention and do not constitute any limitation on the present invention. Any equivalent substitutions or modifications made by those skilled in the art to the technical solutions and content disclosed in the present invention without departing from the scope of the present invention shall be deemed to have remained within the protection scope of the present invention.

Claims

1. An AR glasses supporting dynamic extension of image capturing devices, characterized in that, The AR glasses are built-in with an Android operating system, and the Android operating system is configured with a Camera service module, a driving application and a video application; The Camera service module provides a registration interface and an allocation identifier for an external image acquisition device, and uniformly manages built-in image acquisition devices and the registered external image acquisition device, and generates a device identifier list; The driving application is used for adapting the registration interface through protocol conversion, and completing the registration of the external image acquisition device to the Camera service module; The video application obtains the device identifier list from the Camera service module, and based on a selected target device identifier, calls a corresponding image acquisition device through a system general interface.

2. The AR glasses of claim 1, wherein, The external image acquisition device includes at least one of a USB image acquisition device and a network image acquisition device.

3. The AR glasses of claim 1, wherein, The driving application is also used for automatically detecting the access state of the external image acquisition device, and automatically triggering protocol conversion and registration operation to the Camera service module after detecting the device access.

4. The AR glasses of claim 1, wherein, The device identifier list is associated with the device identifier and attribute information of each image acquisition device, and the attribute information includes device type, image resolution, data transmission protocol and connection state.

5. The AR glasses of claim 1, wherein, When the Camera service module detects that the connection state of the external image acquisition device changes, it updates the corresponding state information in the device identifier list in real time, and pushes a state change notification to the video application which is calling the external image acquisition device.

6. The AR glasses of claim 1, wherein, The system general interface is an image acquisition interface of the Android operating system, and the video application does not need to rely on a software development kit (SDK) specific to the external image acquisition device when calling the system general interface.

7. An implementation method of AR glasses supporting dynamic expansion of image acquisition devices, characterized in that, The method comprises the following steps: Configuring a driving application, a Camera service module and a video application in an Android operating system of AR glasses, and the Camera service module is pre-configured with a registration interface of an external image acquisition device; When the external image acquisition device is accessed, the driving application converts its communication protocol to adapt to the registration interface, and registers the external image acquisition device to the Camera service module by calling the registration interface; The Camera service module allocates a unique identifier to the registered external image acquisition device, and uniformly manages it with built-in image acquisition devices, and generates a device identifier list; The video application obtains the device identifier list from the Camera service module, and based on a selected target device identifier, calls a corresponding image acquisition device through a system general interface.

8. The implementation method of claim 7, wherein, The driving application synchronously uploads attribute information of the external image acquisition device during the registration process, and the Camera service module performs legality verification on the attribute information, and completes the registration and allocates a unique identifier after the verification is passed.

9. The implementation method of claim 7, wherein, The video application selects the target device identifier in the following ways: by determining the target device identifier through a selection command triggered in the graphical interface, or by automatically matching and selecting the target device identifier according to the preset application scenario requirements.

10. The implementation method of claim 7, wherein, The method also includes the following steps: when the external image acquisition device is disconnected from the AR glasses, the driver application sends a device disconnection notification to the Camera service module, the Camera service module updates the status information of the external image acquisition device, and pushes a device switching prompt to the video application that is calling the external image acquisition device to guide the application to call other available image acquisition devices.

Images