Uwb device identification allocation method, apparatus and system

Abstract

This invention discloses a method, apparatus, and system for assigning UWB device identifiers. The method includes: in response to receiving a registration request from a UWB device, an edge node obtains a long identifier (GLID) carried in the registration request; based on preset verification rules, the edge node verifies the validity of the long identifier (GLID), and after the validity verification is successful, assigns a short identifier (SLID) to the UWB device; wherein the short identifier (SLID) is used to identify the UWB device during communication within a local network, and the long identifier (GLID) is used to identify the UWB device during communication within a global network. This invention solves the technical problems of wasted identifier resources or insufficient communication efficiency in existing UWB communication technologies.

Description

Technical Field

[0001] This invention relates to the field of communications, and more specifically, to a method, apparatus, and system for assigning UWB device identifiers. Background Technology

[0002] UWB technology, with its high-precision positioning capabilities, low power consumption, and strong anti-interference characteristics, is widely used in fields such as the Internet of Things, smart manufacturing, and indoor navigation. Due to its wide frequency bandwidth, time-division multiplexing is typically used to prevent signal collisions during communication between multiple nodes. In time-division multiplexing mode, node capacity is directly related to the amount and length of communication messages. To maximize node capacity, it is necessary to minimize the amount and length of necessary communication messages between nodes.

[0003] As a core field that is essential and frequently used in UWB communication, the length and allocation method of the device identifier directly affect communication efficiency and node capacity. Therefore, designing a short, precise and unique device identifier allocation scheme is the key to improving the performance of multi-node UWB communication.

[0004] Currently, existing UWB device identifier allocation schemes are mainly divided into two categories:

[0005] The first type involves setting a globally unique identifier for the device at the factory. This identifier can have a fixed or variable length. The drawback of this approach is that, to ensure global uniqueness, the identifier length is usually quite long, which consumes a significant amount of communication bandwidth, increases message transmission length, hinders the efficiency improvement of time-sharing multiplexing communication among multiple nodes, and limits the expansion of node capacity. This drawback is particularly pronounced in scenarios with densely deployed nodes.

[0006] The second category involves centralized allocation of device identifiers by a gateway or backend during device operation. The allocation strategies are mainly divided into sequential allocation and random allocation with deduplication detection. Sequential allocation is efficient and avoids duplicates, but it has significant drawbacks: when two closely spaced independent UWB systems operate in parallel, the identical identifier allocation order leads to numerous short identifier conflicts, severely impacting communication stability. Random allocation with deduplication detection can reduce local conflicts to some extent, but when local node density is high, the probability of duplicate allocation increases. Without a reasonable fallback strategy, this can result in inefficient identifier allocation, or even failure to complete allocation, and it also fails to completely resolve identifier conflicts between closely spaced independent systems.

[0007] In addition, UWB communication has obvious locality characteristics, that is, devices usually only communicate with other devices within the same local network at high frequency, and communicate with other devices globally at extremely low frequency. Existing solutions do not make full use of this characteristic, resulting in waste of identification resources or insufficient communication efficiency.

[0008] Therefore, there is an urgent need for a device identifier allocation scheme that takes into account the characteristics of short and concise identifiers, efficient allocation, low conflict rate, and can fully adapt to the locality of UWB communication. Summary of the Invention

[0009] This invention provides a UWB device identifier allocation method, apparatus, and system to at least solve the technical problems of wasted identifier resources or insufficient communication efficiency in existing UWB communication technologies.

[0010] According to one aspect of the present invention, a UWB device identifier allocation method is provided, comprising: in response to receiving a registration request sent by a UWB device, an edge node obtains a long identifier GLID carried in the registration request; based on a preset verification rule, the edge node verifies the validity of the long identifier GLID, and after the validity verification is passed, allocates a short identifier SLID to the UWB device; wherein, the short identifier SLID is used to identify the UWB device when communicating within a local network, and the long identifier GLID is used to identify the UWB device when communicating within a global network.

[0011] According to another aspect of the present invention, a UWB device identifier allocation apparatus is also provided, comprising: a registration verification module configured to, in response to receiving a registration request sent by a UWB device, an edge node obtains a long identifier GLID carried in the registration request and performs validity verification on the long identifier GLID based on a preset verification rule; and an identifier allocation module configured to, after the validity verification is passed, allocate a short identifier SLID to the UWB device; wherein the short identifier SLID is a length-coded identifier unique within the local network corresponding to the edge node, used for identifying the UWB device within the local network, and the long identifier GLID is a length-coded identifier unique within the global network, used for identifying the UWB device within the global network.

