TWI555417B - Improved techniques for wireless network service discovery - Google Patents

Description

Improved technology for wireless network service discovery Field of invention

The embodiments described herein are generally related to communicating over a wireless network. More specifically, the embodiments described herein are generally related to wireless network service discovery operations.

Background of the invention

In a wireless communication network in which the service is provided by multiple wireless devices, any particular wireless device may employ service discovery techniques to become services provided by other wireless devices in the wireless network. During the execution of the service discovery process, such wireless devices may send data such as a scan box containing information indicating the type of service or service sought to locate. The greater the amount of such information transmitted over a wireless network, the greater the additional burden of service discovery. When repeatedly transmitting lengthy service names, the additional burden of service discovery may be significant and may result in degradation of network performance.

In accordance with an embodiment disclosed herein, at least one machine readable medium comprising a plurality of instructions is provided that, in response to execution on a computing device, causes the computing device to perform the following actions: One of the services in the line network determines a service name; a service identifier (ID) is determined for the service, the service ID containing one of the number of bits is less than one bit included in the service name for the service The number; and generate a service ID mapping information to map the service ID to the service name.

100‧‧‧Wireless network

102, 104, 106‧‧‧ wireless devices

103, 105, 107, 307 ‧ ‧ services

110‧‧‧Management device

112‧‧‧General Management Services Information

200, 300‧‧‧ equipment

202, 302‧‧‧ processor circuit

204, 304‧‧‧ memory unit

220-1‧‧‧Management components

220-2, 320-2‧‧‧Dynamic components

220-a, 320-a‧‧‧ software components

222, 322‧‧‧Service ID mapping information

223, 323‧‧‧ Service ID mapping entries

224, 324‧‧‧ Service Name

226, 326‧‧‧ Service ID

228, 328‧‧‧General/Local Management (U/L) Bits

230, 330‧‧‧ scan box

244, 344‧‧‧ transceiver

240, 340‧‧‧ system

307‧‧‧Local Management Services

320-1‧‧‧Determining components

321‧‧‧ hash algorithm

400, 500‧‧‧ logic flow

402-406, 502-508‧‧‧

600‧‧‧Storage media

700‧‧‧Communication device

710‧‧‧ radio interface

712‧‧‧ Receiver

714‧‧‧ frequency synthesizer

716‧‧‧transmitter

718-f‧‧‧Antenna

720‧‧‧Base frequency circuit

722‧‧‧ Analog to Digital Converter

724‧‧‧Digital to analog converter

726‧‧‧Baseband or physical layer (PHY) processing circuits

727‧‧‧Memory Access Control (MAC) Processing Circuit

728‧‧‧Logical circuits

730‧‧‧ Computing Platform

732‧‧‧ memory controller

734‧‧" interface

740‧‧‧Processing components

750‧‧‧ platform components

Figure 1 illustrates one embodiment of an operating environment.

2 illustrates an embodiment of a first device and an embodiment of a first system.

Figure 3 illustrates an embodiment of a second device and an embodiment of a second system.

Figure 4 illustrates an embodiment of a first logic flow.

Figure 5 illustrates an embodiment of a second logic flow.

Figure 6 illustrates an embodiment of a storage medium.

Figure 7 illustrates an embodiment of a computing architecture.

Detailed description

Various embodiments are generally related to techniques for wireless network service discovery. In some embodiments, for example, a device can include a processor circuit, a management component executed by the processor circuit to determine a service name for a service in a wireless network and to decide to serve one of the services ID, the number of bits included in the service ID is less than the number of bits included in the service name for the service, and is performed by the processor circuit executing one of the mapping components to generate the service ID mapping information The service ID to the service name. Other embodiments are described and patents are claimed.

1 illustrates a wireless network 100 that includes an embodiment of an operating environment of various embodiments. As shown in FIG. 1, wireless devices 102, 104, and 106 and management device 110 communicate over wireless network 100. In some embodiments, wireless network 100 can include a wireless network that conforms to one or more Wi-Fi Alliance (WFA) standards. For example, in various embodiments, wireless network 100 may issue operations in accordance with the WFA Wi-Fi Direct standard, 2010. In several other embodiments, wireless network 100 can include a Wi-Fi P2P wireless network, a wireless network operating in accordance with one or more of the American Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards, or according to any other wireless communication A wireless network operated by the agreement. Embodiments are not limited to this one.

In various embodiments, wireless devices 102, 104, and 106 can provide services 103, 105, and 107 for use with each other and/or by other wireless devices in wireless network 100. Services 103, 105, and 107 may include applications, functions, operations, and/or other types of services. Embodiments of services 103, 105, and 107 may include operations such as printing operations, applications such as gaming applications and social networking applications, functions such as sending and receiving functions, and/or other types of services. In an embodiment where the wireless network 100 includes a Wi-Fi Direct wireless network, the services 103, 105, and 107 may include direct services. In several embodiments, each of services 103, 105, and 107 can have an associated service name. For example, in one embodiment, where the service 103 includes a "Tic-Tac-Toe" game application, the associated service name may be "TicTacToe.Game.Apps". Embodiments are not limited to this one.

In various embodiments, one of services 103, 105, and 107 Or more can include general management services. The general management service may include services registered with the management device such that the management device maintains knowledge of the services and their corresponding service names. The wireless device in the network can become aware of the general management service by performing service exploration through the management device. In the embodiment of FIG. 1, services 103 and 105 can include general management services. The management device 110 can manage general management service information 112, which contains information describing the services 103 and 105, such as its service name. The wireless device 106 can be aware of the services 103 and 105 by communicating with the management device 110. Similarly, the wireless device 104 can communicate with the management device 110 to know the service 103, and the wireless device 102 can communicate with the management device 110 to know the service 105. Embodiments are not limited to this one.

In some embodiments, one or more of services 103, 105, and 107 can include local management services. The local management service may include services that are not logged in to the management device. By performing service discovery through wireless devices that provide such services, wireless devices in the network can become aware of locally managed services. In the embodiment of FIG. 1, service 107 can include locally managed services, and wireless devices 102 and 104 can become aware service 107 by communicating with wireless device 106. Embodiments are not limited to this one.

In various embodiments, service names for services such as services 103, 105, and 107 of FIG. 1 may be quite long. For example, in some embodiments, the length of the service name can be a 64 octet Domain Name System (DNS) string format. In a wireless network that includes a large number of interworking wireless devices, there may be a considerable additional burden associated with repeated service communication with long service names during service discovery operations. To reduce this extra burden, a short service identifier (ID) can be generated that is significantly smaller than the service name. For example, in various In an embodiment, the length of the service ID may be 6 octets. A service ID can be generated for each service name and can be used instead of the service name during the service discovery communication. An advantage of several embodiments may be to generate a service ID and to replace the service name during the service discovery communication, which may significantly reduce the network overhead. Other advantages may be associated with the disclosed subject matter, and embodiments are not limited to this context.

2 illustrates a block diagram of an apparatus 200 that may include one embodiment of the management device 110 of FIG. 1 in various embodiments. In some embodiments, device 200 can include a service ID management device that communicates over a wireless network 100 that includes one of the Wi-Fi Direct wireless networks. Although the device 200 shown in FIG. 2 has a multiplicity of components in certain topologies, it is to be understood that the device 200 may contain more or fewer components in other topologies for a given desire. Embodiments are not limited to this one.

Device 200 can include a computer-generated device 200 having processor circuitry 202 configured to execute one or more software components 220-a. It is noted that "a" and "b" and "c" and similar symbols as used herein are intended to mean any variable of a positive integer. Thus, for example, if a value of a = 5 is now set, then a complete set of software components 220-a can include components 220-1, 220-2, 220-3, 220-4, and 220-5. Embodiments are not limited to this one.

Device 200 can include processor circuit 202. Processor circuit 202 is generally configurable to execute one or more software components 220-a. Processor circuit 202 can be any of a variety of commercially available processors including, but not limited to, AMD® Athlon®, Duron®, and Opteron®. Processor; ARM® application, embedded and secure processor; IBM® and Motorola® DragonBall® and PowerPC® processors; IBM and Sony® Cell processors; Intel® Intel® Sileron®, Core (2) Dual (Duo®), Core i3, Core i5, Core i7, Itanium®, Pentium®, Xeon®, and XScale® Processor; and similar processors. Dual microprocessors, multi-core processors, and other multi-processor architectures may also be employed as the processor circuit 202.

Device 200 can also include a memory unit 204. The memory unit 204 can use any machine readable or computer readable medium capable of storing data, including both electrical and non-electrical memory. For example, the memory unit 204 may include read only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM) synchronous DRAM (SDRAM), static RAM ( SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), polymer memory such as ferroelectric polymer memory, chalcogen memory, phase transition Or ferroelectric memory, 矽-oxide-nitride-oxide-矽 (SONOS) memory, magnetic or optical card, or any other type of media suitable for storing information. It is noted that some or all of the memory unit 204 may be included on the same integrated circuit of the processor circuit 202, or alternatively, some or all of the memory unit 204 may be disposed at the processor circuit 202. An integrated circuit or other medium external to the integrated circuit such as a hard disk drive. Although memory unit 204 is included within device 200 of FIG. 2, in some embodiments, memory unit 204 can be external to device 200. Embodiments are not limited to this one.

Device 200 can include a management component 220-1. In some embodiments, management component 220-1 can be configured to be hosted by processor circuit 202 to dispatch a service ID to a general management service in wireless network 100. In various embodiments, the size of the service ID may be smaller than the service name for the general management service. For example, in several embodiments, the general management service may have a service name in the DNS name format of length 64 octets, and the corresponding service ID may be 6 octets in length. Embodiments are not limited to this one.

Device 200 can include a pair of mapping components 220-2. In various embodiments, the mapping component 220-2 can be configured to maintain the service ID mapping information 222 by execution of the processor circuit 202. The service ID mapping information 222 may include information indicating that the service name is mapped to one of the service IDs of the general management service in the wireless network 100. In some embodiments, for a given service ID, the service ID mapping information 222 can indicate a service name for one of the services identified by the service ID. In various embodiments, device 200 is operative to store service ID mapping information 222 in memory unit 204. Embodiments are not limited to this one.

FIG. 2 also illustrates an embodiment of a system 240. System 240 can include device 200 and transceiver 244. Transceiver 244 can include one or more radios capable of transmitting and receiving signals using a variety of suitable wireless communication technologies. Such techniques may involve communication across one or more wireless networks. Example wireless networks include, but are not limited to, wireless local area networks (WLANs), wireless personal area networks (WPANs), wireless metropolitan area networks (WMANs), residential networks, and satellite networks. Transmitter 244 can operate in accordance with one or more applicable standards of any version across such network communications. In several embodiments, for example, Transceiver 244 can operate in accordance with Wi-Fi Direct standards. Embodiments are not limited to this one.

In a typical operation, device 200 and/or system 240 is operative to generate a service ID for a general management service in wireless network 100, and maintain service ID mapping information 222, with a license decision associated with each generated service ID. The name of the junction service.

In various embodiments, wireless device 102 is operable to register service 103 with device 200 and/or system 240. In several embodiments, device 200 and/or system 240 is operable to receive service name 224 from wireless device 102 during the registration process. The service name 224 can include a service name for one of the services 103, which can include a general management service. In various embodiments, the service name 224 can include a relatively long string of characters. For example, in some embodiments, the service name 224 can include a service name string in the form of a DNS name of length 64 octets. In one embodiment, where service 103 includes a Tic-Tac-Toe game application, service name 224 may include the string "TicTacToe.Game.App." Embodiments are not limited to this one.

In various embodiments, management component 220-1 is operable to dispatch a service ID 226 to service 103. In some embodiments, management component 220-1 is operable to dispatch a service ID 226 to service 103 such that service ID 226 in the service ID for the universal management service of wireless network 100 is unique. In various embodiments, management component 220-1 is operable to dispatch service ID 226 based on service ID mapping information 222. In some embodiments, management component 220-1 is operable to process service ID mapping information 222 to determine a service ID that is already in use, and is operable to dispatch a different one than any service ID currently in use. Service ID 226. In various embodiments, service ID 226 can include a relatively short value. For example, in several embodiments, service ID 226 may include a string of characters or a value of 6 octets in length. Embodiments are not limited to this one.

In various embodiments, management component 220-1 is operative to generate a service ID 226 that includes a generic/local management (U/L) bit 228. In some embodiments, U/L bit 228 can include a one-bit indication that the service 103 identified by service ID 226 is general or local managed. For example, in various embodiments, a value of "0" for U/L bit 228 may indicate that a service is general management and a value of "1" may indicate that a service is locally managed. In other embodiments, a "1" value indicates that a service is general management, and a value of "0" indicates that a service is locally managed. In some embodiments, U/L bit 228 can include one of the first bit of service ID 226, the last bit of service ID 226, or any other bit of service ID 226. In various embodiments, management component 220-1 is operable to generate service ID 226 such that 228 has a value indicating service 103 as a general management service. In the foregoing embodiment, the service name 224 includes the string "TicTacToe.Game.App", and the management component 220-1 is operable to generate a service ID 226 containing the hexadecimal value "0000 0000 0003", which is in the A one-digit "0" value indicates that the service 103 is a general management service. Embodiments are not limited to this one.

In several embodiments, the mapping component 220-2 can be operated to map the service name 224 to the service ID 226 assigned to the service 103. In various embodiments, the mapping component 220-2 may map the service name 224 to the service ID 226 by generating a service ID mapping entry 223 in the service ID mapping information 222. Service ID mapping entry 223 may contain information indicating service ID 226 refers to service The general management service corresponding to the name 224. In the foregoing embodiment, the service 103 includes a tic-tac-toe application. The service ID mapping entry 223 may include the information indicating that the service ID "0000 0000 0003" refers to the application and corresponds to the service name "TicTacToe.Game.App". Embodiments are not limited to this one.

In several embodiments, wireless device 104 may desire to utilize service 103 provided by wireless device 102. In various embodiments, instead of scanning service 103 based on its service name 224, wireless device 104 is operable to scan service 103 based on its service ID 226. In some embodiments, the wireless device 104 is operable to communicate with the device 200 and/or system 240, and to determine the service ID 226 for the service 103 based on the service ID mapping entry 223. For example, the wireless device 104 can send a service ID query identifying the service name 224 to the device 200 and/or system 240, and the management component 220-1 can identify the service ID 226 based on the service ID mapping entry 223, and respond The service ID 226 is sent to the wireless device 104 for the service ID query. The wireless device 104 can then operate to scan the service 103 based on the service ID 226 identified by the service ID mapping entry 223. For example, in various embodiments, the wireless device 104 is operable to broadcast a scan box 230 that includes a service ID 226, and the wireless device 102 is operable to respond to the scan box 230. In some embodiments, the use of the service ID 226 may cause the wireless device 104 to conserve power, bandwidth, and/or other transmission resources because the size of the scan box 230 is comparable to the conventional method in which the service name is included in the scan. The inside of the box can be reduced. Embodiments are not limited to this one.

3 illustrates a block diagram of a device 300 that provides an embodiment of a wireless device, such as one of the wireless devices 106 of FIG. 1, including one of the local management services. to In various embodiments, device 300 can include a wireless station (STA) that communicates over a wireless network 100 that includes a Wi-Fi Direct wireless network. Although the device 300 shown in FIG. 3 has a limited number of components in certain topologies, it will be appreciated that the device 300 can include more or fewer components of other topologies, as desired for a given purpose. Embodiments are not limited to this one.

Device 300 can include a computer-generated device 300 having a processor circuit 302 configured to execute one or more software components 320-a. Processor circuit 302 can be any of a variety of commercially available processors and can be the same as or similar to processor circuit 202 of FIG.

Device 300 can also include a memory unit 304. The memory unit 304 can be any machine readable or computer readable medium capable of storing data, including electrical and non-electrical memory, and can be the same as or similar to the memory unit 204 of FIG. It is noted that some or all of the memory unit 304 may be included on the same integrated circuit of the processor circuit 302, or alternatively, some or all of the memory unit 304 may be disposed at the processor circuit 302. An integrated circuit or other medium external to the integrated circuit such as a hard disk drive. Although memory unit 304 is included within device 300 of FIG. 3, in some embodiments, memory unit 304 can be external to device 300. Embodiments are not limited to this one.

Device 300 can include a decision component 320-1. In some embodiments, decision component 320-1 can be configured to be executed by processor circuit 302 to determine a service ID for local management services of device 300. In various embodiments, the size of the service ID may be smaller than the service name for the general management service. For example, in several embodiments, the general management service can have a length of 64 The octet is the service name in the DNS name format, and the corresponding service ID can be 6 octets in length. Embodiments are not limited to this one.

Device 300 can include a pair of mapping components 320-2. In various embodiments, the mapping component 320-2 can be configured to maintain the service ID mapping information 322 by execution of the processor circuit 302. The service ID mapping information 322 may include information indicating that the service name is mapped to one of the service IDs for the local management service of the device 300. In some embodiments, for a given service ID, the service ID mapping information 322 can indicate a service name for one of the services identified by the service ID. In various embodiments, device 300 is operative to store service ID mapping information 322 in memory unit 304. Embodiments are not limited to this one.

FIG. 3 also illustrates an embodiment of a system 340. System 340 can include device 300 and transceiver 344. Transceiver 344 can include one or more radios capable of transmitting and receiving signals using various suitable wireless communication technologies, and can be the same as or similar to transceiver 244 of FIG. Embodiments are not limited to this one.

In normal operation, device 300 and/or system 340 is operable to generate a service ID 326 for a service 307 and maintain service ID mapping information 322 for a service ID 326 that is associated with service 307.

In some embodiments, service 307 can include a local management service provided by device 300 and/or system 340. In various embodiments, the service name 324 can include one of the services 307 service names. In several embodiments, the service name 324 can include a relatively long string of characters. For example, in various embodiments, the service name 324 can include a DNS name of length 64 octets. The format of the service name. In one embodiment, the service 307 includes a social networking application called "My Face", and the service name 324 can include the string "MyFace.SocialNetwork.Apps". Embodiments are not limited to this one.

In several embodiments, decision component 320-1 is operative to determine one of service 326 for service 307. In various embodiments, service ID 326 can include a relatively short value. For example, in several embodiments, service ID 326 can include a string of characters or a value of 6 octets in length. In various embodiments, service ID 326 can include a general/local management (U/L) bit 328. U/L bit 328 may contain a bit indicating whether the service 307 identified by service ID 326 is general or local, and may be the same or similar to U/L bit 228 of FIG. In several embodiments, decision component 320-1 is operable to determine service ID 326 such that U/L bit 328 has a value indicating that service 307 is a local management service. Embodiments are not limited to this one.

In various embodiments, decision component 320-1 is operative to determine service ID 326 based on a hash algorithm 321 . The hash algorithm 321 can include an algorithm to convert a string of characters, such as the service name 324, into a shorter string, a sequence of bits, or a value. In some embodiments, the hash algorithm 321 can be selected based on the defined length of the service name 324 and the service ID 326. For example, in various embodiments, one of the service names 324 has a defined format that includes 64 octets, and one of the service IDs 326 has a defined format that includes 6 octets including U/L bits 328, a hash algorithm 321 can be selected to convert a 64 octet string to a 47 bit value. Embodiments of the hash algorithm 321 may include a SHA-1 hash function, a SHA-256 hash function, and a SHA-512 hash function. a hash function of the formula, or any other suitable type. Embodiments are not limited to this one.

In some embodiments, decision component 320-1 is operative to hash service name 324 according to hash algorithm 321 and to append U/L bit 328 to the result to obtain service ID 326. In the foregoing embodiment, wherein the service name 324 includes the string "MyFace.SocialNetwork.Apps", the decision component 320-1 is operable to determine that a service ID 326 includes a hexadecimal value "AF71 C289 EE01", which is in the The "1" value in one element indicates that service 307 is a local management service, while the remaining 47 bits contain the result produced by hash algorithm 321 . An advantage of various embodiments may be that the service ID 326 is determined by the hash service name 324, and the probability of a service ID 326 being matched to a different service determinant having a different service name may be minimized. For example, if one of the service IDs 326 contains a 47-bit plus U/L bit 328 in a defined format, then the probability that the second different service name will also be hashed to the service ID 326 will typically be about 2 ⁴⁷ . Thus, the usage permission of the hash algorithm 321 generates a service ID 326 that will be extremely likely to be unique within the wireless network 100 even if the generation of the service ID 326 does not consult the service ID of other services within the wireless network 100. This is the case. Embodiments are not limited to this one.

In several embodiments, the mapping component 320-2 is operable to map the service name 324 to the service ID 326 that has been determined for the service 307. In various embodiments, the mapping component 320-2 is operable to generate a service ID mapping entry 323 in the service ID mapping information 322 and to map the service name 324 to the service ID 326. The service ID mapping entry 323 may include an information indicating that the service ID 326 refers to a local management service corresponding to the service name 324. In the foregoing embodiment The medium service 307 includes a social network application, and the service ID mapping entry 323 may include a information indicating service ID "AF71 C289 EE01" which refers to the application and corresponds to the service name "MyFace.SocialNetwork.Apps". Embodiments are not limited to this one.

In some embodiments, wireless device 104 can include a device that also provides service 307. In various embodiments, the wireless device is operable to determine other wireless devices that provide service 307 in wireless network 100. In some embodiments, instead of using the service name 324 of the service 307 to scan for such wireless devices, the wireless device 104 is operable to scan for the wireless device providing the service 307 based on the service ID 326 for the service 307. For example, in various embodiments, the wireless device is operable to determine the service ID 326 using the hash algorithm 321 and is then operable to broadcast a scan box 330 containing one of the service IDs 326. Processor circuit 302 of device 300 and/or system 340 is then operable to determine that device 300 and/or system 340 provides service 307 based on service ID mapping entries 323, and may indicate that service 307 is a locally available message. The wireless device 104 is answered. In some embodiments, the use of service ID 326 may cause wireless device 104 to conserve power, bandwidth, and/or other transmission resources because scan box 330 is sized to match the known method where the service name is included in the scan. The inside of the box can be reduced. Embodiments are not limited to this one.

One or more representative logic flows representing exemplary approaches for performing the novel aspects of the disclosed architecture are included herein. Although one or more of the methods shown herein are shown and described as a series of acts for the purpose of illustration, those skilled in the art will understand and appreciate that the methods are not limited to the order of the acts. Accordingly, some actions can be shown here and The different sequences described occur and/or occur simultaneously. For example, those skilled in the art will appreciate that the method of consciousness can be additionally represented as a series of interrelated related states or events, such as in a state diagram. Moreover, not all of the acts exemplified in one method are novel and desirable.

A logic flow can be implemented in software, firmware, and/or hardware. In software and firmware embodiments, a logic flow may be implemented by computer executable instructions stored on non-transitional computer readable media or machine readable media such as optical, magnetic or semiconductor storage devices. Embodiments are not limited to this one.

4 illustrates an embodiment of a logic flow 400 that may represent operations performed by one or more embodiments described herein. For example, FIG. 4 may illustrate operations performed by device 200 and/or system 240 of FIG. 2 in accordance with various embodiments. As shown in FIG. 4, at 402, a service name of one of the general management services can be received. For example, device 200 and/or system 240 of FIG. 2 may receive service name 224 corresponding to service 103 from wireless device 102. At 404, a unique service ID can be assigned to the general management service identified by the service name. For example, the management component 220-1 of FIG. 2 is operable to dispatch a unique service ID 226 to the service 103. At 406, the service ID can be mapped to the service name for the general management service. For example, the management component 220-2 of FIG. 2 is operable to generate a service ID mapping entry 223 for the service ID mapping information 222 indicating that the service ID 226 corresponds to the service name 224 and the service 103. Embodiments are not limited to this one.

FIG. 5 illustrates an embodiment of a logic flow 500 that may represent operations performed by one or more embodiments described herein. For example, Figure 5 It may represent operations performed by device 300 and/or system 340 of FIG. 3 in accordance with several embodiments. As shown in FIG. 5, at 502, a service name of one of the local management services can be determined. For example, decision component 320-1 of FIG. 3 is operable to determine a service name 324 for one of local management services 307. At 504, the hash value can be obtained from the hash service name by the hash algorithm. For example, decision component 320-1 of FIG. 3 is operable to determine a hash value based on hash algorithm 324 based on hash algorithm name 324. At 506, a service ID for one of the local management services can be determined by appending a U/L bit to the hash value. For example, decision component 320-1 of FIG. 3 is operable to determine service ID 326 by appending U/L bit 328 to the hash value, and U/L bit 328 can indicate that service 307 is a local management service. At 508, the service ID can be mapped to the service name. For example, the mapping component 320-2 of FIG. 3 is operable to generate a service ID mapping entry 323 for the service ID mapping information 322 indicating that the service ID 326 corresponds to the service name 324 and the local management service 307. Embodiments are not limited to these examples.

FIG. 6 illustrates an embodiment of a storage medium 600. Storage medium 600 can include a manufactured article. In one embodiment, storage medium 600 may comprise any non-transitional computer readable medium or machine readable medium, such as an optical, magnetic or semiconductor storage device. The storage medium can store various types of computer executable instructions, such as one or both of the present logic flow 400 and the logic flow 500. Embodiments of computer readable or machine readable storage media may include any tangible medium capable of storing electronic material, including electrical or non-electrical memory, removable or non-removable memory, Memory, writable or non-writable memory can be erased or not erased. Embodiments of computer executable instructions may include any suitable type of code, such as source code, Compilation code, de-decoding, executable code, static code, dynamic code, object-oriented code, visual code, and so on. Embodiments are not limited to this one.

FIG. 7 illustrates one embodiment of a communication device 700 for a wireless network, such as wireless network 100 of FIG. Device 700 can be embodied, for example, as device 200, system 240, device 300, system 340, storage medium 600, and/or a logic circuit 728. Logic circuit 728 can include physical circuitry to perform operations such as described for device 200 or device 300. As shown in FIG. 7, device 700 can include a radio interface 710, a baseband circuit 720, and a computing platform 730, although embodiments are not limited to such configurations.

The apparatus 700 can be internal to a single computing entity, such as all or a portion of its structure and/or operation for the device 200, the system 240, the device 300, the system 340, the storage medium 600, and/or a logic circuit 728, within a single device. In addition, apparatus 700 can utilize the following decentralized system architecture to distribute portions of its structure and/or operation for device 200, system 240, device 300, system 340, storage medium 600, and/or logic circuit 728 across multiple computing entities. Such as client-server architecture, three-tier architecture, N-tier architecture, tightly coupled or cluster architecture, peer-to-peer architecture, guest-host architecture, shared database architecture, and other types of decentralized systems. Embodiments are not limited to this one.

In one embodiment, the radio interface 710 can include a single carrier or multi-carrier modulated signal (eg, including complementary code keying (CCK) and/or orthogonal frequency division multiplexing (OFDM) symbols) for transmitting and/or receiving. A component or combination of components, but embodiments are not limited to any particular air permeable interface or modulation scheme. The radio interface 710 can include, for example, a receiver 712, a frequency A rate synthesizer 714, and/or a transmitter 716. The radio interface 710 can include a bias control, a crystal oscillator, and/or one or more antennas 718-f. In another embodiment, the radio interface 710 can use an external voltage controlled oscillator (VCO), a surface acoustic wave filter, an intermediate frequency (IF) filter, and/or an RF filter, if desired. Due to the various potential RF interface designs, the extension description is removed.

The baseband circuit 720 can be in communication with the radio interface 710 to process the received and/or transmitted signals, and can include, for example, an analog-to-digital converter 722 for downconverting the received signals for upconverting the signals for transmission to the digital Analog converter 724. Again, baseband circuit 720 can include a baseband or physical layer (PHY) processing circuit 726 for PHY link layer processing for individually receiving/transmitting signals. The baseband circuit 720 can include, for example, a memory access control (MAC) processing circuit 727 for MAC/data link layer processing. The baseband circuit 720 can include a memory controller 732 for communicating with the MAC processing circuitry 727 and/or a computing platform 730 via one or more interfaces 734.

In some embodiments, PHY processing circuit 726 can include a frame construction and/or detection module combining additional circuitry, such as buffer memory to construct and/or deconstruct a communication frame. Additionally or alternatively, the MAC processing circuitry 727 can share processing for certain such functions, or perform such processing independently of the PHY processing circuitry 726. In several embodiments, MAC and PHY processing can be integrated into a single circuit.

Computing platform 730 can provide computing functionality for device 700. As shown, computing platform 730 can include a processing component 740. In addition to or in addition to the baseband circuit 720, the apparatus 700 can use the processing component 740 to perform for the device 200, system 240, device 300, system 340, storage medium 600, and/or logic The processing operations or logic of circuit 728. Processing component 740 (and/or PHY 726 and/or MAC 727) can include various hardware components, software components, or a combination of both. Embodiments of hardware components can include devices, logic devices, components, processors, microprocessors, circuits, processor circuits (eg, processor circuit 120), circuit components (eg, transistors, resistors, capacitors, inductors, etc.) ), integrated circuit, application-specific integrated circuit (ASIC), programmable logic device (PLD), digital signal processor (DSP), field programmable gate array (FPGA), memory unit, logic gate, temporary memory , semiconductor devices, wafers, microchips, wafer sets, and the like. Examples of software components may include software components, programs, applications, computer programs, applications, system programs, software development programs, machine programs, operating system software, mediation software, firmware, software modules, routines, and secondary , function, method, program, software interface, application programming interface (API), instruction set, calculation code, computer code, code segment, computer code segment, character, value, symbol, or any of them combination. Deciding whether an embodiment uses hardware components and/or software components can now be visually expected for a given one, depending on any number of factors, such as desired calculation rate, power level, heat resistance, processing cycle budget, input Data rate, output data rate, memory resources, data bus speed and other design or performance limitations.

Computing platform 730 can further include other platform components 750. Other platform components 750 include common computing components, such as one or more processors, multi-core processors, coprocessors, memory cells, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, Audio card, multimedia input/output (I/O) components (eg digital display), power supply Wait. Embodiments of the memory unit can include, but are not limited to, various types of computer readable and machine readable storage media in one or more higher speed memory units, such as read only memory (ROM), random access memory. Body (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM) synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrical Erase programmable ROM (EEPROM), flash memory, polymer memory such as ferroelectric polymer memory, chalcogen memory, phase change or ferroelectric memory, germanium-oxide-nitride-oxide- SONOS memory, magnetic or optical cards, arrays of devices such as Redundant Array of Independent Disks (RAID) drives, solid state memory devices (such as USB memory, Solid State Drives (SSD)), and any device suitable for storing information Other types of media.

The device 700 can be, for example, an ultra mobile device, a mobile device, a fixed device, a machine to machine (M2M) device, a personal digital assistant (PDA), a mobile computing device, a smart phone, a telephone, a digital phone, a cell phone, a user. Equipment, e-book reader, mobile phone, one-way pager, two-way pager, communication device, computer, personal computer (PC), desktop computer, laptop computer, notebook computer, small notebook computer, handheld computer , tablet, server, server array or server farm, web server, web server, internet server, workstation, mini computer, mainframe computer, supercomputer, network facility, web facility, decentralized Computer systems, multiprocessor systems, processor-based systems, consumer electronics, programmable consumer electronics, gaming devices, televisions, digital TVs, set-top boxes, wireless access points, base stations, Node B , user station, mobile user center, none Line grid controller, router, hub, gateway, bridge, switch, machine, or a combination thereof. Accordingly, the functions and/or specific configurations of the apparatus 700 described herein can be included in or deleted from various embodiments of the apparatus 700 as desired.

Embodiments of device 700 may be implemented using a single input single output (SISO) architecture. However, some of the adaptive antenna technologies that may now include the use of bundled or spatially split multidirectional access (SDMA) and/or multiple antennas (eg, antenna 718-f) for transmitting and/or receiving using MIMO communication techniques. .

The components and features of device 700 can be implemented using any combination of discrete circuits, application specific integrated circuits (ASICs), logic gates, and/or single chip architectures. Again, if appropriate, the features of device 700 can be implemented using a microcontroller, a programmable logic array, and/or a microprocessor, or any combination of the foregoing. It should be noted that hardware, firmware and/or software components may be referred to herein as "logic" or "circuitry" collectively or individually.

It will be appreciated that the example apparatus 700 shown in the block diagram of FIG. 7 can represent a number of potentially functional one illustrative embodiments. Accordingly, the partitioning, deletion, or inclusion of the functions of the blocks depicted in the drawings are not intended to necessarily exclude, delete, or be included in the implementation of such hardware components, circuits, software, and/or components for performing such functions. In the example.

The following examples are related to further embodiments:

Embodiment 1 is at least one machine readable medium comprising a plurality of instructions responsive to execution on a computing device such that the computing device determines a service name for one of the services in a wireless network; determining one for the service Service identifier (ID), the service ID contains less than one number of bits A one-digit number included in the service name for the service; and generating a service ID mapping information to map the service ID to the service name.

In Embodiment 2, the service ID of Embodiment 1 may optionally include a Universal/Local Management (U/L) bit indicating that the service includes one of a general management service or a local management service.

In Embodiment 3, the service of Embodiment 2 can optionally include a general management service, and the U/L bit can optionally include a value indicating that the service includes a general management service.

In embodiment 4, the at least one machine readable medium of embodiment 3 can optionally include service management instructions responsive to execution on the computing device such that the computing device determines the service for the service The ID makes the service ID unique within the wireless network.

In embodiment 5, the at least one machine readable medium of any of embodiments 3 to 4 can optionally include service management instructions responsive to execution on the computing device such that the computing device receives A service ID query is identified for one of the service names, and the service ID is sent in response to the service ID query.

In embodiment 6, the service of embodiment 2 can optionally include a local management service, and the U/L bit can optionally include a value indicating that the service includes a local management service.

In embodiment 7, the at least one machine readable medium of embodiment 6 can optionally include service management instructions responsive to execution on the computing device such that the computing device is responsive to the hash function The service name generates a hash value and generates the service ID based on the hash value.

In embodiment 8, the at least one machine readable medium of embodiment 7 can optionally include service management instructions responsive to execution on the computing device such that the computing device lends the U/L bit The service ID is generated by the hash to the hash value.

In Embodiment 9, the hash function of any one of Embodiments 7 to 8 includes a Secure Hash Algorithm 1 (SHA-1) hash function, a SHA-256 hash function, or a SHA-512 hash. Function.

In embodiment 10, the at least one machine readable medium of any of embodiments 7 to 9 can optionally include service management instructions responsive to execution on the computing device such that the computing device receives A scan box containing one of the service IDs, and in response to the scan box, sends a message indicating that the service is locally available.

In Embodiment 11, the wireless network of any of Embodiments 1 to 10 can optionally include a Wi-Fi Direct Connect network.

In embodiment 12, the service name of any of embodiments 1 to 11 may optionally include a Domain Name System (DNS) string format.

In Embodiment 13, the service name of any of Embodiments 1 to 12 may optionally include 64 octets.

In Embodiment 14, the service ID of any of Embodiments 1 to 13 may optionally include 6 octets.

In embodiment 15, the U/L bit of any of embodiments 1 to 14 can optionally include one of the first bits of the service ID.

In embodiment 16, the U/L bit of any of embodiments 1 to 15 may optionally include one of the last bits of the service ID.

Embodiment 17 is a service management device including a processor circuit; a management component executed by the processor circuit to determine a service name for a service in a wireless network and determine a service identification for the service (ID), the service ID contains one of the number of bits less than a one-digit number included in the service name for the service; and a pair of mapping components to be executed by the processor circuit to generate a service The ID maps the information and maps the service ID to the service name.

In embodiment 18, the service ID of embodiment 17 can optionally include a universal/local management (U/L) bit indicating that the service comprises one of a general management service or a local management service.

In embodiment 19, the service of embodiment 18 can optionally include a general management service, and the U/L bit can optionally include a value indicating that the service includes a general management service.

In embodiment 20, the management component of embodiment 19 is selectively executable by the processor circuit to determine the service ID for the service such that the service ID is unique within the wireless network.

In embodiment 21, the management component of any one of embodiments 19 to 20 is selectively executable by the processor circuit to receive a service ID query identifying the service name, and to send the response in response to the service ID query Service ID.

In embodiment 22, the service of embodiment 18 can optionally include a local management service, and the U/L bit can optionally include a value indicating that the service includes a local management service.

In embodiment 23, the management component of embodiment 22 is optional The processor circuit is operative to generate a hash value for the service name based on a hash function and to generate the service ID based on the hash value.

In embodiment 24, the management component of embodiment 23 is selectively executable by the processor circuit to generate the service ID by appending the U/L bit to the hash value.

