Connection request handling

Abstract

A method for connection request handling in a network is provided. The method is performed by a first node of a network. The first node is deployed in an emergency response event. The method includes, in response to obtaining the first input, changing a state of the first node from a first state to a second state. The method includes receiving, from a first wireless device deployed in an emergency response event, a first request for information indicating a state of a first node. The method includes initiating a transmission of a first response to a first wireless device. The method includes, in response to receiving the second request from the first wireless device, initiating a one-to-one connection with the first wireless device, and changing the state of the first node from the second state to the first state.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to methods of handling connection requests in a network, and nodes and devices configured to operate according to these methods. BACKGROUND

[0002] Emergency services, such as fire services, are organisations that ensure public safety, security and health by resolving and mitigating different emergency situations. As such, emergency services need to make use of all advantages possible when handling emergency response events. This is particularly important when responding to increasingly complex events. Indeed, emergency response events can involve a large number of people, including responders and members of the public, and responders are typically equipped with specialist equipment that must be carefully monitored and maintained to provide safety for the responders. For example, fire services often deal with toxic environments created by flammable materials that result in smoke, lack of oxygen, increased temperature, toxic gases and intense air flow. To cope with some of these risks, firefighters carry breathing apparatus (BA). The proper management of this specialist equipment can mean the difference between a successful outcome of an event and a disaster.

[0003] Furthermore, emergency services must be prepared to adapt to a variety of different environments, both natural and man-made, which presents further challenges to the organisation and effective handling of events. As such, ineffective management of such events can result in serious harm to the public and cause damage to infrastructure that cannot be repaired.

[0004] In the past, emergency services, such as fire services, have relied on analogue tools to monitor and control the handling of emergency response events. For example, an entry control operator (ECO) would typically use a physical board, such as an entry control board (ECB), to keep track of firefighters deployed at an event, such as a building fire. In this case, the ECO monitors the event by physically organising the board with the help of counters that clearly show the name of the firefighter deployed at the event and the time that the firefighter entered the event. As such, the counters can be physical elements that are added and removed from the board to allow the ECO to keep track of the personnel deployed at the event. The addition of a physical counter to the board can act as an event registration for the corresponding firefighter. In addition to the physical board, the ECO would typically also use a radio to manually control the event and receive updates on the status of personnel.

[0005] In recent years, some emergency services have adopted telemetry technology to provide enhanced communication between personnel deployed in an incident. In particular, emergency service personnel can be provided with equipment that is capable of communicating (wirelessly) with other personnel, and which provides for sharing information describing the equipment wearer and the state of the equipment itself. Thus, emergency service personnel can be provided with equipment that is capable of transmitting critical information to an ECO in real time, which gives the ECO more time to make decisions, and potentially life-saving decisions. Therefore, the technology of enhanced communication provides a significant advantage to the overall safety of the personnel involved in an incident, and provides better protection for the responders deployed.

[0006] However, there are certain challenges in the current technology for handling communication establishment between equipment deployed in an incident. In particular, it is necessary to ensure that the relevant equipment and the corresponding communication between the equipment is handled in a safe and correct manner. In particular, the management of equipment deployed in an incident is typically handled by professionals with expertise and specialists in handling emergency response incidents. Therefore, only certain types of equipment should be allowed to interfere with the incident. More importantly, it is necessary to prevent malicious and / or unauthorised devices from affecting the operation of the incident management, as such interference can potentially cause serious harm or damage to the personnel involved, and / or the environment in which the incident occurs. SUMMARY

[0007] As mentioned previously, there are certain challenges in the current technology for handling communication establishment between equipment deployed in an incident. In particular, it is desirable to prevent attackers, and / or malicious or unauthorised devices from accessing equipment deployed in an emergency response incident. Such third party devices can negatively affect the emergency response system, and therefore pose a danger to the personnel involved.

[0008] According to an aspect of the present disclosure, there is therefore provided a first method of handling connection requests in a network. The first method is performed by a first node of the network. The first node is deployed in an emergency response incident. The first method comprises changing a state of the first node from a first state to a second state in response to obtaining a first input. In the first state, the first node is unable to initiate a connection with a wireless device. In the second state, the first node is able to initiate a one-to-one connection with a wireless device. The first method comprises receiving a first request from a first wireless device deployed in the emergency response incident, the first request requesting information indicating the state of the first node. The first method comprises initiating transmission of a first response to the first wireless device. The first response comprises first information indicating that the state of the first node is the second state. The first method comprises initiating the one-to-one connection with the first wireless device and changing the state of the first node from the second state to the first state in response to receiving a second request from the first wireless device. The second request is a request for the first wireless device to connect to the first node.

[0009] According to another aspect of the disclosure, there is also provided a second method of handling a connection request in a network. The second method is performed by a first wireless device deployed in an emergency response event. The second method comprises initiating transmission of a first request to a first node of the network. The first request is a request for information indicative of a status of the first node. The first node is deployed in the emergency response event. The second method comprises receiving a first response from the first node, the first response comprising first information indicative of the status of the first node being a second status in which the first node is capable of initiating a one-to-one connection with the wireless device. The second method further comprises in response to receiving the first response from the first node, initiating transmission of a second request to the first node, wherein the second request is a request for the first wireless device to connect to the first node.

[0010] According to another aspect of the disclosure, there is also provided a first node comprising processing circuitry configured to operate according to the first method. In some embodiments, the first node can comprise at least one memory for storing instructions that, when executed by the processing circuitry, cause the first node to operate according to the first method.

[0011] According to another aspect of the disclosure, there is also provided a first wireless device comprising processing circuitry configured to operate according to the second method. In some embodiments, the first wireless device can comprise at least one memory for storing instructions that, when executed by the processing circuitry, cause the first wireless device to operate according to the second method.

[0012] According to another aspect of the disclosure, there is provided a method performed by a system. The method comprises the first method described previously and the second method described previously.

[0013] According to another aspect of the disclosure, there is provided a system comprising the first node described previously and the first wireless device described previously.

[0014] According to another aspect of the disclosure, there is provided a computer program comprising instructions which, when executed by processing circuitry, cause the circuitry to perform any one or more of the first method and the second method described previously.

[0015] According to another aspect of the disclosure, there is provided a computer program product embodied on a non-transitory machine-readable medium comprising instructions executable by processing circuitry to cause the processing circuitry to perform any one or more of the first method and the second method.

[0016] Thus, in the manner described above, improved techniques for handling connection requests in a network are provided. These techniques are improved because the first node deployed in the emergency response event is advantageously configured with a first state and a second state, which enables a qualified device (e.g., authorized) to initiate a one-to-one connection with the wireless device. In particular, the first node can be configured in a first state in which the first node is unable to initiate a connection with the wireless device. The first node can remain in the first state until the first node obtains a first response that triggers the first node to enter the second state in which the first node is able to initiate a one-to-one connection with the wireless device. In this manner, the techniques described herein avoid a malicious and / or unauthorized device from gaining access to the first node. This type of connection handling is particularly useful because the first node is deployed in an emergency response event and thus can involve a potentially life-threatening situation in which secure and reliable communication is necessary. BRIEF DESCRIPTION OF DRAWINGS

[0017] For a better understanding of the technology, and to show how the same can be carried into effect, there will now be described by way of example, with reference to the following drawings, in which:

[0018] Figure 1 is a block diagram illustrating a first node in accordance with an embodiment;

[0019] Figure 2 is a block diagram illustrating a method performed by a first node in accordance with an embodiment;

[0020] Figure 3 is a block diagram illustrating a first wireless device in accordance with an embodiment;

[0021] Figure 4 is a block diagram illustrating a method performed by a first wireless device in accordance with an embodiment; and

[0022] Figures 5 to 8 is a block diagram illustrating a method performed in a system in accordance with some embodiments. DETAILED DESCRIPTION

[0023] In general, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the technology described, unless explicitly defined otherwise, and / or implicitly indicated otherwise by its use in the context of the specification. All references to a / an / the [element, device, component, means, step, etc.] are to be interpreted openly as referring to at least one instance of said element, device, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless explicitly stated otherwise, or inherently required. Any of the embodiments disclosed herein can be applied to any other embodiments, wherever technically feasible. Similarly, any advantages, features, or benefits described in relation to any of the embodiments can be applied to any other embodiment, wherever technically feasible. Other objectives, features and advantages of the enclosed embodiments will be apparent from the description.

[0024] Some embodiments contemplated herein will now be described more fully with reference to the drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be limited to the embodiments set forth herein; rather, they are provided for illustrative purposes.

