WO2017105071A1 - Method and apparatus for performing service discovery using nfc in wireless communication system - Google Patents

Abstract

The present specification may provide a method by which a terminal performs service discovery in a wireless communication system. The method for performing service discovery may comprise the steps of: a first terminal transmitting a handover request message to a second terminal using near field communication (NFC); and the first terminal receiving a handover selection message from the second terminal using NFC. Connection capability exchange (CCEX) information can be included in the handover request message and the handover selection message.

Description

Method and apparatus for performing service discovery using NFC in wireless communication system

The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for performing service discovery using near field communication (NFC) in a wireless communication system.

Wireless communication systems are widely deployed to provide various kinds of communication services such as voice and data. In general, a wireless communication system is a multiple access system capable of supporting communication with multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency (SC-FDMA). division multiple access (MCD) systems and multi-carrier frequency division multiple access (MC-FDMA) systems.

In addition, with the development of information and communication technology, various wireless communication technologies have been developed. Among these, WLAN is based on radio frequency technology, and can be used in homes, businesses, or businesses by using portable terminals such as personal digital assistants (PDAs), laptop computers, and portable multimedia players (PMPs). It is a technology that allows wireless access to the Internet in a specific service area.

Standards for Wireless Local Area Network (WLAN) technology are being developed by the Institute of Electrical and Electronics Engineers (IEEE) 802.11 group. IEEE 802.11a and b use an unlicensed band at 2.4. GHz or 5 GHz, IEEE 802.11b provides a transmission rate of 11 Mbps, and IEEE 802.11a provides a transmission rate of 54 Mbps. IEEE 802.11g applies Orthogonal Frequency Division Multiplexing (OFDM) at 2.4 GHz to provide a transmission rate of 54 Mbps. IEEE 802.11n provides a transmission rate of 300 Mbps by applying multiple input multiple output OFDM (MIMO-OFDM). IEEE 802.11n supports a channel bandwidth of up to 40 MHz, in which case it provides a transmission rate of 600 Mbps. IEEE 802.11p is a standard for supporting WAVE (Wireless Access in Vehicular Environments). For example, 802.11p provides the improvements needed to support Intelligent Transportation Systems (ITS). IEEE 802.11ai is a standard for supporting fast initial link setup of an IEEE 802.11 station (STA).

The DLS (Direct Link Setup) related protocol in a wireless LAN environment according to IEEE 802.11e is based on QBSS (Quality BSS) in which a Basic Service Set (BSS) supports Quality of Service (QoS). In QBSS, not only non-AP STAs but also APs are QAPs (Quality APs) supporting QoS. However, in the currently commercialized WLAN environment (for example, WLAN environment according to IEEE 802.11a / b / g), the AP supports QoS even if the Non-AP STA is a QSTA (Quality STA) supporting QoS. Most legacy APs do not. As a result, even in the currently commercialized wireless LAN environment, even if the QSTA, there is a limit that can not use the DLS service.

Recently, wireless short-range communication technologies such as Wi-Fi are widely applied to the market, and the connection between devices is not only based on a local network but also through a direct connection between devices. One of the direct connection technologies between devices using Wi-Fi is Wi-Fi Direct.

Wi-Fi Direct is a network connectivity standard that describes the operation of the link layer. There is no definition of a protocol or standard for the application at the upper level, which makes the compatibility and operation inconsistent when the application is run after being connected between Wi-Fi Direct devices. Because of this problem, the Wi-Fi Alliance (WFA) is currently working on a standard technology that includes a higher-level application technology called Wi-Fi Direct Services (WFDS).

WFA has announced a new standard for delivering data through direct connections between mobile devices called Wi-Fi Direct, and the industry is actively developing technology to meet the Wi-Fi Direct specification. In a strict sense, Wi-Fi Direct corresponds to a trade name as a marketing term, and the technical specification for this is collectively referred to as Wi-Fi P2P (Peer to Peer). Accordingly, in the present invention dealing with Wi-Fi based P2P technology, Wi-Fi Direct or Wi-Fi P2P may be used without distinction. In a conventional Wi-Fi network, a method of accessing an Internet network after accessing through an AP (Access Point) was a general method of using a Wi-Fi equipped device. The method of data communication through direct connection between devices has been used by some users because it has been installed in devices such as mobile phones and notebook PCs equipped with wireless communication technologies such as Bluetooth, but the transmission speed is slow and the actual use has a long transmission distance. It is limited to within 10m. In particular, there are technical limitations in the haptic performance when used in an environment where a large amount of data transmission or a large number of Bluetooth devices exist.

On the other hand, Wi-Fi P2P has been added to support direct communication between devices while retaining most of the features of the existing Wi-Fi standard. Therefore, there is an advantage in that the device equipped with the Wi-Fi chip can fully utilize hardware and physical characteristics, and provide P2P communication between devices mainly by upgrading software functions.

As is widely known, devices equipped with Wi-Fi chips are expanding to a wide variety of ranges, such as note PCs, smartphones, smart TVs, game consoles, cameras, etc., and a sufficient number of suppliers and technical development personnel are formed. However, software development that supports the Wi-Fi P2P specification has not yet been activated, because even if the Wi-Fi P2P specification is released, related software that can easily utilize the specification cannot be distributed.

In the P2P group, there is a device that plays the role of an AP in an existing infrastructure network. In the P2P standard, the device is called a P2P group owner (GO). Various P2P clients may exist around P2P GO. Only one GO can exist in one P2P group, and all other devices become client devices.

In addition, recently, the use of NFC (Near Field Communication) is increasing, and there is a need for a method of providing a service in an environment in which a plurality of systems or interfaces are provided.

The present disclosure relates to a method of performing service discovery using NFC in a wireless communication system.

The present specification relates to a method for performing service discovery through NFC based on an application service platform (ASP) in a wireless communication system.

The present specification relates to a method for providing information exchanged when performing service discovery using NFC in a wireless communication system.

The present disclosure relates to a method of exchanging information on a connection capability via NFC to perform a service connection in a wireless communication system.

According to one embodiment of the present specification, a method for performing a service discovery by a terminal in a wireless communication system can be provided. In this case, the method for performing the service discovery, the first terminal transmits the handover request message to the second terminal using the Near Field Communication (NFC), the first terminal using the NFC, the second handover selection message to the second terminal It may include receiving from the terminal. In this case, the handover request message and the handover selection message may include connection capability exchange (CCEX) information.

According to one embodiment of the present specification, a first terminal for performing service discovery in a wireless communication system may be provided. In this case, the first terminal may include a receiving module for receiving information from an external device, a transmitting module for transmitting information to the external device, and a processor for controlling the receiving module and the transmitting module. In this case, the processor may transmit a handover request message to the second terminal using Near Field Communication (NFC) and receive a handover selection message from the second terminal using NFC. In this case, the handover request message and the handover selection message may include connection capability exchange (CCEX) information.

In addition, the following may be commonly applied to a method and apparatus for performing service discovery using NFC in a wireless communication system.

According to one embodiment of the present specification, the CCEX information may include a first bit indicating whether a P2P connection is supported and a second bit indicating whether an infrastructure connection is supported. have.

In this case, according to an embodiment of the present specification, when the first bit indicates that the P2P connection is supported, the handover request message and the handover selection message may include a Wi-Fi P2P Carrier configuration record. ) May be further included.

At this time, according to one embodiment of the present specification, the Wi-Fi P2P carrier setting record may include attribute information on a P2P connection.

In addition, according to one embodiment of the present specification, when the second bit indicates that the infrastructure connection is supported, the handover request message and the handover selection message may include a Wi-Fi infrastructure carrier configuration record (Wi-Fi Infrastructure Carrier). configuration record) may be further included.

In this case, according to an embodiment of the present specification, the Wi-Fi infrastructure carrier configuration record may include attribute information on an infrastructure connection.

In addition, according to one embodiment of the present specification, CCEX information may be included in a verb record in a handover request message and a handover selection message.

In addition, according to one embodiment of the present specification, flag information may be further included in the handover request message and the handover selection message.

In this case, according to an embodiment of the present specification, the flag information may include a seek bit and a provide bit.

In this case, according to an embodiment of the present specification, the search bit may be a bit indicating whether a service is requested, and the providing bit may be a bit indicating whether a service is provided.

In this case, according to one embodiment of the present specification, when the search bit indicates that the service is requested and the provision bit indicates that the service is not provided, the terminal is a terminal that searches for the service identified by the service hash, The message transmitted by the terminal may be a handover request message.

Further, according to one embodiment of the present specification, when the search bit does not indicate to request a service but the provision bit indicates to provide a service, the terminal is a terminal that advertises a service identified by the service hash, The message transmitted by the terminal may be a handover selection message.

In addition, according to one embodiment of the present specification, the handover selection message may include service hash and advertisement ID information.

In addition, according to one embodiment of the present specification, when the search bit indicates to request a service and the provide bit indicates to provide a service, the terminal searches for a service identified by the first service hash, and 2 The service identified by the service hash can be advertised.

The present disclosure may provide a method of performing service discovery using NFC in a wireless communication system.

The present disclosure may provide a method of performing service discovery through NFC based on an application service platform in a wireless communication system.

The present disclosure may provide a method for providing information exchanged when performing service discovery using NFC in a wireless communication system.

The present disclosure may provide a method of exchanging information on a connection capability through NFC to perform a service connection in a wireless communication system.

Effects obtained in the present specification are not limited to the above-mentioned effects, and other effects not mentioned above may be clearly understood by those skilled in the art from the following description. will be.

1 illustrates a structure of an IEEE 802.11 system to which the present invention can be applied.

2 is a block diagram illustrating exemplary operation of a communication system employing access devices and wireless user devices.

3 illustrates a Wi-Fi Direct (WFD) network.

4 illustrates a process of configuring a WFD network.

5 shows a typical P2P network topology.

FIG. 6 is a diagram illustrating a situation in which one P2P device forms a P2P group and is connected to an AP by operating as an STA of a WLAN.

7 is a diagram illustrating an aspect of a WFD network when P2P is applied.

8 is a simplified block diagram of a Wi-Fi Direct Services (WFDS) device.

FIG. 9 is a view illustrating a process of connecting a WFDS session by discovering devices and discovering services between WFDS devices in a conventional WFDS.

FIG. 10 is a diagram illustrating a service application platform (ASP) supporting a plurality of interfaces.

11 is a block diagram of a service in which an NFC interface is added in addition to the Wi-Fi interface.

12 is a diagram for a method of exchanging an NFC handover request and a handover selection message in a terminal supporting NFC.

13 is a diagram illustrating a message format for an NFC handover message in a terminal supporting NFC.

14 is a diagram illustrating a method of performing service discovery using NFC.

15 illustrates a handover request message and a handover selection message.

16 is a diagram illustrating a method of performing service discovery for a plurality of services using NFC.

17 illustrates a method of using a pre-connected Wi-Fi infrastructure interface.

18 illustrates a method of performing a service connection by forming a P2P group after performing service discovery using NFC.

19 is a flowchart illustrating a method of performing service discovery using NFC.

20 is a block diagram of a terminal device according to one embodiment of the present specification.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings. The detailed description, which will be given below with reference to the accompanying drawings, is intended to explain exemplary embodiments of the present invention and is not intended to represent the only embodiments in which the present invention may be practiced. The following detailed description includes specific details in order to provide a thorough understanding of the present invention. However, one of ordinary skill in the art appreciates that the present invention may be practiced without these specific details.

The following embodiments combine the components and features of the present invention in a predetermined form. Each component or feature may be considered to be optional unless otherwise stated. Each component or feature may be embodied in a form that is not combined with other components or features. In addition, some components and / or features may be combined to form an embodiment of the present invention. The order of the operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.

Specific terms used in the following description are provided to help the understanding of the present invention, and the use of such specific terms may be changed to other forms without departing from the technical spirit of the present invention.

In some instances, well-known structures and devices are omitted or shown in block diagram form, centering on the core functions of each structure and device, in order to avoid obscuring the concepts of the present invention. In addition, the same components will be described with the same reference numerals throughout the present specification.

Embodiments of the present invention may be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802 system, 3GPP system, 3GPP LTE and LTE-A (LTE-Advanced) system and 3GPP2 system. That is, steps or parts which are not described to clearly reveal the technical spirit of the present invention among the embodiments of the present invention may be supported by the above documents. In addition, all terms disclosed in the present document can be described by the above standard document.

The following techniques include code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and the like. It can be used in various radio access systems. CDMA may be implemented with a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA may be implemented with wireless technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented in a wireless technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA).

In addition, terms such as first and / or second may be used herein to describe various components, but the components should not be limited by the terms. The terms are only for the purpose of distinguishing one component from another component, for example, without departing from the scope of rights in accordance with the concepts herein, the first component may be called a second component, and similarly The second component may also be referred to as a first component.

In addition, throughout the specification, when a part is said to "include" a certain component, it means that it can further include other components, except to exclude other components unless otherwise stated. And “…” described in the specification. unit", "… “Unit” refers to a unit that processes at least one function or operation, which may be implemented in a combination of hardware and / or software.

Hereinafter, for the sake of clarity, the following description focuses on the IEEE 802.11 system, but the technical spirit of the present invention is not limited thereto.

1 is a diagram illustrating an exemplary structure of an IEEE 802.11 system to which the present invention can be applied.

The IEEE 802.11 architecture may consist of a plurality of components, and by their interaction, a WLAN may be provided that supports transparent STA mobility for higher layers. The Basic Service Set (BSS) may correspond to a basic building block of an IEEE 802.11 LAN. FIG. 1 illustrates the case where two BSSs (BSS1 and BSS2) exist and each BSS includes two STAs (STA1 and STA2 are included in BSS1 and STA3 and STA4 are included in BSS2). Here, the STA means a device that operates according to the Medium Access Control (MAC) / PHY (Physical) specification of IEEE 802.11. The STA includes an access point (AP) STA (simply an AP) and a non-AP (non-AP) STA. The AP corresponds to a device that provides a network (eg, WLAN) connection to a non-AP STA through an air interface. The AP may be configured in fixed or mobile form and includes a portable wireless device (eg, laptop computer, smart phone, etc.) that provides a hot spot. AP is a base station (BS), Node-B, Evolved Node-B (eNB), Base Transceiver System (BTS), femto base station in other wireless communication fields (Femto BS) and the like. Non-AP STAs generally correspond to devices that users directly handle, such as laptop computers, PDAs, wireless modems, and smartphones. The non-AP STA may include a terminal, a wireless transmit / receive unit (WTRU), a user equipment (UE), a mobile station (MS), a mobile terminal, a mobile subscriber station. (Mobile Subscriber Station, MSS) and the like.

In FIG. 1, an ellipse representing a BSS may be understood to represent a coverage area where STAs included in the BSS maintain communication. This area may be referred to as a basic service area (BSA). The most basic type of BSS in an IEEE 802.11 LAN is an independent BSS (IBS). For example, the IBSS may have a minimal form consisting of only two STAs. In addition, the BSS (BSS1 or BSS2) of FIG. 1, which is the simplest form and other components are omitted, may correspond to a representative example of the IBSS. This configuration is possible when STAs can communicate directly. In addition, this type of LAN may not be configured in advance, but may be configured when a LAN is required, which may be referred to as an ad-hoc network.

The membership of the STA in the BSS may be dynamically changed by turning on or off the STA, entering or exiting the BSS region, or the like. In order to become a member of the BSS, the STA may join the BSS using a synchronization process. In order to access all services of the BSS infrastructure, the STA may be associated with the BSS.

2 illustrates a communication system 200 employing access devices (eg, AP STAs) 202A, 202B, and 202C and wireless user devices (eg, non-AP STAs).

2, access devices 202A-C are connected to a switch 204 that provides a connection to a Wide Area Network (WAN) 206, such as the Internet. Each of the access devices 202A-C provides a wireless connection to wireless devices within a coverage area (not shown) of the access device via a time division multiplexed network. Thus, access devices 202A-C jointly provide the entire WLAN coverage area of system 200. For example, the wireless device 208 may be within the coverage area of the access devices 202A and 202B at the location indicated by the box marked with a solid line. Thus, the wireless device 208 can receive beacons from each of the access devices 202A and 202B, such as the solid arrows 21OA and 21OB. When the wireless device 208 roams from the solid line box to the dashed box, the wireless device 208 enters the coverage area of the access device 202C and exits the coverage area of the access device 202A. Thus, wireless device 208 may receive beacons from access devices 202B and 202C, such as dashed arrows 212A and 212B.

When the wireless device 208 roams within the entire WLAN coverage area provided by the system 200, the wireless device 208 can determine which access device currently provides the best connection to the wireless device 208. . For example, the wireless device 208 may repeatedly scan the beacons of adjacent access devices and measure the signal strength (eg, power) associated with each of the beacons. Thus, the wireless device 208 can be coupled with an access device that provides an optimal network connection based on the maximum beacon signal strength. The wireless device 208 may use other criteria related to optimal connection. For example, an optimal connection may be associated with more desirable services (eg, content, data rate, etc.).

3 illustrates a Wi-Fi Display (WFD) network.

A WFD network is a network that allows Device to Device (D2D) (or Peer to Peer, P2P) communication with each other without Wi-Fi devices joining home, office, and hotspot networks. As proposed by the Wi-Fi Alliance. Hereinafter, WFD based communication is referred to as WFD D2D communication (simply, D2D communication) or WFD P2P communication (simply, P2P communication). In addition, the WFD P2P performing apparatus is referred to as a WFD P2P apparatus, or simply a P2P apparatus.

Referring to FIG. 3, the WFD network 300 may include at least one Wi-Fi device including a first WFD device 302 and a second WFD device 304. WFD devices include devices that support Wi-Fi, such as display devices, printers, digital cameras, projectors, and smartphones. The WFD device also includes a non-AP STA and an AP STA. In the example shown, the first WFD device 302 is a smartphone and the second WFD device 304 is a display device. WFD devices in the WFD network may be directly connected to each other. Specifically, P2P communication refers to a case in which a signal transmission path between two WFD devices is set directly between corresponding WFD devices without passing through a third device (eg, an AP) or an existing network (eg, accessing a WLAN via an AP). can do. Here, the signal transmission path directly set between the two WFD devices may be limited to the data transmission path. For example, P2P communication may refer to a case where a plurality of non-STAs transmit data (eg, voice / video / text information) without passing through the AP. Signal transmission paths for control information (e.g., resource allocation information for P2P configuration, wireless device identification information, etc.) may be used for WFD devices (e.g., non-AP STA-to-non-AP STA, non-AP STA-to- Set directly between APs, or between two WFD devices (e.g., non-AP STA-to-non-AP STA) via an AP, or an AP and a corresponding WFD device (e.g., AP-to-non-AP STA) # 1, AP-to-non-AP STA # 2).

4 illustrates a process of configuring a WFD network.

Referring to FIG. 4, the WFD network configuration process can be roughly divided into two processes. The first process is a neighbor discovery (ND) procedure (S402a), and the second process is a P2P link establishment and communication process (S404). Through a neighbor discovery process, a WFD device (eg, 302 of FIG. 3) finds another neighboring WFD device (eg, 304 of FIG. 3) within its (wireless) coverage and associates with the WFD device, e.g. For example, information necessary for pre-association can be obtained. Here, pre-connection may mean a second layer pre-connection in a wireless protocol. The information required for pre-connection may include, for example, identification information for the neighboring WFD device. The neighbor discovery process may be performed for each available wireless channel (S402b). Thereafter, the WFD device 302 may perform a process for establishing / communicating a WFD P2P link with another WFD device 304. For example, after the WFD device 302 is connected to the peripheral WFD device 304, the WFD device 304 may determine whether the WFD device 304 is a WFD device that does not satisfy the service requirement of the user. To this end, the WFD device 302 may discover the corresponding WFD device 304 after the second layer pre-connection with the peripheral WFD device 304. If the WFD device 304 does not satisfy the service requirement of the user, the WFD device 302 disconnects the second layer connection established for the WFD device 304 and establishes a second layer connection with another WFD device. Can be set. On the other hand, when the WFD device 304 satisfies the service requirements of the user, the two WFD devices 302 and 304 may transmit and receive signals through the P2P link.

5 shows a typical P2P network topology.

As shown in FIG. 5, a client having a P2P GO and a P2P function may be directly connected or may be connected to a legacy client having no P2P GO and a P2P function.

FIG. 6 is a diagram illustrating a situation in which one P2P device forms a P2P group and is connected to an AP by operating as an STA of a WLAN.

As shown in FIG. 6, the P2P technical standard defines a situation in which a P2P device operates in this mode as a concurrent operation.

In order for a series of P2P devices to form a group, which device is to be a P2P GO is determined by a Group Owner Intent value of a P2P attribute ID. This value can range from 0 to 15. P2P devices exchange this value with each other so that the device with the highest value becomes P2P GO. Legacy devices that do not support Wi-Fi P2P technology may be subordinate to the P2P group, but the functions of the existing devices are limited to the function of infrastructure network access through P2P GO. do.

According to the Wi-Fi P2P specification, P2P devices transmit beacon signals by using Orthogonal Frequency Division Multiplexing (OFDM), so 11a / g / n is used as a Wi-Fi P2P device. Can be.

The P2P specification includes four functions as follows to perform the operation in which the P2P GO and P2P clients are connected.

First, P2P discovery covers technology items such as device discovery, service discovery, group formation, and P2P invitation. Device discovery allows two P2P devices to exchange device related information such as mutual device name or device type through the same channel. Service discovery exchanges information related to the service to be used through P2P. Grouping is the ability to determine which device will be a P2P GO to form a new group. P2P invitation is a function of calling a permanently formed P2P group or joining a P2P device to an existing P2P group.

Second, P2P Group Operation describes the formation and termination of P2P groups, connections to P2P groups, communication within P2P groups, services for P2P client discovery, and the operation of persistent P2P groups. .

Third, P2P power management deals with the P2P device power management method and the signal processing method at the time of the power saving mode.

Finally, Managed P2P Device deals with forming P2P group from one P2P device and simultaneously accessing infrastructure network through WLAN AP.

The characteristics of the P2P group will be described. The P2P group is similar to the existing infrastructure basic service set (BSS) in that P2P GO serves as an AP and a P2P client plays a STA. Therefore, P2P devices must be equipped with software that can act as a GO and a client. P2P devices are distinguished by using P2P device addresses, such as MAC addresses. However, when a P2P device communicates within a P2P group, it uses a P2P interface address to communicate with it. It is not necessary to use a globally unique ID address. The P2P group has a single identifier P2P group ID, which consists of a combination of SSID (Service Set Identifier) and P2P device address of P2P GO. Wi-Fi P2P specification uses WPA2-PSK / AES for security. The life cycle of a P2P group is a one-time (temporary) connection method and a persistent connection method that attempts the same connection again after a certain time. In the case of Persistent group, once the P2P group is formed, each other's role, credentials, SSID, and P2P group ID are cached, and it is possible to quickly connect groups by applying the same connection type when reconnecting. .

The following explains how to connect to Wi-Fi. Wi-Fi devices have a two-phase connection process. First, two P2P devices find each other, and second, a group formation step of determining a role of P2P GO or P2P client between the devices found. First, the discovery step is to connect the P2P devices to each other, which is composed of a detailed search and listen state. The search state conducts active searches using a probe request frame, which uses social channels of channels 1, 6, and 11 to limit the scope of the search for quick search. To search. A P2P device in a listen state selects only one of three social channels and remains in a reception state. If another P2P device receives a probe request frame transmitted in a discovery state, a probe response frame is received. Answer The P2P devices may repeatedly search and listen, respectively, and reach each other's common channels. The P2P device uses a probe request frame and a probe response frame to find a device type, a manufacturer, or a friendly device name to selectively associate with each other after discovering the other party. In addition, service discovery may be used to identify compatible services between devices existing in the P2P device, in order to determine whether a service provided in each device is compatible with other devices. The P2P specification does not specify a specific service discovery standard. P2P device users can search for nearby P2P devices and services and then quickly connect to the device or service they want.

The second step will be described as a group formation step. When the P2P devices complete the find step described above, the existence of the counterpart devices is completed. Based on this, two P2P devices should enter the GO negotiation phase to construct a BSS. This negotiation phase is largely divided into two sub-phases. The first is GO negotiation and the second is Wi-Fi Protected Setup. In the GO negotiation phase, each device negotiates its role as a P2P GO or P2P client and establishes an operating channel for use within the P2P group. In the WPS phase, conventional operations are performed in the existing WPS, such as exchanging PIN information input by a user of a device through a keypad, and a simple setup through a push button. The role of P2P GO within the P2P Group is at the heart of the P2P Group. The P2P GO assigns a P2P interface address, selects the operating channel of the group and sends out a beacon signal containing the various operating parameters of the group. Only P2P GO can transmit beacon signal in P2P group, so P2P device can quickly identify P2P GO and join group in the scan phase. Alternatively, P2P GO may start a P2P group session on its own, or start a session after using the method described in the P2P discovery phase. The value to be a P2P GO that plays such an important role is not a fixed value in any device but can be adjusted by an application or a higher layer service. Therefore, a developer wants to be a P2P GO according to the purpose of each application. You can select the appropriate value.

Next, P2P addressing will be described. The P2P device allocates and uses the P2P interface address using the MAC address within the P2P group session. In this case, the P2P interface address of the P2P GO is a BSSID (BSS Identifier), which is substantially the MAC address of the P2P GO.

The disconnection of the P2P group will be described. If the P2P session is terminated, the P2P GO should inform all P2P clients of the end of the P2P group session through de-authentication. On the P2P client side, you can also disconnect from the P2P GO, which should be disassociated if possible. The P2P GO that receives the client's disconnect request can determine that the P2P client has disconnected. If P2P GO detects an abnormal protocol error from a P2P client or a P2P client that interferes with the P2P group connection, it causes rejection of authentication or denial of association. Record in response and send.

7 is a diagram illustrating an aspect of a WFD network when P2P is applied.

FIG. 7 illustrates an aspect of the WFD network when a new P2P application (eg, social chat, location-based service provision, game linkage, etc.) is applied. Referring to FIG. 7, a plurality of P2P devices 702a to 702d perform P2P communication 710 in a WFD network, and P2P device (s) constituting the WFD network are changed at any time by the movement of the P2P device. The WFD network itself can be newly created or destroyed in dynamic / short time. As such, a feature of the new P2P application portion is that in a dense network environment, P2P communication can be made and terminated dynamically and in a short time between a large number of P2P devices.

8 shows a simplified block diagram of a Wi-Fi Direct Services (WFDS) device.

Wi-Fi Direct MAC layer and higher define a platform for application service called ASP (Application Service Platform). ASPs play a role in session management, command processing of services, and control and security between ASPs between upper applications and lower Wi-Fi Direct. On top of ASP, it supports four basic services defined by WFDS: Send, Play, Display, Print, and the corresponding application and user interface (UI). In this case, the send service refers to a service and an application capable of performing file transfer between two WFDS devices. Play service refers to a streaming service and application for sharing A / V, photo, and music based on DLNA between two WFDS devices. Print services define services and applications that enable printing of documents and photos between a device and a printer device having content such as documents and photos. Display services define services and applications that enable screen sharing between WFA's Miracast Source and Miracast Sink. And enable service is defined to use ASP common platform when supporting third party application besides basic service.

Among the terms described in the present invention, the service hash is formed from the service name by using the first six octets of the service hash algorithm (eg, SHA256) hashing of the service name. The service hash used in the present invention does not mean only a specific one, but is preferably understood as a sufficient representation of the service name using a probe request / response discovery mechanism. For example, if the service name is "org.wifi.example", the first 6 bytes of the hashed value of this service name as SHA256 is the hash value.

The WFDS includes a hash value in the probe request message and, if a service matches, checks whether the service is supported by responding with a probe response message including a service name. That is, the service name is a name of a user readable service in the form of DNS. The service hash value means the upper six bytes of the 256-byte value generated by this service name algorithm (eg SHA256). As in the previous example, if the service name is "org.wifi.example", the service hash may be a value of "4e-ce-7e-64-39-49".

Therefore, in the present invention, a part of the value hashed through the algorithm is expressed as a service hash (information), and may be included in the message as one piece of information.

How to set up an existing WFDS

FIG. 9 is a view illustrating a process of connecting a WFDS session by discovering devices and discovering services between WFDS devices in a conventional WFDS.

For convenience of description, as shown in FIG. 4, device A serves as an advertiser to advertise a WFDS that can be provided to a seeker, and device B serves an advertised service. Assume that it serves to seek. Device A is a device that advertises its own service and the other party seeks to start the service, and device B performs a process of searching for a device supporting the service by a higher application or a user's request.

The service stage of the device A advertises the WFDS that it can provide to the application service platform (ASP) stage of the device A. The service unit of the B device may also advertise the WFDS that it can provide to the ASP of the B device. The device B instructs the service terminal from the application terminal of the device B to use the WFDS as a searcher, and the service terminal instructs the ASP terminal to find the target device to use the WFDS.

The ASP terminal of the B device transmits a peer-to-peer probe request message to find its WFDS target device (S910). At this time, in the P2P probe request message, the service name of the service that the user wants to find or supports can be hashed and put in the form of a service hash. When receiving the P2P probe request message from the searcher, the device A transmits a P2P probe response message to the device B in response to the corresponding service (S920). The P2P probe response message includes the service supported by the service name or the hash value and the corresponding advertisement ID value. This process is a device discovery process in which A device and B device can know whether they are WFDS devices and support services.

Subsequently, the P2P service discovery process may optionally indicate the details of a specific service. The device B, which finds a device capable of WFDS with itself, transmits a P2P service discovery request message to the corresponding device (S930). Receiving the P2P service discovery request message from the device B, the device A matches the service advertised at the service terminal of the device A with the P2P service name and the P2P service information received from the device B at the ASP. The P2P service discovery response message is transmitted to the device (S940). This will use the GAS protocol defined in IEEE 802.11u. When the request for the service search is completed, the device B can inform the application and the user of the search result. Until this point, the Wi-Fi Direct group is not formed, and when a user selects a service and the service performs a connect session, P2P group formation is performed.

In addition, the ASP may be operated based on at least one of Wi-Fi, Wi-Fi Direct, Neighbor Awareness Networking (NAN), Near Field Communication (NFC), and Bluetooth Low Energy (BLE). In this case, the above-described Wi-Fi may be one interface. That is, the interface may refer to a method for supporting the operation of the terminal. In this case, a specific method for interworking with the device / service discovery by the ASP will be described based on the above-described interfaces.

In this case, as an example, the BLE of the above-described interface uses a frequency of 2.4 GHz and may be a Bluetooth transmission / reception scheme in a form of reducing power consumption. That is, it can be used to transmit data while reducing power consumption in order to transmit and receive extremely small amount of data quickly. This will be described later.

In addition, as an example, a NAN (Neighbor Awareness Networking) network includes a NAN terminal using the same set of NAN parameters (for example, a time interval between successive discovery windows, a duration of a discovery window, a beacon interval, or a NAN channel, etc.). Can mean. The NAN terminals may configure a NAN cluster, where the NAN cluster may use the same set of NAN parameters and may mean a set of NAN terminals synchronized to the same discovery window schedule. A NAN terminal belonging to a NAN cluster may directly transmit a multicast / unicast NAN service discovery frame to another NAN terminal within a range of a discovery window.

Also, for example, NFC may operate in a relatively low frequency band of 13.56 MHz. In this case, when two P2P devices support NFC, an NFC channel may be selectively used. The searching P2P device may discover the P2P device using the NFC channel. NFC device discovery may mean that two P2P devices agree on a common channel for group formation and share provisioning information, such as a device's password.

A detailed interworking method will be described below with ASP for the above-described interfaces. In this case, although the above-described configuration is presented as an interface that can be linked with the ASP, this is only an example, and it may be possible to support other interfaces, but is not limited to the above-described embodiment.

FIG. 10 is a diagram illustrating an application service platform (ASP) supporting a plurality of interfaces.

As described above, the service terminal of the advertiser terminal advertises a service that it can provide, and as another terminal, the service terminal of the searcher terminal instructs the ASP terminal to find a target device to use the service. Could. That is, in the past, the service could be searched for and supported between terminals through the ASP.

In this case, referring to FIG. 10, the ASP may support a plurality of interfaces. In this case, as an example, the ASP may support a plurality of interfaces for performing service discovery. In addition, the ASP may support a plurality of interfaces for performing a service connection.

In this case, as an example, the plurality of interfaces for performing service discovery may be at least one of Wi-Fi Direct, Neighbor Awareness Networking (NAN), Near Field Communication (NFC), Bluetooth Low Energy (BLE), and WLAN Infrastructure.

In addition, the plurality of interfaces for performing service connection may be at least one of Wi-Pi Direct and Infrastructure. Also, as an example, the ASP may support a plurality of frequency bands. In this case, as an example, the plurality of frequency bands may be 2.4 GHz, 5 GHz, 60 GHz, or the like. In addition, as an example, information about a frequency band of less than 1 GHz may be supported. That is, the ASP may support a plurality of frequency bands and is not limited to a specific frequency band.

Referring to FIG. 10, a first terminal may perform device discovery or service discovery for a first service using an ASP. Thereafter, when the search for the device discovery or the service discovery is completed, the service connection may be performed based on the search result. In this case, as an example, the interface used for the service discovery search and the interface performed for the service connection may be different from each other, and may be selected from a plurality of interfaces.

In this case, information or parameters for supporting the plurality of interfaces described above in the ASP may be used.

In relation to the above-described ASP, as an example, the service terminal of the terminal may obtain information on a service discovery method and a connection method capable of supporting the first service from the ASP. In this case, the first service may be one service provided by the terminal and is not limited to a specific service.

The service terminal of the terminal may call the AdvertiseService () or SeekService () method to the ASP based on the information obtained from the ASP. That is, the terminal may use the ASP as an advertiser or a searcher to perform service discovery for the first service, which may be the same as the existing ASP operation. In addition, after the service discovery for the first service is performed, the terminal may perform a service connection based on the service discovery result. In this case, the service connection may be a P2P or WLAN infrastructure. In this case, for example, since both service connections support a plurality of frequency bands, the connection may be performed based on a preferred band.

In this case, as an example, the information about the service discovery method and the connection method may be as shown in Table 1 below.

TABLE 1

11 is a block diagram of a service in which an NFC interface is added in addition to the Wi-Fi interface.

For example, as illustrated in FIG. 11, the existing Wi-Fi interface could use a 2.4 GHz band in 802.11n and a 5 GHz band in 802.11ac. In this case, the NFC may operate in a relatively low frequency band of 13.56MHz. Services such as Wi-Fi Direct (WFD), infrastructure mode, Tunneled Direct Link Setup (TDLS), and NAN (Neighbor Area Network) are available on the Wi-Fi interface. At this time, there is a need for a scheme for unifying management by applying NFC to the above-described ASP. In addition, as WFDS technology is gradually developed, support for 3rd party applications may be required.

In this case, as an example, when two P2P devices support NFC, an NFC out-of-band channel may be selectively used in a device discovery step. The searching P2P device may discover the P2P device using the NFC OOB channel. NFC OOB device discovery may mean that two P2P devices agree on a common channel for group formation and share provisioning information, such as a device's password. Also, as an example, the P2P device or the P2P group owner may use an NFC handover request / selection message for OOB device discovery. The NFC handover request / selection message may be exchanged over the OOB channel prior to group formation or P2P invitation.

12 is a diagram for a method of exchanging an NFC handover request and a handover selection message in a terminal supporting NFC.

Referring to FIG. 12, two terminals supporting NFC may negotiate at least one alternative carrier for data exchange. In this case, as an example, a terminal requesting handover (hereinafter, a handover request terminal) may transmit a handover request message to a terminal (hereinafter, handover selector) which selects whether to handover. . In this case, as an example, the handover request message may include information on at least one alternative carrier. In this case, for example, alternative carriers may be set for each interface. That is, different alternative carriers may mean different interfaces.

For example, FIG. 12 may include alternative carrier information for Bluetooth and alternative carrier information for Wi-Fi. Thereafter, the handover selection terminal may receive a handover request message. When the handover selection terminal receives the handover request message, the handover selection terminal may select an alternative carrier based on the handover request message. In this case, the handover selection terminal may perform the selection based on whether it is an alternative carrier that it can support. Thereafter, the handover selection terminal may transmit a handover selection message to the handover request terminal. Thereafter, the handover requesting terminal and the handover selecting terminal may perform data exchange using the selected alternative carrier.

In this case, as an example, FIG. 12A may be an example of selecting one alternative carrier among a plurality of alternative carriers. In this case, the handover request terminal and the handover selection terminal may perform data exchange based on one selected alternative carrier.

On the other hand, Figure 12 (b) is a case where the handover selection terminal supports a plurality of alternative carriers may include information on the plurality of alternative carriers in the handover selection message. In this case, when the handover request terminal receives the handover selection message, the handover request terminal may exchange data using a preferred alternative carrier among a plurality of alternative terminals. In addition, when data exchange with the preferred alternative carrier is impossible, the handover request terminal may perform data exchange using another alternative carrier, which is not limited to the above-described embodiment.

That is, the handover requesting terminal and the handover selecting terminal may exchange data for handover using an alternative carrier supported. Also, as an example, the alternative carrier described above may be at least one of Wi-Fi Direct, NAN, NFC, BLE, and WLAN infrastructure as an interface, and is not limited to the above-described embodiment.

13 is a diagram illustrating a message format for an NFC handover message in a terminal supporting NFC.

The handover message may include a record field for the handover and an NFC Data Exchange Frame (NDEF) record field. At this time, zero or more NDEF record fields may be configured. That is, the NDEF record field may not be included depending on the need, or may include a plurality. In this case, as an example, the NDEF record may be a carrier configurator record, which will be described later.

Also, as an example, the record field for the handover may include a handover request record, a handover select record, a handover mediate record, and a handover initiate record. ) Can be configured to any one. That is, the message used in the handover may be set differently according to each type.

In addition, the record field for the handover may include at least one or more of a header field, a version field, and an alternative carrier field. In this case, as an example, the alternative carrier field may include zero or more fields. That is, alternative carrier fields may not be included or a plurality may be included depending on supported alternative carriers.

As an example, the alternative carrier field may include at least one of a header field, a carrier power state field, a carrier data reference field, and an auxiliary data reference field. have. In this case, as an example, the carrier data reference field may include zero or more fields. That is, the carrier data reference field may not be included or may be included in plural as necessary. In addition, the auxiliary data reference field may include zero or more fields. That is, the auxiliary data reference field may also be included or plural as necessary.

In this case, the carrier data reference field and the auxiliary data reference field may indicate an NDEF record field as a pointer. For example, the NDEF record indicated by the carrier data reference field may be either a handover carrier record or a carrier configuration record. Also, as an example, the NDEF record indicated by the carrier data reference field may be an IP network record or a verb record, and is not limited to the above-described embodiment. That is, the carrier data reference field may indicate an NDEF record including information about a carrier.

In addition, the auxiliary data reference may also be a pointer indicating an NDEF record including information about the auxiliary data. In this case, as an example, the NDEF record indicated by the auxiliary data reference field may be any one of an auxiliary data record or a verb record. In addition, as an example, the NDEF record indicated by the auxiliary data reference field may be any one of a network identifier or a device information. That is, the auxiliary data reference may indicate an NDEF record including auxiliary information about a carrier.

In this case, as an example, verb record information may be configured with respective fields, as shown in FIG. 13, to include respective information. In addition, the network identifier may also be configured with respective fields to include respective information. As described above, the terminal that supports NFC may exchange a handover message based on NFC, and may perform the above-described service discovery.

Hereinafter, a method for performing service discovery using NFC in the case of forming an ASP session based on service connection based on the above description will be described.

14 is a diagram illustrating a method of performing service discovery using NFC.

Referring to FIG. 14, a seeker device (or a handover request terminal) 1420 may provide a SeekService () method to an ASP to perform service discovery through NFC. In this case, as an example, the SeekService () method may include at least one service hash. Also, as an example, the SeekService () method may further include at least one or more of connection capability exchange information (CCEX) and carrier configuration record information. Thereafter, the ASP of the searcher terminal 1420 may set an NFC tag (NFC config) and transmit a handover request message to an advertiser device (Advertise Device or handover selection terminal) 1410 based on the NFC touch. have. In this case, as an example, the handover request message may be transmitted for each request of the searcher terminal 1420. That is, it can be performed independently for each request or service. As an example, the handover request message may include at least one of service hash, CCEX information, and carrier configuration record information as information included in the SeekService () method. Thereafter, the advertiser terminal 1410 may check whether there is a match for a service supported through service hash matching. Thereafter, the advertiser terminal 1410 may transmit a handover selection message to the searcher terminal 1420. In this case, as an example, the advertiser terminal 1410 may call the AdvertiseService () method, and the AdvertiseService () method may include at least one of a service hash, an advertiser ID, an advertisement ID, CCEX information, and carrier setting record information. This may be included. In this case, as an example, the handover selection message may include at least one of service hash, advertiser ID (Advertisement ID), CCEX information, and carrier setting record information as information included in the above-described AdvertiseService () method. Thereafter, the searcher terminal 1420 may report a search result to a higher layer as a SearchResult () event. Thereafter, the searcher terminal 1420 may perform the ASP session connection by calling the ConnectSession () method and performing Wi-Fi connection establishment.

15 illustrates a handover request message and a handover selection message.

In this case, when performing service discovery using the NFC described above in FIG. 14, the message format as shown in FIG. 15 may be used.

More specifically, referring to FIGS. 13 and 15, in the handover request message, the handover record field may be a handover request record. In this case, the handover request record may include an alternative carrier record as described above. In addition, the alternative carrier record may include a carrier data reference field. In this case, the carrier data reference field may be a first value and / or a second value, which will be described later.

In addition, the first NDEF record of the handover request message may be a verb NDEF record as an auxiliary data record. In this case, the verb NDEF record may include at least one of an NDEF record header, a context ID, a flag, an external record ID, a service hash, and CCEX information.

In another NDEF record, a Wi-Fi P2P Carrier configuration record and / or a Wi-Fi Infrastructure Carrier configuration record may be set. This will also be described later.

In the handover selection message, the handover record field may be a handover select record. In this case, the handover request record may include an alternative carrier record as described above. In addition, the alternative carrier record may include a carrier data reference field. In this case, the carrier data reference field may be a first value and / or a second value, which will be described later.

In addition, the first NDEF record of the handover selection message may be a verb NDEF record as an auxiliary data record. In this case, the verb NDEF record may include at least one of an NDEF record header, a context ID, a flag, an external record ID, a service hash, an advertisement ID, and CCEX information. It may include one.

In another NDEF record, a Wi-Fi P2P Carrier configuration record and / or a Wi-Fi Infrastructure Carrier configuration record may be set. This will also be described later.

The verb NDEF record included in the above handover request message and the handover selection message may be defined as shown in Table 2 below.

In more detail, the Context Identifier field may be used as identification information about a domain or a configuration. In addition, the flag field may consist of four subfields, and may indicate information on a service in consideration of service discovery performed through NFC. For example, the flag field may include a seek bit and a provide bit. In this case, the search bit may be set to a first value ('1' in the following table) if the service bit is provided as a 1 bit (when the service is requested). In addition, the providing bit may be set to a first value ('1' in the following table) when providing a service as one bit. More specifically, the search bit and the provide bit may be as shown in Table 3 below. For example, if the search bit is the first value and the provide bit is the second value ('2' in the following table), the search information may include only information about the service hash. That is, the terminal may perform a search for the service specified by the service hash as the searcher terminal 1510 or the handover requester terminal. That is, when searching for a service as the searcher terminal 1510, the search bit and the provide bit of the flag field may be set to a first value and a second value, respectively. Also, as an example, if the search bit is the second value and the provision bit is the first value, the search information may include service hash and advertisement ID information. That is, the terminal may include a service hash for a specific service as an advertiser terminal 1520 or a handover selector terminal. In addition, advertiser ID information, which is a value temporarily used for service advertisement, may be included. That is, when the advertiser terminal 1520 performs the advertisement for the service, the search bit and the provide bit of the flag field may be set to the second value and the first value, respectively.

As another example, both the search bit and the provide bit may be set to a first value. In this case, as an example, the terminal may serve as a searcher terminal and an advertiser terminal. For example, the terminal may search for the first service as a searcher terminal through a service hash corresponding to the first service. On the other hand, the terminal may perform the advertisement for the second service through the service hash corresponding to the second service as the advertiser terminal for the second service, for this purpose, the service hash and the advertiser ID information corresponding to the second service. Can be provided. That is, whether or not the terminal plays a role as a searcher terminal and / or as an advertiser terminal based on each service may be indicated through a search bit and a provision bit of a flag field, and are not limited to the above-described embodiment. Do not.

In addition, the verb NDEF record of the handover request message and the handover selection message may include an external record ID length field, an external record ID field, and a service hash field. In addition, the verb NDEF record of the handover selection message may include the following advertisement ID field, and the verb NDEF record of the handover request message may not include the following advertisement ID field.

Also, as an example, the verb NDEF record of the handover message may include CCEX information. In this case, as an example, the CCEX information may be information indicating an interface for performing a service connection. For example, as described above, the service connection may be performed through a P2P connection or Wi-Fi direct connection or an infrastructure connection. At this time, as an example, when the first bit ('Bit 0' in the following table) of the CCEX information is the first value ('1' in the following table), P2P connection is supported and a Wi-Fi P2P carrier setting record exists. Can be instructed. On the other hand, if the first bit ('Bit 0' in the table below) of the CCEX information is the second value ('2' in the table below), the P2P connection is not supported and the Wi-Fi P2P carrier setting record does not exist. May be indicated.

Also, as an example, when the second bit of CCEX information ('Bit 0' in the table below) is the first value ('1' in the table below), the infrastructure connection is supported and the Wi-Fi infrastructure carrier configuration record May be indicated to exist. On the other hand, if the second bit of CCEX information ('Bit 0' in the table below) is the second value ('2' in the table below), the infrastructure connection is not supported and a Wi-Fi infrastructure carrier setup record exists. It may be indicated as not to be limited, but is not limited to the following examples.

TABLE 2

TABLE 3

In a more specific embodiment, the handover request record of the handover request message may be located in the first record of the NDEF message. That is, it is necessary to provide the handover type and the necessary information first, and may be located in the first record. In this case, the ID of the alternative carrier record of the handover request record may be 'A' as the first value. Also, as an example, the carrier data reference of the handover request record may be set to a first value and / or a second value. In this case, the first value may be an ID of a Wi-Fi P2P carrier setting record. In addition, the second value may be an ID of a Wi-Fi infrastructure carrier configuration record. That is, the carrier data reference may include a value corresponding to a supported interface during P2P connection and / or infrastructure connection. For example, only one of the two or both may be supported, and is not limited to the above-described embodiment.

Next, the verb NDEF record message of the handover request message may be located in the second record following the handover request record. In this case, the payload of the verb NDEF record may be set as shown in Table 1 and Table 2 above. However, as an example, the CCEX information may be composed of one octet, and the first value (ex, 0x40) in which only the infrastructure connection is supported and the second value (ex, 0x80) and the infrastructure in which only the P2P connection is supported. It may be set to any one of the third values ex and 0Xc0 supporting both P2P connections, and are not limited to the above-described embodiment.

In this case, as an example, a Wi-Fi P2P carrier configuration record and a Wi-Fi infrastructure carrier configuration record may be included if necessary according to the supported interface based on the handover request message, and are not limited to the above-described embodiment. That is, if only Wi-Fi P2P carrier setup records are included, if only Wi-Fi infrastructure carrier setup records are included, if both Wi-Fi P2P carrier setup records and Wi-Fi infrastructure carrier setup records are included, and There may be a case where neither the Fi P2P carrier setup record and the Wi-Fi infrastructure carrier setup record are included, but are not limited to the above-described embodiment.

The handover selection message may also be similar to the handover request message. The handover selection record of the handover selection message may be located at the first record of the NDEF message. That is, it is necessary to provide the handover type and the necessary information first, and may be located in the first record. In this case, the ID of the alternative carrier record of the handover selection record may be 'A' as the first value. Also, as an example, the carrier data reference of the handover selection record may be set to a first value and / or a second value. In this case, the first value may be an ID of a Wi-Fi P2P carrier setting record. In addition, the second value may be an ID of a Wi-Fi infrastructure carrier configuration record. That is, the carrier data reference may include a value corresponding to a supported interface during P2P connection and / or infrastructure connection.

For example, only one of the two or both may be supported, and is not limited to the above-described embodiment.

Next, the verb NDEF record message of the handover selection message may be located in the second record following the handover selection record. In this case, the payload of the verb NDEF record may be set as shown in Table 1 and Table 2 above. However, as an example, the CCEX information may be composed of one octet, and the first value (ex, 0x40) in which only the infrastructure connection is supported and the second value (ex, 0x80) and the infrastructure in which only the P2P connection is supported. It may be set to any one of the third values ex and 0Xc0 supporting both P2P connections, and are not limited to the above-described embodiment.

In this case, as an example, a Wi-Fi P2P carrier configuration record and a Wi-Fi infrastructure carrier configuration record may be included if necessary according to the supported interface based on the handover selection message, and are not limited to the above-described embodiment. That is, if only Wi-Fi P2P carrier setup records are included, if only Wi-Fi infrastructure carrier setup records are included, if both Wi-Fi P2P carrier setup records and Wi-Fi infrastructure carrier setup records are included, and There may be a case where neither the Fi P2P carrier setup record and the Wi-Fi infrastructure carrier setup record are included, but are not limited to the above-described embodiment. In addition, as an example, as described above, the verb NDEF record of the handover selection message may include an advertisement ID as a temporary ID, as described above.

In addition, as an example, the CCEX information included in the above-described handover request record may be included when the SeekService () method or the ASPSeekInstance () method is called in the searcher terminal (or the handover request terminal). In addition, the CCEX information included in the handover selection record may be included when the AdvertiseSerivce () method is called in the advertiser terminal (or the handover selector terminal), and is not limited to the above-described embodiment.

As another example, the Wi-Fi P2P carrier setting record and / or the Wi-Fi infrastructure carrier setting record may further include information on a preferred connection as the connection capability information, and is not limited to the above-described embodiment.

As another example, the Wi-Fi infrastructure carrier setup record may be used to use an infrastructure connection for an already existing service session, and is not limited to the above-described embodiment.

In addition, the above-described CCEX information may be included in the handover message as a CCEX attribute (CCEX Attribute), which may be as shown in Table 4 below.

TABLE 4

In addition, as an example, the infrastructure connection information may also be included in the above-described Wi-Fi infrastructure carrier setup record as an infrastructure connection information attribute, which may be as shown in Table 5 below. This will be described later.

TABLE 5

16 is a diagram illustrating a method of performing service discovery for a plurality of services using NFC.

The searcher terminal (or handover requester terminal) may transmit a handover request message to the advertiser terminal (or handover selector terminal), as described above. In this case, as an example, the searcher terminal may transmit a handover request message including information on a plurality of services.

More specifically, referring to FIG. 16, the searcher terminal (or the handover requester terminal 1610) may transmit a handover request message. In this case, the handover request message may include information about a plurality of services. For example, the handover request record of the handover request message may include a plurality of alternative carrier records, as described above. At this point, for example, each alternative carrier record may indicate each NDEF record. Specifically, the carrier data reference field of each alternative carrier record in the handover request record may be set to a first value and / or a second value. In this case, the first value may be an ID of a Wi-Fi P2P carrier setting record. Also, the second value may be an ID of a Wi-Fi infrastructure carrier setup record, as described above. In addition, each verb NDEF record indicated by each alternative carrier record may be included in the handover request message. In addition, each carrier establishment record corresponding to each alternative carrier record may be included in the handover request message. That is, a record for each service may be set in the handover request message, which is not limited to the above-described embodiment. However, as an example, the connection capability information for each service may use the existing interface or perform service connection through the same interface for efficiency, and may not be limited to the above-described embodiment.

In addition, as an example, the advertiser terminal (or handover selector terminal 1620) receiving the handover request message checks the supported services through service hashes of a plurality of services included in the handover request message, and information about the same. May be transmitted to the searcher terminal 1610.

17 illustrates a method of using a pre-connected Wi-Fi infrastructure interface.

The searcher terminal may transmit a handover request message and receive a handover selection message from the advertiser terminal. In this case, as an example, a Wi-Fi infrastructure connection may already be established between the searcher terminal and the advertiser terminal. In this case, the handover request message and the handover selection message may include information on the Wi-Fi infrastructure connection already connected. For example, the attribute information about the Wi-Fi infrastructure connection may be included in the Wi-Fi infrastructure carrier configuration record. In this case, the attribute information on the Wi-Fi infrastructure connection may include information about the BSSID of the AP, the infrastructure address of the infrastructure, the IP address, and the like, but is not limited to the above-described embodiment. Do not.

18 illustrates a method of performing a service connection by forming a P2P group after performing service discovery using NFC.

The advertiser terminal 1810 and the searcher terminal 1820 may perform a service search through a handover request message and a handover selection message, as described above.

In this case, as an example, the alternative carrier record may indicate that the Wi-Fi P2P carrier setting record is included. In this case, as an example, the attribute information as the information on the Wi-Fi P2P interface included in the Wi-Fi P2P carrier setting record may be as shown in Table 6 below.

TABLE 6

That is, the Wi-Fi P2P carrier setting record includes a field for a P2P_Version attribute, a feature capability field, a connection capability information field, and an information field for a persistent P2P group. It may include at least any one of.

In this case, as an example, the P2P version field may be set to “0x02” or “0x00”. That is, the P2P version field may be set to a value indicating major version or minor version as information on the P2P version. In this case, the minor version may be a version considering backward compatibility with the previous system.

In addition, as an example, as an ASP supporting another interface as described above, it may be set to a new P2P version value, and is not limited to the above-described embodiment.

In addition, the feature capability field may be a field including information necessary for exchanging information on the ASP transmission capability parameter. In addition, the connection capability information field may include information related to the setting of Auto GO (Group Owner) or PersistentGO. In addition, the persistent P2P group field may include information about the persistent P2P group. That is, the Wi-Fi P2P carrier setting record may include information about Wi-Fi P2P in which an ASP session is formed based on the P2P connection. More specifically, when two terminals want to start a new connection required in the service session, the Wi-Fi P2P carrier configuration record may be included in the handover request message.

Also, as an example, a network identity record (Ni) may be included when there is no connection or a P2P topology is unknown. That is, the network identification record may be a record including information on a network address for identifying a network interface connected as a specific carrier. In this case, for example, the network identifiers may use a corresponding search protocol to obtain a current network address corresponding to the identifiers. For example, the identification attribute may be included in the form of a TLV.

19 is a flowchart illustrating a method for performing discovery by a terminal according to an embodiment of the present specification.

The first terminal may transmit a handover request message including CCEX information to the second terminal using NFC. (S1910) In this case, as described above with reference to FIGS. 10 to 18, the first terminal and the second terminal are ASPs. It may be a terminal for performing service discovery using any one of a plurality of interfaces based on. In addition, the first terminal and the second terminal may be a terminal for performing a service connection using a Wi-Fi direct or infrastructure based on the ASP, as described above. In this case, the first terminal and the second terminal may perform a search for a service using NFC. That is, the handover request message transmitted by the first terminal may be a searcher terminal and a message transmitted to perform a service search. In this case, as an example, the handover request message may include CCEX information. In this case, the CCEX information may include a first bit indicating whether P2P connection is supported. In this case, when the first bit indicates that the P2P connection is supported, the handover request message may include a Wi-Fi P2P carrier configuration record. At this time, the Wi-Fi P2P carrier setting record may include attribute information on the P2P connection, as described above. In addition, the CCEX information may include a second bit indicating whether the infrastructure connection is supported. In this case, when the second bit indicates that the infrastructure connection is supported, the handover request message may include a Wi-Fi infrastructure carrier configuration record. In this case, the Wi-Fi infrastructure carrier configuration record may include attribute information on the infrastructure connection, as described above.

Next, the first terminal may receive a handover selection message transmitted by the second terminal (S1920). At this time, as described above with reference to FIGS. 10 to 18, the second terminal provides a service through the handover selection message. To advertise on That is, the second terminal may perform an advertisement for the service through the handover selection message as the advertiser terminal. In this case, as an example, the handover selection message may include CCEX information. At this point, similar to the handover request message, the CCEX information may include a first bit indicating whether the P2P connection is supported. In this case, when the first bit indicates that the P2P connection is supported, the handover request message may include a Wi-Fi P2P carrier configuration record. At this time, the Wi-Fi P2P carrier setting record may include attribute information on the P2P connection, as described above. In addition, the CCEX information may include a second bit indicating whether the infrastructure connection is supported. In this case, when the second bit indicates that the infrastructure connection is supported, the handover request message may include a Wi-Fi infrastructure carrier configuration record. In this case, the Wi-Fi infrastructure carrier configuration record may include attribute information on the infrastructure connection, as described above.

Next, the first terminal and the second terminal may establish a service connection establishment and an ASP session. (S1930) In this case, as described above with reference to FIGS. 10 to 18, the first terminal and the second terminal may include a handover request message and The CCEX information included in the handover selection message may be used to exchange information on an interface for performing service connection and ASP session establishment. In this case, when the first terminal and the second terminal supports the P2P connection, the first terminal and the second terminal may perform the connection to the service through the P2P connection. In addition, when the first terminal and the second terminal supports the infrastructure connection, the first terminal and the second terminal may perform the connection to the service through the infrastructure connection. In addition, when the first terminal and the second terminal supports both P2P connection and infrastructure connection, the first terminal and the second terminal can select any one of the two interfaces to perform the service connection, which is described above As shown.

20 is a block diagram of a terminal device according to one embodiment of the present specification.

The terminal device may be a terminal capable of performing service discovery. In this case, the terminal device 100 includes a transmitting module 110 for transmitting a wireless signal, a receiving module 130 for receiving a wireless signal, and a processor 120 for controlling the transmitting module 110 and the receiving module 130. can do. In this case, the terminal 100 may communicate with an external device by using the transmitting module 110 and the receiving module 130. In this case, the external device may be another terminal device. As another example, the external device may be a base station. That is, the external device may be a device capable of communicating with the terminal device 100 and is not limited to the above-described embodiment. The terminal device 100 may transmit and receive digital data such as content using the transmission module 110 and the reception module 130.

According to one embodiment of the present specification, the processor 120 of the terminal device 100 may transmit a handover request message to another terminal using NFC. In addition, the processor 120 of the terminal device 100 may receive a handover selection message from another terminal using NFC. In this case, the handover request message and the handover selection message may include CCEX information, as described above. The CCEX information may include a first bit indicating whether P2P connection is supported. In this case, when the first bit indicates that the P2P connection is supported, the handover request message may include a Wi-Fi P2P carrier configuration record. At this time, the Wi-Fi P2P carrier setting record may include attribute information on the P2P connection, as described above. In addition, the CCEX information may include a second bit indicating whether the infrastructure connection is supported. In this case, when the second bit indicates that the infrastructure connection is supported, the handover request message may include a Wi-Fi infrastructure carrier configuration record. In this case, the Wi-Fi infrastructure carrier configuration record may include attribute information on the infrastructure connection, as described above.

Embodiments of the present invention described above may be implemented through various means. For example, embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.

For implementation in hardware, a method according to embodiments of the present invention may include one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), and Programmable Logic Devices (PLDs). It may be implemented by field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, and the like.

In the case of an implementation by firmware or software, the method according to the embodiments of the present invention may be implemented in the form of a module, a procedure, or a function that performs the functions or operations described above. The software code may be stored in a memory unit and driven by a processor. The memory unit may be located inside or outside the processor, and may exchange data with the processor by various known means.

The detailed description of the preferred embodiments of the invention disclosed as described above is provided to enable any person skilled in the art to make and practice the invention. Although the above has been described with reference to the preferred embodiments of the present invention, those skilled in the art will variously modify and change the present invention without departing from the spirit and scope of the invention as set forth in the claims below. I can understand that you can. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein. In addition, while the preferred embodiments of the present specification have been shown and described, the present specification is not limited to the specific embodiments described above, and the technical field to which the present invention belongs without departing from the gist of the present specification claimed in the claims. Of course, various modifications can be made by those skilled in the art, and these modifications should not be individually understood from the technical spirit or prospect of the present specification.

In the present specification, both the object invention and the method invention are described, and the description of both inventions may be supplementarily applied as necessary.

In the above-described wireless communication system, a method of performing discovery by the terminal is described with reference to an example applied to a P2P system, but it is possible to apply to various wireless communication systems in addition to the P2P system.

Claims (15)

1. A method for a terminal to perform service discovery in a wireless communication system,

   Transmitting, by the first terminal, a handover request message to the second terminal using near field communication (NFC);

   Receiving, by the first terminal, a handover selection message from the second terminal using NFC;

   And the handover request message and the handover selection message include connection capability exchange (CCEX) information.
2. The method of claim 1,

   The CCEX information includes a first bit indicating whether a P2P connection is supported and a second bit indicating whether an infrastructure connection is supported.
3. The method of claim 2,

   When the first bit indicates that the P2P connection is supported, the handover request message and the handover selection message further include a Wi-Fi P2P Carrier configuration record. How to Perform Discovery.
4. The method of claim 3, wherein

   And the Wi-Fi P2P carrier setting record includes attribute information on the P2P connection.
5. The method of claim 2,

   If the second bit indicates that the infrastructure connection is supported, the handover request message and the handover selection message further include a Wi-Fi Infrastructure Carrier configuration record. , How to perform service discovery.
6. The method of claim 5,

   And the Wi-Fi infrastructure carrier setup record includes attribute information on the infrastructure connection.
7. The method of claim 1,

   The CCEX information is included in a verb record (Verb Record) in the handover request message and the handover selection message.
8. The method of claim 1,

   And the flag information is further included in the handover request message and the handover selection message.
9. The method of claim 8,

   The flag information includes a seek bit and a provide bit.
10. The method of claim 9,

    The search bit is a bit indicating whether a service is requested, and the provide bit is a bit indicating whether the service is provided.
11. The method of claim 10,

    If the search bit indicates to request a service and the offer bit indicates to not provide a service, the terminal is a terminal searching for a service identified by a service hash, and the message transmitted by the terminal is a hand. A method of performing service discovery, which is an over request message.
12. The method of claim 10,

    If the search bit does not indicate to request a service but the provided bit indicates to provide a service, the terminal is a terminal advertising a service identified by a service hash, and the message transmitted by the terminal is a hand. A method of performing service discovery, which is an over select message.
13. The method of claim 12,

    And performing the service discovery including the service hash and advertisement ID information in the handover selection message.
14. The method of claim 10,

    When the search bit indicates to request a service and the offer bit indicates to provide a service, the terminal searches for a service identified by the first service hash, and a service identified by the second service hash. A method of performing a service discovery, which is a terminal for advertising.
15. A first terminal for performing service discovery in a wireless communication system,

    A receiving module for receiving information from an external device;

    A transmitting module for transmitting information to an external device; And

    A processor for controlling the receiving module and the transmitting module,

    The processor,

    Transmitting a handover request message to a second terminal using near field communication (NFC),

    Receive a handover selection message from the second terminal using NFC,

    The handover request message and the handover selection message includes Connection Capability Exchange (CCEX) information, the first terminal for performing service discovery.

Images