In an embodiment, the third field indicates the availability of the UWB services information in an in-band UWB service information response message.

In an embodiment, the UWB services information in the in-band UWB service information response message is obtained from the first device using the in-band communication protocol.

In an embodiment, the OOB communication protocol comprises one of a Bluetooth protocol, a Wireless Fidelity (Wi-Fi) protocol, and a Near Field Communication (NFC) protocol.

In an embodiment, the in-band communication protocol comprises a UWB protocol.

In an embodiment, the UWB services information is denoted using a bitmask representation.

In an embodiment, the UWB services information is denoted using one or more UWB service information Identification value corresponding to the one or more UWB services.

In an embodiment, the UWB controller in the first device is configured to receive an OOB UWB service information request message from the second UWB device after establishing the OOB connection with the first device, wherein the OOB UWB service information request message comprises a query for a support of the one or more UWB services by the first UWB device and the UWB services information corresponding to the one or more UWB services. Further, generate a OOB UWB service information response message comprising a support for a subset of the one or more UWB services supported by the first device and the UWB services information corresponding to the one or more UWB services. Furthermore, send the OOB UWB service information response message to the second UWB device.

In an embodiment, the OOB UWB service information request message is a CMD_GET_SERVICE_INFO comprising a value of a request type as GET.

In an embodiment, the OOB UWB service information request message for obtaining the UWB services information comprises a Num_of_Service field indicating a count of the one or more UWB services for which the UWB services information is requested. Further, one or more Service_ID fields indicating a UWB service Identification value corresponding to the one or more UWB services.

In an embodiment, the OOB UWB service information response message for providing the UWB services information comprises a Num_of_Service field indicating a count of the one or more UWB services supported by the first device. Further, one or more Service_ID fields indicating a UWB service Identification value corresponding to the one or more UWB services supported by the first device. Furthermore, one or more common parameters field. Thereafter, a length of extended service information field indicating a length of the extended service information field in bytes, and an extended service information data.

In an embodiment, the UWB controller in the first device is configured to receive an in-band UWB service information request message from the second UWB device in an in-band connection, wherein the in-band UWB service information request message comprises a query for a support of the one or more UWB services by the first UWB device and the UWB services information corresponding to the one or more UWB services. Further, generate an in-band UWB service information response message comprising a support for a subset of the one or more UWB services supported by the first device and the UWB services information corresponding to the one or more UWB services. Furthermore, send the in-band UWB service information response message to the second UWB device.

In an embodiment, the in-band UWB service information request message is a CMD_GET_SERVICE_INFO comprising a value of a request type as GET.

In an embodiment, the in-band UWB service information request message for obtaining the UWB services information comprises a Num_of_Service field indicating a count of the one or more UWB services for which the UWB services information is requested. Further, one or more Service_ID fields indicating a UWB service Identification value corresponding to the one or more UWB services.

In an embodiment, the in-band UWB service information response message for providing the UWB services information using in-band communication protocol comprises at least one of a Num_of_Service field indicating a count of the one or more UWB services supported. Further, one or more Service_ID fields indicating a UWB service Identification value corresponding to the one or more UWB services supported by the first device. Furthermore, one or more common parameters field. Thereafter, a length of extended service information field indicating a length of the extended service information field in bytes, and an extended service information data.

In an embodiment, the UWB controller in the first device is configured to periodically broadcast the advertisement message comprises sending the advertisement message using the OOB communication protocol after completion of a pre-defined time period, wherein the second UWB device receives the advertisement message when the second UWB device is in a communication range of the first UWB device.

These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. Also, the various embodiments described herein are not necessarily mutually exclusive, as some embodiments can be combined with one or more other embodiments to form new embodiments. The term “or” as used herein, refers to a non-exclusive or, unless otherwise indicated. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those skilled in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.

As is traditional in the field, embodiments may be described and illustrated in terms of blocks which carry out a described function or functions. These blocks, which may be referred to herein as managers, units, modules, hardware components or the like, are physically implemented by analog and/or digital circuits such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits and the like, and may optionally be driven by firmware and software. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like. The circuits constituting a block may be implemented by dedicated hardware, or by a processor (e.g., one or more programmed microprocessors and associated circuitry), or by a combination of dedicated hardware to perform some functions of the block and a processor to perform other functions of the block. Each block of the embodiments may be physically separated into two or more interacting and discrete blocks without departing from the scope of the disclosure. Likewise, the blocks of the embodiments may be physically combined into more complex blocks without departing from the scope of the disclosure.

