US20140126470A1 - Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices - Google Patents

Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices Download PDF

Info

Publication number
US20140126470A1
US20140126470A1 US13/839,323 US201313839323A US2014126470A1 US 20140126470 A1 US20140126470 A1 US 20140126470A1 US 201313839323 A US201313839323 A US 201313839323A US 2014126470 A1 US2014126470 A1 US 2014126470A1
Authority
US
United States
Prior art keywords
enabled
request
request message
message
wireless
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/839,323
Inventor
Emily Qi
Venkata VALLABHU
Rita Lee
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intel Corp
Original Assignee
Intel Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US201261721837P priority Critical
Application filed by Intel Corp filed Critical Intel Corp
Priority to US13/839,323 priority patent/US20140126470A1/en
Assigned to INTEL CORPORATION reassignment INTEL CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: VALLABHU, Venkata, QI, EMILY, LEE, Rita
Publication of US20140126470A1 publication Critical patent/US20140126470A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/14Direct-mode setup
    • H04W76/023
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/66Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/104Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/104Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks
    • H04L67/1061Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks involving node-based peer discovery mechanisms
    • H04L67/1063Discovery through centralizing entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/18Management of setup rejection or failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/104Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks
    • H04L67/1061Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks involving node-based peer discovery mechanisms
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/10Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network
    • H04L67/104Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks
    • H04L67/1061Network-specific arrangements or communication protocols supporting networked applications in which an application is distributed across nodes in the network for peer-to-peer [P2P] networking; Functionalities or architectural details of P2P networks involving node-based peer discovery mechanisms
    • H04L67/1072Discovery involving ranked list compilation of candidate peers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W60/00Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10Small scale networks; Flat hierarchical networks
    • H04W84/12WLAN [Wireless Local Area Networks]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/06Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Abstract

Systems, apparatuses, and methods are directed to a first peer-to-peer (P2P) enabled device configured to wirelessly transmit a first request message and a second P2P-enabled device configured to wirelessly receive the first request message. In response to receiving the first request message, the second P2P-enabled device wirelessly transmits a second request message to the first P2P-enabled device, and if the first request message is rejected by the second P2P-enabled device, the second request message includes status control information indicating that the first request message is rejected. In addition, if the first request message is to be cancelled, the first P2P-enabled device transmits another request message to the second P2P-enabled device with status control information indicating that the first request message has been cancelled.

Description

    CROSS REFERENCE TO RELATED APPLICATIONS
  • The present Patent Application is based on, and claims priority to, U.S. Provisional Patent Application No. 61/721,837 filed on Nov. 2, 2012, the entire content of which is hereby incorporated by reference.
  • TECHNICAL FIELD
  • This disclosure relates generally to the field of wireless communications, and in particular, to peer-to-peer wireless systems and methods.
  • BACKGROUND ART
  • Traditionally, wireless communication systems have employed a centralized control architecture. That is, devices serviced by such systems operate under the supervision of, as well as communicate directly with, a network controller that regulates the control information, messaging transactions, and timing to achieve the necessary endpoint-to-endpoint connectivity. In particular, the messaging transaction and control information are routed directly to the network controller to ensure centralized control of communications between the devices.
  • Recently, wireless communication systems having decentralized architectures, such as peer-to-peer (P2P) networks, have gained much interest given their level of flexibility and user convenience. In wireless P2P networks, wireless devices may establish connectivity and communicate directly with each other without having to route messages or control information through a centralized network controller. Such wireless P2P connectivity to allow users to connect devices in an easy and convenient manner and enable users to share, show, print, and synchronize content.
  • However, for various transactions, wireless P2P networks may lack certain control measures that affect message transfer efficiencies and, ultimately, overall communications.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 depicts an overview of a wireless peer-to-peer system, in accordance with various aspects and principles of the present disclosure.
  • FIG. 2 depicts a message flow diagram illustrating an exemplary process for a wireless peer-to-peer system, in accordance with various aspects and principles of the present disclosure.
  • FIG. 3 depicts a message flow diagram illustrating an exemplary process for a wireless peer-to-peer system, in accordance with various aspects and principles of the present disclosure.
  • DETAILED DESCRIPTION
  • In the description that follows, like components have been given the same reference numerals, regardless of whether they are shown in different embodiments. To illustrate an embodiment(s) of the present disclosure in a clear and concise manner, the drawings may not necessarily be to scale and certain features may be shown in somewhat schematic form. Features that are described and/or illustrated with respect to one embodiment may be used in the same way or in a similar way in one or more other embodiments and/or in combination with or instead of the features of the other embodiments.
  • In accordance with various embodiments of this disclosure, what is proposed is a system and method directed to a first peer-to-peer (P2P) enabled device configured to wirelessly transmit a first request message and a second P2P-enabled device configured to wirelessly receive the first request message. In response to receiving the first request message, the second P2P-enabled device wirelessly transmits a second request message to the first P2P-enabled device, and if the first request message is rejected by the second P2P-enabled device, the second request message includes status control information indicating that the first request message is rejected.
  • Moreover, if the first request message is to be cancelled, the first P2P-enabled device transmits another request message to the second P2P-enabled device with status control information indicating that the first request message has been cancelled.
  • These and other features and characteristics, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of claims. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.
  • With regard to wireless P2P networks, the inventors have observed certain drawbacks in P2P transactions that require user intervention. For example, transactions requesting P2P-enabled devices to join a P2P network will require user input after a request notification, advising the user of the invitation, is received by the user. Other transactions requiring user input may include provision requests, negotiation requests, connection requests, etc. However, there is no mechanism for a receiving P2P device to reject such requests that are initiated by a requesting P2P device. Nor is there a mechanism for a requesting P2P device to cancel its invitation to a receiving P2P device to join the network.
  • These drawbacks may affect the transfer efficiency of the P2P devices. For example, in some wireless P2P systems, the requesting P2P device has to wait for a certain timeout period (e.g., 120 sec.) in the channel before determining whether the invitation is successful or not. Given that the requesting P2P device may also have other concurrent operations that need to be executed, waiting for such a timeout period compromises overall efficiency. Moreover, different applications may have their own timing constraints, so such a timeout period may further impact overall efficiency. In addition, the inability for a requesting P2P device to cancel its invitation may further exacerbate such efficiency issues, as the requesting P2P would have to wait for the transactional cycle including the timeout period, even though it no longer has an interest in sustaining the invitation.
  • Therefore, what is proposed is a P2P system, apparatus, and method that employs a status control mechanism that enables the rejection and/or cancellation of P2P message requests requiring user input. In this manner, the efficiency of message transfers may be significantly improved by avoiding any delays and timeouts in rejecting and cancelling such requests.
  • With this said, FIG. 1 depicts an overview of wireless peer-to-peer (P2P) system 100, in accordance with various aspects and principles of the present disclosure. The architecture of system 100 comprises wireless P2P-enabled device 102A and wireless P2P-enabled device 102B which are configured to wirelessly communicate directly each other via a wireless P2P networking protocol. For purposes of clarity, the embodiment of system 100 is depicted with wireless P2P-enabled device 102A configured as the “requesting” device while wireless P2P-enabled device 102B is configured as the “receiving” device. This is not intended to be limiting in any way, as the “requesting” and “receiving” functionality may easily be swapped among devices 102A and 102B, in accordance with the principles of the present disclosure.
  • The phrase “wireless P2P network” and “wireless P2P networking protocol” refers to a network that enables devices to communicate directly with each other via wireless signals in a decentralized peer-to-peer manner. Such networks may operate in accordance with one or more of the following standards or specifications and subsequent revisions as well as other standards for wireless networking: ANSI/IEEE 802.11 Standard for Information technology-Telecommunications and information exchange between systems-Local and metropolitan area networks, and its associated group of standards, such as for example Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications, Amendment 1 to Part 11, Amendment 3 to Part 11, P802.11u/D.8.0 Draft Standard, P802.11v/7.0 Draft Standard, Wi-Fi Alliance WMM™. Specification (including WMM™ Power Save) Specification version 1.1, Wi-Fi Alliance Technical Committee P2P Task Group WiFi Peer-to-Peer (P2P) Technical Specification version 1.0, and others.
  • The phrase “wireless P2P device” refers to any device that may communicate with other devices via wireless signals in accordance with a peer-to-peer network, as discussed above. Wireless P2P devices may, therefore include the necessary circuitry, hardware, firmware, and software or any combination thereof to effect wireless P2P communications. Such devices may comprise, for example, a laptop, mobile device, cellular/smartphone, gaming device, tablet computer, a wireless-enabled patient monitoring device, personal communication system (PCS) device, personal digital assistant (PDA), personal audio device (PAD), portable navigational device, and/or any other electronic wireless-enabled device configured to receive a wireless signal. As such, wireless P2P devices may be configured with variety of components, such as, for example, processor(s), memories, display screen, camera, input devices as well as communication-based elements. The communication-based elements may include, for example, antenna, interfaces, transceivers, modulation/demodulation and other circuitry, configured to wirelessly communicate and transmit/receive information. Wireless P2P devices may also include a bus infrastructure and/or other interconnection means to connect and communicate information between various components and communication elements noted above.
  • The processor(s) of the wireless P2P devices may be part of a core processing or computing unit that is configured to receive and process input data and instructions, provide output and/or control other components of the wireless P2P devices in accordance with embodiments of the present disclosure. Such processing elements may include a microprocessor, a memory controller, a memory and other components. The microprocessor may further include a cache memory (e.g., SRAM), which along with the memory may be part of a memory hierarchy to store instructions and data. The microprocessor may also include one or more logic modules such as a field programmable gate array (FPGA) or other logic array.
  • The memory of the wireless P2P devices may take the form of a dynamic storage device coupled to the bus infrastructure and configured to store information, instructions, and application programs to be executed by the processor(s) or controller(s) associated of the wireless P2P devices. Some or all of the memory may be implemented as Dual In-line Memory Modules (DIMMs), and may be one or more of the following types of memory: Static random access memory (SRAM), Burst SRAM or SynchBurst SRAM (BSRAM), Dynamic random access memory (DRAM), Fast Page Mode DRAM (FPM DRAM), Enhanced DRAM (EDRAM), Extended Data Output RAM (EDO RAM), Extended Data Output DRAM (EDO DRAM), Burst Extended Data Output DRAM (BEDO DRAM), Enhanced DRAM (EDRAM), synchronous DRAM (SDRAM), JEDECSRAM, PCIOO SDRAM, Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), SyncLink DRAM (SLDRAM), Direct Rambus DRAM (DRDRAM), Ferroelectric RAM (FRAM), or any other type of memory device. Wireless P2P devices may also include read only memory (ROM) and/or other static storage devices coupled to the bus infrastructure and configured to store static information and instructions for the processor(s) and/or controller(s) associated with the wireless P2P devices.
  • Returning to FIG. 1, a user (i.e., “requesting user”) initiates a request intended for another user (i.e., “receiving user”). The request is inputted in requesting wireless P2P-enabled device 102A which generates and wirelessly transmits a request message to receiving P2P-enabled device 102B. In certain embodiments, the request message may take the form of an invitation request frame in which requesting wireless P2P-enabled device 102A invites receiving P2P-enabled device 102B to associate with the P2P network. However, the invitation request message form is not intended to be limiting, as the requested message may equally take the form of any request message that necessitates user input on the receiver side to effect a response to the request message, such as, for example, provisioning request messages, negotiation request messages, connection request messages, etc., in accordance with the various aspects of present disclosure,
  • As shown in FIG. 1, after the receiving user receives the request message, the user inputs his response, either acceptance or rejection, into receiving P2P-enabled device 102B. In turn, receiving P2P-enabled device 102B generates and wirelessly transmits a responsive message back to requesting wireless P2P-enabled device 102A regarding the acceptance or rejection of the request. As will be described in further detail below, the responsive message also includes a status attribute control mechanism that contains codes to expedite the processing of the message transaction, such as, the rejection and cancellation of P2P message requests, resulting in the increase of overall efficiency.
  • To this end, FIG. 2 depicts a detailed message flow diagram illustrating exemplary process 200 for wireless P2P system 100, in accordance with various aspects and principles of the present disclosure. Process 200 is represented as a transactional message flow diagram illustrating transactional messages in the form of frames between requesting wireless P2P-enabled device 102A and receiving P2P-enabled device 102B. In the illustrated embodiment, process 200 employs status code control attribute information configured to provide an indication of the status of a user response to an initial request.
  • Initially, requesting user inputs a request into requesting wireless P2P-enabled device 102A, as noted by message 201. Requesting wireless P2P-enabled device 102A then generates and wirelessly transmits a request frame, in accordance with the requesting user's request, at message 202. For sake of clarity, the request frame is represented as an invitation request frame, although the request frame may equally be represented by a variety of request messages, such as an invitation request message, provisioning request message, negotiation request message, connection request message, etc., as noted above.
  • Upon receipt of the invitation request frame, receiving P2P-enabled device 102B transmits a notification of the request to receiving user, as shown by message 204. The notification is passed on to a higher protocol stack layer of receiving P2P-enabled device 102B, which is then processed to generate an alert message, such as a pop-up window, dialog box, alarm, or any other suitable means for notifying the user of the invitation request and allowing the entry of user input.
  • Meanwhile, at message 206, receiving P2P-enabled device 102B transmits a response frame to requesting wireless P2P-enabled device 102A with a status code indicating it has receive the invitation request frame and that it is awaiting the “user input” to the invitation request frame.
  • The receiving user enters his response regarding the acceptance/rejection of the invitation request, which is presented to receiving P2P-enabled device 102B, at message 208. The higher layers of receiving P2P-enabled device 102B subsequently generate a request frame containing status code control attribute information and P2P-enabled device 102B then transmits the generated request frame to requesting wireless P2P-enabled device 102A, at message 210.
  • It will be appreciated that the status code control attribute information is configured with information that provides an indication of the status of the response to the initial invitation request. In certain embodiments, if the user input response is to reject the invitation request (i.e., “reject”), receiving P2P-enabled device 102B generates and transmits a request frame with a status control attribute information having the status code field set to “FAIL: user rejected”.
  • On the other hand, if the user input response is to accept the invitation (i.e., “accept”), receiving P2P-enabled device 102B generates and transmits a request frame without any status control attribute information. In addition, if no response is received from the higher layers (i.e., user), the receiving P2P-enabled device 102B will do nothing and the requesting P2P device 102B will timeout.
  • Returning to FIG. 2, after receiving the request frame containing status code control attribute information from P2P-enabled device 102B, requesting wireless P2P-enabled device 102A forwards a notification of the acceptance or rejection of the request to the requesting user, at message 212. After which, at message 214, requesting wireless P2P-enabled device 102A forwards a response frame to receiving P2P-enabled device 102B with status control attribute information having the status code field set to “SUCCESS”, indicating that the acceptance or rejection was successfully received.
  • In this manner, the requesting P2P device avoids the latency in having to wait for certain timeout periods in the channel before determining that the request rejected, as any rejection to the initial request by the receiving P2P device is presented to the requesting P2P device in due course.
  • FIG. 3 depicts a detailed message flow diagram illustrating exemplary process 300 for wireless P2P system 100, in accordance with various aspects and principles of the present disclosure. Like process 200, process 300 is represented as a transactional message flow diagram illustrating transactional messages in the form of frames between requesting wireless P2P-enabled device 102A and receiving P2P-enabled device 102B. In the illustrated embodiment, process 300 employs status code control attribute information configured to provide an indication a request to cancel or abort a previously-submitted request.
  • Initially, requesting user inputs a request into requesting wireless P2P-enabled device 102A, as noted by message 301. Requesting wireless P2P-enabled device 102A then generates and transmits a request frame, in accordance with the requesting user's request, at message 302. Again, for the sake of tractability, the request frame is embodied as an invitation request frame, although the request frame may be directed to an invitation request message, provisioning request message, negotiation request message, connection request message, etc., as noted above.
  • Upon receipt of the invitation request frame, receiving P2P-enabled device 102B transmits a notification of the request to receiving user, as shown by message 304. The notification is passed on to a higher protocol stack layer of receiving P2P-enabled device 102B, which is then processed to generate an alert message, such as a pop-up window, dialog box, alarm, or any other suitable means for notifying the user of the invitation request and allowing the entry of user input.
  • Meanwhile, at message 306, receiving P2P-enabled device 102B transmits a response frame to requesting wireless P2P-enabled device 102A with a status code indicating that it is awaiting “user input” to the invitation request frame.
  • However, as depicted at message 308, the requesting user inputs a cancellation to abort the previously-submitted invitation request. In response, requesting wireless P2P-enabled device 102A generates a request frame containing status code control attribute information and transmits that request frame to receiving P2P-enabled device 102B, at message 310. In this case, the status code control attribute information is configured to provide an indication of a request to cancel the previously-submitted request. In particular, requesting wireless P2P-enabled device 102A generates and transmits a request frame with a status control attribute information having the status code field set to “CANCEL”.
  • Upon receipt of the request frame with the “CANCEL” status code by receiving P2P-enabled device 102B, the CANCEL request frame is passed on to a higher protocol stack layer of receiving P2P-enabled device 102B, at message 312, which is then processed to generate an alert, such as a pop-up window, dialog box, alarm, or any other suitable means for notifying the user that the invitation request has been cancelled.
  • At message 314, receiving P2P-enabled device 102B then forwards a response frame to requesting wireless P2P-enabled device 102A with status control attribute information having the status code field set to “SUCCESS”, indicating that the cancellation was received and successful.
  • In this manner, the requesting P2P device is able to cancel a request that was previously submitted to receiving P2P device, thereby avoiding any delays in being forced to wait through the transaction processing cycles.
  • EXAMPLES
  • The following examples pertain to numerous embodiments, consistent with the various aspects and principles of the present disclosure.
  • Example 1 is a wireless system that includes a first peer-to-peer (P2P)-enabled device configured to wirelessly transmit a first request message containing a request requiring a response; and a second P2P-enabled device configured to wirelessly receive the first request message, wherein, upon receiving the first request message, the second P2P-enabled device wirelessly transmits a second request message to the first P2P-enabled device, and wherein, if the request contained in the first request message is rejected by the second P2P-enabled device, the second request message includes status control information indicating that the first request message is rejected.
  • In Example 2, the subject matter of Example 1 may optionally include that if the request contained in the first request message is accepted by the second P2P-enabled device, the second request message omits the status control information.
  • In Example 3, the subject matter of Example 1 may optionally include that prior to transmitting the second request message, the second P2P-enabled device transmits a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 4, the subject matter of Example 1 may optionally include that the first P2P-enabled device transmits a second response message to the second P2P-enabled device to indicate acknowledgement of the rejection of the request.
  • In Example 5, the subject matter of Example 1 may optionally include that the first P2P-enabled device transmits a second response message to the second P2P-enabled device to indicate acknowledgement of the acceptance of the request.
  • Example 6 is a wireless system that includes a first peer-to-peer (P2P)-enabled device configured to wirelessly transmit a first request message containing a request requiring a response; and a second P2P-enabled device configured to wirelessly receive the first request message, wherein, upon receiving an input indicating that the first request message is to be cancelled, the first P2P-enabled device transmits a second request message to the second P2P-enabled device that includes status control information indicating that the first request has been cancelled.
  • In Example 7, the subject matter of Example 6 may optionally include that prior to transmitting the second request message, the second P2P-enabled device transmits a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 8, the subject matter of Example 6 may optionally include that the second P2P-enabled device transmits a second response message to the first P2P-enabled device to indicate acknowledgement of the cancellation of the request.
  • Example 9 is a wireless method that provides wirelessly transmitting a first request message by a first peer-to-peer (P2P) enabled device, the request message containing a request requiring a response; wirelessly receiving the first request message by a second P2P-enabled device; and wirelessly transmitting a second request message by the second P2P-enabled device to the first P2P-enabled device, in response to receiving the first request message, wherein, if the request contained in the first request message is rejected by the second P2P-enabled device, the second request message includes status control information indicating that the first request message is rejected.
  • In Example 10, the subject matter of Example 9 may optionally provide that if the request contained in the first request message is accepted by the second P2P-enabled device, the second request message omits the status control information.
  • In Example 11, the subject matter of Example 9 may optionally provide that prior to transmitting the second request message, transmitting, by the second P2P-enabled device, a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 12, the subject matter of Example 9 may optionally provide transmitting, by the first P2P-enabled device, a second response message to the second P2P-enabled device to indicate acknowledgement of the rejection of the request.
  • In Example 13, the subject matter of Example 9 may optionally provide transmitting, by the first P2P-enabled device, a second response message to the second P2P-enabled device to indicate acknowledgement of the acceptance of the request.
  • Example 14 is a wireless method that provides wirelessly transmitting a first request message by a first peer-to-peer (P2P) enabled device, the request message containing a request requiring a response; wirelessly receiving the first request message by a second P2P-enabled device; and wherein, upon receiving an input indicating that the first request message is to be cancelled, transmitting, by the first P2P-enabled device, a second request message to the second P2P-enabled device that includes status control information indicating that the first request has been cancelled.
  • In Example 15, the subject matter of Example 14 may optionally provide that prior to transmitting the second request message, transmitting, by the second P2P-enabled device, a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 16, the subject matter of Example 14 may optionally provide transmitting, by the second P2P-enabled device, a second response message to the first P2P-enabled device to indicate acknowledgement of the cancellation of the request.
  • Example 17 is a computer-readable medium comprising computer-readable instructions physically embodied thereon which, when executed by a processor, causes the processor to perform a method comprising: wirelessly transmitting a first request message by a first peer-to-peer (P2P) enabled device, the request message containing a request requiring a response; wirelessly receiving the first request message by a second P2P-enabled device; and wirelessly transmitting a second request message by the second P2P-enabled device to the first P2P-enabled device, in response to receiving the first request message, wherein, if the request contained in the first request message is rejected by the second P2P-enabled device, the second request message includes status control information indicating that the first request message is rejected.
  • In Example 18, the subject matter of Example 17 may optionally provide that if the request contained in the first request message is accepted by the second P2P-enabled device, the second request message omits the status control information.
  • In Example 19, the subject matter of Example 17 may optionally provide that prior to transmitting the second request message, transmitting, by the second P2P-enabled device, a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 20, the subject matter of Example 17 may optionally provide transmitting, by the first P2P-enabled device, a second response message to the second P2P-enabled device to indicate acknowledgement of the rejection of the request.
  • In Example 21, the subject matter of Example 17 may optionally provide transmitting, by the first P2P-enabled device, a second response message to the second P2P-enabled device to indicate acknowledgement of the acceptance of the request.
  • Example 22 is a computer-readable medium comprising computer-readable instructions physically embodied thereon which, when executed by a processor, causes the processor to perform a method comprising: wirelessly transmitting a first request message by a first peer-to-peer (P2P) enabled device, the request message containing a request requiring a response; wirelessly receiving the first request message by a second P2P-enabled device; and wherein, upon receiving an input indicating that the first request message is to be cancelled, transmitting, by the first P2P-enabled device, a second request message to the second P2P-enabled device that includes status control information indicating that the first request has been cancelled.
  • In Example 23, the subject matter of Example 22 may optionally provide that prior to transmitting the second request message, transmitting, by the second P2P-enabled device, a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 24, the subject matter of Example 22 may optionally provide transmitting, by the second P2P-enabled device, a second response message to the first P2P-enabled device to indicate acknowledgement of the cancellation of the request.
  • Example 25 is a wireless system that includes a first peer-to-peer (P2P)-enabled device configured to wirelessly transmit a first request message containing a request requiring a response; and a second P2P-enabled device configured to wirelessly receive the first request message, wherein, upon receiving the first request message, the second P2P-enabled device wirelessly transmits a second request message to the first P2P-enabled device, and wherein, if the request contained in the first request message is rejected by the second P2P-enabled device, the second request message includes status control information indicating that the first request message is rejected.
  • In Example 26, the subject matter of Example 25 may optionally include that if the request contained in the first request message is accepted by the second P2P-enabled device, the second request message omits the status control information.
  • In Example 27, the subject matter of Example 25 may optionally include that prior to transmitting the second request message, the second P2P-enabled device transmits a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 28, the subject matter of Example 25 may optionally include that the first P2P-enabled device transmits a second response message to the second P2P-enabled device to indicate acknowledgement of the rejection of the request.
  • In Example 29, the subject matter of Example 25 may optionally include that the first P2P-enabled device transmits a second response message to the second P2P-enabled device to indicate acknowledgement of the acceptance of the request.
  • Example 30 is a wireless system that includes a first peer-to-peer (P2P)-enabled device configured to wirelessly transmit a first request message containing a request requiring a response; and a second P2P-enabled device configured to wirelessly receive the first request message, wherein, upon receiving an input indicating that the first request message is to be cancelled, the first P2P-enabled device transmits a second request message to the second P2P-enabled device that includes status control information indicating that the first request has been cancelled.
  • In Example 31, the subject matter of Example 30 may optionally include that prior to transmitting the second request message, the second P2P-enabled device transmits a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 32, the subject matter of Example 30 may optionally include that the second P2P-enabled device transmits a second response message to the first P2P-enabled device to indicate acknowledgement of the cancellation of the request.
  • Example 33 is a wireless method that provides wirelessly transmitting a first request message by a first peer-to-peer (P2P) enabled device, the request message containing a request requiring a response; wirelessly receiving the first request message by a second P2P-enabled device; and wirelessly transmitting a second request message by the second P2P-enabled device to the first P2P-enabled device, in response to receiving the first request message, wherein, if the request contained in the first request message is rejected by the second P2P-enabled device, the second request message includes status control information indicating that the first request message is rejected.
  • In Example 34, the subject matter of Example 33 may optionally provide that if the request contained in the first request message is accepted by the second P2P-enabled device, the second request message omits the status control information.
  • In Example 35, the subject matter of Example 33 may optionally provide that prior to transmitting the second request message, transmitting, by the second P2P-enabled device, a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 36, the subject matter of Example 33 may optionally provide transmitting, by the first P2P-enabled device, a second response message to the second P2P-enabled device to indicate acknowledgement of the rejection of the request.
  • In Example 37, the subject matter of Example 33 may optionally provide transmitting, by the first P2P-enabled device, a second response message to the second P2P-enabled device to indicate acknowledgement of the acceptance of the request.
  • Example 38 is a wireless method that provides wirelessly transmitting a first request message by a first peer-to-peer (P2P) enabled device, the request message containing a request requiring a response; wirelessly receiving the first request message by a second P2P-enabled device; and wherein, upon receiving an input indicating that the first request message is to be cancelled, transmitting, by the first P2P-enabled device, a second request message to the second P2P-enabled device that includes status control information indicating that the first request has been cancelled.
  • In Example 39, the subject matter of Example 38 may optionally provide that prior to transmitting the second request message, transmitting, by the second P2P-enabled device, a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 40, the subject matter of Example 38 may optionally provide transmitting, by the second P2P-enabled device, a second response message to the first P2P-enabled device to indicate acknowledgement of the cancellation of the request.
  • Example 41 is a computer-readable medium comprising computer-readable instructions physically embodied thereon which, when executed by a processor, causes the processor to perform a method comprising: wirelessly transmitting a first request message by a first peer-to-peer (P2P) enabled device, the request message containing a request requiring a response; wirelessly receiving the first request message by a second P2P-enabled device; and wirelessly transmitting a second request message by the second P2P-enabled device to the first P2P-enabled device, in response to receiving the first request message, wherein, if the request contained in the first request message is rejected by the second P2P-enabled device, the second request message includes status control information indicating that the first request message is rejected.
  • In Example 42, the subject matter of Example 41 may optionally provide that if the request contained in the first request message is accepted by the second P2P-enabled device, the second request message omits the status control information.
  • In Example 43, the subject matter of Example 41 may optionally provide that prior to transmitting the second request message, transmitting, by the second P2P-enabled device, a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 44, the subject matter of Example 41 may optionally provide transmitting, by the first P2P-enabled device, a second response message to the second P2P-enabled device to indicate acknowledgement of the rejection of the request.
  • In Example 45, the subject matter of Example 41 may optionally provide transmitting, by the first P2P-enabled device, a second response message to the second P2P-enabled device to indicate acknowledgement of the acceptance of the request.
  • Example 46 is a computer-readable medium comprising computer-readable instructions physically embodied thereon which, when executed by a processor, causes the processor to perform a method comprising: wirelessly transmitting a first request message by a first peer-to-peer (P2P) enabled device, the request message containing a request requiring a response; wirelessly receiving the first request message by a second P2P-enabled device; and wherein, upon receiving an input indicating that the first request message is to be cancelled, transmitting, by the first P2P-enabled device, a second request message to the second P2P-enabled device that includes status control information indicating that the first request has been cancelled.
  • In Example 47, the subject matter of Example 46 may optionally provide that prior to transmitting the second request message, transmitting, by the second P2P-enabled device, a first response message to indicate waiting of an input responsive to the request contained in the first request message.
  • In Example 48, the subject matter of Example 46 may optionally provide transmitting, by the second P2P-enabled device, a second response message to the first P2P-enabled device to indicate acknowledgement of the cancellation of the request.
  • Example 49 is an apparatus comprising means for performing the method of claims 33-37.
  • Example 50 is an apparatus comprising means for performing the method of claims 39-40.
  • Example 51 is a computer-readable medium comprising computer-readable instructions physically embodied thereon which, when executed by a processor, causes the processor to perform the method of any of claims 33-37.
  • Example 52 is a computer-readable medium comprising computer-readable instructions physically embodied thereon which, when executed by a processor, causes the processor to perform the method of any of claims 39-40.
  • Having thus described the basic concepts, it will be rather apparent to those skilled in the art after reading this detailed disclosure that the foregoing detailed disclosure is intended to be presented by way of example only and is not limiting. Various alterations, improvements, and modifications will occur and are intended to those skilled in the art, though not expressly stated herein. These alterations, improvements, and modifications are intended to be suggested by this disclosure, and are within the spirit and scope of the exemplary embodiments of this disclosure.
  • Moreover, certain terminology has been used to describe embodiments of the present disclosure. For example, the terms “one embodiment,” “an embodiment,” and/or “some embodiments” mean that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Therefore, it is emphasized and should be appreciated that two or more references to “an embodiment” or “one embodiment” or “an alternative embodiment” in various portions of this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined as suitable in one or more embodiments of the present disclosure. In addition, the term “logic” is representative of hardware, firmware, software (or any combination thereof) to perform one or more functions. For instance, examples of “hardware” include, but are not limited to, an integrated circuit, a finite state machine, or even combinatorial logic. The integrated circuit may take the form of a processor such as a microprocessor, an application specific integrated circuit, a digital signal processor, a micro-controller, or the like.
  • Furthermore, the recited order of processing elements or sequences, or the use of numbers, letters, or other designations therefore, is not intended to limit the claimed processes and methods to any order except as can be specified in the claims. Although the above disclosure discusses through various examples what is currently considered to be a variety of useful embodiments of the disclosure, it is to be understood that such detail is solely for that purpose, and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover modifications and equivalent arrangements that are within the spirit and scope of the disclosed embodiments.
  • Similarly, it should be appreciated that in the foregoing description of embodiments of the present disclosure, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the various inventive embodiments. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed subject matter requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive embodiments lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description.

