WO2019194391A1

WO2019194391A1 - Method for transferring information related to wireless device in wireless lan system, and configurator terminal using same

Info

Publication number: WO2019194391A1
Application number: PCT/KR2018/015093
Authority: WO
Inventors: 윤정환; 박기원; 조영준; 김나명
Original assignee: 엘지전자 주식회사
Priority date: 2018-04-03
Filing date: 2018-11-30
Publication date: 2019-10-10

Abstract

A method for transferring information related to a wireless device in a wireless LAN system, according to the present embodiment, comprises the steps of: allowing a configurator terminal to acquire, from an enrollee terminal, bootstrap information including list information related to an easy network setup technology supported by the enrollee terminal; allowing the configurator terminal to receive a DPP configuration request frame from the enrollee terminal; and allowing the configurator terminal to transmit a DPP configuration response frame to the enrollee terminal as a response to the DPP configuration request frame, wherein the DPP configuration response frame includes connection information related to an AP to be associated with the enrollee terminal and network setup information for the easy network setup technology related to the list information.

Description

Method for delivering information about wireless device in WLAN system and constructor terminal using same

The present disclosure relates to wireless communication, and more particularly, to a method for delivering information about a wireless device in a WLAN system and a constructor terminal using the same.

The Internet of Things (IoT) is a technology that connects to the Internet by embedding sensors and communication functions in various things. In addition, the Internet of Things (IoT) may be understood as an artificial intelligence technology in which things connected through wireless communication exchange data with each other and analyze data and provide analyzed information to a user. Herein, the thing may be various embedded systems such as home appliances, mobile devices, or wearable devices.

Open Connectivity Foundation (OCF) connects IoT devices based on a lightweight Coap Protocol (Constrained Application Protocol) according to the Representational State Transfer (REST) structure when implementing the IoT, and interconnects resources existing in IoT devices. Platform technology that enables control.

Most easy network setup techniques, including OCF, require a secure data channel for the delivery of information that requires security, such as AP connection information. That is, the enrollee may activate the soft AP function to transmit data after being connected to the WLAN system.

Disclosure of Invention An object of the present specification is to provide a method for delivering information about a wireless device in a WLAN system having improved performance and a configurator terminal using the same.

In a method for delivering information about a wireless device in a WLAN system according to an embodiment of the present disclosure, a configurator terminal may include bootstrap information including list information on an easy network setup technology supported by the registrant terminal from a registrant terminal. Obtaining a; Receiving, by the configurator terminal, a DPP setting request frame from the registrant terminal; And the configurator terminal transmits the DPP configuration response frame to the subscriber terminal in response to the DPP configuration request frame, wherein the DPP configuration response frame is for easy network setup technology associated with connection information and list information about the AP to be combined with the subscriber terminal. Including network setup information.

According to an embodiment of the present disclosure, a method for delivering information about a wireless device in a WLAN system having improved performance and a configurator terminal using the same are provided.

1 is a conceptual diagram illustrating a structure of a WLAN system.

2 is a conceptual diagram illustrating a scanning method in a WLAN.

3 is a conceptual diagram illustrating an authentication and association procedure after scanning of an AP and an STA.

4 is a diagram illustrating a neighbor discovery process.

5 is a conceptual diagram of a DPP procedure.

6 is a flowchart illustrating a process of performing a DPP procedure between wireless devices.

FIG. 7 is a diagram for explaining the role of each device and an easy setup technique based on OCF.

8A and 8B are flowcharts illustrating a process of performing device configuration provisioning based on an easy network setup technique.

9 is a flowchart illustrating a process of performing cloud server provisioning based on easy network setup technology.

10 is a flowchart illustrating a method for delivering setup information in a WLAN system according to an exemplary embodiment.

11 is a block diagram illustrating a wireless device to which an embodiment of the present invention may be applied.

12 is a block diagram illustrating an example of an apparatus included in a processor.

The above-described features and the following detailed description are all exemplary for ease of description and understanding of the present specification. That is, the present specification is not limited to this embodiment and may be embodied in other forms. The following embodiments are merely examples to fully disclose the present specification, and are descriptions to convey the present specification to those skilled in the art. Thus, where there are several methods for implementing the components of the present disclosure, it is necessary to clarify that any of these methods may be implemented in any of the specific or equivalent thereof.

In the present specification, when there is a statement that a configuration includes specific elements, or when a process includes specific steps, it means that other elements or other steps may be further included. That is, the terms used in the present specification are only for describing specific embodiments and are not intended to limit the concept of the present specification. Furthermore, the described examples to aid the understanding of the invention also include their complementary embodiments.

The terminology used herein has the meaning commonly understood by one of ordinary skill in the art to which this specification belongs. Terms commonly used should be interpreted in a consistent sense in the context of the present specification. In addition, terms used in the present specification should not be interpreted in an idealistic or formal sense unless the meaning is clearly defined. Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

1 is a conceptual diagram illustrating a structure of a WLAN system. FIG. 1A shows the structure of an infrastructure network of the Institute of Electrical and Electronic Engineers (IEEE) 802.11.

Referring to FIG. 1A, the WLAN system 10 of FIG. 1A may include at least one basic service set (hereinafter, referred to as 'BSS', 100, 105). The BSS is a set of access points (APs) and stations (STAs) that can successfully synchronize and communicate with each other, and is not a concept indicating a specific area.

For example, the first BSS 100 may include a first AP 110 and one first STA 100-1. The second BSS 105 may include a second AP 130 and one or more STAs 105-1, 105-2.

The infrastructure BSS (100, 105) may include at least one STA, AP (110, 130) providing a distribution service (Distribution Service) and a distribution system (DS, 120) connecting a plurality of APs. have.

The distributed system 120 may connect the plurality of

BSSs

100 and 105 to implement an extended service set 140 which is an extended service set. The ESS 140 may be used as a term indicating one network to which at least one

AP

110 or 130 is connected through the distributed system 120. At least one AP included in one ESS 140 may have the same service set identification (hereinafter, referred to as SSID).

The portal 150 may serve as a bridge for connecting the WLAN network (IEEE 802.11) with another network (for example, 802.X).

In a WLAN having a structure as shown in FIG. 1A, a network between

APs

110 and 130 and a network between

APs

110 and 130 and STAs 100-1, 105-1, and 105-2 may be implemented. Can be.

1B is a conceptual diagram illustrating an independent BSS. Referring to FIG. 1B, the WLAN system 15 of FIG. 1B performs communication by setting a network between STAs without the

APs

110 and 130, unlike FIG. 1A. It may be possible to. A network that performs communication by establishing a network even between STAs without the

APs

110 and 130 is defined as an ad-hoc network or an independent basic service set (BSS).

Referring to FIG. 1B, the IBSS 15 is a BSS operating in an ad-hoc mode. Since IBSS does not contain an AP, there is no centralized management entity. Thus, in the IBSS 15, the STAs 150-1, 150-2, 150-3, 155-4, and 155-5 are managed in a distributed manner.

All STAs 150-1, 150-2, 150-3, 155-4, and 155-5 of the IBSS may be mobile STAs, and access to a distributed system is not allowed. All STAs of the IBSS form a self-contained network.

The STA referred to herein includes a medium access control (MAC) conforming to the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard and a physical layer interface to a wireless medium. As any functional medium, it can broadly be used to mean both an AP and a non-AP Non-AP Station (STA).

The STA referred to herein includes a mobile terminal, a wireless device, a wireless transmit / receive unit (WTRU), a user equipment (UE), and a mobile station (MS). It may also be called various names such as a mobile subscriber unit or simply a user.

2 is a conceptual diagram illustrating a scanning method in a WLAN.

Referring to FIG. 2, a scanning method may be classified into passive scanning 200 and active scanning 250.

Referring to FIG. 2A, the passive scanning 200 may be performed based on the beacon frame 230 that the AP 210 broadcasts periodically. The AP 210 of the WLAN may broadcast the beacon frame 230 to the non-AP STA 240 every specific period (for example, 100 msec).

The beacon frame 230 may include information about the current network. The non-AP STA 240 may periodically receive the beacon frame 230. In order to perform an authentication / association process, the non-AP STA 240 may perform scanning on the AP 210 and the channel based on the network information included in the beacon frame 230.

The passive scanning method 200 is a technique in which the non-AP STA 240 receives the beacon frame 230 transmitted from the AP 210 without first transmitting the frame. Thus, passive scanning 200 has the advantage that the overall overhead incurred by data transmission / reception in the network is small.

However, since scanning can be performed manually in proportion to the period of the beacon frame 230, the time taken to perform scanning increases.

A detailed description of the beacon frame is described in IEEE 2015 Draft P802.11-REVmb ™ July 2015 'IEEE Standard for Information Technology Telecommunications and information exchange between systems--and metropolitan area networks--AN Medium Access Control (MAC) and Physical. Layer (PHY) Specifications (hereinafter referred to as IEEE 802.11) '.

Referring to FIG. 2B, the active scanning 250 is a technique in which the non-AP STA 290 transmits the probe request frame 270 to the AP 260 to proactively perform scanning.

The AP 260 may receive the probe request frame 270 from the non-AP STA 290. The AP 260 may wait for a random time to prevent frame collision. The AP 260 may transmit a probe response frame 280 including network information to the non-AP STA 290 in response to the probe request frame 270. The non-AP STA 290 may obtain network information based on the received probe response frame 280.

