Indoor cluster communication method and system based on UWB positioning

Abstract

The present invention discloses an indoor cluster communication method and system based on UWB positioning, which belongs to the technical field of communication systems. The technical problem to be solved is how to realize the visual scheduling of indoor personnel by the cluster communication system. The method and system include the following steps: a global dispatching station in the cluster communication system initiates an initialization request to the UWB positioning engine, and based on the initialization request, the UWB positioning engine returns the tag information of the UWB positioning tag corresponding to each cluster user to the cluster communication system, and the tag information includes the tag identification code, user name and configuration parameters; the global dispatching station pre-defines the user information of each cluster user, and binds the cluster user and the tag identification code; for the target cluster user to be located, a positioning subscription request is initiated to the UWB positioning engine through the global dispatching station, and the UWB positioning engine periodically returns the location information to the global dispatching station based on the tag identification code and subscription period specified in the subscription request.

Description

Technical Field

[0001] The present invention relates to the technical field of communication systems, and in particular to an indoor cluster communication method and system based on UWB positioning. Background Art

[0002] Currently, trunking communication systems rely on GPS for positioning, enabling map-based visual command and dispatch. The dispatch center periodically subscribes to user device GPS data. Upon successful subscription, the device's actual location is displayed on a map. This location allows for cluster calls, dynamic reorganization, and trajectory playback. However, when law enforcement or on-duty personnel enter indoor environments, user devices are unable to report GPS information, making visual trunking dispatch impossible.

[0003] UWB positioning technology uses radio pulse signals with nanosecond-level pulse widths as positioning carriers, effectively avoiding interference and offering the highest accuracy for indoor wireless positioning. By deploying a specified number of UWB positioning base stations within an area, tags attached to people, vehicles, and assets can be accurately located in real time. However, UWB positioning systems are typically isolated, enabling only personnel control within the UWB system and failing to effectively connect with trunked communication systems.

[0004] How to realize the visual scheduling of indoor personnel by the cluster communication system is a technical problem that needs to be solved. Summary of the Invention

[0005] The technical task of the present invention is to address the above shortcomings and provide an indoor cluster communication method and system based on UWB positioning to solve the technical problem of how to realize the visual scheduling of indoor personnel by the cluster communication system.

[0006] In a first aspect, the present invention provides an indoor cluster communication method based on UWB positioning, which is applied to a cluster communication system and a UWB positioning engine. The global dispatch console of the cluster communication system interacts with the UWB positioning engine through a synchronous interface. The method comprises the following steps:

[0007] In the trunking communication system, the global dispatching console initiates an initialization request to the UWB positioning engine. Based on the initialization request, the UWB positioning engine returns the tag information of the UWB positioning tag corresponding to each cluster user to the trunking communication system. The tag information includes the tag identification code, user name, and configuration parameters.

[0008] The global dispatching console pre-defines user information of each cluster user, including a user name. Each cluster user has a different user name. Based on the user name, the cluster user is bound to the tag identification code through the global dispatching console.

[0009] For the target cluster user to be located, a positioning subscription request is initiated to the UWB positioning engine through the global dispatch center. The UWB positioning engine periodically returns location information to the global dispatch center based on the tag identification code and subscription period specified in the subscription request.

[0010] Preferably, after receiving the initialization request, the UWB positioning engine verifies the initiator of the initialization request, and after confirming that the initiator of the initialization request is the global dispatching station, returns the tag information of the UWB positioning tag corresponding to each cluster user to the global dispatching station;

[0011] After receiving the subscription request, the UWB positioning engine verifies the initiator of the subscription request, confirms that the initiator of the subscription request is the global dispatch station, and returns the corresponding tag information to the global dispatch station based on the tag identification code specified in the subscription request.

[0012] Preferably, for the target cluster user to be located, the lower dispatching station in the cluster communication system sends a subscription request to the UWB positioning engine through the global dispatching station, and receives the location information returned by the UWB positioning engine through the global dispatching station.

[0013] Preferably, the global dispatching station caches the received tag information and location information locally.

[0014] Preferably, the UWB positioning engine returns the tag information and location information to the global dispatching console in the form of XML text.

[0015] In a second aspect, the present invention provides an indoor cluster communication system based on UWB positioning, comprising a cluster communication system, a UWB positioning engine, and an interface, wherein a global dispatching console in the cluster communication system interacts with the UWB positioning engine through the interface;

[0016] The global dispatching station in the cluster communication system is used to initiate an initialization request to the UWB positioning engine, and the UWB positioning engine is used to return the tag information of the UWB positioning tag corresponding to each cluster user to the cluster communication system based on the initialization request, and the tag information includes a tag identification code, user name and configuration parameters;

[0017] The global dispatching console pre-defines user information of each cluster user, wherein the user information includes a user name, and the user names of cluster users are different. Based on the user name, the cluster user and the tag identification code are bound through the global dispatching console;

[0018] For a target cluster user to be located, the global dispatching station in the cluster communication system is used to initiate a location subscription request to the UWB positioning engine;

[0019] Correspondingly, the UWB positioning engine is used to periodically return location information to the global dispatching station based on the tag identification code and subscription period specified in the subscription request.

[0020] Preferably, after receiving the initialization request, the UWB positioning engine is used to perform: verifying the initiator of the initialization request, and after confirming that the initiator of the initialization request is the global dispatching station, returning the tag information of the UWB positioning tag corresponding to each cluster user to the global dispatching station;

[0021] After receiving the subscription request, the UWB positioning engine is used to perform: verifying the initiator of the subscription request, and after confirming that the initiator of the subscription request is the global dispatch station, returning the corresponding tag information to the global dispatch station based on the tag identification code specified in the subscription request.

[0022] Preferably, for the target cluster user to be located, the lower dispatching station in the cluster communication system is used to send a subscription request to the UWB positioning engine through the global dispatching station, and is used to receive the location information returned by the UWB positioning engine through the global dispatching station.

[0023] Preferably, the global dispatching station is used to cache the received tag information and location information locally.

[0024] Preferably, the UWB positioning engine is used to return the tag information and location information to the global dispatching console in the form of XML text.

[0025] The UWB positioning-based indoor cluster communication method and system of the present invention have the following advantages:

[0026] The combination of the cluster communication system and UWB indoor positioning technology enables subscription to UWB tag information data and location information, realizing precise visual scheduling capabilities indoors and solving the problem of indoor scheduling being impossible in industry scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments or descriptions of the prior art. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0028] The present invention will be further described below with reference to the accompanying drawings.

[0029] Figure 1 This is a schematic diagram of the interaction between the global dispatching console and the UWB positioning engine through an interface in the indoor cluster communication method based on UWB positioning in Example 1;

[0030] Figure 2 A flowchart of an indoor cluster communication method based on UWB positioning;

[0031] Figure 3 It is a message protocol stack for the interface between the global dispatching station and the UWB positioning engine in the indoor cluster communication method based on UWB positioning in Example 1;

[0032] Figure 4 This is a schematic diagram of the communication between the global dispatching station and the UWB positioning engine based on the HTP protocol in the indoor cluster communication method based on UWB positioning in Example 1. DETAILED DESCRIPTION

[0033] The present invention will be further described below with reference to the accompanying drawings and specific embodiments so that those skilled in the art can better understand the present invention and implement it. However, the embodiments given are not intended to limit the present invention. Unless there is a conflict, the embodiments of the present invention and the technical features in the embodiments may be combined with each other.

[0034] The embodiments of the present invention provide an indoor cluster communication method and system based on UWB positioning, which are used to solve the technical problem of how to implement visual scheduling of indoor personnel by a cluster communication system.

[0035] Example 1:

[0036] The present invention provides an indoor cluster communication method based on UWB positioning, such as Figure 1 The system is applied to a cluster communication system and a UWB positioning engine, and the global dispatching console of the cluster communication system exchanges data with the UWB positioning engine through a synchronous interface.

[0037] like Figure 2 As shown, the method of this embodiment includes the following steps:

[0038] S100: In a cluster communication system, a global dispatching console initiates an initialization request to a UWB positioning engine. Based on the initialization request, the UWB positioning engine returns tag information of a UWB positioning tag corresponding to each cluster user to the cluster communication system. The tag information includes a tag identification code, a user name, and configuration parameters.

[0039] S200: User information of each cluster user is predefined in the global dispatching console, the user information including a user name, and the user names of cluster users are different. Based on the user name, the cluster user is bound to the tag identification code through the global dispatching console;

[0040] S300: For the target cluster user to be located, a location subscription request is initiated to the UWB positioning engine through the global dispatching station. The UWB positioning engine periodically returns location information to the global dispatching station based on the tag identification code and subscription period specified in the subscription request.

[0041] In this embodiment, the synchronization interface between the global dispatch station and the UWB positioning engine communicates based on the HTTPS protocol to transmit tag information and location information between the global dispatch station and the UWB positioning engine. The message protocol stack is as follows: Figure 3 The control functions of the interface include managing data acquisition requests and responses.

[0042] In step S100 , after receiving the initialization request, the UWB positioning engine verifies the initiator of the initialization request, and after confirming that the initiator of the initialization request is the global dispatching station, returns the tag information of the UWB positioning tag corresponding to each cluster user to the global dispatching station.

[0043] Request UWB tag information:

