WO2017057988A1 - Procédé de fusionnement d'un terminal de nan dans une grappe de nan dans un système de communication sans fil, et dispositif - Google Patents

Procédé de fusionnement d'un terminal de nan dans une grappe de nan dans un système de communication sans fil, et dispositif Download PDF

Info

Publication number
WO2017057988A1
WO2017057988A1 PCT/KR2016/011054 KR2016011054W WO2017057988A1 WO 2017057988 A1 WO2017057988 A1 WO 2017057988A1 KR 2016011054 W KR2016011054 W KR 2016011054W WO 2017057988 A1 WO2017057988 A1 WO 2017057988A1
Authority
WO
WIPO (PCT)
Prior art keywords
nan
cluster
terminal
data
beacon frame
Prior art date
Application number
PCT/KR2016/011054
Other languages
English (en)
Korean (ko)
Inventor
김동철
박기원
이병주
조영준
임태성
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Publication of WO2017057988A1 publication Critical patent/WO2017057988A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/32—Connectivity information management, e.g. connectivity discovery or connectivity update for defining a routing cluster membership
    • 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

Definitions

  • the present specification relates to a wireless communication system, and more particularly, to a method and apparatus for merging a neighbor awareness networking (NAN) terminal to another NAN cluster in a wireless communication system.
  • NAN neighbor awareness networking
  • 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 merging a NAN terminal into another NAN cluster in a wireless communication system.
  • an object of the present disclosure is to provide a method for controlling schedule information between NAN terminals.
  • An object of the present disclosure is to provide a method for controlling the operation of NAN terminals when a NAN terminal merges with another NAN terminal in a wireless communication system.
  • a method for merging a NAN terminal into a NAN cluster in a wireless communication system may be provided.
  • the method of merging to the NAN cluster the first NAN terminal included in the first NAN cluster receiving a beacon frame of the second NAN cluster, obtaining cluster grade information of the second NAN cluster based on the beacon frame And merging the second NAN cluster when the cluster grade of the second NAN cluster is larger than the cluster grade of the first NAN cluster.
  • the first NAN terminal may transmit a notification frame to other NAN terminals in the NAN data cluster.
  • a receiving module for receiving information from an external device, a transmitting module for transmitting information to an external device, a receiving module, and a transmitting module It may include a processor for controlling the.
  • the processor receives the beacon frame of the first NAN cluster using the receiving module, obtains the cluster class information of the first NAN cluster based on the received beacon frame, and the cluster class of the first NAN cluster is the second NAN If greater than the cluster grade of the cluster, merge into a first NAN cluster, the first NAN terminal is included in the second NAN cluster, the first NAN terminal is included in the NAN data cluster in the second NAN cluster, the first NAN cluster When merged into the first NAN terminal may transmit a notification frame to other NAN terminals in the NAN data cluster.
  • the following may be commonly applied to a method and apparatus for merging a NAN terminal into a NAN cluster in a wireless communication system.
  • the notification frame may be transmitted in the NDC schedule interval.
  • the notification frame includes ID information of the second NAN cluster, time synchronization information of the second NAN cluster, anchor master rank information of the second NAN cluster, and time information moving to the second NAN cluster. Can be.
  • data beacon hop count information is included in the notification frame transmitted by the first NAN terminal. It may be further included.
  • the first NAN terminal may transmit a data beacon frame to the NAN terminals included in the NAN data cluster.
  • the data beacon frame may be transmitted in the NDC schedule period.
  • the first NAN terminal transmits a data beacon frame based on a backoff counter value, but the backoff counter may be determined based on dHC information.
  • the first NAN terminal when the first NAN terminal is merged into the second NAN cluster, the first NAN terminal may be set to a non-master and non-sink state.
  • the beacon frame may be any one of a NAN synchronization beacon frame and a NAN discovery beacon frame.
  • the present disclosure may provide a method and apparatus for merging a NAN terminal into another NAN cluster in a wireless communication system.
  • the present specification may provide a method of controlling schedule information between NAN terminals when the NAN terminal merges with another NAN terminal in a wireless communication system.
  • a NAN terminal when a NAN terminal merges with another NAN terminal in a wireless communication system, it may provide a method of controlling operations of the NAN terminals.
  • 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 of forming a NAN data cluster.
  • FIG. 11 illustrates a method of forming a NAN data path.
  • FIG. 12 is a diagram illustrating a method of setting an NDL schedule.
  • FIG. 13 is a diagram illustrating a method for operating a NAN terminal based on an NDL and an NDC.
  • FIG. 14 is a diagram illustrating a method for operating a NAN terminal based on an NDL and an NDC.
  • 15 is a diagram illustrating a method of operating a NAN terminal when the NAN terminal is merged with another NAN cluster.
  • 16 is a flowchart illustrating a method in which a NAN terminal is merged into another NAN cluster.
  • 17 is a flowchart illustrating a method in which a NAN terminal is merged into another NAN cluster.
  • 18 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 are provided by standard documents disclosed in at least one of the wireless access systems IEEE 802 system, 3GPP system, 3GPP LTE and LTE-Advanced (LTE-A) system, 3GPP2 system, Wi-Fi system and NAN system Can be supported. 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
  • 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.
  • 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 other than 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 of forming a NAN data cluster.
  • NAN terminals As described above, data exchange between NAN terminals may be performed.
  • the AP or GO may inform the client terminal of its existence by transmitting a beacon frame, and may perform parameter update for data / system based on the presence or absence of traffic. Therefore, there is a need for a terminal for controlling parameter updates based on traffic even in communication between NAN terminals.
  • NAN terminals may perform a setup process and data communication for data communication between a discovery window (DW).
  • the NAN data path may be a path through which NAN terminals perform data exchange between discovery windows.
  • two NAN terminals may form a NAN Data Link (NDL).
  • NDL NAN Data Link
  • two NAN terminals may perform data exchange in the NAN data path based on the NAN data link.
  • NDL schedule NDL Schedule for NAN data link of two NAN terminals may be formed, which will be described later.
  • the NAN terminals may form a NAN data cluster (NDC).
  • NDC NAN data cluster
  • the NAN data cluster may be a set of NAN terminals having at least one NAN data link.
  • NAN terminals in the NAN data cluster may have a common NDC schedule.
  • the NDL schedule may be a superset of the NDC schedule. That is, the plurality of NAN terminals forming the NAN data link may have an NDC schedule as a common schedule.
  • a service provider NAN terminal may exist in the NAN data cluster.
  • there may be a scheduler NAN terminal that performs a role for schedule management in the NAN data cluster.
  • the scheduler NAN terminal may play a role similar to the above-described AP or GO, which will be described later.
  • a plurality of NAN terminals may exist in a NAN cluster.
  • the first NAN terminal 1010 and A and the second NAN terminal 1020 and B may have a NAN data link.
  • the second NAN terminal 1020 and the third NAN terminal 1030 and C may have a NAN data link.
  • the first NAN terminal 1010, the second NAN terminal 1020, and the third NAN terminal 1030 may have one NAN data cluster.
  • the NDL schedules of the first NAN terminal 1010 and the second NAN terminal 1020 and the NDL schedules of the second NAN terminal 1020 and the third NAN terminal 1030 may include the NDC schedule in common.
  • the first NAN terminal 1010, the second NAN terminal 1020, and the third terminal 1030 included in the same NAN data cluster may have a common NDC schedule.
  • other NAN data clusters may be formed within the NAN cluster.
  • the NAN terminals may be included in a plurality of NAN data links and a plurality of NAN data clusters.
  • the third NAN terminal 1030 may be included in a plurality of NAN data clusters, and is not limited to the above-described embodiment.
  • FIG. 11 illustrates a method of forming a NAN data path.
  • two NAN terminals may establish a NAN data path based on the NAN data link.
  • one of the two NAN terminals may be an NDP responder NAN terminal (NDP Responder) 1110 and one may be an NDP initiator NAN terminal (NDP Initiator, 1120). That is, the NAN terminal to start data path formation among two NAN terminals may be an NDP initiator NAN terminal, and the responding terminal may be an NDP responder NAN terminal.
  • NDP Responder NDP responder NAN terminal
  • NDP Initiator NDP initiator NAN terminal
  • the service / application terminal of the NDP initiator NAN terminal 1120 may call a data request (DataRequest ()) method with the NAN DE and MAC terminals.
  • the NDP initiator NAN terminal 1120 may transmit an NDP request to the NDP responder NAN terminal 1110.
  • the NAN DE and NAN MAC terminals of the NDP responder NAN terminal 1110 may call a data indication (DataIndication ()) event to the service / application terminal.
  • the service / application terminal of the NDP responder NAN terminal 1110 may call a data response (DataResponse ()) method to the NAN DE and NAN MAC terminals.
  • the NDP responder NAN terminal 1110 may transmit an NDP response to the NDP initiator NAN terminal 1120.
  • the NDP responder NAN terminal 1110 and the NDP initiator NAN terminal 1120 may perform NDL setup.
  • the NDL setting may be set through an NDL schedule. Thereafter, the NDP responder NAN terminal 1110 and the NDP initiator NAN terminal 1120 may call a DataConfirm () event. Thereafter, the NDP responder NAN terminal 1110 and the NDP initiator NAN terminal 1120 may perform data communication. Through this, two NAN terminals in the NAN cluster may perform data exchange with each other, and are not limited to the above-described embodiment.
  • FIG. 12 is a diagram illustrating a method of setting an NDL schedule.
  • two NAN terminals may exchange messages for establishing a NAN data path.
  • one of the two NAN terminals may be an NDL Schedule Initiator NAN terminal 1220, and the other may be an NDL Schedule Responder NAN terminal 1210.
  • the above-described NDP initiator NAN terminal may be an NDL schedule initiator terminal
  • an NDP responder NAN terminal may be an NDL schedule responder terminal.
  • the NDL schedule starter NAN terminal 1220 may select an NDC schedule for an NDL schedule.
  • the NDL schedule initiator NAN terminal 1220 may form a new NAN data cluster to select an NDC schedule.
  • a new NAN cluster may be formed by the NDL schedule initiator NAN terminal 1220.
  • the NDL schedule initiator NAN terminal 1220 may select any one of NDC schedules of a participating NAN data cluster.
  • the NDL schedule initiator NAN terminal 1220 may transmit an NDL schedule request to the NDL schedule responder NAN terminal 1210. Thereafter, the NDL schedule responder NAN terminal 1210 may transmit an NDL schedule response to the NDL schedule initiator NAN terminal 1220.
  • the NDL schedule initiator NAN terminal 1210 and the NDL schedule responder NAN terminal 1220 may set an NDL schedule.
  • FIG. 13 is a diagram illustrating a method for operating a NAN terminal based on an NDL and an NDC.
  • NAN terminals may have a NAN data link and a NAN data cluster.
  • NAN terminals may exchange information for data exchange through an NDL schedule, which is a schedule for a NAN data link.
  • NAN terminals in the NAN data cluster may exchange information on the NAN data cluster and information on data exchange through an NDC schedule, which is a schedule for the NAN data cluster.
  • the NDL schedule may be a superset of the NDC schedule, as described above.
  • NAN terminals may operate at 2.4 GHz and / or 5 GHz. At this time, the NAN terminals may perform synchronization or exchange frames in the discovery window, as described above. In this case, NAN terminals may transmit data between discovery windows. That is, a resource block for data communication may be set between the discovery windows. In this case, the NAN terminals may have an NDL schedule and an NDC schedule in a resource block set between discovery windows. In addition, NAN terminals may perform data communication in resource blocks set between discovery windows.
  • the NDL schedule may have one or more time blocks between discovery windows.
  • the time block may be set as a bundle of a plurality of consecutive slots in units of 16 TUs.
  • the two NAN terminals forming the NDL may share information on when and through which channel through NDL schedule negotiation. That is, information necessary for data communication between two NAN terminals forming an NDL in an NDL schedule may be exchanged. Accordingly, for the NAN data path and the NAN data link, two NAN terminals may operate by updating their existence and related parameter information through the NDL schedule. In this case, when only one NAN terminal transmits a message, if a message is idle after performing a clear channel assessment (CCA) without contention, the message may be transmitted. However, when a plurality of NAN terminals transmit a message, a contention window (CW) value may be preset and transmitted.
  • CCA clear channel assessment
  • a scheduler NAN terminal and a non-scheduler NAN terminal for an NDL schedule may be determined.
  • Two NAN terminals may determine a scheduler NAN terminal and a non-scheduler NAN terminal based on the above-described NDL schedule request and NDL schedule response. That is, two NAN terminals may determine a scheduler NAN terminal and a non-scheduler NAN terminal through negotiation, and are not limited to the above-described embodiment.
  • FIG. 14 is a diagram illustrating a method for operating a NAN terminal based on an NDL and an NDC.
  • a time window from 0 TU to 16TU may correspond to a discovery window period.
  • the discovery window from 0TU to 16TU may be a discovery window related to operation at 2.4 GHz.
  • from 128TU to 144TU may also be a discovery window.
  • the discovery window from 128 TU to 144 TU may be a discovery window associated with operation at 5 GHz.
  • one cycle to 512 TU is completed and the next discovery window interval may arrive.
  • time blocks 1410, 1420, and 1430 may be set between the discovery windows.
  • an NDL schedule may be set in the above-described time blocks 1410, 1420, and 1430. That is, the above-described time blocks 1410, 1420, and 1430 may be time blocks for an NDL schedule.
  • data exchange may be performed between NAN terminals in another section between discovery windows, as described above. For example, two NAN terminals may perform data exchange after a time block corresponding to an NDL schedule. That is, the NDL schedule may be set to exchange necessary information before two NAN terminals perform data exchange.
  • any one of the time blocks 1410, 1420, and 1430 may be set as a time block for an NDC schedule. In this case, information commonly applied to the NAN data cluster may be exchanged in the NDC schedule.
  • the NAN terminal may transmit a paging message for each NAN data link in the NDC schedule interval.
  • the NAN data link is formed between two NAN terminals, and the paging message may include only one NDL ID.
  • each NAN The terminals may have one common NDL ID.
  • the service provider or scheduler NAN terminal may provide the NDL ID to the counterpart NAN terminal through a paging message.
  • the counterpart NAN terminal and the service provider or scheduler NAN terminal are always awake in the sink mode NAN data link (S-NDL) interval based on the paging message. That is, in the case of a service based on one purpose, such as a chat or broadcast service, it may be set to awake on a specific NAN data link based on a paging message, and is not limited to the above-described embodiment.
  • the NAN terminal lists in the NAN data cluster may be shared with all NAN terminals in the NAN data cluster through an NDC schedule.
  • the scheduler NAN terminal in the NAN data cluster may obtain information about all NAN terminals in the NAN data cluster.
  • the scheduler NAN terminal may share the update information to all NAN terminals of the NAN data cluster.
  • the information of the NAN terminal may include at least one of address information (NAN MAC address, data address, IP address), role and status information of the NAN terminal, and NAN data link / NAN data cluster information. It is not limited to one embodiment.
  • 15 is a diagram illustrating a method of operating a NAN terminal when the NAN terminal is merged with another NAN cluster.
  • NAN terminals may form a NAN data link to perform data exchange.
  • the NAN terminal may be included in the NAN data cluster.
  • NAN terminals included in the same NAN data cluster may have a common NDC schedule, as described above.
  • a NAN terminal having one or more active NAN data links (active NDLs) may be merged into another NAN cluster.
  • the above-described NAN terminal (NAN terminal having one or more activated NAN data link) discovers another NAN cluster and is located within the range of the NAN cluster.
  • the above-described NAN terminal may check the cluster grade (CG) of the NAN cluster that includes the NAN terminal, and may determine the cluster grade of the found NAN cluster.
  • the cluster grade may be calculated based on Equation 2 below.
  • A1 may be a Master Preference value of the anchor master in the NAN cluster.
  • A2 may be an 8 octet TSF value of the NAN cluster. That is, the cluster grade of the NAN cluster may be determined based on the anchor master rank in the NAN cluster.
  • the NAN terminal may receive a NAN Synchronization Beacon frame or a NAN Discovery Beacon frame for another NAN cluster. Through this, the NAN terminal may acquire cluster grade information of another NAN cluster. In this case, when the cluster grade of another NAN cluster is larger than the cluster grade of its own NAN cluster, the NAN terminal may be merged into the discovered NAN cluster. In this case, the NAN terminal may adjust the current TSF timer with a timing clock or clock offset value of the new NAN cluster.
  • the NAN terminal may be a NAN terminal forming one or more NAN data links as described above.
  • the NAN terminal may be a terminal forming a NAN data cluster.
  • an announcement frame may be transmitted to other NAN terminals in the NAN data cluster in the NDC schedule of the NAN data cluster.
  • the information included in the notification frame may be as shown in Table 3 below.
  • the notification frame includes new NAN cluster ID information, TSF offset information for the new NAN cluster compared to the current NAN cluster, anchor master rank information of the new NAN cluster, and time information for moving the NAN terminal to the new NAN cluster. May be included.
  • cluster grade information of the new NAN cluster may be included in the notification frame instead of anchor master rank information of the new NAN cluster.
  • information on the master preference and the 8 octet TSF value of the anchor master of the new NAN cluster may be included instead of the anchor master rank information of the new NAN cluster. That is, cluster grade information for the new NAN cluster may be included in the notification frame and transmitted, but is not limited to the above-described embodiment.
  • additional capability information of the UE may be selectively included in the notification frame as compared with the TSF of the new NAN cluster.
  • hop count information with an anchor master of a new NAN cluster may be selectively included in a notification frame.
  • the notification frame may include information on the merged new NAN cluster, which is not limited to the above-described embodiment.
  • each NAN terminal included in the NAN data cluster may receive information about a new NAN cluster.
  • each NAN terminal may transmit the above-described notification frame to merge each NAN data link into a new NAN cluster.
  • the notification frame may include information as shown in Table 3 below, but is not limited to the above-described embodiment.
  • NAN terminals may receive a plurality of notification frames.
  • the NAN terminals may transmit a notification frame for merging based on information on a notification frame having a cluster grade or a master preference and an 8 octet TSF value from information included in the notification frame.
  • a notification frame for merging may be transmitted based on the notification frame information with a fast switching time.
  • the NAN terminal may not allow merging to a new NAN cluster.
  • the NAN terminal may indicate whether merging is allowed to the counterpart NAN terminal using an indicator on whether the merging is allowed.
  • the indicator may be indicated as "NON-MERGING".
  • the counterpart NAN terminal does not want to merge with the new NAN cluster, it may indicate information about the merging impossible through the indicator.
  • NAN terminal forming one or more NAN data links or a NAN terminal included in a NAN data cluster joins a new NAN cluster
  • the role and state of the NAN terminal are described in the above-described non-master non- It can be fixed as a sink (Non-Master Non-Sync, NMNS).
  • NMNS Non-Master Non-Sync
  • the NAN terminal may be awakened in the discovery window that comes first after joining the new NAN data cluster.
  • the NAN terminal may be configured to be awake for several discovery windows after the first discovery window. This allows time and synchronization when joining a new NAN cluster.
  • the first NAN terminals 1510 and C may be NAN terminals included in the first NAN data cluster.
  • the first NAN terminal 1510 may be a NAN terminal included in the first NAN cluster.
  • the first NAN data cluster and the first NAN cluster may have different concepts, as described above.
  • the NAN terminals included in the first NAN data cluster may be NAN terminals having a capability for cluster merging. That is, NAN terminals included in the first NAN data cluster may be merged into another NAN cluster other than the first NAN cluster.
  • the first NAN terminal 1510 may receive a NAN synchronization beacon or a NAN discovery beacon frame of the second NAN cluster.
  • the first NAN terminal 1510 may calculate a cluster grade for the second NAN cluster based on information included in the NAN synchronization beacon or the NAN discovery frame.
  • the cluster grade of the second NAN cluster may be greater than the cluster grade of the first NAN cluster.
  • the first NAN terminal 1510 may transmit a notification frame to the NAN terminals in the first NAN data cluster in the NDC schedule period.
  • the information on the notification frame may be as described in Table 3 above.
  • the first NAN terminal 1510 receives a NAN beacon frame (NAN synchronization beacon frame or NAN discovery beacon frame), but may not receive any notification frame in the NDC schedule interval. That is, the first NAN terminal 1510 may be the first NAN terminal attempting merging to the second NAN cluster.
  • the first NAN terminal 1510 may include a new parameter in the notification frame and transmit the notification frame.
  • the new parameter may be a hop count for data beacons (dHC).
  • dHC hop count newly defined for the data beacon, and is not limited to the aforementioned name. In the following description, it is described as dHC for convenience of description.
  • the first NAN terminal 1510 may include its hop count for the second NAN cluster in the notification frame and transmit the notification frame. That is, the first NAN terminal 1510 may transmit hop count information for identification as a first NAN terminal to be merged in a notification frame and is not limited to the above-described embodiment.
  • the second NAN terminal 1520 and B and the third NAN terminal 1530 and Z may receive a notification frame transmitted by the first NAN terminal 1510.
  • the notification frame may include dHC.
  • the second NAN terminal 1520 and the third NAN terminal 1530 may transmit a new notification frame in a broadcast manner based on the received notification frame after receiving the notification frame.
  • the dHC value may be increased by one in the notification frame transmitted by the second NAN terminal 1520 and the third NAN terminal 1530.
  • the fourth NAN terminal 1540 and A may receive a notification frame transmitted by the second NAN terminal 1520 and the third NAN terminal 1530. Thereafter, the fourth NAN terminal 1540 may transmit a new notification frame in a broadcast manner based on the received notification frame.
  • the dHC of the notification frame transmitted by the fourth NAN terminal 1540 may be a value increased by one from the dHC value of the notification frame transmitted by the second NAN terminal 1520 and the third NAN terminal 1530. That is, hop count information of NAN terminals included in the first NAN data cluster may be included in the notification frame and transmitted.
  • the first NAN terminal 1510, the second NAN terminal 1520, the third NAN terminal 1530, and the fourth NAN terminal 1540 merge with the second NAN cluster based on the received notification frame information. Can be.
  • the role and state of the terminals 1510, 1520, 1530, and 1540 may be NMNS.
  • a data beacon frame may be transmitted in an NDC schedule for the first NAN data cluster, and synchronization may be performed through this.
  • the data beacon frame may be as shown in Table 4 below.
  • the data beacon frame may include time stamp information.
  • the data beacon frame may include role and status information of the NAN terminal.
  • the data beacon frame may include NAN cluster ID, anchor master rank, hop count information and beacon transmission time information of the anchor master as the cluster information, but is not limited to the above-described embodiment.
  • the NAN terminals included in the first NAN data cluster receive the above information
  • the NAN terminals update the TSF timer and the anchor master record.
  • the NAN terminals may operate only to update the above-described information and not directly become an anchor master as a result of anchor master selection. That is, the NAN terminals included in the NAN data cluster may be configured not to directly become anchor masters in consideration of the NAN data cluster.
  • NAN terminals in the same NAN data cluster may prevent the master rank value from being changed when receiving a notification frame or receiving a NAN beacon frame and merging to another NAN cluster. That is, the master preference, random factor, and NAN interface address constituting the master rank may not be changed.
  • the data beacon frame needs to be sequentially transmitted from the first NAN terminal 1510 toward the second NAN terminal 1520 and the third NAN terminal 1530. Therefore, it may be necessary to set the backoff value for sequentially transmitting the data beacon frame.
  • the backoff counter was randomly used based on Table 5 below. That is, in consideration of Table 5 below, a synchronization beacon frame was transmitted using randomly distributed values uniformly distributed in the [0, CW_RS] interval.
  • the backoff count value may be set by dividing the case where the hop count is 0 and the case where the hop count is greater than 0, and is not limited to the above-described embodiment.
  • NAN data cluster is also performing data communication, there is a need to match the time synchronization of the NAN terminals in the NAN data cluster. That is, in the above-described first NAN data cluster, the first NAN terminal 1510 transmits the data beacon frame first, and the second NAN terminal 1520 and the third NAN terminal 1530 transmit the data beacon frame first. The fourth NAN terminal 1540 needs to operate to transmit the data beacon frame.
  • the backoff count value may be set based on the hop counter of the notification frame transmitted by each NAN terminal.
  • each NAN terminal may set a backoff count value based on a hop count value for the anchor master of the new NAN cluster.
  • the backoff count may be set as a hop count value.
  • the backoff count may be set based on Equation 3 below. That is, the backoff count may be set based on the hop count integer multiple value.
  • the backoff count values may be set not to overlap in consideration of the difference between the hop count values.
  • some overlap may be set, and the present invention is not limited to the above-described embodiment.
  • the hop count may be set based on the above-described method based on a value obtained by subtracting a hop count value of the NAN terminal that initially sent the data beacon. That is, the backoff count value may be set in consideration of the hop count value sequentially increasing based on the hop count value of the first NAN terminal 1510.
  • the backoff value for data beacon frame transmission may be set using the dHC value of the above-described notification frame.
  • the hop count may be distinguished from the case where the hop count is 0 and the non-zero case.
  • the backoff count may be differentially set so as not to overlap according to the dHC value.
  • the backoff count value may be large.
  • the NAN terminal having a small dHC value may be configured to transmit the data beacon frame first.
  • the NAN terminal may transmit the data beacon frame at the same time by overlapping the backoff count value, it is not limited to the above-described embodiment.
  • 16 is a flowchart illustrating a method in which a NAN terminal is merged into another NAN cluster.
  • the first NAN terminal included in the first NAN cluster may receive the beacon frame of the second NAN cluster (S1610). As described above with reference to FIGS. 10 to 15, the NAN data cluster is formed in the NAN cluster. Can be.
  • the first NAN terminal may be a NAN terminal included in a NAN data cluster in the first NAN cluster.
  • the first NAN terminal may receive a beacon frame from the second NAN cluster which is another NAN cluster.
  • the beacon frame may be any one of a NAN synchronization beacon frame and a NAN discovery beacon frame.
  • the first NAN terminal may obtain cluster grade information of the second NAN cluster based on the received beacon frame (S1620). At this time, as described above with reference to FIGS. It may be determined based on the Master Preference and an 8 octet TSF value. That is, the cluster grade may be determined based on the master rank for the anchor masters in the cluster.
  • the first NAN terminal may be merged into the second NAN cluster (S1630).
  • the cluster grade of the second NAN cluster is higher than the cluster grade of the first NAN cluster.
  • the first NAN terminal may be merged into the second NAN cluster.
  • the first NAN terminal may transmit a notification frame to other NAN terminals in the NAN data cluster.
  • the first NAN terminal is located in the first NAN cluster. It may be a NAN terminal included in a NAN data cluster.
  • the first NAN terminal may provide information for merging to the second NAN cluster to other NAN terminals in the NAN data cluster through a notification frame. Through this, other NAN terminals in the NAN data cluster may also be merged into the second NAN cluster.
  • the notification frame may be transmitted in the NDC schedule interval, as described above.
  • 17 is a flowchart illustrating a method in which a NAN terminal is merged into another NAN cluster.
  • the first NAN terminal may obtain cluster grade information of the second NAN cluster based on the beacon frame of the second NAN cluster.
  • the cluster grade may be determined based on the rank of the anchor master in the cluster, as described above.
  • the first NAN terminal may be included in the first NAN cluster without merging into the second NAN cluster (S1720).
  • the first NAN terminal may be merged into the second NAN cluster and may transmit a notification frame to other NAN terminals in the NAN data cluster.
  • the NAN terminals included in the first NAN terminal and the NAN data cluster may be NAN terminals that are allowed to merge to other NAN clusters.
  • the first NAN terminal may provide information on merging to other NAN terminals in the NAN data cluster through a notification frame, as described above.
  • the notification frame may include hop count information for the data beacon.
  • the backoff counter may be determined based on hop count information for the data beacon. The backoff counter may be used when the first NAN terminal transmits another NAN data beacon in the NAN data cluster, as described above.
  • 18 is a block diagram of a terminal device.
  • the terminal device may be a NAN terminal.
  • 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 processor 120 of the terminal device 100 may receive a beacon frame of the first NAN cluster by using the receiving module 130.
  • the first NAN cluster may be a NAN cluster different from the NAN cluster currently containing the terminal device (or NAN terminal). Thereafter, the processor 120 may obtain cluster grade information of the first NAN cluster based on the received beacon frame.
  • the processor 120 may merge into the first NAN cluster.
  • the second NAN cluster may be a NAN cluster in which a terminal device (or a NAN terminal) is currently included.
  • the terminal device may be included in the NAN data cluster in the second NAN cluster.
  • the NAN data cluster may have a common NDC schedule, as described above.
  • the processor 120 may transmit a notification frame to other NAN terminals in the NAN data cluster. In this way, the terminal device can provide information for merging to the first cluster to other NAN terminals in the NAN data cluster.
  • 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

La présente invention concerne un procédé au moyen duquel un terminal de NAN se fusionne dans une grappe de NAN dans un système de communication sans fil, le procédé comprenant les étapes consistant : à recevoir une trame de balise d'une seconde grappe de NAN par un premier terminal de NAN inclus dans une première grappe de NAN ; à acquérir des informations de qualité de grappe de la seconde grappe de NAN sur la base de la trame de balise ; et à se fusionner dans la seconde grappe de NAN lorsqu'une qualité de grappe de la seconde grappe NAN est supérieure à une qualité de grappe de la première grappe NAN, le premier terminal NAN étant incluse dans une grappe de données de NAN dans la première grappe de NAN, et le premier terminal de NAN transmet une trame de notification à d'autres terminaux de NAN dans la grappe de données de NAN, lorsqu'il se fusionne dans la seconde grappe NAN.
PCT/KR2016/011054 2015-10-02 2016-10-04 Procédé de fusionnement d'un terminal de nan dans une grappe de nan dans un système de communication sans fil, et dispositif WO2017057988A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201562236817P 2015-10-02 2015-10-02
US62/236,817 2015-10-02
US201562251126P 2015-11-05 2015-11-05
US62/251,126 2015-11-05

Publications (1)

Publication Number Publication Date
WO2017057988A1 true WO2017057988A1 (fr) 2017-04-06

Family

ID=58427683

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2016/011054 WO2017057988A1 (fr) 2015-10-02 2016-10-04 Procédé de fusionnement d'un terminal de nan dans une grappe de nan dans un système de communication sans fil, et dispositif

Country Status (1)

Country Link
WO (1) WO2017057988A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
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 삼성전자주식회사 클러스터 간의 데이터 송수신 방법 및 장치
WO2019055098A1 (fr) * 2017-09-13 2019-03-21 Intel IP Corporation Appareil, système et procédé de communication de données sur un chemin de données d'informatique de réseau à portée de voisinage (nan) (ndp)
WO2021132940A1 (fr) * 2019-12-23 2021-07-01 삼성전자 주식회사 Dispositif électronique et procédé de commande de communication de dispositif électronique basée sur un réseautage sensible au voisinage (nan)
WO2024096530A1 (fr) * 2022-11-03 2024-05-10 삼성전자 주식회사 Dispositif électronique de fusion de grappes de communication nan et son procédé de fonctionnement

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150098388A1 (en) * 2013-08-13 2015-04-09 Huawei Device Co., Ltd. Method, device, and system for joining neighbor awareness network device cluster
WO2015073676A1 (fr) * 2013-11-14 2015-05-21 Qualcomm Incorporated Fusion de grappes nan assistée par serveur
US20150200811A1 (en) * 2014-01-14 2015-07-16 Nokia Corporation Method, apparatus, and computer program product for wireless network cluster discovery and concurrency management
WO2015119440A1 (fr) * 2014-02-05 2015-08-13 엘지전자 주식회사 Procédé et dispositif pour émettre et recevoir des signaux au moyen d'un terminal nan d'un système de communication sans fil
WO2015126220A2 (fr) * 2014-02-24 2015-08-27 엘지전자 주식회사 Procédé de participation à une grappe nan dans un système de communication sans fil, et dispositif associé

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150098388A1 (en) * 2013-08-13 2015-04-09 Huawei Device Co., Ltd. Method, device, and system for joining neighbor awareness network device cluster
WO2015073676A1 (fr) * 2013-11-14 2015-05-21 Qualcomm Incorporated Fusion de grappes nan assistée par serveur
US20150200811A1 (en) * 2014-01-14 2015-07-16 Nokia Corporation Method, apparatus, and computer program product for wireless network cluster discovery and concurrency management
WO2015119440A1 (fr) * 2014-02-05 2015-08-13 엘지전자 주식회사 Procédé et dispositif pour émettre et recevoir des signaux au moyen d'un terminal nan d'un système de communication sans fil
WO2015126220A2 (fr) * 2014-02-24 2015-08-27 엘지전자 주식회사 Procédé de participation à une grappe nan dans un système de communication sans fil, et dispositif associé

Cited By (8)

* Cited by examiner, † Cited by third party
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
WO2018221961A1 (fr) * 2017-06-01 2018-12-06 Samsung Electronics Co., Ltd. Procédé et appareil de transmission et de réception de données entre groupes
KR20180131965A (ko) * 2017-06-01 2018-12-11 삼성전자주식회사 클러스터 간의 데이터 송수신 방법 및 장치
US10924911B2 (en) 2017-06-01 2021-02-16 Samsung Electronics Co., Ltd Method and apparatus for inter-cluster data transmission and reception
KR102502806B1 (ko) * 2017-06-01 2023-02-23 삼성전자주식회사 클러스터 간의 데이터 송수신 방법 및 장치
WO2019055098A1 (fr) * 2017-09-13 2019-03-21 Intel IP Corporation Appareil, système et procédé de communication de données sur un chemin de données d'informatique de réseau à portée de voisinage (nan) (ndp)
WO2021132940A1 (fr) * 2019-12-23 2021-07-01 삼성전자 주식회사 Dispositif électronique et procédé de commande de communication de dispositif électronique basée sur un réseautage sensible au voisinage (nan)
WO2024096530A1 (fr) * 2022-11-03 2024-05-10 삼성전자 주식회사 Dispositif électronique de fusion de grappes de communication nan et son procédé de fonctionnement

Similar Documents

Publication Publication Date Title
WO2017057988A1 (fr) Procédé de fusionnement d'un terminal de nan dans une grappe de nan dans un système de communication sans fil, et dispositif
WO2016140466A1 (fr) Procédé de mise en oeuvre de radiomessagerie dans un système lan sans fil et dispositif utilisant ce procédé
WO2015126220A2 (fr) Procédé de participation à une grappe nan dans un système de communication sans fil, et dispositif associé
WO2015060651A1 (fr) Procédé et appareil de transmission de signal par un terminal nan dans un système de communication sans fil
WO2015152657A1 (fr) Procédé et appareil pour émettre-recevoir un signal par un terminal de réseautage sensible au voisinage (nan) dans un système de communication sans fil
WO2016171527A1 (fr) Procédé et appareil pour effectuer une inscription auprès d'un serveur de mandataire nan dans un système de communications sans fil
WO2018048202A1 (fr) Procédé et dispositif de recherche de point d'accès dans un réseau local (lan) sans fil
WO2015170818A1 (fr) Procédé et appareil de réception d'un signal au moyen d'un dispositif nan dans un système de communication sans fil
WO2016036140A1 (fr) Procédé et dispositif d'ordonnancement de ressource sans fil pour nan
WO2015072796A1 (fr) Procédé et appareil de modification d'état d'un terminal nan dans un système de communications sans fil
WO2016144088A1 (fr) Procédé et appareil permettant de transmettre des données à l'aide de multiples canaux dans un système de communication sans fil
WO2015069041A1 (fr) Procédé et appareil permettant à un terminal nan d'émettre/de recevoir un signal dans un système de communication sans fil
WO2011149285A2 (fr) Procédé et appareil d'émission-réception de données dans système de réseau local (lan) sans fil
WO2015126187A1 (fr) Procédé et dispositif pour partager une adresse de multidiffusion pour un dispositif nan dans un système de communication sans fil
WO2013151311A1 (fr) Procédé et appareil d'accès à un canal dans un système wlan
WO2013151312A1 (fr) Procédé et appareil d'accès à un canal dans un système wlan
WO2015115829A1 (fr) Procédé et dispositif au moyen desquels un terminal nan transmet une trame de recherche de service nan dans un système de communication sans fil
WO2017105154A1 (fr) Procédé et dispositif au moyen desquels un terminal de nan exécute une opération de télémétrie dans un système de communication sans fil
WO2016137224A1 (fr) Procédé et appareil pour transmettre des données dans un système de communication sans fil
WO2013141669A1 (fr) Procédé et appareil d'accès à un canal dans un système lan sans fil
WO2016204497A1 (fr) Procédé et appareil permettant à un serveur mandataire nan de mettre en oeuvre une fonction de dispositif relais dans un système de communication sans fil
WO2017146461A1 (fr) Procédé pour réseau sensible au voisinage selon un schéma de radiomessagerie et terminal sans fil utilisant celui-ci
WO2013058577A2 (fr) Procédé de planification dans un système de communication sans fil et dispositif correspondant
WO2017065561A1 (fr) Procédé et appareil de transmission de trame par un terminal nan dans un système de communications sans fil
WO2014092450A1 (fr) Procédé et dispositif d'accès à un canal à base de fenêtre d'accès restreint dans un système wlan

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: 16852134

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16852134

Country of ref document: EP

Kind code of ref document: A1