In the case of the active scanning 250, since the non-AP STA 290 performs the scanning, the time used for scanning is short. However, since the probe request frame 270 needs to be transmitted by the non-AP STA 290, network overhead for frame transmission and reception increases.

Probe request frame 270 is disclosed in IEEE 802.11 8.3.3.9 and probe response frame 280 is disclosed in IEEE 802.11 8.3.3.10.

When the above scanning procedure is completed, the AP and the STA may perform an authentication and association procedure.

2 and 3, the non-AP STA may perform an authentication and association procedure with one of a plurality of APs that have completed the scanning procedure through passive / active scanning. For example, authentication and association procedures may be performed through two-way handshaking.

FIG. 3A is a conceptual diagram illustrating an authentication and combining procedure after passive scanning, and FIG. 3B is a conceptual diagram illustrating an authentication and combining procedure after active scanning.

The authentication and association procedure can be performed regardless of whether an active scanning method or passive scanning was used. For example, the

APs

300 and 350 may connect to the

non-AP STAs

305 and 355, an authentication request frame 310, an authentication response frame 320, and an association request frame. , 330, and association response frame 340, the authentication and association procedure may be performed.

In detail, the authentication procedure may be performed by transmitting the authentication request frame 310 to the

APs

300 and 350 in the

non-AP STAs

305 and 355. The

AP

300 or 350 may transmit the authentication response frame 320 to the

non-AP STAs

305 and 355 in response to the authentication request frame 310. Authentication frame format is described in IEEE 802.11 8.3.3.11.

In detail, the joining procedure may be performed by transmitting the join request frame 330 to the

APs

300 and 305 in the

non-AP STAs

305 and 355. The

AP

300 or 350 may transmit the association response frame 340 to the

non-AP STAs

305 and 355 in response to the association request frame 330.

The association request frame 330 may include information regarding the capability of the

non-AP STAs

305 and 355. The

APs

300 and 350 may determine whether to support the

non-AP STAs

305 and 355 based on the information about the performance of the

non-AP STAs

305 and 355 included in the association request frame 330. Can be.

For example, when the support for the

non-AP STAs

305 and 355 is possible, the

APs

300 and 350 support the association request frame 340 in the association response frame 340, and why and the support thereof. Capability information may be included and transmitted to the

non-AP STAs

305 and 355. Association frame format is described in IEEE 802.11 8.3.3.5/8.3.3.6.

If the combined procedure mentioned in FIG. 3 is performed, a normal data transmission and reception procedure may be performed between the AP and the STA.

4 is a diagram illustrating a neighbor discovery process. 4 may be understood as an operation between a peer to peer (P2P) device and a P2P device.

Referring to FIG. 4, in S410, a neighbor discovery process may be initiated by an indication of a station management entity (SME) / application / user / vendor. For example, the neighbor discovery process may include a scan phase S412 and a find phase S414-S416.

The scan step S412 may include an operation of scanning for all available wireless channels according to the 802.11 scheme. This allows the P2P device to identify the best operating channel.

The search steps S414-S416 may include a listen mode S414 and a search mode S416. The P2P device may alternately repeat the listening mode S414 and the search mode S416. The

P2P devices

202 and 204 may perform active scanning using a probe request frame in the search mode S416.

For example, the search range may be limited to a social channel such as channel 1, channel 6, or channel 11 (eg, 2412 MHz, 2437 MHz, 2462 MHz) for quick searching.

In addition, the

P2P devices

202 and 204 may maintain a reception state on a selected one of three social channels in the listening mode S414.

In this case, when a probe request frame transmitted by another P2P device (eg, 202) in the search mode is received, the P2P device (eg, 204) may respond with a probe response frame.

The time (eg, 100, 200, 300 Time Units (TU)) for the listening mode S414 may be randomly determined. P2P devices can reach each other's common channels through repetition of the search mode and the receive mode.

If another P2P device is found, the P2P device may exchange probe request frames and probe response frames with other P2P devices. This allows P2P devices to discover / exchange each other's device type, manufacturer or friendly device name.

If necessary information about the neighboring P2P device found through the neighbor discovery process is obtained, the P2P device (eg, 202) may inform the SME / application / user / vendor of the P2P device discovery (S418).

At present, P2P is mainly used for semi-static communication such as remote printing, photo sharing and the like. However, due to the popularity of Wi-Fi devices and location-based services, the utilization of P2P is getting wider.

For example, social chat (e.g., wireless devices subscribed to Social Network Service (SNS) recognize wireless devices in the vicinity and send and receive information based on location based services), location-based advertising, location- P2P is expected to be actively used for news broadcasting and game linkage between wireless devices. For convenience, such P2P applications are referred to as novel P2P applications.

5 is a conceptual diagram of a device provisioning protocol (DPP) procedure.

Referring to FIG. 5, the DPP architecture for the DPP procedure may include a DPP Bootstrapping protocol, a DPP Authentication protocol, a DPP Configuration protocol, and a DPP Introduction protocol. You can define the device roles.

In the DPP procedure, there can be two types of roles for the wireless device. For example, there may be a role of a configurator and an enrollee. As another example, there may be a role of an initiator and a responder.

For clarity and concise description of FIG. 5, the configurator may be understood as the first wireless device 510. In addition, the registrant may be understood as the second wireless device 520.

The first wireless device 510 as a configurator may support setup of the second wireless device 520 as a registrant. Constructors and registrants may engage in the DPP bootstrap protocol, the DPP authentication protocol, and the DPP configuration protocol.

The configurator or registrar may play the role of an initiator in the DPP bootstrap protocol and the DPP authentication protocol. However, only an enrollee can initiate the DPP configuration protocol and the DPP introduction protocol.

The DPP authentication protocol may require the initiator to obtain the responder's bootstrapping key as part of the bootstrap mechanism. Optionally, to provide mutual authentication, the wireless devices can obtain each other's bootstrap keys.

Once the DPP authentication protocol is complete, the configurator can provision the registrant for device-to-device communication or infrastructure communication.

As part of this provisioning, the configurator may allow the enrollee to establish secure associations with other peers in the network. Here, the peer may be understood as the wireless device 530 already configured by the constructor.

The constructor and the registrant can be associated with the DPP authentication protocol. Depending on the bootstrap scenario, the configurator or registrar may play the role of initiator or responder, respectively.

The wireless device initiating the DPP authentication protocol may serve as the initiator. The wireless device responding to the initiator's request may act as a responder. The DPP authentication protocol may provide the initiator with authentication of the responder. Optionally, the DPP authentication protocol may provide the responder with authentication of the initiator.

For example, to perform unidirectional authentication, the initiator can obtain the responder's bootstrapping key. In addition, to selectively perform mutual authentication, the initiator and the responder may obtain each other's bootstrap keys.

For example, to configure an unprovisioned device 520 that serves as a registrar, the wireless device 510 may serve as a configurator. For example, an unprovisioned wireless device can be an access point or other wireless device.

When the wireless device 510 serving as a configurator initiates the DPP authentication protocol with the unprovisioned wireless device 520, the wireless device 510 may serve as an initiator.

6 is a flowchart illustrating a process of performing a DPP procedure between wireless devices. The DPP procedure of FIG. 6 may be implemented in a 3-way handshaking manner.

5 and 6, the first wireless device 610 may serve as an initiator, and the second wireless device 620 may serve as a responder. In addition, the first wireless device 610 may serve as a configurator, and the second wireless device 620 may serve as an enrollee.

In operation S610, the first wireless device 610 and the second wireless device 620 may perform a DPP bootstrap protocol.

For example, the first wireless device 610 serving as a configurator may obtain bootstrap information from the second wireless device 620 serving as a registrant using an out-of-band mechanism.

For example, the OOB mechanism may be implemented based on a scan QR code method based on a QR code (eg, 521), an NFC tap method, or a Bluetooth Low Energy exchange method. .

For example, the bootstrap information may include information regarding the enrollee's bootstrapping public key for the DPP authentication protocol. As an example, the bootstrap public key may be used only for the DPP authentication protocol by the constructor and registrant.

For example, the information on the global operating class channel or the channel list may be further included in the bootstrap information.

In this case, to initiate the DPP authentication protocol, the wireless device (eg, 620) may indicate that it is listening on one of the listed channels for another device (eg, 610).

As another example, the information on the global operating class channel or the information on the channel list may not be included in the bootstrap information.

In this case, the wireless device (eg, 620) may not provide guidance to which device is listening to the other device (eg, 610). Accordingly, another device (eg, 610) must iterate over all available channels.

Iteration over multiple channels can result in significant additional delay in the DPP authentication protocol. Accordingly, an apparatus using QR Code bootstrapping may be required to include a single channel or at most a short list of possible channels in the bootstrap information.

The first wireless device 610 of FIG. 6 may start an operation on a specified channel based on the bootstrap information obtained from the second wireless device 620. The second wireless device 620 of FIG. 6 may listen on a specific channel during step S610.

In operation S620, the first wireless device 610 and the second wireless device 620 may perform a DPP authentication protocol.

For example, the first wireless device 610 serving as a configurator may transmit a DPP authentication request frame to the second wireless device 620 serving as a registrar. In this case, the DPP authentication request frame may be transmitted through at least one channel corresponding to bootstrap information (eg, a channel list).

In operation S621, the first wireless device 610 may transmit a DPP authentication request frame to the second wireless device 620. Subsequently, the first wireless device 610 may wait for a response to the DPP authentication request frame transmitted in step S621.

For example, the first wireless device 610 may determine whether a DPP authentication response frame, which is a response to the DPP authentication request frame transmitted in step S621, from the second wireless device 620 is received within a predetermined time. .

For example, the predetermined time may be set based on a transmission time of the DPP authentication request frame in step S621.

For clarity and concise description of FIG. 6, it may be assumed that the DPP authentication response frame is not received until a predetermined time elapses in response to the DPP authentication request frame transmitted in step S621.

If the DPP authentication response frame is not received until a predetermined time elapses according to the above assumption, step S622 is performed for retransmission of the DPP authentication response frame.

In operation S622, the first wireless device 610 may retransmit the DPP authentication request frame to the second wireless device 620. Subsequently, the first wireless device 610 may wait for a response to the DPP authentication request frame transmitted in step S622.

For example, the first wireless device 610 may determine whether a DPP authentication response frame, which is a response to the DPP authentication request frame retransmitted in step S622, from the second wireless device 620 within a predetermined time. .

For example, the predetermined time may be set based on a transmission time of the DPP authentication request frame in step S622.

For clarity and concise description of FIG. 6, it may be assumed that the DPP authentication response frame is not received until a predetermined time elapses in response to the DPP authentication request frame resent in step S622.

If the DPP authentication response frame is not received until a predetermined time elapses according to the above assumption, step S623 is performed for retransmission of the DPP authentication response frame.

In operation S623, the first wireless device 610 may retransmit the DPP authentication request frame to the second wireless device 620. Subsequently, the first wireless device 610 may determine whether the DPP authentication response frame is received from the second wireless device 620 within a predetermined time in response to the DPP authentication request frame resent in step S623.

For example, the predetermined time may be set based on a transmission time of the DPP authentication request frame in step S623.

For clarity and concise description of FIG. 6, it may be assumed that a DPP authentication response frame is received from the second wireless device 620 within a predetermined time. According to the above assumption, if a DPP authentication response frame is received before a predetermined time elapses, step S624 is performed.

In operation S624, the first wireless device 610 may receive a DPP authentication response frame from the second wireless device 620 in response to the DPP authentication request frame resent in operation S623.

In operation S625, the first wireless device 610 may transmit a DPP authentication confirmation frame to the second wireless device 620 to complete the DPP authentication protocol.

When the DPP authentication protocol S620 is successfully performed according to the transmission of the DPP authentication confirmation frame, a secure channel may be established between the initiator (or configurator) and the responder (or registrant).

In operation S630, the first wireless device 610 and the second wireless device 620 may perform a DPP configuration protocol.

In operation S630, the first wireless device 610 and the second wireless device 620 may use the same MAC address. In operation S630, the first wireless device 610 and the second wireless device 620 may use the same channel used during the DPP authentication protocol.

In operation S631, to start the DPP configuration protocol, the second wireless device 620 may transmit a DPP configuration request frame to the first wireless device 610. Here, regardless of whether the initiator or responder plays the role of the configurator, the DPP configuration request frame can be sent only by the enrollee.

In operation S632, the first wireless device 610 may transmit a DPP configuration response frame to the second wireless device 620 in response to the DPP configuration request frame. The DPP configuration response frame may include a DPP configuration object. For example, the DPP configuration object may include a plurality of parameter information as shown in Table 1 below.

When the aforementioned steps S610 to S630 are successfully performed, network information of the WLAN system including an AP (not shown) previously associated with the first wireless device 610 is displayed in the second wireless device 620. Can be forwarded to For example, the network information may include SSID information or password information.

That is, the second wireless device 620 may be connected to the first wireless device 610 without performing an association procedure with an AP (not shown) coupled to the first wireless device 610. It may be connected to the WLAN system based on the network information received from 610.

Enrolly device 710 may be a device that needs to be configured to participate in a user's device network. For example, the entree device 710 may include limited CPU, memory, and power resources. The Enrolly 710 device may include a user interface for receiving a user input and connecting to a network desired by the user.

The moderator device 720 may be an apparatus that allows the enrolly device 710 to easily connect to the target WiFi network and the IoTivity cloud server. For example, the moderator device 720 can provide information about the enroller device 730 to the enroller device 710.

Enroller device 730 may be a network entity to be connected by enrolly device 710.

In operation S710, the moderator device 720 may collect information about the enroller device 730 from the enroller device 730. For example, the information about the enroller device 730 may be information such as a service set identifier (SSID) of the enroller device 730.

In operation S720, the arbiter device 720 may transmit information about the enroller device 730 to the enroller device 710. The device may transmit information regarding the enroller device 730 based on a soft AP function or a Bluetooth technology.

In operation S730, the arbiter device 720 may be connected to the enroller device 730 based on the information about the enroller device 730.

In the present specification, the Easy Network Setup technology refers to a technology that helps a specific device to easily connect a counterpart device to a specific network.

The entree device 810 may be connected with the moderator device 820 based on the soft AP function. If the secure provisioning step S810 and the enroling information retrieval step S820 are performed between the entree device 810 and the arbiter device 820, step S830 may be performed.

In operation S830, the arbiter device 820 may transmit WiFi related information to the entree device 810.

For example, the WiFi related information may include the SSID of the enroller device 830 corresponding to the WiFi AP, information about a password of the enroller device 830, and a security type of the enroller device 830. It may include information about (ie authentication and encryption type).

Upon receiving the information from the moderator device 820, the entree device 810 can destroy the soft AP function of the enrollee device 810. In addition, the entree device 810 may attempt to connect with the enroller device 830 based on the information obtained from the moderator device 820.

It will be appreciated that when the soft AP function of the entree device 810 is activated and the entree device 810 is WiFi-connected with the moderator device 820, WiFi-related information may be communicated to the entree device 810.

That is, although the size of the WiFi-related information is relatively small, there is a problem that the WiFi connection and WiFi release process is required.

After the enrolling device 910 is connected to the enroller device 830 according to the above-described process of FIG. 8, through the step S900, the arbiter device 920 provides information necessary for connection with the IoTivity cloud server 940. 910 may be forwarded.

In operation S900, the arbiter device 920 may transmit cloud access information to the entree device 910.

For example, the moderator device 920 may update the “/ CoAPCloudconf” resource based on an access token issued from the IoTivity cloud server 940.

For example, the “oAPCloudconf” resource may include information on Auth Provider Name, information on OCF Cloud interface Uniform Resource Locator (URL), information on Access Token, information on Cloud Server Identity, and Last Error code information. .

Enrolly device 910 may attempt to register with IoTivity cloud server 940 based on the given cloud access information.

For example, there may be several IoTivity cloud servers 940 according to the deployment of the entree device 910. In this case, the moderator device 920 may provide a Uniform Resource Identifier (URI) of the cloud interface server on which the entree device 910 is expected to be registered.

6 and 9, different easy network setup techniques may have different network information delivered according to a purpose of use.

For example, the OCF-based network information may include SSID information, password information, and server address information of a cloud. As another example, the network information based on the DPP procedure may include SSID information and password information.

In other words, the DPP procedure has a problem in that a parameter for additional information required in an OCF-based network such as cloud server information is not defined in addition to the AP connection information.

Furthermore, when following the OCF base, there is a problem that an additional procedure as shown in FIG. 9 for transmitting network setup information is required for connection with a cloud server.

For clarity and concise description of FIG. 10, the first wireless device 1010 may be referred to as an enrollee terminal, and the second wireless device 1020 may be referred to as a configurator terminal.

The first wireless device 1010 may include a responder module 1011 and an entree module 1012. For example, the responder module 1011 may be understood as a logical object that controls the first wireless device 1010 to act as a responder and an enrollee according to the DPP procedure of FIG. 6.

In addition, the entree module 1012 may be understood as a logical object that controls the first wireless device 1010 to operate as the entree device (eg, 710 of FIG. 7) based on the OCF of FIG. 7.

The second wireless device 1020 can include an initiator module 1021 and a moderator module 1022. For example, the initiator module 1021 may be understood as a logical object that controls the second wireless device 1020 to act as an initiator and a configurator according to the DPP procedure of FIG. 6.

In addition, the moderator module 1022 may be understood as a logical object that controls the second wireless device 1020 to operate as a moderator device based on the OCF of FIG. 7 (eg, 720 of FIG. 7).

For clarity and concise description of FIG. 10, it may be assumed that the second wireless device 1020 is pre-coupled with the access point 1030 based on the initiator module 1021. Also, it may be assumed that the second wireless device 1020 previously stores information about the cloud server 1040 based on the moderator module 1022.

Referring to FIG. 10, when the power of the first wireless device 1010 is turned on, the entree module 1012 of the first wireless device 1010 may be started. Then, to initiate the DPP bootstrap protocol, entree module 1012 may pass the OCF information to responder module 1011.

In addition, the moderator module 1022 of the second wireless device 1020 can request the initiator module 1021 to retrieve the DPP bootstrap information.

In operation S1010, the DPP bootstrap protocol may be performed between the first wireless device 1010 and the second wireless device 1020.

For example, the second wireless device 1020 serving as a configurator may obtain bootstrap information from the first wireless device 1010 serving as an enroller.

For example, the bootstrap information may include information regarding the enrollee's bootstrapping public key of the first wireless device 1010 that is the registrant for the DPP authentication protocol.

Further, the bootstrap information may include list information of easy network setup techniques supported by the first wireless device 1010 acting as a registrant. For example, the information on the list of easy network setup techniques may be implemented in an attribute manner as shown in Table 2 below.

That is, the second wireless device 1020 may be configured by the easy network setup technology (eg, OCF, one M2M) supported by the first wireless device 1010 based on the bootstrap information obtained from the first wireless device 1010. You can check the type.

For example, the second wireless device 1020 may determine that the first wireless device 1010 supports OCF based on the bootstrap information obtained from the first wireless device 1010.

In operation S1020, the DPP authentication protocol may be performed between the first wireless device 1010 and the second wireless device 1020. If the DPP authentication protocol is successfully performed, a secure channel may be established between the initiator (or configurator) and the responder (or registrant).

It will be appreciated that the description of the authentication protocol procedure may be replaced with the description of step S620 of FIG. 6 above.

In operation S1030, the DPP configuration protocol may be performed between the first wireless device 1010 and the second wireless device 1020.

In operation S1030, the first wireless device 1010 and the second wireless device 1020 may use the same MAC address. In operation S1030, the first wireless device 1010 and the second wireless device 1020 may use the same channel used during the DPP authentication protocol.

In operation S1031, to start the DPP configuration protocol, the first wireless device 1010 serving as a registrar may transmit a DPP configuration request frame to the second wireless device 1020 serving as a constructor.

In operation S1032, the second wireless device 1020 may transmit a DPP configuration response frame to the first wireless device 1010 in response to the DPP configuration request frame.

According to this embodiment, the DPP configuration response frame may include a DPP configuration object. For example, the DPP configuration object may include a plurality of parameter information as shown in Table 3 below.

Referring to Table 3, the DPP configuration object may include connection information (eg, SSID, password) for the AP. Furthermore, an 'Easy Network Setup object' may be added to the DPP configuration object.

Additionally, the 'Easy Network Setup object' according to the present embodiment may further include network setup information for easy network setup technology. For example, when identification information indicating an open connectivity foundation (OCF) is included in the list information included in the bootstrap information, the network setup information may include address information of a cloud server for the registrant terminal.

In step S1033, the responder module 1011 of the first wireless device 1010 may inform the enrolly module 1012 of the completion of the DPP procedure.

For example, the enrolly module 1012 may obtain connection information (eg, SSID, password) about the AP and address information (eg, URI address information) of the cloud server from the responder module 1011.

In operation S1040, the first wireless device 1010 may be connected to the AP 1030 without a separate coupling procedure based on the responder module 1011 according to connection information (eg, SSID and password) about the AP.

In operation S1050, the first wireless device 1010 may be connected to the cloud server 1050 based on address information (eg, URI address information) of the cloud server 1040 obtained through the enrolly module 1012.

In FIG. 10, it is shown that step S1050 is performed after step S1040, but it is to be understood that the present specification is not limited thereto. For example, step S1040 and step S1050 may be performed at the same time. Alternatively, step S1050 may be performed before step S1040.

According to the present embodiment, data according to each easy network setup technique may be exchanged without additional procedures.

Referring to FIG. 11, the wireless device may be implemented as an AP or a non-AP STA as an STA capable of implementing the above-described embodiment. In addition, the wireless device may correspond to the above-described user, or may correspond to a transmitting terminal for transmitting a signal to the user.

The wireless device of FIG. 11 includes a processor 1110, a memory 1120 and a transceiver 1130 as shown. The illustrated processor 1110, memory 1120, and transceiver 1130 may be implemented as separate chips, or at least two blocks / functions may be implemented through one chip.

The transceiver 1130 is a device including a transmitter and a receiver. When a specific operation is performed, only one of the transmitter and the receiver may be performed, or both the transmitter and the receiver may be performed. have.

The transceiver 1130 may include one or more antennas for transmitting and / or receiving wireless signals. In addition, the transceiver 1130 may include an amplifier for amplifying the reception signal and / or the transmission signal and a bandpass filter for transmission on a specific frequency band.

The processor 1110 may implement the functions, processes, and / or methods proposed herein. For example, the processor 1110 may perform an operation according to the present embodiment described above. That is, the processor 1110 may perform the operation disclosed in the embodiment of FIGS. 1 to 10.

The processor 1110 may include an application-specific integrated circuit (ASIC), another chipset, a logic circuit, a data processing device, and / or a converter for mutually converting baseband signals and wireless signals.

The memory 1120 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium, and / or other storage device.

For convenience of description, an example of FIG. 12 is described based on a block for a transmission signal, but it is obvious that the reception signal can be processed using the block.

The illustrated data processor 1210 generates transmission data (control data and / or user data) corresponding to the transmission signal. The output of the data processor 1210 may be input to the encoder 1220. The encoder 1220 may perform coding through a binary convolutional code (BCC) or a low-density parity-check (LDPC) technique. At least one encoder 1220 may be included, and the number of encoders 1220 may be determined according to various information (eg, the number of data streams).

The output of the encoder 1220 may be input to the interleaver 1430. The interleaver 1230 performs an operation of distributing consecutive bit signals over radio resources (eg, time and / or frequency) to prevent burst errors due to fading or the like. At least one interleaver 1230 may be included, and the number of the interleaver 1230 may be determined according to various information (eg, the number of spatial streams).

The output of the interleaver 1230 may be input to a constellation mapper 1240. The constellation mapper 1240 performs constellation mapping such as biphase shift keying (BPSK), quadrature phase shift keying (QPSK), quadrature amplitude modulation (n-QAM), and the like.

The output of the constellation mapper 1240 may be input to the spatial stream encoder 1250. Spatial stream encoder 1250 performs data processing to transmit a transmission signal over at least one spatial stream. For example, the spatial stream encoder 1250 may perform at least one of space-time block coding (STBC), cyclic shift diversity (CSD) insertion, and spatial mapping on a transmission signal.

The output of the spatial stream encoder 1250 may be input to an IDFT 1260 block. The IDFT 1260 block performs an inverse discrete Fourier transform (IDFT) or an inverse Fast Fourier transform (IFFT).

The output of the IDFT 1260 block is input to the Guard Interval (GI) inserter 1270, and the output of the GI insert 1270 is input to the transceiver 1230 of FIG. 13.

In the detailed description of the present specification, specific embodiments have been described, but various modifications are possible without departing from the scope of the present specification. Therefore, the scope of the present specification should not be limited to the above-described embodiments, but should be determined not only by the claims below but also by the equivalents of the claims of the present invention.

Claims

In the WLAN system for transmitting information about a wireless device,

Obtaining, by the configurator terminal, bootstrap information including list information on Easy Network Setup technology supported by the registrant terminal from the registrant terminal;

Receiving, by the configurator terminal, a Device Provisioning Protocol (DPP) setting request frame from the registrant terminal; And

The configurator terminal transmits a DPP configuration response frame to the registrant terminal in response to the DPP configuration request frame, wherein the DPP configuration response frame includes connection information about the access point (AP) to be combined with the subscriber terminal and the list. And network setup information for the easy network setup technique associated with the information.
The method of claim 1,

And when the list information includes identification information indicating an Open Connectivity Foundation (OCF), the network setup information includes address information of a cloud server for the registrant terminal.
The method of claim 2,

The registrant terminal is connected to the AP based on the connection information,

The registrant terminal is connected to the cloud server based on the address information.
The method of claim 2,

The constructor terminal is pre-coupled with the AP,

The address information is obtained in advance by the constructor terminal based on the information received from the cloud server.
The method of claim 2,

The connection information includes service set identifier (SSID) information of the AP,

The address information includes uniform resource identifier (URI) information of the cloud server.
In the configurator terminal performing a method for transmitting information about a wireless device in a wireless LAN system, the configurator terminal,

A transceiver for transmitting and receiving a radio signal; And

A processor coupled to the transceiver, wherein the processor includes:

And is configured to obtain bootstrap information including list information regarding Easy Network Setup technology supported by the registrant terminal from the registrant terminal,

Is configured to receive a Device Provisioning Protocol (DPP) setting request frame from the registrant terminal,

And transmit a DPP configuration response frame to the registrant terminal in response to the DPP configuration request frame, wherein the DPP configuration response frame is associated with the list information and the connection information about the AP to be associated with the subscriber terminal; Terminal including network setup information for the description.
The method of claim 6,

When the list information includes identification information indicating an Open Connectivity Foundation (OCF), the network setup information includes address information of a cloud server for the registrant terminal.
The method of claim 7, wherein

The registrant terminal is connected to the AP based on the connection information,

The registrant terminal is connected to the cloud server based on the address information.
The method of claim 7, wherein

The constructor terminal is pre-coupled with the AP,

The terminal information is obtained in advance by the constructor terminal based on the information received from the cloud server.
The method of claim 7, wherein

The connection information includes service set identifier (SSID) information of the AP,

The address information terminal including the Uniform Resource Identifier (URI) information of the cloud server.
In the WLAN system for transmitting information about a wireless device,

Transmitting, by the registrant terminal, bootstrap information including list information of easy network setup technology supported by the registrant terminal to the constructor terminal;

Transmitting, by the registrant terminal, a Device Provisioning Protocol (DPP) setting request frame to the constructor terminal;

The registrant terminal receives a DPP configuration response frame from the configuration terminal in response to the DPP configuration request frame, wherein the DPP configuration response frame is connected information about the AP (access point) to be combined with the subscriber terminal and the list. Network setup information for the easy network setup technique associated with the information, wherein when the list information includes identification information indicating Open Connectivity Foundation (OCF), the network setup information is address information of a cloud server for the registrant terminal. Comprising;

The registrar terminal connecting with the AP based on the connection information; And

And by the registrant terminal, connecting with the cloud server based on the address information.