In embodiment 25, the hash function of any one of embodiments 23 to 24 includes a Secure Hash Algorithm 1 (SHA-1) hash function, a SHA-256 hash function, or a SHA-512 hash. Function.

In embodiment 26, the management component of any one of embodiments 23 to 25 is selectively executable by the processor circuit to receive a scan box containing the service ID, and to send a message in response to the scan frame Indicates that the service is locally available.

In embodiment 27, the wireless network of any of embodiments 17 to 26 can optionally include a Wi-Fi Direct Connect network.

In embodiment 28, the service name of any of embodiments 17 to 27 can optionally include a Domain Name System (DNS) string format.

In embodiment 29, the service name of any of embodiments 17 to 28 may optionally include 64 octets.

In embodiment 30, the service ID of any of embodiments 17 to 29 may optionally include 6 octets.

In embodiment 31, the U/L bit of any of embodiments 17 to 30 can optionally include one of the first bits of the service ID.

In embodiment 32, the U/L bit of any of embodiments 17 to 31 can optionally include one of the last bits of the service ID.

Embodiment 33 is a system comprising the service management device of any one of embodiments 17 to 32, a display, a radio frequency (RF) transceiver, and one or more RF antennas.

Embodiment 34 is a service management method, including determining a service name for a service in a wireless network; determining a service identifier (ID) for the service, the service ID including one of the number of bits is less than a one-digit number within the service name for the service; and generating a service ID mapping information to map the service ID to the service name.

In embodiment 35, the service ID of embodiment 34 can optionally include a universal/local management (U/L) bit indicating that the service comprises one of a general management service or a local management service.

In embodiment 36, the service of embodiment 35 can optionally include a general management service, and the U/L bit can optionally include a value indicating that the service includes a general management service.

In embodiment 37, the service management method of embodiment 36 can optionally include determining the service ID for the service such that the service ID is unique within the wireless network.

In embodiment 38, the service management method of any one of embodiments 36 to 37 can optionally include receiving a service ID query identifying the service name and transmitting the service ID in response to the service ID query.

In embodiment 39, the service of embodiment 35 can optionally include a local management service, the U/L bit optionally including a value indicating that the service includes a local management service.

In Embodiment 40, the service management method of Embodiment 39 is optional. Optionally, generating a hash value for the service name based on a hash function and generating the service ID based on the hash value.

In embodiment 41, the service management method of embodiment 40 can optionally include generating the service ID by appending the U/L bit to the hash value.

In Embodiment 42, the hash function of any one of Embodiments 40 to 41 includes a Secure Hash Algorithm 1 (SHA-1) hash function, a SHA-256 hash function, or a SHA-512 hash. Function.

In the embodiment 43, the service management method of any one of embodiments 40 to 42 can optionally include receiving a scan box including the service ID, and in response to the scan box, sending a message indicating that the service system is local available.

In embodiment 44, the wireless network of any of embodiments 34 to 43 can optionally include a Wi-Fi Direct Connect network.

In embodiment 45, the service name of any of embodiments 34 to 44 can optionally include a Domain Name System (DNS) string format.

In embodiment 46, the service name of any of embodiments 34 to 45 can optionally include 64 octets.

In embodiment 47, the service ID of any of embodiments 34 to 46 may optionally include 6 octets.

In embodiment 48, the U/L bit of any of embodiments 34 to 47 can optionally include one of the first bits of the service ID.

In embodiment 49, the U/L bit of any of embodiments 34 to 48 can optionally include one of the last bits of the service ID.

Embodiment 50 is an apparatus comprising means for performing a service management method as in any one of embodiments 34 to 49.

Embodiment 51 is a system comprising an apparatus as in embodiment 50, a display, a radio frequency (RF) transceiver, and one or more RF antennas.

Embodiment 52 is at least one machine readable medium comprising a plurality of instructions responsive to execution on a computing device such that the computing device performs one of the service management methods of any of embodiments 34-49.

Embodiment 53 is a communication device configuration to perform a service management method as in any one of embodiments 34 to 49.

Embodiment 54 is a service management device, comprising: means for determining a service name for a service in a wireless network; and means for determining a service identifier (ID) for the service, the service ID including The one-digit number is less than the one-digit number included in the service name for the service; and the component used to generate the service ID mapping information to map the service ID to the service name.

In embodiment 55, the service ID of embodiment 54 can optionally include a universal/local management (U/L) bit indicating that the service comprises one of a general management service or a local management service.

In embodiment 56, the service of embodiment 55 can optionally include a general management service, and the U/L bit can optionally include a value indicating that the service includes a general management service.

In embodiment 57, the service management device of embodiment 56 can optionally include means for determining the service ID for the service such that the service ID is unique within the wireless network.

In embodiment 58, the service management device of any one of embodiments 56 to 57 can optionally include means for receiving a service ID query identifying one of the service names, and for transmitting in response to the service ID query The component of the service ID.

In embodiment 59, the service of embodiment 55 can optionally include a local management service, and the U/L bit can optionally include a value indicating that the service includes a local management service.

In embodiment 60, the service management device of embodiment 59 can optionally include means for generating a hash value for the service name based on a hash function, and means for generating the service ID based on the hash value. .

In embodiment 61, the service management device of embodiment 60 can optionally include means for generating the service ID by appending the U/L bit to the hash value.

In embodiment 62, the hash function of any one of embodiments 60 to 61 includes a Secure Hash Algorithm 1 (SHA-1) hash function, a SHA-256 hash function, or a SHA-512 hash. Function.

In embodiment 63, the service management device of any one of embodiments 60 to 62 can optionally include means for receiving a scan box including the service ID, and for transmitting a message indication in response to the scan box This service is a locally available component.

In embodiment 64, the wireless network of any of embodiments 54-63 can optionally include a Wi-Fi Direct Connect network.

In embodiment 65, the service name of any of embodiments 54 to 64 can optionally include a Domain Name System (DNS) string format.

In embodiment 66, the service name of any of embodiments 54 to 65 can optionally include 64 octets.

In embodiment 67, the service ID of any of embodiments 54 to 66 may optionally comprise 6 octets.

In embodiment 68, the U/L bit of any of embodiments 54-67 can optionally include one of the first bits of the service ID.

In embodiment 69, the U/L bit of any of embodiments 54-68 can optionally include one of the last bits of the service ID.

Some embodiments may use the expression "one embodiment" or "an embodiment" along with its derivatives. These terms are meant to be inclusive of the particular features, structures, or characteristics described in connection with the embodiments. The phrase "in one embodiment" is used in the specification and is not necessarily all referring to the same embodiment.

Further, in the preceding and subsequent detailed descriptions and/or claims, the words "coupled" and/or linked may be used together with their derivatives. In a particular embodiment, a link may be used to indicate that two or more elements are in direct physical and/or electrical contact with each other. Coupling may mean that two or more elements are in direct physical and/or electrical contact with each other. However, coupling can also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other. For example, "coupled" may mean that two or more elements are not in contact with each other but are indirectly joined together through another element or intermediate element.

In addition, the word "and/or" may mean "and" and may mean "or", which means "mutual exclusion" or "one", which means "partial but not all", which means "both" No, and/or can mean "both", but this case The scope of the subject matter is not limited to this one. The words "including" and "comprising", along with their derivatives, may be used and are intended to be synonymous with each other.

It is emphasized that the summary description disclosed herein is provided to allow the reader to quickly determine the nature of the technical disclosure. However, it is important to understand that the summary description is not intended to interpret or limit the scope or meaning of the scope of the patent application. In addition, as will be apparent from the foregoing detailed description, a plurality of features are grouped in a single embodiment for the disclosure. This method of disclosure should not be interpreted as reflecting that the embodiments of the claimed invention require more features than those explicitly recited in the claims. Rather, the gist of the present invention has fewer features than all of the features of the single disclosed embodiment, as reflected in the scope of the appended claims. Thus, the claims are intended to be in the In the accompanying patent applications, the terms "including" and "in" are used exclusively as the verbal English equivalents of the individual terms "including" and "in". In addition, the terms "first", "second", "third", etc. are used merely as labels, rather than numerical requirements for their objects.

The foregoing has described embodiments including the disclosed architecture. It is of course impossible to describe every conceivable combination of components and/or methods, but skilled artisans will appreciate that further combinations and permutations may be made. Accordingly, the novel architecture is intended to cover all such changes, modifications and variations that are within the scope of the appended claims.

100‧‧‧Wireless network

102, 104, 106‧‧‧ wireless devices

103, 105, 107‧‧ services

110‧‧‧Management device

112‧‧‧General Management Services Information

Claims (25)

At least one machine readable medium comprising a plurality of instructions responsive to execution on a computing device to cause the computing device to: determine a service name for one of the services in a wireless network; A service identifier (ID) for the service, the service ID including a number of bits, the number of bits being less than the number of bits included in the service name for the service; and generating a service ID mapping information To map the service ID to the service name. The at least one machine readable medium of claim 1 wherein the service ID comprises a universal/local management (U/L) bit indicating that the service comprises one of a general management service or a local management service. The at least one machine readable medium of claim 2, wherein the service comprises a general management service, the U/L bit comprising a value indicating that the service comprises a general management service. At least one machine readable medium of claim 3, comprising instructions responsive to execution on the computing device, such that the computing device determines the service ID for the service such that the service ID is The wireless network is unique inside. At least one machine readable medium as claimed in claim 2, wherein the service includes a local management service, the U/L bit containing a value indicating the service Contains a local management service. The at least one machine readable medium of claim 5, comprising instructions that, in response to being executed on the computing device, cause the computing device to: generate a hash for the service name based on a hash function a value; and generating the service ID based on the hash value. The at least one machine readable medium of claim 6, wherein the hash function comprises a Secure Hash Algorithm 1 (SHA-1) hash function, a SHA-256 hash function, or a SHA-512 hash function . At least one machine readable medium as claimed in claim 1, wherein the wireless network comprises a Wi-Fi Direct Connect network. An apparatus for wireless network service discovery, comprising: a processor circuit; a management component for executing by the processor circuit to determine a service name for one of a service in a wireless network, and Determining a service identifier (ID) for the service, the service ID containing a number of bits, the number of bits being less than the number of bits included in the service name for the service; and a pair of mapping components, It is executed by the processor circuit to generate a service ID mapping information, and the service ID is mapped to the service name. The device of claim 9, wherein the service ID comprises a universal/local management (U/L) bit indicating that the service comprises one of a general management service or a local management service. The device of claim 10, wherein the service comprises a general management service, the U/L bit comprising a value indicating that the service comprises a general management service. The device of claim 11, wherein the management component is configured to execute by the processor circuit to determine the service ID for the service such that the service ID is unique within the wireless network. The device of claim 10, wherein the service comprises a local management service, the U/L bit comprising a value indicating that the service comprises a local management service. The device of claim 13, wherein the management component is configured to execute by the processor circuit to generate a hash value for the service name based on a hash function and generate the service ID based on the hash value. The device of claim 14, wherein the hash function comprises a Secure Hash Algorithm 1 (SHA-1) hash function, a SHA-256 hash function, or a SHA-512 hash function. The device of claim 9, wherein the wireless network comprises a Wi-Fi Direct Connect network. The device of claim 9, comprising: a display; a radio frequency (RF) transceiver; and one or more RF antennas. A method for wireless network service discovery, comprising the steps of: determining a service name for one of a service in a wireless network; Determining a service identifier (ID) for the service, the service ID containing a number of bits, the number of bits being less than the number of bits included in the service name for the service; and generating a service ID mapping Information to map the service ID to the service name. The method of claim 18, wherein the service ID comprises a universal/local management (U/L) bit indicating that the service comprises one of a general management service or a local management service. The method of claim 19, wherein the service comprises a general management service, the U/L bit comprising a value indicating that the service comprises a general management service. The method of claim 20, comprising determining the service ID for the service such that the service ID is unique within the wireless network. The method of claim 19, wherein the service comprises a local management service, the U/L bit comprising a value indicating that the service comprises a local management service. The method of claim 22, comprising: generating a hash value for the service name based on a hash function; and generating the service ID based on the hash value. The method of claim 23, wherein the hash function comprises a Secure Hash Algorithm 1 (SHA-1) hash function, a SHA-256 hash function, or a SHA-512 hash function. The method of claim 18, wherein the wireless network comprises a Wi-Fi Direct network.