[0025] As noted above, techniques are provided herein for handling connection requests in a network. The techniques described herein can be used in relation to any network, e.g. any communication or telecommunication network, e.g. a cellular network. The network referred to herein can be a radio network. For example, the network referred to herein can be a 2.4 GHz radio network. In some examples, the network can comprise a Wi-Fi network (e.g. based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards). Alternatively, or in addition, the network can comprise a Bluetooth network (e.g. based on the IEEE 802.15.1 family of standards).

[0026] Some techniques described herein are performed by a first node of a network. The first node referred to herein can be configured to route communications between a wireless device and a BA. Herein, the first node can be any entity in the network that can be configured to act as a transceiver between the wireless device and the BA. Thus, in some examples, the first node referred to herein can be configured to operate as a repeater device between different entities in the network referred to herein. The first node referred to herein can be configured to receive communications from the first wireless device referred to herein, and / or from the BA. The first node referred to herein can be configured to initiate transmission of information to the first wireless device referred to herein, and / or to the BA. Herein, the term "initiate" can mean, for example, to cause or to establish. Thus, any reference to an entity (e.g. the first node) "initiating a transmission" will be understood to mean that the entity (e.g. the processing circuitry of the entity) can be configured to transmit itself (e.g. via a communication interface of the entity), or can be configured to cause another entity to transmit.

[0027] Some techniques described herein are performed by a first wireless device. As described herein, a wireless device can be any type of wireless device. More specifically, the wireless device referred to herein can be any device configured to communicate wirelessly with one or more other entities (e.g. in the network referred to herein). For example, the first wireless device can be a user equipment (UE). The first wireless device referred to herein can include, but is not limited to, a smart device, such as a smartphone or a tablet. The first wireless device can be configured to run an application (or "app"), for example, that enables the wireless device to communicate with one or more other entities in the network. The app can provide a user (e.g. an ECO) of the first wireless device with the ability to manage and / or control events described herein. The first wireless device can be configured to enable the user of the first wireless device to create, edit and / or view event information. For example, the first wireless device can be configured to enable the user of the first wireless device to view one or more BAs (e.g. deployed in an event) in the network. Alternatively, or in addition, the first wireless device can be configured to enable the user of the first wireless device to reconfigure one or more BAs and / or respective one or more wearers of the one or more BAs into groups (e.g. teams). The reconfiguration can include, for example, assigning and / or removing the BAs, and / or the wearers of the BAs, to and / or from the groups, respectively. Thus, the event can be managed and controlled (e.g. centrally) using the first wireless device.

[0028] As described herein, the first node referred to herein is deployed in an emergency response event with the first wireless device referred to herein. The emergency response event herein can be any type of emergency response event. More specifically, the emergency response event can refer to any event that involves addressing and / or resolving an emergency situation. The emergency situation referred to herein can be a situation that is urgent, unexpected, and / or dangerous that poses a direct risk to health, life, property, and / or the environment. The emergency situation can require immediate intervention to prevent the situation from worsening. Examples of the emergency response event referred to herein include, but are not limited to, events that pose a threat to life, a threat to health, and / or a threat to the environment. For example, the emergency response event referred to herein can include a fire-related event (e.g., a building fire, a forest fire, a car fire, etc.). Alternatively, or in addition, the emergency response event referred to herein can involve a hazardous material operation (e.g., handling of a substance that poses a risk to health, safety, property, and / or the environment).

[0029] Some techniques described herein relate to a breathing apparatus (BA). The BA referred to herein can be configured to initiate transmission of information (e.g., a signal) and / or receive information. For example, the BA referred to herein can be configured to initiate transmission of information to the first node referred to herein. The BA referred to herein can be any type of BA. More specifically, the BA referred to herein can be any type of apparatus (e.g., device) worn by a wearer of the BA to provide a supply of breathing gas (e.g., air) to the wearer. Thus, the BA can be advantageously used in environments that pose an immediate danger to life or health. For example, the BA referred to herein can be a self-contained breathing apparatus (SCBA) and / or a compressed air breathing apparatus (CABA). The BA referred to herein can be a closed circuit BA. Alternatively, the BA referred to herein can be an open circuit BA.

[0030] Figure 1 A first node 100 according to an embodiment is shown. The first node 100 can be used for handling connection requests in a network.

[0031] As Figure 1 shown, the first node 100 comprises a processing circuit (or logic) 102. The processing circuit 102 controls the operation of the first node 100 and can implement the methods described herein in relation to the first node 100. The processing circuit 102 can be configured or programmed to control the first node 100 in the manner described herein.

[0032] The processing circuit 102 can comprise one or more hardware components, such as one or more processors (e.g., one or more microprocessors, one or more multi-core processors, and / or one or more digital signal processors (DSPs)), one or more processing units, one or more processing modules, and / or one or more controllers (e.g., one or more microcontrollers). The one or more hardware components can be arranged, disposed, and / or configured on one or more printed circuit board assemblies (PCBAs) contained in one or more housing components. The one or more hardware components can be configured or programmed (e.g., with software or computer program code) to perform the various functions described herein with respect to the first node 100. In some embodiments, each of the one or more hardware components can be configured to perform, or for performing, an individual or multiple steps of the methods described herein with respect to the first node 100. The processing circuit 102 can be configured to execute software to perform the methods described herein with respect to the first node 100. The processing circuit 102 can thus be implemented in numerous ways, with software and / or hardware, to perform the various functions described herein with respect to the first node 100.

[0033] Briefly, the processing circuit 102 of the first node 100 is configured to change a state of the first node from a first state to a second state in response to obtaining a first input. In the first state, the first node is unable to initiate a connection with a wireless device. In the second state, the first node is able to initiate a one-to-one connection with a wireless device. The processing circuit 102 of the first node 100 is further configured to receive a first request from a first wireless device deployed in an emergency response event, the request requiring information indicating the state of the first node. The processing circuit 102 of the first node 100 is further configured to initiate transmission of a first response to the first wireless device. The first response includes the first information indicating the state of the first node is the second state. The processing circuit 102 of the first node 100 is further configured to initiate a one-to-one connection with the first wireless device and change the state of the first node from the second state to the first state in response to receiving a second request from the first wireless device. The second request is a request for the first wireless device to connect to the first node.

[0034] As Figure 1As shown, the first node 100 may optionally include memory 104. Alternatively, memory 104 may be external to (i.e., independent of or remote from) the first node 100. Memory 104 may include any type of non-transitory machine-readable medium, such as at least one cache or system memory. Memory 104 may include volatile or non-volatile memory. Examples of memory 104 include, but are not limited to, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), and electrically erasable PROM (EEPROM), and / or any other memory.

[0035] Processing circuitry 102 may be communicatively coupled (e.g., connected) to memory 104. Processing circuitry 102 may be configured to communicate with and / or connect to memory 104. Memory 104 may be used to store program code or instructions that, when executed by processing circuitry 102, cause first node 100 to operate as described herein. For example, memory 104 may be configured to store program code or instructions that can be executed by processing circuitry 102 to cause first node 100 to operate according to the methods described herein regarding first node 100. Alternatively, or furthermore, memory 104 may be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or the like described herein. Processing circuitry 102 may be configured to control memory 104 to store information, data, messages, requests, responses, indications, notifications, signals, or the like described herein.

[0036] like Figure 1 As shown, the first node 100 may optionally include a user interface 106. The user interface 106 may be configured to present (or output, display, or provide) information required or generated by the methods described herein. For example, the user interface 106 may be configured to present (or output, display, or provide) any information, data, messages, requests, responses, instructions, notifications, signals, or the like described herein. Alternatively, or furthermore, the user interface 106 may be configured to receive user input. For example, the user interface 106 may allow a user to manually enter information or instructions to interact with and / or control the first node 100. Thus, the user interface 106 may be a user interface that enables information to be presented (or output, display, or provide) and / or enables a user to provide user input. For example, the user interface 106 may be configured to display event information indicating evacuation orders for personnel deployed in an event.

[0037] User interface 106 may include one or more components for presenting information and / or enabling a user to provide user input. The one or more components for presenting information may include one or more visual components (e.g., a display or display screen, a graphical user interface (GUI) such as a touchscreen, one or more light-emitting diodes (LEDs), and / or any other visual components), one or more audio components (e.g., one or more speakers, and / or any other audio components), and / or one or more haptic / vibration components (e.g., an oscillation function, or any other haptic / vibration feedback component), or any other user interface, or any combination of user interfaces. The one or more components enabling a user to provide user input may include one or more visual components (e.g., one or more switches, one or more buttons, a keypad, a keyboard, a mouse, a graphical user interface (GUI) such as a touchscreen, and / or any other visual components), and / or one or more audio components (e.g., one or more microphones, and / or any other audio components), and / or one or more haptic / vibration components (e.g., an oscillation function, or any other haptic / vibration feedback component), or any other user interface, or any combination of user interfaces.

[0038] like Figure 1 As shown, the first node 100 may optionally include a communication interface (or communication circuitry) 108. The communication interface 108 may be communicatively coupled (e.g., connected) to the processing circuitry 102, the memory 104, and / or the user interface 106. While the communication interface 108 and the user interface 106 are shown as separate interfaces, in other embodiments, the communication interface 108 may be part of the user interface 106. The processing circuitry 102 may be configured to communicate with and / or connect to the communication interface 108. In some embodiments, the processing circuitry 102 may be configured to control the communication interface 108 to operate in the manner described herein. The communication interface 108 may be used to enable the first node 100 or components of the first node 100 (e.g., the processing circuitry 102, the memory 104, the user interface 106, and / or any other component of the first node 100) to communicate with and / or connect to each other, and / or communicate with and / or connect to one or more other components.

[0039] For example, communication interface 108 may be operable to allow processing circuitry 102 to communicate and / or connect to memory 104, and / or vice versa. Similarly, communication interface 108 may be operable to allow processing circuitry 102 to communicate and / or connect to user interface 106, and / or vice versa. Similarly, communication interface 108 may be operable to allow processing circuitry 102 to communicate and / or connect to any other entity mentioned herein, such as the first wireless device. Communication interface 108 may be configured to transmit and / or receive information, data, messages, requests, responses, indications, notifications, signals, or the like described herein. Processing circuitry 102 may be configured to control communication interface 108 to transmit and / or receive information, data, messages, requests, responses, indications, notifications, signals, or the like described herein.

[0040] Communication interface 108 enables the first node 100 or its components to communicate and / or connect in any suitable manner. For example, communication interface 108 can enable the first node 100 or its components to communicate and / or connect wirelessly, via a wired connection, or via any other communication (or data transfer) mechanism. In some wireless implementations, for example, communication interface 108 can enable the first node 100 or its components to communicate and / or connect using radio frequency (RF), Wi-Fi, Bluetooth, or any other wireless communication technology. In some examples, communication interface 108 may include a proprietary radio module.

[0041] although Figure 1 The first node 100 is shown as including a single memory 104, but it should be understood that the first node 100 may include at least one memory (i.e., a single memory or multiple memories) 104, which operate in the manner described herein. Similarly, although Figure 1 The first node 100 is shown as including a single user interface 106, but it should be understood that the first node 100 may include at least one user interface (i.e., a single user interface or multiple user interfaces) 106 that operate in the manner described herein. Similarly, although Figure 1 The first node 100 is shown as including a single communication interface 108. It is understood that the first node 100 may include at least one communication interface (i.e., a single communication interface or multiple communication interfaces) 108, which operate in the manner described herein. It should also be understood that... Figure 1 Only the components required to illustrate the implementation of the first node 100 are shown, and in actual implementation, the first node 100 may include additional or alternative components in addition to the components shown.

[0042] Figure 2A method according to embodiments is shown. The method is for handling connection requests in a network. Reference is made to Figure 1 The first node 100 described can be configured to operate according to Figure 2 the method described. For example, the method can be performed under control of the processing circuitry 102 of the first node 100. Reference is made to Figure 2 The method described can be a computer-implemented method.

[0043] With reference to block 110 in Figure 2 In response to obtaining the first input, the state of the first node 100 changes from a first state to a second state. More specifically, the first node 100 (e.g. the processing circuitry 102 of the first node 100) changes the state of the first node 100. In the first state, the first node is unable to initiate a connection with a wireless device. In the second state, the first node is able to initiate a one-to-one connection with a wireless device.

[0044] The state of the first node 100 can be a connection state and / or a device connection state. Thus, the state of the first node 100 can indicate whether the first node 100 is able to initiate a connection with a wireless device. As described herein, in the first state, the first node 100 is unable to initiate a connection with a wireless device (e.g. the first wireless device mentioned herein). Thus, in some examples, when the first node 100 is in the first state, the first node 100 can be prevented from initiating any connection with any wireless device. In some examples, the first node 100 can prevent any external connection by configuring the communication interface 108 of the first node 100 to, thereby configuring the state of the first node 100 to the first state. According to some examples, the communication interface 108 of the first node 100 can be referred to herein as a wireless (e.g. radio) module. In some examples, the first node 100 can configure one or more rules to handle connections in a network. In some of these examples, changing the state of the first node 100 from the second state to the first state can comprise changing the one or more rules (e.g. a rule set) from “allowed” to “none”.

[0045] As described herein, in the second state, the first node 100 is able to initiate a one-to-one connection with a wireless device. Thus, in some examples, the first node 100 can initiate (e.g., establish) a one-to-one connection with a wireless device in the second state. In some examples, the state of the first node 100 can be configured by configuring the communication interface 108 of the first node 100 to allow external connections, thereby configuring the state of the first node 100. In some examples, the first node 100 can configure one or more rules to handle connections in the network. In some of these examples, changing the state of the first node 100 from the first state to the second state can include changing the one or more rules (e.g., rule set) from "none" to "allowed". Entering the second state of the first node 100 can include the first node 100 (re)configuring the network to become (e.g., externally) wireless device connectable.

[0046] A one-to-one connection as referred to herein can be a unique connection of the first node 100 with a single wireless device (e.g., one of a plurality of wireless devices). Thus, in some examples, the first node 100 can only communicate and / or connect with one wireless device as referred to herein. In some examples, a one-to-one connection as referred to herein can correspond to a unique connection of the first node 100 with a wireless device configured to run an application. It will be appreciated that a wireless device as referred to herein can not include a BA as referred to herein. Thus, initiation, establishment and / or maintenance of a one-to-one connection between the first node 100 and a wireless device (e.g., a first wireless device as referred to herein) can not prohibit the ability of the first node 100 to connect with one or more BAs as referred to herein. A one-to-one connection can enable the first node 100 to authorize a single (e.g., mobile) wireless device to communicate with the first node 100 (e.g., to allow the wireless device to receive information about an emergency response event, and / or to control an emergency response event).

[0047] In some examples, the first input described above can be obtained through a user interface of the first node 100 (e.g., the user interface 106 of the first node 100). For example, obtaining the first input can include pressing a button on the first node 100 (e.g., by a user). Thus, in some examples, a user can need to physically interact with the first node 100 to initiate a connection of the first node 100 with a wireless device. Obtaining the first input can trigger the first node 100 to enter the second state, as defined herein. Obtaining the first input in the manner described above can increase the level of security provided by the method described. For example, where obtaining the first input includes pressing a button on the first node 100, an authorized party can need to obtain physical access to the first node 100. Figure 2

[0048] As Figure 2 ​As shown in block 112 in FIG. 1, a first request is received from a first wireless device deployed in the emergency response event. The first request is a request for information indicating a status of the first node 100. More specifically, the first node 100 (e.g., the processing circuitry 102 of the first node 100) receives the first request from the first wireless device (e.g., via the communication interface 108 of the first node 100).

[0049] As shown in block 114 in FIG. 1, transmission of a first response to the first wireless device is initiated. More specifically, the first node 100 (e.g., the processing circuitry 102 of the first node 100) initiates transmission of the first response (e.g., via the communication interface 108 of the first node 100). The first response includes first information indicating that the status of the first node is a second status. Thus, the first wireless device can be informed that the first node 100 is capable of initiating a one-to-one connection, as defined herein. Figure 2

[0050] As shown in block 116 in FIG. 1, a one-to-one connection with the first wireless device is initiated in response to receiving a second request from the first wireless device. More specifically, the first node 100 (e.g., the processing circuitry 102 of the first node 100) initiates the one-to-one connection with the first wireless device. The second request is a request for the first wireless device to connect to the first node 100. Figure 2 As shown in block 118 in FIG. 1, the status of the first node 100 is changed from the second status to the first status in response to receiving the second request from the first wireless device. More specifically, the first node 100 (e.g., the processing circuitry 102 of the first node 100) changes the status of the first node 100 from the second status to the first status. Thus, in some examples, the first node 100 can change the status of the first node 100 from the second status to the first status as soon as the one-to-one connection with the first wireless device is initiated, as defined herein. Thus, the first node 100 can prevent any further connection establishment with another wireless device.

