CN115118719A - Method and system for connecting camera equipment of cloud desktop - Google Patents
Method and system for connecting camera equipment of cloud desktop Download PDFInfo
- Publication number
- CN115118719A CN115118719A CN202210698353.8A CN202210698353A CN115118719A CN 115118719 A CN115118719 A CN 115118719A CN 202210698353 A CN202210698353 A CN 202210698353A CN 115118719 A CN115118719 A CN 115118719A
- Authority
- CN
- China
- Prior art keywords
- camera
- cloud desktop
- client
- image data
- server
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 28
- 238000012544 monitoring process Methods 0.000 claims description 8
- 238000005516 engineering process Methods 0.000 description 7
- 230000014509 gene expression Effects 0.000 description 7
- 238000004891 communication Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/08—Protocols specially adapted for terminal emulation, e.g. Telnet
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
- G06F9/452—Remote windowing, e.g. X-Window System, desktop virtualisation
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Studio Devices (AREA)
Abstract
A camera device connection method and system of a cloud desktop are provided, wherein the method comprises the following steps that a) operation of opening a camera on the cloud desktop by a user is monitored through a preset interface; b) acquiring the camera setting through an ioctl system interface; c) sending the camera setting, an open instruction and a camera ID to a client through a cloud desktop protocol, and d) decompressing after receiving a data packet by the client; e) the client opens the local camera equipment according to the corresponding camera ID; different from the prior art, the scheme can acquire the information of the camera after the client is connected with the camera by utilizing the protocol of the cloud desktop, generate the corresponding drive at the cloud server, and present the camera shooting picture when the cloud server runs the camera control instruction.
Description
Technical Field
The invention relates to the field of cloud desktop application, in particular to a method and a system for connecting camera equipment on a cloud desktop.
Background
The Linux cloud desktop is an application of a cloud computing technology, and is simply characterized in that virtualization software is installed in a server in a data center machine room through a virtualization technology, and then a plurality of virtual machines are created through configuration of the software, and the virtual machines have relatively independent CPU and memory resources, so that an actual server can be divided into the plurality of virtual machines, and the virtual machines are provided for a plurality of users to be used independently, different users use different virtual machines, the CPU and the memory resources cannot be seized mutually, and mutual conflict cannot be caused by operation of the same machine. In an application scene of a Linux cloud desktop, in order to meet the use habits of most users, a Windows operating system is generally installed in a virtual machine, and the user uses a desktop service of the virtual machine, which is similar to a normal computer, to browse a webpage, edit a document and the like.
The Linux cloud desktop protocol is a core technology in the Linux cloud desktop technology, is a key for controlling the Linux cloud desktop by operating local equipment by a user, and the core part of the Linux cloud desktop protocol is a virtualization mapping of each local equipment on the Linux cloud desktop. The virtualization technology of the camera device belongs to one of the modules. In the prior art, the Linux cloud desktop does not support the relevant design of camera equipment, and the relativity of the cloud desktop is influenced.
Disclosure of Invention
Therefore, a camera connection configuration method of a cloud desktop is needed to be provided, which can solve the problem of configuring and connecting a camera in an environment of the cloud desktop.
In order to achieve the above object, the inventor provides a camera device connection method of a cloud desktop, comprising the following steps,
a) monitoring the operation of opening a camera on a cloud desktop by a user through a preset interface;
b) acquiring the camera setting through an ioctl system interface;
c) sending the camera setting and open instruction and the camera ID to a client through a cloud desktop protocol,
d) decompressing after the client receives the data packet;
e) the client opens the local camera equipment according to the corresponding camera ID;
f) and the client writes the camera setting information and starts to acquire image data.
g) And sending the acquired image data to a server through a cloud desktop protocol.
h) And searching for a corresponding camera drive according to the camera ID, and writing image data into the corresponding camera drive through ioctl.
i) And the server reads the image data from the driver and displays the image data on the cloud desktop.
In some embodiments of the application, the method further includes the steps that a local client scans equipment nodes under an equipment directory, traverses locally connected physical camera equipment, acquires equipment information corresponding to the physical camera equipment nodes, sends the equipment information to a server through a cloud desktop protocol, and the server creates a camera driver according to the received equipment information and writes the equipment information into the camera driver.
In some embodiments of the present application, the device information includes one or more of a resolution supportable by the camera, a format supportable by the camera, a product name of the camera, and a hardware descriptor of the camera.
In some embodiments of the present application, the camera settings include camera resolution and image format.
In some embodiments of the present application, the camera ID includes a product ID and a vendor ID.
A camera equipment connection system of a cloud desktop comprises a client and a server which can be used for operating the cloud desktop, and is specifically used for executing the following steps,
a) monitoring the operation of opening a camera on a cloud desktop by a user through a preset interface;
b) acquiring the camera setting through an ioctl system interface;
c) sending the camera setting and open instruction and the camera ID to a client through a cloud desktop protocol,
d) decompressing after the client receives the data packet;
e) the client opens the local camera equipment according to the corresponding camera ID;
f) and the client writes the camera setting information and starts to acquire image data.
g) And sending the acquired image data to a server through a cloud desktop protocol.
h) And searching for a corresponding camera drive according to the camera ID, and writing image data into the corresponding camera drive through ioctl.
i) And the server reads the image data from the driver and displays the image data on the cloud desktop.
In some embodiments of the application, the method further includes the step of scanning, by the local client, the device node under the device directory, traversing the locally connected physical camera device, acquiring device information corresponding to the physical camera device node, sending the device information to the server through the cloud desktop protocol, creating, by the server, a camera driver according to the received device information, and writing the device information into the camera driver.
In some embodiments of the present application, the device information includes one or more of a resolution supportable by the camera, a format supportable by the camera, a product name of the camera, and a hardware descriptor of the camera.
In some embodiments of the present application, the camera settings include camera resolution and image format.
In some embodiments of the present application, the camera ID includes a product ID and a vendor ID.
Different from the prior art, the scheme can acquire the information of the camera after the client is connected with the camera by utilizing the protocol of the cloud desktop, generate the corresponding drive at the cloud server, and present the camera shooting picture when the cloud server runs the camera control instruction.
Drawings
Fig. 1 is a flowchart of a method for connecting a camera device of a cloud desktop according to an embodiment;
FIG. 2 is a schematic diagram of a video streaming process according to an embodiment;
fig. 3 is a flow chart of a local physical camera access according to an embodiment;
fig. 4 is an access flow chart of a camera virtualization device according to an embodiment;
fig. 5 is a block diagram of a camera device connection system of a cloud desktop according to an embodiment.
Detailed Description
In order to explain technical contents, structural features, objects and effects of the technical solutions in detail, the following detailed description is given with reference to the accompanying drawings in combination with the embodiments.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase "an embodiment" in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or related to other embodiments specifically defined. In principle, in the present application, the technical features mentioned in the embodiments can be combined in any manner to form a corresponding implementable technical solution as long as there is no technical contradiction or conflict.
Unless defined otherwise, technical terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs; the use of relational terms herein is intended to describe specific embodiments only and is not intended to limit the present application.
In the description of the present application, the term "and/or" is a expression for describing a logical relationship between objects, meaning that three relationships may exist, for example a and/or B, meaning: there are three cases of A, B, and both A and B. In addition, the character "/" herein generally indicates that the former and latter associated objects are in a logical relationship of "or".
In this application, terms such as "first" and "second" are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions.
Without further limitation, in this application, the use of "including," "comprising," "having," or other similar expressions in phrases and expressions of "including," "comprising," or "having," is intended to cover a non-exclusive inclusion, and such expressions do not exclude the presence of additional elements in a process, method, or article that includes the recited elements, such that a process, method, or article that includes a list of elements may include not only those elements but also other elements not expressly listed or inherent to such process, method, or article.
As is understood in the examination of the guidelines, the terms "greater than", "less than", "more than" and the like in this application are to be understood as excluding the number; the expressions "above", "below", "within" and the like are understood to include the present numbers. Furthermore, the description of embodiments herein of the present application of the term "plurality" means more than two (including two), and expressions relating to "plurality" similar thereto are also to be understood, such as "plurality", etc., unless explicitly defined otherwise.
In the description of the embodiments of the present application, spatially relative expressions such as "central," "longitudinal," "lateral," "length," "width," "thickness," "up," "down," "front," "back," "left," "right," "vertical," "horizontal," "vertical," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," "circumferential," and the like are used, and the indicated orientations or positional relationships are based on the orientations or positional relationships shown in the specific embodiments or drawings and are only for convenience of describing the specific embodiments of the present application or for the convenience of the reader, and do not indicate or imply that the device or component in question must have a specific position, a specific orientation, or be constructed or operated in a specific orientation and therefore should not be construed as limiting the embodiments of the present application.
Unless specifically stated or limited otherwise, the terms "mounted," "connected," "secured," and "disposed" used in the description of the embodiments of the present application are to be construed broadly. For example, the connection can be a fixed connection, a detachable connection, or an integrated connection; it can be mechanical connection, electrical connection, and communication connection; they may be directly connected or indirectly connected through an intermediate; which may be communication within two elements or an interaction of two elements. Specific meanings of the above terms in the embodiments of the present application can be understood by those skilled in the art to which the present application pertains in accordance with specific situations.
In order to solve the problem of intelligently identifying risks in enterprise project data, the enterprise project risk monitoring method based on artificial intelligence is designed.
As shown in fig. 1, a method for connecting a camera device on a cloud desktop according to the present application includes the following steps,
a) monitoring the operation of opening a camera on a cloud desktop by a user through a preset interface;
b) acquiring the camera setting through an ioctl system interface;
c) sending the camera setting and open instruction and the camera ID to a client through a cloud desktop protocol,
d) decompressing after the client receives the data packet;
e) the client opens the local camera equipment according to the corresponding camera ID;
f) and the client writes the camera setting information and starts to acquire image data.
g) And sending the acquired image data to a server through a cloud desktop protocol.
h) And searching for a corresponding camera drive according to the camera ID, and writing image data into the corresponding camera drive through ioctl.
i) And the server reads the image data from the driver and displays the image data on the cloud desktop.
The method can be operated in a cloud desktop camera equipment connection system, the system can comprise a client and a server, the client can be local computer processing equipment connected with a physical camera, and the server can be computer equipment for operating remote cloud desktop service.
In some specific embodiments, please refer to fig. 2, a user may operate a virtual camera on a cloud desktop, and during the virtualization driving, the operation performed by the user on the camera device may be acquired in real time by monitoring a file-operation interface of the camera driver. For example, when a user uses a Linux cloud desktop, the operation of the user is captured by a virtualized device driver when the operation of opening and closing a camera is performed on a virtual camera device on the Linux cloud desktop through the cameras by using software, the operation of the user is packaged into a camera operation instruction of a Linux cloud desktop protocol, the camera operation instruction is issued to a local terminal through a protocol channel, and the operation performed by the user is synchronized on a physical camera driver of the local terminal.
When a user opens the virtual camera on the Linux cloud desktop, the open operation is sent to the local terminal through a protocol channel of the Linux cloud desktop. In the open instruction, the ID of the virtual camera operated by the user on the Linux cloud desktop is included, and the picture setting information of the camera, the picture information including the resolution and the picture format, are all sent to the local terminal together in the instruction. The information can be written into the camera equipment on the local terminal, and the corresponding picture information input by the camera equipment is collected. After the picture is sent to a server on the Linux cloud desktop, the information is written into a driver through an ioctl interface of the rewritten camera driver through the camera ID. At this time, the video software operated on the Linux cloud desktop by the user, such as a video conference or a wechat video, can acquire the picture. Experience is the same as if the user had turned on a camera locally. When the user switches to other resolutions or other picture formats, the operations are also executed according to the above flow, and finally the picture selected by the user is presented in front of the user.
In some embodiments of the present application, as shown in fig. 3, the method further includes a step of, by the S31, scanning, by the local client, the device node in the device directory, traversing the locally connected physical camera device, acquiring device information corresponding to the physical camera device node, sending, by the S32, the device information to the server through a cloud desktop protocol, creating, by the server, a camera driver according to the received device information, and writing the device information into the camera driver. By the scheme, the camera information can be called from the local client, and the related drive can be established on the server. The technical effect of recording the camera information on the server is achieved.
In some embodiments of the present application, the device information includes one or more of a resolution supportable by the camera, a format supportable by the camera, a product name of the camera, and a hardware descriptor of the camera.
In a specific embodiment, referring to fig. 4, the virtualization technology of the camera device is that after the camera device is physically connected to the local terminal, the protocol client on the local terminal reads out the device detailed information on the local camera device driver, which includes the basic hardware capability of the camera device. Including the supported picture formats (e.g., YUYV or mjpeg, even some cameras may only support GRAY), the resolution lists that the cameras can support, etc., each format has a corresponding resolution list, and these lists are likely to be different and need to be packed separately. Hardware information of the camera can be read out, including the Vendor ID and the Product ID, and special information which can identify a manufacturer of the Product and the model of the Product is collected, and is arranged together with the hardware capability information and then sent to a protocol server on a Linux cloud desktop through a protocol channel.
After the hardware information is collected by the server side on the Linux cloud desktop, on a driver layer, a virtual camera driver is created on the Linux cloud desktop through a CTWebcam camera driver management tool which is developed in a customized mode and based on the V4l2looback principle, and the hardware information of the camera driver is the hardware information of the read local camera device. In this way, the technology of virtualization of the locally physically connected camera device on the Linux cloud desktop is realized. These virtualized camera devices can be identified by the camera usage software on the desktop, including camera software, video call software, and video conferencing software.
On a Linux device management tree, a class named CTWebcam is created in a sys directory of a system to uniformly manage camera device drivers mapped by a Linux cloud desktop protocol, and each driver is created with a specific node in a devices directory of the class directory, so that hardware identification information such as Product ID and Vendor ID read from a local terminal is written. This node is also a fixed directory identified by the Linux system for the hardware device information. Therefore, software on the Linux cloud desktop can acquire the hardware information of the mapped camera device. Thus, a complete virtual mapping camera device is created on the Linux cloud desktop.
A cloud desktop camera device connection system, here see fig. 5, includes a client 50 and a server 51 for operating a cloud desktop, and is specifically configured to perform the following steps,
a) monitoring the operation of opening a camera on a cloud desktop by a user through a preset interface;
b) acquiring the camera setting through an ioctl system interface;
c) sending the camera setting and open instruction and the camera ID to a client through a cloud desktop protocol,
d) decompressing after the client receives the data packet;
e) the client opens the local camera equipment according to the corresponding camera ID;
f) and the client writes the camera setting information and starts to acquire image data.
g) And sending the acquired image data to a server through a cloud desktop protocol.
h) And searching for a corresponding camera drive according to the camera ID, and writing image data into the corresponding camera drive through ioctl.
i) And the server reads the image data from the driver and displays the image data on the cloud desktop.
In some embodiments of the application, the method further includes the step of scanning, by the local client, the device node under the device directory, traversing the locally connected physical camera device, acquiring device information corresponding to the physical camera device node, sending the device information to the server through the cloud desktop protocol, creating, by the server, a camera driver according to the received device information, and writing the device information into the camera driver.
In some embodiments of the present application, the device information includes one or more of a resolution supportable by the camera, a format supportable by the camera, a product name of the camera, and a hardware descriptor of the camera.
In some embodiments of the present application, the camera settings include camera resolution and image format.
In some embodiments of the present application, the camera ID includes a product ID and a vendor ID.
It should be noted that, although the above embodiments have been described herein, the invention is not limited thereto. Therefore, based on the innovative concepts of the present invention, the technical solutions of the present invention can be directly or indirectly applied to other related technical fields by making changes and modifications to the embodiments described herein, or by using equivalent structures or equivalent processes performed in the content of the present specification and the attached drawings, which are included in the scope of the present invention.
Claims (10)
1. A camera equipment connection method of a cloud desktop is characterized by comprising the following steps,
a) monitoring the operation of opening a camera on a cloud desktop by a user through a preset interface;
b) acquiring the camera setting through an ioctl system interface;
c) sending the camera setting and open instruction and the camera ID to a client through a cloud desktop protocol,
d) decompressing after the client receives the data packet;
e) the client opens the local camera equipment according to the corresponding camera ID;
f) the client writes the camera setting information and starts to acquire image data;
g) sending the acquired image data to a server through a cloud desktop protocol;
h) searching a corresponding camera drive according to the camera ID, and writing image data into the corresponding camera drive through ioctl;
i) and the server reads the image data from the driver and displays the image data on the cloud desktop.
2. The method for connecting the camera devices on the cloud desktop according to claim 1, further comprising the steps of scanning device nodes by a local client under a device directory, traversing locally connected physical camera devices, acquiring device information corresponding to the physical camera device nodes, sending the device information to a server through a cloud desktop protocol, creating a camera driver by the server according to the received device information, and writing the device information into the camera driver.
3. The camera device connection method of the cloud desktop according to claim 2, wherein the device information includes one or more of a resolution supportable by the camera, a format supportable by the camera, a product name of the camera, and a hardware descriptor of the camera.
4. The cloud desktop camera device connection method of claim 1, wherein the camera settings comprise camera resolution and image format.
5. The cloud desktop camera device connection method according to claim 1, wherein the camera ID includes a product ID and a vendor ID.
6. A camera equipment connection system of a cloud desktop is characterized by comprising a client and a server which can be used for operating the cloud desktop, and is specifically used for executing the following steps,
a) monitoring the operation of opening a camera on a cloud desktop by a user through a preset interface;
b) acquiring the camera setting through an ioctl system interface;
c) sending the camera setting and open instruction and the camera ID to a client through a cloud desktop protocol,
d) decompressing after the client receives the data packet;
e) the client opens the local camera equipment according to the corresponding camera ID;
f) the client writes the camera setting information and starts to acquire image data;
g) sending the acquired image data to a server through a cloud desktop protocol;
h) searching a corresponding camera drive according to the camera ID, and writing image data into the corresponding camera drive through ioctl;
i) and the server reads the image data from the driver and displays the image data on the cloud desktop.
7. The cloud desktop camera device connection system according to claim 1, further configured to perform steps of scanning, by the local client, the device node under the device directory, traversing the locally connected physical camera device, obtaining device information corresponding to the physical camera device node, sending the device information to the server via the cloud desktop protocol, creating, by the server, a camera driver according to the received device information, and writing the device information into the camera driver.
8. The cloud desktop camera device connection system of claim 7, wherein the device information comprises one or more of a camera supportable resolution, a camera supportable format, a camera product name, and a camera hardware descriptor.
9. The cloud desktop camera device connection system of claim 6, wherein the camera settings comprise camera resolution and image format.
10. The cloud desktop camera device connection system of claim 6, wherein the camera ID comprises a product ID and a vendor ID.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210698353.8A CN115118719B (en) | 2022-06-20 | 2022-06-20 | Method and system for connecting camera equipment of cloud desktop |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210698353.8A CN115118719B (en) | 2022-06-20 | 2022-06-20 | Method and system for connecting camera equipment of cloud desktop |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115118719A true CN115118719A (en) | 2022-09-27 |
| CN115118719B CN115118719B (en) | 2023-11-10 |
Family
ID=83328440
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210698353.8A Active CN115118719B (en) | 2022-06-20 | 2022-06-20 | Method and system for connecting camera equipment of cloud desktop |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115118719B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104199723A (en) * | 2014-09-09 | 2014-12-10 | 福建升腾资讯有限公司 | Camera mapping method based on virtual equipment |
| US20150244787A1 (en) * | 2014-02-21 | 2015-08-27 | Andrew T. Fausak | Front-end high availability proxy |
| US20150346931A1 (en) * | 2014-05-30 | 2015-12-03 | Citrix Systems, Inc. | Method and System for Managing Peripheral Devices for Virtual Desktops |
| WO2016161749A1 (en) * | 2015-04-10 | 2016-10-13 | 中兴通讯股份有限公司 | Data transmission method, device and system |
| CN108304247A (en) * | 2017-12-19 | 2018-07-20 | 华为技术有限公司 | The method and apparatus of access camera, server, readable storage medium storing program for executing |
| CN112287363A (en) * | 2020-10-21 | 2021-01-29 | 麒麟软件有限公司 | Sensor redirection method and system based on Android system remote desktop |
| CN114040017A (en) * | 2021-11-08 | 2022-02-11 | 麒麟软件有限公司 | Remote desktop server camera relocation system and method for Android system |
| CN114047964A (en) * | 2022-01-13 | 2022-02-15 | 麒麟软件有限公司 | Method for enabling Android-supported camera to be hot-plugged when Linux is compatible with Android system |
-
2022
- 2022-06-20 CN CN202210698353.8A patent/CN115118719B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150244787A1 (en) * | 2014-02-21 | 2015-08-27 | Andrew T. Fausak | Front-end high availability proxy |
| US20150346931A1 (en) * | 2014-05-30 | 2015-12-03 | Citrix Systems, Inc. | Method and System for Managing Peripheral Devices for Virtual Desktops |
| CN104199723A (en) * | 2014-09-09 | 2014-12-10 | 福建升腾资讯有限公司 | Camera mapping method based on virtual equipment |
| WO2016161749A1 (en) * | 2015-04-10 | 2016-10-13 | 中兴通讯股份有限公司 | Data transmission method, device and system |
| CN108304247A (en) * | 2017-12-19 | 2018-07-20 | 华为技术有限公司 | The method and apparatus of access camera, server, readable storage medium storing program for executing |
| CN112287363A (en) * | 2020-10-21 | 2021-01-29 | 麒麟软件有限公司 | Sensor redirection method and system based on Android system remote desktop |
| CN114040017A (en) * | 2021-11-08 | 2022-02-11 | 麒麟软件有限公司 | Remote desktop server camera relocation system and method for Android system |
| CN114047964A (en) * | 2022-01-13 | 2022-02-15 | 麒麟软件有限公司 | Method for enabling Android-supported camera to be hot-plugged when Linux is compatible with Android system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115118719B (en) | 2023-11-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3657824A2 (en) | System and method for multi-user control and media streaming to a shared display | |
| EP2854348B1 (en) | Interface display method and system of home gateway applicable to multiple display types | |
| CN104618793A (en) | Information processing method and electronic equipment | |
| US8209436B2 (en) | Method and system of migrating profiles in telecommunications devices | |
| CN109033393B (en) | Sticker processing method, device, storage medium and electronic equipment | |
| JP6772235B2 (en) | How to synchronize equipment lists, equipment, equipment, computer storage media and programs | |
| CN108628864B (en) | Data access method and data management device | |
| CN115118719A (en) | Method and system for connecting camera equipment of cloud desktop | |
| JP2000322354A (en) | Device and method for managing network and computer readable storage medium with method stored therein | |
| US10466954B2 (en) | Display control method and display control device | |
| US20240100415A1 (en) | Game control method and apparatus, and storage medium | |
| JP2002247539A (en) | Network projector device | |
| JP5975003B2 (en) | Virtualization control device, virtualization system, virtualization method, and virtualization control program. | |
| CN113709541A (en) | WEB-based multi-terminal equipment interaction method, system and terminal equipment | |
| JP2002095071A (en) | Network system and control method of apparatus | |
| JPH104407A (en) | Network management device and its method | |
| CN109298958A (en) | The call method and related system of service | |
| CN116661955B (en) | Hardware access method, device, electronic equipment and storage medium | |
| CN114461157B (en) | IDV client multi-screen divide-and-conquer method and system | |
| CN112596752B (en) | Internet of things method and system for electronic evidence obtaining equipment | |
| CN116347015B (en) | System and method for smooth switching based on multiple USB cameras | |
| EP4149062A1 (en) | Deployment method and apparatus for virtualized network service | |
| US20240184824A1 (en) | Data interworking method between onem2m system and ngsi-ld system | |
| CN105915624A (en) | Method, device and system for updating data and external equipment | |
| JP2004289704A (en) | Moving image system, moving image server, and its control method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |