HK1173596B - Method and apparatus for providing peer -to -peer direct link communication with network connection - Google Patents

Description

Method and apparatus for providing end-to-end direct link communication to a network connection

Cross Reference to Related Applications

This application claims the benefit of U.S. provisional application No.61/243,833, filed on 9/18/2009, the contents of which are incorporated by reference into this application.

Background

A Wireless Local Area Network (WLAN) in Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more Stations (STAs) associated with the AP. The AP may access or connect to a Distribution System (DS) or another type of wired or wireless network that carries traffic within and outside the BSS. Traffic originating from outside the BSS to the STAs may be delivered through the AP. Traffic originating from STAs to destinations outside the BSS may be sent by the AP to the respective destinations. Traffic between STAs within a BSS may be communicated through an AP, where a source STA may send traffic to the AP and the AP communicates traffic to a destination STA. Traffic between STAs within the BSS may be referred to as peer-to-peer traffic.

Peer-to-peer traffic routed through an AP may be inefficient. For example, the traffic may be transmitted from the source STA to the AP and then from the AP to the destination STA, thereby transmitting the same information twice. Each transmission may limit the medium access overhead that may be incurred twice for the reasons described above. It is therefore desirable to have a method and apparatus for establishing and operating efficient peer-to-peer communication.

Disclosure of Invention

A method and apparatus may be used for peer-to-peer communication. The method and apparatus may allow network connectivity during a peer-to-peer communication session. The device may be a STA configured to transmit a first end-to-end communication frame and receive a responsive second end-to-end communication frame. The STA may be configured to communicate with the AP during an end-to-end communication session with another STA. Communication with the AP may occur when the STA is not in direct communication with another STA.

Drawings

The invention will be understood in more detail from the following description, given by way of example and understood in conjunction with the accompanying drawings, in which:

FIG. 1A is a system block diagram of an example communication system in which one or more disclosed embodiments may be implemented;

FIG. 1B is a system block diagram of an example wireless transmit/receive unit (WTRU) that may be used in the communication system shown in FIG. 1A;

FIG. 1C is a system block diagram of an example wireless access network and an example core network that may be used in the communication system shown in FIG. 1A;

FIG. 2 is a block diagram of an example end-to-end communication frame;

FIG. 3 is a flow chart of an example TDLS setup method;

fig. 4 is a block diagram of an example method for establishing an AP connection during peer-to-peer communication;

fig. 5 is a flow diagram of an example method when a STA responds with a TDLS scheduled AP connect response frame;

fig. 6 is another flow diagram of an example method when a STA responds with a TDLS scheduled AP connect response frame;

fig. 7 is another flow diagram of an example method when a STA responds with a TDLS scheduled AP connect response frame;

fig. 8 is a block diagram of an example frame body of a TDLS scheduled AP connection request frame;

fig. 9 is a block diagram of an example frame body of a TDLS scheduled AP connection response frame;

fig. 10 is a block diagram of an example frame body of a TDLS unscheduled AP connection request frame;

fig. 11 is a block diagram of an example frame body of a TDLS non-scheduled AP connection response frame;

fig. 12 is a flow diagram of an example method for establishing an AP connection during peer-to-peer communication; and

fig. 13 is a flow diagram of an example method in which a TDLS peer Power Save Mode (PSM) request/response frame may be used between two STAs to establish or change PSM according to a periodic schedule.

Detailed Description

FIG. 1A is a system block diagram of an example communication system 100 in which one or more disclosed embodiments may be implemented. The communication system 100 may be a multiple-access system that provides content, such as voice, data, video, messaging, broadcast, etc., to a plurality of wireless users. Communication system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, communication system 100 may use one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), orthogonal FDMA (ofdma), single carrier FDMA (SC-FDMA), and so forth.

As shown in fig. 1A, the communication system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a Radio Access Network (RAN)104, a core network 106, a Public Switched Telephone Network (PSTN)108, the internet 110, and other networks 112, it being understood that any number of WTRUs, base stations, networks, and/or network elements are contemplated by the disclosed embodiments. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless communication. By way of example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include User Equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a Personal Digital Assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a media transfer protocol (MTC) device, consumer electronics, and the like.

The communication system 100 may also include a base station 114a and a base station 114b, each of the base stations 114a, 114b may be any type of device configured to wirelessly interact with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the core network 106, the internet 110, and/or the network 112. For example, the base stations 114a, 114B may be Base Transceiver Stations (BTSs), node B, e node bs, home enodeb, site controllers, Access Points (APs), wireless routers, and the like. Although the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

The base station 114a may be part of the RAN 104, which RAN 104 may also include other base stations and/or network elements (not shown) such as site controllers (BSCs), Radio Network Controllers (RNCs), relay nodes, and the like. Base station 114a and/or base station 114b may be configured to transmit and/or receive wireless signals within a particular geographic area, which may be referred to as a cell (not shown). A cell may also be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, one for each sector of the cell. In another embodiment, the base station 114a may use multiple-input multiple-output (MIMO) technology and thus may use multiple transceivers for each sector of the cell.

The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which air interface 116 may be any suitable wireless communication link (e.g., radio frequency, microwave, Infrared (IR), Ultraviolet (UV), visible light, etc.). Air interface 116 may be established using any suitable Radio Access Technology (RAT).

More specifically, as previously described, communication system 100 may be a multiple access system and may use one or more channel access schemes such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA and the like. For example, the base station 114a in the RAN 104 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) terrestrial radio access (UTRA), which may establish the air interface 116 using wideband cdma (wcdma). WCDMA may include, for example, High Speed Packet Access (HSPA) and/or evolved HSPA (HSPA +). HSPA may include High Speed Downlink Packet Access (HSDPA) and/or High Speed Uplink Packet Access (HSUPA).

In another embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as evolved UMTS terrestrial radio access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and/or LTE-advanced (LTE-a).

In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA20001x, CDMA2000EV-DO, temporary Standard 856(IS-856), Global System for Mobile communications (GSM), enhanced data rates for GSM evolution (EDGE), GSM EDGE (GERAN).

For example, the base station 114B in fig. 1A may be a wireless router, a home nodeb, a home enodeb, or an access point, and may use any suitable RAT for facilitating communication connections in a local area, such as a company, home, vehicle, campus, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE802.11 to establish a Wireless Local Area Network (WLAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a Wireless Personal Area Network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may use a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE-a, etc.) to establish a femto cell (pico cell) and a femto cell (femtocell). As shown in fig. 1A, the base station 114b may have a direct connection to the internet 110. Thus, the base station 114b does not have to access the internet 110 via the core network 106.

