WO2017123068A1 - Procédé et appareil d'échange de données par un terminal nan dans un système de communications sans fil - Google Patents

Procédé et appareil d'échange de données par un terminal nan dans un système de communications sans fil Download PDF

Info

Publication number
WO2017123068A1
WO2017123068A1 PCT/KR2017/000511 KR2017000511W WO2017123068A1 WO 2017123068 A1 WO2017123068 A1 WO 2017123068A1 KR 2017000511 W KR2017000511 W KR 2017000511W WO 2017123068 A1 WO2017123068 A1 WO 2017123068A1
Authority
WO
WIPO (PCT)
Prior art keywords
nan
terminal
nan terminal
service
data link
Prior art date
Application number
PCT/KR2017/000511
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 WO2017123068A1 publication Critical patent/WO2017123068A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H04W4/08—User group 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
    • H04W76/00—Connection management
    • 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 performing a data exchange by a neighbor awareness networking (NAN) terminal 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 for performing data exchange by a NAN terminal in a wireless communication system.
  • An object of the present specification is to provide a method for a NAN terminal to perform data exchange based on a multicast service type in a wireless communication system.
  • An object of the present specification is to provide a method for sharing information between NAN terminals in a NAN data cluster (NDC) in a wireless communication system.
  • NDC NAN data cluster
  • a method for performing data exchange by a NAN terminal in a wireless communication system may be provided.
  • the method of performing the data exchange between the NAN terminal receives the NAN data link request message for the first service from another NAN terminal, and in response to the NAN data link request, the NAN data link response message to the second NAN terminal Transmitting, establishing a NAN data link with another NAN terminal, and performing data exchange with the second NAN terminal through the NAN data path.
  • the first service is a multicast service
  • information on the multicast service type may be provided to another NAN terminal.
  • a receiving module for receiving information from an external device, a transmitting module for transmitting information to an external device, and a receiving module and a transmitting module are controlled. It may include a processor. At this time, the processor receives a NAN data link request message for the first service from another NAN terminal, transmits a NAN data link response message to another NAN terminal in response to the NAN data link request, and establishes a NAN data link with the NAN terminal. And exchange data with another NAN terminal through the NAN data path.
  • the first service is a multicast service
  • information on the multicast service type may be provided to another NAN terminal.
  • the multicast service type may be set to any one of the first type and the second type.
  • the first type is a multicast service type in which one service provider NAN terminal provides a first service to a plurality of NAN terminals, and the second type is a plurality of NAN terminals.
  • the first service may be a multicast service type provided.
  • the plurality of NAN terminals that provide the first service may form a multicast group.
  • the plurality of NAN terminals included in the multicast group may share common address information and provide a first service based on the common address information.
  • the first NAN terminal when the first NAN terminal and the second NAN terminal form a multicast group, the first NAN terminal includes information indicating a second type in a NAN data link response message. It may transmit to the second NAN terminal.
  • the third NAN terminal when the third NAN terminal joins the multicast group, the third NAN terminal is the first NAN.
  • a NAN data link establishment procedure may be performed with either the terminal or the second NAN terminal.
  • the third NAN terminal when the third NAN terminal performs a NAN data link establishment procedure with either one of the first NAN terminal and the second NAN terminal, the third NAN terminal performs the NAN data link establishment procedure.
  • Common address information may be received from the performing NAN terminal.
  • the first NAN terminal when the third NAN terminal performs a NAN data link establishment procedure with the first NAN terminal, the first NAN terminal provides information about the second NAN terminal to the third NAN terminal.
  • information about the third NAN terminal may be provided to the second NAN terminal, and the second NAN terminal and the third NAN terminal may perform data exchange based on the information received from the first NAN terminal.
  • the first NAN terminal and the second NAN terminal when the first NAN terminal and the second NAN terminal form a multicast group, the first NAN terminal and the second NAN terminal form a second type in a process of forming a NAN data link. Information can be exchanged.
  • the present specification may provide a method in which a NAN terminal performs data exchange in a wireless communication system.
  • the present specification may provide a method in which a NAN terminal performs data exchange based on a multicast service type in a wireless communication system.
  • the present specification may provide a method for sharing information between NAN terminals in a NAN data cluster (NDC) in a wireless communication system.
  • NDC NAN data cluster
  • 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 illustrates a method for NAN terminals establishing a NAN data link.
  • 16 is a diagram illustrating a structure of frames exchanged by NAN terminals.
  • 17 is a diagram illustrating a method in which a NAN terminal operates based on a multicast service type.
  • 18 is a diagram illustrating a method of performing data exchange between NAN terminals.
  • 19 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 B and the third NAN terminal 1030 and C may have a NAN data link.
  • the first NAN terminals 1010 and A, the second NAN terminals 1020 and B, and the third NAN terminals 1030 and C may have one NAN data cluster.
  • the NDL schedules of the first NAN terminals 1010 and A and the second NAN terminals 1020 and B and the NDL schedules of the second NAN terminals 1020 and B and the third NAN terminals 1030 and C are commonly NDC schedules. It may include. That is, the first NAN terminals 1010 and A, the second NAN terminals 1020 and B, and the third terminals 1030 and C included in the same NAN data cluster may have a common NDC schedule. In addition, other NAN data clusters may be formed within the NAN cluster. In addition, the NAN terminals may be included in a plurality of NAN data links and a plurality of NAN data clusters. For example, the third NAN terminals 1030 and C may be included in a plurality of NAN data clusters, and the present invention is not limited to the above-described embodiment.
  • information on the NAN data cluster as information exchanged in an NDC schedule may be as shown in Table 3 below.
  • synchronization information NDC tight synchronization
  • the synchronization information may include at least one of a time stamp, device role / state information, and cluster information. That is, information for synchronizing the NAN terminals included in the NAN data cluster may be included.
  • NDC information updates may be included.
  • the NDC update information may include at least one or more of NAN Cluster Merging Announcement and NDC Base Schedule Announcement information. That is, with respect to the NAN data cluster, update information such as cluster merging or NDC base schedule change may be included and exchanged.
  • the terminal update information may include at least one information of a further availability update (FA update), capability and operation mode update (Capability and Operating mode updates) information. That is, when information of the NAN terminal included in the NAN data cluster is changed, the information on the NAN terminal may be included and exchanged.
  • FA update further availability update
  • Capability and Operating mode updates Capability and Operating mode updates
  • information for maintaining and managing the NAN data cluster may be included in the NDC schedule and exchanged, but 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. Parameters for the above-described methods and events are described below.
  • 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.
  • 15 illustrates a method for NAN terminals establishing a NAN data link.
  • NAN terminals may establish a NAN data link and a NAN data path.
  • the NDP / NDL requester terminal 1520 may transmit an NDP / NDL request message to the NDP / NDL responder terminal 1510 (hereinafter, the responder terminal).
  • the requestor terminal 1520 may be a subscriber terminal, and the responder terminal 1510 may be a publisher terminal.
  • the responder terminal 1510 may transmit an NDP / NDL response message to the requester terminal 1520 in response.
  • the NDP / NDL response message may be message 1 (Msg. 1).
  • the requestor terminal 1520 and the responder terminal 1510 may establish a NAN data link and a NAN data path through the exchange of messages 2 to 4 (Msg. 2 to Msg. 4) as additional messages.
  • the requestor terminal 1520 and the responder terminal 1510 may perform a process related to setup / join of a NAN data cluster in a process of establishing a NAN data link and a NAN data path. . Specifically, the requestor terminal 1520 and the responder terminal 1510 may exchange information on whether to join the existing NAN data cluster or to create a new NAN data cluster in the process of establishing the NAN data link and the NAN data path. Can be.
  • the NAN DE and NAN MAC stages when a new NAN data cluster is created, the NAN DE and NAN MAC stages generate an NDC ID and address information used in the NDC and return them to a service / application stage, and return the information to other NAN terminals.
  • the address information used in the NDC may be at least one of an NDC IPv6 Multicast IP address and an NDC IPv6 multicast Ethernet address.
  • address information used in the NDC may be defined and used as a MAC level multicast / broadcast address regardless of IPv6. That is, by defining and assigning a unique MAC address for each NAN data cluster, it can be configured as a frame including IPv6 or a MAC level frame including a specific MAC address. Accordingly, address information may be set differently.
  • the requestor terminal 1520 and the responder terminal 1510 determine whether to create or join the NAN data cluster, and then, in the process of setting the NDC schedule (or NDC base schedule) for the NAN data link and the NAN data path. You can decide. In this case, as an example, when creating a NAN data cluster, a new NDC schedule may be generated. In addition, as an example, when joining an existing NAN data cluster, it may be set to follow an existing NDC schedule.
  • the controller may be operated in a secure mode for security.
  • an NDC Multicast Master Key (NDC MMK) or an NDC Multicast Temporary Key (NDC MTK) may be generated and shared.
  • the NAN terminal additionally joining the NAN data cluster may receive the above-described key value.
  • NAN terminals in the NAN data cluster may exchange information necessary for NAN data cluster maintenance and management based on the above-described address information and security information in the NDC schedule interval, and the present invention is not limited to the above-described embodiment.
  • the above-described responder terminal 1510 may be a security authenticator, and the requester terminal 1520 may be a security supplicant.
  • the responder terminal 1510 and the requester terminal 1520 may have a shared paired master key (PMK) as a shared key.
  • the responder terminal 1510 providing the service may transmit a random number for generating a paired temporary key (PTK) to the requester terminal 1520 through message 1 (or an NDP / NDL response message).
  • the responder terminal 1510 and the requester terminal 1520 may generate a PTK using random numbers.
  • the requester terminal 1520 may encrypt the random number value and necessary information using the PTK values generated through the message 2 and provide the encrypted information to the responder terminal 1510.
  • the responder terminal 1510 and the requester terminal 1520 may confirm that the same PMK exists as a shared key.
  • the responder terminal 1510 may generate an MTK using GMK (Group Master Key), encrypt the GTK using information of the PTK in message 3, and deliver the MTK to the requester terminal 1520.
  • the requester terminal 1520 may transmit the message 4 to the responder terminal 1510 as an ACK for the message 3.
  • the details of the above-mentioned messages 1 to 4 for unicast may be based on the IEEE802.11 standard.
  • the responder terminal 1510 which is a service provider, may provide MTK to the requester terminal 1520 by encrypting it. It is not limited to one embodiment.
  • NDC MTKSA NDC MTKSA
  • 16 is a diagram illustrating a structure of frames exchanged by NAN terminals.
  • a field for a frame is set based on a NAN Synchronization frame or a NAN Discovery Beacon Frame format.
  • the frame may include three address fields as A1, A2, and A3.
  • the A1 field may be set as a destination address.
  • the A2 field may be set to a source / transmitter address.
  • the A3 field may be set to a cluster ID.
  • A1 may be a frame format used in the NAN data cluster, and A1 needs to include a MAC address used in the NAN data cluster.
  • A1 may include destination information as one address information, and a new A4 field may be set to NAN data cluster ID. That is, in the case of the NAN data cluster, an address information field for indicating that the NAN terminals in the NAN data cluster perform frame exchange may be included, and is not limited to the above-described embodiment.
  • 17 is a diagram illustrating a method in which a NAN terminal operates based on a multicast service type.
  • the NAN data link and the NAN data path may be configured in two NAN terminals.
  • the multicast service may be a type in which one NAN terminal provides a service to a plurality of NAN terminals (hereinafter, a one-to-many type).
  • one NAN terminal may provide a service to a plurality of other NAN terminals.
  • FIG. 17 there is a type (hereinafter, many-to-many type) in which a plurality of NAN terminals provide a service to each other.
  • a service among a plurality of NAN terminals such as a chat or a game, and an operation considering this may be necessary when the NAN terminal operates.
  • the publisher NAN terminal may include information indicating that a service needs to be provided as a many-to-many type in the publish message and transmit the same. Also, as an example, in FIG. 15, the publisher NAN terminal is message 3, and information about a multi-to-many type service is included in a message transmitted to a subscriber NAN terminal in a process of setting up a NAN data link and a NAN data path. It can be transmitted by including.
  • the NAN terminals provide a many-to-many type service
  • a method of setting and using the address information of Table 5 as one common value may be considered.
  • the NAN terminals when the NAN terminals set the above-described address information as one value, it is necessary to share information about the address when other NAN terminals join the group.
  • the message when the publisher NAN terminal provides the address information, the message may be included in the message 3 of FIG. 15 and transmitted.
  • the subscriber NAN terminal when the subscriber NAN terminal provides address information, the subscriber NAN terminal may include the address information in the message 2 in FIG. 15.
  • the first NAN terminal 1710 and the second NAN terminal 1720 may be a group providing multi-to-many services as a multicast group.
  • the third NAN terminal 1730 joins the multicast group, the third NAN terminal 1730 is connected to the first NAN terminal 1710 or the second NAN terminal 1720 with the NAN data link and the NAN. You can set the data path.
  • the third NAN terminal 1730 establishes a NAN data link and a NAN data path with any NAN terminal, the above-described address information needs to be shared.
  • the third NAN terminal 1730 establishes a NAN data link and a NAN data path with the first NAN terminal 1710 or the second NAN terminal 1720, or GMK (Group Master Key or MMK) or You can also share a GTK (Group Temporary Key or MTK). That is, key information shared in the multicast group may be provided.
  • GMK Group Master Key or MMK
  • GTK Group Temporary Key or MTK
  • NAN terminals in a multicast group need to be able to communicate with each other. That is, even if the third NAN terminal 1730 performs setting of the NAN data link and the NAN data path with either the first NAN terminal 1710 or the second NAN terminal 1720, the third NAN terminal 1730 communicates with another NAN terminal. There is a need to do it.
  • the first NAN terminal 1710 and the second NAN terminal 1720 may first establish a NAN data link and a NAN data path. Thereafter, when the third NAN terminal 1730 sets up the NAN data link and the NAN data path with the first NAN terminal 1710, the first NAN terminal 1710 sends the second NAN to the third NAN terminal 1730. Information about the existence of the terminal 1720 may be provided. In this case, as an example, the first NAN terminal 1710 may provide presence information based on a unicast or multicast / broadcast scheme. In addition, the first NAN terminal 1710 needs to inform the second NAN terminal 1720 of the join of the third NAN terminal 1730.
  • the first NAN terminal 1710 may provide information about a join based on a unicast or multicast / broadcast scheme. Also, as an example, the first NAN terminal 1710 may provide information on whether the third NAN terminal 1730 is joined through an ACK message.
  • the third NAN terminal 1730 may transmit a notification message for the group join to the second NAN terminal 1720.
  • the notification message may be transmitted based on a unicast or multicast / broadcast scheme.
  • the terminals receiving the same in the multicast group may provide a response to the third NAN terminal 1730.
  • the NAN terminal joining the multicast group can communicate with other terminals in the group.
  • the entire notification message may be transmitted to the terminals in the multicast group.
  • the notification message may be transmitted to the neighboring terminal. In this case, by updating the MAC address and / or terminal information as the terminal list information in the group, and sharing the information with the terminal in the group, it is possible to share information about the join release.
  • the publisher may provide the other NAN terminals with information indicating the end-to-many service type through a publish message.
  • the publish message may further include information indicating whether the publisher is a source terminal that provides a service, but is not limited to the above-described embodiment.
  • the address information for Table 5 described above may be provided, and the method may be the same.
  • 18 is a diagram illustrating a method of performing data exchange between NAN terminals.
  • the first NAN terminal may receive a NAN data link request message for the first service from the second NAN terminal (S1810).
  • the first NAN terminal is a publisher NAN.
  • the terminal, and the second NAN terminal may be a subscriber NAN terminal.
  • the first NAN terminal may receive a request message for the NAN data link or the NAN data path from the second NAN terminal.
  • the first NAN terminal may transmit a NAN data link response message including information indicating the multicast service type to the second NAN terminal (S1830).
  • the multicast service type may be a first type in which one NAN terminal provides a service to a plurality of NAN terminals.
  • the first type may be the above-described end-to-many type.
  • the multicast service type may be a second type in which a plurality of NAN terminals provide a service to each other.
  • the second type may be the above-mentioned many-to-many type.
  • the first NAN terminal may provide information on whether the first type or the second type is type information for the first service to the second NAN terminal.
  • the first NAN terminal may transmit information on the multicast service type to the second NAN terminal through a NAN data link or a NAN data path response message.
  • the first NAN terminal may transmit information on the multicast service type to the second NAN terminal in the process of setting up the NAN data link, and the present invention is not limited to the above-described embodiment.
  • the first NAN terminal may transmit a NAN data link or NAN data path response message that does not include information on the multicast service type to the second NAN terminal.
  • a response message including information on a NAN data link or a NAN data path may be transmitted.
  • the first NAN terminal may establish a NAN data link based on the information exchanged with the second NAN terminal and perform data exchange through the NAN data path (S1850).
  • the first NAN terminal and the second NAN terminal may operate as a multicast group based on common address information.
  • the NAN terminal performing the NAN data link setup procedure with the new NAN terminal in the multicast group may provide information about the NAN terminal in the multicast group.
  • the NAN terminal performing the NAN data link setup procedure with the new NAN terminal in the multicast group may provide join information of the new NAN terminal to other NAN terminals in the multicast group, as described above.
  • 19 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, a NAN management 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 perform a search for a specific service using at least one of a publish message and a subscribe message.
  • the UE may perform a search for a specific service using at least one of a publish message and a subscribe message using a NAN interface, and is limited to the above-described embodiment. It doesn't work.
  • the processor 120 may receive a NAN data link request message for the first service from another NAN terminal using the reception module 110. Thereafter, the processor 120 may transmit the NAN data link response message to the second NAN terminal in response to the NAN data link request using the transmission module 130. Thereafter, the processor 120 may form a NAN data link with another NAN terminal and perform data exchange with another NAN terminal through a NAN data path.
  • the first service is a multicast service
  • information on the multicast service type may be provided to another NAN terminal.
  • the information on the multicast service type may be included in a NAN data link response message and transmitted to another NAN terminal.
  • the information on the multicast service type may be transmitted to another NAN terminal in the process of performing the NAN data link setup procedure, and is not limited to the above-described embodiment.
  • 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)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un procédé d'échange de données par un terminal NAN dans un système de communications sans fil. Le procédé d'échange de données par le terminal NAN peut comprendre les étapes consistant à : recevoir un message de demande de liaison de données NAN pour un premier service depuis un autre terminal NAN; transmettre un message de réponse de liaison de données NAN vers un second terminal NAN en réponse à la demande de liaison de données NAN; établir une liaison de données NAN avec l'autre terminal NAN; et échanger des données avec le second terminal NAN via un trajet de données NAN. Dans ce cas, lorsque le premier service est un service de multidiffusion, le terminal NAN peut fournir des informations associées à un type de service de multidiffusion à l'autre terminal NAN.
PCT/KR2017/000511 2016-01-14 2017-01-16 Procédé et appareil d'échange de données par un terminal nan dans un système de communications sans fil WO2017123068A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662278463P 2016-01-14 2016-01-14
US62/278,463 2016-01-14
US201662281203P 2016-01-21 2016-01-21
US62/281,203 2016-01-21

Publications (1)

Publication Number Publication Date
WO2017123068A1 true WO2017123068A1 (fr) 2017-07-20

Family

ID=59312200

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2017/000511 WO2017123068A1 (fr) 2016-01-14 2017-01-16 Procédé et appareil d'échange de données par un terminal nan dans un système de communications sans fil

Country Status (1)

Country Link
WO (1) WO2017123068A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109195103A (zh) * 2018-08-10 2019-01-11 Oppo广东移动通信有限公司 多媒体资源共享方法、相关设备以及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015152657A1 (fr) * 2014-04-02 2015-10-08 엘지전자 주식회사 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
WO2015157566A2 (fr) * 2014-04-11 2015-10-15 Qualcomm Incorporated Procédé et appareil de découverte de groupe sur un réseau de découverte de voisins (nan) optimisé gps
US20150350866A1 (en) * 2014-06-02 2015-12-03 Qualcomm Incorporated Peer discovery in neighbor awareness networking (nan) aided data link networks

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015152657A1 (fr) * 2014-04-02 2015-10-08 엘지전자 주식회사 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
WO2015157566A2 (fr) * 2014-04-11 2015-10-15 Qualcomm Incorporated Procédé et appareil de découverte de groupe sur un réseau de découverte de voisins (nan) optimisé gps
US20150350866A1 (en) * 2014-06-02 2015-12-03 Qualcomm Incorporated Peer discovery in neighbor awareness networking (nan) aided data link networks

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Enabling Always on Service Discovery: Wifi Neighbor Awareness Networking (NAN", IEEE WIRELESS COMMUNICATIONS, vol. 22, no. 2, 29 April 2015 (2015-04-29), pages 118 - 125, XP011579866, Retrieved from the Internet <URL:http://ieeexplore.ieee.org/document/7096294> *
WIFI ALLIANCE, NEIGHBOR AWARENESS NETWORKING TECHNICAL SPECIFICATION VERSION 1.0, 1 May 2015 (2015-05-01), Retrieved from the Internet <URL:http//www.wi-fi.org/download.php?file=/sites/default/files/private/NeighborAwarenessNetworkingTechnicalSpecification_v1_0_0.pdf> *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109195103A (zh) * 2018-08-10 2019-01-11 Oppo广东移动通信有限公司 多媒体资源共享方法、相关设备以及存储介质
CN109195103B (zh) * 2018-08-10 2020-12-15 Oppo广东移动通信有限公司 多媒体资源共享方法、相关设备以及存储介质

Similar Documents

Publication Publication Date Title
WO2016137224A1 (fr) Procédé et appareil pour transmettre des données dans un système de communication sans fil
WO2015126220A2 (fr) Procédé de participation à une grappe nan dans un système de communication sans fil, et dispositif associé
WO2016171527A1 (fr) Procédé et appareil pour effectuer une inscription auprès d&#39;un serveur de mandataire nan dans un système de communications sans fil
WO2016140466A1 (fr) Procédé de mise en oeuvre de radiomessagerie dans un système lan sans fil et dispositif utilisant ce procédé
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
WO2015126187A1 (fr) Procédé et dispositif pour partager une adresse de multidiffusion pour un dispositif nan dans un système de communication sans fil
WO2015170818A1 (fr) Procédé et appareil de réception d&#39;un signal au moyen d&#39;un dispositif nan dans un système de communication sans fil
WO2015072796A1 (fr) Procédé et appareil de modification d&#39;état d&#39;un terminal nan dans un système de communications sans fil
WO2015060651A1 (fr) Procédé et appareil de transmission de signal par un terminal 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
WO2017057988A1 (fr) Procédé de fusionnement d&#39;un terminal de nan dans une grappe de nan dans un système de communication sans fil, et dispositif
WO2015069041A1 (fr) Procédé et appareil permettant à un terminal nan d&#39;émettre/de recevoir un signal dans un système de communication sans fil
WO2016144088A1 (fr) Procédé et appareil permettant de transmettre des données à l&#39;aide de multiples canaux dans un système de communication sans fil
WO2016036140A1 (fr) Procédé et dispositif d&#39;ordonnancement de ressource sans fil pour nan
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
WO2013151312A1 (fr) Procédé et appareil d&#39;accès à un canal dans un système wlan
WO2011149285A2 (fr) Procédé et appareil d&#39;émission-réception de données dans système de réseau local (lan) sans fil
WO2016190721A1 (fr) Procédé et appareil permettant de fournir un service de mandataire par l&#39;intermédiaire d&#39;un serveur mandataire nan dans un système de communications sans fil
WO2013141669A1 (fr) Procédé et appareil d&#39;accès à un canal dans un système lan sans fil
WO2013122398A1 (fr) Procédé et appareil pour le balayage basé sur le filtrage dans un système wlan
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
WO2015119454A1 (fr) Procédé et dispositif pour modifier l&#39;état d&#39;un terminal de réseautage sensible au voisinage (nan) dans un système de communication sans fil
WO2017065561A1 (fr) Procédé et appareil de transmission de trame par un terminal nan dans un système de communications sans fil
WO2015119440A1 (fr) Procédé et dispositif pour émettre et recevoir des signaux au moyen d&#39;un terminal nan d&#39;un système de communication sans fil

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

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

Country of ref document: EP

Kind code of ref document: A1