Camera mounting method, calling method, system, device and storage medium

Abstract

The present application relates to a camera mounting method, calling method, system, device and storage medium. The method comprises: receiving a mounting request for a camera to be mounted sent by a client, the mounting request comprising a first signature parameter generated by the client; parsing the mounting request to obtain a parsing result, and generating a second signature parameter of the camera to be mounted according to the parsing result; matching the first signature parameter with the second signature parameter, and if they are the same, obtaining a target node of the camera to be mounted, and mounting the camera to be mounted under the target node. The use of this method can realize safe and efficient mounting of cameras, and improve the accuracy of the mounting target node of the camera.

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a camera mounting method, calling method, system, device and storage medium. Background Art

[0002] With the continuous development of Internet of Things technology, the functions of cameras are becoming more and more abundant. By connecting to the network, cameras can realize functions such as remote monitoring and real-time video transmission, which greatly improves people's life and work experience.

[0003] When a large number of new cameras are installed, the registration of the cameras consumes a lot of manpower and material resources, and there is a possibility of inaccurate registration nodes. Summary of the invention

[0004] Based on this, it is necessary to provide a camera mounting method, calling method, system, device and storage medium to address the above technical problems.

[0005] In a first aspect, the present application provides a camera mounting method, the method comprising:

[0006] Receiving a docking request for a camera to be docked sent by a client, wherein the docking request includes a first signature parameter generated by the client;

[0007] Parsing the attachment request to obtain a parsing result, and generating a second signature parameter of the camera to be attached according to the parsing result;

[0008] The first signature parameter is matched with the second signature parameter. If they are the same, the target node of the camera to be mounted is obtained, and the camera to be mounted is mounted under the target node.

[0009] In one embodiment, parsing the docking request to obtain a parsing result, and generating a second signature parameter of the camera to be docked according to the parsing result includes:

[0010] Parsing the docking request to obtain the encryption parameters and application ID of the camera to be docked;

[0011] Determine the key information of the camera to be attached according to the application ID;

[0012] According to the secret key information, a signature calculation is performed on the encryption parameter and the application ID to generate a second signature parameter.

[0013] In one embodiment, matching the first signature parameter with the second signature parameter, if they are the same, obtaining the target node of the camera to be mounted, and mounting the camera to be mounted under the target node includes:

[0014] Decrypt the encrypted parameters of the camera to be attached according to the secret key information, and extract the camera parameters of the camera to be attached and the user selection node;

[0015] It is determined whether there is a binding relationship between the camera parameters and the user information of the client. If so, the user selected node is used as the target node of the camera to be attached.

[0016] In one embodiment, the step of docking the camera to be docked under the target node includes:

[0017] Determine whether the target node belongs to the pre-allocated docking area of ​​the camera to be docked. If so, dock the camera to be docked under the target node.

[0018] In one embodiment, before receiving the docking request of the camera to be docked sent by the client, the method further includes:

[0019] According to the hierarchical coding rules, an administrative region tree diagram is constructed, wherein the administrative region tree diagram includes region nodes and region codes of the region nodes;

[0020] The user information of the client is obtained, and based on the user information, a camera docking area is pre-allocated for each of the clients from the administrative area tree diagram.

[0021] In one embodiment, the regional node includes a root node and a child node, the regional code of the root node is composed of a province code, an industry code and a self-incrementing serial number, and the regional code of the child node is composed of a parent regional code and a self-incrementing serial number.

[0022] In a second aspect, the present application also provides a camera calling method, the method comprising:

[0023] Receive the call request sent by the client;

[0024] According to the calling request, the pre-allocated docking area of ​​the client is returned; the client selects a target camera from the docking area for display, and the target camera includes the camera docked by the client and / or the cameras docked by other clients.

[0025] In a third aspect, the present application further provides a camera mounting system, the system comprising:

[0026] A receiving module, used for receiving a docking request for a camera to be docked sent by a client, wherein the docking request includes a first signature parameter generated by the client;

[0027] A parsing module, used for parsing the docking request to obtain a parsing result, and generating a second signature parameter of the camera to be docked according to the parsing result;

[0028] The mounting module is used to match the first signature parameter with the second signature parameter. If they are the same, the target node of the camera to be mounted is obtained, and the camera to be mounted is mounted under the target node.

[0029] In a fourth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the contents described in the first aspect above are implemented.

