System and method for loading network device
By determining the trusted area in the wireless network and automatically loading the IoT device using UWB technology, the existing cumbersome loading process is solved, and a more efficient and user-friendly loading experience is achieved.
Patent Information
- Application Number
- CN202410567729.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-04-23
- Filing Date
- 2024-05-09
- Publication Date
- 2024-11-22
AI Technical Summary
The existing process of loading IoT devices is cumbersome, and users need to manually scan the QR code or enter the setting code, which increases user friction, especially when multiple devices need to be loaded, which is time-consuming and impractical.
By determining the trusted area covered by wireless networks and detecting electronic devices near the trusted area, using UWB technology to automatically load IoT devices, including the concepts of fixed trusted areas and mobile trusted areas, and using user interface widgets to receive configuration parameters and perform augmented reality presentation, automatically adjusting the position of the moving center to load the device.
Significantly reduces user intervention and time during loading, provides a more user-friendly loading experience, improves efficiency and security of loading multiple devices, reduces manual steps, and enhances the seamlessness of loading .
Smart Images

Figure CN119011316A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to facilitating onboarding of network devices, and in particular to ultra-wideband (UWB) enabled devices and systems that use UWB technology to provide a more user-friendly way to onboard devices. Background Art
[0002] The Internet of Things (IoT) is an object with sensors, processing power, software and other technologies that connects and exchanges data with other devices and systems through the Internet or other communication networks. IoT is widely used in home automation, which can include lighting, heating, air conditioning, media, security systems and camera systems, such as in smart homes. In a smart home, IoT is loaded into a wireless local network covering the perimeter of the home space. Users can control and manage IoT in the wireless local network from a mobile device. Typically, users need to manually add new devices to the wireless local network and then configure it. For example, a wireless local network can be a wireless area network established based on network standards such as Matter, Zigbee, WiFi, IrDA, Thread, etc.
[0003] However, the existing onboarding process may be cumbersome for users. For example, a user may need to manually scan a QR code and / or enter a setup code to onboard a newly installed IoT device. The manual steps may increase user friction and may become time-consuming and impractical if many IoT devices need to be onboarded. Therefore, a more user-friendly way to onboard IoT devices is needed. Summary of the invention
[0004] Embodiments of the present disclosure provide a method for loading an electronic device into a wireless network. The method includes determining a trusted zone covered by the wireless network and detecting an electronic device near the trusted zone. In response to the electronic device being identified and being within the trusted zone, the electronic device is loaded into the wireless network.
[0005] In some embodiments, determining the trusted zone includes determining a fixed trusted zone or determining a mobile trusted zone.
[0006] In some embodiments, determining the fixed trusted zone includes receiving a first configuration parameter and storing the first configuration parameter in a memory; and the first configuration parameter includes at least one of: a perimeter-center distance from a fixed center, and an angle from the fixed center, or an angle at the fixed center.
[0007] In some embodiments, the fixed trusted region includes at least one of an area surrounding the fixed center or an area originating from the fixed center.
[0008] In some embodiments, receiving the first configuration parameter includes at least one of: receiving a perimeter-center distance and an angle at a fixed center via a user interface (UI) widget; receiving a perimeter-center distance and an angle at a fixed center on a displayed plan view covered by a wireless network via a UI widget; or receiving a perimeter-center distance and an angle to a fixed center on an augmented reality (AR) presentation of an area covered by a wireless network via a UI widget.
[0009] In some embodiments, the fixed center includes at least one of a hub, a router, a modem, a television, a set-top box, a smart speaker, or a range extender.
[0010] In some embodiments, determining the mobile trusted zone includes receiving a second configuration parameter and storing the second configuration parameter in a memory; and the second configuration parameter includes at least one of a perimeter-center distance from a center of movement or an angle from a center of movement.
[0011] In some embodiments, the mobile trusted zone includes at least one of an area surrounding the mobile center or an area originating from the mobile center.
[0012] In some embodiments, the mobile center includes a mobile device having an imaging device.
[0013] In some embodiments, detecting the electronic device includes detecting a beacon signal of the electronic device, the beacon signal including a device identification (ID) of the electronic device.
[0014] In some embodiments, the method further includes: comparing the device ID to a device information database; determining that the device is identified in response to locating a match with the device ID in the device information database; and determining that the device is not identified in response to not locating a match with the device ID in the device information database.
[0015] In some embodiments, in response to the electronic device not being recognized, a prompt is presented via a user interface (UI) widget to load the electronic device using at least one of Bluetooth, near field communication (NFC), or a QR code.
[0016] In some embodiments, the method further includes: in response to the electronic device being identified, initiating UWB ranging with the electronic device; and determining the position of the electronic device relative to the fixed center and the mobile center based on the UWB ranging and corresponding configuration parameters of each of the fixed center and the mobile center.
[0017] In some embodiments, in response to the electronic device being in at least one of a fixed trusted zone or a mobile trusted zone, a prompt is presented via a user interface (UI) widget requesting to onboard the electronic device.
[0018] In some embodiments, the electronic device is automatically onboarded in response to the electronic device being in at least one of the fixed trusted zone or the mobile trusted zone.
[0019] In some embodiments, in response to the electronic device not being in the fixed trusted zone or the mobile trusted zone, a prompt is presented via a user interface (UI) widget to adjust the position of the mobile center so that the electronic device is located in the mobile trusted zone.
[0020] In some embodiments, adjusting the position of the movement center includes at least one of: moving the movement center toward the electronic device, or changing the orientation of the movement center to face the electronic device.
[0021] In some embodiments, the method further includes, after presenting the prompt based on the UWB ranging and corresponding configuration parameters of the mobile trusted zone, initiating another UWB ranging with the electronic device to determine a location of the electronic device relative to the mobile center.
[0022] In some embodiments, in response to the electronic device being outside of the mobile trusted zone after the prompt, another prompt is presented via a user interface (UI) widget to onboard the electronic device using at least one of Bluetooth, near field communication (NFC), or a QR code.
[0023] In some embodiments, in response to the electronic device being in the mobile trusted zone, a prompt is presented via a UI widget requesting to load the electronic device.
[0024] In some embodiments, the electronic device is automatically onboarded in response to the electronic device being in the mobile trusted zone.
[0025] In some embodiments, the electronic device comprises an ultra-wideband (UWB) device.
[0026] Embodiments of the present disclosure also provide an electronic device, which may include an ultra-wideband (UWB) device. The electronic device includes a transceiver that can be used to perform UWB communications, and a memory for storing program instructions, device information, configuration parameters, angle of arrival, and distance from ranging operations. The electronic device also includes a processor, which is coupled to the transceiver and the memory. In some embodiments, the transceiver and the processor are integrated in a single system on a chip (SoC). The processor can be used to execute program instructions, which, when executed by the processor, cause the electronic device to perform operations to load another electronic device into a wireless local network. The operations include: determining a trusted area covered by the wireless network; detecting another electronic device near the trusted area; and in response to another electronic device being identified and inside the trusted area, loading another electronic device into the wireless network. In some embodiments, the electronic device includes wireless technologies other than UWB. For example, the electronic device may include Bluetooth, Thread, Wi-Fi, etc.
[0027] In some embodiments, determining the trusted zone includes determining a fixed trusted zone or determining a mobile trusted zone.
[0028] In some embodiments, determining the fixed trusted zone includes receiving a first configuration parameter and storing the first configuration parameter in a memory; and the first configuration parameter includes at least one of: a perimeter-center distance from a fixed center, and an angle from the fixed center, or an angle at the fixed center.
[0029] In some embodiments, the fixed trusted region includes at least one of an area surrounding the fixed center or an area originating from the fixed center.
[0030] In some embodiments, receiving the first configuration parameter includes at least one of: receiving a perimeter-center distance and an angle at a fixed center via a user interface (UI) widget; receiving a perimeter-center distance and an angle at a fixed center on a displayed plan view covered by a wireless network via a UI widget; or receiving a perimeter-center distance and an angle to a fixed center on an augmented reality (AR) presentation of an area covered by a wireless network via a UI widget.
[0031] In some embodiments, the fixed center includes at least one of a hub, a router, a modem, a television, a set-top box, a smart speaker, or a range extender.
[0032] In some embodiments, determining the mobile trusted zone includes receiving a second configuration parameter and storing the second configuration parameter in a memory; and the second configuration parameter includes at least one of a perimeter-center distance from a center of movement or an angle from a center of movement.
[0033] In some embodiments, the mobile trusted zone includes at least one of an area surrounding the mobile center or an area originating from the mobile center.
[0034] In some embodiments, the mobile center includes a mobile device having an imaging device.
[0035] Those skilled in the art will appreciate the scope of the present disclosure and understand additional aspects thereof after reading the following detailed description of the preferred embodiments and the related drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] The accompanying drawings incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.
[0037] Figure 1A An exemplary wireless communication system according to some aspects of the present disclosure is shown, which includes a wireless local network, a plurality of network devices in the wireless local network, and a mobile device communicatively coupled to the wireless local network.
[0038] Figure 1B A block diagram of an exemplary mobile device configured for UWB communications according to some aspects of the present disclosure is shown.
[0039] Figure 1C A block diagram of an exemplary network device configured for UWB communications according to some aspects of the present disclosure is shown.
[0040] Figure 1D A signaling diagram between two UWB devices according to some aspects of the present disclosure is shown.
[0041] Figure 1E Another signaling diagram between two UWB devices according to some aspects of the present disclosure is shown.
[0042] Figure 2A An exemplary environment for onboarding a network device according to some aspects of the present disclosure is shown.
[0043] Figure 2B-2D An exemplary fixed trusted region according to some aspects of the present disclosure is shown.
[0044] Figure 2E and 2F An exemplary mobile trusted zone according to some aspects of the present disclosure is shown.
[0045] Figures 3A-3C An exemplary display on a UI widget for configuring a trusted zone is shown in accordance with some aspects of the present disclosure.
[0046] Figure 4A An exemplary signaling diagram for onboarding a network device according to some aspects of the present disclosure is shown.
[0047] Figure 4B A method for loading a network device according to some aspects of the present disclosure is shown. Figure 4A The process flow corresponding to the signaling diagram.
[0048] Figures 5A-5D An exemplary display on a UI widget for loading a network device according to some aspects of the present disclosure is shown.
[0049] Figure 6 A flow chart of an exemplary method for onboarding a network device according to some aspects of the present disclosure is shown. DETAILED DESCRIPTION
[0050] The embodiments set forth below represent information necessary to enable those skilled in the art to practice the embodiments and to illustrate the best mode for practicing the embodiments. Upon reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize the applications of these concepts not specifically described herein. It should be understood that these concepts and applications fall within the scope of the present disclosure and the appended claims.
[0051] It should be understood that although the terms first, second, etc. can be used to describe various elements in this article, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the present disclosure, the first element can be referred to as the second element, and similarly, the second element can be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more items in the associated listed items.
[0052] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the present disclosure. As used herein, unless the context clearly indicates otherwise, the singular forms "a, an" and "the" are also intended to include plural forms. It should also be understood that when used herein, the terms "comprises, comprising" and / or include, including specify the presence of the features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their groups.
[0053] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the present disclosure belongs. It will be further understood that, unless explicitly defined herein, the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant technology, and will not be interpreted in an idealized or overly formal sense. In addition, throughout this specification and drawings, similar reference numerals represent similar features.
[0054] It should be understood that the blocks in each signaling diagram or flowchart and the combination of signaling diagrams or flowcharts can be executed by computer program instructions. Since the computer program instructions can be equipped in a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, the instructions executed by the processor of the computer or other programmable data processing device generate components for performing the functions described in the blocks in conjunction with each signaling diagram or flowchart. Since the computer program instructions can be stored in a computer-usable or computer-readable memory, which can be directed to a computer or other programmable data processing device to implement the functions in a specified manner, the instructions stored in the computer-usable or computer-readable memory can produce a product containing instructions for performing the functions described in conjunction with the blocks in each signaling diagram or flowchart. Since the computer program instructions can be equipped in a computer or other programmable data processing device, a process executed by a computer as a series of operating steps performed by the computer or other programmable data processing device is generated and the instructions for operating the computer or other programmable data processing device can provide steps for performing the functions described in conjunction with the blocks in each signaling diagram or flowchart.
[0055] Each box may represent a module, a fragment or a portion of a code containing one or more executable instructions for performing a specified logical function. In addition, it should be noted that in some alternative execution examples, the functions mentioned in the box may occur in different orders. For example, depending on the corresponding functions, two boxes shown in succession may be executed substantially simultaneously or in reverse order.
[0056] In the following, the embodiments are described in detail with reference to the accompanying drawings. In addition, although a communication system using ultra-wideband (UWB) is described in conjunction with the embodiments, as an example, the embodiments may also be applicable to other communication systems with similar technical backgrounds or features. For example, a communication system using Bluetooth or ZigBee may be included. In addition, the embodiments may be modified within such a range without significantly departing from the scope of the present disclosure, and such modifications may be applicable to other communication systems, as determined by a person of ordinary skill in the art.
[0057] UWB may refer to a short-range, high-rate wireless communication technology that uses a wide frequency band of several hundred MHz to several GHz or wider, low spectrum density, and short pulse width (e.g., 1nsec to 4nsec) in a baseband state. UWB may refer to the frequency band itself to which UWB communication is applied. UWB can achieve secure and accurate ranging between devices. Therefore, UWB achieves relative position estimation based on the distance and / or angle between two devices, or achieves accurate position estimation of a device based on the distance to a fixed device (whose position is known, also referred to as an anchor device). The present disclosure assumes that the user carries a device that can communicate via UWB (referred to as a "UWB-enabled user device" or simply a user device). In the present disclosure, a UWB device may be referred to as an IoT device equipped with UWB in a wireless network.
[0058] In home automation, IoT is controlled and managed in a wireless local network, which is usually a wireless area network. Wireless local networks are established based on certain Internet protocols (such as Matter, Zigbee, Thread, Bluetooth or Bluetooth Low Energy (BLE), WiFi, IrDA, etc.). For example, Matter is an emerging application layer connection standard designed to enable developers to increase compatibility between IoT in wireless local networks. Loading IoT devices, that is, adding new devices to an existing network and enabling these devices to be monitored and controlled through user interface (UI) widgets, is a basic feature of IoT networking standards. In order to meet security requirements, existing IoT network standards usually involve manual steps for loading new devices. For example, in Matter, the loading process usually requires manual scanning of the QR code of the IoT device that needs to be loaded. Other methods that bypass QR code scanning will still require the user to trigger device discovery, select the device and enter the loading payload (e.g., setup code). Near field communication (NFC) can simplify the process, but still requires physical access to the device. While users expect an increasingly seamless experience, these manual steps increase user friction and can become time-consuming and impractical if many IoT devices need to be onboarded at once.
[0059] Embodiments of the present disclosure provide a system and method that minimizes user input / intervention when loading a network device (e.g., an IoT device) and provides a more user-friendly and seamless loading experience. In the present disclosure, a trusted zone is set and configured by a user. The trusted zone provides the user with an option to simplify the loading process based on user preferences. For example, if the network device is located in a trusted zone, the system can automatically load the network device or only require the user's loading confirmation to load. The system can discover the network device, search for device information of the network device, and determine the location of the network device relative to the trusted zone based on UWB technology such as arrival angle and / or ranging. If the network device is identified but outside the trusted zone, the system can prompt the user to confirm the intention to load the network device. If the network device is not identified and is outside the trusted zone, the system can notify the user to load the network device by not using a trusted zone (e.g., a more conventional method, such as scanning a QR code, etc.). In various embodiments, the trusted zone includes a fixed trusted zone and a mobile trusted zone. The fixed trusted zone is located around or originates from a fixed center, such as a fixed UWB device (e.g., a network control device). For example, a fixed UWB device may include a home hub. A mobile trusted zone is located around or originates from a mobile hub, such as a mobile device. Depending on the location of the IoT, the system may resort to a fixed trusted zone and / or a mobile trusted zone for loading of various scenarios. A detailed description is provided in the present disclosure.
[0060] The disclosed systems and methods can minimize user intervention in the onboarding process by utilizing the location of the device to be onboarded (e.g., a network device) using UWB technology. In some embodiments, based on user configuration or preference, onboarding can be performed with minimal manual action (e.g., performed in the background or requiring only minimal user confirmation). The security of onboarding can be maintained by introducing manual steps only when necessary (or based on user preferences / configuration) and in a manner that creates less friction than existing onboarding methods. The location of the device can be determined in real time with the desired high accuracy and security by using UWB technology such as AoA and / or ranging (e.g., two-way ranging or TWR). The technical solution provided can significantly reduce the time and effort required to onboard multiple devices. In the present disclosure, the device to be onboarded may not need to be within close physical range of the user (i.e., a button press, NFC tap, or QR code scan may be required), and thus facilitates the onboarding of devices in hard-to-reach locations.
[0061] Figure 1A is a diagram illustrating an example communication system 100 including a wireless local network, a network device in the wireless local network, and a mobile device communicatively coupled to the wireless local network according to an example embodiment of the present disclosure.
[0062] The wireless local network 102 may include a network control device 104 and a plurality of network devices 106-1, 106-2, ..., 106-n. The wireless local network 102 may be any wireless area network, such as an automation network in a residential area, hospital, commercial building, factory, playground, school, etc. For ease of explanation, a home automation network is described as an example in the present disclosure. The network devices 106-1, ..., 106-n may include a plurality of network devices that allow a user to access, control and / or configure via a mobile device 108. In some embodiments, the network devices 106-1, ..., 106-n may include a plurality of IoT devices, which may be devices to be loaded equipped with a UWB transceiver. The IoT device (e.g., one or more of the network devices 106-1, ..., 106-n) may have the same IoT connection as the network control device 104 and may be programmed with a unique device identification number (ID). The mobile device 108 may be a "user device" capable of voice and / or data communication. The mobile device 108 may have built-in software and hardware that enables the mobile device 108 to communicate with the network control device 104, the network devices 106-1, ..., 106-n and / or the cloud network 110 via radio signals. In some embodiments, the mobile device 108 includes a UWB transceiver configured for UWB functionality and / or data transmission. The mobile device 108 may include a cellular phone, a smart phone, a laptop computer, a tablet computer, a personal digital assistant (PDA), a computing device, a wearable device (e.g., a smart watch, etc.), or any other mobile device with wireless connection capabilities. In some embodiments, the mobile device 108 may be equipped with UWB functionality and support loading through an application / UI widget. The mobile device 108 may include a display and may be used as a UI widget for configuring a trusted zone and any additional verification of the intended loading. In some embodiments, the mobile device 108 may act as the network control device 104 for loading. Although in Figure 1A Only a single mobile device 108 is shown, but one of ordinary skill in the art will appreciate that multiple mobile devices may be connected to network devices 106-1, ..., 106-n. A user may interact with network devices 106-1, ..., 106-n using an application, a web browser, a proprietary program, or any other program executed and operated by mobile device 108. In some embodiments, mobile device 108 may communicate directly with network devices 106-1, ..., 106-n (e.g., via communication link 114). In some embodiments, mobile device 108 may communicate with network devices 106-1, ..., 106-n via network control device 104 (e.g., via communication link 116) and / or cloud network 110 (e.g., via communication link 118).
[0063] The network control device 104 has its radio communication range formed by a radio communication scheme. The communication range may cover surroundings, such as residences, commercial buildings, hospitals, amusement parks, etc. For example, the network control device 104 may use one or more radio communication schemes to communicate data and signals with network devices 106-1, 106-2, ..., 106-n located within the radio communication range as indicated by the dotted line. The network control device 104 may also be communicatively connected to the cloud network 110 via a wired / wireless communication link 112, and communicatively connected to the mobile device 108 via a communication link 116. In some embodiments, the network control device 104 may use a wired communication protocol and / or a wireless communication protocol. The network control device 104 may obtain device information and device status information from the network devices 106-1, ..., 106-n located within the radio communication range, and provide the acquired information to the cloud network 110. The network control device 104 may also provide network control device information and network control device status information to the cloud network 110. In some embodiments, the network control device 104 has wireless communication capabilities and may include, but is not limited to, one or more of a gateway, a hub, a TV, a router, a modem, a range extender, a set-top box, a smart speaker, a mobile device (e.g., a tablet, a mobile phone), etc. In some embodiments, the network control device 104 may be a fixed device and may be equipped with UWB functionality and IoT connectivity (e.g., BLE, Thread). The network control device 104 may be used to establish a trusted zone and determine whether the network device is inside / outside the trusted zone. In some embodiments, the network control device 104 includes one or more home hubs. For example, the network control device 104 may include a gateway that allows data to flow from the wireless local network 102 to the cloud network 110 and vice versa. In some embodiments, the network control device 104 uses more than one Internet Protocol (IP) communication to connect the wireless local network 102 and the cloud network 110. In various embodiments, the network control device 104 communicates with IP such as Matter, Zigbee, Bluetooth or BLE, WiFi, IrDA, Thread, etc.
[0064] The network devices 106-1, ..., 106-n may transmit device information and device status information to the network control device 104 and / or the mobile device 108. The network devices 106-1, ..., 106-n may each have built-in software and hardware that enable each network device to communicate with the mobile device 108 and / or the network control device 104 via radio signals such as UWB, WiFi, BLE, NFC, etc. In some embodiments, each of the network devices 106-1, ..., 106-n includes a UWB transceiver configured for ranging and / or data transmission. For example, the network devices 106-1, ..., 106-n may include headphones (e.g., 106-1), light bulbs (e.g., 106-2), cameras (e.g., 106-3), augmented / virtual reality (AR / VR) devices (e.g., 106-4), televisions (e.g., 106-5), speakers (e.g., 106-6), ... and switches (e.g., 106-n).
[0065] The network control device 104 can also provide access to one or more external networks, such as a cloud network 110, the Internet, and / or other wide area networks, to the mobile device 108 and the network devices 106-1, ..., 106-n. The cloud network 110 may include a cloud infrastructure system that provides cloud services. In some embodiments, the services provided by the cloud network 110 may include registration and access control of the network devices 106-1, ..., 106-n. The cloud network 110 may include one or more computers, servers, and / or systems. In some embodiments, the cloud network 110 may include an application server that hosts applications, and users can order and use applications via a communication link 112. In some embodiments, wireless links 114 and 116 may each include a UWB communication interface. Wireless links 114 and 116 may also support other types of wireless connections, such as a Bluetooth communication interface, a Thread communication interface, a Wi-Fi communication interface, a cellular network connection (e.g., 4G, 5G) interface, a near field communication (NFC) interface, a ZigBee communication interface, or a combination thereof. In some embodiments, the cloud network 110 may be stored with device information (e.g., device keys, vendor information, device type, etc.) of the network devices 106-1, ..., 106-n. The device information of each network device may correspond to a unique device ID of the network device. In some embodiments, it is a device ID stored in a device information database, such as a vendor-specific database and / or a distributed certificate ledger (DCL). The network control device 104 and / or the mobile device 108 may access the database and / or the DCL.
[0066] Upon power-up or reset, the network devices 106-1, ..., 106-n may register with the cloud network 110 and be associated with a logical network within the wireless local network 102. It should be appreciated that the wireless local network 102 may include other components than those depicted, and that the specific number of components and / or their arrangement is not limited. Figure 1A The limitations of the description.
[0067] Figure 1B An example of a mobile device 108 is shown. The mobile device 108 may be a cellular phone, a smart phone, a laptop computer, a tablet computer, a personal digital assistant (PDA), a computing device, or any other mobile device with wireless connectivity. In some embodiments, the mobile device 108 includes a processor 103, a digital signal processor (DSP) 105, a transceiver 107, an antenna 117, a memory 109, an input device 111, an output device 113, and a bus 115. The hardware components of the mobile device 108 may be communicatively coupled to the bus 115. In some embodiments, the bus 115 may be used for communication between the cores of the processor 103 and / or with the memory 109. The processor 103 may include one or more general-purpose processors and / or one or more special-purpose processors (e.g., a digital signal processing chip, a graphics acceleration processor, etc.). The processor 103 may process wireless signals 119 received by the transceiver 107, such as ranging signals / data from UWB communications. The input device 111 may include a camera, a mouse, a keyboard, a touch-sensitive screen / display, a touchpad, a keyboard, etc. Output device 113 may include a display, printer, etc. In some embodiments, a user may load an application that automatically opens a camera with a field of view (FOV). In some embodiments, a user may receive an AR element / indicator on output device 113 (e.g., a UI widget or display) and may enter a user response on input device 111 (e.g., a user interface widget or display).
[0068] The mobile device 108 may include a transceiver 107 communicatively coupled to the bus 115. The transceiver 107, i.e., a UWB transceiver, may be configured to transmit and receive wireless signals 119 via an antenna 117. The wireless signals 119 may be transmitted / received via a wireless network. In some embodiments, the wireless network may be any wireless network, such as a wireless local network (e.g., wireless local network 102), such as WiFi, a personal access network (PAN), such as Matter, Thread, or Or cellular network (e.g., 4G, 5G). The transceiver 107 can be configured to receive signals 119 from a network control device (e.g., 104), a network device (e.g., 106-1, ..., 106-n), a cloud network (e.g., 110), etc. via an antenna 117. The mobile device 108 can also be configured to decode and / or decrypt various signals received from the network control device 104, the network device 106-1, ..., 106-n, the cloud network 110, etc. via the DSP 105 and / or the processor 103.
[0069] The memory 109 may include one or more non-transitory storage devices, which may include local and / or network accessible storage devices, disk drives, drive arrays, optical storage devices, solid-state storage devices, such as random access memory ("RAM") and / or read-only memory ("ROM"), programmable ROM, flash-updatable ROM, etc. Such storage devices may be configured to implement any suitable data storage, including but not limited to various file systems, database structures, etc. In some embodiments, the memory 109 may store with a device database that includes device information (e.g., device identification (ID), device key, vendor information, device type, etc.) for one or more of the network devices 106-1, ..., 106-n.
[0070] In various embodiments, the functions / operations may be stored as one or more instructions or codes in the memory 109, such as on a computer-readable storage medium such as RAM, ROM, FLASH, or a disk drive, and executed by the processor 103 or the DSP 105. The mobile device 108 may also include software components (e.g., located in the memory 109), including, for example, an operating system, device drivers, executable libraries, and / or other executable codes, such as one or more applications. The application may include a computer program that is stored in the memory 109 and executed by the processor 103 and / or the DSP 105 to implement various functions under the control of the operating system. The computer program may have been pre-packaged with the mobile device 108, or may have been downloaded by the user to the memory 109 of the mobile device 108. Some mobile applications may be user-interactive applications with more interactions, such as applications for loading network devices and AR applications for displaying network devices in the background, while some other mobile applications may be user-interactive less in nature.
[0071] Figure 1CAn example of a network device 106 is shown, which may represent any of network devices 106-1, ..., 106-n. Network device 106 may include a transceiver 127, such as a UWB transceiver, and an antenna 131 (communicatively coupled to transceiver 127) for wireless communication with mobile device 108 and / or network control device 104. Depending on the type, network device 106 may optionally include a processor 123, a memory 129, and a bus 125.
[0072] The transceiver 127 may be used to transmit and receive wireless signals 139 via the antenna 131. The wireless signals 139 may be transmitted / received via a wireless network. In some embodiments, the wireless network may be any wireless network, such as a wireless local network (e.g., wireless local network 102), such as WiFi, a personal access network (PAN), such as Matter, or Thread, or cellular network (e.g., 4G, 5G). The transceiver 127 can be configured to receive wireless signals 139 from a network control device (e.g., 104), a mobile device (e.g., 108), etc. via the antenna 127. Optionally, the network device 106 can include a DSP (not shown) for decoding and / or decrypting various received signals 139.
[0073] Optionally, the network device 106 may include a processor 123 and a memory 129. The processor 123 may include one or more general-purpose processors and / or one or more special-purpose processors similar to the processor 103. The memory 129 may include one or more non-transitory storage devices similar to the memory 109. Optionally, the network device 106 may include a bus 125 that communicatively couples the processor 123, the transceiver 127, and the memory 129 so that the processor 123 can execute instructions stored in the memory 129 and can process signals 139 received by the transceiver 127, such as ranging signals / data from UWB communications. In some embodiments, the memory 129 may store location information of one or more network devices and configuration parameters of a trusted zone. For example, the memory 129 may store location information of another network device, a boundary / perimeter of a trusted zone based on configuration parameters, location information of the mobile device 108, and the like.
[0074] The user can use, for example, an onboarding application with an AR feature to onboard the network device 106 to the wireless local network 102 through the mobile device 108. In some embodiments, the AR feature shows the network device 106 in an environment for the user to confirm the onboarding, shows an environment that allows the user to configure a trusted zone, etc. In order to onboard the network device, the network control device 104 and / or the mobile device 108 can perform UWB communication with the network device 106 to obtain the location information of the network device 106. Figure 1D UWB communication between UWB device 1 and UWB device 2 using single-sided two-way ranging (SS TWR) is shown. In some embodiments, UWB device 1 may represent a network control device 104 or a mobile device 108, and UWB device 2 may represent a network device 106. In some embodiments, UWB device 1 is an initiator of TWR, and UWB device 2 is a responder of TWR.
[0075] UWB device 1 may discover UWB device 2 using out-of-band (OOB) technology such as BLE, and may establish an OOB (e.g., BLE) channel for initial characterization 156 (e.g., negotiation and service data exchange). In some embodiments, UWB device 1 discovers UWB device 2 and establishes an OOB channel using a device ID transmitted by UWB device 2 via BLE. After the initial characterization, UWB devices 1 and 2 may begin UWB communication, such as UWB ranging such as SS TWR. UWB device 1 may transmit a poll 158 to UWB device 2. UWB device 2 may determine an arrival time 160 and reply at a time T 答复 Then, a response frame 162 is transmitted to the UWB device 1. The response frame 162 may include, for example, the reply time T of the UWB device 2. 答复 The UWB device 1 may determine the time between the transmission of the poll 158 and the reception of the response frame 162 as T 循环 , and the time of flight (TOF) can be calculated as (T 循环 -T 答复 ) / 2. UWB device 1 may calculate the distance D between UWB device 1 and UWB device 2 as D=TOF×speed of light. In some embodiments, UWB device 1 further determines the angle of arrival (AoA) based on the phase change between polling 158 and response frame 162 detected from an antenna (e.g., antenna 131) of UWB device 1. That is, UWB device 1 may determine the relative position of UWB device 2 (e.g., relative position relative to UWB device 1) based on the distance D and the angle of arrival. In some embodiments, response frame 162 further includes a device ID of UWB device 2.
[0076] Figure 1EAnother UWB communication between UWB device 1 and UWB device 2 using dual-side two-way ranging (DS TWR) is shown. Figure 1D Unlike the SS TWR shown in , in some embodiments, UWB device 1 and UWB device 2 may perform DS TWR, such as UWB TWR 170, and determine TWR distance and arrival angle at 172 and 174, respectively. It should also be noted that other ranging methods may also be used to determine the distance and / or arrival angle between UWB devices 1 and 2, such as one-way ranging (OWR). The specific ranging method used between UWB devices 1 and 2 is not limited by the embodiments of the present disclosure.
[0077] Figure 2A An operating environment 200 is shown according to some embodiments, where a network device is in the vicinity of a network control device and can be authenticated by the network control device and / or the mobile device for onboarding. Figure 2A As shown in FIG. 2 , the operating environment 200 may include a network control device 206, a mobile device 210, a device information database 202, and a network device 204. The network control device 206 may be an example of the network control device 104, the network device 204 may be an example of the network device 106, and the mobile device 210 may be an example of the mobile device 108. The device information database 202 may be stored in a cloud network (e.g., the cloud network 110) that is communicatively coupled to the network control device 206 and the mobile device 210. Return to reference Figure 1A , the network control device 206 can communicate with the mobile device 210 via the communication link 116, and can communicate with the device information database 202 via the communication link 112. The network device 204 can communicate with the network control device 206 via the communication link 212, and can communicate with the mobile device 210 via the communication link 114. The mobile device 210 can communicate with the device information database 202 via the communication link 118. In some embodiments, the communication links 114, 116, and 212 can each include various IP protocols, such as Matter, Zigbee, Bluetooth or BLE, WiFi, IrDA, Thread, etc.
[0078] A trusted zone may be set near the network control device 206 and / or the mobile device 219. In an example, the network control device 206 may be a fixed center whose location does not change. The fixed trusted zone 208 may be defined around or originate from a fixed center, such as the network control device 206. The mobile device 210 may be a mobile center, such as a mobile center whose location may change when a user carrying the mobile device 210 moves. The mobile trusted zone 214 may be defined around or originate from a mobile center, such as the mobile device 210. In some embodiments, the trusted zone may include one or more of the fixed trusted zone 208 and the mobile trusted zone 214, such as both. In some embodiments, the trusted zone may include one of the fixed trusted zone 208 and the mobile trusted zone 214. In an example, the trusted zone may include only the mobile trusted zone 214, such as when the network control device 206 is not available. In various embodiments, the mobile device 210 may function independently or as a supplemental component to the network control device 206. In various embodiments, mobile device 210 may detect and verify loading of network device 204 with or without the presence of network control device 206 .
[0079] In some embodiments, if the network control device 206 and / or the mobile device 210 detects a nearby network device 204, the network control device 206 and / or the mobile device 210 may check the device information of the network device 204 by looking up the device ID of the network device 204 in the device information database 202. If a match with the device ID can be found in the device information database 202, the network control device 206 and / or the mobile device 210 may determine that the network device 204 is identified. The network control device 206 may initiate UWB ranging to determine the location of the network device 204 by determining the distance D and AoA of the network device 204 relative to the network control device 206. If the network device 204 is located in the fixed trusted zone 208, the network control device 206 may onboard the network device 204. If the network device 204 is located outside the fixed trusted zone 208, the network control device 206 and / or the mobile device 210 may determine whether the network device 204 is located in the mobile trusted zone 214 and confirm the user's intention to onboard. In some embodiments, the user's intention to onboard is confirmed by prompting the user to bring network device 204 into mobile trusted zone 214. If the user confirms onboarding by positioning network device 204 in mobile trusted zone 214, network control device 206 and / or mobile device 210 may onboard network device 204. Details of the operation are described below. Figure 2B-2F Examples of a fixed trusted zone 208 and a mobile trusted zone 214 are shown.
[0080] Figure 2B-2D is an example of a fixed trusted zone 208 according to some embodiments. Figure 2B As shown in , the fixed trusted zone 208 may have a circular shape centered around the network control device 206 (e.g., a fixed center). The fixed trusted zone 208 may have a perimeter-to-center distance of r1, such as a radius, which may be a suitable distance configured by the user. In some embodiments, the “perimeter-to-center” distance refers to any point on the perimeter to the geometric center of the network control device 206 or the mobile device 210. Figure 2C As shown in , the fixed trusted zone 208 may have a sector shape originating from the network control device 206. The sector shape may have a radius r2 and an inner angle θ. In some embodiments, the sector shape, such as the radius r2 and the inner angle θ, may be configured by a user. Figure 2D Another example of a fixed trusted zone 208 is shown, which is formed by merging the fixed trusted zones of more than one network control device. Figure 2D , two network control devices 206-1 and 206-2 are positioned close enough to each other so that the fixed trusted zones (or fixed trusted sub-zones) centered thereon merge (or at least partially overlap) to form a fixed trusted zone 208. In some embodiments, the fixed trusted sub-zone around the network control device 206-1 may have a perimeter-to-center distance d1, and the fixed trusted sub-zone around the network control device 206-2 may have a perimeter-to-center distance d2. In some embodiments, d1 and d2 may be configured by a user. In various embodiments, d1 and d2 may be the same or may be different, and may remain constant or may vary.
[0081] Figure 2E and 2F is an example of a mobile trusted zone 214 according to some embodiments. Figure 2E As shown in , mobile trusted zone 214 may have a circular shape centered around mobile device 210 (eg, mobile center). Mobile trusted zone 214 may have a perimeter-to-center distance, such as a radius, of r3, which may be a suitable distance configured by the user. Figure 2F As shown in , the mobile trusted zone 214 can have a sector shape originating from the network control device 206. The sector shape can have a radius r4 and an inner angle α. In some embodiments, the sector shape, such as the radius r4 and the inner angle α, can be configured by the user. In some embodiments, the sector shape can originate from the front of the mobile device 210, rather than the geometric center of the mobile device 210. The mobile trusted zone 214 allows the user to bring the mobile device 210 close to the network device 204, or turn the mobile device 210 so that the network device 204 can be located in the mobile trusted zone 214. In some embodiments, the mobile trusted zone 214 is used to confirm the user's intention to load the network device 204.
[0082] In various embodiments, the fixed trusted zone 208 and / or the mobile trusted zone 214 of the present disclosure may have any suitable shape, such as circular, rectangular, square, triangular, sector, regular, irregular, etc. The fixed trusted zone 208 and / or the mobile trusted zone 214 may completely or partially surround the corresponding center (e.g., the network control device 206 or the mobile device 210), or originate from the corresponding center. The embodiments are not intended to limit the scope of the present disclosure.
[0083] Figures 3A-3C An example of a user configuring a trusted zone on a UI widget according to some embodiments is shown. For example, a user can configure a trusted zone on the display / screen of mobile device 210 and can set any security preferences for loading network devices. In some embodiments, a user can configure a trusted zone before loading any network device and can modify the configuration at any desired time. For example, a user can configure a trusted zone only once and then use the configuration to load various network devices.
[0084] like Figure 3A As shown in , according to some embodiments, the user may choose to configure a fixed trusted zone using a mobile device 210 enabled with a UWB function having an AR function. In some embodiments, the mobile device 210 is also equipped with other ranging technologies, such as light detection and ranging (LiDAR), which may be used with or without UWB in ranging. In this example, the user may turn on an imaging device, such as a camera, on the mobile device 210 and turn the mobile device 210 toward a network control device, such as a TV 302. The mobile device 210 may display the TV 302 and any other objects in the field of view (FOV), such as furniture (e.g., a bench 304 and tableware 306), on the UI widget 310. In some embodiments, the mobile device 210 may display a fixed trusted zone 308 as a configurable colored area originating from the geometric center of the TV 302. In some embodiments, the mobile device 210 may display a message on the UI widget 310 to prompt the user to configure the fixed trusted zone 308. For example, although not shown, the mobile device 210 may display "Please drag the colored area to set the trusted zone size. You can change the radius and angle." The user may use a fingertip to change the radius and angle of the fixed trusted zone 308 so that the fixed trusted zone 308 can cover a desired area. The television 302 may determine the perimeter of the fixed trusted zone 308 based on the user's input. The television 302 (e.g., a network control device) and / or the mobile device 210 may record / store the radius and angle as configuration parameters, and may use the configuration parameters to determine the location of the network device to be loaded relative to the television 302 and / or the mobile device 210 (e.g., a fixed center and / or a mobile center).
[0085] like Figure 3BAs shown in , according to some embodiments, the user may choose to configure another fixed trusted zone using a mobile device 210 enabled with a UWB function having an AR function. The user may turn on an imaging device, such as a camera, on the mobile device 210 and turn the mobile device 210 toward the area the user wants to configure. The UI widget 310 may show any object in the FOV (e.g., a wall, floor, furniture) and receive user input as a hand-drawn on the UI widget 310. For example, although not shown, the mobile device 210 may display "Please draw a line through the home to set the trusted zone size". The user may draw a line 312 on the UI widget 310 as the boundary / periphery of the fixed trusted zone. In some embodiments, the line 312 may be straight and / or curved and may be editable to change its length and orientation. The network control device (not shown) may determine the perimeter of the fixed trusted zone based on the location of the mobile device 210 and the user's input using a suitable algorithm such as triangulation. The network control device and / or mobile device 210 can record / store the length and / or orientation of line 312 as configuration parameters, and the configuration parameters can be used to determine the position of the network device to be loaded relative to the network control device and / or mobile device 210 (e.g., a fixed center and / or a mobile center).
[0086] like Figure 3C As shown in , according to some embodiments, a user can choose to configure another fixed trusted zone using the mobile device 210 by drawing / selecting on a plan view of the area that the user wants to configure. The user can open a plan view 314 (e.g., pre-stored in the mobile device 210 and / or the cloud network 110), which shows a plan view of the area that the user wants to configure. The user can use a fingertip to tap or draw one or more fixed trusted zones 316 and 318 around the corresponding network control device. The network control device (not shown) can determine the perimeter of the fixed trusted zone based on the size provided by the plan view 314 and the user input. The network control device and / or the mobile device 210 can record / store any distance (e.g., radius) and angle as configuration parameters, and the configuration parameters can be used to determine the position of the network device to be loaded relative to the network control device and / or the mobile device 210 (e.g., fixed center and / or mobile center).
[0087] In some embodiments, although not shown, the fixed trusted zone may not be around or originate from a fixed center (e.g., a network control device). For example, the fixed trusted zone may be defined as being near the fixed center, and the user may determine the fixed trusted zone by entering / customizing the area on a UI widget of the mobile device using a fingertip, similar to Figures 3A-3CBased on the user input, the network control device may determine the fixed trusted zone using a suitable algorithm such as triangulation based on the location of the mobile device 210 and the user input. In various embodiments, the network control device may use Figures 3A-3C Any of the configuration methods shown in , such as AR assistance, hand drawing, and / or using a floor plan, to determine a fixed trust region.
[0088] In some embodiments, although not shown, the user may also input a radius and angle for moving the trusted zone (refer to Figure 2E and 2F The network control device and / or the mobile device 210 may record / store the radius and angle as configuration parameters, and may use the configuration parameters to determine the position of the network device to be loaded relative to the mobile device 210 (eg, a fixed center and / or a mobile center).
[0089] In some embodiments, Figure 3C As shown in , after the user enters the configuration parameters, the mobile device 210 may notify the user that "your trusted zone setup is complete". In some embodiments, the mobile device 210 may also request the user's consent to load the network device without further interaction. For example, Figure 3C As shown in , mobile device 210 may display on UI widget 310 “Confirm that any supported devices in the trusted zone will be automatically added to your home network.” The user may select “Yes” to confirm the automatic loading, or select “No” to require user confirmation.
[0090] Figure 4A A signaling diagram between the device information database 202, the mobile device 210, the network control device 206, and the network device 204 is shown according to some embodiments. Figure 4B Shows Figure 4A The process flow of the operations in . Figures 5A-5D 2 shows an example of a display on a UI widget 310 of a mobile device 210 when loading a network device 204 according to some embodiments. For ease of illustration, Figure 4A , 4B Described together with 5A-5D.
[0091] At step 402, a trusted zone is determined by the network control device 206 and / or the mobile device 210. In some embodiments, the trusted zone includes a fixed trusted zone (e.g., 208) and / or a mobile trusted zone (e.g., 214). A user can configure the area / coverage on the mobile device 210, and the configuration parameters of the trusted zone can be stored on the network control device 206, the mobile device 210, and / or the cloud network 110. The details of the trusted zone and the configuration process can be referred to Figures 2A-2D The descriptions of 3A-3C are not repeated here.
[0092] At step 404, a network device 204, such as an IoT device to be onboarded, may be powered on and may announce its presence by transmitting a BLE beacon (and / or by other wireless technology) containing its unique device ID. The device ID may contain device information, such as vendor information, product information, and a unique identifier field.
[0093] At step 406 , the network control device 206 , such as a home hub, may detect the device ID of the network device 204 by scanning the BLE beacons.
[0094] At step 408, the network control device 206 may check the device ID in the device information database 202, which may include a direct communication link (DCL) or a vendor-specific database. If no match for the device ID is found in the device information database 202, the network control device 206 may determine that the device ID (e.g., and the network device 204) is not recognized.
[0095] If the device ID is not recognized, then in step 410, network device 206 may trigger mobile device 210 to prompt the user to begin onboarding network device 204 using existing IoT standard onboarding processes, such as requesting manual verification of the onboarding payload (in the case of Matter, scanning a QR code).
[0096] If the device ID is recognized, then at step 412, the network control device 206 may trigger the mobile device 210 to notify the user of the network device 204, such as that a specific product from a specific supplier has been found. For example, the mobile device 210 may display the device information of the network device 204 on a UI widget (e.g., 310) for the user to view. Figure 5A As shown in , the network device 204 can be a smart speaker, and the mobile device 210 can notify the user that a "new smart speaker has been found."
[0097] At step 414 , the network control device 206 and the network device 204 may then negotiate a session key via BLE (and / or other wireless technologies) using an anonymous authenticated key negotiation scheme.
[0098] At step 416, the network control device 206 and the network device 204 may use the negotiated session key and ranging session parameters to start a secure UWB ranging session using TWR and / or AoA. In some embodiments, the network control device 206 may determine the distance and angle between the network control device 206 and the network device 204. In some embodiments, the network control device 206 is the initiator of the UWB ranging session and the network device 204 is the responder. Based on the results of the ranging session, the network control device 206 may determine the relative position between the fixed trusted zone 208 and the network device 204 based on the results of the ranging session and the configuration parameters of the fixed trusted zone 208.
[0099] If it is determined that the network device 204 is outside the fixed trusted zone 208, then in step 418, the network control device 206 may trigger the mobile device 210 to prompt the user via the UI widget 310 to adjust the position of the mobile device 210, for example, to bring the mobile device 210 closer to the network device 204 so that the network device 204 can be within the mobile trusted zone 214. In some embodiments, the mobile device 210 may display guidance and / or instructions on the UI widget 310 to prompt the user to move / rotate the mobile device 210 in a certain direction. In some embodiments, the instructions may prompt the user to move the mobile device 210 in a certain direction by a determined distance. In some embodiments, additionally or alternatively, the instructions may prompt the user to rotate the mobile device 210 by a determined angle so that the mobile device 210 can point to the network device 204. Return to reference Figure 2E and 2F If the user intends to load the network device 204, the user can adjust the position of the mobile device 210 so that the network device 204 is within the radius of r3 (for Figure 2E ) or within the radius and angle α of r4 (for Figure 2F ). In the example, Figure 5B As shown in , the mobile device 210 can inform the user that "the smart speaker is outside the trusted zone" and "If you want to continue adding this device to the home network, please center the smart speaker within the blue circle." In order to center the smart speaker, the user may need to move and / or rotate the mobile device 210 so that the smart speaker can be located in the mobile trusted zone 214 (e.g., Figure 2E and 2F In some embodiments, even if it is determined that network device 204 is located within fixed trusted zone 208, the device manufacturer may enforce the use of mobile trusted zone 214 as a second step.
[0100] In step 420 , the mobile device 210 and the network device 204 may negotiate a session key using an anonymous authenticated key negotiation scheme via BLE (and / or other wireless technologies).
[0101] In step 422, the mobile device 210 and the network device 204 may start a secure UWB ranging session using TWR and / or AoA. In some embodiments, the mobile device 210 may determine the distance and angle between the mobile device 210 and the network device 204. In some embodiments, the mobile device 210 is the initiator of the UWB ranging session and the network device 204 is the responder. Based on the results of the ranging session, the mobile device 210 may determine the relative position between the mobile trusted zone 214 and the network device 204 based on the results of the ranging session and the configuration parameters of the mobile trusted zone 214. Step 422 may be used to verify whether the user actually intends to load the pointed network device 204, rather than acting as an intermediary to simulate the device to be loaded. If the verification fails (e.g., the distance is too large, so that the network device 204 is outside the mobile trusted zone 214), the operation proceeds to step 410, which prompts the user to use an alternative loading process on the UI widget 310, such as scanning a QR code, to load the network device 204.
[0102] If the network control device 206 and / or the mobile device 210 determines that the network device 204 is within the mobile trusted zone 214 or the authentication is successful, then in step 424, the network control device 206 may trigger the mobile device 210 to prompt the user for confirmation in the notification menu on the UI widget 310 to notify the user that the network device 204 can be added / loaded. In some embodiments, the mobile device 210 may present the configuration options and confirmation to the user on the UI widget 310. For example, Figure 5C As shown in , the mobile device 210 may display “Do you want to add a smart speaker to your bedroom?” on the UI widget 310. In some embodiments, if the user has provided consent for automatic loading without confirmation when setting up the trusted zone in step 402, the confirmation step may be optional.
[0103] In step 426 , the network control device 206 and / or the mobile device 210 may load the network device 204 into the local network.
[0104] In step 428, after the loading is complete, the network control device 206 may trigger the mobile device 210 to notify the user that the network device 204 has been added. Figure 5D As shown in , the mobile device 210 can display “A new smart speaker has been set up in your bedroom” on the UI widget 310.
[0105] Figure 66 is a flow chart of a method 600 for a network control device and / or a mobile device to facilitate loading of a UWB device according to some embodiments of the present disclosure. The method 600 is merely an example and is not intended to limit the present disclosure beyond what is explicitly recited in the claims. Additional operations may be provided before, during, and after the method 600, and some of the operations described may be replaced, deleted, or moved around for additional embodiments of the method 600. For ease of illustration, the method 600 is described in conjunction with Figures 2A-2F , 3A-3C, 4A and 4B Description Figure 6 .
[0106] At step 602, a trusted zone covered by a wireless network is determined. Figures 2A-2F 3A-3C , the mobile device 210 may receive user input via the network control device 206 and / or the mobile device 210 to configure the trusted zone.
[0107] At step 604, a UWB device is detected near the trusted zone. Figure 2A , 4A 4B , the network control device 206 can detect the device ID of the network device 204 through the BLE advertisement, and can determine the location of the network device 204 based on the configuration parameters of the UWB ranging and the trusted zone.
[0108] At step 606, if the UWB device is identified and is within the trusted zone, the UWB device is loaded into the wireless network. Figure 2A , 4A 4B , if the network control device 206 finds a match for the device ID in the device information database and determines that the network device 204 is located in the trusted zone, the network control device 206 may load the network device 204 .
[0109] Those skilled in the art will recognize improvements and modifications to the preferred embodiments of the present disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein and the claims below.
Claims
1. A method for loading an electronic device in a wireless network, wherein include: determining a trusted zone covered by the wireless network; detecting the electronic device in proximity to the trusted zone; as well as In response to the electronic device being identified and within the trusted zone, the electronic device is onboarded into the wireless network. 2 . The method of claim 1 , wherein determining the trusted zone comprises determining a fixed trusted zone or determining a mobile trusted zone.
3. The method according to claim 2, in: The determining the fixed trusted zone comprises receiving a first configuration parameter and storing the first configuration parameter in a memory; and The first configuration parameter comprises at least one of: a perimeter-center distance from a fixed center, and an angle to or at the fixed center. 4 . The method of claim 3 , wherein the fixed trusted region comprises at least one of a region surrounding the fixed center or a region originating from the fixed center.
5. The method of claim 3, wherein the receiving the first configuration parameter comprises at least one of the following: receiving the perimeter-center distance and the angle at the fixed center via a user interface (UI) widget; receiving, via the UI widget, the perimeter-center distance and the angle at the fixed center on a displayed plan view covered by the wireless network; or A perimeter-center distance and the angle from the fixed center are received via the UI widget on an augmented reality (AR) representation of an area covered by the wireless network.
6. The method of claim 3, wherein the fixed center comprises at least one of a hub, a router, a modem, a television, a set-top box, a smart speaker, or a range extender.
7. The method according to claim 2, in: The determining the mobile trusted zone comprises receiving a second configuration parameter and storing the second configuration parameter in a memory; and The second configuration parameter includes at least one of a perimeter-center distance from a center of movement or an angle from the center of movement.
8. The method of claim 7, wherein the mobile trusted zone comprises at least one of an area surrounding the mobile center or an area originating from the mobile center.
9. The method of claim 7, wherein the mobile center comprises a mobile device having an imaging device. 10 . The method of claim 1 , wherein the detecting the electronic device comprises detecting a beacon signal of the electronic device, the beacon signal comprising a device identification (ID) of the electronic device.
11. The method according to claim 10, further comprising: include: comparing the device ID to a device information database; In response to locating a match with the device ID in the device information database, determining that the device is identified; as well as In response to not locating a match to the device ID in the device information database, it is determined that the device is not identified. 12 . The method of claim 1 , wherein in response to the electronic device not being recognized, presenting a prompt to load the electronic device using at least one of Bluetooth, near field communication (NFC), or a QR code via a user interface (UI) widget.
13. The method according to claim 2, further comprising: include: In response to the electronic device being identified, initiating ultra-wideband (UWB) ranging with the electronic device; as well as The position of the electronic device relative to the fixed center and the mobile center is determined based on the UWB ranging and corresponding configuration parameters of each of the fixed center and the mobile center. 14 . The method of claim 13 , in response to the electronic device being in at least one of the fixed trusted zone or the mobile trusted zone, presenting a prompt requesting to load the electronic device via a user interface (UI) widget.
15. The method of claim 13, automatically loading the electronic device in response to the electronic device being in at least one of the fixed trusted zone or the mobile trusted zone.
16. The method according to claim 13, in response to the electronic device not being in the fixed trusted zone or the mobile trusted zone, presenting a prompt to adjust the position of the mobile center so that the electronic device is located in the mobile trusted zone via a user interface (UI) widget. 17 . The method of claim 16 , wherein the adjusting the position of the movement center comprises at least one of: moving the movement center toward the electronic device, or changing the orientation of the movement center to face the electronic device.
18. The method of claim 16, further comprising, after presenting the prompt based on the UWB ranging and corresponding configuration parameters of the mobile trusted zone, initiating another UWB ranging with the electronic device to determine a location of the electronic device relative to the mobile center.
19. A method according to claim 18, wherein in response to the electronic device being outside the mobile trusted zone after the prompt, another prompt is presented via a user interface (UI) widget to load the electronic device using at least one of Bluetooth, near field communication (NFC), or a QR code.
20. The method of claim 16, in response to the electronic device being in the mobile trusted zone, presenting a prompt requesting to load the electronic device via the UI widget.
21. The method of claim 16, automatically loading the electronic device in response to the electronic device being in the mobile trusted zone.
22. The method of claim 1, wherein the electronic device comprises an ultra-wideband (UWB) device.
23. An electronic device, include: a transceiver capable of performing ultra-wideband (UWB) communications; a memory for storing program instructions, device information, configuration parameters, angles of arrival, and distances from ranging operations; as well as a processor coupled to the transceiver and the memory, wherein the processor is operable to execute the program instructions, which when executed by the processor cause the electronic device to perform the following operations to load another electronic device into the wireless local network: determining a trusted zone covered by the wireless network; detecting the other electronic device in proximity to the trusted zone; as well as In response to the other electronic device being identified and within the trusted zone, the other electronic device is onboarded into the wireless network.
24. The electronic device of claim 23, wherein determining the trusted zone comprises determining a fixed trusted zone or determining a mobile trusted zone.
25. The electronic device according to claim 24, in: The determining the fixed trusted zone comprises receiving a first configuration parameter and storing the first configuration parameter in a memory; and The first configuration parameter comprises at least one of: a perimeter-center distance from a fixed center, and an angle to or at the fixed center.
26. The electronic device of claim 25, wherein the fixed trusted zone comprises at least one of an area surrounding the fixed center or an area originating from the fixed center.
27. The electronic device of claim 25, wherein the receiving the first configuration parameter comprises at least one of the following: receiving the perimeter-center distance and the angle at the fixed center via a user interface (UI) widget; receiving, via the UI widget, the perimeter-center distance and the angle at the fixed center on a displayed plan view covered by the wireless network; or A perimeter-center distance and the angle from the fixed center are received via the UI widget on an augmented reality (AR) representation of an area covered by the wireless network.
28. The electronic device of claim 25, wherein the fixed center comprises at least one of a hub, a router, a modem, a television, a set-top box, a smart speaker, or a range extender.
29. The electronic device according to claim 24, in: The determining the mobile trusted zone comprises receiving a second configuration parameter and storing the second configuration parameter in a memory; and The second configuration parameter includes at least one of a perimeter-center distance from a center of movement or an angle from the center of movement.
30. The electronic device of claim 29, wherein the mobile trusted zone comprises at least one of an area surrounding the mobile center or an area originating from the mobile center.
31. The electronic device of claim 29, wherein the mobile center comprises a mobile device having an imaging device.
32. The electronic device of claim 23, comprising a UWB device.
Citation Information
Cited By
Medical sign-identification tag
WO2026074549A1
