# US 2014/0153513 A1 · Method and apparatus for setting up an internet protocol address in a wireless communication system > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0153513 A1 - Document ID: US20140153513A1 - Status: Published application - Kind: A1 - Application number: 14/096,766 - Filed: 2013-12-04 - Published: 2014-06-05 - Earliest claimed: 2012-12-04 - Assignees: Samsung Electronics Co., Ltd. - Applicants: Samsung Electronics Co., Ltd. - Inventors: Jong-Hyo LEE; Ji-Hye Lee; Se-Hee Han; Jae-Eun Han; Chil-Youl Yang; Myoung-Hwan Lee; Chun-Ho Lee; Tae-Young Lee - Web page: https://patentgrep.com/patent/US20140153513A1 ## CPC - H04W 12/06: Authentication - H04L 61/5007: Internet protocol [IP] addresses - H04L 61/5014: using dynamic host configuration protocol [DHCP] or bootstrap protocol [BOOTP] - H04L 61/503: using an authentication, authorisation and accounting [AAA] protocol, e.g. remote authentication dial-in user service [RADIUS] or Diameter - H04W 8/26: Network addressing or numbering for mobility support - H04L 61/5038: for local use, e.g. in LAN or USB networks, or in a controller area network [CAN] - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A method and apparatus are provided for a client device to be allocated an Internet Protocol (IP) address by a Group Owner (GO) device, for direct communication between the client device and the GO device. The method includes transmitting, by the client device, an Association Request message to the GO device, receiving an Association Response message from the GO device, in response to the Association Request message, and receiving, by the client device, an IP address of the client device allocated by the GO device, during an authentication process between the client device and the GO device. ## Claims ### Claim 1 A method for setting up an Internet Protocol (IP) address between devices in a wireless communication system, the method comprising: transmitting, by a first device to a second device, an IP address pair proposed by the first device including a first IP address for the first device and a first IP address for the second counterpart device; receiving, by the first device from the second device, an IP pair proposed by the second device including a second IP address for the first device and a second IP address for the second device; determining one of the first device and the second device as a Group Owner (GO) device; determining the one of the first device and the second device not determined as the GO device as a client device; and determining a set IP address of the first device and a set IP address of the second device using the IP address pair proposed by the GO device. ### Claim 2 (depends on 1) The method of claim 1, further comprising performing Near Field Communication (NFC) tagging to establish an initial association between the first device and the second device. ### Claim 3 (depends on 1) The method of claim 1, further comprising discarding the IP address pair proposed by the client device. ### Claim 4 (depends on 1) The method of claim 1, wherein the IP address pair proposed by the first device is transmitted through a Handover Request message and the IP address pair proposed by the second device is transmitted through a Handover Select message. ### Claim 5 (depends on 4) The method of claim 4, wherein the Handover Request message and the Handover Select message further comprise information for determining the first device and the second device as the client device or the GO device. ### Claim 6 A method for allocating an Internet Protocol (IP) address to a client device by a Group Owner (GO) device, for direct communication between the GO device and the client device, the method comprising: transmitting, by the client device, an IP address allocation request to the GO device through an Association Request message; and receiving, by the client device, an IP address allocated to the client device by the GO device, through an Association Response message. ### Claim 7 (depends on 6) The method of claim 6, wherein the Association Request message includes a Client Address item for requesting the IP address of the client device, a Group Owner Address item for requesting an IP address of the GO device, and a Subnet Mask item for requesting information for identification of a subnet used by the client device and the GO device. ### Claim 8 (depends on 6) The method of claim 6, wherein the Association Response message includes the IP address of the client device, an IP address of the GO device, and information for identification of a subnet used by the client device and the GO device. ### Claim 9 (depends on 7) The method of claim 7, wherein the Association Request message further includes a Router Address item including a gateway address. ### Claim 10 A method of a client device to be allocated an Internet Protocol (IP) address by a Group Owner (GO) device for direct communication between the client device and the GO device, the method comprising: transmitting, by the client device, an Association Request message to the GO device; receiving an Association Response message from the GO device in response to the Association Request message; and receiving, by the client device, the IP address of the client device allocated by the GO device, during an authentication process between the client device and the GO device. ### Claim 11 (depends on 10) The method of claim 10, wherein the client device receives the IP address of the client device, an IP address of the GO device, and a subnet value used by the GO device through an IP Allocation Key Data Encryption (KDE). ### Claim 12 (depends on 11) The method of claim 11, wherein the IP Allocation KDE is included in an Extensible Authentication Protocol over Local Area Network (LAN) (EAPOL)-Key frame. ### Claim 13 (depends on 10) The method of claim 10, further comprising transmitting an IP address request to the GO device in the authentication process between the client device and the GO device. ### Claim 14 (depends on 13) The method of claim 13, wherein the client device transmits the IP address request to the GO device through an IP Address Request Key Data Encapsulation (KDE). ### Claim 15 (depends on 14) The method of claim 14, wherein the IP Address Request KDE is included in an Extensible Authentication Protocol over Local Area Network (LAN) (EAPOL)-Key frame. ### Claim 16 (depends on 10) The method of claim 10, wherein receiving the IP address of the client device comprises: Receiving a first random number from the GO device; generating a Pairwise Transient Key (PTK) and a second random number using the first random number and a Pairwise Master Key (PMK); transmitting the second random number and a Message Integrity Check (MIC) key to the GO device; and receiving, from the GO device, the IP address of the client device, an IP address of the GO device, a Robust Security Network Information Element (RSN IE), an MIC, and a Group Temporal Key (GTK). ### Claim 17 A method for allocating an Internet Protocol (IP) address to a client device by a Group Owner (GO) device for direct communication between the client device and the GO device, the method comprising: receiving, by the GO device, an Association Request message from the client device; transmitting an Association Response message to the client device, in response to the Association Request message; and transmitting, by the GO device, the IP address of the client device to the client device, during an authentication process between the GO device and the client device. ### Claim 18 (depends on 17) The method of claim 17, wherein the GO device transmits the IP address of the client device, an IP address of the GO device, and a subnet value used by the GO device through an IP Allocation Key Data Encapsulation (KDE). ### Claim 19 (depends on 18) The method of claim 18, wherein the IP Allocation KDE is included in an Extensible Authentication Protocol over Local Area Network (LAN) (EAPOL)-Key frame. ### Claim 20 (depends on 17) The method of claim 17, further comprising receiving an IP address allocation request from the client device in the authentication process between the client device and the GO device. ### Claim 21 (depends on 20) The method of claim 20, wherein the GO device receives the IP address allocation request from the client device through an IP Address Request Key Data Encapsulation (KDE). ### Claim 22 (depends on 20) The method of claim 20, wherein the IP Address Request KDE is included in an Extensible Authentication Protocol over Local Area Network (LAN) (EAPOL)-Key frame. ### Claim 23 (depends on 17) The method of claim 17, wherein transmitting the IP address of the client device comprises: transmitting a first random number to the client device; receiving a second random number and a first Message Integrity Check (MIC) from the client device; generating a Pairwise Transient Key (PTK) using the first random number and a Pairwise Master Key (PMK); performing verification with the first MIC; allocating the IP address to be used by the client device; and transmitting the IP address of the client device, an IP address of the GO device, a Robust Security Network Information Element (RSN IE), a second MIC, and a Group Terminal Key (GTK) to the client device. ### Claim 24 A device for setting up Internet Protocol (IP) addresses with another device in a wireless communication system, the device comprising: a transmitter configured to transmit, to the another device, an IP address pair proposed by the device including a first IP address for the device and a first IP address for the another; a receiver configured to receive an IP pair proposed by the another device including a second IP address for the device and a second IP address for the another device; and a controller configured to determine one of the device and the another device as a Group Owner (GO) device, determine the one of the device and the another device not determined as the GO device as a client device, and determine a set IP address of the device and a set IP address of the another device using the IP address pair proposed by the GO device. ### Claim 25 (depends on 24) The device of claim 24, wherein the transmitter and the receiver are configured to perform Near Field Communication (NFC) tagging to establish an initial association between the device and the another device. ### Claim 26 (depends on 24) The device of claim 24, wherein the controller is configured to discard the IP address proposed by the client device. ### Claim 27 (depends on 24) The device of claim 24, wherein the IP address pair proposed by the device is transmitted through a Handover Request message and the IP address pair proposed by the another device is received through a Handover Select message. ### Claim 28 (depends on 27) The device of claim 27, wherein the Handover Request message and the Handover Select message further comprise information for determining the device and the another device as the client device or the GO device. ### Claim 29 A device to be allocated an Internet Protocol (IP) address by a counterpart device, for direct communication between the device and the counterpart device, the device comprising: a controller configured to determine the counterpart device and the device as a Group Owner (GO) device and a client device, respectively; a transmitter configured to transmit an IP address allocation request to the GO device through an Association Request message; and a receiver configured to receive the IP address of the client device allocated by the GO device through an Association Response message, in response to the Association Request message. ### Claim 30 (depends on 29) The device of claim 29, wherein the Association Request message comprises a Client Address item for requesting the IP address of the client device, a Group Owner Address item for requesting an IP address of the GO device, and a Subnet Mask item for requesting information for identification of a subnet used by the client device and the GO device. ### Claim 31 (depends on 29) The device of claim 29, wherein the Association Response message comprises the IP address of the client device, an IP address of the GO device, and information for identification of a subnet used by the client device and the GO device. ### Claim 32 (depends on 30) The device of claim 30, wherein the Association Request message further comprises a Router Address including a gateway address. ### Claim 33 A client device to be allocated an Internet Protocol (IP) address by a Group Owner (GO) device, for direct communication between the client device and the GO device, the client device comprising: a transmitter configured to transmit an Association Request message to the GO device; and a receiver configured to receive an Association Response message from the GO device, in response to the Association Request message, and to receive an IP address of the client device allocated by the GO device during an authentication process between the client device and the GO device. ### Claim 34 (depends on 33) The client device of claim 33, wherein the receiver is configured to receive the IP address of the client device, an IP address of the GO device, and a subnet value used by the GO device through an IP Allocation Key Data Encryption (KDE). ### Claim 35 (depends on 34) The client device of claim 34, wherein the IP Allocation KDE is included in an Extensible Authentication Protocol over Local Area Network (LAN) (EAPOL)-Key frame. ### Claim 36 (depends on 33) The client device of claim 33, further comprising: a transmitter configured to transmit an IP address request to the GO device during the authentication process between the client device and the GO device. ### Claim 37 (depends on 36) The client device of claim 36, wherein the transmitter is configured to transmit the IP address request to the GO device through an IP Address Request Key Data Encapsulation (KDE). ### Claim 38 (depends on 36) The client device of claim 36, wherein the IP Address Request KDE is included in an Extensible Authentication Protocol over Local Area Network (LAN) (EAPOL)-Key frame. ### Claim 39 (depends on 33) The client device of claim 33, wherein the receiver is configured to receive a first random number, the IP address of the client device, an IP address of the GO device, a Robust Security Network Information Element (RSN IE), a Message Integrity Check (MIC), and a Group Temporal Key (GTK) from the GO device, wherein the client device further comprises a controller configured to generate a Pairwise Transient Key (PTK) and a second random number using the first random number and a Pairwise Master Key (PMK), and wherein the transmitter is configured to transmit the second random number and a MIC key to the GO device. ### Claim 40 A Group Owner (GO) device for allocating an Internet Protocol (IP) address to a client device for direct communication between the client device and the GO device, the GO device comprising: a receiver configured to receive an Association Request message from the client device; and a transmitter configured to transmit an Association Response message to the client device, in response to the Association Request message, and to transmit the IP address of the client device to the client device during an authentication process between the GO device and the client device. ### Claim 41 (depends on 40) The GO device of claim 40, wherein the transmitter is configured to transmit the IP address of the client device, an IP address of the GO device, and a subnet value used by the GO device through an IP Allocation Key Data Encapsulation (KDE). ### Claim 42 (depends on 41) The GO device of claim 41, wherein the IP Allocation KDE is included in an Extensible Authentication Protocol over Local Area Network (LAN) (EAPOL)-Key frame. ### Claim 43 (depends on 40) The GO device of claim 40, wherein the receiver is configured to receive an IP address allocation request from the client device during the authentication process between the client device and the GO device. ### Claim 44 (depends on 43) The GO device of claim 43, wherein the receiver is configured to receive the IP address allocation request from the client device through an IP Address Request Key Data Encapsulation (KDE). ### Claim 45 (depends on 43) The GO device of claim 43, wherein the IP Address Request KDE is included in an Extensible Authentication Protocol over Local Area Network (LAN) (EAPOL)-Key frame. ### Claim 46 (depends on 41) The GO device of claim 41, wherein the transmitter is configured to transmit a first random number, the IP address of the client device, an IP address of the GO device, a Robust Security Network Information Element (RSN IE), a first Message Integrity Code (MIC), and a Group Terminal Key (GTK) to the client device, wherein the GO device further comprises a controller configured to generate a Pairwise Transient Key (PTK) using the first random number and a Pairwise Master Key (PMK), to perform verification with a second MIC, and allocate the IP address to be used by the client device, and wherein the receiver is configured to receive a second random number and the second MIC from the client device.