Referring now to the drawings and more particularly to FIGS. 1 through 8, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

FIG. 1A illustrates an example environment for communicating Ultra-Wide Band (UWB) services information supported by a first UWB device to a second UWB device, according to the embodiments as disclosed herein.

In one implementation, Ultra-Wide Band (UWB) services are provided and/or obtained by a first UWB device (101) and a second UWB device (102). The first UWB device (101) and the second UWB device (102) communicate using a communication network. The communication network may include at least one of a wired interface and a wireless interface. The UWB services for example, may include at least one of a payment service, a file transfer service, an access control service, and the like. The UWB services mentioned herein should not be treated as a limitation, rather be treated as examples. The first UWB device (101) and the second UWB device (102) may communicate using at least one of an Out of Band (OOB) communication protocol and an in-band communication protocol. The OOB communication protocol comprises one of a Bluetooth protocol, a Wireless Fidelity (Wi-Fi) protocol, and a Near Field Communication (NFC) protocol. The in-band communication protocol comprises the UWB protocol. The first UWB device (101) and the second UWB device (102) may include at least one of a laptop, a computer, a smartphone, a payment terminal, an access control terminal, an electronic appliance such as television, refrigerator, and the like, an automobile, and the like,

In an embodiment, the first UWB device (101) may include a memory (101A), a processor (101B) and an UWB controller (101C) communicatively coupled to the memory (101A) and the processor (101B). The UWB controller (101C) in the first UWB device (101) is configured to indicate an availability of the UWB services information to the second UWB device (102) and send the UWB services information to the second UWB device (102).

The processor (101A) may be a general-purpose processor, such as a Central Processing Unit (CPU), an Application Processor (AP), or the like, a graphics-only processing unit such as a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU) and the like. The processor (101A) may include multiple cores to execute the instructions.

The UWB controller (101C) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.

In an embodiment, the UWB controller (101C) in the first UWB device (101) is configured to generate an advertisement message (301), generate an extended advertisement message (304), and periodically broadcast the advertisement message (301). Further, the UWB controller (101C) in the first UWB device (101) is configured to send the extended advertisement message (304) after sending the advertisement message (301), receive a scan request message (302) from the second UWB device (102), receive an OOB UWB service information request message (305) from the second UWB device (102), receive an in-band UWB service information request message (307) from the second UWB device (102). Furthermore, the UWB controller (101C) in the first UWB device (101) is configured to send a scan response message (303), an OOB UWB service information response message (306), and an in-band UWB service information response message (308) to the second UWB device (102).

In an embodiment, the second UWB device (102) may include a memory (102A), a processor (102B) and an UWB controller (102C) communicatively coupled to the memory (102A) and the processor (102B). The UWB controller (102C) in the second UWB device (102) is configured to receive the advertisement message (301) from the first UWB device (101) when the second UWB device (102) is in a communication range of the first UWB device (101). The advertisement message (301) indicates the availability of the UWB services information. For example, the communication range may be 0.5 meters, 1 meter, 2 meter and the like. Further the communication range is based on at least one of the OOB communication protocol and the in-band communication protocol.

The processor (102B) may be a general-purpose processor, such as a Central Processing Unit (CPU), an Application Processor (AP), or the like, a graphics-only processing unit such as a Graphics Processing Unit (GPU), a Visual Processing Unit (VPU) and the like. The processor (102B) may include multiple cores to execute the instructions.

The UWB controller (102C) is implemented by processing circuitry such as logic gates, integrated circuits, microprocessors, microcontrollers, memory circuits, passive electronic components, active electronic components, optical components, hardwired circuits, or the like, and may optionally be driven by a firmware. The circuits may, for example, be embodied in one or more semiconductor chips, or on substrate supports such as printed circuit boards and the like.