The RAN 104 may communicate with a core network 106, which may be any type of network configured to provide voice, data, application, and/or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102 d. For example, the core network 106 may provide call control, billing services, mobile location-based services, prepaid calling, internetworking, video distribution, etc., and/or perform high-level security functions, such as user authentication. Although not shown in fig. 1A, it is to be understood that the RAN 104 and/or the core network 106 may communicate directly or indirectly with other RANs that employ the same RAT as the RAT 104 or a different RAT. For example, in addition to connecting to the RAN 104, which may employ E-UTRA radio technology, the core network 106 may also communicate with other RANs (not shown) that employ GSM radio technology.

The core network 106 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the internet 110, and/or other networks 112. The PSTN 108 may include a circuit-switched telephone network that provides Plain Old Telephone Service (POTS). The internet 110 may include a global system of interconnected computer networks and devices that use common communication protocols, such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) in the TCP/IP internet protocol suite. The network 112 may include a wireless or wired communication network owned and/or operated by other service providers. For example, the network 112 may include another core network connected to one or more RANs, which may employ the same RAT as the RAN 104 or a different RAT.

Some or all of the WTRUs 102a, 102b, 102c, 102d in the communication system 100 may include multi-mode capabilities, i.e., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over multiple communication links. For example, the WTRU102c shown in fig. 1A may be configured to communicate with a base station 114a using a cellular-based radio technology and to communicate with a base station 114b using an IEEE802 radio technology.

Figure 1B is a system block diagram of an example WTRU 102. As shown in fig. 1B, the WTRU102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a keypad 126, a display/touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system chipset 136, and other peripherals 138. It is to be appreciated that the WTRU102 may include any subset of the above elements, while being consistent with the above embodiments.

The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a Digital Signal Processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of Integrated Circuit (IC), a state machine, or the like. The processor 118 may perform signal coding, data processing, power control, input/output processing, and/or any other functions that enable the WTRU102 to operate in a wireless environment. The processor 118 may be coupled to a transceiver 120, which transceiver 120 may be coupled to a transmit/receive element 122. Although processor 118 and transceiver 120 are depicted in fig. 1B as separate components, it will be appreciated that processor 118 and transceiver 120 may be integrated together into an electronic package or chip.

Transmit/receive element 122 may be configured to transmit signals to a base station (e.g., base station 114a) or receive signals from a base station (e.g., base station 114a) over air interface 116. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In another embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive, for example, IR, UV, or visible light signals. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and receive both RF signals and optical signals. It should be appreciated that transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

Furthermore, although transmit/receive element 122 is depicted in fig. 1B as a single element, WTRU102 may include any number of transmit/receive elements 122. More particularly, the WTRU102 may use MIMO technology. Thus, in one embodiment, the WTRU102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

Transceiver 120 may be configured to modulate signals to be transmitted by transmit/receive element 122 and to demodulate signals received by transmit/receive element 122. As described above, the WTRU102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU102 to communicate via multiple RATs, such as UTRA and IEEE 802.11.

The processor 118 of the WTRU102 may be coupled to and may receive user input data from a speaker/microphone 124, a keypad 126, and/or a display/touch screen 128 (e.g., a Liquid Crystal Display (LCD) unit or an Organic Light Emitting Diode (OLED) display unit). The processor 118 may also output data to a speaker/microphone 124, a keypad 126, and/or a display/touch screen 128. Further, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 106 and/or the removable memory 132. The non-removable memory 106 may include Random Access Memory (RAM), readable memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a Subscriber Identity Module (SIM) card, a memory stick, a Secure Digital (SD) memory card, and the like. In other embodiments, the processor 118 may access data from and store data in memory that is not physically located on the WTRU102 but is located on a server or home computer (not shown).

The processor 118 may receive power from the power source 134 and may be configured to distribute power to other components in the WTRU102 and/or control power to other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (nickel cadmium (NiCd), nickel zinc (NiZn), nickel metal hydride (NiMH), lithium ion (Li-ion), etc.), solar cells, fuel cells, and the like.

The processor 118 may also be coupled to a GPS chipset 136, which the GPS chipset 136 may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location based on the timing of signals received from two or more neighboring base stations. It is to be appreciated that the WTRU may acquire location information by any suitable location determination method while being consistent with an embodiment.

The processor 118 may also be coupled to other peripherals 138, which peripherals 138 may include one or more software and/or hardware modules that provide additional features, functionality, and/or a wireless or wired connection. For example, peripheral devices 138 may include accelerometers, electronic compasses (e-compass), satellite transceivers, digital cameras (for photos or video), Universal Serial Bus (USB) ports, vibration devices, television transceiversHands-free earphone and BluetoothA module, a Frequency Modulation (FM) radio unit, a digital music player, a media player, a video game player module, an internet browser, and so forth.

Fig. 1C is a system block diagram of RAN 104 and core network 106 according to one embodiment. As previously described, the RAN 104 may communicate with the WTRUs 102a, 102b, 102c over the air interface 116 using E-UTRA radio technology. The RAN 104 may also communicate with a core network 106.

The RAN 104 may include enodebs 140a, 140B, 140c, although it is noted that the RAN 104 may include any number of enodebs while remaining consistent with an embodiment. The enodebs 140a, 140B, 140c may each include one or more transceivers for communicating with the WTRUs 102a, 102B, 102c over the air interface 116. In one embodiment, the enodebs 140a, 140B, 140c may implement MIMO technology. Thus, the enodeb 140a, for example, may use multiple antennas to send wireless signals to the WTRU102a and receive wireless signals from the WTRU102 a.

each of the enode bs 140a, 140B, 140c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, user scheduling, etc., in the uplink and/or downlink. As shown in fig. 1C, the enode bs 140a, 140B, 140C may communicate with each other via an X2 interface.

The core network 106 shown in fig. 1C may include a mobility management gateway (MME)142, a serving gateway 144, and a Packet Data Network (PDN) gateway 146. Although each of the above elements are described as part of the core network 106, it is noted that any of these elements may be owned and/or operated by an entity other than the core network operator.

MME 142 may be connected to enodebs 140a, 140B, 140c in RAN 104 through an S1 interface and may serve as a control node. For example, the MME 142 may be responsible for signaling, bearer activation/deactivation, selection of a particular serving gateway during initial connection of the WTRUs 102a, 102b, 102c to the users of the WTRUs 102a, 102b, 102c, and the like. MME 142 may also provide control plane functionality for handover between RAN 104 and other RANs (not shown) that use other radio technologies, such as GSM or WCDMA.

The serving gateway 144 may be connected to each of the enodebs 140a, 140B, 140c in the RAN 104 through an S1 interface. The serving gateway 144 may generally route and forward user data packets to and from the WTRUs 102a, 102b, 102 c. The serving gateway 144 may also perform other functions such as anchoring the user plane during inter-enodeb handovers, triggering paging when downlink data is available to the WTRUs 102a, 102B, 102c, managing and storing the context of the WTRUs 102a, 102B, 102c, and so on.

The serving gateway 144 may also be connected to a PDN gateway 146, where the PDN gateway 146 may provide the WTRUs 102a, 102b, 102c with access to a packet-switched network, such as the internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. An Access Router (AR)150 of a Wireless Local Area Network (WLAN)155 may communicate with the internet 110. AR 150 may facilitate communication between APs 160a, 160b, and 160 c. APs 160a, 160b, and 160c may communicate with STAs 170a, 170b, and 170 c.

The core network 106 may facilitate communication with other networks. For example, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and conventional landline communication devices. For example, the core network 106 may include or communicate with an IP gateway, such as an IP Multimedia Subsystem (IMS) server, where the IP gateway service serves as an interface between the core network 106 and the PSTN 108. In addition, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to a network 112, where the network 112 may include other wired or wireless networks owned and/or operated by other service providers.

The term "STA" as referred to below includes, but is not limited to, a wireless transmit/receive unit (WTRU), a User Equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a Personal Digital Assistant (PDA), a computer, a mobile network device (MID), or any other type of user equipment capable of operating in a wireless environment. The term "AP" as referred to below includes, but is not limited to, a base station, a node B, a site controller, or any other type of interfacing device capable of operating in a wireless environment.

The term "scheduled AP connection" referred to below refers to an AP connection that may be defined by a schedule or a pattern of AP connection instances (instances) each having a duration, and may be updated between two peer STAs to change the agreed schedule or pattern. An example of a scheduled AP connection may be that a STA connects to an AP periodically through a time interval at a particular starting or reference time. The term "unscheduled AP connection" referred to below refers to an AP connection that may be defined by multiple AP connection instances each having a duration and may not be updated once agreement is reached between two peer STAs. An example of an unscheduled AP connection is that a STA connects to an AP at a particular starting or reference time over two unequal time intervals. Another non-scheduled AP connection example may be for a STA to connect to an AP at a particular starting or reference time through a single time interval.

The channel through which an AP in a BSS operates to communicate with an associated STA may be referred to as a "fundamental channel" hereinafter. If the direct link is on a channel that is not the fundamental channel, then the channel may be referred to hereinafter as the "offline channel".

The methods and apparatus may provide an enhanced channel direct link setup (TDLS) mechanism for Very High Throughput (VHT) WLANs capable of data transmission above 100 Mbps. For VHT applications in WLANs, it is desirable to support scheduled and/or unscheduled AP connection periods/periods for direct link communication to obtain end-to-end application related information. This may be relevant in the case of direct link establishment on an offline channel or a non-BSS channel. This example application may be the use of a network connection to obtain content and other information associated with video communications between peer STAs, such as network games, promotions, recommendations, online video information, etc., in video playback units and video display units, for example, in an electronic electrical engineers (IEEE)802.11ac/ad network.

End-to-end communication frames, such as TDLS action frames, may be used to support scheduled and/or unscheduled AP connections. The end-to-end communication frame may have the property of managing the frame subtype Action and trigger an Acknowledgement (ACK) frame from the receiving STA when successfully received. In another variant, the end-to-end communication frame used to support scheduled and/or non-scheduled AP connections may have the management frame subtype "action No ACK (action No ACK)", and may not trigger an ACK from the receiving STA when successfully received. Further, these management frame subtype "no ACK action" end-to-end communication frames may be aggregated by STAs with one or more data frames, control frames, and management frames for transmission in aggregated packet data units.

Fig. 2 is a block diagram of an example end-to-end communication frame. Referring to fig. 2, a peer-to-peer communication frame 200 may include a category field 210, an action field 220. Action field 220 may include a value identifying an end-to-end communication frame type, such as a TDLS setup request, a TDLS setup response, or a TDLS teardown. Additional examples of action field 220 values and end-to-end communication frames are listed in table 1 below. The peer-to-peer communication frame 200 may include other fields 230- "defined according to the peer-to-peer communication frame type, where one or more of the fields may be an Information Element (IE).

Action field value	End-to-end communication frame
		0	TDLS setup request
1	TDLS setup response
		2	TDLS setup confirmation
3	TDLS demolition
		4	TDLS peer traffic indication
5	TDLS channel switch request
		6	TDLS channel switch response
7	TDLS peer PSM request
		8	TDLS peer PSM response
9	TDLS AP PHY data rate request
		10	TDLS AP PHY data rate response
11-255	Retention

Table 1802.11 z end-to-end communication frame and corresponding action field value

The TDLS mechanism may be enhanced to support scheduled and/or unscheduled connection periods with the AP, for example, by modifying the end-to-end communication frames or modifying the end-to-end communication frames and adding new end-to-end communication frames. The action field value assigned to the new peer-to-peer communication frame may be selected from the reserved digits 11-255 currently in 802.11z as shown in table 1 above in a flexible and convenient manner. The STA may encapsulate the modified or new peer-to-peer communication frame in a data frame or any other frame to communicate through the AP and transmit the encapsulated frame to the STA directly or through the AP.

The following is a first example implementation of transmitting capability information by a STA in a TDLS request and TDLS response request frame that may indicate whether there is support for scheduled and unscheduled AP connection times/periods in the STA. This may be accomplished by modifying the end-to-end communication frame as shown in the list in table 2 below.

Action field value	End-to-end communication frame
		0	TDLS setup request (amendment)
1	TDLS setup response (modify)
		2	TDLS setup confirmation
3	TDLS demolition
		4	TDLS peer traffic indication
5	TDLS channel switch request
		6	TDLS channel switch response
7	TDLS peer PSM request
		8	TDLS peer PSM response
9	TDLS AP PHY data rate request
		10	TDLS AP PHY data rate response
11-255	Retention

TABLE 2 modified end-to-end communication frames for VHT

Fig. 3 is a flow chart of an example TDLS setup method 300. The STA initiating TDLS may encapsulate a TDLS setup request frame 310 in a data frame. The originating STA may transmit data frames to the receiving STA through the AP to request TDLS to establish the direct link 320. The TDLS setup request frame may include an 802.11 extended capability information element as one field therein. A subfield comprising one or more bits may be used in the extended capability information element to indicate whether there is support for scheduled and unscheduled AP connection times/periods in the originating STA. In one variant, a dedicated subfield comprising one or more bits may be used for the indication of the AP connection period/period that supports scheduling. This subfield may be different from the dedicated subfield that includes one or more bits for indicating support for non-scheduled AP connection periods/periods. Thus, the TDLS setup request frame may be modified in this manner so that STAs initiating TDLS may indicate support for scheduled and unscheduled AP connection times/periods. Accordingly, the STA may indicate support for scheduled and non-scheduled AP connections by setting the corresponding subfield or subfields appropriately in the extended capability information element in the TDLS setup request frame.

In response to transmitting the modified TDLS setup request frame, the originating STA may receive a TDLS setup response frame 330 encapsulated in a data frame. The data frame may be received by the AP. The STA responding to the modified TDLS setup request frame may indicate support for scheduled and unscheduled AP connection times/periods by including an 802.11 extended capability information element in the TDLS setup response frame. As described in the case of the modified TDLS setup request frame, a subfield including one or more bits may be used in the extended capability information element to indicate whether there is support for scheduled and non-scheduled AP connection periods/periods in the STA. In one variation, a dedicated subfield comprising one or more bits may be used for the indication of scheduled AP connection time/period support. This subfield may be different from the dedicated subfield that includes one or more bits for indicating support for non-scheduled AP connection periods/periods. Thus, the TDLS setup response frame may be modified in this manner so that STAs responding to the modified TDLS setup request frame may indicate support for scheduled and unscheduled AP connection times/periods. Accordingly, the STA may indicate support for scheduled and non-scheduled AP connections by appropriately setting one or more corresponding subfields in an extended capability information element included in the TDLS setup response frame.

The STA may be enabled to transmit capability information in a TDLS request and TDLS response frame indicating whether there is support for scheduled and/or unscheduled AP connection times/periods in the STA. Transmitting capability information by a STA may be achieved by using: (1) either the TDLS request and TDLS response frames in 802.11z as in table 1 are appropriately modified or (2) new TDLS request and TDLS response frames. A subfield comprising one or more bits may be used to indicate whether there is support or capability for scheduled and/or unscheduled AP connection times/periods in the STA. In one variation, a dedicated new subfield including one or more bits may be used for the indication of support or capability for a scheduled AP connection period/period that is different from the dedicated new subfield including one or more bits for indicating support or capability for a non-scheduled AP connection period/period.

The STA may be enabled to transmit scheduled/unscheduled AP connection time/period information in the TDLS request and TDLS response frames. The status information may be used in the TDLS response frame to indicate success or failure of the TDLS scheduled/unscheduled AP connection request operation, and whether the operation resulted in a failure, the reason for the failure. For TDLS scheduled/unscheduled AP connection request operations, the following success and failure indications may be used in the status information: the AP connection period/cycle information is accepted, the AP connection period/cycle information is rejected, and the AP connection period/cycle information is rejected but proposed instead of the AP connection period/cycle information.

Fig. 4 is a flow diagram of an example method for establishing an AP connection during peer-to-peer communication. STA1405 may transmit a TDLS request frame 410 to STA2415 including the proposed scheduled/unscheduled AP connection period/cycle, wherein the TDLS request frame 410 indicates support for scheduled/unscheduled AP connections. The STA2415 may transmit the scheduled/unscheduled AP connection period/cycle information in the TDLS response frame 420 if the relevant state information in the TDLS response frame 420 indicates that "AP connection period/cycle information is rejected but alternative AP connection period/cycle information is proposed". The dialog token field may be used in the TDLS request and response frames to match the TDLS response frame with the TDLS request frame. The alternate AP connection period/cycle information may be used by the initiator STA to modify its AP connection period/cycle information and send it to STA2415 in a subsequent TDLS request frame.

After successfully receiving the TDLS response frame and the status code indicating acceptance from STA2415, the proposed scheduled/unscheduled AP connection time/period is established 430 between peer STAs 405 and 415. The peer STA maintains the scheduled/unscheduled AP connection according to the agreed AP connection period/cycle. If the TDLS direct link is on the offline channel 440, the peer STAs 405, 415 may switch to the fundamental channel 450 for communicating with the AP 455 and then return to the offline channel 460, all within each AP connection period 470 allowed by the agreed scheduled/unscheduled AP connection times/periods between the peer STAs. The transmission of the information of the scheduled/unscheduled AP connection times/periods by the STA may be achieved by using the following means: (1) a TDLS request and TDLS response frame modified as appropriate as any of the TDLS request and TDLS response frames in table 1 or (2) a modified TDLS request and TDLS response frame.

To transmit the scheduled AP connection period/period information, an information element called an AP connection scheduling information element may be defined. For example, the information element may contain fields including an element ID, length, and scheduling information such as start time, end time, duration, periodicity, and reference timing describing which time intervals may be used as AP connections. Once the AP connection schedule is established between peer STAs 405 and 415, the AP connection schedule may be valid until the peer STAs 405, 415 explicitly update the current AP connection schedule with the TDLS request/response exchange procedure or the TDLS direct link is torn down.

To transmit the non-scheduled AP connection time period/period information, an information element called an AP connection time period/period information element may be defined. For example, the information element may contain fields including an element ID, length, and period/cycle information such as start time, end time, duration, and a reference timing describing which time intervals may be used as AP connections in that order or any other order. Note that the AP connection period/period field or information element may specify only a single AP connection time interval. Once the unscheduled AP connection period/cycle protocol is established between peer STAs 405 and 415, the unscheduled AP connection period/cycle protocol may be active until either the agreed AP connection period/cycle expires or the TDLS direct link is torn down, whichever occurs first. Once the unscheduled AP connection time/period protocol is established, it may not be updated by either of the peer STAs 405, 415.

When the STA needs to communicate with the AP 455, the STA may establish an AP connection time/period by transmitting scheduled/unscheduled AP connection time/period information using the TDLS request frame 410 and the TDLS response frame 420. For example, the TDLS scheduling AP connection request frame and the TDLS scheduling AP connection response frame may be used in table 3 shown below. The TDLS scheduled AP connection request frame and the TDLS scheduled AP connection response frame may support a scheduled AP connection period/cycle when on a TDLS direct link.

TABLE 3 modifications and additions to end-to-end communication frames for VHT

The STA may send a TDLS schedule AP connection request frame to the peer STA that includes the proposed AP connection schedule, the TDLS schedule AP connection request frame indicating support for scheduling AP connections. The peer STA may respond with a TDLS scheduled AP connection response frame with a state code set in one of three ways: (1) accepting the proposed AP connection schedule (2) rejecting the proposed AP connection schedule or (3) rejecting the proposed AP connection schedule and proposing an alternate schedule.

Fig. 5 is a flow diagram of an example method 500 in which a STA accepts a proposed AP connection schedule by responding with a TDLS schedule AP connection response frame with a set of status codes. The STA may receive the TDLS scheduled AP connection request frame 510 and accept the proposed AP connection schedule 520. The STA may then establish an AP connection schedule 530.

Fig. 6 is a flow diagram of an example method 600 in which a STA responds to a TDLS scheduled AP connection request frame with a TDLS scheduled AP connection response frame with a set of state codes to reject a proposed AP connection schedule. The STA may receive the TDLS scheduled AP connection request frame 610 and reject the proposed AP connection schedule 620. Once the proposed AP connection schedule is rejected, the STA may continue ongoing end-to-end communication 630.

Fig. 7 is a flow diagram of an example method 700 in which a STA responds to a TDLS scheduled AP connection request frame with a TDLS scheduled AP connection response frame with a set of state codes to reject a proposed AP connection schedule and propose an alternative schedule. The STA may receive the first TDLS schedule AP connection request frame 710 and reject the proposed AP connection schedule 720 indicated in the received TDLS schedule AP connection request frame. The STA may transmit the alternative schedule 730 in the AP connection response frame of the first TDLS schedule. In response, the STA may receive the AP connection request frame 740 scheduled by the second TDLS. The STA may then transmit a second TDLS scheduled AP connection request frame 740. The STA may then transmit an AP connection response frame 750 indicating the accepted second TDLS schedule and determine a proposed AP connection schedule 760.

Once the AP connection schedule is established, it may be valid until either the STA explicitly updates the current AP connection schedule using the TDLS scheduled AP connection request/response exchange procedure or the TDLS direct link is torn down. The STA may maintain the AP connection according to the coordinated AP connection schedule. If the TDLS direct link is on the offline channel, the STAs may switch to the fundamental channel in order to communicate with the AP and then return to the offline channel, all within each AP connection period allowed by the established AP connection schedule between the STAs.

The STA may encapsulate the TDLS scheduled AP connection request frame in a data frame and transmit the AP connection request frame to the peer STA directly or through the AP so that the scheduled AP connection period/cycle is established or changed while on the TDLS direct link. The frame body of the TDLS scheduled AP connection request frame 800 may include information as shown in fig. 8.

For example, the frame body of the TDLS scheduled AP connection request frame 800 may include a category field 810, an action field 820, a dialog token field 830, a link identifier field 840, and an AP connection schedule 850. Referring to fig. 8, the category field 810 may be set to a value representing TDLS. The action field 820 may be set to a value representing a TDLS scheduled AP connection request.

The dialog token field 830 may be set to a value selected by the STA and used to match the action response frame with the action request frame. This value may be determined to be unique in a TDLS scheduled AP connection request frame where a corresponding TDLS scheduled AP connection response frame is not received.

The link identifier field 840 may include a link identifier information element, such as defined in ieee802.11 z. The information element may include information identifying the TDLS direct link. The link identifier information element may include fields including an element ID, a length, a BSSID, a TDLS initiator STA address, and a TDLS responder STA address.

The AP connection schedule field 850 may specify a schedule for the AP connection. This may be accomplished by setting this field to an information element that includes AP connection scheduling and other related information. An information element called AP connection scheduling information element may be defined for this purpose. For example, the information element may contain fields including an element ID, length, and scheduling information such as start time, end time, duration, periodicity, and reference timing describing which timing intervals may be used as AP connections.

The STA may encapsulate a TDLS scheduled AP connection response frame in a data frame and transmit the TDLS scheduled AP connection response frame to a peer STA directly or through an AP in response to the TDLS scheduled AP connection request frame. The frame body of the TDLS scheduled AP connection response frame 900 may include information as shown in fig. 9.

For example, the frame body of the TDLS scheduled AP connection response frame 900 may include a category field 910, an action field 920, a dialog token field 930, a status code field 940, a link identifier field 950, and an AP connection schedule field 960. Referring to fig. 9, the category field 910 may be set to a value representing TDLS. The action field 920 may be set to a value representing a TDLS scheduled AP connection response.

The session token field 930 may be set to a value contained in a corresponding received TDLS scheduled AP connection request frame. This field may be used to match action response frames with action request frames.

The status code field 940 may be set to indicate success or failure of the TDLS scheduled AP connection request operation and whether the operation results in failure, the reason for the failure. For TDLS scheduled AP connection request operations, the following success and failure indications may be used: the AP connection schedule is accepted, the AP connection schedule is rejected, and the AP connection schedule is rejected but an alternative schedule is proposed. Additional status codewords may be added to the existing status codewords in IEEE802.11 to indicate success and failure of AP connection request operation indication for TDLS scheduling.

The link identification field 950 may include a link identifier information element, such as defined in IEEE802.11 z. The information element may include information identifying the TDLS direct link. The direct link information element may contain fields including an element ID, a length, a BSSID, a TDLS initiator STA address, and a TDLS responder STA address.

The AP connection schedule field 960 may specify the schedule for the AP connection and may be present only if the status code field corresponds to "AP connection schedule rejected but alternative schedule proposed". The AP connection schedule may be specified by setting this field to an information element containing the AP connection schedule and other related information. An information element called AP connection scheduling information element may be defined for this purpose. An information element of an AP connection request frame defined for TDLS scheduling may be used herein. For example, the information element may contain fields including an element ID, a length, and scheduling information such as a start time, an end time, a duration, a periodicity, and a reference timing describing which time interval may be used as an AP connection.

As an alternative to using TDLS scheduled AP connection request and response frames, the STA may use a TDLS non-scheduled AP connection request frame and a TDLS non-scheduled AP connection response frame as shown in table 3 to support a non-scheduled AP connection period/cycle while on the TDLS direct link.

Similar to the TDLS scheduled AP connection request frame, the STA may encapsulate a TDLS non-scheduled AP connection request frame in a data frame and transmit the TDLS non-scheduled AP connection request frame to the peer STA directly or through the AP to establish or change a non-scheduled AP connection period/cycle when on the TDLS direct link. The frame body of the TDLS non-scheduled AP connection request frame 1000 may contain information as shown in fig. 10.

For example, the frame body of the TDLS non-scheduled AP connection request frame 1000 may include a category field 1010, an action field 1020, a session token field 1030, a link identifier field 1040, and an AP connection period/period field 1050. Referring to fig. 10, the category field 1010 may be set to a value representing TDLS. The action field 1020 may be set to a value representing a TDLS unscheduled AP connection request.

The dialog token field 1030 may be set to a value selected by the STA and used to match the action response frame with the action request frame. The value may be determined such that the value is unique in a TDLS unscheduled AP connection response frame, where a corresponding unscheduled AP connection request frame has not been received.

The link identifier field 1040 may contain a link identifier information element such as defined in IEEE802.11 z. The information element may contain information identifying the TDLS direct link. The direct link information element may contain fields including an element ID, a length, a BSSID, a TDLS initiator STA address, and a TDLS initiator STA address.

The AP connection period/period field 1050 may specify a period/period for AP connection. This may be accomplished by setting this field to a field containing AP connection times/periods and other relevant information. An information element called AP connection period/period information element may be defined for this purpose. For example, the information element may contain fields including element ID, length, and connection period/cycle information, such as start time, end time, duration, periodicity, and reference timing describing which timing intervals may be used as AP connections. Note that the AP connection period/period field or information element may specify only a single AP connection time interval or period.