[0030] In a fifth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the content described in the first aspect above is implemented.

[0031] The above-mentioned camera mounting method, calling method, system, device and storage medium receive a mounting request for the camera to be mounted sent by the client, and the mounting request includes a first signature parameter generated by the client; parses the mounting request to obtain a parsing result, and generates a second signature parameter of the camera to be mounted based on the parsing result; matches the first signature parameter with the second signature parameter, and if they are the same, obtains the target node of the camera to be mounted, and mounts the camera to be mounted under the target node, thereby realizing safe and efficient mounting of the camera, and at the same time improving the accuracy of the camera's mounting target node. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 A diagram showing an application environment of a camera mounting method in an embodiment;

[0034] Figure 2 A schematic diagram of a process of a camera mounting method in one embodiment;

[0035] Figure 3 is a flow chart of step 202 in one embodiment;

[0036] Figure 4 is a flow chart of step 203 in one embodiment;

[0037] Figure 5 A schematic diagram of a process of pre-allocating a docking area of ​​a camera for a client in one embodiment;

[0038] Figure 6 A structural block diagram of an administrative region tree diagram in an embodiment;

[0039] Figure 7 A schematic diagram of a process of a camera calling method in one embodiment;

[0040] Figure 8 A structural block diagram of a camera mounting system in one embodiment;

[0041] Fig. 9 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0042] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0043] Unless otherwise defined, the technical terms or scientific terms involved in this application should be understood by people with ordinary skills in the technical field to which this application belongs. The words "one", "a", "a", "the" and the like involved in this application do not indicate a quantity limitation, and may indicate the singular or plural. The terms "include", "comprise", "have" and any of their variations involved in this application are intended to cover non-exclusive inclusions; for example, a process, method, system, product or device that includes a series of steps or modules (units) is not limited to the listed steps or units, but may also include steps or units that are not listed, or may also include other steps or units inherent to these processes, methods, products or devices. The words "connect", "connected", "coupled" and the like involved in this application are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The "multiple" involved in this application refers to two or more. "And / or" describes the association relationship of associated objects, indicating that there may be three relationships, for example, "A and / or B" can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects before and after are in an "or" relationship. The terms "first", "second", "third", etc. involved in this application are only used to distinguish similar objects and do not represent a specific ordering of the objects.

[0044] The camera mounting method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown, the client 102 communicates with the server 104 through a network. The data storage system 106 can store data that the server 104 needs to process. The data storage system 106 can be integrated on the server 104, or placed on the cloud or other network servers.

[0045] The server 104 receives a docking request for a camera to be docked sent by a client, wherein the docking request includes a first signature parameter generated by the client; the docking request is parsed to obtain a parsing result, and a second signature parameter of the camera to be docked is generated based on the parsing result; the first signature parameter is matched with the second signature parameter, and if they are the same, a target node of the camera to be docked is obtained, and the camera to be docked is docked under the target node.

[0046] The client 102 may be, but is not limited to, various cameras, personal computers, laptops, smart phones, tablet computers, etc. The server 104 may be an independent physical server, a server cluster or a distributed system consisting of multiple physical servers, or a cloud server providing cloud computing services.

[0047] In an exemplary embodiment, Figure 2 As shown, a camera mounting method is provided, which is applied to Figure 1 The server in is taken as an example to illustrate, including the following steps 201 to 203.

[0048] Step 201: receiving a docking request for a camera to be docked sent by a client, wherein the docking request includes a first signature parameter generated by the client.

[0049] Step 202: parse the docking request to obtain a parsing result, and generate a second signature parameter of the camera to be docked according to the parsing result.

[0050] Specifically, the docking request is parsed to obtain a parsing result including the client application ID, user information and encryption parameters of the camera to be docked. According to the parsing result, a second signature parameter of the camera to be docked is generated on the server.

[0051] Step 203, matching the first signature parameter with the second signature parameter, if they are the same, obtaining the target node of the camera to be mounted, and mounting the camera to be mounted under the target node.

[0052] Specifically, the first signature parameter of the client is matched with the second signature parameter generated on the server. If the two are the same, it means that the camera to be mounted can be mounted on the server. The target node of the camera to be mounted is obtained from the server, and the camera to be mounted is mounted under the target node.