[0044] GET / UWB / ;data-sync? version=1.0&applicant_type=dc&data_type=user_info&fleet_id=5&versionid=HTTP / 1.1.

[0045] In step S300 , after receiving the subscription request, the UWB positioning engine verifies the initiator of the subscription request, confirms that the initiator of the subscription request is the global dispatch station, and returns the corresponding tag information to the global dispatch station based on the tag identification code specified in the subscription request.

[0046] like Figure 4 As shown, the process of requesting UWB location data is:

[0047] GET / UWB / ;data-sync? version=1.0&applicant_type=dc&data_type=user_location&user_info=111111&fleet_id=5&versionid=HTTP / 1.1

[0048] Successful response

[0049] HTTP / 1.1 200 OK.

[0050] The UWB positioning engine returns the tag information and location information to the global dispatch center in the form of XML text. When the visual scheduling function is turned off, the dispatch center initiates a location subscription request to the positioning engine.

[0051] In this embodiment, the global dispatching console visually presents the UWB location information of the cluster users and can initiate related cluster services based on the location information on the map.

[0052] The trunked communication system includes a global dispatching station and lower-level dispatching stations. For a target trunked user to be located, the lower-level dispatching station in the trunked communication system sends a subscription request to the UWB positioning engine through the global dispatching station, and receives the location information returned by the UWB positioning engine through the global dispatching station. In other words, in this embodiment, when the lower-level dispatching station needs to obtain user location information, it must initiate a subscription request for positioning information from the global dispatching station.

[0053] In this embodiment, the global dispatch station may cache part of the data, and use the cached data when the UWB subscription request fails.

[0054] In the scenario of combining with outdoor visual scheduling, the global dispatch console needs to request longitude and latitude information from the UWB engine, convert the indoor positioning information into longitude and latitude, and achieve consistency and continuity with the outdoor positioning information.

[0055] Example 2:

[0056] The present invention provides an indoor cluster communication system based on UWB positioning, comprising a cluster communication system, a UWB positioning engine and an interface. A global dispatching console in the cluster communication system communicates with the UWB positioning engine via the interface.

[0057] Among them, the global dispatching console in the cluster communication system is used to initiate an initialization request to the UWB positioning engine, and the UWB positioning engine is used to return the tag information of the UWB positioning tag corresponding to each cluster user to the cluster communication system based on the initialization request. The tag information includes the tag identification code, user name and configuration parameters.

[0058] As a specific implementation of the positioning engine, after receiving the initialization request, the positioning engine is used to perform the following: verify the initiator of the initialization request, and after confirming that the initiator of the initialization request is the global dispatch station, return the tag information of the UWB positioning tag corresponding to each cluster user to the global dispatch station.

[0059] Request UWB tag information:

[0060] GET / UWB / ;data-sync? version=1.0&applicant_type=dc&data_type=user_info

[0061] &fleet_id=5&versionid=HTTP / 1.1.

[0062] The global dispatching console pre-defines user information of each cluster user, including a user name. The user names of cluster users are different. Based on the user name, the cluster user and the tag identification code are bound through the global dispatching console.

[0063] For the target cluster user to be located, the global dispatching station in the cluster communication system is used to initiate a positioning subscription request to the UWB positioning engine; correspondingly, the UWB positioning engine is used to periodically return location information to the global dispatching station based on the tag identification code and subscription period specified in the subscription request.

[0064] As a specific implementation of the positioning engine, after receiving a subscription request, the positioning engine is used to perform the following: verify the initiator of the subscription request, and after confirming that the initiator of the subscription request is the global dispatch station, return the corresponding tag information to the global dispatch station based on the tag identification code specified in the subscription request.

[0065] The process of requesting UWB location data is as follows:

[0066] GET / UWB / ;data-sync? version=1.0&applicant_type=dc&data_type=user_location&user_info=111111&fleet_id=5&versionid=HTTP / 1.1

[0067] Successful response

[0068] HTTP / 1.1 200 OK.

[0069] In this embodiment, the UWB positioning engine returns the tag information and location information to the global dispatching console in the form of XML text. When the visual scheduling function is turned off, the dispatching console initiates a location subscription request to the positioning engine.

[0070] For the target cluster user to be located, the lower dispatching station in the cluster communication system is used to send a subscription request to the UWB positioning engine through the global dispatching station, and is used to receive the location information returned by the UWB positioning engine through the global dispatching station.

[0071] In this embodiment, the global dispatching console visually presents the UWB location information of the cluster users and can initiate related cluster services based on the location information on the map.

[0072] As a specific implementation of the global dispatch console, it caches received tag and location information locally. If a UWB subscription request fails, the cached data is used. In scenarios integrated with outdoor visual dispatch, the global dispatch console requests longitude and latitude information from the UWB engine, converts the indoor positioning information into longitude and latitude, and ensures consistency and continuity with the outdoor positioning information.

[0073] The present invention has been shown and described in detail above through the accompanying drawings and preferred embodiments. However, the present invention is not limited to these disclosed embodiments. Based on the above multiple embodiments, those skilled in the art can know that the code review methods in the above different embodiments can be combined to obtain more embodiments of the present invention, and these embodiments are also within the scope of protection of the present invention.

Claims

1. An indoor cluster communication method based on UWB positioning, characterized in that: Applied to a cluster communication system and a UWB positioning engine, the global dispatching console of the cluster communication system exchanges data with the UWB positioning engine through a synchronous interface, and the method includes the following steps: In the trunking communication system, the global dispatching console initiates an initialization request to the UWB positioning engine. Based on the initialization request, the UWB positioning engine returns the tag information of the UWB positioning tag corresponding to each cluster user to the trunking communication system. The tag information includes the tag identification code, user name, and configuration parameters. The global dispatching console pre-defines user information of each cluster user, including a user name. Each cluster user has a different user name. Based on the user name, the cluster user is bound to the tag identification code through the global dispatching console. For the target cluster user to be located, a positioning subscription request is initiated to the UWB positioning engine through the global dispatch center. The UWB positioning engine periodically returns location information to the global dispatch center based on the tag identification code and subscription period specified in the subscription request.

2. The indoor cluster communication method based on UWB positioning according to claim 1, characterized in that: After receiving the initialization request, the UWB positioning engine verifies the initiator of the initialization request, and after confirming that the initiator of the initialization request is the global dispatching station, returns the tag information of the UWB positioning tag corresponding to each cluster user to the global dispatching station; After receiving the subscription request, the UWB positioning engine verifies the initiator of the subscription request, confirms that the initiator of the subscription request is the global dispatch station, and returns the corresponding tag information to the global dispatch station based on the tag identification code specified in the subscription request.

3. The indoor cluster communication method based on UWB positioning according to claim 1 or 2, characterized in that: For the target cluster user to be located, the lower dispatching station in the cluster communication system sends a subscription request to the UWB positioning engine through the global dispatching station, and receives the location information returned by the UWB positioning engine through the global dispatching station.

4. The indoor cluster communication method based on UWB positioning according to claim 3, characterized in that: The global dispatching station caches the received tag information and location information locally.

5. The indoor cluster communication method based on UWB positioning according to claim 1, characterized in that: The UWB positioning engine returns the tag information and location information to the global dispatching console in the form of XML text.

6. An indoor cluster communication system based on UWB positioning, characterized in that: It includes a cluster communication system, a UWB positioning engine and an interface, wherein the global dispatching console in the cluster communication system interacts with the UWB positioning engine through the interface; The global dispatching station in the cluster communication system is used to initiate an initialization request to the UWB positioning engine, and the UWB positioning engine is used to return the tag information of the UWB positioning tag corresponding to each cluster user to the cluster communication system based on the initialization request, and the tag information includes a tag identification code, user name and configuration parameters; The global dispatching console pre-defines user information of each cluster user, wherein the user information includes a user name, and the user names of cluster users are different. Based on the user name, the cluster user and the tag identification code are bound through the global dispatching console; For a target cluster user to be located, the global dispatching station in the cluster communication system is used to initiate a location subscription request to the UWB positioning engine; Correspondingly, the UWB positioning engine is used to periodically return location information to the global dispatching station based on the tag identification code and subscription period specified in the subscription request.

7. The indoor cluster communication system based on UWB positioning according to claim 6, characterized in that: After receiving the initialization request, the UWB positioning engine is used to perform the following operations: verifying the initiator of the initialization request, and after confirming that the initiator of the initialization request is the global dispatching station, returning the tag information of the UWB positioning tag corresponding to each cluster user to the global dispatching station; After receiving the subscription request, the UWB positioning engine is used to perform: verifying the initiator of the subscription request, confirming that the initiator of the subscription request is the global dispatch station, and returning the corresponding tag information to the global dispatch station based on the tag identification code specified in the subscription request.

8. The indoor cluster communication system based on UWB positioning according to claim 6 or 7, characterized in that: For the target cluster user to be located, the lower dispatching station in the cluster communication system is used to send a subscription request to the UWB positioning engine through the global dispatching station, and is used to receive the location information returned by the UWB positioning engine through the global dispatching station.

9. The indoor cluster communication system based on UWB positioning according to claim 8, characterized in that: The global dispatch console is used to cache the received tag information and location information locally.

10. The indoor cluster communication system based on UWB positioning according to claim 6, characterized in that: The UWB positioning engine is used to return the tag information and location information to the global dispatching console in the form of XML text.

Images