[0012] According to another aspect of the present invention, a UWB device identifier allocation system is also provided, comprising: a UWB device; and an edge node, wherein the edge node includes the UWB device identifier allocation device as described above.

[0013] In this embodiment of the invention, the above solution solves the technical problems of wasted identification resources or insufficient communication efficiency in UWB communication in the prior art. Attached Figure Description

[0014] The accompanying drawings, which are included to provide a further understanding of the invention and form part of this application, illustrate exemplary embodiments of the invention and, together with their description, serve to explain the invention and do not constitute an undue limitation thereof. In the drawings:

[0015] Figure 1 This is a flowchart of an optional UWB device identifier allocation method according to an embodiment of the present invention;

[0016] Figure 2 This is a flowchart of another optional UWB device identifier allocation method according to an embodiment of the present invention;

[0017] Figure 3 This is an architecture diagram of an optional UWB device identifier allocation system according to an embodiment of the present invention;

[0018] Figure 4 This is a flowchart of another optional UWB device identifier allocation method according to an embodiment of the present invention;

[0019] Figure 5 This is a flowchart of an optional UWB device identifier adaptive allocation method based on operating status according to an embodiment of the present invention;

[0020] Figure 6 This is a schematic diagram of an optional adaptive allocation device according to an embodiment of the present invention;

[0021] Figure 7 A schematic diagram of the structure of a computer device suitable for implementing embodiments of the present disclosure is shown. Detailed Implementation

[0022] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0023] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0024] According to an embodiment of the present invention, a method embodiment of a UWB device identifier allocation method is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0025] To address the shortcomings of existing UWB device identifier allocation schemes, such as unreasonable identifier length, high conflict rate, limited node capacity, and failure to adapt to the locality of UWB communication, this invention provides a UWB device identifier allocation method and system.

[0026] Figure 1 This is a UWB device identifier allocation method according to an embodiment of the present invention, such as... Figure 1 As shown, the method includes the following steps:

[0027] Step S102: In response to receiving a registration request from a UWB device, the edge node obtains the long identifier GLID carried in the registration request.

[0028] First, the global network is divided into multiple local networks, and edge nodes are deployed in each local network. The edge nodes create the identifier mapping table and the short identifier resource pool, wherein the identifier mapping table is used to store long identifier GLID, short identifier SLID and device online status information.

[0029] Then, the edge node obtains the long identifier GLID carried in the registration request. The long identifier GLID is used to identify the UWB device when communicating within the global network, while the short identifier SLID is used to identify the UWB device when communicating within the local network.

[0030] Step S104: Based on preset verification rules, the edge node verifies the validity of the long identifier GLID, and after the validity verification is passed, assigns a short identifier SLID to the UWB device.

[0031] For example, a candidate short identifier (SLID) is generated in the short identifier resource pool using a random allocation method, and the candidate short identifier (SLID) is checked for being occupied based on the identifier mapping table. When the candidate short identifier (SLID) is not occupied, it is allocated as the short identifier (SLID) to the UWB device. When the candidate short identifier (SLID) is occupied, the random allocation method is repeated until the number of repetitions does not reach the threshold, at which point a new candidate short identifier (SLID) is generated randomly and is not occupied, or the number of repetitions reaches the threshold.

[0032] In this embodiment, each device is assigned a globally unique long identifier at the factory, ensuring the global uniqueness of all devices and meeting the needs of cross-local network communication and global management. Local communication uses short identifiers to meet the needs of efficient communication, thus achieving an organic unity between global uniqueness and local efficiency. This solves the problem that existing solutions either have excessively long global identifiers or serious local conflicts.

[0033] After the number of repeated executions reaches the threshold, the method further includes: the edge node traversing the short identifier resource pool based on the identifier mapping table to determine the currently unused minimum short identifier SLID; and allocating the minimum short identifier SLID as the short identifier SLID to the UWB device.

[0034] After the UWB device completes the allocation of the short identifier SLID, the edge node establishes a mapping relationship between the long identifier GLID and the short identifier SLID in the identifier mapping table; and / or when the UWB device is detected to be offline and exceeds a preset timeout period, the mapping relationship between the long identifier GLID and the short identifier SLID is deleted from the identifier mapping table, and the short identifier SLID is returned to the short identifier resource pool, resulting in an updated identifier mapping table.

[0035] The long identifier GLID is a binary code identifier of a first length that is unique within the global network. The long identifier GLID is pre-allocated by the production end and fixed in the storage module of the UWB device during the manufacturing stage. The short identifier SLID is a binary code identifier of a second length that is unique within the local network to which the edge node belongs, and the second length is less than the first length.

[0036] This application embodiment, while ensuring the uniqueness of device identifiers, simplifies the identifier length used in the communication process, thereby improving the communication efficiency of multiple nodes; it also reduces the probability of identifier conflicts in nearby independent systems, improving communication stability. Furthermore, this application embodiment optimizes the identifier allocation strategy, balancing allocation efficiency and identifier resource utilization; it fully utilizes the locality characteristic of UWB communication, achieving a balance between global uniqueness and local communication efficiency, ultimately expanding the node capacity of multi-node UWB systems.

[0037] Figure 2 This is another UWB device identifier allocation method according to an embodiment of the present invention. This method combines factory pre-allocation and runtime dynamic allocation, utilizes the locality characteristic of UWB communication, adopts a two-layer identifier architecture of long and short identifiers, and, with an optimized allocation strategy, can fully utilize resources. For example... Figure 2 As shown, the method includes the following steps:

[0038] Step S202: The device is pre-assigned a globally unique long identifier at the factory.

[0039] Each UWB device is assigned a globally unique long identifier (GLID) by the manufacturer upon leaving the factory. This long identifier uses a sufficiently long encoding (such as 64-bit binary encoding) to ensure global uniqueness across all UWB devices. It is used for global identification, initial registration, and authentication during cross-local network communication. The long identifier is permanently stored in the device's storage module after leaving the factory and cannot be modified, serving as the device's permanent global identity credential.

[0040] Step S204: Local network deployment and edge node initialization.

[0041] In UWB multi-node communication scenarios, local networks are divided according to communication range. Each local network deploys an edge gateway or edge server (hereinafter collectively referred to as "edge node"). The edge node is responsible for the allocation and maintenance of short identifiers for all UWB devices within its local network, as well as the management of the mapping relationship between long and short identifiers. During edge node initialization, an identifier mapping table is created to store information such as the long identifier (GLID), short identifier (SLID), and online status of devices within its local network. Initially, the mapping table is empty.

[0042] Step S206: Device access and dynamic allocation of short identifiers.

[0043] When a UWB device accesses a local network, it sends a registration request to the edge node of the local network. This request carries the device's globally unique long identifier (GLID). After receiving the registration request, the edge node first verifies the validity of the long identifier (such as verifying the identifier format and whether it is a valid factory identifier). If the verification is successful, the edge node dynamically assigns a locally unique short identifier (SLID) to the device. The short identifier uses a shorter fixed-length encoding (such as 8-16 bit binary encoding) and only needs to be unique within the local network, without needing to be globally unique, in order to minimize the length of communication messages.

[0044] This embodiment fully utilizes the locality characteristic of UWB communication. When devices communicate locally, they use short identifiers, which greatly reduces the length of the identifier field in the communication message, reduces the amount of message transmission, adapts to the time-division multiplexing communication mode of multiple nodes, effectively improves communication efficiency, reduces the probability of signal collisions, and significantly expands the node capacity of the multi-node UWB system, which is especially suitable for scenarios with dense node deployment.

[0045] The allocation of short identifiers adopts a hybrid strategy of "random allocation with duplicate detection + sequential allocation as a fallback". The specific allocation process is as follows:

[0046] (1) The edge node randomly generates a short identifier from the preset short identifier resource pool, queries the identifier mapping table maintained by itself, and checks whether the randomly generated short identifier has been assigned.

[0047] (2) If the short identifier has not been assigned, it shall be assigned to the currently accessed device, and the long identifier, short identifier and online status information of the device shall be added to the identifier mapping table to complete the short identifier assignment;

[0048] (3) If the short identifier has been assigned, record the number of repetitions, generate a new short identifier randomly, and repeat steps (1)-(2).

[0049] (4) If the number of times the random allocation is repeated exceeds the preset threshold (the preferred threshold in this invention is 3 times), then switch to the sequential allocation strategy: the edge node queries the identifier mapping table, finds the shortest identifier that is not currently in use, allocates it to the current access device, and updates the identifier mapping table.

[0050] This embodiment adopts a hybrid allocation strategy of "random allocation + sequential fallback". Random allocation with duplicate detection can avoid a large number of identifier conflicts caused by sequential allocation in close-range independent UWB systems. When the random allocation is repeated more than 3 times, it switches to sequential allocation. This not only solves the problem of high repetition probability and low allocation efficiency of random allocation when nodes are dense, but also ensures the timeliness of identifier allocation, takes into account both the conflict rate and allocation efficiency, and improves the communication stability in multiple scenarios.

[0051] Step S208, Local communication and identifier mapping maintenance.

[0052] After a device connects to the local network and obtains a short identifier (SLID), it only needs to carry the short identifier (SLID) as its identity when communicating with other devices within the local network, enabling short message transmission and reducing message length and communication bandwidth usage. The edge node maintains an identifier mapping table in real time. When a device goes offline, the mapping relationship between the device's long identifier and short identifier is retained for a period of time (a preset timeout period can be used). If the device reconnects within the timeout period, it directly reuses the original short identifier without reallocation. If the device does not reconnect within the timeout period, the edge node releases the short identifier and returns it to the short identifier resource pool for use by newly connected devices, improving the utilization rate of identifier resources.

[0053] In this embodiment, edge nodes maintain a mapping relationship between short and long identifiers. After a device goes offline and times out, it releases the short identifier for reuse by a new device, thus avoiding the waste of short identifier resources. The hybrid allocation strategy can dynamically adjust the allocation method according to the local node density. When the node density is low, random allocation can make full use of identifier resources. When the node density is high, sequential fallback can ensure allocation efficiency, adapting to UWB communication scenarios with different node densities.

[0054] Step S210, cross-local network communication and identity conversion.

[0055] When a device needs to communicate with devices in other local networks, the device sends its long identifier (GLID) to the edge node of its local network. The edge node forwards the communication request carrying the long identifier to the edge node of the target local network through the communication link across local networks. The edge node of the target local network queries its own identifier mapping table based on the long identifier (if the target device is in the same network), obtains the corresponding short identifier, and then forwards the communication request to the target device. The communication response process is similar, realizing normal communication across local networks while taking into account both global uniqueness and local communication efficiency.

[0056] This application also provides a UWB device identifier allocation system, which is used to implement the above-mentioned UWB device identifier allocation method, such as... Figure 3 As shown, the system includes a UWB device 36, an edge node 34, and an optional cloud management platform 32.

[0057] UWB devices, as communication terminals, have built-in storage and communication modules. The storage module is used to store the globally unique long identifier (GLID) assigned at the factory. The communication module is used to send registration requests and transmit communication messages to edge nodes. Short identifiers (SLID) are used in local communication, while long identifiers (GLID) are used in cross-local network communication.

[0058] Edge nodes are deployed in each local network, serving as the core for identifier allocation and management. They include a registration and verification module, an identifier allocation module, a mapping maintenance module, and a communication forwarding module. The registration and verification module receives registration requests from UWB devices and verifies the validity of the long identifier (GLID) carried in the request. The identifier allocation module assigns short identifiers (SLIDs) to verified UWB devices, employing a random allocation strategy with duplicate detection. When the random allocation is repeated more than three times, it switches to a sequential allocation strategy. The mapping maintenance module creates and maintains an identifier mapping table, storing information such as the long identifier, short identifier, and online status of devices within the local network, enabling the release and reuse of short identifiers and real-time updates of mapping relationships. The communication forwarding module forwards communication messages from devices within the local network, as well as message forwarding and identifier conversion (the conversion between long and short identifiers) during cross-local network communication.

[0059] The cloud management platform is an optional device used for global management of all edge nodes in the local network. It can query information such as the identifier allocation, mapping relationship, and online status of each edge node, enabling unified monitoring of all devices. When an edge node fails, it can assist in emergency handling of identifier allocation, thereby improving the reliability of the system.

[0060] The system has a simple architecture, with edge nodes deployed in local networks, eliminating the need for real-time intervention from a centralized backend, thus reducing deployment costs and maintenance complexity. It can adapt to UWB multi-node communication scenarios of different scales, and can be flexibly deployed in both small local networks and large multi-local network linkage scenarios. It is also compatible with existing UWB communication systems, making it easy to upgrade and transform.