[0053] In the above-mentioned camera mounting method, by comparing whether the first signature parameter of the client is the same as the second signature parameter generated on the server based on the mounting request, the target node for the camera to be mounted is determined, thereby achieving safe and efficient mounting of the camera, while improving the accuracy of the camera's mounting target node.

[0054] In an exemplary embodiment, Figure 3 As shown, step 202 parses the docking request to obtain a parsing result, and generates a second signature parameter of the camera to be docked based on the parsing result, specifically including the following steps 301 to 303.

[0055] Step 301, parse the docking request to obtain the encryption parameters and application ID of the camera to be docked.

[0056] Step 302: Determine the key information of the camera to be attached according to the application ID.

[0057] Step 303: Perform signature calculation on the encryption parameter and the application ID according to the secret key information to generate a second signature parameter.

[0058] Specifically, before the client sends a docking request, the user logs in to the client through user information, selects the node to be docked of the camera to be docked on the client, and encrypts the camera parameters and the user-selected node using the XXTEA algorithm according to the secret key information assigned by the server to each client, and obtains the encryption parameters of the camera to be docked. Then, the client generates a first signature parameter for the encryption parameters and the application ID using the hmac_sha256 algorithm according to the secret key information. The client generates a docking request based on the first signature parameter. The server receives the docking request, parses the docking request, obtains the encryption parameters and application ID of the camera to be docked, and determines the unique secret key information sent by the server to the client according to the application ID. The server performs hmac_sha256 signature calculation on the encryption parameters and the application ID according to the secret key information to generate a second signature parameter.

[0059] In this embodiment, the registration request is parsed and the parsing result is used to generate a second signature parameter on the server side, thereby improving the accuracy of the verification between the client and the server.

[0060] In one embodiment, if Figure 4As shown, step 203 matches the first signature parameter with the second signature parameter. If they are the same, the target node of the camera to be mounted is obtained, and the camera to be mounted is mounted under the target node, which specifically includes the following steps 401 to 402.

[0061] Step 401: decrypt the encrypted parameters of the camera to be attached according to the secret key information, and extract the camera parameters of the camera to be attached and the user selection node.

[0062] Step 402, determining whether there is a binding relationship between the camera parameters and the user information of the client, and if so, taking the user selected node as the target node of the camera to be attached.

[0063] Specifically, the server uses the XXTEA algorithm to decrypt the encrypted information of the camera to be attached according to the secret key information, extracts the camera parameters and user selection node of the camera to be attached, and determines whether there is a binding relationship between the camera parameters and the user information on the client. If so, the user selection node is used as the target node for camera attachment. If not, the result of attachment failure is returned to the client.

[0064] In this embodiment, by further decryption, the binding relationship between the camera to be mounted and the user information is judged, so as to determine whether the node selected by the user can be used as the target node of the camera to be mounted, thereby achieving safe mounting of the camera and improving the accuracy of camera mounting.

[0065] In one embodiment, step 203 docks the camera to be docked under the target node, and also includes: determining whether the target node belongs to the pre-allocated docking area of ​​the camera to be docked, and if so, docking the camera to be docked under the target node.

[0066] In detail, the server pre-allocates a docking area for each user, and determines whether the target node of the camera to be docked belongs to the docking area of ​​the client user. If so, the camera to be docked is docked under the target node.

[0067] In one embodiment, Figure 5 As shown, before step 201 receives the docking request of the camera to be docked sent by the client, the method also includes the following steps 501 to 502.

[0068] Step 501: construct an administrative region tree diagram according to the hierarchical coding rule, wherein the administrative region tree diagram includes region nodes and region codes of the region nodes.

[0069] Step 502, obtaining the user information of the client, and pre-allocating the camera docking area for each of the clients from the administrative area tree diagram according to the user information.

[0070] Specifically, an administrative region tree diagram is constructed on the server side according to the hierarchical coding rules, wherein the administrative region tree diagram includes region nodes and region codes of the region nodes, wherein Figure 6 As shown, the regional node includes a root node and a child node. The regional code of the root node is composed of "province code_industry code-self-incrementing serial number", and the regional code of the child node is composed of "parent region code-self-incrementing serial number". The user logs in and registers the user information on the client, and the administrator pre-assigns the camera's docking area for the user from the administrative area tree diagram and stores it on the server. The server initializes the pre-assigned docking area as a business cascade code and returns it to the client. The user can select the docking regional node by scanning the business cascade code.

[0071] In one embodiment, Figure 7 As shown, a camera calling method is provided, and the method includes the following steps 701 to 702.

[0072] Step 701: Receive a call request sent by a client.

[0073] Step 702, according to the call request, returning the pre-allocated docking area of ​​the client; the client selects a target camera from the docking area for display, and the target camera includes the camera docked by the client and / or the cameras docked by other clients.

[0074] Specifically, when the client's camera is docked, the server receives the call request sent by the client and returns the pre-allocated docking area corresponding to the client. The user can select the target camera from the docking area for display, and the target camera includes the camera docked by the client and / or the cameras docked by other clients. When the target camera that the client needs to display is not in the pre-allocated docking area, the client can submit the area code of the target camera docking area node to the server. The server obtains the corresponding shared camera according to the area code and displays it to the user, so that the user can use the relevant functions of the camera. The client can also scan the service cascade code to select the target camera under the area node.

[0075] In a preferred embodiment, a camera mounting is provided, which specifically includes the following contents:

[0076] S1, construct an administrative region tree diagram according to the hierarchical coding rules on the server side.

[0077] S2, the user logs in and registers the user information on the client, and the administrator pre-assigns the camera's docking area for the user from the administrative area tree diagram and stores it on the server. The server initializes the pre-assigned docking area as a service cascade code and returns it to the client.

[0078] S3, the user selects the node to be attached to the camera by scanning the service cascade code, and encrypts the camera parameters and the user-selected node using the XXTEA algorithm according to the secret key information assigned by the server to each client, and obtains the encrypted parameters of the camera to be attached. The client generates the first signature parameter for the encrypted parameters and the application ID using the hmac_sha256 algorithm according to the secret key information. The client generates an attachment request based on the first signature parameter.

[0079] S4, the server receives the docking request, parses the docking request, and obtains the first signature parameter, encryption parameter and application ID of the camera to be docked.

[0080] S5, the server determines the secret key information sent by the server to the client according to the application ID, and performs hmac_sha256 signature calculation on the encryption parameter and the application ID according to the secret key information to generate a second signature parameter. At the same time, the encryption parameters of the camera to be attached are decrypted according to the secret key information, and the camera parameters and the user selection node of the camera to be attached are extracted. It is determined whether there is a binding relationship between the camera parameters and the user information of the client. If so, the user selection node is used as the target node of the camera to be attached.

[0081] S6, the server matches the first signature parameter of the client with the second signature parameter generated on the server, and if the two are the same, obtains the target node of the camera to be docked from the server, and determines whether the target node belongs to the pre-allocated docking area of ​​the camera to be docked, and if so, docks the camera to be docked to the target node.

[0082] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0083] Based on the same inventive concept, the embodiment of the present application also provides a camera mounting system for implementing the camera mounting method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more camera mounting system embodiments provided below can refer to the limitations on the camera mounting method above, and will not be repeated here.

[0084] In an exemplary embodiment, Figure 8 As shown, a camera mounting system is provided, comprising:

[0085] The receiving module 801 is used to receive a docking request for a camera to be docked sent by a client, where the docking request includes a first signature parameter generated by the client.

[0086] The parsing module 802 is used to parse the docking request to obtain a parsing result, and generate a second signature parameter of the camera to be docked according to the parsing result.

[0087] The mounting module 803 is used to match the first signature parameter with the second signature parameter. If they are the same, the target node of the camera to be mounted is obtained, and the camera to be mounted is mounted under the target node.

[0088] In one of the embodiments, the parsing module 802 is also used to: parse the docking request to obtain the encryption parameters and application ID of the camera to be docked; determine the key information of the camera to be docked based on the application ID; and perform signature calculation on the encryption parameters and the application ID based on the key information to generate a second signature parameter.

[0089] In one of the embodiments, the docking module 803 is also used to: decrypt the encrypted parameters of the camera to be docked according to the secret key information, extract the camera parameters and the user selection node of the camera to be docked; determine whether there is a binding relationship between the camera parameters and the user information of the client, and if so, use the user selection node as the target node of the camera to be docked.

[0090] In one of the embodiments, the docking module 803 is further used to: determine whether the target node belongs to the pre-allocated docking area of ​​the camera to be docked, and if so, dock the camera to be docked to the target node.