In an embodiment, the UWB controller (102C) in the second UWB device (102) is configured to receive an extended advertisement message (304) from the first UWB device (101), send a scan request message (302) to the first UWB device (101), send an OOB UWB service information request message (305) to the first UWB device (101), send an in-band UWB service information request message (307) to the first UWB device (101). Further, the UWB controller (102C) in the second UWB device (102) is configured to receive a scan response message (303), an OOB UWB service information response message (306), and an in-band UWB service information response message (308) from the first UWB device (101).

In an embodiment, first UWB device (101) and the second UWB device (102) is one of a controller device or a controlee device. For example, if the first UWB device (101) is the controller device, the second UWB device (102) is the controlee device. In another example, if the first UWB device (101) is the controlee device, the second UWB device (102) is the controller device. Further, the controlee device indicates a device requesting services from the controller device. For example, consider a file transfer service, the controlee device indicates a device requesting the UWB services information associated with a file transfer request from the controller device.

In an embodiment, the second UWB device (102) identifies the supported UWB services on the first UWB device (101) using the advertisement message (301). The advisement message indicates the availability of the UWB services and a means to obtain the UWB services information. Further, the second UWB device (102) establishes a connection with the first UWB device (101) for using the one or more UWB services of the first UWB device (101).

In an embodiment, the second UWB device (102) requires a UWB service (say for example, Service ‘X’) from the first UWB device (101). However, the second UWB device (102) has no information regarding the support for the service ‘X’ by the first UWB device (101). Therefore, the first UWB device (101) periodically broadcasts a list of one or more UWB services supported by the first UWB device (101) and other configuration information associated with the one or more UWB services supported by the first UWB device (101).

In another embodiment, the second UWB device (102) sends a query if service ‘X’ is supported by the first UWB device (101). The first UWB device (101) responds with a “success or yes” and the other UWB service information if the service ‘X’ is supported by the first UWB device (101). Alternatively, the first UWB device (101) responds with a “Failure or no” if the service ‘X’ is not supported by the first UWB device (101). Further, the second UWB device (102) receives the response and avails the one or more UWB services. The periodic broadcast of the one or more UWB services reduces a power consumption in the UWB devices (101 and 102). Further, the indication of the availability of the UWB services information reduces messages exchange and enables faster communication between the UWB devices (101 and 102).

In a first example, consider FIG. 1B illustrating an example use case for performing a peer to peer payment and proximity based file transfer between a first UWB device (101) and the second UWB device (102).

Consider, a User ‘B’ willing to transfer money to a User ‘A’ using a proximity based UWB payments service. The User ‘B’ brings the second UWB device (102) (say for example, a UWB enabled phone) within the communication range of the first UWB device (101) (say for example, a UWB enabled phone) of the User ‘A’. However, the second UWB device (102) of the User ‘B’ has no information regarding the support and availability for the UWB payments service in the first UWB device (101) of the User ‘A’. Therefore, the first UWB device (101) of the User ‘A’ provides a list of one or more UWB services (for example, a UWB Payments service, a UWB File transfer service and the like) and other configuration information for one or more UWB services supported by the first UWB device (101) of the User ‘A’ to the second UWB device (102) of the User ‘B’. Further, User ‘B’ may selects the UWB Payments Service in the second UWB device (102), and proceed to initiate a payment transaction with the first UWB device (101) for sending money to the User ‘A’.

Further, the User ‘B’ is willing to transfer one or more files to the User ‘A’ using a proximity based UWB File Transfer service. The User ‘B’ brings the second UWB device (102) (say for example, a UWB enabled phone) within the communication range of the first UWB device (101) (say for example, a UWB enabled phone) of the User ‘A’. However, the second UWB device (102) of the User ‘B’ has no information regarding the support and availability of the UWB File Transfer Service in the first UWB device (101) of the User ‘A’. Therefore, the second UWB device (102) of the User ‘B’ sends a query message to the first UWB device (101) of the User ‘A’. The query message includes a request for the support of the UWB File Transfer service. The first UWB device (101) of the User ‘A’ responds with at least one of a “Success or yes” and other service details (like configuration and connection setup) if the UWB File Transfer service is supported by the first UWB device (101). Alternatively, the first UWB device (101) responds with a “Failure or no” if the UWB File Transfer service is not supported by the first UWB device (101). If the response from the first UWB device (101) is a “Success or yes” the User ‘B’ proceeds to share files from the second UWB device (102) with the first UWB device (101) of the User ‘A’.

In a second example, consider FIG. 1C illustrating an example use case of performing a payment transaction between a first UWB device (101) and the second UWB device (102).

In an embodiment, a user with the second UWB device (102) (say for example, a UWB enabled phone) is willing to initiate a payment transaction with the first UWB device (101) (say for example, a wireless point of sale (PoS) terminal) in a shop using proximity based UWB Payments Service. The User brings the second UWB device (102) in the communication range of the first UWB device (101) i.e. PoS terminal. However, the second UWB device (102) has no information whether the first UWB device (101) i.e. PoS terminal supports the UWB payment service or not. Further, the first UWB device (101) i.e. the PoS terminal broadcasts the advertisement message (301) indicating the support for the UWB Payments Service along with other UWB services information (such as configuration and connection setup). The second UWB device (102) of the User receives the advertisement message (301) from the first UWB device (101) i.e. PoS terminal and proceeds to initiate the payment transaction from the second UWB device (102) with the first UWB device (101) i.e., PoS terminal.

In a third example, consider FIG. 1D illustrating an example scenario of using a UWB enabled phone as a remote control and a gaming joystick for operating a Television (TV).

Consider, the second UWB device (102) (say for example, a UWB enabled phone) of a user. The user is willing to use the second UWB device (102) as a remote control and as a gaming joystick for interacting with the first UWB device (101) (i.e. TV). However, the second UWB device (102) of the user is not aware if a UWB remote control service, and a UWB gaming service is supported by the first UWB device (101) (i.e. TV). Therefore, the TV advertises the list of one or more UWB services supported by the TV and other UWB service information (such as configuration and connection setup). For example, TV broadcasts the advertisement message (301) indicating a support for the UWB remote control service and the UWB gaming service. The second UWB device (102) of the User reads the broadcasted advertisement message (301) and selects the UWB remote control service. Further, the user operates and controls the first UWB device (101) (i.e. TV) using the second UWB device (102). Furthermore, the User may select the UWB gaming service and use the second UWB device (102) as the joystick for interacting with the first UWB device (101) (i.e. TV) for playing games.

In another embodiment, the second UWB device (102) of the User may query for the list of one or more UWB services supported by the first UWB device (101) (i.e., TV). The TV responds to the query with the UWB remote control service, the UWB gaming service and other UWB services information (such as configuration and connection setup). Further. The second UWB device (102) of the User reads the response to the query and selects the UWB remote control service. The user controls the TV using the second UWB device (102). Furthermore, the User may select the UWB gaming service and uses the second UWB device (102) as joystick for interacting with the TV for play the games.

In yet another embodiment, the second UWB device (102) of the User may query for a support for the UWB remote control service with the first UWB device (101) (i.e. TV). The TV responds with a “success or yes” and provides other UWB services information (such as configuration and connection setup). Further, the second UWB device (102) of the User reads the response to the query and the user uses the second UWB device (102) as a remote control for operating the TV. Furthermore, when the user wants to play games, the second UWB device (102) of the User may query for a support of the UWB gaming service with the first UWB device (101) (i.e. the TV). The TV may respond with the “success or yes” and provide other UWB services information to the second UWB device (102). The second UWB device (102) of the User reads the response to the query and uses the second UWB device (102) as the joystick for gaming and interacting with the TV.

In a fourth example, consider FIG. 1E illustrating an example scenario of using a UWB enabled phone as an access key for operating a car.

Consider a User willing to rent a car. The User moves towards the car and wishes to unlock doors of the car (i.e. first UWB device (101)) using the second UWB device (102) (say for example, a UWB enabled phone) of the User. However, the second UWB device (102) is not aware whether the car supports the UWB access service. Therefore, the car broadcasts the advertisement message (301) indicating a support for the UWB access service and provides other UWB services information required to enable the second UWB device (102) to be used as the UWB based key. The user may lock or unlock doors of the car using the second UWB device (102).

In a fifth example, consider FIG. 1F illustrating an example scenario of using a UWB enabled phone as a key for operating a door lock.

Consider, the user willing to unlock a door (i.e. first UWB device (101)) using the second UWB device (102) (say for example, a UWB enabled phone) of the user. The second UWB device (102) of the user supports the UWB physical access service and the second UWB device (102) is not aware whether the door supports the UWB physical access service. Therefore, the second UWB device (102) of the User sends a query for the supports of the UWB physical access service. The door responds with a “success or yes” and provides the UWB services information required to enable the second UWB device (102) of the user to be used as a key to open the door based on UWB access control service.

FIG. 2 shows an example flowchart illustrating a method of communicating UltraWide Band (UWB) services information supported by a first UWB device (101) to a second UWB device (102), according to the embodiments as disclosed herein.

At the step 201, the method comprises generating, by the first UWB device (101), an advertisement message (301) comprising at least one of a first field indicating an availability of the UWB services information before establishing an Out of Band (OOB) connection with the first UWB device (101), a second field indicating an availability of the UWB services information after establishing the OOB connection with the first UWB device (101), and a third field indicating an availability of the UWB services information in an in-band connection.

In an embodiment, the first UWB device (101) and the second UWB device (102) is one of the controller device or the controlee device. The advertisement message (301) generated by the first UWB device (101) indicating the availability of the UWB services information is as shown in FIG. 3.

In an embodiment, the first field indicates the availability of the UWB services information before establishing an Out of Band (OOB) connection with the first UWB device (101). For example, the first field may be denoted using a single bit or a flag, an integer number, and the like. When the first field is denoted using a single bit, and a value of the single bit equal to one ‘1’ indicates that the UWB services information is available to the second UWB device (102) without establishing the OOB connection with the first UWB device (101). Further, when the first field is denoted using a single bit, and a value of the single bit equal to zero ‘0’ indicates that the UWB services information is not available to the second UWB device (102) without establishing the OOB connection with the first UWB device (101). The first field denoted using a single bit is shown in Table 1.

TABLE 1

Indication of the UWB services information available

to be shared pre-association/pre-connection

1 bit

Further, the first field indicates the availability of the UWB services information in at least one of the advertisement message (301) or an extended advertisement message (304) or a scan response message (303). The availability of the UWB services information indicates a location of the presence of the UWB services information.

In an embodiment, the second field indicates the availability of the UWB services information after establishing the OOB connection with the first UWB device (101). For example, the second field may be denoted using a single bit or a flag, an integer number, and the like. When the second field is denoted using a single bit, and a value of the single bit equal to one ‘1’ indicates that the UWB services information is available to the second UWB device (102) after establishing the OOB connection with the first UWB device (101). Further, when the second field is denoted using a single bit, a value of the single bit equal to zero ‘0’ indicates that the UWB services information is not available to the second UWB device (102) after establishing the OOB connection with the first UWB device (101). The second field denoted using a single bit is shown in Table 2.

TABLE 2

Indication for UWB services info available to

be shared post-association/post-connection

1 bit

Further, the second UWB device (102) obtains the UWB services information from the first UWB device (101) in the OOB UWB service information response message (306) using the OOB communication protocol. The OOB communication protocol comprises one of the Bluetooth protocol, the Wireless Fidelity (Wi-Fi) protocol, and the Near Field Communication (NFC) protocol.

In an embodiment, the third field indicates the availability of the UWB services information in the in-band connection. For example, the third field may be denoted using a single bit or a flag, an integer number, and the like. When the third field is denoted using a single bit, a value of the single bit equal to one ‘1’ indicates that the UWB services information is available to the second UWB device (102) in the in-band connection. Further, when the third field is denoted using a single bit, a value of the single bit equal to zero ‘0’ indicates that the UWB services information is not available to the second UWB device (102) in the in-band connection. The third field denoted using a single bit is shown in Table 3.

TABLE 3

Indication for UWB services info available to be shared in-band

1 bit

Further, the second UWB device (102) obtains the UWB services information from the first UWB device (101) in an in-band UWB service information response message (308) using the in-band communication protocol. The in-band communication protocol comprises the UWB protocol.

In an embodiment, when the first field, the second field, and the third field are denoted using a three single bits in the advertisement message (301), the three single bits may have a value equal to one “1” or zero “0”. For example, if the value of the single bit corresponding to the second field and the third field is equal to one “1”, the value of the single bit corresponding to the first field is equal to zero ‘0’. Then, in one embodiment, the second UWB device (102) may obtain the UWB services information after establishing the OOB connection with the first UWB device (101) using the OOB UWB service information response message (306). In another embodiment, the second UWB device (102) may obtain the UWB services information using the in-band UWB service information response message (308) in the in-band connection.

At the step 202, the method comprises periodically broadcasting, by the first UWB device (101), the advertisement message (301) using an Out of Band (OOB) communication protocol.

In an embodiment, periodically broadcasting, by the first UWB device (101), the advertisement message (301) comprises sending the advertisement message (301) using the OOB communication protocol after completion of a pre-defined time period denoted by signal 1 in FIG. 3. The pre-defined time period is configured in the memory (101A) of the first UWB device (101). For example, the pre-defined time period may be 10 milliseconds, 20 milliseconds and the like. The OOB communication protocol comprises one of a Bluetooth protocol, a Wireless Fidelity (Wi-Fi) protocol, and a Near Field Communication (NFC) protocol.

Further, the second UWB device (102) receives the advertisement message (301) when the second UWB device (102) is in the communication range of the first UWB device (101).

In an embodiment, the second UWB device (102) reads the advertisement message (301) and identifies the availability of the UWB services information based on a value of the first field, the second field and the third field.

In a first embodiment, if the first field indicates the availability of the UWB services information, then the second UWB device (102) obtains the UWB services information within the advertisement message (301) using the OOB communication protocol as shown in FIG. 4. The UWB services information corresponds to the one or more UWB services supported by the first UWB device (101). Further, the second UWB device (102) obtains the UWB services information before establishing the connection with the first UWB device (101) (i.e. pre-association or pre-connection).

In a second embodiment, if the first field indicates the availability of the UWB services information, then the second UWB device (102) may generate and send a scan request message (302) as shown by signal 2 in FIG. 5. The scan request message (302) includes the query whether the one or more UWB services are supported by the first UWB device (101). The first UWB device (101) upon receiving the scan request message (302), generates and sends the scan response message (303) to the second UWB device (102) as shown by the signal 3 in FIG. 5. The scan response message (303) comprises “Success or yes” corresponding to the one or more UWB services supported by the first UWB device (101) and the corresponding UWB services information. Further, the scan response message (303) comprises “failure or no” corresponding to the one or more UWB services not supported by the first UWB device (101). Further, the second UWB device (102) obtains the UWB services information before establishing the connection with the first UWB device (101) (i.e. pre-association or pre-connection).

In an third embodiment, if the first field indicates the availability of the UWB services information, then the second UWB device (102) may receive the extended advertisement message (304) after receiving the advertisement message (301) as shown by the signal 2 in FIG. 6. Further, the extended advertisement message (304) comprises the UWB services information corresponding to the one or more UWB services supported by the first UWB device (101). Further, the second UWB device (102) obtains the UWB services information before establishing the connection with the first UWB device (101) (i.e. pre-association or pre-connection).

In an embodiment, the UWB services information in the advertisement message (301), or in extended advertisement message (304), or in the scan response message (303) is denoted using the bitmask representation. Further the bitmask representation may be denoted using “N” bits when a count of the one or more UWB services supported by the first UWB device (101) is equal to “N”. For example, the bitmask representation may be denoted as “0100” where 5 bits denote 5 UWB services and a value “0” indicates no support and a value “1” indicates a support for the corresponding UWB service. The bitmask or bloom filter representation of the UWB services information is shown in Table 4.

TABLE 4

Contents of the pre-association/pre-
Size in

S. No
connection UWB services Information IE
bits

1
Bitmask/Bloom filter representation of UWB
N bits

services supported