[0051] Figure 2 Although not shown in FIG. 1, in some examples, the method can include initiating a timer in response to obtaining the first input. Thus, in some examples, obtaining the first input (e.g., receiving a button press) can trigger initiation of the timer (e.g., a countdown). The timer can correspond to (e.g., be set for) a time period (e.g., 2 seconds, 5 seconds, 10 seconds, 20 seconds, 30 seconds, etc.). The time period can be preconfigured and / or stored in the first node 100. In some examples, the one-to-one connection with the first wireless device can only be initiated if the second request is received before the timer expires.

[0052] Although not shown in FIG. 1, in some examples, the method can include initiating a timer in response to obtaining the first input. Thus, in some examples, obtaining the first input (e.g., receiving a button press) can trigger initiation of the timer (e.g., a countdown). The timer can correspond to (e.g., be set for) a time period (e.g., 2 seconds, 5 seconds, 10 seconds, 20 seconds, 30 seconds, etc.). The time period can be preconfigured and / or stored in the first node 100. In some examples, the one-to-one connection with the first wireless device can only be initiated if the second request is received before the timer expires. Figure 2 Although not shown in FIG. 1, in some examples, the method can include initiating a timer in response to obtaining the first input. Thus, in some examples, obtaining the first input (e.g., receiving a button press) can trigger initiation of the timer (e.g., a countdown). The timer can correspond to (e.g., be set for) a time period (e.g., 2 seconds, 5 seconds, 10 seconds, 20 seconds, 30 seconds, etc.). The time period can be preconfigured and / or stored in the first node 100. In some examples, the one-to-one connection with the first wireless device can only be initiated if the second request is received before the timer expires.

[0053] Figure 2 ​​​In some examples, if the timer expires before the second request is received, the method can include truncating the method to omit the step of initiating the one-to-one connection with the first wireless device. Thus, if the timer expires, as defined herein, before the second request is received, the first node 100 can not establish the one-to-one connection with the first wireless device 200. Thus, in some examples, obtaining the first input can start a countdown timer for a time period in which the first wireless device is allowed to initiate a connection to the first node 100. If the connection procedure is not completed within the (e.g., predefined) time period (e.g., the one-to-one connection with the first wireless device is not initiated), the first node 10 can change its state from the second state to the first state (e.g., to block any external connection to the wireless device).

[0054] In some examples, the second request can include an identifier of the first wireless device. The identifier of the first wireless device can be unique to the first wireless device. In some examples, the identifier of the first wireless device can be a media access control (MAC) address. Thus, the identifier of the first wireless device can be a unique alphanumeric attribute that can be used to identify the first wireless device.

[0055] In some examples, the identifier of the first wireless device can be generated by the first wireless device, as described herein. Alternatively, in some examples, the identifier of the first wireless device can be generated by a cloud entity.

[0056] In some examples, initiating the one-to-one connection with the first wireless device can include storing the identifier of the first wireless device (e.g., in the memory 104 of the first node 100). In some examples, the first node 100 can configure the connection policy of the first node 100 to only approve connection requests associated with (e.g., containing) the identifier of the first wireless device (e.g., stored). For example, the first node 100 can reconfigure the wireless module of the first node 100 to only allow the identifier (e.g., MAC address) of the first wireless device. In some examples, initiating the one-to-one connection with the first wireless device can include initiating transmission of a second response to the first wireless device. The second response can include second information indicating that the identifier of the first wireless device has been accepted (e.g., by the first node 100). Thus, the second information can indicate that the first node 100 has authorized the first wireless device to connect to the first node 100. Once the one-to-one connection is initiated, the first wireless device can be able to manage and / or control the emergency response event through the first node 100.

[0057] Although Figure 3In some examples, the method can comprise initiating in response to obtaining the second input. Thus, in some examples, the first node 100 can be initiated in response to obtaining the second input. In some examples, the above-mentioned second input can be obtained via a user interface of the first node 100 (e.g. the user interface 106 of the first node 100). For example, obtaining the second input can comprise pressing a power button on the first node 100 (e.g. by a user). In some examples, the state of the first node 100 can be set to the first state in response to the initiation. More specifically, the first node 100 (e.g. the processing circuitry 102 of the first node) can be configured to set the state of the first node 100 to the first state in response to the initiation (e.g. being turned on). Thus, in some examples, obtaining the second input can trigger the first node 100 to enter the first state as defined herein.

[0058] In some examples, the first node 100 can be configured to transmit third information to the first wireless device. As described herein, the first node 100 can be configured as a transceiver. The third information can be received from one or more breathing apparatuses (BAs) deployed in an emergency response event. Thus, in some examples, the first node 100 can act as a transceiver between the first wireless device and the one or more BAs.

[0059] As described herein, in some examples, the network can comprise a wireless network.

[0060] Figure 3 A first wireless device 200 according to an embodiment is shown. The first wireless device 200 can handle connection requests in a network.

[0061] As Figure 3 shown, the first wireless device 200 comprises processing circuitry (or logic) 202. The processing circuitry 202 controls the operation of the first wireless device 200 and can implement the methods described herein in which the first wireless device 200 is involved. The processing circuitry 202 can be configured or programmed to control the first wireless device 200 in the manner described herein.

[0062] Processing circuitry 202 may include one or more hardware components, such as one or more processors (e.g., one or more microprocessors, one or more multi-core processors, and / or one or more digital signal processors (DSPs)), one or more processing units, one or more processing modules, and / or one or more controllers (e.g., one or more microcontrollers). The one or more hardware components may be arranged on one or more printed circuit board assemblies (PCBAs) and contained within one or more housing assemblies. The one or more hardware components may be configured or programmed (e.g., using software or computer program code) to perform the various functions described herein relating to the first wireless device 200. In a particular implementation, each of the one or more hardware components may be configured to perform, or be used to perform, one or more steps of the methods described herein relating to the first wireless device 200. Processing circuitry 202 may be configured to run software to perform the methods described herein relating to the first wireless device 200. Therefore, processing circuitry 202 may be implemented in a variety of ways, through software and / or hardware, to perform the various functions described herein relating to the first wireless device 200.

[0063] In short, the processing circuitry 202 of the first wireless device 200 is configured to initiate a transmission of a first request to the first node 100 of the network. The first request is a request for information indicating the state of the first node. The first node 100 is deployed in an emergency response event. The processing circuitry 202 of the first wireless device 200 is also configured to receive a first response from the first node 100, the first response including first information indicating that the state of the first node 100 is a second state in which the first node 100 is capable of initiating a one-to-one connection to the wireless device. The processing circuitry 202 of the first wireless device 200 is also configured to, in response to receiving the first response from the first node 100, initiate a transmission of a second request to the first node 100. The second request is a request for the first wireless device 200 to connect to the first node 100.

[0064] like Figure 3 As shown, the first wireless device 200 may optionally include memory 204. Alternatively, memory 204 may be outside the first wireless device 200 (e.g., independent or remote). Memory 204 may include any type of non-transitory machine-readable medium, such as at least one cache or system memory. Memory 204 may include volatile or non-volatile memory. Examples of memory 204 include, but are not limited to, random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), and electrically erasable PROM (EEPROM), and / or any other memory.

[0065] Processing circuitry 202 may be communicatively coupled (e.g., connected) to memory 204. Processing circuitry 202 may be configured to communicate with or be connected to memory 204. Memory 204 may be used to store program code or instructions that, when executed by processing circuitry 202, cause the first wireless device 200 to operate in the manner described herein. For example, memory 204 may be configured to store program code or instructions executable by processing circuitry 202 that cause the first wireless device 200 to operate according to the methods described herein regarding the first wireless device 200. Alternatively, or furthermore, memory 204 may be configured to store any information, data, messages, requests, responses, indications, notifications, signals, or the like described herein. Processing circuitry 202 may be configured to control memory 204 to store information, data, messages, requests, responses, indications, notifications, signals, or the like as described herein.

