WO2014088378A1 - 무선 통신 시스템에서 세션 초기화 방법 및 장치 - Google Patents
무선 통신 시스템에서 세션 초기화 방법 및 장치 Download PDFInfo
- Publication number
- WO2014088378A1 WO2014088378A1 PCT/KR2013/011349 KR2013011349W WO2014088378A1 WO 2014088378 A1 WO2014088378 A1 WO 2014088378A1 KR 2013011349 W KR2013011349 W KR 2013011349W WO 2014088378 A1 WO2014088378 A1 WO 2014088378A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- session
- url
- asp
- wfd
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/14—Direct-mode setup
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/005—Discovery of network devices, e.g. terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
- H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W92/00—Interfaces specially adapted for wireless communication networks
- H04W92/16—Interfaces between hierarchically similar devices
- H04W92/18—Interfaces between hierarchically similar devices between terminal devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
Definitions
- the following description relates to a wireless communication system, and more particularly, to a method and apparatus for initializing a session related to Wi-Fi Direct.
- 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
- Wi-Fi Direct Wi-Fi Direct
- Wi-Fi P2P peer
- Wi-Fi Direct devices can be connected without a complicated configuration process, and in order to provide various services to a user, they can support an operation of exchanging data with each other at a communication speed of a general WLAN system.
- Wi-Fi Direct Service WFDS
- ASP application service platform
- the present invention provides a method for initializing a session for a send service in Wi-Fi Direct.
- a first technical aspect of the present invention is a method for initiating a Send session with a second device by a first device supporting Wi-Fi Direct service, the method comprising: establishing an Application Service Platform (ASP) session; And initiating a Send session using a Uniform Resource Locator (URL) related to a device description, wherein the URL associated with the device description is obtained prior to completing the ASP session establishment. Session initialization method.
- ASP Application Service Platform
- URL Uniform Resource Locator
- a second technical aspect of the present invention is a first device for supporting a Wi-Fi Direct service, comprising: a receiving module; And a processor, wherein the processor establishes an Application Service Platform (ASP) session, initializes a Send session using a Uniform Resource Locator (URL) related to a device description, and specifies the device specification.
- ASP Application Service Platform
- the URL associated with is the first device obtained in the ASP session establishment step.
- the first and second technical aspects of the present invention may include the following.
- the URL related to the device specification may be included in an Advertisement () method transmitted by the service layer of the second device.
- the URL related to the device specification included in the advertisement method may be delivered to the first device through one or more of a probe request procedure or a service discovery procedure.
- a discovery procedure related to Universal Plug and Play may be omitted.
- the parameter value related to the service information request transmitted by the service layer of the first device may be set to a value other than NULL.
- the parameter related to the service information request may be included in a SeekService method.
- the URL related to the device specification may be included in a ConfirmService () method transmitted by the service layer of the second device.
- the URL related to the device specification included in the confirmation service method may be delivered to the first device through a provision discovery procedure or a group formation procedure.
- the URL related to the device specification may be included in a session ready method (SessionReady () method) transmitted by the service layer of the second device.
- SessionReady () method SessionReady
- the device specification includes device information, variables, OS type / version, UPnP version, URL related to the service specification, URL for control, URL for eventing, and presentation for presentation. It may include one or more of URLs for presenting.
- the first terminal may be able to perform a close session (CloseSession ()) even in the canceled state (canceled state).
- the discovery process according to the UPnP procedure can be omitted, so that session initialization for the transport service can be efficiently performed.
- FIG. 1 is a diagram illustrating an exemplary structure of an IEEE 802.11 system.
- FIG. 2 is a diagram illustrating a Wi-Fi Direct network.
- FIG. 3 is a diagram illustrating a process of configuring a Wi-Fi Direct network.
- FIG. 4 is a diagram illustrating a neighbor discovery process.
- 5 is a view for explaining a new aspect of the Wi-Fi Direct network.
- FIG. 6 is a view for explaining a method for establishing a link for Wi-Fi Direct communication.
- FIG. 7 is a diagram for describing a method of associating with a communication group performing Wi-Fi Direct.
- FIG. 8 is a view for explaining a method for establishing a link for Wi-Fi Direct communication.
- FIG. 9 is a view for explaining a method for setting a link participating in a Wi-Fi Direct communication group.
- FIG. 10 is a view for explaining the WFDS framework components.
- 11 is a diagram for explaining a WFDS operation.
- FIG. 12 is a diagram for explaining an ASP session setup sequence in WFDS.
- FIG. 13 is a diagram for describing a send service in WFDS.
- FIG. 14 illustrates a transport session initialization according to an embodiment of the present invention.
- 15 to 16 are diagrams for explaining the end of a transmission session according to an embodiment of the present invention.
- 17 is a state diagram related to the termination of a transport session according to an embodiment of the present invention.
- FIG. 18 is a block diagram illustrating a configuration of a wireless device according to an embodiment of the present invention.
- each component or feature may be considered to be optional unless otherwise stated.
- Each component or feature may be embodied in a form that is not combined with other components or features.
- some components and / or features may be combined to form an embodiment of the present invention.
- the order of the operations described in the embodiments of the present invention may be changed. Some components or features of one embodiment may be included in another embodiment or may be replaced with corresponding components or features of another embodiment.
- Embodiments of the present invention may be supported by standard documents disclosed in at least one of the wireless access systems IEEE 802 system, 3GPP system, 3GPP LTE and LTE-A (LTE-Advanced) system and 3GPP2 system. That is, steps or parts which are not described to clearly reveal the technical spirit of the present invention among the embodiments of the present invention may be supported by the above documents. In addition, all terms disclosed in the present document can be described by the above standard document.
- CDMA code division multiple access
- FDMA frequency division multiple access
- TDMA time division multiple access
- OFDMA orthogonal frequency division multiple access
- SC-FDMA single carrier frequency division multiple access
- CDMA may be implemented with a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000.
- TDMA may be implemented with wireless technologies such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE).
- GSM Global System for Mobile communications
- GPRS General Packet Radio Service
- EDGE Enhanced Data Rates for GSM Evolution
- OFDMA may be implemented in a wireless technology such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA).
- Wi-Fi IEEE 802.11
- WiMAX IEEE 802.16
- E-UTRA Evolved UTRA
- 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 LAN. 1 exemplarily shows that there are two BSSs (BSS1 and BSS2) and two STAs are included 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 LAN 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 LAN may not be configured in advance, but may be configured when a LAN is required, which 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).
- DSM distribution system medium
- 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.
- the plurality of media logically different, the flexibility of the IEEE 802.11 LAN structure (DS structure or other network structure) can be described. That is, the IEEE 802.11 LAN structure can be implemented in various ways, the corresponding LAN 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 means 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.
- IEEE 802.11a and b use an unlicensed band at 2.4. GHz or 5 GHz, IEEE 802.11b provides a transmission rate of 11 Mbps, and IEEE 802.11a provides a transmission rate of 54 Mbps.
- IEEE 802.11g applies Orthogonal Frequency Division Multiplexing (OFDM) at 2.4 GHz to provide a transmission rate of 54 Mbps.
- IEEE 802.11n provides a transmission rate of 300 Mbps by applying multiple input multiple output OFDM (MIMO-OFDM). IEEE 802.11n supports a channel bandwidth of up to 40 MHz, in which case it provides a transmission rate of 600 Mbps.
- OFDM Orthogonal Frequency Division Multiplexing
- the DLS (Direct Link Setup) related protocol in a wireless LAN environment according to IEEE 802.11e is based on QBSS (Quality BSS) in which a Basic Service Set (BSS) supports Quality of Service (QoS).
- QBSS Quality BSS
- AP non-AP
- QAPs QAPs
- WLAN environment for example, WLAN environment according to IEEE 802.11a / b / g
- the AP supports QoS even if the Non-AP STA is a QSTA (Quality STA) supporting QoS.
- Most legacy APs do not.
- the QSTA there is a limit that can not use the DLS service.
- Tunneled Direct Link Setup is a newly proposed wireless communication protocol to overcome this limitation.
- TDLS does not support QoS
- QSTAs can set up a direct link even in a wireless LAN environment such as IEEE 802.11a / b / g, which is currently commercially available. To do that. Therefore, TDLS prescribes various procedures for enabling QSTAs to establish a direct link even in a BSS managed by a legacy AP.
- a wireless network supporting such a TDLS is called a TDLS wireless network.
- WLANs mainly dealt with the operation of an infrastructure BSS in which a wireless access point (AP) functions as a hub.
- the AP is responsible for supporting physical layer support for wireless / wired connection, routing for devices on the network, and providing services for adding / removing devices to and from the network.
- the devices in the network are connected through the AP, not directly with each other.
- Wi-Fi Direct The enactment of the Wi-Fi Direct standard has been discussed as a technology to support direct connections between devices.
- Wi-Fi Direct networks allow Device to Device (D2D) (or Peer-to-Peer) communication with each other, even if Wi-Fi devices do not join home, office, and hotspot networks. It is proposed by the Wi-Fi Alliance as a workable network.
- Wi-Fi Direct-based communication is referred to as WFD D2D communication (simply, D2D communication) or WFD P2P communication (simply, P2P communication).
- WFD D2D communication implies, D2D communication
- WFD P2P communication implies, P2P communication
- a WFD P2P performing apparatus is referred to as a WFD P2P apparatus, simply a P2P apparatus.
- the WFD network 200 may include at least one Wi-Fi device including a first WFD device 202 and a second WFD device 204.
- WFD devices include devices that support Wi-Fi, such as display devices, printers, digital cameras, projectors, and smartphones.
- the WFD device includes a Non-AP STA and an AP STA.
- the first WFD device 202 is a mobile phone and the second WFD device 204 is a display device. WFD devices in the WFD network may be directly connected to each other.
- a signal transmission path between two WFD devices is directly connected between the corresponding WFD devices without passing through a third device (for example, an AP) or an existing network (for example, accessing a WLAN through an AP). It may mean a case where it is set.
- the signal transmission path directly established between the two WFD devices may be limited to the data transmission path.
- P2P communication may refer to a case where a plurality of non-STAs transmit data (eg, voice / video / text information) without passing through the AP.
- Signal transmission paths for control information may be used for WFD devices (eg, Non-AP STA-to-Non-AP STA, Non-AP STA-).
- WFD devices eg, Non-AP STA-to-Non-AP STA, Non-AP STA-.
- Direct-to-AP or between two WFD devices (e.g., Non-AP STA-to-Non-AP STA) via an AP, or AP and corresponding WFD device (e.g., AP- To-Non-AP STA # 1, AP-to-Non-AP STA # 2).
- FIG. 3 is a view for explaining a process of configuring a WFD network.
- the WFD network configuration process can be roughly divided into two processes.
- the first process is a neighbor discovery process (Neighbor Discovery, ND, procedure) (S302a), and the second process is a P2P link establishment and communication process (S304).
- a neighbor discovery process a WFD device (eg, 202 of FIG. 2) finds another neighboring WFD device (eg, 204 of FIG. 2) within its (wireless) coverage and associates with that WFD device. ),
- information necessary for pre-association can be obtained.
- pre-association may mean a second layer pre-association in a wireless protocol.
- the information necessary for pre-association may include, for example, identification information about a neighboring WFD device.
- the neighbor discovery process may be performed for each available wireless channel (S302b). Thereafter, the WFD device 202 may perform a process for establishing / communicating a WFD P2P link with another WFD device 204. For example, after the WFD device 202 is associated with the peripheral WFD device 204, the WFD device 204 may determine whether the WFD device 204 does not satisfy the service requirement of the user. To this end, the WFD device 202 may search for the WFD device 204 after the second layer pre-association with the peripheral WFD device 204. If the WFD device 204 does not satisfy the service requirement of the user, the WFD device 202 disconnects the second layer association established for the WFD device 204 and establishes a second layer association with another WFD device. Can be set. On the other hand, when the WFD device 204 satisfies the service requirements of the user, the two WFD devices 202 and 204 can transmit and receive signals through the P2P link.
- FIG. 4 is a diagram illustrating a neighbor discovery process.
- the example of FIG. 4 may be understood as the operation between the WFD device 202 and the WFD device 204 in FIG. 3.
- the neighbor discovery process of FIG. 3 may be initiated by an instruction of a station management entity (SME) / application / user / vendor (S410), a scan phase (S412), and a discovery step ( find phase (S414-S416).
- the scan step S412 includes an operation of scanning for all available wireless channels according to the 802.11 scheme. This allows the P2P device to identify the best operating channel.
- the search steps S414-S416 include a listen mode S414 and a search mode S416, and the P2P device alternately repeats the listening mode S414 and the search mode S416.
- the P2P devices 202 and 204 perform an active search using a probe request frame in the search mode (S416), and the search range is set to channels 1, 6, and 11 (eg, 2412) for quick search. It can be limited to a social channel (2437, 2462MHz).
- the P2P devices 202 and 204 select only one of three social channels in the listening mode S414 and maintain the received state.
- the P2P device eg, 204
- the listening mode (S414) time may be given randomly (eg, 100, 200, 300 Time Units (TU)).
- the P2P device may repeat the search mode and the receive mode repeatedly and reach each other's common channel.
- the P2P device may discover / exchange the device type, manufacturer or friendly device name using the probe request frame and the probe response frame to selectively bind to the P2P device after discovering another P2P device.
- the P2P device eg, 202
- the P2P device may notify the SME / application / user / vendor of the P2P device discovery (S418).
- P2P is mainly used for semi-static communication such as remote printing, photo sharing and the like.
- wireless chat e.g., wireless devices subscribed to Social Network Service (NSS) recognizes and transmits information to wireless devices in the vicinity based on location-based services
- location-based advertising e.g., location-based advertising
- location- P2P is expected to be actively used for news broadcasting and game linkage between wireless devices.
- P2P applications are referred to as novel P2P applications.
- FIG. 5 is a diagram for explaining a new aspect of the WFD network.
- 5 may be understood as a WFD network aspect when a new P2P application (eg, social chat, location-based service provision, game linkage, etc.) is applied.
- a new P2P application eg, social chat, location-based service provision, game linkage, etc.
- a plurality of P2P devices 502a-502d perform P2P communication 510, and the P2P device (s) constituting the WFD network are changed at any time by the movement of the P2P device.
- the WFD network itself can be newly created or destroyed in dynamic / short time.
- a feature of the new P2P application portion is that in a dense network environment, P2P communication can be made and terminated dynamically and shortly between a large number of P2P devices.
- FIG. 6 is a view for explaining a method for establishing a link for WFD communication.
- the first STA 610 (hereinafter referred to as A) is operating as a group owner in the existing WFD communication. If A 610 finds a second STA 620 (hereinafter referred to as B) that is not in WFD communication, which is a new WFD communication object, during communication with the group client 630 of the existing WFD communication, A ( 610 attempts to establish a link with B 620.
- the new WFD communication is the WFD communication between the A 610 and the B 620, and A is the group owner, so that communication setting may be performed separately from the communication of the existing group client 630.
- a WFD link can be established.
- a 610 invites B 620 to an existing WFD communication group. Due to WFD communication characteristics, A 610 and B 620, A 610 and an existing group client exist. WFD communication between the 630 is possible, but WFD communication between the B 620 and the existing group client 630 may not be supported. If the Intra-BSS option is enabled (or set to On) among the P2P group capabilities of Wi-Fi Direct, WFD direct communication between the B 620 and the existing group client 630 (ie, Wi-Fi Direct). Direct communication between clients within the BSS) may be possible.
- FIG. 7 is a diagram for explaining a method of associating with a communication group performing WFD.
- a first STA 710 (hereinafter referred to as A) is in communication with the group client 730 as a group owner, and a second STA 720 (hereinafter referred to as B) is a group client. 740 is communicating as a group owner.
- the A 710 may terminate the existing WFD communication and may join the WFD communication group to which the B 720 belongs.
- a 710 becomes a group client of B since B 720 is the group owner.
- a 710 preferably terminates existing WFD communication before requesting association with B 720.
- FIG. 8 is a diagram for explaining a method of establishing a link for WFD communication.
- the second STA 820 (hereinafter referred to as B) is operating as a group owner in the existing WFD communication.
- the first STA (810, hereinafter referred to as A) which is not in the WFD communication, which has discovered the B 820, is new to the B 820.
- Attempt to establish a link for WFD communication if B 820 accepts the link setup, a new WFD communication link between A 810 and B 820 is established, and A 810 operates as a client of the WFD group of existing B 820. do.
- the A 810 joins the WFD communication group of the B 820.
- a 810 may communicate only with the group owner B 820 in WFD, and WFD communication between A 810 and the client 830 of the existing WFD communication may not be supported. If the Intra-BSS option is enabled (or set to On) among the P2P group capabilities of Wi-Fi Direct, the WFD direct communication between the A 810 and the client 830 of the existing WFD communication (ie, Wi-Fi Direct) is performed. Direct communication between clients within Fi Direct BSS) may be enabled.
- FIG. 9 is a diagram for explaining a method of establishing a link participating in a WFD communication group.
- the first STA 910 (hereinafter referred to as A) is in WFD communication with the group owner 930 as a group client.
- a 910 terminates the link with the group owner 930 ( terminate and join the BF's WFD.
- Wi-Fi Direct Service (WFDS)
- Wi-Fi Direct is a network connectivity standard that defines the behavior of the link layer. Since no standard is defined for an application that operates on the upper layer of the link configured by Wi-Fi Direct, it was difficult to support compatibility when devices that support Wi-Fi Direct run applications after they are connected to each other. To address this problem, standardization of the behavior of higher layer applications called Wi-Fi Direct Service (WFDS) is under discussion at the Wi-Fi Alliance (WFA).
- WFDS Wi-Fi Direct Service
- FIG. 10 is a view for explaining the WFDS framework components.
- the Wi-Fi Direct layer of FIG. 10 means a MAC layer defined by the Wi-Fi Direct standard.
- the Wi-Fi Direct layer can be configured as software that is compatible with the Wi-Fi Direct standard.
- a wireless connection may be configured by a physical layer (not shown) compatible with the Wi-Fi PHY.
- a platform called Application Service Platform (ASP) is defined above the Wi-Fi Direct layer.
- ASP is a common shared platform and performs session management, command processing of services, and inter-ASP control and security functions between the upper application layer and the lower Wi-Fi Direct layer. do.
- the service layer contains use case specific services.
- WFA defines four basic services: Send, Play, Display, and Print.
- the Enable (API) Application Program Interface (API) is defined to enable the ASP common platform to support third party applications in addition to basic services.
- a service defined by Send, Play, Display, Print, or a third party application is illustrated, but the scope of application of the present invention is not limited thereto.
- the term "service” refers to Wi-Fi Serial Bus (WSB), Wi-Fi docking (Wi-Fi), in addition to the services defined by the Send, Play, Display, Print, or third-party applications.
- WB Wi-Fi Serial Bus
- Wi-Fi docking Wi-Fi
- NAN Neighbor Awareness Networking
- Send refers to services and applications that can perform file transfers between two WFDS devices.
- Play refers to services and applications that share or stream audio / video (A / V), photos, and music based on the Digital Living Network Alliance (DLNA) between two WFDS devices.
- Print refers to services and applications that enable document and photo output between a printer and a device having content such as documents and photos.
- Display refers to services and applications that enable screen sharing between WFA's Miracast sources and sinks.
- the application layer may provide a user interface (UI), and expresses information in a form recognizable by a person, and delivers user input to a lower layer.
- UI user interface
- 11 is a diagram for explaining a WFDS operation.
- An ASP is a logical entity that implements common functions required by services. These functions may include device discovery, service discovery, ASP-session management, connection topology management, security, and the like.
- An ASP-session is a logical link between the ASP of device A and the ASP of device B.
- Peer-to-peer (P2P) connectivity between peer devices is required to initiate an ASP-session.
- An ASP can set up a plurality of ASP-sessions between two devices. Each ASP-session can be identified by a session identifier assigned by the ASP requesting the ASP-session.
- a service is a logical entity that provides usage-specific functions to other services or applications using ASP.
- a service of one device may communicate with a corresponding service of one or more other devices using a service-specific protocol (which may be defined by a service standard and an ASP protocol).
- the interface between the ASP and the service is defined by methods and events.
- the method represents an operation initiated by a service, and a parameter (or field) of the method may include information on an operation to be performed.
- Event provides information from ASP to service.
- the ASPs on each device create an ASP-session between the devices dedicated to service X. If the user then wishes to use service Y, a new ASP-session for that service is established.
- FIG. 12 is a diagram for explaining an ASP session setup sequence in WFDS.
- some of the devices can act as service advertisers and other devices can act as service seekers.
- the service seeker discovers the service advertiser (s) and, if it finds the desired service, the service seeker may request a connection with the service advertiser.
- the device A plays a role of a service advertiser and the device B plays a role of a service seeker.
- FIG. 12 A brief description of the ASP session setup operation of FIG. 12 illustrates a process in which a specific service of a WFDS device discovers another WFDS device and service, requests a service, establishes a Wi-Fi Direct connection, and operates an application. Indicates.
- device A may advertise its service and wait for another device to find the service.
- the ASP of the device A may respond to another device based on the information included in the Advertisement () method provided from the service layer.
- Device B is the device to find and start the service.
- the device B performs a process of searching for a device supporting a service by a request of a higher application or a user.
- the service layer of device B may include information necessary for the SeekService () method and pass it to the ASP.
- the ASP of the device B may transmit a probe request frame to another device.
- a request is made by including a service name of a service to be searched for or supported by the probe request frame in the form of a hash.
- the device A may try hash matching and transmit a probe response frame to the device B when supporting a service corresponding to the hash value.
- the probe response frame may include a service name, an advertisement ID value, and the like.
- the process of exchanging and receiving a probe request / response frame may be referred to as a device discovery process in which devices A and B support WFDS, and what services each device supports.
- devices A and B may exchange information on specific details of a specific service through a P2P service discovery process.
- information such as a service name (a plurality of service names when searching for support of a plurality of services) and a service information request may be transmitted from the device B to the device A through a service discovery request message.
- the device A may inform the device B that the corresponding service can be provided if the matching is performed by performing service information matching.
- the service discovery response message may include information such as a service name, advertisement ID, service status, and the like.
- the service status information is information indicating whether a service requested from a remote device is available on the service advertiser side.
- This service discovery process may be performed using the Generic Advertisement Protocol (GAS) defined in the IEEE 802.11u system.
- GAS Generic Advertisement Protocol
- the ASP of the device B When the ASP of the device B completes the operation requested by the SeekService () method requested by the service layer, the ASP may notify the application and the user of the result (ie, SearchResult) through the service.
- the result ie, SearchResult
- a group of Wi-Fi Direct is not formed, and when a user selects a service and the service performs a session connection (that is, ConnectSession), P2P group formation is performed. At this time, session information and connection capability information are exchanged through a provision discovery request and a provision discovery response.
- a session connection that is, ConnectSession
- the session information is hint information indicating rough information of a service requested by a device requesting a service.
- the session information is, for example, when requesting a file transfer service, information about the number, size, etc. of a file, so that the other party can determine whether to accept or reject the service request.
- the connection capability may be used as information for creating a group during GO negotiation (Group Owner negotiation) and P2P invitation.
- the ASP of device A When device B delivers a provision discovery request message to device A, the ASP of device A sends a session request including service information to the service layer, and the service layer delivers the service information to the application / user. . If the application / user decides to accept the session based on the session information, ConfirmService () is passed to the ASP through the service layer.
- the ASP of device A delivers a provision discovery response message to device B, whose status information may be set to deferred. This is to indicate that the service is not immediately accepted and is waiting for user input. Accordingly, the ASP of device B may inform that the service request has been delayed while delivering a ConectStatus event to the service layer.
- a follow-on provisioning discovery process may be performed. That is, device A may deliver a provision discovery request message to device B. This can be called a follow-on provisioning discovery process.
- This message may include service information along with information indicating that the status of the service is successful. Accordingly, the ASP of the device B may inform that the service request has been accepted while delivering a ConectStatus event to the service layer.
- the ASP of device B may deliver a provision discovery response message to device A, which may include connection capability information.
- a P2P group is created through GO negotiation or an invitation process, and a second layer (L2) connection and an IP (Internet Protocol) connection are performed.
- L2 second layer
- IP Internet Protocol
- devices A and B deliver a REQUEST_SESSION message requesting a session through an ASP coordination protocol.
- the REQUEST_SESSION message may include an advertisement ID, a MAC address (mac_addr), a session identifier (session ID), and the like.
- the MAC address refers to the address of the P2P device.
- device A may deliver an ACK message to device B.
- the device A Upon receiving the device A, the device A notifies the higher service / application that the session is connected, and the service layer can request port information for the session, and bind the session and the port. Accordingly, the ASP can open the corresponding port (ASP can open the port inside the firewall) and inform the service layer that the port is ready. The service layer may inform the ASP that the session is ready (SessionReady ()).
- the ASP of the device A sends the ADDED_SESSION message to the counterpart device.
- the ADDED_SESSION message may include a session ID and MAC address information. Accordingly, a service may be uniquely identified.
- the ASP of the device B Upon receiving the ADDED_SESSION message, the ASP of the device B notifies the service layer of the session connection and informs the service layer that the port is ready (PortReady ()) through a port request, port binding, and the like. ASP can open ports in a firewall.
- an application socket connection may be announced between the service layer of device A and device B. Since the ASP session is established by the above-described procedures, individual service specific operations (eg, send, play, etc.) may be performed.
- FIG. 13 (a) shows the configuration of a send service among services of Wi-Fi Direct.
- the Wi-Fi Direct Send service consists of an L2 connection (castle), a control plane, and a data plane.
- the transport service uses the interface provided by the ASP to find a device that will support the transport service.
- the control plane is used to establish and manage the Wi-Fi Direct transfer session, and the data plane is used to provide the actual file transfer path.
- Figure 13 (b) shows a functional structure for a Wi-Fi direct transmission service.
- the send transmitter uses a UPnP enabled control point for the Wi-Fi Direct transmission session. "Transport" is used to send the actual file from the transport sender to the send receiver.
- the Wi-Fi Direct transfer service uses the UPnP protocol.
- the session is controlled using the UPnP protocol and actual data is transmitted.
- the UPnP control point (which may be a terminal / device / device or service seeker) that wants to use the service may be URL information related to a device description through a discovery procedure defined in UPnP (Uniform Resource Locator (URL) for device description). ), IP, etc., and initiate a transport session.
- URL Uniform Resource Locator
- the device description (device description, device information, variable, OS type, version, UPnP version, URL for service description, URL for control, URL for eventing) using information such as URL information, IP, port, etc. related to the device specification.
- a URL for presenting, etc., information about a command to perform file transfer, a variable / declaration related thereto, and the like may be obtained using a URL related to a service specification.
- the transport session is initialized after the ASP session is established, the device which intends to use the service acquires IP information when the ASP session is established.
- the UPnP discovery procedure can be omitted, thereby increasing the procedural efficiency.
- a URL related to the device specification is acquired in advance for use in an HTTP GET request. Therefore, the present invention proposes to omit the UPnP discovery procedure by acquiring the URL related to the device specification in the step before the completion of the ASP session establishment.
- the URL related to the device specification may be included in the service_informaiton of the advertising service.
- the URL related to the device specification may be included in the Advertisement () method transmitted by the service layer of the service advertiser.
- the URL related to the device specification included in the advertisement method may be delivered to the service seeker through one or more of a probe request procedure or a service discovery procedure.
- the discovery procedure related to Universal Plug and Play may be omitted when a send session is initiated. If the value of the parameter (service_information_request parameter) related to the service information request of the SeekService method is set to NULL, the service discovery process may be skipped and the service seeker may not obtain a URL related to the device specification. To this end, together with the above-described configuration, the parameter value related to the service information request may be set to a value other than NULL.
- the URL related to the device specification may be included in the ConfirmService () method transmitted by the service layer.
- the URL related to the device specification included in the confirmation service method may be delivered to the service seeker through a provision discovery procedure or a group formation procedure.
- the provision discovery request may include a Service Instance attribute as shown in Table 1 below.
- This field should include the file name. For the single file transfer case, this field represent the name of the file to be transferred during the Send Session. When sending the multiple files, this field includes any one of file name as a representative for all other files. Which file to select to represent all other files depends on the implementation. For eg, file which has biggest size. In case user sending multiple files in the container, then this field should include container name. The receiver device should interpret the text as UTF-8 string to be displayed on the user interface.
- the URL related to the device specification may be included in the SessionReady () method.
- the URL information in the session ready event sent from the service layer of the service advertiser to the ASP layer include it in the ADDED_SESSION command, and send it to the service seeker, and include this information in the ASP event to notify SendTransmitter's FileTransferservice. can do.
- the above descriptions have been mainly focused on the URL related to the device specification, the above description may also be applied to the URL related to the service specification.
- the above methods may be applied to URL for control or URL for eventing.
- the FTS server may simultaneously inform all of the URL information about the service description / control / eventing by using the above proposed method or in a combination of one or both.
- the send transmitter is a service seeker in the foregoing description
- the send receiver is a service advertiser
- an ASP session established between the transmit sender and the transmit receiver is described above. It may be an ASP session established by an embodiment of.
- CreateSession () may include a send transmitter device identity and file meta information.
- file meta information may be included in a mandatory. This is because the receiver needs information on the number of files to be transmitted and sent to the sender to cancel or modify the session.
- the sending sender or sending receiving end may terminate the session or send the end request.
- the transmitting receiving end may terminate the session.
- the transmitting sender may perform a session termination request. If there is a file to be sent at the time of cancellation, the sending and receiving end may perform automatic session termination after all files have been transmitted. Alternatively, the transmitting sender may immediately make a termination request.
- the transmitting and receiving side may be set to notify the transmitting and transmitting side as an event even when any variable changes.
- Fig. 15 (a) shows the termination of the Wi-Fi Direct transmission session by the transmission sender. If all files are transmitted, the transmitting sender may perform a CloseSession () action.
- the transmission receiver receives CloseSession (), it checks the state of the session. If the state is "Ready_For_Transport", the session is terminated and the transmission transmission side returns a termination success. If the status is "Transporting", the transmitting and receiving party returns an error code 704 of "Transport in progress”. After the session ends, the FileTransfer service hosted on the sender and receiver generates an event that sets the TransportStatus status variable to SessionID: SessionClosed.
- Figure 15 (b) shows the end of the Wi-Fi Direct transmission session by the transmission receiving side. If the transmitting and receiving side wants to cancel all the transmitting sessions or all the files transmitted to the transmitting and receiving side, the transmitting and receiving side may terminate the session.
- the FileTransfer service hosted at the sending receiver When the sending receiver requests to terminate the session, the FileTransfer service hosted at the sending receiver generates an event that sets the TransportStatus status variable to SessionID: SessionClosed.
- SessionClosed When the sending sender receives the SessionClosed event, it notifies the user of the end of the session and ends the session.
- Fig. 15C shows the cancellation of the ongoing session by the transmitting and receiving side
- Fig. 15D shows the cancellation of the ongoing session by the transmitting and receiving side.
- Fig. 16A shows the suspension and resumption of ongoing transfers by the transmitting sender.
- the suspension and resumption of transmission can be notified to the user.
- FIG. 16 (b) shows the suspension and resumption of ongoing transfers by the transmitting and receiving side
- FIG. 16 (c) shows the modification of the Wi-Fi Direct transmission session.
- 17 is a state diagram of a file transfer session according to an embodiment of the present invention.
- the CancelSession () action when the CancelSession () action is performed in the Ready_For_Transport state, it is not necessary to perform CancelSession () after the transition to the Canceled state. Therefore, the CloseSession () action may be performed even in the Ready_For_Transport state to immediately transition to the End state. Alternatively, the CancelSession () action is not executed in the Ready_For_Transport state.
- the TransferPaused state transitions to the Canceled state.
- the CancelSession () action may be performed by a request of a transmitting sender / receiver or even without a request.
- it executes the CloseSession () action to go to the SessionClosed state.
- the CancelSession () action may be performed by a request of a transmitting sender / receiver or even without a request.
- the CancelSession () action may be performed by a request of a transmitting sender / receiver or even without a request.
- Table 2 below describes each state illustrated in FIG. 17 and shows state transitions.
- READY_FOR_TRANSPORT This state represents the FileTransfer service is ready to receive the file from the Transmitter device.
- the service receives the file data via HTTP PUT or any other out of band mechanism, then the service changes the state to the TRANSPORTING In case of any internal error conditions, the service may change the state to ERROR When file is completely received by the service then, the service may change the state from FINISHED to READY_FOR_TRANSPORT.
- TRANSPORTING This state of the FileTransfer service represents the file transfer is ongoing, and the service is receiving the file data.
- ongoing File Transfer service receives the CancelTransferaction, then the service stop receiving file data and changes the state to CANCELLED
- the service receives the PausedTransfer action, it stop receiving the file data till the transfer is resumed using ResumeTransfer action.
- FileTransfer service changes the state to TRANSFER PAUSEDWhen the file is completely received from the Transmitter device, then the service change the state to FINISHED When the previously paused transfer is resumed by the Transmitter or by the Receiver it changes the state from TRANSFER PAUSED to TRANSPORTING SessionPaused: [noofbytes] This is the transient state to represent the ongoing file transfer is paused by the Transmitter device or the Receiver device.
- FIG. 18 is a block diagram illustrating a configuration of a wireless device according to an embodiment of the present invention.
- the wireless device 10 may include a processor 11, a memory 12, and a transceiver 13.
- the transceiver 13 may transmit / receive a radio signal, for example, may implement a physical layer according to the IEEE 802 system.
- the processor 11 may be electrically connected to the transceiver 13 to implement a physical layer and / or a MAC layer according to the IEEE 802 system.
- the processor 11 may be configured to perform one or more operations among an application, a service, and an ASP layer according to various embodiments of the present invention described above.
- a module for implementing the operation of the wireless device according to various embodiments of the present invention described above may be stored in the memory 12 and executed by the processor 11.
- the memory 12 may be included in the processor 11 or installed outside the processor 11 and connected to the processor 11 by a known means.
- the wireless device 10 of FIG. 18 may be configured to support Wi-Fi Direct service and perform session setup.
- the processor 11 includes a provision discovery process between the first wireless device and the second wireless device to create a session for a first service. It may be configured to set up a peer-to-peer connection between second wireless devices.
- the processor 11 may send a session request (REQUEST_SESSION) message from the first wireless device to the second wireless device (or the wireless device 10 may cause the second wireless device to generate a session for a second service). May be configured to control the transceiver) to receive a session request (REQUEST_SESSION) message. Session information for the second service may be included in the session request message.
- 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.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Mobile Radio Communication Systems (AREA)
- Computer And Data Communications (AREA)
- Telephone Function (AREA)
Abstract
Description
Field | Size (octets) | Value (Hexadecimal) | Description |
Number Of Files | 2 | Variable | No of files during the session |
Total Size Of the Files | 4 | Variable | Total size in KBs |
File or Container Name | Variable | Variable | This field should include the file name. For the single file transfer case, this field represent the name of the file to be transferred during the Send Session. When sending the multiple files, this field includes any one of file name as a representative for all other files. Which file to select to represent all other files depends on the implementation. For e.g., file which has biggest size. In case user sending multiple files in the container, then this field should include container name. The receiver device should interpret the text as UTF-8 string to be displayed on the user interface. |
State | Description | Transition From | Transition To |
Start | This is an initialization phase for the File Transfer service | In Start state when the FileTransfer service receives the CreateSession action to create the new file transfer session, the service can automatically accept the incoming session and change to READY_FOR_TRANSPORT state. Or in case of manual acceptance it transits to intermidiate state “WAITING_FOR_USER_INPUT” | |
WAITING_FOR_USER_INPUT | This is an intermediate state, in which FileTransfer service waits for the user input for the incoming file transfer session request. | When user accept the incoming file transfer, the FileTransfer state change to READY_FOR_TRANSPORT state When user did not respond to the incoming file transfer, and on internal time out event then the FileTransfer state change to ERROR state. | |
READY_FOR_TRANSPORT | This state represents the FileTransfer service is ready to receive the file from the Transmitter device. | When the service receives the file data via HTTP PUT or any other out of band mechanism, then the service changes the state to the TRANSPORTING In case of any internal error conditions, the service may change the state to ERROR | When file is completely received by the service then, the service may change the state from FINISHED to READY_FOR_TRANSPORT. |
TRANSPORTING | This state of the FileTransfer service represents the file transfer is ongoing, and the service is receiving the file data. | When ongoing File Transfer service receives the CancelTransferaction,then the service stop receiving file data and changes the state to CANCELLED When the service receives the PausedTransfer action, it stop receiving the file data till the transfer is resumed using ResumeTransfer action. During this time FileTransfer service changes the state to TRANSFER PAUSEDWhen the file is completely received from the Transmitter device, then the service change the state to FINISHED | When the previously paused transfer is resumed by the Transmitter or by the Receiver it changes the state from TRANSFER PAUSED to TRANSPORTING |
SessionPaused:[noofbytes] | This is the transient state to represent the ongoing file transfer is paused by the Transmitter device or the Receiver device. | When the service receives the ResumeTransfer action or the Receiver resumes the previously paused file transfer, then the service starts receiving the file and change the state to TRANSPORTING | |
FINISHED | This is an intermediate state which represents the ongoing file transfer is completed | When there are still one or more file transfer to be expected, then the service changes the state to READY_FOR_TRANSFPORT.When there are no file transfer to be expected, and the service receives the CloseSession action then it changes the state to END | |
CANCELLED | This is an intermediate state to represent current ongoing file transfer is cancelled by the Transmitter device or the Receiver device | The service stops receiving the ongoing file data and changes the state to READY_FOR_TRANSPORT when the service expects to receive one and more file transfer request When the service does not expect to receive the file and receives the CloseSession action, then the service changes the state to END |
Claims (13)
- 와이파이 다이렉트 서비스를 지원하는 제 1 장치가 제2 장치와의 전송(Send) 세션을 초기화하는 방법에 있어서,ASP(Application Service Platform) 세션을 수립하는 단계; 및장치 명세(device description)에 관련된 URL(Uniform Resource Locator)을 사용하여 전송(Send) 세션을 초기화하는 단계;를 포함하며,상기 장치 명세에 관련된 URL은 상기 ASP 세션 수립 완료 이전에 획득된 것인, 세션 초기화 방법.
- 제1항에 있어서,상기 장치 명세에 관련된 URL은 상기 제2 장치의 서비스 계층이 전송하는 애드버타이즈먼트 메소드(Advertisement() method)에 포함된 것인, 세션 초기화 방법.
- 제2항에 있어서,상기 애드버타이즈먼트 메소드에 포함된 상기 장치 명세에 관련된 URL은 프로브 요청 절차 또는 서비스 디스커버리 절차 중 하나 이상을 통해 상기 제1 장치에게 전달되는, 세션 초기화 방법.
- 제2항에 있어서,상기 전송 세션 초기화 시, UPnP(Universal Plug and Play)에 관련된 디스커버리 절차는 생략되는, 세션 초기화 방법.
- 제2항에 있어서,상기 제1 장치의 서비스 계층이 전송하는 서비스 정보 요청에 관련된 파라미터 값은 NULL이 아닌 값으로 설정되는, 세션 초기화 방법.
- 제4항에 있어서,상기 서비스 정보 요청에 관련된 파라미터는 시크서비스 메소드(SeekService method)에 포함된 것인, 세션 초기화 방법.
- 제1항에 있어서,상기 장치 명세에 관련된 URL은 상기 제2 장치의 서비스 계층이 전송하는 컨펌서비스 메소드(ConfirmService() method)에 포함된 것인, 세션 초기화 방법.
- 제7항에 있어서,상기 컨펌서비스 메소드에 포함된 상기 장치 명세에 관련된 URL은 프로비젼디스커버리(Provision Discovery) 절차 또는 그룹 정보(Group formation) 절차를 통해 상기 제1 장치에게 전달되는, 세션 초기화 방법.
- 제1항에 있어서,상기 장치 명세에 관련된 URL은 상기 제2 장치의 서비스 계층이 전송하는 세션레디 메소드(SessionReady() method)에 포함된 것인, 세션 초기화 방법.
- 제1항에 있어서,상기 장치 명세에 관련된 URL을 사용하여 장치 명세를 획득하는 단계; 및상기 장치 명세에 포함된 서비스 명세에 관련된 URL을 사용하여 파일전송(filetransfer) 수행에 관련된 정보를 획득하는 단계;를 더 포함하는, 세션 초기화 방법.
- 제10항에 있어서,상기 장치 명세는, 기기정보, 변수, OS 타입/버전, UPnP 버전, 상기 서비스 명세에 관련된 URL, 제어를 위한 URL(URL for control), 이벤팅을 위한 URL(URL for eventing), 프레젠팅을 위한 URL(URL for presenting) 중 하나 이상을 포함하는, 세션 초기화 방법.
- 제1항에 있어서,상기 제1 단말은 상기 전송이 캔슬된 상태(canceled state)에서도 종료세션(CloseSession()) 수행이 가능한, 세션 초기화 방법.
- 와이파이 다이렉트 서비스를 지원하는 제1 장치에 있어서,수신 모듈; 및프로세서를 포함하고,상기 프로세서는, ASP(Application Service Platform) 세션을 수립하고, 장치 명세(device description)에 관련된 URL(Uniform Resource Locator)을 사용하여 전송(Send) 세션을 초기화하며,상기 장치 명세에 관련된 URL은 상기 ASP 세션 수립 단계에서 획득된 것인, 제1 장치.
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020157018389A KR20150105334A (ko) | 2012-12-09 | 2013-12-09 | 무선 통신 시스템에서 세션 초기화 방법 및 장치 |
EP13861330.2A EP2931002A4 (en) | 2012-12-09 | 2013-12-09 | METHOD AND APPARATUS FOR SESSION INITIALIZATION IN WIRELESS COMMUNICATION SYSTEM |
AU2013356802A AU2013356802B2 (en) | 2012-12-09 | 2013-12-09 | Method and device for session initialization in wireless communication system |
CN201380064243.5A CN104854953A (zh) | 2012-12-09 | 2013-12-09 | 用于无线通信系统中的会话初始化的方法和设备 |
JP2015546396A JP2016511944A (ja) | 2012-12-09 | 2013-12-09 | 無線通信システムにおけるセッション初期化方法および装置 |
US14/650,498 US20150327313A1 (en) | 2012-12-09 | 2013-12-09 | Method and device for session initialization in wireless communication system |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201261735042P | 2012-12-09 | 2012-12-09 | |
US61/735,042 | 2012-12-09 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014088378A1 true WO2014088378A1 (ko) | 2014-06-12 |
Family
ID=50883726
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/KR2013/011349 WO2014088378A1 (ko) | 2012-12-09 | 2013-12-09 | 무선 통신 시스템에서 세션 초기화 방법 및 장치 |
Country Status (7)
Country | Link |
---|---|
US (1) | US20150327313A1 (ko) |
EP (1) | EP2931002A4 (ko) |
JP (1) | JP2016511944A (ko) |
KR (1) | KR20150105334A (ko) |
CN (1) | CN104854953A (ko) |
AU (1) | AU2013356802B2 (ko) |
WO (1) | WO2014088378A1 (ko) |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2016036140A1 (ko) * | 2014-09-04 | 2016-03-10 | 엘지전자 주식회사 | Nan을 위한 무선 자원 스케줄링 방법 및 장치 |
JP2016058917A (ja) * | 2014-09-10 | 2016-04-21 | セイコーエプソン株式会社 | 映像表示システム、映像表示システムを構成する映像送信装置と映像受信表示装置との間の映像無線伝送規格に従った接続方法、コンピュータープログラム、映像送信装置、映像受信表示装置 |
WO2016068632A1 (ko) * | 2014-10-29 | 2016-05-06 | 엘지전자 주식회사 | 무선 통신 시스템에서 와이파이 다이렉트를 지원하는 장치가 디스커버리를 수행하는 방법 및 장치 |
WO2016148550A1 (ko) * | 2015-03-19 | 2016-09-22 | 엘지전자 주식회사 | 무선 통신 시스템에서 어플리케이션 서비스 플랫폼 세션 형성을 수행하는 방법 및 장치 |
CN107005831A (zh) * | 2014-12-08 | 2017-08-01 | 苹果公司 | 周边感知联网数据路径 |
JP2018503987A (ja) * | 2015-10-29 | 2018-02-08 | 小米科技有限責任公司XiaomiInc. | 情報処理方法および装置 |
JP2018512757A (ja) * | 2015-02-23 | 2018-05-17 | クゥアルコム・インコーポレイテッドQualcomm Incorporated | Nanデータリンクグループ形成およびデータフレームアドレス設定のための方法および装置 |
Families Citing this family (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9622278B2 (en) | 2010-10-26 | 2017-04-11 | Kingston Digital Inc. | Dual-mode wireless networked device interface and automatic configuration thereof |
US9781087B2 (en) | 2011-09-09 | 2017-10-03 | Kingston Digital, Inc. | Private and secure communication architecture without utilizing a public cloud based routing server |
US10237253B2 (en) | 2011-09-09 | 2019-03-19 | Kingston Digital, Inc. | Private cloud routing server, private network service and smart device client architecture without utilizing a public cloud based routing server |
US11863529B2 (en) | 2011-09-09 | 2024-01-02 | Kingston Digital, Inc. | Private cloud routing server connection mechanism for use in a private communication architecture |
US11683292B2 (en) | 2011-09-09 | 2023-06-20 | Kingston Digital, Inc. | Private cloud routing server connection mechanism for use in a private communication architecture |
US9935930B2 (en) | 2011-09-09 | 2018-04-03 | Kingston Digital, Inc. | Private and secure communication architecture without utilizing a public cloud based routing server |
US10601810B2 (en) | 2011-09-09 | 2020-03-24 | Kingston Digital, Inc. | Private cloud routing server connection mechanism for use in a private communication architecture |
JP6271839B2 (ja) * | 2013-01-25 | 2018-01-31 | キヤノン株式会社 | 通信装置、通信装置の制御方法、プログラム |
US9264751B2 (en) * | 2013-02-15 | 2016-02-16 | Time Warner Cable Enterprises Llc | Method and system for device discovery and content management on a network |
JP6253250B2 (ja) * | 2013-05-01 | 2017-12-27 | キヤノン株式会社 | 通信装置、通信装置の制御方法、プログラム |
US10021180B2 (en) * | 2013-06-04 | 2018-07-10 | Kingston Digital, Inc. | Universal environment extender |
US9641960B2 (en) * | 2014-11-12 | 2017-05-02 | Qualcomm Incorporated | MirrorLink with wireless serial bus |
JP6643848B2 (ja) * | 2015-09-24 | 2020-02-12 | キヤノン株式会社 | 通信装置、通信方法、およびプログラム |
US10033789B2 (en) * | 2016-09-29 | 2018-07-24 | Intel Corporation | Connectionless wireless media broadcast |
US10602557B2 (en) | 2016-11-30 | 2020-03-24 | Microsoft Technology Licensing, Llc | Discovering and protecting data streams in multi-path communication environments |
US10455632B2 (en) | 2016-11-30 | 2019-10-22 | Microsoft Technology Licensing, Llc | Dynamic identification of network connection preferences |
US10966073B2 (en) | 2017-11-22 | 2021-03-30 | Charter Communications Operating, Llc | Apparatus and methods for premises device existence and capability determination |
US11368552B2 (en) | 2019-09-17 | 2022-06-21 | Charter Communications Operating, Llc | Methods and apparatus for supporting platform and application development and operation |
WO2023234432A1 (ko) * | 2022-05-30 | 2023-12-07 | 엘지전자 주식회사 | 미라캐스트 제공 방법 및 미라캐스트 제공 시스템 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20110073239A (ko) * | 2009-12-22 | 2011-06-29 | 삼성전자주식회사 | WiFi Direct 네트워크에서의 서비스 탐색 방법 및 장치 |
KR20120073150A (ko) * | 2010-12-24 | 2012-07-04 | 삼성전자주식회사 | 와이파이 다이렉트 통신 방식에서의 컨텐트 보호를 위한 방법 및 장치 |
KR20120095572A (ko) * | 2011-02-21 | 2012-08-29 | 삼성전자주식회사 | 휴대용 단말기에서 와이파이 다이렉트 연결 기반 유니버설 플러그 앤 플레이 서비스를 제공하기 위한 장치 및 방법 |
KR20120103567A (ko) * | 2009-11-17 | 2012-09-19 | 삼성전자주식회사 | 와이파이 다이렉트 네트워크에서의 와이파이 디스플레이 서비스 탐색 방법 및 장치 |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001024546A (ja) * | 1999-07-02 | 2001-01-26 | Canon Inc | 無線通信装置、無線通信制御方法、無線通信システム、及び記憶媒体 |
US7171475B2 (en) * | 2000-12-01 | 2007-01-30 | Microsoft Corporation | Peer networking host framework and hosting API |
US7664861B2 (en) * | 2005-02-02 | 2010-02-16 | Verizon Laboratories Inc. | Managed peer-to-peer file sharing |
JP4530420B2 (ja) * | 2006-05-15 | 2010-08-25 | 日本電信電話株式会社 | ファイル転送システム、ファイル転送プログラムおよびファイル転送方法 |
KR100804831B1 (ko) * | 2006-12-28 | 2008-02-20 | 삼성전자주식회사 | 무선 usb 호스트 및 무선 usb 디바이스간에 세션을생성하고 관리하는 방법, 무선 usb 호스트 및 무선usb 디바이스 |
US8559340B2 (en) * | 2009-12-22 | 2013-10-15 | Samsung Electronics Co., Ltd. | Method and apparatus for service discovery in Wi-Fi direct network |
US8959183B2 (en) * | 2010-01-27 | 2015-02-17 | Code Systems Corporation | System for downloading and executing a virtual application |
CN102835066B (zh) * | 2010-02-03 | 2015-05-20 | 三星电子株式会社 | 用于在通用即插即用电话服务中的文件传输的电话服务器和方法 |
US8554970B2 (en) * | 2011-04-18 | 2013-10-08 | Nokia Corporation | Method, apparatus and computer program product for creating a wireless docking group |
-
2013
- 2013-12-09 CN CN201380064243.5A patent/CN104854953A/zh active Pending
- 2013-12-09 JP JP2015546396A patent/JP2016511944A/ja active Pending
- 2013-12-09 AU AU2013356802A patent/AU2013356802B2/en not_active Ceased
- 2013-12-09 US US14/650,498 patent/US20150327313A1/en not_active Abandoned
- 2013-12-09 EP EP13861330.2A patent/EP2931002A4/en not_active Withdrawn
- 2013-12-09 WO PCT/KR2013/011349 patent/WO2014088378A1/ko active Application Filing
- 2013-12-09 KR KR1020157018389A patent/KR20150105334A/ko not_active Application Discontinuation
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20120103567A (ko) * | 2009-11-17 | 2012-09-19 | 삼성전자주식회사 | 와이파이 다이렉트 네트워크에서의 와이파이 디스플레이 서비스 탐색 방법 및 장치 |
KR20110073239A (ko) * | 2009-12-22 | 2011-06-29 | 삼성전자주식회사 | WiFi Direct 네트워크에서의 서비스 탐색 방법 및 장치 |
KR20120073150A (ko) * | 2010-12-24 | 2012-07-04 | 삼성전자주식회사 | 와이파이 다이렉트 통신 방식에서의 컨텐트 보호를 위한 방법 및 장치 |
KR20120095572A (ko) * | 2011-02-21 | 2012-08-29 | 삼성전자주식회사 | 휴대용 단말기에서 와이파이 다이렉트 연결 기반 유니버설 플러그 앤 플레이 서비스를 제공하기 위한 장치 및 방법 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2931002A4 * |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10499408B2 (en) | 2014-09-04 | 2019-12-03 | Lg Electronics Inc. | Wireless resource scheduling method and device for NAN |
WO2016036140A1 (ko) * | 2014-09-04 | 2016-03-10 | 엘지전자 주식회사 | Nan을 위한 무선 자원 스케줄링 방법 및 장치 |
CN106688258A (zh) * | 2014-09-04 | 2017-05-17 | Lg电子株式会社 | 用于nan的无线资源调度方法和装置 |
CN106688258B (zh) * | 2014-09-04 | 2020-05-08 | Lg电子株式会社 | 用于nan的无线资源调度方法和装置 |
US10129900B2 (en) | 2014-09-04 | 2018-11-13 | Lg Electronics Inc. | Wireless resource scheduling method and device for NAN |
JP2016058917A (ja) * | 2014-09-10 | 2016-04-21 | セイコーエプソン株式会社 | 映像表示システム、映像表示システムを構成する映像送信装置と映像受信表示装置との間の映像無線伝送規格に従った接続方法、コンピュータープログラム、映像送信装置、映像受信表示装置 |
WO2016068632A1 (ko) * | 2014-10-29 | 2016-05-06 | 엘지전자 주식회사 | 무선 통신 시스템에서 와이파이 다이렉트를 지원하는 장치가 디스커버리를 수행하는 방법 및 장치 |
KR101901951B1 (ko) | 2014-10-29 | 2018-09-28 | 엘지전자 주식회사 | 무선 통신 시스템에서 와이파이 다이렉트를 지원하는 장치가 디스커버리를 수행하는 방법 및 장치 |
US10264441B2 (en) | 2014-10-29 | 2019-04-16 | Lg Electronics Inc. | Method and apparatus for performing discovery by device supporting Wi-Fi Direct in wireless communication system |
CN107005831A (zh) * | 2014-12-08 | 2017-08-01 | 苹果公司 | 周边感知联网数据路径 |
JP2018512757A (ja) * | 2015-02-23 | 2018-05-17 | クゥアルコム・インコーポレイテッドQualcomm Incorporated | Nanデータリンクグループ形成およびデータフレームアドレス設定のための方法および装置 |
WO2016148550A1 (ko) * | 2015-03-19 | 2016-09-22 | 엘지전자 주식회사 | 무선 통신 시스템에서 어플리케이션 서비스 플랫폼 세션 형성을 수행하는 방법 및 장치 |
JP2018503987A (ja) * | 2015-10-29 | 2018-02-08 | 小米科技有限責任公司XiaomiInc. | 情報処理方法および装置 |
Also Published As
Publication number | Publication date |
---|---|
KR20150105334A (ko) | 2015-09-16 |
US20150327313A1 (en) | 2015-11-12 |
AU2013356802B2 (en) | 2017-07-20 |
JP2016511944A (ja) | 2016-04-21 |
CN104854953A (zh) | 2015-08-19 |
AU2013356802A1 (en) | 2015-07-23 |
EP2931002A4 (en) | 2016-07-13 |
EP2931002A1 (en) | 2015-10-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2014088378A1 (ko) | 무선 통신 시스템에서 세션 초기화 방법 및 장치 | |
WO2014123383A1 (ko) | 무선 통신 시스템에서 세션 수립 방법 및 장치 | |
WO2014109513A1 (ko) | 무선 통신 시스템에서 디스커버리 방법 및 장치 | |
KR101611329B1 (ko) | 무선 통신 시스템에서 서비스 전환 방법 및 장치 | |
JP6377624B2 (ja) | 直接通信システムにおいてサービス探索又は広告方法及びそのための装置 | |
WO2014098437A1 (ko) | 무선랜 시스템에서 서비스 발견 방법 및 장치 | |
KR101680675B1 (ko) | 직접 통신 시스템에서 서비스 탐색 또는 광고 방법 및 이를 위한 장치 | |
WO2017039376A1 (ko) | 무선 통신 시스템에서 연결 능력 정보를 교환하는 방법 및 장치 | |
WO2017018823A1 (ko) | 무선 통신 시스템에서 어플리케이션 서비스 플랫폼 세션 형성 방법 및 장치 | |
KR20160026866A (ko) | 직접 통신 시스템에서 디바이스 탐색 방법 및 이를 위한 장치 | |
WO2016148523A1 (ko) | 무선 통신 시스템에서 서비스 디스커버리를 수행하는 방법 및 장치 | |
WO2017014579A1 (ko) | 무선 통신 시스템에서 디스커버리를 수행하는 방법 및 장치 | |
WO2016167618A9 (ko) | 무선 통신 시스템에서 서비스 디스커버리를 수행하는 방법 및 장치 | |
WO2016148406A1 (ko) | 무선 통신 시스템에서 어플리케이션 서비스 플랫폼을 이용하여 서비스를 지원하는 방법 및 장치 | |
WO2015119329A1 (ko) | 무선 통신 시스템에서 디스커버리를 수행하는 방법 및 장치 | |
WO2014129844A1 (ko) | 와이파이 다이렉트(Wi- Fi Direct) P2P(Peer to Peer) 통신을 위한 기기 발견 방법 및 이를 위한 장치 | |
WO2015167269A1 (ko) | 무선 통신 시스템에서 서비스 디스커버리 방법 및 장치 | |
WO2016190618A1 (ko) | 무선 통신 시스템에서 세션 핸드오버를 수행하는 방법 및 장치 | |
WO2016209019A1 (ko) | 무선 통신 시스템에서 mdns를 이용하여 디스커버리를 수행하는 방법 및 장치 | |
WO2016148550A1 (ko) | 무선 통신 시스템에서 어플리케이션 서비스 플랫폼 세션 형성을 수행하는 방법 및 장치 | |
WO2017155271A1 (ko) | 무선 통신 시스템에서 트랜스포트를 통해 스트리밍을 제공받는 방법 및 장치 | |
KR101901951B1 (ko) | 무선 통신 시스템에서 와이파이 다이렉트를 지원하는 장치가 디스커버리를 수행하는 방법 및 장치 | |
WO2017105071A1 (ko) | 무선 통신 시스템에서 nfc를 이용하여 서비스 디스커버리를 수행하는 방법 및 장치 | |
WO2017099518A2 (ko) | 무선 통신 시스템에서 ble 인터페이스를 이용하여 서비스 디스커버리를 수행하는 방법 및 장치 | |
WO2016126138A1 (ko) | 무선 통신 시스템에서 세션 수립 방법 및 장치 |
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: 13861330 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14650498 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2015546396 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2013861330 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 20157018389 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2013356802 Country of ref document: AU Date of ref document: 20131209 Kind code of ref document: A |