[0061] The system provided in this application embodiment can be applied to indoor UWB positioning and communication. The system can include two relatively close independent local networks (network A and network B), with one edge gateway deployed in each local network. Each edge gateway manages 50-100 UWB positioning tags (i.e., UWB devices). The specific implementation of this system can also be as follows: Figure 4 As shown, it includes the following steps:

[0062] Step S402: The device is pre-assigned a globally unique long identifier at the factory.

[0063] Each UWB positioning tag is assigned a 64-bit binary globally unique long identifier (GLID) by the production end when it leaves the factory. The encoding format adopts the UUID v4 standard to ensure that the GLID of all tags is globally unique. The GLID is fixed in the tag's Flash storage module and cannot be modified.

[0064] One edge gateway is deployed on network A and one on network B. The edge gateway adopts an industrial-grade IoT gateway and supports UWB signal reception and forwarding. When the edge gateway is initialized, an identifier mapping table is created. The mapping table contains five fields: "GLID (64-bit), SLID (8-bit), device online status, registration time, and last communication time". In the initial state, all fields are empty, and the short identifier resource pool is 00000000-11111111 (a total of 256 8-bit binary identifiers).

[0065] Step S404: Device access and dynamic allocation of short identifiers.

[0066] When a UWB positioning tag accesses network A, the tag sends a registration request to the edge gateway of network A through the UWB communication module, carrying its own 64-bit GLID in the request.

[0067] After receiving the request, the registration and verification module of the edge gateway verifies whether the encoding format of the GLID conforms to the UUID v4 standard. If the verification is successful, the identifier allocation module executes the allocation strategy.

[0068] 1) The identifier allocation module randomly generates an 8-bit binary short identifier (e.g., 00000010), queries the identifier mapping table, and checks whether the SLID has been allocated. If it has not been allocated, the SLID is assigned to the tag, and the corresponding GLID, SLID, online status (online), registration time, and current time are entered into the mapping table to complete the allocation.

[0069] 2) If the randomly generated SLID has already been assigned (e.g., 00000010 has been assigned to another tag), record the repetition count (marked as 1), and generate a new SLID (e.g., 00000011). Query the mapping table again. If the SLID is still repeated, continue generating until the repetition count reaches 3.

[0070] 3) When duplicates occur in all 3 random generation attempts, the identifier allocation module switches to a sequential allocation strategy, queries the mapping table for the smallest unused SLID (e.g., the current smallest unused SLID is 00000100), assigns that SLID to the label, and completes the allocation;

[0071] The tag access process of network B is exactly the same as that of network A. Due to the use of a random allocation strategy, the probability of SLID duplication between the two close-range networks A and B is extremely low, thus avoiding a large number of conflicts.

[0072] Step S406, Local communication and identifier mapping maintenance.

[0073] After a tag is connected, when communicating with other tags and edge gateways within network A, it only carries an 8-bit SLID as its identity identifier, significantly shortening the message length compared to the existing 64-bit GLID scheme. The edge gateway's mapping and maintenance module updates the device's online status in real time. When a tag goes offline, it records the last communication time. If the timeout exceeds a preset timeout period (e.g., 10 minutes), the tag's SLID is released and returned to the short identifier resource pool for reuse by newly connected tags. If the tag reconnects within the timeout period, the edge gateway queries the mapping table and reuses the original SLID without needing to reallocate it.

[0074] Finally, cross-local network communication and identifier conversion are performed. When a tag in network A needs to communicate with a tag in network B, the tag in network A sends its 64-bit GLID to the edge gateway of network A. The edge gateway of network A forwards the communication request carrying the GLID to the edge gateway of network B via the Ethernet link. The edge gateway of network B queries its own identifier mapping table to find the SLID corresponding to the GLID (if the tag has already connected to network B), and forwards the communication request to the tag. The tag's response message is returned through the reverse path, realizing cross-network communication.

[0075] This application also provides a UWB device identifier allocation method, such as... Figure 5 As shown, it includes the following steps:

[0076] Step S502, local network initialization;