[0066] like Figure 3 As shown, the first wireless device 200 may optionally include a user interface 206. The user interface 206 may be configured to present (or output, display, or provide) information required or generated by the methods described herein. For example, the user interface 206 may be configured to present (or output, display, or provide) any information, data, messages, requests, responses, instructions, notifications, signals, or the like described herein. Alternatively, or additionally, the user interface 206 may also be configured to receive user input. For example, the user interface 206 may allow a user to manually enter information or instructions to interact with and / or control the first wireless device 200. Therefore, the user interface 206 may be a user interface capable of presenting (or outputting, displaying, or providing) information and enabling a user to provide user input. For example, the user interface 206 may be configured to display event information indicating evacuation orders for personnel deployed in an event.

[0067] User interface 206 may include one or more components for presenting information and / or one or more components that enable the user to provide user input. The one or more components for presenting information may include one or more visual components (e.g., a display or display screen, a graphical user interface (GUI) such as a touchscreen, one or more lights, such as one or more light-emitting diodes (LEDs), and / or any other visual component), one or more audio components (e.g., one or more speakers, and / or any other audio component), and / or one or more haptic / vibration components (e.g., an oscillation function, or any other haptic / vibration feedback component), or any other user interface, or a combination of user interfaces. The one or more components that enable the user to provide user input may include one or more visual components (e.g., one or more switches, one or more buttons, a keypad, a keyboard, a mouse, a graphical user interface (GUI) such as a touchscreen, and / or any other visual component), and / or one or more audio components (e.g., one or more microphones, and any other audio component), and / or one or more haptic / vibration components (e.g., an oscillation function, or any other haptic / vibration feedback component), or any other user interface, or a combination of user interfaces.

[0068] like Figure 3 As shown, the first wireless device 200 may optionally include a communication interface (or communication circuitry) 208. The communication interface 208 may be communicatively coupled (e.g., connected) to the processing circuitry 202, the memory 204, and / or the user interface 206. Although the communication interface 208 and the user interface 206 are shown as separate interfaces, in other embodiments, the communication interface 208 may be part of the user interface 206. The processing circuitry 202 may be configured to communicate with and / or connect to the communication interface 208. In some embodiments, the processing circuitry 202 may be configured to control the communication interface 208 to operate in the manner described herein. The communication interface 208 may be used to enable the first wireless device 200, or components of the first wireless device 200 (e.g., the processing circuitry 202, the memory 204, the user interface 206, and / or any other component of the first wireless device 200), to communicate with and / or connect to each other, and / or communicate with and / or connect to one or more other components.

[0069] For example, the communication interface 208 can be operable to allow the processing circuitry 202 to communicate and / or connect with the memory 204, and / or vice versa. Similarly, the communication interface 208 can be operable to allow the processing circuitry 202 to communicate and / or connect with the user interface 206, and / or vice versa. Similarly, the communication interface 208 can be operable to allow the processing circuitry 202 to communicate and / or connect with any one or more of the entities mentioned herein (e.g., the first node). The communication interface 208 can be configured to transmit and / or receive information, data, messages, requests, responses, indications, notifications, signals, or similar as described herein. The processing circuitry 202 can be configured to control the communication interface 208 to transmit and / or receive information, data, messages, requests, responses, indications, notifications, signals, or similar as described herein.

[0070] The communication interface 208 can enable the first wireless device 200, or components of the first wireless device 200, to communicate or connect in any suitable way. For example, the communication interface 208 can enable the first wireless device 200, or components of the first wireless device 200, to communicate and / or connect wirelessly, through a wired connection, or through any other communication (or data transfer) mechanism. In some wireless implementations, for example, the communication interface 208 can enable the first wireless device 200, or components of the first wireless device 200, to communicate and / or connect using radio frequency (RF), Wi-Fi, Bluetooth, or any other wireless communication techniques. In some examples, the communication interface 208 can comprise a proprietary radio module.

[0071] Although Figure 3 The first wireless device 200 as shown includes a single memory 204, it will be appreciated that the first wireless device 200 can comprise at least one memory (i.e. a single memory or multiple memories) 204, operating in the manner described herein. Similarly, although Figure 3 The first wireless device 200 as shown includes a single user interface 206, it will be appreciated that the first wireless device 200 can comprise at least one user interface (i.e. a single user interface or multiple user interfaces) 206, operating in the manner described herein. Similarly, although Figure 3 The first wireless device 200 as shown includes a single communication interface 208, it will be appreciated that the first wireless device 200 can comprise at least one communication interface (i.e. a single communication interface or multiple communication interfaces) 208, operating in the manner described herein. It will further be appreciated that, Figure 4 Only the components necessary to illustrate the embodiments of the first wireless device 200 are shown, and in a practical implementation the first wireless device 200 can comprise additional or alternative components to those shown.

[0072] Figure 3A method according to an embodiment is shown. The method is for handling a connection request in a network. Reference is made to Figure 4 The first wireless device 200 described can be configured to operate according to Figure 4 the method described. For example, the method can be performed under control of the processing circuitry 202 of the first wireless device 200. Reference is made to Figure 4 The method described can be a computer-implemented method.

[0073] Reference is made to Figure 4 At block 210, transmission of a first request is initiated to a first node 100 of a network. More specifically, the first wireless device 200 (e.g. the processing circuitry 202 of the first wireless device 200) initiates transmission of the first request (e.g. by the communication interface 208 of the first wireless device 200). Thus, the first node 100 can receive the first request from the first wireless device 200. The first request is a request for information indicative of a status of the first node 100, as defined herein. Also as defined herein, the first node 100 is deployed in an emergency response event.