Claims (16)

What is claimed is:
1. A wireless system, comprising:
a first peer-to-peer (P2P)-enabled device configured to wirelessly transmit a first request message containing a request requiring a response; and
a second P2P-enabled device configured to wirelessly receive the first request message,
wherein, upon receiving the first request message, the second P2P-enabled device wirelessly transmits a second request message to the first P2P-enabled device, and
wherein, if the request contained in the first request message is rejected by the second P2P-enabled device, the second request message includes status control information indicating that the first request message is rejected.
2. The wireless system of claim 1 wherein, if the request contained in the first request message is accepted by the second P2P-enabled device, the second request message omits the status control information.
3. The wireless system of claim 1 wherein, prior to transmitting the second request message, the second P2P-enabled device transmits a first response message to indicate waiting of an input responsive to the request contained in the first request message.
4. The wireless system of claim 1 wherein, the first P2P-enabled device transmits a second response message to the second P2P-enabled device to indicate acknowledgement of the rejection of the request.
5. The wireless system of claim 2 wherein, the first P2P-enabled device transmits a second response message to the second P2P-enabled device to indicate acknowledgement of the acceptance of the request.
6. A wireless system, comprising:
a first peer-to-peer (P2P)-enabled device configured to wirelessly transmit a first request message containing a request requiring a response; and
a second P2P-enabled device configured to wirelessly receive the first request message,
wherein, upon receiving an input indicating that the first request message is to be cancelled, the first P2P-enabled device transmits a second request message to the second P2P-enabled device that includes status control information indicating that the first request has been cancelled.
7. The wireless system of claim 6 wherein, prior to transmitting the second request message, the second P2P-enabled device transmits a first response message to indicate waiting of an input responsive to the request contained in the first request message.
8. The wireless system of claim 6, wherein the second P2P-enabled device transmits a second response message to the first P2P-enabled device to indicate acknowledgement of the cancellation of the request.
9. A wireless method, comprising:
wirelessly transmitting a first request message by a first peer-to-peer (P2P) enabled device, the request message containing a request requiring a response;
wirelessly receiving the first request message by a second P2P-enabled device; and
wirelessly transmitting a second request message by the second P2P-enabled device to the first P2P-enabled device, in response to receiving the first request message,
wherein, if the request contained in the first request message is rejected by the second P2P-enabled device, the second request message includes status control information indicating that the first request message is rejected.
10. The method of claim 9 wherein, if the request contained in the first request message is accepted by the second P2P-enabled device, the second request message omits the status control information.
11. The method of claim 9 wherein, prior to transmitting the second request message, transmitting, by the second P2P-enabled device, a first response message to indicate waiting of an input responsive to the request contained in the first request message.
12. The method of claim 9, further including transmitting, by the first P2P-enabled device, a second response message to the second P2P-enabled device to indicate acknowledgement of the rejection of the request.
13. The method of claim 10, further including transmitting, by the first P2P-enabled device, a second response message to the second P2P-enabled device to indicate acknowledgement of the acceptance of the request.
14. A wireless method, comprising:
wirelessly transmitting a first request message by a first peer-to-peer (P2P) enabled device, the request message containing a request requiring a response;
wirelessly receiving the first request message by a second P2P-enabled device; and
wherein, upon receiving an input indicating that the first request message is to be cancelled, transmitting, by the first P2P-enabled device, a second request message to the second P2P-enabled device that includes status control information indicating that the first request has been cancelled.
15. The method of claim 14 wherein, prior to transmitting the second request message, transmitting, by the second P2P-enabled device, a first response message to indicate waiting of an input responsive to the request contained in the first request message.
16. The method of claim 14, further including transmitting, by the second P2P-enabled device, a second response message to the first P2P-enabled device to indicate acknowledgement of the cancellation of the request.
US13/839,323 2012-11-02 2013-03-15 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices Abandoned US20140126470A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US201261721837P true 2012-11-02 2012-11-02
US13/839,323 US20140126470A1 (en) 2012-11-02 2013-03-15 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US13/839,323 US20140126470A1 (en) 2012-11-02 2013-03-15 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices
US14/964,682 US20160095149A1 (en) 2012-11-02 2015-12-10 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices
US15/276,392 US10028322B2 (en) 2012-11-02 2016-09-26 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices
US16/032,717 US10588169B2 (en) 2012-11-02 2018-07-11 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/964,682 Continuation US20160095149A1 (en) 2012-11-02 2015-12-10 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices

Publications (1)

Publication Number Publication Date
US20140126470A1 true US20140126470A1 (en) 2014-05-08

Family

ID=50622314

Family Applications (4)

Application Number Title Priority Date Filing Date
US13/839,323 Abandoned US20140126470A1 (en) 2012-11-02 2013-03-15 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices
US14/964,682 Abandoned US20160095149A1 (en) 2012-11-02 2015-12-10 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices
US15/276,392 Active US10028322B2 (en) 2012-11-02 2016-09-26 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices
US16/032,717 Active US10588169B2 (en) 2012-11-02 2018-07-11 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices

Family Applications After (3)

Application Number Title Priority Date Filing Date
US14/964,682 Abandoned US20160095149A1 (en) 2012-11-02 2015-12-10 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices
US15/276,392 Active US10028322B2 (en) 2012-11-02 2016-09-26 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices
US16/032,717 Active US10588169B2 (en) 2012-11-02 2018-07-11 Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices

Country Status (1)

Country Link
US (4) US20140126470A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150030012A1 (en) * 2013-07-24 2015-01-29 Funai Electric Co., Ltd. Communication device
US10028322B2 (en) 2012-11-02 2018-07-17 Intel Corporation Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105659689B (en) * 2013-08-20 2019-09-17 三星电子株式会社 Method and system for the dual role processing in wireless environment

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120215851A1 (en) * 2011-02-21 2012-08-23 Research In Motion Limited On The Managed Peer-To-Peer Sharing In Cellular Networks

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060069800A1 (en) * 2004-09-03 2006-03-30 Microsoft Corporation System and method for erasure coding of streaming media
CN101273342A (en) 2005-05-10 2008-09-24 文卡特·斯里尼瓦斯·米纳瓦里 System for controlling multimedia function and service of telephone based on SIP and its improving method
US8077683B2 (en) * 2005-11-03 2011-12-13 Interdigital Technology Corporation Method and system for performing peer-to-peer communication between stations within a basic service set
EP2092693A1 (en) * 2006-10-17 2009-08-26 Panasonic Corporation System and method for mobility in multihop networks
US20080189429A1 (en) * 2007-02-02 2008-08-07 Sony Corporation Apparatus and method for peer-to-peer streaming
TWI578811B (en) * 2009-03-12 2017-04-11 內數位專利控股公司 Method and apparatus for performing component carrier-specific reconfiguration
EP2484098B1 (en) * 2009-09-30 2018-04-11 Orange Data sharing method and system
WO2011126321A2 (en) * 2010-04-07 2011-10-13 엘지전자 주식회사 Group-based m2m communication method
US8352563B2 (en) * 2010-04-29 2013-01-08 Damaka, Inc. System and method for peer-to-peer media routing using a third party instant messaging system for signaling
EP2577887A4 (en) * 2010-05-26 2016-11-16 Lg Electronics Inc Nas-based signaling protocol for overload protection of random access in massive machine type communication
US9265078B2 (en) * 2011-05-02 2016-02-16 Lg Electronics Inc. Method for performing device-to-device communication in wireless access system and apparatus therefor
US8930514B2 (en) * 2011-06-10 2015-01-06 Blackberry Limited System and method for conducting peer-to-peer (P2P) communications
US20140126470A1 (en) 2012-11-02 2014-05-08 Emily Qi Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120215851A1 (en) * 2011-02-21 2012-08-23 Research In Motion Limited On The Managed Peer-To-Peer Sharing In Cellular Networks

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10028322B2 (en) 2012-11-02 2018-07-17 Intel Corporation Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices
US10588169B2 (en) 2012-11-02 2020-03-10 Intel Corporation Mechanism to enable rejection and cancellation of request actions from wireless peer-to-peer devices
US20150030012A1 (en) * 2013-07-24 2015-01-29 Funai Electric Co., Ltd. Communication device