In an embodiment, the UWB services information in the advertisement message (301), or in extended advertisement message (304), or in the scan response message (303) is denoted using one or more UWB service information Identification value corresponding to the one or more UWB services. The UWB services information is denoted using a list of UWB services supported by the first UWB device (101) as shown in Table 5. The value “N” denotes a count of the one or more UWB services supported by the first UWB device (101). Further, the UWB services information includes the UWB service information Identification value (i.e. UWB service Identifier) corresponding to the one or more UWB services as shown in Table 6.

TABLE 5

Contents of the pre-association/pre-
Size in

S. No
connection UWB services Information IE
bits

1
List of UWB service information IE for
Variable (N * 16 bits)

services supported

TABLE 6

Size in

S. No
Contents of UWB service information IE
bits

1
UWB service identifier
16 bits

In an embodiment, the second UWB device (102) reads the advertisement message (301) and identifies the availability of the UWB services information after establishing the OOB connection with the first UWB device (101) based on a value of the second field in the advertisement message (301) as shown by signal 1 in FIG. 7. The second UWB device (102) sets up the OOB connection with the first UWB device (101) as shown by signal 2 in FIG. 7.

Further, the first UWB device (101) receives an OOB UWB service information request message (305) from the second UWB device (102) after establishing the OOB connection with the first UWB device (101) as shown by signal 3 in FIG. 7. The OOB UWB service information request message (305) comprises a query for a support of the one or more UWB services by the first UWB device (101) and the UWB services information corresponding to the one or more UWB services. The OOB UWB service information request message (305) is a CMD_GET_SERVICE_INFO comprising a value of a request type as GET.

The OOB UWB service information request message (305) for obtaining the UWB services information comprises a Num_of_Service field indicating a count of the one or more UWB services for which the UWB services information is requested. Further, OOB UWB service information request message (305) comprises one or more Service_ID fields indicating a UWB service Identification value corresponding to the one or more UWB services. The table 7 and table 8 below shows different embodiments for denoting the Num_of_Service field, one or more Service_ID fields in the OOB UWB service information request message (305).

TABLE 7

Contents of the post-association/post-

connection UWB services info request IE
Size in

S. No
format 1
bits

1
UWB service Identifier
16 bits

TABLE 8

Contents of the post-association/post-

connection UWB services info Request IE
Size in

S. No
format 2
bits

1
Number of UWB service
16

2
List of UWB service identifier for
16 bits * N

supported services

In an embodiment, when the second UWB device (102) requests for all supported UWB services information, the UWB service Identifier=‘0’ or NULL in format 1 and the list of UWB service identifier={0} or { } in format 2. The OOB UWB service information request message (305) is without any input parameters.

In an embodiment, when the second UWB device (102) requests for a single UWB services information, the UWB service identifier is a 16-bit value in format 1. The list of UWB service identifier comprises {UWB service Id}, and a Num of UWB service=1 in format 2.

In an embodiment, when the second UWB device (102) requests for a plurality of UWB services information, the List of UWB service identifiers comprises the UWB service identifiers and the number of UWB service is a count of the UWB services for which the support is requested in format 2.

In an embodiment, after receiving the OOB UWB service information request message (305), the first UWB device (101) generates the OOB UWB service information response message (306) comprising a support for a subset of the one or more UWB services supported by the first UWB device (101) and the UWB services information corresponding to the one or more UWB services. Further, the first UWB device (101) sends the OOB UWB service information response message (306) to the second UWB device (102) as shown by signal 4 in FIG. 7.

In an embodiment, the OOB UWB service information response message (306) for providing the UWB services information comprises a Num_of_Service field indicating a count of the one or more UWB services supported by the first UWB device (101). Further, the OOB UWB service information response message (306) comprises one or more Service_ID fields indicating a UWB service Identification value corresponding to the one or more UWB services supported by the first UWB device (101). Furthermore, the OOB UWB service information response message (306) comprises one or more common parameters field. Thereafter, the OOB UWB service information response message (306) comprises a length of extended service information field indicating a length of the extended service information field in bytes, and an extended service information data. The Table 9, Table 10, Table 11, and Table 12 below show different embodiments for denoting the OOB UWB service information response message (306).

TABLE 9

Contents of the post-association/post-
Size in

S. No
connection UWB services info response IE
bits