[0074] The method performed by the first wireless device 200 (as described with reference to Figure 4 The method performed by the first wireless device 200 can be performed in response to the wireless device 200 being started (e.g. turned on). Alternatively, or in addition, the method performed by the first wireless device 200 can be performed in response to a (e.g. software) application running on the first wireless device 200 being started (e.g. by a user of the first wireless device 200). For example, the application (at start-up) can aim to establish a connection with the first node 100 (e.g. software) over a wireless connection, and request a status of the first node 100.

[0075] As shown in block 212 in Figure 4 The first response is received from the first node 100. More specifically, the first wireless device 200 (e.g. the processing circuitry 202 of the first wireless device 200) receives the first response (e.g. by the communication interface 208 of the first wireless device 200). The first response comprises first information, indicative of the status of the first node 100 being a second status, in which status the first node is able to initiate a one-to-one connection with a wireless device, as defined herein. In some examples, the first information can be indicative of the first node 100 waiting for information to complete an authorization (e.g. of a connection with a wireless device).

[0076] As shown in block 214 in Figure 4At block 214, in response to receiving the first response from the first node 100, the first wireless device 200 initiates transmission of a second request to the first node 100. More specifically, the first wireless device 200 (e.g., the processing circuitry 202 of the first wireless device 200) initiates transmission of the second request (e.g., by the communication interface 208 of the first wireless device 200). Thus, the first node 100 can receive the second request from the first wireless device 200. The second request is a request for the first wireless device 200 to connect to the first node 100. In some examples, the second request can include an identifier (e.g., a MAC address) of the first wireless device 200, as defined herein. In some examples, the identifier of the first wireless device 200 can be a hash (e.g., a value). An application running on the first wireless device 200 can obtain (e.g., retrieve) the identifier of the first wireless device 200. In some examples, the application running on the first wireless device 200 can initiate transmission of the second request.

[0077] The identifier of the first wireless device 200 can be used to verify that the first wireless device 200 (e.g., the application running thereon) has a suitable provenance for one or more commands and / or requests to be accepted and / or processed by the first node 100 (e.g., the application running thereon). Verifying the first wireless device 200 (e.g., the application running thereon) can be referred to herein as “software layer authorization”.

[0078] In some examples, the identifier of the first wireless device 200 can be generated by the first wireless device 200. For example, where the identifier of the first wireless device 200 is a hash (e.g., a value), the first wireless device 200 (e.g., the application running thereon) can generate the hash. The hash can be unique to the first wireless device 200. The hash can be generated in a manner that enables the hash to be identified by the first node 100. In other words, the hash can enable the first node 100 to determine that the hash corresponds to a valid provenance (e.g., an application running on the first wireless device 200).

[0079] A hash referred to herein can be a generated value. In some examples, a hash can be generated using a hash function. A hash function can be described as a mathematical primitive configured to uniquely map a large input space to a relatively small output space. Generating a hash by a hash function can be based on one or more inputs. For example, the one or more inputs can correspond to one or more characteristics and / or identifiers of the first wireless device 200. A hash referred to herein can be an output (e.g., a value) of a hash function generated based on the one or more inputs.

[0080] In some examples, the one or more inputs can include an (e.g., mobile) application number. For example, the application number can be a number corresponding (e.g., uniquely) to the application running on the first wireless device 200. For example, the application number can be a version number corresponding to the application running on the first wireless device 200. In some examples, the one or more inputs can include (e.g., mobile) application binary data. The application binary data can include data indicating (e.g., specifying) an installation location of the application running on the first wireless device 200. In some examples, the application binary data can not include transient data and / or user data. In some examples, the one or more inputs can include a secret identifier. The secret identifier can be generated by an owner and / or developer of the application running on the first wireless device 200. For example, the secret identifier can be a private encryption key. In some examples, the one or more inputs can include information indicating one or more features of the application running on the first wireless device 200. The one or more features can include features supported, enabled, and / or permitted by the application running on the first wireless device 200.

[0081] As described herein, a hash (e.g., value) can be an output generated by a hash function based on one or more inputs mentioned herein. The hash can be utilized in a variety of ways. For example, the first node 100 can verify the application running on the first wireless device 200 based on the hash. For example, the first node 100 can verify that the application running on the first wireless device 200 is valid and / or approved (e.g., by a vendor of the first node 100) before allowing any interaction with the first wireless device 200. In some examples, the first node 100 can enable and / or disable certain functionality for the first wireless device 200 based on the hash. For example, the first node 100 can enable and / or disable features for the application running on the first wireless device 200 based on (e.g., permission) information included in the hash.

[0082] In some examples, the identifier of the first wireless device 200 can be generated by the cloud entity. In these examples, although Figure 4 Although not shown in FIG. 6, the method can include initiating transmission of a third request to the cloud entity. The third request can be a request for the cloud entity to generate the identifier. Although Figure 4 Although not shown in FIG. 6, in some examples, the method can include receiving a third response from the cloud entity. The third response can include the identifier. Thus, in some examples, in the case that the identifier of the first wireless device 200 is a hash (e.g., value), the cloud entity can generate the hash.

[0083] Although not shown in FIG. 6, in some examples, the method can include receiving a third response from the cloud entity. The third response can include the identifier. Thus, in some examples, in the case that the identifier of the first wireless device 200 is a hash (e.g., value), the cloud entity can generate the hash. Figure 5In some examples, a second response can be received from the first node 100. The second response can include second information indicating that the identifier of the first wireless device 200 has been accepted (e.g., by the first node 100). Thus, in some examples, the first node 100 can validate and process the identifier (e.g., hash) before returning the second response to the wireless device 200 (on which the application is running). The second response can include information indicating that the first node 100 has established a one-to-one connection with the first wireless device 200.

[0084] In some examples, any subsequent communications between the first node 100 and the first wireless device 200 can include the identifier (e.g., unique hash) of the first wireless device 200. Thus, the first node 100 can validate (e.g., authenticate) subsequent communications of the first wireless device 200. Thus, in the event that a different (e.g., running an application) wireless device attempts to communicate with the first node 100, the authorization process described herein can need to be performed again for the different wireless device.

[0085] As described herein, in some examples, the first node 100 can be configured to transmit third information to the first wireless device 200. The third information can be received from one or more breathing apparatus deployed in the emergency response event mentioned herein.

[0086] Thus, in the manner described above, improved techniques for handling connection requests in a network are provided. More specifically, the improved techniques allow a first node 100 (e.g., base station) deployed in an emergency response event to authorize a single wireless device (e.g., physical mobile device) to communicate with the first node 100. Such techniques have advantages in an emergency response event, as a one-to-one connection can be established between the first node 100 and the first wireless device 200, ensuring that important information (e.g., status updates of emergency service personnel, and / or commands / instructions) can be communicated securely between the first node 100 and the first wireless device 200, free from interference from other (e.g., malicious) entities.

[0087] Figure 5 is a block diagram illustrating a method performed in a system (e.g., network) according to an embodiment. As Figure 5 shown, the system can include the first node 100 (“base station”) mentioned herein, and the first wireless device 200 (“mobile device”) mentioned herein. Although not shown in Figure 5 , the first node 100 and the first wireless device 200 can be deployed in an emergency response event (e.g., building fire). As Figure 5As shown, in some examples, the communication between the first node 100 and the first wireless device 200 can be direct. For example, the communication path between the first node 100 and the first wireless device 200 can not involve any intermediary entities.

[0088] As described herein, and as shown in block 304 and block 308, the first node 100 and the first wireless device 200 each include a communication interface. As Figure 5 As shown in block 312, in some examples, the communication interfaces of the first node 100 and the first wireless device 200 can include a Wi-Fi module. Thus, in some examples, the first node 100 and the first wireless device 200 can communicate over a Wi-Fi network. Also as described herein, and as shown in block 314, the first node 100 and the first wireless device 200 can each include a Wi-Fi module. Figure 5 As shown in block 312, in some examples, the communication interfaces of the first node 100 and the first wireless device 200 can include a Wi-Fi module. Thus, in some examples, the first node 100 and the first wireless device 200 can communicate over a Wi-Fi network. Also as described herein, and as shown in block 314, the first node 100 and the first wireless device 200 can each include a Wi-Fi module.

[0089] As described herein, the first node 100 can initiate in response to obtaining the second input. The first node 100 can set the state of the first node 100 to the first state in response to the initiation, as defined herein. As Figure 5 As shown by arrow 312 in block 310, the second input can include obtaining the second input from a user 310. In some examples, receiving the second input can include pressing (e.g., by the user 310) a (power) button on the first node 100. Setting the state of the first node 100 to the first state can include initializing the Wi-Fi module of the first node 100. Initializing the Wi-Fi module of the first node 100 can include, for example, initializing a Wi-Fi network by the Wi-Fi module of the first node 100. In these examples, the Wi-Fi module of the first node 100 (e.g., when in the first state) can be initialized to prevent any connection to a wireless device when the first node 100 is in the first state.

[0090] Also as described herein, the first node 100 changes the state of the first node 100 from the first state to the second state in response to obtaining the first input, as defined herein. As Figure 5As indicated by arrow 314, in some examples, obtaining the first input may include obtaining the first input from user 310. In some examples, receiving the second input may include pressing (connect) a button on the first node 100 (e.g., by user 310). Changing the state of the first node 100 from the first state to the second state may include reconfiguring the Wi-Fi module of the first node 100. In these examples, the Wi-Fi module of the first node 100 (e.g., when in the first state) may be reconfigured to allow the first node 100 to connect to a wireless device (e.g., the first wireless device 200). Configuring the Wi-Fi module of the first node 100 may include configuring the Wi-Fi network of the Wi-Fi module to allow the first node 100 to connect to the wireless device. In these examples, when the state of the first node 100 is the second state, the Wi-Fi network may become visible (i.e., accessible) to one or more wireless devices (e.g., the first wireless device).

[0091] like Figure 5 As indicated by arrow 316, in some examples, the first wireless device 200 can be activated by the user 310 (e.g., by pressing the power button on the first wireless device 200). Figure 5 As indicated by arrow 318, the first wireless device 200 (e.g., the second application 306 of the first wireless device 200) can initiate the transmission of a first request to the first node 100 (e.g., the first application 302 of the first node 100), as defined herein. Therefore, the first node 100 (e.g., the first application 302 of the first node 100) can receive the first request from the first wireless device 200 (e.g., the second application 306 of the first wireless device 200). Figure 5 As indicated by arrow 320, a first node 100 (e.g., a first application 302 of the first node 100) can initiate the transmission of a first response to a second application 306 of a first wireless device 200, as defined herein. Therefore, a second application 306 of the first wireless device 200 can receive a first response from the first node 100 (e.g., the first application 302 of the first node 100). Figure 6 As indicated by arrow 322, the first wireless device 200 (e.g., the second application 306 of the first wireless device 200) can initiate the transmission of a second request to the first node 100 (e.g., the first application 302 of the first node 100), as defined herein. Therefore, the first node 100 (e.g., the first application 302 of the first node 100) can receive the second request from the first wireless device 200 (e.g., the second application 306 of the first wireless device 200). As described herein, the second request is a request for the first wireless device 200 to connect to the first node 100.

[0092] DespiteFigure 6 Without being explicitly shown in

[0093] In some examples, the first node 100 can configure itself to allow connection with the first wireless device 200 (e.g., and no other wireless devices). As described herein, in some examples, the second request can include an identifier of the first wireless device 200. Accordingly, the first node 100 can store the identifier of the first wireless device 200. Alternatively, or in addition, the first node 100 can configure the communication interface 108 of the first node 100 to only communicate with the first wireless device 200 based on the identifier of the first wireless device 200. For example, the first node 100 can configure the Wi-Fi module of the first node 100 to only allow communication associated with the MAC address of the first wireless device 200.

[0094] Figure 5 is a block diagram illustrating a method performed in a system (e.g., a network) according to an embodiment. Figure 6 The illustrated system can be described with reference to the system of Figure 6 .

[0095] As described above, the first node 100 can be configured to allow connection with the first wireless device 200 (e.g., and no other wireless devices). As described herein, in some examples, the second request can include an identifier of the first wireless device 200. Accordingly, the first node 100 can store the identifier of the first wireless device 200. Alternatively, or in addition, the first node 100 can configure the communication interface 108 of the first node 100 to only communicate with the first wireless device 200 based on the identifier of the first wireless device 200. For example, the first node 100 can configure the Wi-Fi module of the first node 100 to only allow communication associated with the MAC address of the first wireless device 200. Figure 6 As shown by arrow 402 in Figure 6 Without being explicitly shown in Figure 6 In some examples, the first wireless device 200 can generate the identifier of the first wireless device 200 in response to the initiation of the second application 306. In these examples, the identifier of the first wireless device 200 can be generated prior to the initiation of the second application 306 as shown by arrow 402 in

[0096] In some examples, the identifier of the first wireless device 200 can be generated if the first wireless device 200 (e.g., the second application 306) has not been authorized to communicate with the first node 100 (e.g., the first application 302). For example, the identifier of the first wireless device 200 can be generated (e.g., automatically) by the wireless device 200 if the first wireless device 200 has not performed an authorization procedure with the first node 100, as described herein.

[0097] As shown by arrow 404 in Figure 6 , the first wireless device 200 (e.g., the second application 306) can initiate transmission of a second request to the first node 100 (e.g., the first application 302), as defined herein. Thus, the first node 100 (e.g., the first application 302) can receive the second request from the first wireless device 200 (e.g., the second application 306). The second request can include the identifier of the first wireless device 200. Thus, in some examples, the first wireless device 200 can register the identifier of the first wireless device 200 with the first node 100. Thus, the second request can be referred to herein as a “registration request.”

[0098] Although not explicitly shown in Figure 7 , in some examples, the first node 100 (e.g., the first application 302 of the first node 100) can accept the second request and / or accept (e.g., validate) the identifier of the first wireless device 200. The first node 100 (e.g., the first application 302 of the first node 100) can store the identifier of the first wireless device 200 (e.g., in the memory 104 of the first node 100). Thus, the first node 100 can register the first wireless device 200 at the first node. As shown by arrow 406 in Figure 7 , the first node 100 (e.g., the first application 302 of the first node 100) can initiate transmission of a second response to the first wireless device 200. Thus, the first wireless device 200 (e.g., the second application 306 of the first wireless device 200) can receive the second response from the first node 100. The second response can include second information indicating that the identifier of the first wireless device 200 has been accepted. Thus, in some examples, the first node 100 can inform the first wireless device 200 that the identifier of the first wireless device 200 has been accepted.

[0099] Figure 7 is a block diagram illustrating a method performed in a system (e.g., a network) according to an embodiment. In addition to the example system shown in Figure 5 , the system shown in Figure 6 may all refer to Figure 7 and Figure 7The illustrated system to describe. Cloud entity 502 can be a node in the network mentioned herein. As Figure 7 As illustrated, in some examples, first wireless device 200 can communicate wirelessly with cloud entity 502. Although Figure 6 not illustrated in FIG. 5, it should be appreciated that, in some examples, first node 100 can be configured to communicate (e.g., directly) with cloud entity 502.

[0100] Figure 7 The method steps illustrated in step 506 in FIG. 5 can be described with reference to arrow 402 in FIG. 4. Figure 7

[0101] As illustrated in FIG. 5, in some examples, first wireless device 200 can initiate transmission of a second request to cloud entity 502. Thus, cloud entity 502 can receive the second request from first wireless device 200. The second request can be a request for cloud entity 502 to generate an identifier for first wireless device 200, as mentioned herein. Thus, in some examples, cloud entity 502 can generate an identifier for first wireless device 200. The second request can be referred to herein as a request for registration in the cloud system. Figure 7

[0102] Thus, in some examples, cloud entity 502 (e.g., the cloud system) can be used to authorize and / or register second application 306 (e.g., running on first wireless device 200). Thus, cloud entity 502 can ensure that the software of first wireless device 200 (e.g., of second application 306) is from the correct source. After second application 306 initiates (e.g., first time), described with reference to arrow 506 in FIG. 4, second application 306 can guide user 310 (through user interface 206 of first wireless device 200) through a process of registering first wireless device 200 and / or second application 306 to cloud entity 502 (e.g., the cloud system). For example, second application 306 can generate output (e.g., visual) requesting user 310 to log in to cloud entity 502 (e.g., the cloud system). In some examples, in response to a successful user login, a third request can be initiated to cloud entity 502, as defined herein. Figure 7

[0103] As illustrated in FIG. 5, in some examples, first wireless device 200 can initiate transmission of a second request to cloud entity 502. Thus, cloud entity 502 can receive the second request from first wireless device 200. The second request can be a request for cloud entity 502 to generate an identifier for first wireless device 200, as mentioned herein. Thus, in some examples, cloud entity 502 can generate an identifier for first wireless device 200. The second request can be referred to herein as a request for registration in the cloud system. Figure 7 Figure 7 ​​​​As shown in box 504, in some examples, cloud entity 502 may generate (e.g., output) an identifier (e.g., a hash) of the first wireless device 200. The identifier may be a token in this document. The identifier (e.g., a token) may be used by the first wireless device 200 (e.g., a second application 306) to make a request to the first node 100 (e.g., a second request as defined herein). In some examples, the identifier of the first wireless device 200 may be specific to the second application 306. In these examples, the identifier of the first wireless device 200 may refer to an "application token".

[0104] like Figure 6 As indicated by arrow 512, the first wireless device 200 (e.g., the second application 306) may initiate the transmission of a second request to the first node 100 (e.g., the first application 302), as defined herein. Therefore, the first node 100 (e.g., the first application 302) may receive the second request from the first wireless device 200 (e.g., the second application 306). The second request may include an identifier of the first wireless device 200, as defined herein. Thus, in some examples, for example... Figure 7 As shown, the second request may include a token generated by cloud entity 502.

[0105] Although not in Figure 7 While explicitly stated, in some examples, the first node 100 (e.g., the first application 302) can decode the identifier of the first wireless device 200 (e.g., a token generated by cloud entity 502). Other information can be encoded into the token generated by cloud entity 502. For example, the token may include licensing information and / or information indicating licensed features (e.g., should be enabled on the second application 306). The information included in the token can be used by the first node 100 to verify and / or authorize the first wireless device 200 (e.g., the second application 306) as a trusted source. For example, the token may be verified by the first node 100 as being generated by cloud entity 502. In some examples, the information included in the token may be used by the first node 100 as a means of enabling and / or disabling certain functions and / or capabilities of the system. For example, the first node 100 can determine, based on the token, which functions and / or capabilities are provided (e.g., enabled) to the first wireless device 200.

[0106] Although not in Figure 7 As explicitly shown, in some examples, the first node 100 can accept a second request and / or accept (e.g., verify) the identifier (e.g., a token) of the first wireless device 200. The first node 100 (e.g., the first application 302) can store (e.g., in the memory 104 of the first node 100) the identifier (e.g., the token) of the first wireless device 200. Therefore, according to some examples, the first node 100 can register the first wireless device 200 on the first node 100. For example...Figure 7 As shown by arrow 514 in FIG. 6, the first node 100 (e.g., the first application 302 of the first node 100) can initiate transmission of a second response to the first wireless device 200. Thus, the first wireless device 200 (e.g., the second application 306 of the first wireless device 200) can receive the second response from the first node 100. The second response can include second information indicating that the identifier (e.g., the token) of the first wireless device 200 has been accepted. Thus, in some examples, the first node 100 can inform the first wireless device 200 that the identifier of the first wireless device 200 has been accepted. In some examples, the third request, as defined herein, can be initiated only after the first wireless device 200 receives the first response, as defined herein. For example, to utilize the authorization process of the cloud entity 502 described with reference to Figure 8 As shown by arrow 514 in FIG. 6, the first node 100 (e.g., the first application 302 of the first node 100) can initiate transmission of a second response to the first wireless device 200. Thus, the first wireless device 200 (e.g., the second application 306 of the first wireless device 200) can receive the second response from the first node 100. The second response can include second information indicating that the identifier (e.g., the token) of the first wireless device 200 has been accepted. Thus, in some examples, the first node 100 can inform the first wireless device 200 that the identifier of the first wireless device 200 has been accepted. In some examples, the third request, as defined herein, can be initiated only after the first wireless device 200 receives the first response, as defined herein. For example, to utilize the authorization process of the cloud entity 502 described with reference to

[0107] Although Figure 8 The example system shown including the cloud entity 502, it should be understood that in other examples, the system can not include the cloud entity.

[0108] Figure 5 is a block diagram illustrating a method performed in a system (e.g., a network) according to an embodiment. Figure 6 The system shown can be described with reference to Figure 8 and Figure 5 The system shown can be described with reference to

[0109] The method steps shown in Figure 8 may be described with reference to Figure 8 , respectively.

[0110] As described herein, in response to receiving the second request from the first wireless device 200, the first node 100 initiates a one-to-one connection with the first wireless device 200, as defined herein. As Figure 8 As shown by arrow 608 in FIG. 6, in some examples, the first wireless device 200 (e.g., the Wi-Fi module of the first wireless device 200) can initiate transmission of a notification message to the first node 100 (e.g., the Wi-Fi module of the first node 100). Thus, the first node 100 (e.g., the Wi-Fi module of the first node 100) can receive the notification message from the first wireless device 200 (e.g., the Wi-Fi module of the first wireless device 200). The notification message can include information indicating that the first wireless device 200 has initiated the one-to-one connection with the first node 100. As ​As indicated by arrow 612, in some examples, the Wi-Fi module of the first node 100 can notify the first application 302 that initiated the connection. Based on the identifier of the first wireless device 200, as defined herein, the first node 100 (e.g., the first application 302 of the first node 100) can reconfigure the Wi-Fi module of the first node 100.

[0111] like ​ As indicated by arrow 610, the first node 100 (e.g., the Wi-Fi module of the first node 100) can initiate the transmission of an acknowledgment message to the first wireless device 200 (e.g., the Wi-Fi module of the first wireless device 200).

[0112] A computer program is also provided, including instructions that, when executed by processing circuitry (e.g., processing circuitry 102 of the first node 100 described herein and / or processing circuitry 202 of the first wireless device 200 described herein), cause the processing circuitry to perform at least a portion of the methods described herein. A computer program product is provided, implemented on a non-transitory machine-readable medium, including instructions executable by processing circuitry (e.g., processing circuitry 102 of the first node 100 described herein and / or processing circuitry 202 of the first wireless device 200 described herein) to cause the processing circuitry to perform at least a portion of the methods described herein. A computer program product is provided, including a carrier containing instructions for causing processing circuitry (e.g., processing circuitry 102 of the first node 100 described herein and / or processing circuitry 202 of the first wireless device 200 described herein) to perform a portion of the methods described herein. In some embodiments, the carrier may be any one of electronic signals, optical signals, electromagnetic signals, electrical signals, radio signals, microwave signals, or a computer-readable storage medium.

[0113] The techniques described herein facilitate improved (e.g., multi-layered) configurations between a first node 100 and a first wireless device 200 in a network. Specifically, the techniques described herein provide a one-to-one connection between the first wireless device 200 and the first node 100, achieved through authentication by the first wireless device 200 with the first node 100. This allows the first node 100 and the first wireless device 200 to communicate securely, avoiding the risk of malicious or unauthorized devices interfering with the functionality of the first node 100. This is particularly advantageous when the first node is deployed in emergency response events.

[0114] Indeed, in some examples, the first node 100 can be configured to act as a transceiver between the devices deployed in the event and the first wireless device 200. In some of these examples, the first wireless device 200 can be configured to manage (e.g. coordinate) the event through the first node 100. Thus, the techniques described herein can be effectively utilized to prevent malicious and / or unauthorised devices from interfering with the management of an event deployed by the first node 100 and the first wireless device 200. Thus, the techniques described herein can be effectively used to prevent an attacker from gaining access to the first node 100.

[0115] It should be noted that the above-mentioned embodiments illustrate rather than limit the ideas, and that one skilled in the art will be capable of designing many alternative implementations without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims, "a" or "an" does not exclude a plurality, and a single processor or other unit can fulfil the functions of several units listed in the claims. Any reference signs in the claims should not be construed as limiting the scope.

Claims

1. A method for processing connection requests in a network, wherein, The method is executed by a first node (100) of the network, wherein the first node (100) is deployed in an emergency response event, and the method includes: In response to receiving the first input, the state of the first node (100) is changed from the first state (110) to the second state, wherein: In the first state, the first node (100) cannot initiate a connection with the wireless device; and In the second state, the first node (100) is able to initiate a one-to-one connection with the wireless device; A first request is received (112, 318) from a first wireless device (200) deployed in the emergency response event for information indicating the status of the first node (100); A transmission of a first response (114, 320) is initiated to the first wireless device (200), wherein the first response includes first information indicating that the state of the first node (100) is the second state; and In response to receiving a second request from the first wireless device (200), wherein the second request is a request for the first wireless device (200) to connect to the first node: Initiate (116) a one-to-one connection with the first wireless device (200); and Change the state of the first node (100) from the second state (118) to the first state.

2. The method according to claim 1, wherein, The first input is obtained through the user interface of the first node (100).

3. The method according to claim 1 or 2, wherein, The method includes: In response to receiving the first input, a timer is started, wherein the one-to-one connection with the first wireless device (200) is initiated only if the second request is received before the timer expires.

4. The method according to claim 3, wherein, If the timer expires before the second request is received, the method includes: The method is terminated to omit the step of initiating (116) the one-to-one connection with the first wireless device (200).

5. The method according to any one of the preceding claims, wherein, The second request includes the identifier of the first wireless device (200).

6. The method according to claim 5, wherein, The identifier is generated as follows: The first wireless device (200); or Cloud entity (502).

7. The method according to claim 5 or 6, wherein, Initiating the one-to-one connection with the first wireless device (200) includes: Store the identifier; and Transmission of a second response (514) to the first wireless device (200), wherein the second response includes second information indicating that the identifier of the first wireless device (200) has been accepted.

8. The method according to any one of the preceding claims, the method comprising: In response to obtaining a second input power supply; as well as In response to power-on, the state of the first node (100) is set to the first state.

9. A method for processing connection requests in a network, wherein, The method is performed by a first wireless device (200) deployed in an emergency response event, and the method includes: Transmission of a first request (210) is initiated to a first node (100) of the network, wherein the first request is a request for information indicating the status of the first node (100), and wherein the first node (100) is deployed in the emergency response event; Receive (212) a first response from the first node (100), the first response including first information indicating that the state of the first node (100) is a second state, wherein the first node (100) is capable of initiating a one-to-one connection with a wireless device; In response to receiving the first response from the first node (100), a transmission of a second request (214) is initiated to the first node (100), wherein the second request is a request for the first wireless device (200) to connect to the first node (100).

10. The method according to claim 9, wherein, The second request includes the identifier of the first wireless device (200), and the method includes: Transmitting a third request (508) to the cloud entity (502), wherein the third request is a request for the cloud entity (502) to generate the identifier; and Receive (510) a third response from the cloud entity (502), wherein the third response includes the identifier.

11. The method according to claim 9 or 10, wherein the method comprises: Receive (406) a second response from the first node (100), wherein the second response includes second information indicating that the identifier of the first wireless device (200) has been accepted.

12. The method according to any one of the preceding claims, wherein, The first node (100) is configured to transmit third information to the first wireless device (200), wherein the third information is received from one or more breathing devices deployed in the emergency response event.

13. A first node (100), comprising: The processing circuit (102) is configured to operate according to any one of claims 1 to 8 and / or according to claim 12 when it is dependent on any one of claims 1 to 8.

14. A first wireless device (200), comprising: The processing circuit (202) is configured to operate according to any one of claims 9 to 11 and / or according to claim 12 when it is dependent on any one of claims 9 to 11.

15. A computer program product embodied on a non-transitory machine-readable medium, the computer program product comprising instructions executable by processing circuitry, the instructions causing the processing circuitry to perform the method as follows: Any one of claims 1 to 8 and / or claim 12 when it is subordinate to any one of claims 1 to 8; and / or Any one of claims 9 to 11 and / or claim 12 when it is subordinate to any one of claims 9 to 11.

Images