[0077] During the system initialization phase, the UWB communication system is divided into multiple local networks, and edge nodes are deployed within each local network. Upon startup, each edge node constructs data structures related to identifier management, including: establishing an identifier mapping table to record the correspondence between long identifiers (GLIDs) and short identifiers (SLIDs), as well as device online status, access time, and most recent communication time; constructing a short identifier resource pool containing all allocable short identifiers within a preset range; and initializing a runtime status statistics module for real-time collection and updating of the local network's runtime status.

[0078] Step S504: Device access and long identifier acquisition.

[0079] When a UWB device accesses a local area network, it sends a registration request to the corresponding edge node. This registration request carries a long identifier (GLID) pre-assigned to the device at the factory. Upon receiving the registration request, the edge node verifies the validity of the GLID, including verifying the identifier format's legality and uniqueness. If the verification passes, the device is included in the current local network's management scope and enters the short identifier allocation process.

[0080] Step S506, adaptive allocation strategy based on running status;

[0081] Before allocating short identifiers, edge nodes first assess the current operational status of the local network and dynamically determine the identifier allocation strategy based on the assessment results. Specifically, edge nodes obtain the following operational status information through the operational status statistics module: the number of currently online devices, reflecting the network load level; the proportion of short identifier resources used, representing the resource scarcity; the number of identifier conflicts within a preset time window, reflecting allocation stability; and the number of new devices connecting per unit time, reflecting the network's dynamic change rate. After obtaining the above operational status information, edge nodes, based on preset state division rules, classify the current local network into at least one of the following three allocation states: when the number of online devices is small and the resource usage ratio is low, it is determined to be a low-load state; when the resource usage ratio increases or the device access rate increases, it is determined to be a medium-load state; when the detected identifier conflict frequency exceeds a preset threshold, it is determined to be a high-conflict-risk state.

[0082] Step S508: Short identifier allocation and mapping maintenance.

[0083] After determining the allocation status, edge nodes select corresponding short identifier allocation strategies based on different statuses: under low load, a random allocation strategy is used to improve allocation speed; under medium load, a structured allocation strategy is used, dividing the short identifier resource pool into sub-intervals for allocation to reduce the probability of collisions; under high collision risk, a restricted allocation strategy is used, allocating only within currently unoccupied identifier intervals and increasing the collision detection frequency. Through this approach, the short identifier allocation strategy is transformed from a fixed strategy to a dynamically adjusted strategy based on network status, thus balancing allocation efficiency and collision control capabilities under different network conditions.

[0084] In this embodiment, in response to receiving a registration request from a UWB device, the edge node obtains the long identifier GLID carried in the registration request. Based on the current local network's operational status information, the edge node determines an identifier allocation strategy, wherein the operational status information includes at least one of the following: the number of currently online devices, the proportion of short identifier resources occupied, the historical identifier conflict frequency, and the device access rate. Based on the operational status information, the edge node divides the current local network into different allocation states and selects a corresponding short identifier allocation strategy for each allocation state. After the long identifier GLID passes validity verification, a short identifier SLID is allocated to the UWB device according to the selected short identifier allocation strategy. The short identifier SLID is used to identify the UWB device during communication within the local network, and the long identifier GLID is used to identify the UWB device during communication within the global network. The above methods achieve two objectives: firstly, by introducing operational status information, the short identifier allocation strategy can be dynamically adjusted, avoiding the problem of decreased allocation efficiency caused by using a single allocation strategy under high load or high conflict scenarios; secondly, by selecting different allocation strategies according to different network conditions, the probability of identifier conflicts is effectively reduced, and the overall communication stability of the system is improved.

[0085] This application also provides a UWB device identifier allocation device, such as... Figure 6 As shown, the system includes: a registration verification module 62, configured to, in response to receiving a registration request sent by a UWB device, obtain the long identifier GLID carried in the registration request, and perform validity verification on the long identifier GLID based on preset verification rules; and an identifier allocation module 64, configured to allocate a short identifier SLID to the UWB device after the validity verification is passed. The short identifier SLID is a unique length-coded identifier within the local network corresponding to the edge node, used for identifying the UWB device within the local network. The long identifier GLID is a unique length-coded identifier within the global network, used for identifying the UWB device within the global network.

[0086] It should be noted that the UWB device identifier allocation device provided in the above embodiments is only an example of the division of the above functional modules. In practical applications, the above functional allocation can be completed by different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the UWB device identifier allocation device and the UWB device identifier allocation method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0087] Figure 7A schematic diagram of a computer device suitable for implementing embodiments of the present disclosure is shown. It should be noted that... Figure 7 The computer device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0088] like Figure 7 As shown, the computer device includes a central processing unit (CPU) 1001, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage section 1008 into a random access memory (RAM) 1003. The RAM 1003 also stores various programs and data required for system operation. The CPU 1001, ROM 1002, and RAM 1003 are interconnected via a bus 1004. An input / output (I / O) interface 1005 is also connected to the bus 1004.

[0089] The following components are connected to I / O interface 1005: an input section 1006 including a keyboard, mouse, etc.; an output section 1007 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 1008 including a hard disk, etc.; and a communication section 1009 including a network interface card such as a LAN card, modem, etc. The communication section 1009 performs communication processing via a network such as the Internet. A drive 1010 is also connected to I / O interface 1005 as needed. A removable medium 1011, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 1010 as needed so that computer programs read from it can be installed into storage section 1008 as needed.

[0090] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for assigning UWB device identifiers, characterized in that, include: In response to receiving a registration request from a UWB device, the edge node obtains the long identifier GLID carried in the registration request; Based on preset verification rules, the edge node verifies the validity of the long identifier GLID, and after the validity verification is passed, assigns a short identifier SLID to the UWB device; The short identifier SLID is used to identify the UWB device when communicating within a local network, and the long identifier GLID is used to identify the UWB device when communicating within a global network.

2. The method according to claim 1, characterized in that, Assigning a short identifier (SLID) to the UWB device includes: Candidate short identifiers (SLIDs) are generated in the short identifier resource pool using a random allocation method, and the candidate short identifiers (SLIDs) are checked based on the identifier mapping table to see if they have been occupied. When the candidate short identifier (SLID) is not occupied, the candidate short identifier (SLID) is assigned to the UWB device as the short identifier (SLID); When the candidate short identifier (SLID) is already occupied, the random allocation method is repeated until the number of repetitions does not reach the threshold and a new candidate short identifier (SLID) is not occupied, or the number of repetitions reaches the threshold.

3. The method according to claim 2, characterized in that, After the number of repetitions reaches the threshold, the method further includes: The edge node traverses the short identifier resource pool based on the identifier mapping table to determine the smallest unused short identifier SLID. The minimum short identifier (SLID) is assigned as the short identifier (SLID) to the UWB device.

4. The method according to claim 3, characterized in that, Before the edge node obtains the long identifier GLID carried in the registration request, the method further includes: The global network is divided into multiple local networks, and edge nodes are deployed in each local network. The edge node creates the identifier mapping table and the short identifier resource pool, wherein the identifier mapping table is used to store long identifier GLID, short identifier SLID and device online status information.

5. The method according to claim 4, characterized in that, The method further includes: After the UWB device completes the allocation of the short identifier SLID, the edge node establishes a mapping relationship between the long identifier GLID and the short identifier SLID in the identifier mapping table; and / or When the UWB device is detected to be offline and the preset timeout period has been exceeded, the mapping relationship between the long identifier GLID and the short identifier SLID is deleted from the identifier mapping table, and the short identifier SLID is returned to the short identifier resource pool to obtain the updated identifier mapping table.

6. The method according to claim 1, characterized in that, The long identifier GLID is a binary code identifier of a first length that is unique across the global network. The long identifier GLID is pre-allocated by the manufacturing end and stored in the storage module of the UWB device during the manufacturing process; and / or The short identifier SLID is a binary encoded identifier of a second length that is unique within the local network to which the edge node belongs, and the second length is less than the first length.

7. A UWB device identifier allocation device, characterized in that, include: The registration verification module is configured to, in response to receiving a registration request sent by a UWB device, obtain the long identifier GLID carried in the registration request, and verify the validity of the long identifier GLID based on preset verification rules. The identifier allocation module is configured to assign a short identifier (SLID) to the UWB device after the validity verification is passed; The short identifier SLID is a length-coded identifier unique within the local network corresponding to the edge node, used to identify the UWB device within the local network. The long identifier GLID is a length-coded identifier unique within the global network, used to identify the UWB device within the global network.

8. A UWB device identification and allocation system, characterized in that, include: UWB equipment; Edge nodes include the UWB device identifier allocation device as described in claim 7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein, when the program is executed, it controls the device on which the computer-readable storage medium is located to perform the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images