1
Number of UWB service information IE
16 bits

2
List of UWB service information IE for
Variable (N * size

supported services
of UWB service

info IE)

TABLE 10

Size in

S. No
Contents of UWB service information IE
bits

1
UWB service Identifier
16 bits

2
Common service parameters
24

3
Extended service information
variable

TABLE 11

Size in

S. No
Contents of Extended Service information
bits

1
Length of extended service information
32 bits

2
Extended service information data
variable

TABLE 12

Contents of the post-association/post-connection
Size in

UWB services Information response IE
bits

Bitmask/Bloom filter representation of UWB services
N bits

supported

In an embodiment, the second UWB device (102) reads the advertisement message (301) and identifies the availability of the UWB services information in the in-band connection based on the third field in the advertisement message (301) as shown by signal 1 in FIG. 8.

In an embodiment, the first UWB device (101), receives an in-band UWB service information request message (307) from the second UWB device (102) in the in-band connection as shown by signal 2 in FIG. 8. The in-band UWB service information request message (307) comprises a query for a support of the one or more UWB services by the first UWB device (101) and the UWB services information corresponding to the one or more UWB services. The in-band UWB service information request message (307) is a CMD_GET_SERVICE_INFO comprising a value of a request type as GET.

In an embodiment, the in-band UWB service information request message (307) for obtaining the UWB services information comprises a Num_of_Service field indicating a count of the one or more UWB services for which the UWB services information is requested. Further, the in-band UWB service information request message (307) comprises one or more Service_ID fields indicating a UWB service Identification value corresponding to the one or more UWB services.

In an embodiment, in-band UWB service information request message (307) comprises one or more Service_ID fields indicating a UWB service Identification value corresponding to the one or more UWB services. The table 13 and table 14 below shows different embodiments for denoting the Num_of_Service field, one or more Service_ID fields in the in-band UWB service information request message (307).

TABLE 13

Contents of the in-band UWB services info
Size in

S. No
request IE format 1
bits

1
UWB service Identifier
16 bits

TABLE 14

Contents of the in-band UWB services
Size in

S. No
information Request IE format 2
bits

1
Number of UWB service
16

2
List of UWB service identifier for supported
16 bits * N

services

In an embodiment, when the second UWB device (102) requests for all supported UWB services information, the UWB service Identifier=‘0’ or NULL in format 1. The list of UWB service identifier={0} or { } in format 2. The in-band UWB service information request message (307) is without any input parameters.

In an embodiment, when the second UWB device (102) requests for a single UWB services information, the UWB service identifier is a 16-bit value in format 1. The list of UWB service identifier comprises {UWB service Id}, and a Num of UWB service=1 in format 2.

In an embodiment, after receiving the in-band UWB service information request message (307), the first UWB device (101) generates the in-band UWB service information response message (308) comprising a support for a subset of the one or more UWB services supported by the first UWB device (101) and the UWB services information corresponding to the one or more UWB services. Further, the first UWB device (101) sends the in-band UWB service information response message (308) to the second UWB device (102) using the in-band connection as shown in signal 3 in FIG. 8.

In an embodiment, the in-band UWB service information response message (308) for providing the UWB services information using in-band communication protocol comprises at least one of a Num_of_Service field indicating a count of the one or more UWB services supported. Further, the in-band UWB service information response message (308) comprises one or more Service_ID fields indicating a UWB service Identification value corresponding to the one or more UWB services supported by the first UWB device (101). Furthermore, the in-band UWB service information response message (308) comprises one or more common parameters field. Thereafter, the in-band UWB service information response message (308) comprises a length of extended service information field indicating a length of the extended service information field in bytes, and an extended service information data. The Table 15, Table 16, Table 17, and Table 18 below show different embodiments for denoting the in-band UWB service information response message (308).

TABLE 15

Contents of the in-band UWB services info

S. No
response IE
Size in bits

1
Number of UWB service information IE
16 bits

2
List of UWB service information IE for
Variable (N * size

supported services
of UWB service

info IE)

TABLE 16

Size in

S. No
Contents of UWB service information IE
bits

1
UWB service Identifier
16 bits

2
Common service parameters
24

3
Extended service information
variable