The STA may encapsulate a TDLS non-scheduled AP connection response frame in a data frame and transmit the TDLS non-scheduled AP connection response frame to the peer STA directly or through the AP in response to the TDLS non-scheduled AP connection request frame. The frame body of the TDLS non-scheduled AP connection response frame 1100 may include information as shown in fig. 11.

For example, the frame body of the TDLS non-scheduled AP connection response frame 1100 may include a category field 1110, an action field 1120, a session token field 1130, a status code field 1140, a link identifier field 1150, and an AP connection period/cycle field 1160. Referring to fig. 11, the category field 1110 may be set to a value representing TDLS. The action field 1120 may be set to a value representing a TDLS non-scheduled AP connection response.

The session token field 1130 may be set to a value contained in an AP connection request frame that corresponds to the received TDLS non-schedule. This field may be used to match action response frames with action request frames.

The status code field 1140 may be set to indicate the success or failure of the TDLS unscheduled AP connection request operation and whether the operation results in a failure, the reason for the failure. For TDLS unscheduled AP connection request operations, the following success and failure indications may be used: an AP connection period/cycle is accepted, an AP connection period/cycle is rejected, and a period/cycle where an AP connection period/cycle is rejected but replaced is proposed. Additional status codes may be added to the status codes in 802.11 to indicate success and failure indications for TDLS unscheduled AP connection request operations.

The link identifier field 1150 may contain a link identifier information element such as defined in IEEE802.11 z. The information element may contain information identifying the TDLS direct link. The direct link information element may contain fields including an element ID, a length, a BSSID, a TDLS initiator STA address, and a TDLS responder STA address.

The AP connection period/cycle field 1160 may specify a period/cycle for AP connection, and the AP connection period/cycle field 1160 is present if the status code field corresponds to "AP connection period/cycle rejected but alternate period/cycle proposed". The AP connection period/period may be implemented by setting this field to a field containing the AP connection period/period and other relevant information. An information element called AP connection time period/period information element may be defined for this purpose. An information element defined for a TDLS non-scheduled AP connection request frame may be used herein. For example, the information element may contain fields including element ID, length, and connection period/cycle information, such as start time, end time, and reference timing describing which timing intervals may be used for AP connection. Note that the AP connection period/period field or information element may define only a single AP connection time interval or period.

Similar to the example when the STA transmits a TDLS scheduled AP connection request frame, the STA may transmit a TDLS unscheduled AP connection request frame containing an AP connection period/period element, which may represent an indication of unscheduled AP connection, to the peer STA. The peer STA may respond to the TDLS non-scheduled AP connection response frame with a state code set in one of three ways: (1) accepting the proposed AP connection period/period element (2) rejecting the proposed AP connection period/period element (3) rejects the proposed AP connection period/period element but proposes an alternative AP connection period/period.

In a first example, an AP connection time period/period protocol may be established between peer STAs. In a second example, a no-AP connection period/cycle protocol is established. In a third example, an alternate AP connection period/period element may be used by the initiator STA to generate a new TDLS unscheduled AP connection request frame. Upon successful reception of a TDLS unscheduled AP connection response frame with a status code indicating acceptance, the proposed AP connection time/period protocol may be established between peer STAs.

Once the AP connection period/cycle protocol is established, it may be valid until the expiration of the agreed AP connection period/cycle or the TDLS direct link is torn down, whichever occurs first. The AP connection period/period protocol, once established, may not be updated by any STA. If the TDLS direct link is in the offline channel, the STAs may switch to the fundamental channel to communicate with the AP and then return to the offline channel, all within each AP connection period allowed by the agreed AP connection period/cycle between STAs.

In a second example embodiment, a TDLS scheduled AP connection request frame and a TDLS non-scheduled AP connection request frame may be combined into one type of frame called TDLS AP connection request frame that contains all the required information for both scheduled and non-scheduled AP connection times/periods. The STA may encapsulate a TDLS AP connection request frame in a data frame and transmit the TDLS AP connection request frame to a peer STA directly or through an AP to establish or change a scheduled and/or unscheduled AP connection period/cycle while on a TDLS direct link. Accordingly, the TDLS scheduled AP connection response frame and the TDLS non-scheduled AP connection response frame may be combined into one frame called TDLS AP connection response frame containing all required information for both scheduled and non-scheduled AP connection periods/cycles. The STA may encapsulate a TDLS AP connection response frame in a data frame and transmit the TDLS AP connection response frame to the peer STA directly or through the AP in response to the TDLSAP connection request frame.

Fig. 12 is a diagram of an example method 1200 for establishing an AP connection during peer-to-peer communication. Referring to fig. 12, a STA may transmit a first peer-to-peer communication frame 1210. In response, the STA may receive the second peer-to-peer communication frame 1220 and begin communicating with the AP 1230. The initialization and timing of communications with the AP may be based on information indicated in the first end-to-end communication frame 1210, the second end-to-end communication frame 1220, or a combination of both.

The following is an example of transmitting scheduled/non-scheduled AP connection period/period information by STAs in TDLS request and TDLS response frames by modifying the 802.11z end-to-end communication frames listed below as shown in table 4.

TABLE 4 modifications to VHT end-to-end communication frames

Fig. 13 is a flow diagram of an example method 1300 in which a TDLS peer Power Save Mode (PSM) request/response frame may be used between two peer STAs to establish or change PSM according to a periodic schedule. The periodic schedule for the power save mode may be used by peer STAs for AP connections, where the STAs may maintain the AP connections in intervals in which the STAs are not expected to participate in the end-to-end direct communication as shown in fig. 13. Referring to fig. 13, the STA may also explicitly transmit scheduled/non-scheduled AP connection time/period information in the TDLS peer PSM request frame 1310. In other words, when end-to-end communication is not activated, PSM scheduling may be implicitly used for AP connection, or AP connection may be explicitly defined in TDLS peer PSM request frame. The status information may be used in the TDLS peer PSM response frame to indicate the success or failure of the TDLS scheduled/unscheduled AP connection request operation, and whether the operation resulted in a failure, the reason for the failure. If the status information field indicates that "AP connection period/cycle is rejected but alternative AP connection period/cycle information is proposed", the STA may receive the scheduled/unscheduled AP connection period/cycle information in the TDLS peer PSM response frame 1320. The dialog token field may be used in the TDLS peer PSM request and response frame for matching the TDLS peer PSM response frame with the TDLS peer PSM request frame. The STA may then transmit a message into the AP without the STA performing end-to-end direct communication with another STA 1330.

The following is an example of the third embodiment for transmitting scheduled/non-scheduled AP connection period/cycle information by a STA in a TDLS request and TDLS response frame. This may be accomplished by modifying the IEEE802.11z peer-to-peer communication frame as shown in table 5 below.

TABLE 5 modifications to VHT end-to-end communication frames

