CN113852522B - Camera binding and unbinding method based on multiple platforms - Google Patents
Camera binding and unbinding method based on multiple platforms Download PDFInfo
- Publication number
- CN113852522B CN113852522B CN202110609161.0A CN202110609161A CN113852522B CN 113852522 B CN113852522 B CN 113852522B CN 202110609161 A CN202110609161 A CN 202110609161A CN 113852522 B CN113852522 B CN 113852522B
- Authority
- CN
- China
- Prior art keywords
- platform
- camera
- home platform
- unbinding
- binding
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/2803—Home automation networks
- H04L12/2807—Exchanging configuration information on appliance services in a home automation network
-
- 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/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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/50—Network services
- H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Automation & Control Theory (AREA)
- Mobile Radio Communication Systems (AREA)
- Studio Devices (AREA)
Abstract
The invention provides a camera binding method based on a plurality of platforms, wherein the plurality of platforms can comprise an intelligent home platform and a third-party capability platform, and the method comprises the following steps: initiating a camera distribution network by client equipment; acquiring the online state of the camera from the third-party capability platform by the client equipment; in response to the fact that the camera is determined to be on line, calling a binding interface of the intelligent home platform by the client equipment, wherein the calling is asynchronous calling; calling a binding interface of a third-party capability platform by the intelligent home platform to synchronously bind to the third-party capability platform; and responding to the successful synchronization, and executing the binding operation by the intelligent home platform. In addition, the invention also provides a camera unbinding method based on a plurality of platforms. The invention can fully realize the synchronization of the platform binding relationship, and adopts an asynchronous calling mode to realize the high efficiency of interface calling.
Description
Technical Field
The invention relates to a communication technology, in particular to a camera binding and unbinding method based on multiple platforms.
Background
With the large-scale deployment of smart home products, monitoring cameras are increasingly applied. For example, a monitoring camera may be used to care for children, care for the elderly, security monitoring, care for pets, and so forth. Massive home monitoring video streams are uploaded to the platform through the network. In practice, the video stream captured by the camera can be transmitted not only to the smart home platform for smart home applications, but also to third party capability platforms for other purposes. Generally speaking, before a client device can obtain a video stream of a camera from an intelligent home platform or a third-party capability platform, a binding relationship between the client device and the camera needs to be stored in the intelligent home platform or the third-party capability platform. In addition, for example, in the case that the already bound camera is no longer used, the camera and the client device may be unbound, and the binding relationship stored in the smart home platform or the third party capability platform may be deleted.
However, most of the camera binding and unbinding methods in the prior art fail to consider an effective multi-platform data synchronization method, and also fail to consider efficient asynchronous data interaction between the device and the platform.
Accordingly, there is a need in the art for improved multi-platform based camera binding and unbinding methods.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
In view of the above-described deficiencies in the prior art, it is an object of the present invention to provide an improved multi-platform based camera binding and unbinding method.
According to a first aspect of the present invention, a camera binding method based on multiple platforms is provided, where the multiple platforms may include a smart home platform and a third party capability platform, and the method may include: initiating a camera distribution network by the client equipment; acquiring the online state of the camera from the third-party capability platform by the client equipment; in response to the fact that the camera is determined to be on line, calling a binding interface of the intelligent home platform by the client equipment, wherein the calling is asynchronous calling; calling a binding interface of a third-party capability platform by the intelligent home platform so as to synchronously bind to the third-party capability platform; and responding to the successful synchronization, and executing the binding operation by the intelligent home platform.
In an embodiment of the first aspect of the invention, the method may further comprise: before the camera distribution network is initiated, the client device obtains the distribution network mode of the camera from the third-party capability platform, wherein the distribution network mode can comprise a wired distribution network and a wireless distribution network.
In one embodiment of the first aspect of the present invention, the method may further comprise: and after the network distribution mode of the camera is obtained, the client equipment requests to take the camera off the line.
In one embodiment of the first aspect of the present invention, the method may further comprise: and the client equipment initiates a binding relationship checking request to the intelligent home platform to inquire whether the intelligent home platform has the binding relationship of the camera.
In an embodiment of the first aspect of the present invention, if the smart home platform has a binding relationship of the camera, it is determined that the binding of the camera is successful.
In an embodiment of the first aspect of the present invention, if the smart home platform does not have a binding relationship of the camera, the smart home platform calls a unbinding interface of the third party capability platform.
According to a second aspect of the present invention, there is provided a camera unbinding method based on multiple platforms, where the multiple platforms may include a smart home platform and a third party capability platform, and the method may include: sending a camera unbinding request to the intelligent home platform by the client equipment to call an unbinding interface of the intelligent home platform, wherein the call is asynchronous call; calling a unbinding interface of a third-party capability platform by the intelligent home platform; the third-party capability platform executes unbinding operation and returns an unbinding result to the intelligent home platform; and responding to the successful unbinding of the third-party capability platform, and executing the unbinding operation by the intelligent home platform.
In one embodiment of the second aspect of the invention, the method may further comprise: and the client equipment initiates a binding relationship checking request to the intelligent home platform to inquire whether the intelligent home platform has the binding relationship of the camera.
In an embodiment of the second aspect of the present invention, if the smart home platform has no binding relationship of the camera, it is determined that the unbinding of the camera is successful.
In an embodiment of the second aspect of the present invention, if the smart home platform has a binding relationship with the camera, the smart home platform re-executes the unbinding operation.
By adopting the technical scheme provided by the invention, the synchronization of the platform binding relationship can be fully realized, and the high efficiency of interface calling is realized by adopting an asynchronous calling mode.
These and other features and advantages will become apparent upon reading the following detailed description and upon reference to the accompanying drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory only and are not restrictive of aspects as claimed.
Drawings
So that the manner in which the above recited features of the present invention can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to embodiments, some of which are illustrated in the appended drawings. It is to be noted, however, that the appended drawings illustrate only certain typical aspects of this invention and are therefore not to be considered limiting of its scope, for the description may admit to other equally effective aspects.
Fig. 1 illustrates a schematic diagram of a multi-platform based camera binding process according to one embodiment of the invention.
Fig. 2 illustrates a flow diagram of a multi-platform based camera binding method according to an embodiment of the present invention.
Fig. 3 illustrates a schematic diagram of a multi-platform based camera unbinding process in accordance with an embodiment of the invention.
Fig. 4 illustrates a flow diagram of a multi-platform based camera unbinding method according to an embodiment of the present invention.
Fig. 5 illustrates a block diagram of an example of a hardware implementation of an apparatus according to one embodiment of the invention.
Detailed Description
The present invention will be described in detail below with reference to the attached drawings, and the features of the present invention will be further apparent from the following detailed description.
Fig. 1 illustrates a schematic diagram 100 of a multiple platform based camera binding process according to one embodiment of the invention. Diagram 100 illustrates a two platform based camera binding process. It should be noted that the present invention is not limited to two platforms, but may involve three, four, or more platforms.
In the example shown in fig. 1, the camera binding process may involve a client device, a smart home platform 110, a third party capability platform 115, and a camera 120. The handset client 105 may be an example of a client device. The client device may also include a tablet, a portable device, and/or any other user device capable of establishing a binding relationship with the camera 120. The camera 120 can be provided with wired and/or wireless (e.g., wiFi) networking capabilities and a unique device identification code so that a binding relationship can be established with the cell phone client 105 (e.g., cell phone number). The cell phone client 105 can be used to initiate network distribution, binding, and unbinding requests for the cameras. The smart home platform 110 may be used to manage various devices in a home, process camera binding and unbinding requests, and store and synchronize camera binding relationships. The third party capability platform 115 may be used to transmit the video stream while storing the binding relationship. In the present invention, the binding relationship refers to a correspondence relationship between the client device and the camera. When the smart home platform 110 and the third party capability platform 115 store the binding relationship between the client device and the camera, the client device may obtain the video stream collected by the camera through the smart home platform 110 and the third party capability platform 115.
Steps 122-128 in fig. 1 are optional steps. In step 122, the mobile phone client 105 requests the third party capability platform 115 to obtain a distribution network mode of the camera 120, where the distribution network mode may be a wired distribution network and/or a wireless distribution network. For example, the mobile phone client 105 may obtain a unique device identification code of the camera 120 by scanning a two-dimensional code on the camera 120, and then may send a request containing the device identification code to the third party capability platform 115 to obtain a distribution network mode of the camera 120.
In step 124, the third party capability platform 115 returns the network distribution mode of the camera 120 to the mobile client 105.
At step 126, the mobile client 105 requests the third party capability platform 115 to take the camera 120 offline. This action is intended to reset the camera 120.
At step 128, the third party capability platform 115 returns the offline result to the handset client 105.
At step 130, the cell phone client 105 initiates a camera distribution network to enable the camera 120 to access the network for connection to the third party capability platform 115. For example, the mobile phone client 105 may initiate a camera distribution network based on the distribution network mode of the camera 120 obtained in step 124.
At step 132, the cell phone client 105 can request a query from the third party capability platform 115 for the presence status of the camera 120.
At step 134, the third party capability platform 115 can return the camera's online status to the cell phone client 105.
At step 136, if it is determined that the camera is not online (e.g., the third party capability platform 115 cannot contact the camera 120), it indicates that the distribution network has failed, and the entire binding process ends.
In step 138, if it is determined that the camera is online, the mobile phone client 105 may call a binding interface of the smart home platform 110 to request that the binding relationship between the mobile phone client 105 and the camera 120 is stored in the smart home platform 110. In the present invention, the binding interface refers to a software interface, which is used for storing the binding relationship between the mobile phone client 105 and the camera 120, for example. It should be noted that the call in step 138 is an asynchronous call, and the smart home platform 110 does not immediately return the binding result, but only returns the interface call status. Because the binding operation of the intelligent home platform and the third-party capability platform may take a certain time, the interface calling state is returned immediately, so that the user experience can be obviously enhanced, and the user is prevented from waiting for a long time.
In step 140, the smart home platform 110 returns a binding interface calling result to the mobile phone client 105.
At step 142, the smart home platform 110 invokes the binding interface of the third party capability platform 115 to synchronize the binding relationship to the third party capability platform 115. Here, synchronizing the binding relationship may include the third party capability platform 115 performing a binding operation to store the binding relationship of the cell phone client 105 and the camera 120 in the third party capability platform 115. It should be understood that in situations involving more than three platforms, the smart home platform 110 may also invoke binding interfaces of other platforms to synchronize binding relationships to these other platforms.
In step 144, the third party capability platform 115 returns the synchronization result to the smart home platform 110. That is, whether the third party capability platform 115 has stored the binding relationship of the cell phone client 105 and the camera 120 in the third party capability platform 115.
In step 146, if the synchronization fails, the smart home platform 110 repeats step 142 until the synchronization is successful or times out or a maximum number of repetitions is reached. If the synchronization fails after the time-out or the maximum number of repetitions is reached, the entire binding process ends.
In step 148, the smart home platform 110 processes the binding operation on the smart home platform side. For example, the binding interface of the smart home platform 110 stores the binding relationship between the mobile phone client 105 and the camera 120 in the smart home platform 110.
In step 150, the mobile phone client 105 sends a binding relationship check request to the smart home platform 110 to query whether the binding relationship between the mobile phone client 105 and the camera 120 exists on the smart home platform side. In one example, the handset client 105 can send the binding relationship check request after a predetermined time after receiving the invocation result at step 140.
In step 152, the smart home platform 110 returns the binding verification result to the mobile phone client 105.
At step 154, if a binding relationship exists at the smart home platform 110, the binding is successful.
At step 156, if the smart home platform binding fails, the smart home platform 110 invokes the unbind interface of the third party capability platform 115. In the present invention, the binding-removal interface refers to a software interface, which is used to delete the binding relationship between the mobile phone client 105 and the camera 120, for example.
At step 158, the third party capability platform 115 returns the unbinding result to the smart home platform 110.
Fig. 2 illustrates a flow diagram of a multi-platform based camera binding method 200 according to one embodiment of the invention. The camera binding method 200 may involve a client device (e.g., cell phone client 105), a smart home platform (e.g., smart home platform 110), a third party capability platform (e.g., third party capability platform 115), and a camera (e.g., camera 120).
At block 210, method 200 may include initiating, by a client device, a camera distribution network. The purpose of the distribution network is to enable the camera to access the network for connection to a third party capability platform. In one embodiment, before initiating a camera distribution network, a client device may obtain a distribution network mode of the camera from a third party capability platform, where the distribution network mode may include a wired distribution network and a wireless distribution network. In another embodiment, after acquiring the distribution network mode of the camera, the client device may request to take the camera off-line, so as to reset the camera.
At block 220, the method 200 may include obtaining, by the client device, an online status of the camera from the third party capability platform, i.e., determining whether the camera is successful in distributing the network.
At block 230, the method 200 may include, in response to determining that the camera is online (i.e., determining that the camera distribution network was successful), invoking, by the client device, a binding interface of the smart home platform (e.g., to request that a binding relationship of the client device and the camera be stored in the smart home platform), wherein the invocation is an asynchronous invocation. Here, the asynchronous call means that the smart home platform does not immediately return the binding result, but only returns the interface call state.
At block 240, the method 200 may include invoking, by the smart home platform, a binding interface of the third party capability platform to synchronize the binding relationship to the third party capability platform. In one embodiment, synchronizing the binding relationship to the third party capability platform may include storing the binding relationship of the client device and the camera to the third party capability platform.
At block 250, the method 200 may include performing, by the smart home platform, the binding operation in response to the synchronization being successful. In one embodiment, after the third-party capability platform successfully stores the binding relationship between the client device and the camera to the third-party capability platform, the smart home platform performs the binding operation of storing the binding relationship between the client device and the camera to the smart home platform.
In an embodiment, the method 200 may further include initiating, by the client device, a binding relationship check request to the smart home platform to query whether the smart home platform has a binding relationship of the camera. And if the intelligent home platform has the binding relationship of the cameras, determining that the binding of the cameras is successful. Otherwise, if the intelligent home platform does not have the binding relation of the camera, the intelligent home platform calls a unbinding interface of the third-party capacity platform to delete the binding relation between the client equipment and the camera stored in the third-party capacity platform.
Fig. 3 illustrates a schematic diagram 300 of a multi-platform based camera unbinding process according to one embodiment of the invention. Diagram 300 illustrates a two platform based camera unbinding process. It should be noted that the present invention is not limited to two platforms, but may involve three, four, or more platforms.
In the example shown in fig. 3, the camera unbinding process can involve the cell phone client 105, the smart home platform 110, and the third party capability platform 115. Before unbinding, the smart home platform 110 and the third party capability platform 115 respectively store the binding relationship between the mobile phone client 105 and the camera.
In step 305, the mobile phone client 105 sends a camera unbinding request to the smart home platform 110 to call the unbinding interface of the smart home platform, where the call is an asynchronous call (i.e., the smart home platform does not immediately return an unbinding result, but returns an unbinding interface call result). Because the unbinding operation of the intelligent home platform and the third-party capability platform may take a certain time, the interface calling state is returned immediately, so that the user experience can be obviously enhanced, and the user is prevented from waiting for a long time.
In step 310, the smart home platform 110 returns the result of the call of the binding interface to the mobile phone client 105.
At step 315, the smart home platform 110 calls a unbinding interface of the third party capability platform 115 to request camera unbinding (e.g., delete the binding relationship of the cell phone client 105 and camera stored in the third party capability platform 110). It should be understood that in situations involving more than three platforms, the smart home platform 110 may also invoke unbinding interfaces of other platforms to request camera unbinding.
At step 320, the third party capability platform 115 returns the unbinding result to the smart home platform 110.
At step 325, if the third party capability platform 115 fails to unbind, then step 315 is repeated until successful or a timeout or maximum number of iterations is reached.
In step 330, if the third party capability platform 115 is successfully unbound, the smart home platform 110 performs an unbinding operation to delete the binding relationship between the mobile phone client 105 and the camera stored in the smart home platform 110.
In step 335, the mobile phone client 105 sends a binding relationship check request to the smart home platform 110 to query whether the binding relationship between the mobile phone client 105 and the camera exists on the smart home platform side. In one example, the handset client 105 may send the binding relationship check request after a predetermined time after receiving the interface invocation result at step 310.
In step 340, the smart home platform 110 returns the binding verification result to the mobile phone client 105.
In step 345, if the verification result is that the intelligent home platform is successfully unbound, the unbinding process is finished.
In step 350, if the verification result is that the intelligent home platform is not unbound, the mobile phone client 105 requests the intelligent home platform 110 to re-execute the unbinding operation.
Fig. 4 illustrates a flow diagram of a multi-platform based camera unbinding method 400 according to one embodiment of the invention. The camera unbinding method 200 can involve a client device (e.g., the cell phone client 105), a smart home platform (e.g., the smart home platform 110), and a third party capability platform (e.g., the third party capability platform 115).
At block 410, the method 400 may include sending, by the client device, a camera unbinding request to the smart home platform to invoke a unbinding interface of the smart home platform (e.g., to request deletion of a binding relationship of the client device to the camera stored in the smart home platform), where the call is an asynchronous call. Here, the asynchronous call means that the smart home platform does not immediately return the unbinding result, but only returns the interface call state.
At block 420, the method 400 may include invoking, by the smart home platform, an unbinding interface of the third party capability platform (e.g., to request deletion of a binding relationship of a client device and a camera stored in the third party capability platform).
At block 430, the method 400 may include performing, by the third party capability platform, an unbinding operation and returning an unbinding result to the smart home platform. In one embodiment, the operations of block 430 may include deleting, by the third party capability platform, the binding relationship of the client device and the camera stored in the third party capability platform using its unbinding interface, and returning the unbinding result to the smart home platform.
At block 440, the method 400 may include performing, by the smart home platform, an unbinding operation in response to the third party capability platform unbinding being successful. For example, in the case that the unbinding result returned to the smart home platform by the third party capability platform indicates that the unbinding is successful, the smart home platform may use its unbinding interface to delete the binding relationship between the client device and the camera stored in the smart home platform.
In an embodiment, the method 400 may further include initiating, by the client device, a binding relationship check request to the smart home platform to query whether the smart home platform has a binding relationship of the camera. And if the intelligent home platform does not have the binding relationship of the camera, determining that the camera is successfully unbound. Otherwise, if the intelligent home platform still has the binding relationship of the camera, the intelligent home platform executes the unbinding operation again.
Compared with the prior art, the camera binding and unbinding method provided by the invention has the advantages that on one hand, the binding relationship between the platforms is verified in an asynchronous calling mode, so that the interface calling efficiency is improved; on the other hand, the synchronization of the platform binding relationship is realized through the interface synchronous calling mode between the platforms.
Fig. 5 illustrates a block diagram of an example of a hardware implementation of an apparatus 500 according to one embodiment of the invention. The apparatus 500 may be an example of a client device, smart home platform, or third party capability platform described herein. The apparatus 500 may be implemented using a processing system 514 that includes one or more processors 504. Examples of processor 504 include microprocessors, microcontrollers, digital Signal Processors (DSPs), field Programmable Gate Arrays (FPGAs), programmable Logic Devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. In various examples, the apparatus 500 may be configured to perform any one or more of the functions described herein. That is, the processor 504 as utilized in the apparatus 500 may be utilized to implement the methods described above with reference to fig. 1-4.
In this example, the processing system 514 may be implemented with a bus architecture, represented generally by the bus 502. The bus 502 may include any number of interconnecting buses and bridges depending on the specific application of the processing system 514 and the overall design constraints. The bus 502 communicatively couples various circuits including one or more processors (represented generally by processor 504), memory 505, and computer-readable media (represented generally by computer-readable media 506) together. The bus 502 may also link various other circuits such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art, and therefore, will not be described any further. A bus interface 508 provides an interface between the bus 502 and a transceiver 510. The transceiver 510 provides a communication interface or means for communicating with various other apparatus over a transmission medium. Depending on the nature of the device, a user interface 512 (e.g., keypad, display, speaker, microphone, joystick) may also be provided. Of course, such a user interface 512 is optional and may be omitted in some examples.
The processor 504 is responsible for managing the bus 502 and general processing, including the execution of software stored on the computer-readable medium 506. The software, when executed by the processor 504, causes the processing system 514 to perform the various functions described for any particular apparatus. The computer-readable medium 506 and the memory 505 may also be used for storing data that is manipulated by the processor 504 when executing software.
One or more processors 504 in the processing system may execute software. Software should be construed broadly to mean instructions, instruction sets, code segments, program code, programs, subprograms, software modules, applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to in software, firmware, middleware, microcode, hardware description language, or other terminology. The software may reside on computer readable media 506. Computer-readable media 506 may be non-transitory computer-readable media. By way of example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tape), optical disks (e.g., a Compact Disc (CD) or a Digital Versatile Disc (DVD)), smart cards, flash memory devices (e.g., card, stick, or key drives), random Access Memory (RAM), read Only Memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically Erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and/or instructions that may be accessed and read by a computer. Computer-readable media 506 may reside in processing system 514, external to processing system 514, or be distributed across multiple entities including processing system 514. The computer-readable medium 506 may be embodied in a computer program product. By way of example, a computer program product may include a computer-readable medium in packaging material. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure, depending on the particular application and the overall design constraints imposed on the overall system.
In one or more examples, computer-readable storage media 506 may include software configured for various functions. The software may include instructions that may configure the processing system 514 to perform one or more of the functions described with reference to fig. 1-4.
In the description of the present invention, it is to be understood that the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance.
As will be appreciated by one of ordinary skill in the art, various embodiments of the present invention may be provided as a method, apparatus, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-executable program code stored therein.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus, systems, and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks and/or flowchart block or blocks.
Although the various aspects of the present invention have been described thus far with reference to the accompanying drawings, the above-described methods, systems, and apparatuses are merely examples, and the scope of the present invention is not limited to these aspects but only by the appended claims and equivalents thereof. Various components may be omitted or may be replaced with equivalent components. In addition, the steps may also be performed in a different order than described in the present invention. Further, the various components may be combined in various ways. It is also important that as technology develops, many of the described components can be replaced by equivalent components appearing later. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A camera binding method based on a plurality of platforms, wherein the plurality of platforms comprise an intelligent home platform and a third party capability platform, and the method comprises the following steps:
initiating a camera distribution network by the client equipment;
acquiring, by the client device, an online status of the camera from the third party capability platform;
in response to the fact that the camera is determined to be on line, the client device calls a binding interface of the intelligent home platform, wherein the calling is asynchronous calling;
calling a binding interface of the third-party capability platform by the intelligent home platform to synchronously bind to the third-party capability platform; and
and responding to the successful synchronization, and executing the binding operation by the intelligent home platform.
2. The method of claim 1, further comprising:
before a camera is started to distribute a network, the client equipment acquires a network distribution mode of the camera from the third-party capability platform, wherein the network distribution mode comprises a wired network distribution mode and a wireless network distribution mode.
3. The method of claim 2, further comprising:
and after the network distribution mode of the camera is obtained, the client equipment requests to enable the camera to be offline.
4. The method of claim 1, further comprising:
and initiating a binding relationship checking request to the intelligent home platform by the client equipment to inquire whether the intelligent home platform has the binding relationship of the camera.
5. The method according to claim 4, wherein if the smart home platform has the binding relationship of the camera, it is determined that the binding of the camera is successful.
6. The method according to claim 4, wherein if the smart home platform does not have the binding relationship of the camera, invoking, by the smart home platform, a unbinding interface of the third party capability platform.
7. A camera unbinding method based on a plurality of platforms, wherein the plurality of platforms comprise an intelligent home platform and a third party capability platform, and the method comprises the following steps:
sending a camera unbinding request to the intelligent home platform by the client equipment to call an unbinding interface of the intelligent home platform, wherein the call is asynchronous call;
calling, by the smart home platform, a unbinding interface of the third party capability platform;
the third-party capacity platform executes unbinding operation and returns an unbinding result to the intelligent home platform; and
and responding to the successful unbinding of the third-party capability platform, and executing the unbinding operation by the intelligent home platform.
8. The method of claim 7, further comprising:
and initiating a binding relationship checking request to the intelligent home platform by the client equipment to inquire whether the intelligent home platform has the binding relationship of the camera.
9. The method according to claim 8, wherein if the smart home platform does not have the binding relationship of the camera, it is determined that the unbinding of the camera is successful.
10. The method according to claim 8, wherein if the smart home platform has the binding relationship of the camera, the smart home platform re-executes the unbinding operation.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110609161.0A CN113852522B (en) | 2021-06-01 | 2021-06-01 | Camera binding and unbinding method based on multiple platforms |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110609161.0A CN113852522B (en) | 2021-06-01 | 2021-06-01 | Camera binding and unbinding method based on multiple platforms |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113852522A CN113852522A (en) | 2021-12-28 |
| CN113852522B true CN113852522B (en) | 2023-04-07 |
Family
ID=78973016
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110609161.0A Active CN113852522B (en) | 2021-06-01 | 2021-06-01 | Camera binding and unbinding method based on multiple platforms |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113852522B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2024031680A1 (en) * | 2022-08-12 | 2024-02-15 | Oppo广东移动通信有限公司 | Device unbinding method and apparatus, device, storage medium, and program product |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107342984A (en) * | 2017-06-13 | 2017-11-10 | 浙江大华技术股份有限公司 | A kind of system, method and device for apparatus bound |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105282234A (en) * | 2015-09-14 | 2016-01-27 | 北京奇虎科技有限公司 | Intelligent device connection method, device and system |
| CN105245427A (en) * | 2015-11-24 | 2016-01-13 | 深圳酷宅科技有限公司 | Multi-Internet of Things cloud platform terminal access and control system based on bus adaption |
| CN107547314B (en) * | 2016-06-24 | 2021-03-12 | 夏普株式会社 | Intelligent household appliance cloud platform and intelligent household cloud system |
| CN108512881A (en) * | 2017-02-28 | 2018-09-07 | 中兴通讯股份有限公司 | A kind of intelligent domestic system |
| CN107342933B (en) * | 2017-06-16 | 2021-03-19 | 上海庆科信息技术有限公司 | Activation and binding method and device for intelligent equipment |
| CN109474595B (en) * | 2018-11-13 | 2022-09-20 | 京东方科技集团股份有限公司 | Electronic equipment binding method, electronic equipment, mobile terminal and server |
| CN109587016B (en) * | 2018-11-20 | 2021-08-13 | 广东美的制冷设备有限公司 | Household appliance binding system, method, mobile terminal, server, household appliance and medium |
| CN109802886B (en) * | 2019-01-28 | 2021-10-19 | 奥克斯空调股份有限公司 | Method and device for binding third party public number, air conditioner and storage medium |
| CN110830365A (en) * | 2019-11-12 | 2020-02-21 | 芜湖盟博科技有限公司 | Method for developing cloud platform by using WeChat hardware |
-
2021
- 2021-06-01 CN CN202110609161.0A patent/CN113852522B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107342984A (en) * | 2017-06-13 | 2017-11-10 | 浙江大华技术股份有限公司 | A kind of system, method and device for apparatus bound |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113852522A (en) | 2021-12-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20220179682A1 (en) | Task processing method, apparatus, and system based on distributed system | |
| CN113568884B (en) | File management method and device, electronic equipment and storage medium | |
| KR101820392B1 (en) | Method, device and system for establishing data connection | |
| CN104756080B (en) | Extend the function of host equipment | |
| WO2016165470A1 (en) | Vnf instance processing method and device, and vnfm | |
| TW201730790A (en) | Method, device and system for migrating physical machine data to cloud | |
| CN113852522B (en) | Camera binding and unbinding method based on multiple platforms | |
| CN113300854A (en) | Edge node capability expansion method, system and expansion box | |
| CN111200651A (en) | Method, system, device and medium for timed calling of microservice | |
| CN114926163A (en) | Resource cross-chain transfer method and device | |
| CN106375999A (en) | Method and device for quickly connecting WiFi | |
| EP2445171B1 (en) | File transfer protocol client and implementing method thereof | |
| CN104570967B (en) | Long-range control method and system based on android system | |
| CN102413247A (en) | Method and device for recovering crash site of terminal | |
| CN113821333A (en) | Android application program migration method and device | |
| CN106161517B (en) | The method and apparatus for realizing cloud storage access by cloud file system | |
| CN115525453B (en) | Multi-screen collaborative interrupt processing method and electronic equipment | |
| CN108289165B (en) | Method and device for realizing camera control based on mobile phone and terminal equipment | |
| WO2020168666A1 (en) | Data deployment method based on dht network, node device, data deployment system and storage medium | |
| CN115811538A (en) | Method, apparatus, system and medium for requesting and processing digital key service | |
| CN115640169A (en) | Method, system, device and storage medium for ensuring that a master cluster stops providing services | |
| CN114726711A (en) | Method and system for cooperative processing service between devices | |
| JP2015528260A (en) | Method and device for providing communication connections for multiple candidate applications within a mobile device | |
| KR20130056539A (en) | Apparatas and method for performing communication with media transfer protocol supported device in a portable terminal | |
| CN108805741B (en) | Fusion method, device and system of power quality data |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220130 Address after: Room 1423, No. 1256 and 1258, Wanrong Road, Jing'an District, Shanghai 200072 Applicant after: Tianyi Digital Life Technology Co.,Ltd. Address before: 201702 3rd floor, 158 Shuanglian Road, Qingpu District, Shanghai Applicant before: Tianyi Smart Family Technology Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |