WO2016171527A1 - 무선 통신 시스템에서 nan 프록시 서버에 등록을 수행하는 방법 및 장치 - Google Patents
무선 통신 시스템에서 nan 프록시 서버에 등록을 수행하는 방법 및 장치 Download PDFInfo
- Publication number
- WO2016171527A1 WO2016171527A1 PCT/KR2016/004290 KR2016004290W WO2016171527A1 WO 2016171527 A1 WO2016171527 A1 WO 2016171527A1 KR 2016004290 W KR2016004290 W KR 2016004290W WO 2016171527 A1 WO2016171527 A1 WO 2016171527A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- nan
- proxy server
- proxy
- nan proxy
- client
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/06—Registration at serving network Location Register, VLR or user mobility server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/06—De-registration or detaching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W56/00—Synchronisation arrangements
- H04W56/001—Synchronization between nodes
- H04W56/0015—Synchronization between nodes one node acting as a reference for the others
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
- H04W84/20—Master-slave selection or change arrangements
Definitions
- the present specification relates to a wireless communication system, and more particularly, to a method and apparatus for performing registration with a NAN proxy server in a wireless communication system.
- Wireless communication systems are widely deployed to provide various kinds of communication services such as voice and data.
- 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.).
- 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).
- CDMA code division multiple access
- FDMA frequency division multiple access
- TDMA time division multiple access
- OFDMA orthogonal frequency division multiple access
- SC-FDMA single carrier frequency division multiple access
- MCD division multiple access
- MCDMA multi-carrier frequency division multiple access
- MC-FDMA multi-carrier frequency division multiple access
- 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.
- PDAs personal digital assistants
- PMPs portable multimedia players
- An object of the present specification is to provide a method and apparatus for performing registration with a NAN proxy server in a wireless communication system.
- An object of the present specification is to provide a method in which a neighbor awareness networking (NAN) terminal performs a role of a proxy server and a proxy client in a wireless communication system.
- NAN neighbor awareness networking
- the purpose of this specification is to provide a data transmission or power saving function for a NAN terminal serving as a proxy server.
- a wireless communication system may provide a method for a NAN proxy client to register with a NAN proxy server.
- the method for the NAN proxy client to register with the NAN proxy server may include transmitting a subscription message for proxy service discovery to the NAN proxy server, receiving a publish message from the NAN proxy server, and based on the proxy service.
- the method may include transmitting a proxy registration request message to a NAN proxy server and receiving a proxy registration response message based on the proxy registration request message.
- the publish message is a message indicating that the proxy service is supported by the NAN proxy server.
- the NAN proxy client may include a receiving module for receiving the information from the external device, a transmitting module for transmitting the information to the external device, and a processor for controlling the receiving module and the transmitting module.
- the processor sends a subscription message for proxy service discovery to the NAN proxy server, receives a publish message from the NAN proxy server, sends a proxy registration request message to the NAN proxy server based on the proxy service, and registers a proxy.
- the proxy registration response message may be received based on the request message.
- the publish message is a message indicating that the proxy service is supported by the NAN proxy server.
- the NAN proxy client is registered with the NAN proxy server, and the registered NAN proxy client is registered in the first discovery window cycle. It can be awake based.
- the followings may be commonly applied to a method and a NAN terminal device performing a proxy role in a wireless communication system.
- the information on the first discovery window period may be included in the proxy registration request message and transmitted to the NAN proxy server.
- the NAN proxy server may be awake based on the second discovery window period, and the first discovery window period may be set to an integer multiple of the second discovery window period.
- the proxy registration response message may include at least one or more of information indicating whether registration is permitted or registration ID information.
- the NAN proxy server may perform a publishing and subscription function of the NAN proxy client instead.
- a NAN proxy client registered to a NAN proxy server may perform a deregistration procedure.
- the deregistration procedure may include transmitting a deregistration request message to a NAN proxy server and receiving a deregistration response message from a NAN proxy server.
- the NAN proxy client deregisters from the NAN proxy server, and other NAN proxy registered with the NAN proxy server for information on deregistration. Can be provided to clients.
- the method may further include receiving a first frame including information on proxy server capability from the NAN proxy server.
- the first frame may be any one of a NAN beacon frame and a NAN service discovery frame.
- the first frame includes a NAN proxy server attribute field
- the NAN proxy server attribute field includes at least one of a proxy server address field, a proxy server capability field, an awake interval field, and a BSSID field.
- a proxy server address field includes at least one of a proxy server address field, a proxy server capability field, an awake interval field, and a BSSID field.
- the method may further include transmitting a second frame including the proxy client capability information to the NAN proxy server.
- the second frame may include a NAN proxy client attribute field
- the NAN proxy server attribute field may include at least one of a proxy client address field, a proxy server address field, an awake interval field, and a BSSID field.
- a registered NAN proxy client receives a first frame from a NAN proxy server in a discovery window that is awakened based on a first discovery window period, and based on the first frame, a NAN proxy client. You can synchronize with the server.
- the second frame may be transmitted to the NAN proxy server based on the first frame, and the second frame may include information indicating that registration of the NAN proxy client is maintained.
- the present disclosure can provide a method and apparatus for performing registration with a NAN proxy server in a wireless communication system.
- the present disclosure may provide a method in which a neighbor awareness networking (NAN) terminal performs a role of a proxy server and a proxy client in a wireless communication system.
- NAN neighbor awareness networking
- a NAN terminal serving as a proxy server may provide a data transmission or a power saving function.
- FIG. 1 is a diagram illustrating an exemplary structure of an IEEE 802.11 system.
- 2 to 3 are diagrams illustrating a NAN cluster.
- FIG. 4 illustrates a structure of a NAN terminal.
- FIG. 7 is a diagram illustrating a state transition of a NAN terminal.
- FIG. 8 is a diagram illustrating a discovery window and the like.
- FIG. 10 is a diagram illustrating a method in which a NAN terminal registers as a NAN proxy client in a NAN proxy server.
- FIG. 11 is a diagram illustrating a method of releasing registration by a NAN proxy client registered in a NAN proxy server.
- FIG. 12 is a diagram illustrating a discovery window period for a NAN proxy server and a NAN proxy client.
- FIG. 13 is a diagram illustrating a method in which a NAN proxy server supports a NAN terminal.
- FIG. 14 is a diagram illustrating a method of managing NAN proxy clients registered to a plurality of NAN proxy servers.
- 15 is a flowchart illustrating a method of performing a proxy role.
- 16 is a block diagram of a terminal device.
- 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.
- 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.
- 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.
- CDMA code division multiple access
- FDMA frequency division multiple access
- TDMA time division multiple access
- OFDMA orthogonal frequency division multiple access
- SC-FDMA single carrier frequency division multiple access
- 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).
- GSM Global System for Mobile communications
- GPRS General Packet Radio Service
- EDGE Enhanced Data Rates for GSM Evolution
- 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).
- 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.
- 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.
- FIG. 1 is a diagram showing an exemplary structure of an IEEE 802.11 system to which the present invention can be applied.
- the IEEE 802.11 architecture may be composed 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 in an IEEE 802.11 WLAN.
- FIG. 1 exemplarily shows that two BSSs (BSS1 and BSS2) exist and include two STAs as members of each BSS (STA1 and STA2 are included in BSS1 and STA3 and STA4 are included in BSS2). do.
- 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).
- BSA basic service area
- the most basic type of BSS in an IEEE 802.11 WLAN is an independent BSS (IBSS).
- the IBSS may have a minimal form consisting of only two STAs.
- 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.
- this type of WLAN is not configured in advance, but may be configured when a WLAN is required, and may be referred to as an ad-hoc network.
- the membership of the STA in the BSS may be dynamically changed by turning the STA on or off, the STA entering or exiting the BSS region, and the like.
- the STA may join the BSS using a synchronization process.
- the STA In order to access all services of the BSS infrastructure, the STA must be associated with the BSS. This association may be set up dynamically and may include the use of a Distribution System Service (DSS).
- DSS Distribution System Service
- FIG. 1 illustrates components of a distribution system (DS), a distribution system medium (DSM), an access point (AP), and the like.
- DS distribution system
- DSM distribution system medium
- AP access point
- the station-to-station distance directly in the WLAN may be limited by PHY performance. In some cases, this distance limit may be sufficient, but in some cases, communication between more distant stations may be necessary.
- the distribution system DS may be configured to support extended coverage.
- the DS refers to a structure in which BSSs are interconnected. Specifically, instead of the BSS independently as shown in FIG. 1, the BSS may exist as an extended type component of a network composed of a plurality of BSSs.
- DS is a logical concept and can be specified by the nature of the distribution system medium (DSM).
- the IEEE 802.11 standard logically distinguishes between wireless medium (WM) and distribution system media (DSM). Each logical medium is used for a different purpose and is used by different components.
- the definition of the IEEE 802.11 standard does not limit these media to the same or to different ones. In this way the plurality of media are logically different, the flexibility of the IEEE 802.11 WLAN structure (DS structure or other network structure) can be described. That is, the IEEE 802.11 WLAN structure can be implemented in various ways, the corresponding WLAN structure can be specified independently by the physical characteristics of each implementation.
- the DS may support the mobile device by providing seamless integration of multiple BSSs and providing logical services for handling addresses to destinations.
- An AP refers to an entity that enables access to a DS through WM for associated STAs and has STA functionality. Data movement between the BSS and the DS may be performed through the AP.
- STA2 and STA3 shown in FIG. 1 have the functionality of a STA, and provide a function to allow associated STAs STA1 and STA4 to access the DS.
- all APs basically correspond to STAs, all APs are addressable entities. The address used by the AP for communication on the WM and the address used by the AP for communication on the DSM need not necessarily be the same.
- Data transmitted from one of the STAs associated with an AP to the STA address of that AP may always be received at an uncontrolled port and processed by an IEEE 802.1X port access entity.
- transmission data (or frame) may be transmitted to the DS.
- the operation of the STA operating in the WLAN system may be described in terms of a layer structure.
- the hierarchy may be implemented by a processor.
- the STA may have a plurality of hierarchical structures.
- the hierarchical structure covered by the 802.11 standard document is mainly the MAC sublayer and physical (PHY) layer on the DLL (Data Link Layer).
- the PHY may include a Physical Layer Convergence Procedure (PLCP) entity, a Physical Medium Dependent (PMD) entity, and the like.
- PLCP Physical Layer Convergence Procedure
- PMD Physical Medium Dependent
- the MAC sublayer and PHY conceptually contain management entities called MAC sublayer management entities (MLMEs) and physical layer management entities (PLMEs), respectively.These entities provide a layer management service interface on which layer management functions operate. .
- SME Station Management Entity
- An SME is a layer-independent entity that can appear to be in a separate management plane or appear to be off to the side. While the exact features of the SME are not described in detail in this document, they generally do not include the ability to collect layer-dependent states from various Layer Management Entities (LMEs), and to set similar values for layer-specific parameters. You may seem to be in charge. SMEs can generally perform these functions on behalf of general system management entities and implement standard management protocols.
- LMEs Layer Management Entities
- the aforementioned entities interact in a variety of ways.
- entities can interact by exchanging GET / SET primitives.
- a primitive means a set of elements or parameters related to a particular purpose.
- the XX-GET.request primitive is used to request the value of a given MIB attribute (management information based attribute information).
- the XX-GET.confirm primitive is used to return the appropriate MIB attribute information value if the Status is "Success", otherwise it is used to return an error indication in the Status field.
- the XX-SET.request primitive is used to request that the indicated MIB attribute be set to a given value. If the MIB attribute means a specific operation, this is to request that the operation be performed.
- the XX-SET.confirm primitive confirms that the indicated MIB attribute is set to the requested value when status is "success", otherwise it is used to return an error condition in the status field. If the MIB attribute means a specific operation, this confirms that the operation has been performed.
- the MLME and SME may exchange various MLME_GET / SET primitives through a MLME_SAP (Service Access Point).
- various PLME_GET / SET primitives may be exchanged between PLME and SME through PLME_SAP and may be exchanged between MLME and PLME through MLME-PLME_SAP.
- NAN Neighbor Awareness Networking
- the NAN network may consist of NAN terminals using the same set of NAN parameters (eg, time interval between successive discovery windows, interval of discovery window, beacon interval or NAN channel, etc.).
- the NAN terminals may configure a NAN cluster, where the NAN cluster uses the same set of NAN parameters and means a set of NAN terminals synchronized to the same discovery window schedule.
- 2 shows an example of a NAN cluster.
- 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.
- one or more NAN masters may exist in the NAN cluster, and the NAN master may be changed.
- the NAN master may transmit both a sync beacon frame, a discovery beacon frame, and a NAN service discovery frame.
- the NAN terminal is based on a physical layer of 802.11, and includes a NAN discovery engine, a NAN medium access control (MAC), and applications (Application 1, Application 2, ..., Application N).
- NAN APIs are the main component.
- the service request and response are processed through the NAN discovery engine, and the NAN MAC processes the NAN Beacon frames and the NAN Service Discovery frame.
- the NAN discovery engine can provide the functionality of subscribe, publish, and follow-up.
- the publish / subscribe function operates from the service / application through the service interface. When the publish / subscribe command is executed, an instance of the publish / subscribe function is created. Each instance runs independently, and depending on the implementation, several instances can run simultaneously.
- the follow-up function is a means for a service / application to send and receive service specific information.
- the NAN terminal may perform a master role and this may be changed. That is, the NAN terminal may transition various roles and states, and an example thereof is illustrated in FIG. 7.
- the role and state that a NAN terminal may have include a master (hereinafter, master is a master role and sync.State), a non-master sync, a non-master non-sync Sync) and the like.
- master is a master role and sync.State
- non-master sync a non-master non-sync Sync
- Each role and state may determine whether to transmit a discovery beacon frame and / or a sync beacon frame, which may be illustrated in Table 1 below.
- the state of the NAN terminal may be determined through a master rank.
- the master rank indicates the will of the NAN terminal to operate as a NAN master. In other words, a large value indicates a large preference for the NAN master.
- NAN MR may be determined by the following equation (1) by the Master Preference, Random Factor, Device MAC address.
- the Master Preference, Random Factor, and Device MAC address may be indicated through a master indication attribute included in a NAN Beacon frame.
- the master indication attorney may be as illustrated in Table 2 below.
- the NAN terminal that activates the NAN service and starts the NAN cluster sets both the Master Preference and the Random Factor to 0, and resets the NANWarmUp. Until the NANWarmUp expires, the NAN terminal should set the Master Preference field value in the master indication attribute to a value greater than 0 and set the Random Factor value in the master indication attribute to a new value.
- a NAN terminal joining a NAN cluster having an anchor master's Master Preference set to a value greater than 0 may set the Master Preference to a value greater than 0 and set a Random Factor to a new value regardless of whether NANWarmUp expires. .
- the NAN terminal may be an anchor master of the NAN cluster according to the MR value. That is, all NAN terminals have the capability to operate as an anchor master.
- the anchor master means a device having the largest MR in the NAN cluster, having a HC (Hop count to the Anchor Master) value of 0 and having the smallest Anchor Master Beacon Transmit Time (AMBTT) value.
- Two anchor masters may exist temporarily in a NAN cluster, but one anchor master is a principle.
- the NAN terminal which becomes the anchor master in the already existing NAN cluster uses the time synchronization function (TSF) used in the existing NAN cluster as it is.
- TSF time synchronization function
- the NAN terminal may be an anchor master in the following case.
- a new NAN cluster is started, when a master rank is changed (when the MR value of another NAN terminal is changed or when the anchor master's own MR is changed), or when the beacon frame of the current anchor master is no longer received, the NAN The terminal may be an anchor master.
- the NAN terminal may lose the status of the anchor master.
- the anchor master may be determined by an anchor master selection algorithm as described below. That is, the anchor master selection is an algorithm for determining which NAN terminal is the anchor master of the NAN cluster, and each NAN terminal drives the anchor master selection algorithm when participating in the NAN cluster.
- the NAN terminal When the NAN terminal starts a new NAN cluster, the NAN terminal becomes an anchor master of the new NAN cluster. NAN sync beacon frames with hop counters exceeding the threshold are not used by the NAN terminal. Otherwise NAN sync beacon frame is used to determine the anchor master of the NAN cluster.
- the NAN terminal Upon receiving a NAN sync beacon frame having a hop counter that does not exceed the threshold, the NAN terminal compares the stored anchor master rank value with the anchor master rank value in the beacon frame. If the stored anchor master rank value is larger than the anchor master value in the beacon frame, the NAN terminal discards the anchor master value in the beacon frame. If the stored anchor master rank value is smaller than the anchor master value in the beacon frame, the NAN terminal stores a new value increased by 1 in the anchor master rank and the hop counter included in the beacon frame and the AMBTT value in the beacon frame. Also, if the stored anchor master rank value is equal to the anchor master value in the beacon frame, the hop counter is compared. If the hop counter value of the beacon frame is larger than the stored value, the NAN terminal ignores the received beacon frame.
- the NAN terminal When the hop counter value of the beacon frame is equal to (stored value? 1) and the AMBTT value is larger than the stored value, the NAN terminal newly stores the AMBTT value of the beacon frame. If the hop counter value of the beacon frame is less than (stored value? 1), the NAN terminal increments the hop counter value of the beacon frame by one.
- the stored AMBTT value is updated according to the following rules. If the received beacon frame is transmitted by the anchor master, the AMBTT value is set to the lowest 4 octet value of the time stamp included in the beacon. If the received beacon frame is received from a device other than the NAN master or master sink, the AMBTT value is set to a value included in the NAN cluster attribute of the received beacon.
- the NAN terminal assumes itself as an anchor master and sets an anchor master record. You can update it.
- the NAN terminal not the anchor master compares the changed MR with the stored value. If the changed MR value of the NAN terminal is larger than the stored value, the NAN terminal may assume itself as an anchor master and update the anchor master record.
- the NAN terminal sets the anchor master field of the cluster attribute in the NAN sync and discovery beacon frame to the value in the anchor master record, except when the anchor master sets the AMBTT value to the TSF value of the corresponding beacon transmission. Can be.
- the NAN terminal transmitting the NAN sync or discovery beacon frame may ensure that the TSF of the beacon frame will be derived from the same anchor master included in the cluster attribute.
- the NAN terminal i) when the NAN beacon indicates an anchor master rank of a value larger than the anchor master record of the NAN terminal, ii) the NAN beacon indicates an anchor master rank of the same value as the anchor master record of the NAN terminal,
- the TSF timer value in the NAN beacon received with the same cluster ID may be applied.
- NAN terminals participating in the same NAN cluster may be synchronized to a common clock.
- TSF of the NAN cluster may be implemented by a distributed algorithm that must be performed in all NAN terminals.
- Each NAN terminal participating in the NAN cluster may transmit NAN Sync. Beacon frames according to the algorithm.
- the device may synchronize its clock during the discovery window DW.
- the length of the discovery window is 16 TUs.
- one or more NAN terminals may transmit synchronization beacon frames to help all NAN terminals in the NAN cluster synchronize their clocks.
- the transmission time of the NAN Beacon frame is a discovery window interval existing every 512 TUs. All NAN terminals may participate in NAN beacon generation and transmission according to the role and state of the device. Each NAN terminal must maintain its own TSF timer used for NAN beacon cycle timing.
- the NAN sync beacon period may be established by the NAN terminal generating the NAN cluster. A series of TBTTs are defined such that the discovery window interval that can transmit a sync beacon frame is exactly 512 TU apart. A time of zero is defined as the first TBTT, and the discovery window starts at each TBTT.
- Each NAN terminal serving as a master transmits a NAN discovery beacon frame outside the NAN discovery window.
- the NAN terminal in the master role transmits the NAN discovery beacon every 100 TUs.
- the time between successive NAN discovery beacons transmitted from the same NAN terminal is 200 TUs or less.
- the NAN terminal in the master role may omit transmission of the NAN discovery beacon.
- the NAN terminal in the master role may use a WMM Access Category-Voice (AC_VO) contention setting.
- AC_VO WMM Access Category-Voice
- FIG. 8 illustrates a relationship between the transmission of the NAN discovery beacon frame, the NAN sync / discovery beacon frame, and the discovery window.
- FIG. 8 (a) shows transmission of a NAN discovery beacon and a sync beacon frame of a NAN terminal operating in a 2.4 GHz band
- FIG. 8 (b) shows a NAN discovery beacon and synchronization of a NAN terminal operating in a 2.4 GHz and a 5 GHz band. Indicates transmission of a beacon frame.
- each NAN terminal serving as a master may transmit a synchronization beacon frame in the discovery window and may transmit a discovery beacon frame outside the discovery window.
- the discovery window may be repeated every 512 TUs.
- the duration of the discovery window may be 16 TU.
- the discovery window may last for 16 TUs.
- all NAN terminals in the NAN cluster are awakened for each discovery window to receive a synchronization beacon frame from the master NAN terminal, thereby maintaining the NAN cluster.
- power consumption of the terminal may be severe. Therefore, there may be a need for a method of reducing power consumption by dynamically controlling the duration of the discovery window while maintaining synchronization in one NAN cluster.
- the NAN terminal may operate in the 2.4 GHz band or the 5 GHz band.
- the NAN terminal may operate in the Sub 1 GHz band.
- the NAN terminal may be configured to support IEEE 802.11ah supporting the Sub 1 GHz band.
- the NAN terminal may have a different link quality and physical model from 2.4GHz or 5GHz.
- the NAN terminal when the NAN terminal supports 900MHz, the NAN terminal may transmit a signal farther, and may perform communication in a wide range. In this case, data communication between NAN terminals may be performed, and data may be exchanged between NAN terminals.
- the method of efficiently operating power in the NAN terminal may be a problem because it is based on data communication.
- a method of setting a discovery window section may be differently set. 9 is a basic structure in which a synchronization beacon frame is transmitted within a discovery window and a discovery beacon frame is transmitted outside the discovery window, and may be similarly applied to a NAN terminal supporting a 900 MHz band.
- FIG. 10 is a diagram illustrating a method in which a NAN terminal registers as a NAN proxy client in a NAN proxy server.
- the NAN terminals may perform data communication.
- the NAN terminal may awake in the discovery window to receive a frame. In this case, a large amount of power may be consumed when the NAN terminal awakes in all discovery windows to perform a procedure for performing data communication.
- a NAN proxy terminal may be defined as a new role (concept) for the NAN terminal as a method of reducing power consumption of the NAN terminal.
- the NAN proxy terminal may be a NAN proxy server or a NAN proxy client.
- the NAN proxy server may perform a procedure for data communication to the NAN proxy client instead.
- the NAN proxy server may publish and / or subscribe on behalf of the NAN proxy client.
- the NAN proxy server may provide the other NAN terminals with information provided by the NAN proxy client to perform data communication with the other NAN terminals. That is, the NAN proxy server may perform a procedure for data communication on behalf of the NAN proxy client in order to reduce power consumption of the NAN proxy client.
- the NAN proxy server may be a terminal that is not sensitive to power consumption.
- the NAN proxy client may be a terminal operating based on low power. In such a situation, if the NAN proxy client awakes in every discovery window in the same manner as the existing NAN terminal, power consumption may be severe and may interfere with use. Therefore, by using a terminal that is not sensitive to power consumption, the procedure for data communication can be replaced, thereby efficiently performing data communication while reducing power consumption.
- the NAN proxy server in order for the NAN proxy server to perform a procedure for data communication on behalf of the NAN proxy client, it is necessary to obtain information about the NAN proxy client. To this end, the NAN proxy client can be registered with the NAN proxy server.
- a method of registering a NAN proxy client with a NAN proxy server will be described.
- the NAN terminal serving as a proxy server may be a NAN proxy server.
- the NAN proxy server may provide information to other NAN terminals that it can operate as a NAN proxy server.
- the NAN proxy server may include information on the NAN proxy server role in a broadcast message.
- other NAN terminals may identify the NAN proxy server based on the broadcast message.
- the NAN proxy server may provide information indicating the role of the NAN proxy server to other NAN terminals as a publish message, and is not limited to the above-described embodiment.
- the NAN terminals 1010 and 1030 may transmit a subscription message to the NAN proxy server 1020 to find a service of the NAN proxy server 1020. have.
- the NAN terminals 1010 and 1030 may have a hierarchical structure as described above.
- the service / application terminal of the first NAN device A 1010 may apply a subscription to the discovery engine DE of the first NAN terminal 1010 and the NAN MAC as a method. Can provide.
- the primitives of the subscription methods provided to the NAN DE and the NAC MAC by the service / application terminal may be as shown in Table 3 below. That is, the service / application stage may provide information about Table 3 to the NAN DE and NAC MAC stages. More specifically, the service / application stage provides the NAN DE and the NAN MAC stage with information about a service name, service specific information, and configuration parameter that the NAN terminal is to search for. can do.
- the first NAN terminal 1010 may transmit a subscription message to the NAN proxy server 1020. That is, the first NAN terminal 1010 may transmit the subscribe message to the NAN proxy server 1020 based on the subscribe method as an active subscribe.
- the NAN proxy server 1020 matches a Service ID for a service that the NAN proxy server 1020 can provide to publish a publish message. It may transmit to the first NAN terminal 1010.
- the publish type of the publish message may be Solicited.
- the service / application stage publishing method of the NAN proxy server 1020 may be provided to the NAN DE and NAN MAC stages of the NAN proxy server 1020.
- primitives of the publishing method may be as follows.
- the service / application stage may provide information about Table 4 to the NAN DE and NAC MAC stages. More specifically, the service / application stage may include information on a service name, service specific information, and configuration parameters supported by the NAN proxy server 1020, such as NAN DE and NAN MAC. Can be provided at the stage.
- the configuration information may include publish type information indicating that solicited transmission is performed.
- Solicited transmission type information indicating whether the solicited transmission is unicast or broadcast may be included.
- time to live information may be included as information about a time when the publishing function is performed.
- event conditions information indicating whether an event is generated may be included.
- the NAN DE and NAN MAC terminals of the first NAN terminal 1010 receive a discovery result as an event and the first NAN terminal. It may be provided to the service / application stage of 1010. In this way, the first NAN terminal 1010 may complete a service search of the NAN proxy server 1020.
- primitives of the discovery result event may be as shown in Table 5 below.
- the NAN DE and NAN MAC stages include subscribe id information for identifying a subscription function, service_specific_info information as specific service information supported by the NAN proxy server, publish_id information as publish ID information, and address as address information of the proxy server.
- the discovery result event including the information may be provided to the service / application stage.
- the second NAN device (NAN Device B) 1030 may also search for a service of the NAN proxy server 1020 based on the same method as the first NAN terminal 1010.
- the service search for the NAN proxy server 1020 may be separately performed in each of the NAN terminals 1010 and 1030.
- the service / application terminal of the second NAN terminal 1030 that has completed the search for the service of the NAN proxy server 1020 publishes to the NAN DE and NAN MAC terminals of the second NAN terminal 1030. Can be provided.
- Primitives used by the second NAN terminal 1030 to register with the NAN proxy server may be defined as shown in Tables 6 and 7 below. More specifically, the service / application stage of the second NAN terminal 1030 is a publishing method, and the NAN DE and NAN MAC stages of the second NAN terminal 1030 are configured to provide information about proxy registration according to Tables 6 and 7 below. Can be provided to That is, the second NAN terminal 1030 may provide information on proxy registration by reusing existing publish methods and subscribe methods. However, as an example, when the existing publishing method and the subscription method are reused, the service_specific_info field may include information for registering with the proxy server instead of information for the second NAN terminal 1030 to publish. . That is, the second NAN terminal 1030 may use a method to include information on registration using the existing publish method and subscribe method formats as they are.
- the second NAN terminal 1030 may newly define and use Primitives for a method called for registration. That is, the service / application terminal of the second NAN terminal 1030 may provide information about proxy registration by providing a newly defined ProxyRegistration method to the NAN DE and NAN MAC of the second NAN terminal 1030. have.
- Primitives of the newly defined proxy registration method may be as shown in Table 8 below.
- the service / application terminal of the second NAN terminal 1030 may provide a method to the NAN DE and the NAN MAC for NAN proxy server registration.
- the provided method may be a method using an existing publishing method format and including information on proxy registration.
- the method may be a newly defined method for proxy registration, and is not limited to the above-described embodiment.
- the NAN DE and NAN MAC terminals of the second NAN terminal 1030 may transmit a proxy registration request to the NAN proxy server 1020.
- the proxy registration request may be a publish message.
- the proxy registration request may be a type of publishing as a service discovery frame.
- the service discovery attribute for the proxy registration request may be as shown in Table 9 below.
- the Service ID field may be an essential field for the following fields included in the proxy registration request.
- the Service ID field may be defined as a proxy service ID as a service provided by the NAN proxy server.
- the proxy registration request field may include information necessary for the NAN terminal to register with the NAN proxy server.
- a field included in the proxy registration request may include a proxy request TLV (Proxy Registration Request TLV) in the Service Info field.
- the proxy request TLV may be as shown in Table 10 below.
- the proxy request TLV may include an Availability Time field indicating a DW duration that is awakened after the NAN terminal is registered as a proxy client.
- the NAN terminal may include a Service ID field that is an ID for a service requested by the NAN proxy server.
- other information necessary for the NAN terminal to register as a NAN proxy server may be included in the NAN proxy request TLV, which is not limited to the above-described embodiment.
- the NAN proxy server may transmit a proxy response to the second NAN terminal 1030 in response to the proxy request.
- the proxy response may be a publish message.
- the proxy registration response may be published as a service discovery frame.
- the service discovery attribute for the proxy registration response may be as described in Table 9 above.
- the Service ID field may be an essential field for the following fields included in the proxy registration response.
- the Service ID field may be defined as a proxy service ID as a service provided by the NAN proxy server.
- the proxy registration response field may include information necessary for the NAN terminal to register with the NAN proxy server.
- a field included in the proxy registration response may include a proxy response TLV (Proxy Registration Request TLV) in the Service Info field.
- the proxy response TLV may be as shown in Table 11 below.
- the proxy response TLV may include a status indication field indicating whether the NAN proxy server allows the NAN terminal to be registered.
- the proxy response TLV may include a Registration ID field indicating a registration ID.
- the Service ID field may be included as an ID for a service provided by the NAN proxy server.
- other information necessary for the NAN terminal to register as a NAN proxy server may be included in the NAN proxy response TLV, which is not limited to the above-described embodiment.
- the NAN DE and the NAN MAC of the second NAN terminal 1030 may provide a discovery result event to the service / application stage when receiving a confirmation from the NAN proxy server.
- the second NA terminal 1030 may be a NAN proxy client registered with the NAN proxy server based on the discovery result event.
- the NAN terminal may be a NAN proxy client registered with the NAN proxy server.
- FIG. 11 is a diagram illustrating a method of releasing registration by a NAN proxy client registered in a NAN proxy server.
- the NAN proxy client 1130 may maintain a registered state with the NAN proxy server 1120. In this case, as an example, the NAN proxy client 1130 may release registration with respect to the NAN proxy server 1120. For example, the NAN proxy client 1130 may release registration from the NAN proxy server 1120 based on a distance problem or a power consumption problem, and is not limited to the above-described embodiment.
- the service / application stage of the NAN proxy client 1130 may call a method and provide it to the NAN DE and the NAN MAC.
- the called method may use an existing follow-up transmit method format.
- the method may be a newly defined Proxy DeRegistration method. That is, a method for deregistering a proxy may be called and is not limited to the above-described embodiment.
- the Follow-up Transmit method may be as shown in Table 12 below.
- the Proxy DeRegistration method may be as shown in Table 13 below.
- the method may include information about an ID.
- registration_id and Proxy Server Address may be included in Service_specific_info.
- information necessary for proxy deregistration may be included in Service_specific_info while using an existing format.
- registration_id and Proxy Server Address may be provided independently.
- the NAN proxy client 1130 may send a follow-up message to the NAN proxy server 1120.
- the follow-up message may be a follow-up proxy deregistration request message. That is, the NAN proxy client 1130 may transmit a message for proxy deregistration to the NAN proxy server 1120 based on the called method.
- the TLV field of the follow-up proxy deregistration request message may be as shown in Table 14 below. That is, the follow-up proxy deregistration request message may include registration ID information and MAC address information about the NAN proxy server. Through this, the NAN proxy server can identify the registered NAN proxy client and can proceed with the proxy deregistration procedure.
- the NAN proxy client 1130 may then receive a follow-up message from the NAN proxy server 1120.
- the follow-up message may be a follow-up proxy deregistration response message. That is, the NAN proxy client 1130 may receive a message for proxy deregistration from the NAN proxy server 1120 in response to the proxy registration request.
- the TLV field of the follow-up proxy deregistration response message may be as shown in Table 15 below. That is, the follow-up proxy deregistration response message may include registration ID information and status indication indicating whether deregistration is accepted.
- the NAN DE and NAN MAC stages of the NAN proxy client 1130 may provide a Follow-up Receive event to the service / application stage.
- the Follow-up Receive may be as shown in Table 16 below.
- the NAN proxy client 1130 may omit the follow-up Receive event and complete the proxy deregistration procedure.
- the NAN proxy server 1120 may release the proxy server by itself.
- the NAN proxy server 1120 may transmit a proxy deregistration notification to the registered NAN proxy client 1130.
- the deregistration notification may be transmitted in unicast or broadcast, and is not limited to the above-described embodiment. That is, when the NAN proxy server 1120 releases the role of the proxy server, a message informing of this may be transmitted to the NAN proxy client 1130.
- the TLV field of the deregistration notification may be as shown in Table 17 below.
- the TLV field of the registration release notification may include registered ID information.
- the NAN proxy client 1130 may identify the NAN proxy server 1120 that is released and may proceed with the proxy release procedure.
- the NAN proxy client 1130 may request update information on the proxy service from the NAN proxy server 1120.
- the NAN proxy client may determine that the NAN proxy server 1120 no longer exists even though the NAN proxy client does not receive the proxy release notification.
- N may be a preset number and may be a changeable number.
- N update requests may be vendor specific.
- N update requests may be set differently according to a service, and are not limited to the above-described embodiment.
- FIG. 12 is a diagram illustrating a discovery window period for a NAN proxy server and a NAN proxy client.
- the NAN proxy server may support a mechanism for data transmission or power consumption of the NAN terminals.
- two NAN terminals which do not communicate with each other due to a distance problem may perform communication using a NAN proxy server.
- the NAN proxy client may not awake every discovery window, thereby reducing power consumption.
- the NAN terminal may transmit a subscription message to the NAN proxy server to perform service discovery of the NAN proxy server.
- the NAN terminal in order for the NAN terminal to transmit a subscription message to the NAN proxy server, it is necessary to distinguish the NAN proxy server. That is, the NAN terminal needs to confirm the existence of the NAN proxy server.
- the NAN proxy server may publish the service discovery frame by broadcasting to inform that it is the NAN proxy server.
- the publication may be a solicited type or an unsolicited type, and is not limited to the above-described embodiment.
- the NAN proxy server may add a proxy server attribute in the NAN beacon or service discovery frame to inform that the NAN proxy server has the capability of the proxy server.
- the NAN terminal receiving the NAN beacon or the service discovery frame including the proxy server property, the terminal supporting the proxy client function may determine the existence of the neighboring proxy server by analyzing the corresponding property.
- Table 18 may indicate NAN attribute information that may be included in a beacon frame and a service discovery frame.
- the Attribute ID field may be defined with different values to represent different attributes.
- each attribute information may or may not be included in the beacon frame and the service discovery frame.
- specific attribute information of each attribute information may be included as essential (indicated by "M” in the table) or may be displayed as optional (indicated by "O" in the table).
- a proxy server attribute and a proxy client attribute may be defined in the reserved bits of the field for the NAN attribute information.
- the proxy server attribute field may be selectively included in at least one of a NAN synchronization beacon frame, a NAN discovery beacon frame, and a NAN service discovery frame. That is, the proxy server attribute field may be selectively included in each frame as a field defined by the NAN proxy server to inform its existence.
- the proxy client attribute field may be selectively included in the service discovery frame. That is, the proxy client attribute field may be information transmitted based on whether the NAN terminal confirms the existence of the NAN proxy server and whether the NAN terminal can be a NAN proxy client. Therefore, the proxy client attribute field may be transmitted in the NAN service discovery window without being transmitted in the NAN beacon frame.
- the proxy server property field may be configured as shown in Table 19 below.
- the proxy server attribute field may include a Proxy Server Address field including address information of the NAN interface of the proxy server.
- the Proxy Server Capability field may be included as information on the capability of the NAN proxy server.
- the function of the NAN proxy server may be included in the form of a bitmap.
- an awake interval of the NAN proxy server may be represented by an integer value.
- the integer value indicates a discovery window period during which the NAN proxy server awakes. That is, when the integer value is 1, the NAN proxy server may be awakened in every discovery window interval.
- the NAN proxy server may serve as a substitute for the NAN proxy client, and may be awakened every discovery window.
- an integer value may be changed and is not limited to the above-described embodiment.
- the BSSID field may be included as the AP STA.
- the bitmap for the aforementioned proxy server capability field may be represented as shown in Table 20 below.
- the Publish Proxy bit in the Proxy Server Capability Bitmap may indicate whether a NAN proxy server receives a publish request of a neighboring NAN terminal and transmits a proxied service.
- the Subscribe Proxy bit may indicate whether the NAN proxy server can receive a subscription request of a neighboring NAN terminal to find a neighboring service and inform the NAN terminal of the found service.
- the follow-up proxy bit indicates whether or not a function for proxying the follow-up service discovery window of neighboring NAN terminals is possible.
- the Invite Proxy bit indicates whether a function capable of requesting the neighbor NAN terminals to participate in the BSS of the AP STA of the NAN proxy server is possible.
- the NAN Data Path may indicate whether the NAN proxy server supports the NAN data path function.
- the NAN Data Forwarding bit indicates whether the NAN proxy server receives the NAN data path of the NAN terminal and transmits the NAN data path to the neighboring NAN terminals. That is, the proxy server capability field may indicate information about a function that the NAN proxy server can perform, and is not limited to the above-described embodiment.
- the proxy client attribute may be included in a service discovery frame that the NAN proxy client sends to the NAN proxy server.
- the proxy client attribute may include a Proxy Client Address indicating a NAN interface address of the NAN proxy client.
- the proxy client attribute may include a Proxy Server Address indicating the NAN interface address of the NAN proxy server.
- the proxy client property may include an Awake Interval indicating an awake period of the discovery window. In this case, the Awake Interval may indicate, in discovery interval units, a cycle in which the NAN client awakes after the NAN proxy client publishes, subscribes, or follows a follow-up request to the NAN proxy server.
- a NAN proxy client may request a publication and set an Awake Interval of the proxy client property to 3.
- the NAN proxy client may be awakened every three discovery windows after being registered with the NAN proxy server. That is, the NAN proxy client can be awakened in the first discovery window, the fourth discovery window, and the seventh discovery window. It can also be awakened at the same period.
- the NAN proxy client may send a subscription message to the NAN proxy server as described above.
- the NAN proxy client may transmit a follow-up to the NAN proxy server to form a role between the NAN proxy server and the NAN proxy client.
- the NAN proxy client can publish to the NAN proxy server to inform what service it is.
- the awake interval of the discovery window may be determined according to the feature or definition of the NAN proxy client.
- the proxy server address and the DW awake interval may be defined in addition to the existing publication. This allows the NAN proxy client to assume its publishing role to the NAN proxy server. In other words, the NAN proxy client awakes only in a discovery window of a specific period, thereby reducing power consumption by synchronizing with the NAN proxy server.
- the NAN proxy server may always be awake in multiples of the awake interval of the NAN proxy client.
- the NAN proxy client can be awakened only in a discovery window of a certain period based on the Awake Interval.
- the NAN proxy server may always be awake in the discovery window in which the NAN proxy client is awake to perform data exchange with the NAN proxy client. Through this, the NAN proxy client can perform data communication with other terminals while reducing power consumption by using the NAN proxy server.
- FIG. 13 is a diagram illustrating a method in which a NAN proxy server supports a NAN terminal.
- the NAN proxy server may support not only a NAN proxy client but also other NAN terminals.
- the NAN proxy server may publish AP capability information and WLAN attribute information in a service discovery frame.
- the NAN proxy client may perform registration after NAN proxy server discovery.
- the NAN proxy server can then be set up to perform publishing on behalf of the NAN proxy client.
- the NAN proxy server may publish data on behalf of the NAN proxy client to perform data communication with other NAN terminals.
- the NAN proxy server may transmit a service discovery frame including invitation information to the two NAN terminals.
- the invitation information may be information for participating in a data path using a WLAN infrastructure belonging to a BSS of the NAN proxy server.
- the first NAN terminal 1210 and the second NAN terminal 1220 may be NAN proxy clients registered in the NAN proxy server 1240, respectively.
- the NAN proxy server 1240 may support the function of the AP STA.
- the NAN proxy server 1240 informs the first NAN terminal 1210 and the second NAN terminal 1220 of the AP of the AP and communicates data through the AP. Can be done. That is, in the case of supporting the AP as the NAN proxy server 1240, the NAN terminals may support data communication using the WLAN infrastructure.
- FIG. 14 is a diagram illustrating a method of managing NAN proxy clients registered to a plurality of NAN proxy servers.
- the NAN proxy client may be registered with the NAN proxy server.
- the NAN proxy server may publish and / or subscribe on behalf of the NAN proxy client.
- the NAN proxy client awakes only in a discovery window of a certain period to receive information from the NAN proxy server, thereby reducing power consumption.
- the NAN proxy servers 1410, 1420, and 1430 may each include a NAN proxy client. At this time, there may be one or more NAN proxy clients registered in the NAN proxy server. Also, as an example, the number of NAN proxy clients registered in the NAN proxy server may be limited, but is not limited to the above-described embodiment. In this case, as an example, each of the NAN proxy servers 1410, 1420, and 1430 may be adjacent to each other, and service discovery frames may be exchanged with each other. That is, there may be a plurality of NAN proxy servers 1410, 1420, and 1430 including registered NAN proxy clients, which is not limited to the above-described embodiment.
- the NAN proxy client may perform a deregistration procedure by transmitting a message for deregistration to the NAN proxy server in order to deregister the NAN proxy server.
- registration of the NAN proxy client may be released by the NAN proxy server.
- the NAN proxy server stops the role of the proxy server or leaves the role as the NAN proxy server may be considered.
- the NAN proxy server may be turned off to perform a role of the NAN proxy server.
- the NAN proxy client is registered in the NAN proxy server, and thus may not perform smooth data communication. Therefore, there is a need to consider maintaining and updating the proxy for smooth data communication of the NAN proxy client.
- the NAN proxy server may provide information on the role termination to the NAN proxy client.
- the NAN proxy server may provide information to the NAN proxy clients by broadcasting the information indicating that the NAN proxy server stops serving in the service discovery frame.
- the NAN proxy client may be awakened only in a discovery window of a certain period.
- each proxy client can be awakened in a discovery window of a different period. Therefore, the NAN proxy client may not receive information about the role interruption broadcast by the NAN proxy server.
- the NAN proxy server may transmit information about the interruption of the NAN proxy server to the NAN proxy server in the neighbor.
- a NAN proxy server (hereinafter, referred to as an old NAN proxy server) that stops a NAN proxy server role may provide neighbor NAN proxy servers (hereinafter, referred to as a new NAN proxy server) with its own NAN proxy client list information.
- the Old NAN proxy server may improve discovery window period information for each NAN proxy clients.
- the New NAN proxy server may provide NAN proxy clients with information that the NAN proxy server has been changed in place of the Old NAN proxy server.
- the case where the NAN proxy server is suddenly turned off may be considered.
- the NAN proxy client may operate without receiving information that the NAN proxy server does not operate. Therefore, the NAN proxy client may confirm that the NAN proxy server does not operate based on the update period. That is, the NAN proxy client may check that the NAN proxy server does not operate when the NAN proxy client attempts to synchronize with the NAN proxy server in the discovery window where it is awakened. In this case, as an example, the NAN proxy client may check that the NAN proxy server does not operate when synchronization fails in N discovery windows.
- N may be a changeable number and is not limited to the above-described embodiment.
- the NAN proxy client may perform a procedure for re-registering with another NAN proxy server. That is, a new NAN proxy server can be searched for and registered.
- the NAN proxy client that has confirmed that the operation of the NAN proxy server is stopped first among the plurality of NAN proxy clients registered in the NAN proxy server may provide the stop information to other NAN proxy clients. That is, the NAN proxy client can provide the interruption information to other NAN proxy clients registered with the same NAN proxy server.
- the stop information may be broadcast and transmitted.
- the interruption information may be transmitted based on a registration ID for an existing NAN proxy server. That is, the first NAN proxy client that obtains the interrupt information may provide the interrupt information to other NAN proxy clients. This allows other NAN proxy clients to obtain interruption information without delay.
- the NAN proxy client that first determines that the operation of the NAN proxy server is stopped may provide the stop information to another nearby NAN proxy server.
- the NAN proxy client may provide stop information to another NAN proxy server based on the registered ID information. If the NAN proxy client includes information about NAN proxy clients registered with the NAN proxy server, the NAN proxy client may provide the information to another NAN proxy server. At this time, the NAN proxy server receiving the interruption information may act as a new NAN proxy server on behalf of the existing NAN proxy server.
- the NAN proxy server may receive information about the NAN proxy clients.
- NAN proxy clients registered with a NAN proxy server may have different discovery window periods.
- the NAN proxy client may receive a service discovery frame transmitted by the NAN proxy server.
- the NAN proxy client may obtain information about the publishing and / or subscription performed by the NAN proxy server instead.
- the NAN proxy client may transmit a message (hereinafter, keep alive message) indicating to the NAN proxy server that the NAN proxy client is maintained as a NAN proxy client.
- the NAN proxy server may update list information on registered NAN proxy clients based on the received keep alive message.
- the keep alive message may be one example, and when the NAN proxy server receives a message indicating that the NAN proxy client is maintained as the NAN proxy client, the NAN proxy server may update list information on registered NAN proxy clients. That is, the message is not limited to the Keep Alive message, and similar messages or newly defined messages may be possible, but are not limited to the above-described embodiment.
- the NAN proxy server may determine whether to maintain registration or update the list according to whether the NAN proxy clients receive the Keep alive message.
- the NAN proxy server or the NAN proxy client may want to cancel registration, respectively.
- the NAN proxy server may transmit information on deregistration to registered NAN proxy clients.
- the NAN proxy client does not receive any message from the NAN proxy server during a discovery window of a certain period, it may be determined that the NAN proxy server is unavailable, as described above.
- the NAN proxy client when the NAN proxy client intends to deregister, the NAN proxy client may transmit information on deregistration to the NAN proxy server. In this case, as an example, when the NAN proxy client is switched to awake in every discovery window, the NAN proxy server is unnecessary and may perform deregistration.
- the NAN proxy client may request deregistration of the NAN proxy server when it wants to register with another NAN proxy server.
- the NAN proxy client when the NAN proxy client is turned off by itself, it may request deregistration from the NAN proxy server.
- the NAN proxy server and the NAN proxy client may perform deregistration according to predetermined conditions, respectively.
- 15 is a flowchart illustrating a method of performing a proxy role.
- the NAN terminal may transmit a subscription message to the NAN proxy server to search for a service for the NAN proxy server to the NAN proxy server (S1510).
- the application end may call the subscribe method to provide information about the proxy service to the NAN DE and the NAN MAC.
- the NAN terminal may receive a publish message from the NAN proxy server (S1520).
- the NAN proxy server may include information on a proxy service included in a subscription message. Based on the determination, it may be determined whether the proxy service is supported through service matching.
- the NAN proxy server may transmit a publish message to the NAN terminal after service matching.
- the NAN DE and NAN MAC terminals of the NAN terminal may provide a discovery result to a service / application terminal of the NAN terminal.
- the NAN terminal may complete a service search for the NAN proxy server.
- the NAN terminal may transmit a proxy registration request message to the NAN proxy server (S1530).
- the proxy registration request message may include a proxy registration request TLV field.
- the proxy registration request message may include information about a discovery window awake period for the NAN terminal and information about proxy registration.
- the NAN terminal may receive a proxy registration response message based on the proxy registration request message (S1540).
- the NAN terminal receives the NAN. It can be registered with a proxy server. In other words, it can be a NAN proxy client. In this case, the NAN proxy client may be awake based on a predetermined discovery window period.
- the NAN proxy server may publish and / or subscribe on behalf of the NAN proxy client.
- the NAN proxy server may perform a procedure for performing data communication with another NAN terminal on behalf of the NAN proxy client.
- the NAN proxy server and the NAN proxy client may exchange data in a discovery window in which the NAN proxy client is awake, as described above.
- 16 is a block diagram of a terminal device.
- the terminal device may be a NAN terminal.
- the NAN terminal may be a terminal serving as a NAN proxy server.
- the NAN terminal may be a terminal serving as a NAN proxy client, as described above.
- 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.
- the terminal 100 may communicate with an external device by using the transmitting module 110 and the receiving module 130.
- the external device may be another terminal device.
- 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.
- the terminal device 100 may exchange a beacon frame, a service discovery frame, etc. using the transmitting module 110 and the receiving module 130, but is not limited to the above-described embodiment. That is, the terminal device 100 may exchange information with an external device by performing communication by using the transmitting module 110 and the receiving module 130.
- the terminal device 100 may transmit a subscription message for proxy service search to the NAN proxy server using the transmission module 110. Thereafter, the processor 120 may receive the publish message from the NAN proxy server using the reception module 130. In this case, the publish message may be a message indicating that the proxy service is supported by the NAN proxy server. Thereafter, the processor 120 may transmit the proxy registration request message to the NAN proxy server based on the proxy service using the transmission module 110. Thereafter, the processor 120 may receive the proxy registration response message by using the reception module 130. In this case, when the proxy registration response message is received, the NAN proxy client may be registered with the NAN proxy server. In this case, the registered NAN proxy client may be awake based on the first discovery window period, thereby reducing power consumption.
- Embodiments of the present invention described above may be implemented through various means.
- embodiments of the present invention may be implemented by hardware, firmware, software, or a combination thereof.
- 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.
- ASICs Application Specific Integrated Circuits
- DSPs Digital Signal Processors
- DSPDs Digital Signal Processing Devices
- PLDs Programmable Logic Devices
- FPGAs field programmable gate arrays
- processors controllers, microcontrollers, microprocessors, and the like.
- 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 present invention as described above has been described assuming that it is applied to the NAN wireless communication system, but need not be limited thereto.
- the present invention can be applied to various wireless systems in the same manner.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (15)
- 무선통신시스템에서 NAN(Neighbor Awareness Networking) 프록시 클라이언트(Proxy Client)가 NAN 프록시 서버에 등록을 수행하는 방법에 있어서,프록시 서비스 검색에 대한 서브스크라이브 메시지를 상기 NAN 프록시 서버로 전송하는 단계;퍼블리시 메시지를 상기 NAN 프록시 서버로부터 수신하는 단계;로서,상기 퍼블리시 메시지는 상기 프록시 서비스가 상기 NAN 프록시 서버에 의해 지원됨을 나타내는 메시지이고,상기 프록시 서비스에 기초하여 프록시 등록 요청 메시지를 상기 NAN 프록시 서버로 전송하는 단계; 및상기 프록시 등록 요청 메시지에 기초하여 프록시 등록 응답 메시지를 수신하는 단계;를 포함하되,상기 프록시 등록 응답 메시지가 수신되면 상기 NAN 프록시 클라이언트는 상기 NAN 프록시 서버에 등록되고,상기 등록된 NAN 프록시 클라이언트는 제 1 디스커버리 윈도우 주기에 기초하여 어웨이크되는, NAN 프록시 서버 등록 방법.
- 제 1 항에 있어서,상기 제 1 디스커버리 윈도우 주기에 대한 정보는 상기 프록시 등록 요청 메시지에 포함되어 상기 NAN 프록시 서버로 전송되는, NAN 프록시 서버 등록 방법.
- 제2 항에 있어서,상기 NAN 프록시 서버는 제 2 디스커버리 윈도우 주기에 기초하여 어웨이크되되,상기 제 1 디스커버리 윈도우 주기는 상기 제 2 디스커버리 윈도우 주기의 정수배 로 설정되거나, Vender specific하게 정해지는 특정 변수인, NAN 프록시 서버 등록 방법.
- 제 1 항에 있어서,상기 프록시 등록 응답 메시지에는 등록이 허여되는지 여부를 지시하는 정보 및 등록 아이디 정보 중 적어도 어느 하나 이상이 포함되는, NAN 프록시 서버 등록 방법.
- 제 1 항에 있어서,상기 NAN 프록시 클라이언트에 대한 등록이 완료되면, 상기 NAN 프록시 서버가 상기 NAN 프록시 클라이언트의 퍼블리시 및 서브스크라이브 기능을 대신 수행하는, NAN 프록시 서버 등록 방법.
- 제 1 항에 있어서,상기 NAN 프록시 서버에 등록된 상기 NAN 프록시 클라이언트가 등록 해제 절차를 수행하는 단계;를 더 포함하는, NAN 프록시 서버 등록 방법.
- 제 6 항에 있어서,상기 등록 해제 절차는,상기 NAN 프록시 서버로 등록 해제 요청 메시지를 송신하는 단계; 및상기 NAN 프록시 서버로부터 등록 해제 응답 메시지를 수신하는 단계;를 포함하는, NAN 프록시 서버 등록 방법.
- 제 1 항에 있어서,상기 NAN 프록시 서버가 이용 불가능 상태가 되는 경우, 상기 NAN 프록시 클라이언트는 상기 NAN 프록시 서버에서 등록을 해제하고, 상기 등록 해제에 대한 정보를 상기 NAN 프록시 서버에 등록된 다른 NAN 프록시 클라이언트들에게 제공하는, NAN 프록시 서버 등록 방법.
- 제 1 항에 있어서,상기 NAN 프록시 서버로부터 상기 프록시 서버 능력에 대한 정보를 포함하는 제 1 프레임을 수신하는 단계;를 더 포함하는, NAN 프록시 서버 등록 방법.
- 제 9 항에 있어서,상기 제 1 프레임은 NAN 비콘 프레임 및 NAN 서비스 디스커버리 프레임 중 어느 하나인, NAN 프록시 서버 등록 방법.
- 제 9 항에 있어서,상기 제 1 프레임에는 NAN 프록시 서버 속성 필드가 포함되고,NAN 프록시 서버 속성 필드에는 프록시 서버 주소 필드, 프록시 서버 능력 필드, 어웨이크 인터벌 필드 및 BSSID 필드 중 적어도 어느 하나 이상이 포함되는, NAN 프록시 서버 등록 방법.
- 제 9 항에 있어서,상기 제 1 프레임을 수신하면 프록시 클라이언트 능력 정보를 포함하는 제 2 프레임을 상기 NAN 프록시 서버로 전송하는 단계;를 더 포함하되,상기 제 2 프레임에는 NAN 프록시 클라이언트 속성 필드가 포함되고,NAN 프록시 서버 속성 필드에는 프록시 클라이언트 주소 필드, 프록시 서버 주소 필드, 어웨이크 인터벌 필드 및 BSSID 필드 중 적어도 어느 하나 이상이 포함되는, NAN 프록시 서버 등록 방법.
- 제 1 항에 있어서,상기 등록된 NAN 프록시 클라이언트는 제 1 디스커버리 윈도우 주기에 기초하여 어웨이크되는 디스커버리 윈도우에서 상기 NAN 프록시 서버로부터 제 1 프레임을 수신하고,제 1 프레임에 기초하여 상기 NAN 프록시 서버와 동기화를 수행하는, NAN 프록시 서버 등록 방법.
- 제 13 항에 있어서,상기 제 1 프레임에 기초하여 상기 NAN 프록시 서버로 제 2 프레임을 전송하되,상기 제 2 프레임은 상기 NAN 프록시 클라이언트의 등록이 유지되고 있음을 나타내는 정보를 포함하는, NAN 프록시 서버 등록 방법.
- 무선통신시스템에서 NAN 프록시 서버에 등록을 수행하는 NAN 프록시 클라이언트에 있어서,외부 디바이스로부터 인포메이션을 수신하는 수신 모듈;외부 디바이스로 인포메이션을 송신하는 송신 모듈; 및상기 수신 모듈 및 상기 송신 모듈을 제어하는 프로세서;로서,상기 프로세서는,프록시 서비스 검색에 대한 서브스크라이브 메시지를 상기 NAN 프록시 서버로 전송하고,퍼블리시 메시지를 상기 NAN 프록시 서버로부터 수신하되,상기 퍼블리시 메시지는 상기 프록시 서비스가 상기 NAN 프록시 서버에 의해 지원됨을 나타내는 메시지이고,상기 프록시 서비스에 기초하여 프록시 등록 요청 메시지를 상기 NAN 프록시 서버로 전송하고,상기 프록시 등록 요청 메시지에 기초하여 프록시 등록 응답 메시지를 수신하되,상기 프록시 등록 응답 메시지가 수신되면 상기 NAN 프록시 클라이언트는 상기 NAN 프록시 서버에 등록되고,상기 등록된 NAN 프록시 클라이언트는 제 1 디스커버리 윈도우 주기에 기초하여 어웨이크되는, NAN 프록시 서버에 등록을 수행하는 NAN 프록시 클라이언트.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2017555558A JP6744328B2 (ja) | 2015-04-23 | 2016-04-25 | 無線通信システムにおいてnanプロキシサーバーに登録する方法及び装置 |
US15/567,027 US10091640B2 (en) | 2015-04-23 | 2016-04-25 | Method and apparatus for performing registration to NAN proxy server in wireless communication system |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201562151946P | 2015-04-23 | 2015-04-23 | |
US62/151,946 | 2015-04-23 | ||
US201562183200P | 2015-06-23 | 2015-06-23 | |
US62/183,200 | 2015-06-23 | ||
US201562193571P | 2015-07-16 | 2015-07-16 | |
US62/193,571 | 2015-07-16 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016171527A1 true WO2016171527A1 (ko) | 2016-10-27 |
Family
ID=57144602
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2016/004290 WO2016171527A1 (ko) | 2015-04-23 | 2016-04-25 | 무선 통신 시스템에서 nan 프록시 서버에 등록을 수행하는 방법 및 장치 |
Country Status (3)
Country | Link |
---|---|
US (1) | US10091640B2 (ko) |
JP (1) | JP6744328B2 (ko) |
WO (1) | WO2016171527A1 (ko) |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180352413A1 (en) * | 2017-06-01 | 2018-12-06 | Samsung Electronics Co., Ltd. | Method and apparatus for inter-cluster data transmission and reception |
KR20180131965A (ko) * | 2017-06-01 | 2018-12-11 | 삼성전자주식회사 | 클러스터 간의 데이터 송수신 방법 및 장치 |
WO2019044162A1 (ja) * | 2017-08-31 | 2019-03-07 | キヤノン株式会社 | 通信装置、その制御方法、およびプログラム |
WO2019073796A1 (ja) * | 2017-10-13 | 2019-04-18 | キヤノン株式会社 | 通信装置、通信方法、及びプログラム |
CN112956248A (zh) * | 2018-11-07 | 2021-06-11 | 三星电子株式会社 | 用于无线网络中邻近设备之间的通信的装置和方法 |
CN113596157A (zh) * | 2021-07-30 | 2021-11-02 | 绿漫科技有限公司 | 一种基于SpringCloud的联盟链无感发布方法 |
US11323519B2 (en) | 2017-04-19 | 2022-05-03 | Microsoft Technology Licensing, Llc | Internet of things pub-sub data publisher |
WO2023113351A1 (ko) * | 2021-12-13 | 2023-06-22 | 삼성전자 주식회사 | Nan 통신을 수행하는 전자 장치 및 전자 장치의 동작 방법 |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10091713B2 (en) * | 2015-01-27 | 2018-10-02 | Qualcomm Incorporated | Numerology and frames for networks in the sub-1GHz (S1G) band |
US10356595B2 (en) * | 2015-06-05 | 2019-07-16 | Lg Electronics Inc. | Method and device for nan terminal transitioning state in wireless communication system |
JP6655913B2 (ja) * | 2015-09-02 | 2020-03-04 | キヤノン株式会社 | 通信装置、制御方法及びプログラム |
JP2018046450A (ja) * | 2016-09-15 | 2018-03-22 | キヤノン株式会社 | 通信装置、通信方法、及びプログラム |
US11147126B2 (en) | 2018-05-15 | 2021-10-12 | Apple Inc. | Neighbor awareness networking discovery window congestion mitigation |
JP2024050054A (ja) * | 2022-09-29 | 2024-04-10 | パナソニックホールディングス株式会社 | 通信装置、通信制御方法及び通信システム |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20100127812A (ko) * | 2008-03-03 | 2010-12-06 | 콸콤 인코포레이티드 | 무선 클라이언트 단말들에서 전력 보존을 용이하게 하기 위한 프록시 서버 |
US20130227152A1 (en) * | 2010-11-03 | 2013-08-29 | Lg Electronics Inc. | Method for searching for device and communication device using same |
WO2014089252A1 (en) * | 2012-12-05 | 2014-06-12 | Intel Corporation | Methods and arrangements for time synchronization and service discovery |
US20150036540A1 (en) * | 2013-08-05 | 2015-02-05 | Nokia Corporation | Method, apparatus, and computer program product for hop count usage in cluster selection |
US20150081840A1 (en) * | 2013-09-13 | 2015-03-19 | Qualcomm Incorporated | System and method for multihop service discovery with member station proxy service advertisements |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106171015A (zh) * | 2014-08-13 | 2016-11-30 | 联发科技股份有限公司 | 无线通信网络中具有低功耗的服务发现 |
US10200826B2 (en) * | 2015-01-30 | 2019-02-05 | Intel Corporation | Neighbor aware networking (NAN) device and method for service discovery |
US10433353B2 (en) * | 2015-03-09 | 2019-10-01 | Apple Inc. | Neighbor awareness networking service discovery proxy |
US20160285630A1 (en) * | 2015-03-23 | 2016-09-29 | Qualcomm Incorporated | Private service identifiers in neighborhood aware networks |
US9693217B2 (en) * | 2015-05-26 | 2017-06-27 | Nokia Technologies Oy | Method, apparatus, and computer program product for service discovery proxy for wireless communication |
US20160352842A1 (en) * | 2015-05-27 | 2016-12-01 | Qualcomm Incorporated | Proxy advertisements in a neighbor aware network |
US20160352782A1 (en) * | 2015-05-27 | 2016-12-01 | Qualcomm Incorporated | Proxy advertisements in a neighbor aware network |
JP6579883B2 (ja) * | 2015-09-24 | 2019-09-25 | キヤノン株式会社 | 通信装置、制御方法、及びプログラム |
US10736022B2 (en) * | 2015-11-02 | 2020-08-04 | Apple Inc. | Proxy assisted NAN and access point concurrent operation |
-
2016
- 2016-04-25 WO PCT/KR2016/004290 patent/WO2016171527A1/ko active Application Filing
- 2016-04-25 JP JP2017555558A patent/JP6744328B2/ja active Active
- 2016-04-25 US US15/567,027 patent/US10091640B2/en active Active
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20100127812A (ko) * | 2008-03-03 | 2010-12-06 | 콸콤 인코포레이티드 | 무선 클라이언트 단말들에서 전력 보존을 용이하게 하기 위한 프록시 서버 |
US20130227152A1 (en) * | 2010-11-03 | 2013-08-29 | Lg Electronics Inc. | Method for searching for device and communication device using same |
WO2014089252A1 (en) * | 2012-12-05 | 2014-06-12 | Intel Corporation | Methods and arrangements for time synchronization and service discovery |
US20150036540A1 (en) * | 2013-08-05 | 2015-02-05 | Nokia Corporation | Method, apparatus, and computer program product for hop count usage in cluster selection |
US20150081840A1 (en) * | 2013-09-13 | 2015-03-19 | Qualcomm Incorporated | System and method for multihop service discovery with member station proxy service advertisements |
Cited By (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11323519B2 (en) | 2017-04-19 | 2022-05-03 | Microsoft Technology Licensing, Llc | Internet of things pub-sub data publisher |
EP3616441A4 (en) * | 2017-06-01 | 2020-04-15 | Samsung Electronics Co., Ltd. | METHOD AND DEVICE FOR DATA TRANSMISSION AND RECEPTION BETWEEN CLUSTERS |
WO2018221961A1 (en) | 2017-06-01 | 2018-12-06 | Samsung Electronics Co., Ltd. | Method and apparatus for inter-cluster data transmission and reception |
KR20180131965A (ko) * | 2017-06-01 | 2018-12-11 | 삼성전자주식회사 | 클러스터 간의 데이터 송수신 방법 및 장치 |
KR102502806B1 (ko) * | 2017-06-01 | 2023-02-23 | 삼성전자주식회사 | 클러스터 간의 데이터 송수신 방법 및 장치 |
US20180352413A1 (en) * | 2017-06-01 | 2018-12-06 | Samsung Electronics Co., Ltd. | Method and apparatus for inter-cluster data transmission and reception |
US10924911B2 (en) | 2017-06-01 | 2021-02-16 | Samsung Electronics Co., Ltd | Method and apparatus for inter-cluster data transmission and reception |
JP2019047289A (ja) * | 2017-08-31 | 2019-03-22 | キヤノン株式会社 | 通信装置、その制御方法、およびプログラム |
US11350346B2 (en) | 2017-08-31 | 2022-05-31 | Canon Kabushiki Kaisha | Communication apparatus, control method therefor, and non-transitory computer-readable storage medium |
WO2019044162A1 (ja) * | 2017-08-31 | 2019-03-07 | キヤノン株式会社 | 通信装置、その制御方法、およびプログラム |
JP2019075657A (ja) * | 2017-10-13 | 2019-05-16 | キヤノン株式会社 | 通信装置、通信方法、及びプログラム |
WO2019073796A1 (ja) * | 2017-10-13 | 2019-04-18 | キヤノン株式会社 | 通信装置、通信方法、及びプログラム |
JP7118617B2 (ja) | 2017-10-13 | 2022-08-16 | キヤノン株式会社 | 通信装置、通信方法、及びプログラム |
CN112956248A (zh) * | 2018-11-07 | 2021-06-11 | 三星电子株式会社 | 用于无线网络中邻近设备之间的通信的装置和方法 |
CN113596157A (zh) * | 2021-07-30 | 2021-11-02 | 绿漫科技有限公司 | 一种基于SpringCloud的联盟链无感发布方法 |
WO2023113351A1 (ko) * | 2021-12-13 | 2023-06-22 | 삼성전자 주식회사 | Nan 통신을 수행하는 전자 장치 및 전자 장치의 동작 방법 |
Also Published As
Publication number | Publication date |
---|---|
US20180098211A1 (en) | 2018-04-05 |
JP6744328B2 (ja) | 2020-08-19 |
US10091640B2 (en) | 2018-10-02 |
JP2018518095A (ja) | 2018-07-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2016171527A1 (ko) | 무선 통신 시스템에서 nan 프록시 서버에 등록을 수행하는 방법 및 장치 | |
WO2016190721A1 (ko) | 무선 통신 시스템에서 nan 프록시 서버를 통해 프록시 서비스를 제공하는 방법 및 그 장치 | |
WO2016204497A1 (ko) | 무선 통신 시스템에서 nan 프록시 서버가 릴레이 디바이스 역할을 수행하는 방법 및 장치 | |
WO2016137224A1 (ko) | 무선 통신 시스템에서 데이터를 전송하는 방법 및 장치 | |
WO2015152657A1 (ko) | 무선 통신 시스템에서 nan 단말의 신호 송수신 방법 및 장치 | |
WO2016195448A1 (ko) | 무선 통신 시스템에서 nan 단말의 상태 천이 방법 및 장치 | |
WO2015034195A1 (ko) | 멀티 rat 환경에서 위치 갱신 (location area update) 방법 및 페이징을 송수신하는 방법 | |
WO2017146461A1 (ko) | 페이징 기법에 따른 이웃 인식 네트워크를 위한 방법 및 이를 이용한 무선 단말 | |
WO2016167618A1 (ko) | 무선 통신 시스템에서 서비스 디스커버리를 수행하는 방법 및 장치 | |
WO2014142526A1 (ko) | 무선 통신 방법 및 장치 | |
WO2016148406A1 (ko) | 무선 통신 시스템에서 어플리케이션 서비스 플랫폼을 이용하여 서비스를 지원하는 방법 및 장치 | |
WO2017018823A1 (ko) | 무선 통신 시스템에서 어플리케이션 서비스 플랫폼 세션 형성 방법 및 장치 | |
WO2016148523A1 (ko) | 무선 통신 시스템에서 서비스 디스커버리를 수행하는 방법 및 장치 | |
WO2016140466A1 (ko) | 무선랜 시스템에서 페이징 수행 방법 및 이를 이용한 기기 | |
WO2017105154A1 (ko) | 무선 통신 시스템에서 nan 단말이 레인징 오퍼레이션을 수행하는 방법 및 장치 | |
WO2016144088A1 (ko) | 무선 통신 시스템에서 멀티 채널을 이용하여 데이터를 전송하는 방법 및 장치 | |
WO2014030894A1 (ko) | 무선랜 시스템에서 고속 링크 셋업 방법 및 이를 위한 장치 | |
WO2017057988A1 (ko) | 무선 통신 시스템에서 nan 단말이 nan 클러스터로 머징하는 방법 및 장치 | |
WO2017010843A1 (ko) | 무선 통신 시스템에서 프록시 서비스에 대한 프레임을 교환하는 방법 및 장치 | |
WO2019177231A1 (ko) | 무선랜 시스템에서 타겟 액세스 포인트에 대한 정보를 전달하기 위한 방법 및 이를 이용한 액세스 포인트 | |
WO2013122395A1 (ko) | 무선랜 시스템에서 고속 링크 셋업 방법 및 장치 | |
WO2016190618A1 (ko) | 무선 통신 시스템에서 세션 핸드오버를 수행하는 방법 및 장치 | |
WO2016137097A1 (ko) | Nan 장치 간의 데이터 통신 방법 및 데이터 통신을 수행하는 nan 장치 | |
WO2017010731A1 (ko) | 무선 통신 시스템에서 프록시 서비스를 업데이트하는 방법 및 그 장치 | |
WO2017065561A1 (ko) | 무선 통신 시스템에서 nan 단말이 프레임을 전송하는 방법 및 장치 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16783459 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 15567027 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2017555558 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 16783459 Country of ref document: EP Kind code of ref document: A1 |