[0091] In one embodiment, the system further includes a tree diagram construction module, which is used to: construct an administrative region tree diagram according to the hierarchical coding rules, the administrative region tree diagram includes region nodes and region codes of the region nodes; obtain user information of the client, and pre-allocate the camera docking area for each client from the administrative region tree diagram according to the user information. The region node includes a root node and a child node, the region code of the root node consists of a province code, an industry code and a self-incrementing serial number, and the region code of the child node consists of a parent region code and a self-incrementing serial number.

[0092] Each module in the camera docking system can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0093] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig. 9 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. Among them, the processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a camera mounting method is implemented.

[0094] Those skilled in the art will understand that Fig. 9 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0095] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, steps corresponding to the camera mounting method described in the above embodiments are implemented.

[0096] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps corresponding to the camera mounting method described in the above embodiments are implemented.

[0097] In one embodiment, a computer program product is provided, including a computer program, which, when executed by a processor, implements the steps corresponding to the camera mounting method described in the above embodiments.

[0098] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0099] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0100] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A camera mounting method, characterized in that: The method comprises: Receiving a docking request for a camera to be docked sent by a client, wherein the docking request includes a first signature parameter generated by the client; Parsing the attachment request to obtain a parsing result, and generating a second signature parameter of the camera to be attached according to the parsing result; The first signature parameter is matched with the second signature parameter. If they are the same, the target node of the camera to be mounted is obtained, and the camera to be mounted is mounted under the target node; The first signature parameter is matched with the second signature parameter, and if they are the same, a target node of the camera to be mounted is obtained, and the camera to be mounted is mounted under the target node, comprising: Decrypt the encrypted parameters of the camera to be attached according to the secret key information, and extract the camera parameters of the camera to be attached and the user selection node; Determine whether there is a binding relationship between the camera parameters and the user information of the client, and if so, use the user selected node as the target node of the camera to be attached; Determine whether the target node belongs to the pre-allocated docking area of ​​the camera to be docked. If so, dock the camera to be docked under the target node.

2. The camera mounting method according to claim 1, characterized in that: The parsing of the docking request to obtain a parsing result, and generating a second signature parameter of the camera to be docked according to the parsing result comprises: Parsing the docking request to obtain the encryption parameters and application ID of the camera to be docked; Determine the key information of the camera to be attached according to the application ID; According to the secret key information, a signature calculation is performed on the encryption parameter and the application ID to generate a second signature parameter.

3. The camera mounting method according to claim 1, characterized in that: Before receiving the docking request of the camera to be docked sent by the client, the method further includes: According to the hierarchical coding rules, an administrative region tree diagram is constructed, wherein the administrative region tree diagram includes region nodes and region codes of the region nodes; The user information of the client is obtained, and based on the user information, a camera docking area is pre-allocated for each of the clients from the administrative area tree diagram.

4. The camera mounting method according to claim 3, characterized in that: The regional node includes a root node and a child node. The regional code of the root node is composed of a province code, an industry code and a self-incrementing serial number, and the regional code of the child node is composed of a parent regional code and a self-incrementing serial number.

5. A camera calling method, characterized in that: The method comprises: After the camera is mounted according to the method described in any one of claims 1 to 4, a call request sent by the client is received; According to the calling request, the pre-allocated docking area of ​​the client is returned; the client selects a target camera from the docking area for display, and the target camera includes the camera docked by the client and / or the cameras docked by other clients.

6. A camera mounting system, characterized in that: The system comprises: A receiving module, used for receiving a docking request for a camera to be docked sent by a client, wherein the docking request includes a first signature parameter generated by the client; A parsing module, used for parsing the docking request to obtain a parsing result, and generating a second signature parameter of the camera to be docked according to the parsing result; A mounting module, used for matching the first signature parameter with the second signature parameter, and if they are the same, obtaining a target node of the camera to be mounted, and mounting the camera to be mounted under the target node; The first signature parameter is matched with the second signature parameter, and if they are the same, a target node of the camera to be mounted is obtained, and the camera to be mounted is mounted under the target node, comprising: Decrypt the encrypted parameters of the camera to be attached according to the secret key information, and extract the camera parameters of the camera to be attached and the user selection node; Determine whether there is a binding relationship between the camera parameters and the user information of the client, and if so, use the user selected node as the target node of the camera to be attached; Determine whether the target node belongs to the pre-allocated docking area of ​​the camera to be docked. If so, dock the camera to be docked under the target node.

7. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 4 are implemented.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 4 are implemented.

Images