Also Published As

Publication number Publication date
US10028322B2 (en) 2018-07-17
US10588169B2 (en) 2020-03-10
US20160095149A1 (en) 2016-03-31
US20170013662A1 (en) 2017-01-12
US20190045563A1 (en) 2019-02-07

Similar Documents

Publication Publication Date Title
US10177601B2 (en) Systems and methods for wireless power distribution allocation
US10250647B2 (en) Device triggering
EP3000217B1 (en) Electronic device using logical channels for communication
ES2440370B2 (en) Timeout management in a congested wireless communication network
TWI552634B (en) Server and user equipment of enabling direct transport layer connectivity and computer program product thereof
JP6105022B2 (en) Wireless docking
US9559548B2 (en) Cover member, electronic device, and method for wireless charging
EP2523475B1 (en) Zero-Click Sharing of Application Context Across Devices
CN103782652B (en) Small data communication in cordless communication network
US10142750B2 (en) Swapping roles between untethered wirelessly connected devices
EP2695327B1 (en) Systems and methods for implementing multicasting using personal area network (pan) wireless technology
EP2911460B1 (en) Communication apparatus, method of controlling a communication apparatus, and computer program
US8271662B1 (en) Selective pairing of devices using short-range wireless communication
EP3011724B1 (en) Context management
US9713043B2 (en) Electronic device and a method of operating the same
US10261934B2 (en) Method and apparatus for providing interface
KR101080359B1 (en) Method of reestabllishing radio resource control(RRC) connection for emergency call in LTE network
US8509809B2 (en) Third party device location estimation in wireless communication networks
TWI605691B (en) Method, apparatus and system for handling in-device coexistence interference in a wireless network
JP6508591B2 (en) Method and apparatus for reestablishing a tunnel direct link setup (TDLS) session between devices in a wireless network
EP2987387B1 (en) System, method, and device for exposing wireless module data storage
US9729999B2 (en) Cross-layer context management
JP5989811B2 (en) Power saving mechanisms for peer-to-peer communication networks
US7778170B2 (en) Spectrum and medium access allocation for fairness
CN103907394B (en) Method and apparatus for delivering the transmission of small data payload and triggering small data payload within a wireless communication network

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTEL CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:QI, EMILY;VALLABHU, VENKATA;LEE, RITA;SIGNING DATES FROM 20130312 TO 20130320;REEL/FRAME:030558/0127

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION