CN109905645B - Video monitoring equipment directory exchange method and networking platform - Google Patents
Video monitoring equipment directory exchange method and networking platform Download PDFInfo
- Publication number
- CN109905645B CN109905645B CN201711295364.7A CN201711295364A CN109905645B CN 109905645 B CN109905645 B CN 109905645B CN 201711295364 A CN201711295364 A CN 201711295364A CN 109905645 B CN109905645 B CN 109905645B
- Authority
- CN
- China
- Prior art keywords
- networking platform
- platform
- directory
- networking
- device directory
- 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
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N7/00—Television systems
- H04N7/18—Closed-circuit television [CCTV] systems, i.e. systems in which the video signal is not broadcast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- 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/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The embodiment of the invention provides a method and a device for exchanging directories of video monitoring equipment, wherein the method comprises the following steps: the first networking platform marks that the second networking platform is allowed to send response messages in parallel in the request message for acquiring the equipment directory; and after receiving the request message indicating that the parallel transmission of the response message is allowed, the second networking platform transmits the response message containing the equipment directory in a parallel mode. The method provided by the embodiment of the invention adopts a parallel mode to exchange the information of the monitoring equipment, is compatible with the existing standard, can obviously improve the exchange efficiency, saves the time for exchanging the equipment catalog among the networking platforms and improves the real-time property of the shared information of the whole monitoring system.
Description
Technical Field
The invention relates to the field of video monitoring, in particular to a method and a device for exchanging directories of video monitoring equipment.
Background
The safe city video monitoring plays more and more important roles in social management, national security and social stability maintenance, and prevention and attack of terrorist crimes, and therefore safe city video monitoring platforms are established successively in many places. However, as the construction of the safe city goes deep, the video monitoring platforms of the various places in the construction of the safe city are mutually independent, so that interconnection and intercommunication cannot be realized, and respective devices can be shared. Therefore, the national related departments send out documents and require the construction of a video monitoring networking application system with global coverage, whole network sharing, full time availability and whole process controllability, thereby opening the sequence of constructing a large networking of nationwide safe cities.
The large networking construction emphasizes the unified planning of one network in China, and networking and resource sharing are the most important guiding principles and targets for construction. Before this, a series of safe city monitoring platforms have been built all over the country, and the large network firstly connects these platforms into a four-level unified monitoring network system of country, province, city and county.
The national standard GB/T28281 plus 2011 'technical requirements for information transmission, exchange and control of a public safety video monitoring system' is a really unique heterogeneous platform interconnection standard, but the standard is customized without the background and the requirement of large networking, firstly, the interconnection problem of heterogeneous platforms is solved, and when the standard is applied to the scene of large networking in the whole country, some problems are proved to exist.
The GB/T28281 standard has two ways to exchange device directories between networked platforms. One is that the networking platform initiatively initiates a device directory query request to another platform, and the requested networking platform then returns all the video monitoring device directories shared by the requested networking platform to the requested networking platform; the other is that the networking platform initiates the subscription of the device catalog to the other platform, and the subscribed networking platform informs the subscribing networking platform when the shared device changes.
In the prior art, when device directories are exchanged between networking platforms, no matter whether an active device directory query request is adopted or a directory subscription is initiated and a device directory notification of the other party is waited, response messages are sent in series, that is, after one message is successfully sent, the next message is sent again. However, the number of entries of the directory information of the video device which can be recorded in each message is limited, and when hundreds of thousands or even millions of messages exist on some platforms, the efficiency of serially sending the messages is very low, and a long time is needed for successfully sending the complete device directory once.
Disclosure of Invention
The embodiment of the invention provides a method for exchanging a video monitoring equipment directory, wherein the networking platforms exchange the video monitoring equipment directory messages in parallel, so that the exchange efficiency can be improved, the exchange time can be saved, and the method is favorable for keeping the synchronization of the video monitoring equipment directory among the equipment.
In order to achieve the above purpose, the embodiments of the present invention provide the following technical solutions:
in a first aspect, a method for exchanging directories of video surveillance equipment is provided, where the method includes: the second networking platform receives a first equipment directory request message sent by the first networking platform, wherein the first equipment directory request message contains an identifier allowing the second networking platform to send a response message in parallel; the second networked platform then sends a plurality of response messages containing the device directory to the first networked platform in a parallel manner.
The parallel transmission means that the second networking platform continuously transmits the response message containing the device directory when transmitting the response message, and does not need to wait for the next response message to be transmitted after receiving a reply message of the response message.
In one possible design, the plurality of response messages include response message sequence numbers.
In one possible design, if the response message including all the device directories is sent completely, the second networking platform sends a response message indicating that the device directories are sent completely to the first networking platform.
In one possible design, the second networking platform receives a second device directory request message sent by the first networking platform, the second device directory request message includes a response message sequence number, and the second networking platform sends a response message corresponding to the response message sequence number to the first networking platform.
In one possible design, the second networking platform receives a third device directory request message sent by the first networking platform, where the third device directory request message includes an identification of the requested incremental device directory, and the second networking platform sends a response message including the incremental device directory to the first networking platform. By indicating that only the incremental device directory is allowed to be sent in the device directory request message, the situation that the shared device directory is returned to all the shared device directories by the requesting platform even if the shared device directory is not changed after the last request every time the device directory is requested is avoided, repeated exchange of the device directories is avoided, and the time for exchanging the device directories is reduced.
The incremental device directory refers to a device directory which changes when the device directory is requested by the first networking platform last time in the device directory of the second networking platform, and the incremental device directory comprises a new device directory, a deleted device directory and a device directory with changed parameters.
In one possible design, the second networking platform receives a fourth device directory request message sent by the first networking platform, the fourth device directory request message includes a request direct device directory identifier and a target networking platform ID, the second networking platform acquires the direct device directory of the target networking platform according to the target networking platform ID, and sends a response message containing the direct device directory of the target networking platform to the first networking platform. By marking the direct device directory allowing only the return of the target networking platform in the device directory request message, the situation that a series of cascaded message requests and transmissions between the networking platforms possibly occur due to one device directory request message in the prior art, the response speed of the whole system is slowed down, and more targeted device directory exchange is performed between the platforms is avoided.
In one possible design, the method for the second networking platform to obtain the direct device directory of the target networking platform includes: if the ID of the target networking platform is the ID of the second networking platform, the second networking platform acquires a directly-owned device directory stored locally; and if the ID of the target networking platform is the ID of the subordinate networking platform of the second networking platform, the second networking platform sends a request message to the subordinate networking platform to acquire the direct equipment directory of the subordinate networking platform.
In a second aspect, an embodiment of the present invention provides a networking platform having a function of implementing the first networking platform or the second networking platform in the above method embodiments. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above. The networking platform includes: the receiving module is used for receiving a first equipment directory request message sent by a first networking platform, wherein the first equipment directory request message contains an identifier allowing the networking platform to send a response message in parallel; a sending module for sending a plurality of response messages containing the device directory to the first networked platform in a parallel manner.
In a third aspect, an embodiment of the present invention provides a networking platform, including: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer execution instructions, the processor is connected with the memory through the bus, and when the device runs, the processor executes the computer execution instructions stored in the memory, so that the networking implementation platform executes the video monitoring device directory exchange method according to any one of the above first aspects.
In a fourth aspect, an embodiment of the present invention provides a computer storage medium for storing computer software instructions for the above-mentioned networked platform, which includes a program for executing the above-mentioned aspect designed for the networked platform.
In a fifth aspect, an embodiment of the present invention provides a computer program product. The computer program product comprises computer software instructions that can be loaded by a processor to implement the process in the video surveillance appliance directory exchange method of any one of the first aspect.
Through the aspects, the embodiment of the invention can realize parallel exchange of the equipment catalogs among the networking platforms, and can select only to exchange the incremental equipment catalogs or the equipment catalogs directly belonging to the target networking platform, thereby improving the exchange efficiency, saving the time and avoiding the risk of exchanging repeated equipment catalogs and message broadcasting in the whole system.
These and other aspects of the invention are apparent from and will be elucidated with reference to the embodiments described hereinafter.
Drawings
FIG. 1 is a schematic diagram of a network architecture of a possible video surveillance large network according to an embodiment of the present invention;
FIG. 2 is a flow chart of a device directory exchange method between networking platforms;
FIG. 3 is a schematic flow chart of another way of exchanging device directories between networked platforms;
fig. 4 is a flowchart illustrating a method for exchanging device directories between networking platforms according to an embodiment of the present invention;
FIG. 5 is a flowchart illustrating another method for exchanging device directories between networking platforms according to an embodiment of the present invention;
FIG. 6 is a flowchart illustrating another method for exchanging device directories between networking platforms according to an embodiment of the present invention;
fig. 7 is a schematic structural diagram of a networking platform according to an embodiment of the present invention;
FIG. 8 is a schematic diagram of a computer apparatus provided by an embodiment of the present invention;
Detailed Description
The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention. The specific methods of operation in the method embodiments may also be applied in the apparatus embodiments.
The architecture and the service scenario described in the embodiment of the present invention are for more clearly illustrating the technical solution of the embodiment of the present invention, and do not form a limitation on the technical solution provided in the embodiment of the present invention, and it can be known by those skilled in the art that the technical solution provided in the embodiment of the present invention is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.
Fig. 1 is a schematic diagram of a network architecture of a possible video surveillance large network according to an embodiment of the present invention. The networking platform in the network architecture is divided into four stages: at a state level, a provincial level, a city level and a district level, a plurality of networking platforms may be arranged in each level of networking platform under certain situations, and equipment directories can be exchanged among the plurality of networking platforms.
The networking platform is used for storing the equipment catalog of the monitoring equipment and the monitoring content acquired by the monitoring equipment, controlling the monitoring equipment, retrieving and managing the monitoring content, or transmitting the monitoring content according to a request. The device directory includes information such as the numbers, attributes, and parameters of various devices connected to the networking platform. In practice, the device directory may also be other names, such as: device list, device manifest, device information, etc. In the network architecture of the video monitoring large networking shown in fig. 1, networking platforms at different levels are connected together through an Internet Protocol (IP) network, and perform monitoring service access and call with each other. The name networking platform does not in itself constitute a limitation on the device, and in practice, other names are possible, such as: the system comprises a video monitoring networking platform system, a video monitoring networking platform, a central server, a node server or a management server and the like.
According to the GB/T28281 standard, communication between networking platforms follows the SIP (Session initiation Protocol), which is an application layer communication Protocol defined by RFC 3261.
The device directory exchange method provided by the embodiment of the present invention may be applied to a network architecture as shown in fig. 1, and may be applied to exchange device directories between any two networking platforms, for example, between the C city and the D city at the same level, between the C city and the G district at different levels, and between the D city and the E city at different provinces, where device directory exchange is performed between the C city networking platform 110 and the D city networking platform 120, which is used as an example to describe the technical solution provided by the embodiment of the present invention, where the C city networking platform 110 is a request party of the device directory, and the D city networking platform 120 is a sender of the device directory.
For convenience of description, in the present specification, the networking platform that sends the request for obtaining the device directory is referred to as a "first networking platform", the networking platform that sends the device directory is referred to as a "second networking platform", and the "first networking platform" and the "second networking platform" merely represent one logical structure, and the "first" and the "second" herein do not constitute a limitation on the networking platform. Thus, C is the first networking platform 110 and D is the second networking platform 120.
In the GB/T28281 standard, video monitoring equipment catalogs can be exchanged between networking platforms in two ways.
One is that the first networked platform 110 actively initiates a device directory query request to the second networked platform 120, and the second networked platform 120 then returns the full amount of device directories shared to the requesting networked platform 110, as shown in fig. 2. The mode shown in fig. 2 is divided into four steps: 210. the first networking platform 110 sends a device directory query request to the second networking platform 120 through a Message format; 220. the second networked platform 120 sends a 200OK message or other SIP response message to the first networked platform 110 in reply, completing a request dialog; 230. the second networking platform 120 sends a device directory query response to the first networking platform 110 through a Message format, and the Message contains the content of the response to the request in step 210, that is, the device directory requested by the first networking platform 110; 240. the first networked platform 110 sends a Message 200OK or other SIP Message in reply to the second networked platform 120 indicating that a Message sent by the second networked platform 120 has been received, completing a response dialog. Depending on the size of the reply content that the second networked platform 120 needs to send to the first networked platform 110, the second networked platform 120 may send the reply content in multiple response messages for a request sent by the first networked platform 110, i.e., steps 230 and 240 may be repeated multiple times.
As shown in fig. 3, another way is for the first networked platform 110 to initiate a subscription (Subscribe) request for a device directory to the second networked platform 120, and the second networked platform 120 sends a new device directory to the first networked platform 110 when the shared device directory changes. The mode shown in fig. 3 is divided into four steps: 310. the first networking platform 110 sends a device directory subscription request to the second networking platform 120 through a Subscribe message format; 320. the second networked platform 120 sends a 200OK message or other SIP response message to the first networked platform 110 in reply, completing a subscription dialog; 330. when the device directory shared by the second networking platform 120 changes, the second networking platform 120 sends a notification for the device directory subscription request to the first networking platform 110 through a Notify message format, where the Notify message contains the device directory subscribed by the first networking platform 110; 340. the first networked platform 110 sends a message 200OK or other SIP message in reply to the second networked platform 120 indicating that a Notify message sent by the networked platform 120 has been received, completing a notification dialog. Depending on the size of the content that the second networked platform 120 needs to send to the first networked platform 110, for a subscription request sent by the first networked platform 110, the second networked platform 120 may send the reply content via multiple notification (Notify) messages, i.e., steps 330 and 340 may be repeated multiple times.
The Message, Subscribe, Notify, and 200OK in fig. 2 and 3 are Message formats in the SIP protocol.
In the above two switching manners, when the networking platform that sends the device directory needs to send the shared device directory through a plurality of messages, after sending one Message or Notify Message, it needs to wait until receiving the reply Message sent by the receiving party before sending the next Message or Notify Message, and when it needs to send a large number of Message messages or Notify messages, the two switching manners will consume a large amount of time on waiting for the reply Message of the receiving party, so that the efficiency of the whole device directory switching process is low and the duration is long.
The embodiment of the invention provides an equipment directory exchange method, which adopts a parallel sending mode to send an equipment directory and solves the problems that in the prior art, a sender needs to sequentially confirm whether a response message containing the equipment directory is received, so that time is wasted and the equipment directory exchange efficiency is low.
First, the first networking platform 110 sends a first device directory request message indicating that the second networking platform 120 is allowed to send response messages in parallel to the second networking platform 120; next, the second networking platform 120 receives the first device directory request message and then sends a plurality of response messages containing the device directory to the first networking platform 110 in a parallel manner.
The request Message may be in a Message format for actively initiating a device directory query request or a Subscribe Message format for initiating a device directory subscription request, and the response Message may be in a Message format or a Notify Message format, which is not limited in the present application.
The parallel transmission means, specifically, the second networked platform 120 continuously transmits the response messages to the first networked platform 110 without waiting for the reply message of one response message to transmit the next response message.
Fig. 4 is a schematic flow chart of an apparatus directory exchange method according to an embodiment of the present invention. The method can be applied to the network architecture of the video monitoring large networking in fig. 1, which takes the SIP protocol as the communication protocol of the application layer between networking platforms.
In step 410, the first networked platform 110 sends a first device directory request message to the second networked platform 120, the first device directory request message indicating that the second networked platform 120 is allowed to send response messages in parallel.
Specifically, as an implementation manner, taking the directory query request message as an example, the request message format modified on the basis of the request message format in the existing GB/T28281 standard is as follows:
in the embodiment of the present invention, the newly added "QueryParameter" and "enablepallelresponse" parameters may be used to indicate whether the first networking platform 110 allows the second networking platform 120 to send the response message in parallel, and when the "enablepallelresponse" parameter is "True", it represents that the second networking platform 120 is allowed to send the response message in parallel. The "QueryParameter" and "enableparalresponse" are merely examples of names of parameters provided by the embodiment of the present invention, and do not limit the parameters.
In step 420, the second networking platform 120 receives the first device directory request message sent by the first networking platform 110 and sends a 200OK message or other SIP response message as a reply message.
In step 430, the second networked platform 120 sends multiple response messages containing the device directory to the first networked platform 110 in a parallel manner.
Specifically, as an implementation manner, the format of the response message is as follows:
the newly added data item < respSN > in the embodiment of the present invention is used to indicate the sequence number of the response message for the same request, the second networking platform 120 sends the response message with the number of </respSN > 1, 2, and 3 … …, where the number is the sequence number of the response message, and the number of the device directories that need to be sent in total for one request is indicated by < SumNum > in the response message. "respSN" is merely an example of a parameter name provided by the embodiment of the present invention, and does not limit the parameter. Sn1 and deviceId are consistent with the request message for the first networking platform 110 to match the response message. Num1 corresponding to the Num parameter indicates the number of device directory entries contained in the present response message. < Item > … </Item > is a device directory Item type "itemType" defined in the GB/T28281 standard.
Optionally, the second networked platform 120 may retransmit the response via a retransmission mechanism of the SIP protocol to ensure that the first networked platform 110 can receive the response message, as the case may be.
Optionally, if the response message including the device directory is sent completely, the second networking platform 120 sends a response message indicating that the device directory is sent completely to the first networking platform 110. As one implementation, the message format may be as follows:
wherein the value of < respSN > is set to-1, indicating that the response message to the request message with sequence number sn1 has been sent.
Optionally, a < lastespsn > parameter may be added, indicating the maximum response message sequence number for a request message with sequence number sn 1. "lastRespSN" is merely an example of a parameter name provided by an embodiment of the present invention, and does not limit the parameter.
If the device directory request message sent by the first networking platform 110 does not indicate that the parallel sending of the response message is allowed, the second networking platform 120 sends a message containing the device directory in a manner specified by the GB/T28281 standard.
In step 440, the first networking platform 110 sends a reply message to the second networking platform 120 after receiving the response message sent by the second networking platform 120.
The first networked platform 110 receives the response messages sent in parallel and replies with a 200OK or other message in reply to each received response message. The first networked platform 110 may not necessarily receive the response messages sent by the second networked platform 120 in sequence due to changes in network conditions and changes in the routing path of the response messages.
Optionally, the first networking platform 110 determines whether a complete device directory is received, and if the sequence numbers of the received response messages are complete and continuous, and a response message indicating that the response messages are completely sent is received, and the sum of the device directory entries in all the received response messages is equal to the total number of the device directory entries, the first networking platform 110 receives the complete device directory.
If the device directory received by the first networking platform 110 is not complete, all the received response messages may be discarded, and then the request message may be retransmitted, or a second device directory request message for acquiring the missing response message may be sent to the second networking platform 120, where the second device directory request message includes a response message sequence number corresponding to the missing response message. Missing response messages may be obtained by querying the response message sequence number of the received response message.
As one implementation, the format of the request message is as follows:
where "respSN" is the response message sequence number of the response message that is missing and needs to be resent.
When receiving the second device directory request message, the second networking platform 120 sends a response message corresponding to the response message sequence number in the second device directory request message to the first networking platform 110.
The embodiment of the present invention further provides another device directory exchange method, which may be applied to the network architecture shown in fig. 1. In this embodiment, the first networking platform 110 and the second networking platform 120 only exchange incremental device directories after the last device directory exchange, which avoids repeatedly exchanging the same device directory entries and saves a lot of time and resources. The incremental device directory refers to a device directory of the second networked platform 120 that has changed relative to the last time the first networked platform 110 requested the device directory. The incremental device directories include an added device directory, a deleted device directory, and a parameter changed device directory. This will be described in detail with reference to fig. 5.
In this embodiment, 510, the first networked platform 110 sends a third device directory request message to the second networked platform 120, the third device directory request message indicating that the second networked platform 120 is requested to return an incremental device directory. As one implementation, the format of the request message may be as follows:
in the embodiment of the present invention, a < enablementalmode > parameter is newly added to the query parameter < QueryParameter > to indicate whether the first networking platform 110 allows receiving the incremental device directory, and when the < enablementalmode > parameter is "True", it indicates that the first networking platform 110 allows receiving the incremental device directory, and the first networking platform 110 requests the second networking platform 120 to return the incremental device directory. The "enableconmentalmode" is merely an example of a parameter name provided by the embodiment of the present invention, and does not limit the parameter. Optionally, the third device directory request message may also indicate that parallel sending of the response message is allowed, in which case, the second networking platform 120 sends the incremental device directory in a parallel manner; alternatively, the indication of permission to send the response message in parallel may be omitted, in which case the second networked platform 120 sends the incremental device directory serially.
The second networking platform 120 receives 520 the third device directory request message sent by the first networking platform 110 and returns a 200OK message or other SIP response message as a reply message.
At 530, the second networked platform 120 sends a response message containing the incremental device directory to the first networked platform 110. The second networking platform 120 stores the total information of the device directory and the sending time which are sent to the first networking platform 110 last time, and when the request message sent by the first networking platform 110 is received, the currently stored device directory is compared with the stored total information of the device directory which is sent last time, so that the incremental device directory can be obtained. As one implementation, the format of the response message sent by the second networking platform 120 may be as follows:
in the embodiment of the present invention, three lists "AddedDeviceList", "DeletedDeviceList", and "modifiedddevicelist" are added to the response message, where "AddedDeviceList" indicates a device directory added after the device directory was sent last time, "DeletedDeviceList" indicates a device directory deleted after the device directory was sent last time, and "modifiedddevicelist" indicates a device directory modified after the device directory was sent last time. "AddedDeviceList", "DeletedDeviceList", and "modifiedddevicelist" are merely examples of names of parameters provided by embodiments of the present invention, and do not limit the parameters.
Optionally, after receiving the third device directory request, the second networking platform 120 may determine whether the first networking platform 110 has requested the device directory, and if the first networking platform 110 has never requested the device directory, the second networking platform 120 sends all the device directories to the first networking platform 110; if the first networked platform 110 has requested the device directory from the second networked platform 120, the second networked platform 120 sends the incremental device directory to the first networked platform.
As one possible implementation, if the incremental device directory is not available to the second networked platform 120, the second networked platform 120 sends a response message to the first networked platform 110 indicating that the incremental device directory is not available. The situation that the incremental device directory cannot be obtained includes that the second networking platform 120 cannot obtain the incremental device directory after the device directory is last sent to the first networking platform 110, or that a time interval during which the first networking platform 110 last requests the device directory from the second networking platform 120 exceeds a threshold. As one implementation, the format of the response message indicating that the delta device directory is unavailable may be as follows:
the value of < SumNum > is set to-1, indicating that the delta device directory cannot be obtained. After receiving the response message that the incremental device directory cannot be obtained, the first networking platform 110 may resend the request message that does not indicate permission to receive the incremental device directory, and after receiving the request message, the second networking platform 120 sends the full device directory to the first networking platform 110.
After sending the incremental device directory, the second networked platform 120 updates the saved device directory inventory information sent to the first networked platform 110.
The embodiment of the present invention further provides another device directory exchange method, which may be applied to the network architecture shown in fig. 1. In this embodiment, the first networking platform 110 may send the request message indicating that the second networking platform 120 is limited to send only the device directory to which the target networking platform directly belongs, so as to avoid that a series of request messages and response messages are sent due to a request of a higher-level networking platform, and thus the response speed of the entire system is slowed down. The device directory of the direct family refers to a device directory directly connected to the current-level networking platform, rather than a device directory shared by the subordinate networking platforms. This will be described in detail with reference to fig. 6.
In this embodiment, 610, the first networking platform 110 sends a fourth device directory request message to the second networking platform 120, where the direct device directory requesting the target networking platform and the target networking platform ID are indicated in the fourth device directory request message. As one implementation, the format of the request message may be as follows:
in the embodiment of the present invention, a < QueryDirectList > parameter is newly added to the query parameter < querydirameter > to indicate that the first networking platform 110 requires the second networking platform 120 to send only the directordirectory of the target networking platform, and when the < QueryDirectList > parameter is True, the first networking platform 110 indicates that the second networking platform 120 requires the second networking platform 120 to return only the directordirectory of the target networking platform. The "QueryDirectList" is merely an example of a parameter name provided by the embodiment of the present invention, and does not limit the parameter.
620, the second networking platform 120 receives the fourth device directory request message sent by the first networking platform 110 and returns a 200OK message or other SIP response message as a reply message.
630, the second networking platform 120 obtains the direct device directory of the target networking platform according to the ID of the target networking platform, and sends a response message containing the direct device directory of the target networking platform to the first networking platform.
If the ID of the target networking platform is the ID of the second networking platform 120, the locally stored device directory is acquired, and a response message containing the device directory to which the second networking platform 120 directly belongs is sent to the first networking platform 110.
If the ID of the target networking platform is the ID of the subordinate networking platform of the second networking platform 120, the second networking platform 120 sends a request message to the subordinate networking platform to obtain the directly subordinate device directory of the subordinate networking platform, and then sends a response message containing the directly subordinate device directory of the subordinate networking platform to the first networking platform 110. Alternatively, if the second networking platform 120 locally stores the device directory of the subordinate networking platform, the second networking platform 120 directly sends the response message containing the device directory of the subordinate networking platform to the first networking platform 110 without additionally acquiring the direct device directory from the subordinate networking platform.
If the ID of the target networking platform is not the ID of the second networking platform 120 or the ID of the subordinate networking platform of the second networking platform 120, the second networking platform 120 sends a response message indicating that the ID of the target networking platform in the request message is wrong to the first networking platform 110.
The above embodiments mainly introduce the solutions provided by the embodiments of the present invention from the perspective of interaction between networked platforms. It is understood that in order to implement the above-described functions, the networked platform includes corresponding hardware structures and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software depending upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.
In the embodiment of the present invention, the networking platform may be divided into the functional modules according to the method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, the division of the modules in the embodiment of the present invention is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
Fig. 7 shows a possible structural diagram of the networking platform in the above embodiment, in the case of dividing the functional modules by corresponding functions. The networking platform includes: a sending module 710, a receiving module 720, a processing module 730, and a storage module 740.
A sending module 710, configured to send a response message;
a receiving module 720, configured to receive a first device directory request message sent by a first networking platform, where the first device directory request message includes an identifier that allows the networking platform to send a response message in parallel;
a processing module 730 for controlling the sending module to send a plurality of response messages containing the device directory to the first networking platform in a parallel manner;
the storage module 740 is used for storing the device directory list.
In one possible implementation, the processing module 730 assigns a sequence number to the plurality of response messages.
In another possible implementation manner, the receiving module 720 is further configured to receive a second device directory request message sent by the first networking platform, where the second device directory request message includes a response message sequence number, and accordingly, the processing module 730 controls the sending module 710 to send a response message corresponding to the response message sequence number to the first networking platform.
In another possible implementation manner, the receiving module 720 is further configured to receive a third device directory request message sent by the first networking platform, where the third device directory request message includes an identifier of a requested incremental device directory, and the processing module 730 controls the sending module 710 to send a response message including the incremental device directory to the first networking platform.
In another possible implementation manner, the receiving module 720 is further configured to receive a fourth device directory request message sent by the first networking platform, where the fourth device directory request message includes a request direct device directory identifier and a target networking platform ID; the processing module 730 obtains the direct device directory of the target networking platform according to the ID of the target networking platform, and controls the sending module 710 to send a response message containing the direct device directory of the target networking platform to the first networking platform.
In the case of integrated units, the networking platform comprises: the device comprises a processing module, a communication module and a storage module. The processing module is used for controlling and managing actions of the networking platforms, such as judging the content of a received request message and controlling the content sent by a response message, the communication module is used for supporting communication among the networking platforms, and the storage module is used for storing program codes and data of the networking platforms.
The Processing module may be a Processor or a controller, and may be, for example, a Central Processing Unit (CPU), a general-purpose Processor, a Digital Signal Processor (DSP), an Application-Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs, and microprocessors, among others. The communication module may be a transceiver, a transceiving circuit or a communication interface, etc. The storage module may be a memory.
When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the networking platform according to the embodiment of the present invention may be the computer device shown in fig. 8.
Fig. 8 is a schematic diagram of a computer device according to an embodiment of the present invention. The computer device 800 comprises at least one processor 81, a communication bus 82, a memory 83 and at least one communication interface 84.
The communication bus 82 may include a path to transfer information between the aforementioned components. The communication interface 84 may be any device, such as a transceiver, for communicating with other devices or communication Networks, such as ethernet, Radio Access Network (RAN), Wireless Local Area Network (WLAN), etc.
The Memory 83 may be, but is not limited to, a Read-Only Memory (ROM) or other type of static storage device that can store static information and instructions, a Random Access Memory (RAM) or other type of dynamic storage device that can store information and instructions, an Electrically Erasable Programmable Read-Only Memory (EEPROM), a Compact Disc Read-Only Memory (CD-ROM) or other optical Disc storage, optical Disc storage (including Compact Disc, laser Disc, optical Disc, digital versatile Disc, blu-ray Disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory may be self-contained and coupled to the processor via a bus. The memory may also be integral to the processor.
The memory 83 is used for storing application program codes for executing the scheme of the invention, and the processor 81 controls the execution. The processor 81 is configured to execute application program codes stored in the memory 83.
In particular implementations, processor 81 may include one or more CPUs such as CPU0 and CPU1 in fig. 8 as an example.
In particular implementations, computer device 800 may include multiple processors, such as processor 81 and processor 88 in FIG. 8, for example, as an embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).
In particular implementations, computer device 800 may also include output device 85 and input device 86 as one embodiment. An output device 85 is in communication with the processor 81 and may display information in a variety of ways. For example, the output device 85 may be a Liquid Crystal Display (LCD), a Light Emitting Diode (LED) display device, a Cathode Ray Tube (CRT) display device, a projector (projector), or the like. The input device 86 is in communication with the processor 81 and can accept user input in a variety of ways. For example, the input device 86 may be a mouse, a keyboard, a touch screen device, or a sensing device, among others.
The computer device 800 may be a general purpose computer device or a special purpose computer device. In a specific implementation, the computer device 800 may be a desktop computer, a laptop computer, a web server, a Personal Digital Assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, a communication device, an embedded device, or a device with a similar structure as in fig. 8. Embodiments of the present invention are not limited by the type of computer device 800.
Embodiments of the present invention also provide a computer storage medium for storing computer software instructions for the networking platform, which includes program code for executing the above aspects designed for the networking platform. By executing the stored program codes, the device directories can be efficiently exchanged between the networking platforms, the exchange time is saved, and the exchange efficiency is improved.
The embodiment of the invention also provides a computer program product. The computer program product comprises computer software instructions which can be loaded by a processor for implementing the method in the above-described method embodiments.
While the invention has been described in connection with various embodiments, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed invention, from a review of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, apparatus (device), 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 that may all generally be referred to herein as a "module" or "system. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein. A computer program stored/distributed on a suitable medium supplied together with or as part of other hardware, may also take other distributed forms, such as via the Internet or other wired or wireless telecommunication systems.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (devices) 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 flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the invention has been described in conjunction with specific features and embodiments thereof, it will be evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the invention. Accordingly, the specification and figures are merely exemplary of the invention as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the invention. It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (16)
1. A method for exchanging directories of video monitoring equipment is characterized by comprising the following steps:
a second networking platform receives a first equipment directory request message sent by a first networking platform, wherein the first equipment directory request message contains an identifier for indicating whether the second networking platform is allowed to send a response message in parallel;
if the identification marks allow the second networking platform to send response messages in parallel, the second networking platform sends a plurality of response messages containing equipment catalogues to the first networking platform in a parallel mode;
and if the identification does not indicate that the second networking platform is allowed to send the response messages in parallel, the second networking platform sends a plurality of response messages containing the equipment catalog to the first networking platform in a serial mode.
2. The method of claim 1, wherein the plurality of response messages include response message sequence numbers.
3. The method of claim 1, wherein if the plurality of response messages are sent, the second networked platform sends a response message to the first networked platform indicating that the device directory has been sent.
4. The method of claim 2, further comprising:
the second networking platform receives a second equipment directory request message sent by the first networking platform, wherein the second equipment directory request message comprises a response message serial number;
and the second networking platform sends a response message corresponding to the response message serial number to the first networking platform.
5. The method of any one of claims 1 to 4, further comprising:
the second networking platform receives a third equipment directory request message sent by the first networking platform, wherein the third equipment directory request message contains a request increment equipment directory identifier;
the second networked platform sends a response message containing an incremental device directory to the first networked platform.
6. The method of any one of claims 1 to 4, further comprising:
the second networking platform receives a fourth equipment directory request message sent by the first networking platform, wherein the fourth equipment directory request message comprises a request direct equipment directory identifier and a target networking platform ID;
and the second networking platform acquires the direct equipment directory of the target networking platform according to the ID of the target networking platform and returns a response message containing the direct equipment directory of the target networking platform to the first networking platform.
7. The method according to claim 6, wherein the second networking platform obtains the direct device directory of the target networking platform according to the target networking platform ID, specifically comprising:
if the target networking platform ID is the ID of the second networking platform, the second networking platform acquires a directly-owned device directory stored locally;
and if the ID of the target networking platform is the ID of the subordinate networking platform of the second networking platform, the second networking platform sends a device directory request message to the subordinate networking platform to acquire the direct device directory of the subordinate networking platform.
8. The method according to any one of claims 1 to 4, wherein the serial mode is a transmission mode specified in the GB/T28281 standard.
9. A networking platform, comprising:
a receiving module, configured to receive a first device directory request message sent by a first networking platform, where the first device directory request message includes an identifier used to indicate whether the networking platform is allowed to send a response message in parallel;
a sending module, configured to send multiple response messages including an equipment directory to the first networking platform in a parallel manner if the identifier indicates that the networking platform is allowed to send the response messages in parallel; and if the identification does not indicate that the second networking platform is allowed to send the response message in parallel, the second networking platform sends a plurality of response messages containing the equipment catalog to the first networking platform in a serial mode.
10. The networking platform of claim 9, wherein the plurality of response messages sent by the sending module include response message sequence numbers.
11. The networking platform of claim 9, wherein if the plurality of response messages including the device directory are sent completely, the sending module sends a response message indicating that the device directory has been sent completely to the first networking platform.
12. The networking platform of claim 10, wherein:
the receiving module is further configured to receive a second device directory request message sent by the first networking platform, where the second device directory request message includes a response message sequence number;
the sending module is further configured to send a response message corresponding to the response message sequence number to the first networking platform.
13. The networked platform of any one of claims 9 to 12, wherein:
the receiving module is further configured to receive a third device directory request message sent by the first networking platform, where the third device directory request message includes a request incremental device directory identifier;
the sending module is further configured to send a response message containing an incremental device directory to the first networking platform.
14. The networked platform of any one of claims 9 to 12, wherein:
the receiving module is further configured to receive a fourth device directory request message sent by the first networking platform, where the fourth device directory request message includes a request direct device directory identifier and a target networking platform ID;
the networking platform further comprises a processing module used for acquiring the direct equipment directory of the target networking platform according to the ID of the target networking platform, and the sending module is further used for sending a response message containing the direct equipment directory of the target networking platform to the first networking platform.
15. The networking platform of claim 14, wherein the processing module obtains the direct device directory of the target networking platform according to the target networking platform ID, and specifically comprises:
if the target networking platform ID is the ID of the networking platform, the processing module acquires a directly-owned device directory stored locally;
and if the target networking platform ID is the ID of a subordinate networking platform of the networking platform, the processing module controls the sending module to send a device directory request message to the subordinate networking platform so as to acquire a direct device directory of the subordinate networking platform.
16. The networking platform of any of claims 9-12, wherein the serial manner is a transmission manner specified in the GB/T28281 standard.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711295364.7A CN109905645B (en) | 2017-12-08 | 2017-12-08 | Video monitoring equipment directory exchange method and networking platform |
| CN202110212691.1A CN112995598A (en) | 2017-12-08 | 2017-12-08 | Video monitoring equipment directory exchange method and networking platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711295364.7A CN109905645B (en) | 2017-12-08 | 2017-12-08 | Video monitoring equipment directory exchange method and networking platform |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110212691.1A Division CN112995598A (en) | 2017-12-08 | 2017-12-08 | Video monitoring equipment directory exchange method and networking platform |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109905645A CN109905645A (en) | 2019-06-18 |
| CN109905645B true CN109905645B (en) | 2021-02-23 |
Family
ID=66940411
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110212691.1A Pending CN112995598A (en) | 2017-12-08 | 2017-12-08 | Video monitoring equipment directory exchange method and networking platform |
| CN201711295364.7A Active CN109905645B (en) | 2017-12-08 | 2017-12-08 | Video monitoring equipment directory exchange method and networking platform |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110212691.1A Pending CN112995598A (en) | 2017-12-08 | 2017-12-08 | Video monitoring equipment directory exchange method and networking platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN112995598A (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112203063B (en) * | 2020-12-06 | 2021-03-30 | 北京贝思科技术有限公司 | Distributed implementation method and system for video networking and electronic equipment |
| CN116016700A (en) * | 2022-12-09 | 2023-04-25 | 北京京东拓先科技有限公司 | Medical image transmission method and device |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010036615A3 (en) * | 2008-09-24 | 2010-06-10 | Visa International Service Association | Intelligent alert system and method |
| CN104065933A (en) * | 2014-06-30 | 2014-09-24 | 苏州科达科技股份有限公司 | Intelligent data acquisition method and system in video surveillance system |
| CN106330833A (en) * | 2015-06-29 | 2017-01-11 | 中兴通讯股份有限公司 | Communication method based on ICAP (Internet Content Adaptation Protocol), client and server |
| CN106341656A (en) * | 2016-08-31 | 2017-01-18 | 浙江远望信息股份有限公司 | Video equipment monitoring method, device and system |
| CN106372221A (en) * | 2016-09-07 | 2017-02-01 | 华为技术有限公司 | File synchronization method, equipment and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP6234146B2 (en) * | 2013-10-04 | 2017-11-22 | キヤノン株式会社 | RECORDING CONTROL DEVICE, RECORDING CONTROL METHOD, AND PROGRAM |
-
2017
- 2017-12-08 CN CN202110212691.1A patent/CN112995598A/en active Pending
- 2017-12-08 CN CN201711295364.7A patent/CN109905645B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2010036615A3 (en) * | 2008-09-24 | 2010-06-10 | Visa International Service Association | Intelligent alert system and method |
| CN104065933A (en) * | 2014-06-30 | 2014-09-24 | 苏州科达科技股份有限公司 | Intelligent data acquisition method and system in video surveillance system |
| CN106330833A (en) * | 2015-06-29 | 2017-01-11 | 中兴通讯股份有限公司 | Communication method based on ICAP (Internet Content Adaptation Protocol), client and server |
| CN106341656A (en) * | 2016-08-31 | 2017-01-18 | 浙江远望信息股份有限公司 | Video equipment monitoring method, device and system |
| CN106372221A (en) * | 2016-09-07 | 2017-02-01 | 华为技术有限公司 | File synchronization method, equipment and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112995598A (en) | 2021-06-18 |
| CN109905645A (en) | 2019-06-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102415845B1 (en) | Internet of Things Resource Subscription Methods, Devices, and Systems | |
| US10638362B2 (en) | Method and system for group communication, group server, and group member device | |
| CN110958281B (en) | Data transmission method and communication device based on Internet of things | |
| EP1542409A1 (en) | Protocol for multi-hop ad-hoc networks | |
| CN110149392A (en) | A kind of management method and device of PUSH message | |
| CN107404512B (en) | Resource subscription method, resource subscription device and resource subscription system | |
| WO2021136180A1 (en) | Service processing method, device and system | |
| CN109314675A (en) | A kind of the determination method, apparatus and system of network slice | |
| US20140012813A1 (en) | Method and apparatus for synchronizing personal information | |
| CN101459526B (en) | Projector sharing conference system based on service discovery | |
| JP7246379B2 (en) | Service layer message templates in communication networks | |
| US20170257440A1 (en) | Communication System | |
| CN113746928A (en) | Cross-cloud service calling method, device and system | |
| CN109905645B (en) | Video monitoring equipment directory exchange method and networking platform | |
| CN106028311B (en) | A kind of terminal registration method and device | |
| EP2517408A2 (en) | Fault tolerant and scalable load distribution of resources | |
| CN113424608B (en) | Entity for providing external services to a network | |
| CN110768818B (en) | Network management method and device | |
| CN110351107B (en) | Configuration management method and device | |
| KR20120138546A (en) | Apparatus and method for discovery based on priority in distributed network and method for determining discovery backoff time | |
| JP6555627B2 (en) | Information distribution apparatus, push notification transmission method, and computer program | |
| WO2017000256A1 (en) | Positioning method and corresponding apparatus | |
| TWI269555B (en) | Systems, methods and machine-readable storage media for event management | |
| TW201101737A (en) | IPMI server system and method thereof | |
| WO2016074455A1 (en) | Group resource update processing method, device and system, and cse |
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 |