In IEEE802.11z, a TDLS channel switch request/response frame may be used between two STAs in order to switch channels. In the modified procedure, the STA may transmit scheduled/unscheduled AP connection time/period information in the TDLS channel switch request frame. The status information may be used in the TDLS channel switch response frame to indicate success or failure of the TDLS scheduled/unscheduled AP connection request operation, and whether the operation resulted in failure, the reason for the failure. If the status information field indicates that "AP connection period/cycle is rejected but alternative AP connection period/cycle information is proposed", the STA may transmit scheduled/unscheduled AP connection period/cycle information in the TDLS channel switch response frame.

In a fourth example embodiment, a new Enhanced Tunneled Direct Link Setup (ETDLS) may be implemented, wherein some or all aspects of the IEEE802.11z TDLS mechanism and one or more of the new embodiments described above are included. The new ETDLS mechanism may exist in WLANs and operate separately from TDLS of IEEE802.11 z.

In a fifth example embodiment, if a channel DLS is established between two STAs that are in direct end-to-end communication range but associated with different APs, the method and apparatus may be applied to a connection between the two APs and a channel path that is traversing the first AP. Two STAs may then maintain AP connectivity with their respective APs during the agreed AP connectivity period/cycle by establishing AP connectivity consistent with the mechanisms described below.

In a sixth example embodiment, the STA may take proactive steps to determine the protocol for packet exchange during the AP connection period/cycle. For example, the determined protocol for packet exchange may be a MAC protocol for transmitting and receiving data. The STA may determine the protocol to establish one or more medium reservations with the AP for data exchange during the AP connection period/cycle. For example, the STA may use a procedure similar to the IEEE802.11 n packet switching mechanism known as the "Reverse Direction protocol," in which a "Reverse Direction" initiator STA (in this case, the STA) may transmit packets to, or acquire packets from, a "Reverse Direction" responder (in this case, the AP). The STA may use any available means to facilitate scheduling with the AP for data exchange during the AP connection period/cycle. By aligning the AP connection period/cycle with the wake-up period/cycle of the power management scheme, the STA can use any one of the IEEE802.11 power management schemes. For example, the STA may use the IEEE802.11 mechanism to establish scheduled/unscheduled Automatic Power Save Delivery (APSD) to receive data. Another mechanism that the STA may use is a Power Save (PS) mechanism, in which the STA sends a PS-poll frame into the AP to receive buffered data.

The STA may have logic implemented therein to determine whether to use: (1) scheduled and non-scheduled AP connect operations (2) scheduled only AP connect operations (3) non-scheduled only AP connect operations (4) are neither scheduled nor non-scheduled AP connect operations. The page may implement a user interface in the STA, where the user may influence the selection by entering the relevant configuration information.

Examples

1. A method for use in a Station (STA), the method comprising:

receiving a first end-to-end communication frame; and

transmitting a second peer-to-peer communication frame in response to the first peer-to-peer communication frame.

2. The method of embodiment 1, further comprising:

in the case where a STA does not conduct direct communication with another STA, communication is conducted with an Access Point (AP) during an end-to-end communication session with another STA.

3. The method of embodiment 1 or 2, wherein the STA is in Power Save Mode (PSM).

4. The method of any preceding embodiment, further comprising:

rejecting scheduled or unscheduled AP connection periods or periods indicated in the first peer-to-peer communication frame.

5. The method as in any one of the preceding embodiments, wherein the second communication frame indicates an alternate scheduled or unscheduled connection period or periodicity.

6. The method as in any one of embodiments 1-3 or 5, further comprising:

accepting a scheduled or unscheduled AP connection time period or period indicated in the first peer-to-peer communication frame.

7. The method according to any of the preceding embodiments, further comprising:

the protocol used for packet exchange during the AP connection period or cycle is determined.

8. The method according to any of the preceding embodiments, further comprising:

establishing a medium reservation with the AP for the packet exchange during the AP connection period or cycle.

9. The method according to any of the preceding embodiments, further comprising:

and switching to the AP channel under the condition that the STA is in the offline channel.

10. The method of embodiment 9, further comprising:

communicating with the AP over the AP channel.

11. The method of embodiment 9, further comprising:

switching to an offline channel after communicating with the AP.

12. A method as in any preceding embodiment wherein the first peer-to-peer communication frame is an establishment request frame.

13. The method of any preceding embodiment, wherein the second peer-to-peer communication frame is an establishment response frame.

14. A method as in any preceding embodiment wherein the first peer-to-peer communication frame is a channel switch request frame.

15. The method of any preceding embodiment, wherein the second peer-to-peer communication frame is a channel switch response frame.

16. The method of any preceding embodiment, wherein the first end-to-end communication frame is a Tunnel Direct Link Setup (TDLS) frame.

17. The method of any preceding embodiment, wherein the second peer-to-peer communication frame is a channel direct link setup (TDLS) frame.

18. A method as claimed in any preceding embodiment, wherein said first peer-to-peer communication frame is an action frame.

19. A method as in any preceding embodiment wherein the second peer-to-peer communication frame is an action frame.

20. A method as in any preceding embodiment wherein the first peer-to-peer communication frame is a peer Power Save Mode (PSM) request frame.

21. The method of any preceding embodiment, wherein the second peer-to-peer communication frame is a peer Power Save Mode (PSM) response frame.

22. A method as in any preceding embodiment wherein the first peer-to-peer communication frame is received transparently through an AP.

23. The method of any preceding embodiment, wherein the first peer-to-peer communication frame is received directly from another STA.

24. A method as claimed in any preceding embodiment, wherein said first peer-to-peer communication frame is encapsulated in a data frame.

25. A method as in any preceding embodiment wherein the second peer-to-peer communication frame is transmitted encapsulated in a data frame.

26. A method for use in a Station (STA), the method comprising:

transmitting a first peer-to-peer communication frame; and

receiving a second peer-to-peer communication frame in response to the first peer-to-peer communication frame.

27. The method of embodiment 26, further comprising:

communicating with an Access Point (AP) during an end-to-end communication session with another STA on a condition that the STA is not in direct communication with the other STA.

28. The method of embodiment 26 or 27 wherein the STA is in Power Save Mode (PSM).

29. A method as in any of embodiments 26-28 wherein the first peer-to-peer communication frame indicates a scheduled or unscheduled AP connection time period or periodicity.

30. A method as in any of embodiments 26-29 wherein the second peer-to-peer communication frame indicates an optional scheduled or unscheduled AP connection time period or periodicity.

31. The method as in any one of embodiments 26-30, further comprising:

accepting a scheduled or unscheduled AP connection period or period indicated in the second peer-to-peer communication.

32. The method as in any one of embodiments 26-30, further comprising:

rejecting a scheduled or unscheduled AP connection period or cycle indicated in the second peer-to-peer communication.

33. The method as in any one of embodiments 26-32, further comprising:

a protocol for packet exchange during an AP connection period or cycle is determined.

34. The method as in any one of embodiments 26-33, further comprising:

establishing a medium reservation with the AP for the packet exchange during the AP connection period or cycle.

35. The method as in any one of embodiments 26-34, further comprising:

and switching to the AP channel under the condition that the STA is in the offline channel.

36. The method of embodiment 35, further comprising:

communicating with the AP over the AP channel.

37. The method of embodiment 35, further comprising:

switching to an offline channel after communicating with the AP.

38. The method as in any one of embodiments 26-37 wherein the first peer-to-peer communication frame is an establishment request frame.

39. The method as in any one of embodiments 26-38 wherein the second peer-to-peer communication frame is a setup response frame.

40. The method as in any one of embodiments 26-39 wherein the first peer-to-peer communication frame is a channel switch request frame.

41. The method as in any one of embodiments 26-40 wherein the first peer-to-peer communication frame is a channel switch response frame.

42. The method as in any one of embodiments 26-41 wherein the first end-to-end communication frame is a Tunnel Direct Link Setup (TDLS) frame.

43. The method as in any one of embodiments 26-42 wherein the second peer-to-peer communication frame is a channel direct link setup (TDLS) frame.

44. The method as in any one of embodiments 26-43 wherein the first peer-to-peer communication frame is an action frame.

45. The method as in any one of embodiments 26-44 wherein the second peer-to-peer communication frame is an action frame.

46. The method as in any one of embodiments 26-45 wherein the first peer-to-peer communication frame is a peer Power Save Mode (PSM) request frame.

47. The method as in any one of embodiments 26-46 wherein the second peer-to-peer communication frame is a peer Power Save Mode (PSM) response frame.

48. The method as in any one of embodiments 26-47 wherein the first peer-to-peer communication frame is transmitted transparently through the AP.

49. A method as in any of embodiments 26-48 wherein the first peer-to-peer communication frame is transmitted directly to another STA.

50. A method as in any of embodiments 26-49 wherein the first peer-to-peer communication frame is encapsulated in a data frame.

51. The method as in any one of embodiments 26-50 wherein the second peer-to-peer communication frame is received encapsulated in a data frame.

52. A Station (STA) configured to implement the method of any preceding embodiment.

Although the features and elements of the present invention are described above in particular combinations, each feature or element can be used alone without the other features and elements or in various combinations with other features and elements of the present invention. Furthermore, the methods provided by the present invention may be implemented in a computer program, software, or firmware executed by a computer or a processor, wherein the computer program, software, or firmware is embodied in a computer-readable storage medium. Computer-readable media include electronic signals (transmitted over a wired or wireless connection) and computer-readable storage media. Examples of computer readable storage media include, but are not limited to, Read Only Memory (ROM), Random Access Memory (RAM), registers, cache memory, semiconductor memory devices, magnetic media such as internal hard disks and removable disks, magneto-optical media, and optical media such as CD-ROM discs and Digital Versatile Discs (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC, or any host computer.

Claims (20)

1. A method for use in a Station (STA), the method comprising:

transmitting a first peer-to-peer communication frame to a second STA to establish a Power Save Mode (PSM), wherein the first peer-to-peer communication frame comprises a periodic schedule;

receiving a second peer-to-peer communication frame from the second STA in response to the first peer-to-peer communication frame, wherein the second peer-to-peer communication frame includes a status code indicating acceptance of the periodic scheduling;

communicating with the second STA on an offline channel;

entering the PSM related to the second STA based on the periodic schedule; and

communicate with an Access Point (AP) on a fundamental channel while in the PSM related to the second STA.

2. The method of claim 1, further comprising:

determining a protocol for packet exchange during an AP connection period or cycle; and

establishing a medium reservation with the AP for the packet exchange during the AP connection period or cycle.

3. The method of claim 1, further comprising:

switching from the offline channel to the fundamental channel for communicating with the AP.

4. The method of claim 3, further comprising:

and returning to the offline channel when the communication with the AP is finished.

5. The method of claim 1, wherein the first peer-to-peer communication frame is a tunnel direct link setup, TDLS, peer power save mode, PSM, request frame.

6. The method of claim 1, wherein the second peer-to-peer communication frame is a channel direct link setup, TDLS, peer power save mode, PSM, response frame.

7. The method of claim 1, wherein the first peer-to-peer communication frame contains an information element, IE, indicating a scheduled or unscheduled AP connection time period or periodicity.

8. The method of claim 1, wherein the second peer-to-peer communication frame includes an information element, IE, indicating an alternate scheduled or unscheduled AP connection time period or periodicity.

9. The method of claim 1, wherein the first peer-to-peer communication frame is transmitted transparently through the AP or directly to the second STA.

10. The method of claim 1, wherein the first peer-to-peer communication frame is encapsulated in a data frame.

11. The method of claim 1, wherein the second peer-to-peer communication frame is received encapsulated in a data frame.

12. A station, STA, comprising:

a transmitter configured to transmit a first peer-to-peer communication frame to a second STA to establish a Power Save Mode (PSM), wherein the first peer-to-peer communication frame comprises a periodic schedule;

a receiver configured to receive a second peer-to-peer communication frame from the second STA in response to the first peer-to-peer communication frame, wherein the second peer-to-peer communication frame includes a status code indicating acceptance of the periodic schedule; and

a processor configured to cause the STA to operate in the PSM related to the second STA based on the periodic schedule,

wherein the transmitter and the receiver are further configured to:

communicating with the second STA on an offline channel when the STA is not in the PSM related to the second STA; and

communicate with an Access Point (AP) on a fundamental channel while the STA is in the PSM related to the second STA.

13. The STA of claim 12, further comprising:

a processor configured to determine a protocol for packet exchange during an AP connection period or period and establish a medium reservation with the AP for the packet exchange during the AP connection period or period.

14. The STA of claim 12, wherein the processor is further configured to switch from the offline channel to the fundamental channel for communicating with the AP.

15. The STA of claim 14, wherein the processor is further configured to return to the offline channel at the end of communication with the AP.

16. The STA of claim 12, wherein the transmitter is configured to transmit a first peer-to-peer communication frame containing an information element, IE, indicating a scheduled or unscheduled AP connection time or period.

17. The STA of claim 12, wherein the receiver is configured to receive a second peer-to-peer communication frame containing an information element, IE, indicating an alternate scheduled or unscheduled AP connection time period or periodicity.

18. The STA of claim 12, wherein the transmitter is configured to transmit the first peer-to-peer communication frame transparently through the AP or directly to the second STA.

19. The STA of claim 12, wherein the transmitter is further configured to transmit the first peer-to-peer communication frame encapsulated in a data frame.

20. The STA of claim 12, wherein the receiver is further configured to receive the second peer-to-peer communication frame encapsulated in a data frame.