US20120182984A1 - Network allocation - Google Patents
Network allocation Download PDFInfo
- Publication number
- US20120182984A1 US20120182984A1 US13/431,889 US201213431889A US2012182984A1 US 20120182984 A1 US20120182984 A1 US 20120182984A1 US 201213431889 A US201213431889 A US 201213431889A US 2012182984 A1 US2012182984 A1 US 2012182984A1
- Authority
- US
- United States
- Prior art keywords
- communications device
- cts
- signal
- rts
- send
- 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
Links
- 238000004891 communication Methods 0.000 claims abstract description 150
- 238000000034 method Methods 0.000 claims abstract description 16
- 238000010586 diagram Methods 0.000 description 24
- 230000004044 response Effects 0.000 description 9
- 230000008569 process Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 239000004065 semiconductor Substances 0.000 description 2
- 239000000872 buffer Substances 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/08—Non-scheduled access, e.g. ALOHA
- H04W74/0808—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA]
- H04W74/0816—Non-scheduled access, e.g. ALOHA using carrier sensing, e.g. carrier sense multiple access [CSMA] with collision avoidance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W74/00—Wireless channel access
- H04W74/002—Transmission of channel access control information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/20—Control channels or signalling for resource management
Definitions
- IEEE 802.11 As wireless communications have increased, utilization of IEEE 802.11 protocols has also increased.
- a network allocation vector (NAV) may be utilized to reduce the probability of interference.
- NAV network allocation vector
- a NAV that is updated by a request to send (RTS) message may be undesirably reset by receivers if a valid physical layer (PHY) header is not received within a certain timeout.
- one embodiment of a method includes receiving, at a first communications device, without a prior RTS signal being sent, a first clear to send (CTS) signal from a second communications device, addressed to the first communications device, the CTS signal indicating a data exchange duration and sending a second CTS signal, from the first communications device, to the second communications device.
- CTS clear to send
- Some embodiments include receiving logic configured to receive, at a first communications device, without a prior request to send (RTS) signal being sent, a first clear to send (CTS) signal from a second communications device, addressed to the first communications device, the CTS signal indicating a data exchange duration and first sending logic configured to send a second CTS signal, from the first communications device, to the second communications device.
- RTS request to send
- CTS clear to send
- Some embodiments include means for receiving, at a first communications device, without a prior request to send (RTS) signal being sent, a first clear to send (CTS) signal from a second communications device, addressed to the first communications device, the CTS signal indicating a data exchange duration and means for sending a second CTS signal, from the first communications device, to the second communications device.
- RTS request to send
- CTS clear to send
- FIG. 1 depicts a diagram illustrating an exemplary embodiment of a network configuration that may be utilized for wireless communications.
- FIG. 2 depicts a functional block diagram illustrating a communications device, similar to the communications device 102 from FIG. 1 .
- FIG. 3A depicts a flow diagram illustrating an exemplary embodiment of a data exchange between two communications devices, such as in the network configuration of FIG. 1 .
- FIG. 3B depicts a flow diagram illustrating an exemplary embodiment of a communication of a clear to send (CTS) signal followed by a request to send (RTS) signal, similar to the diagram from FIG. 3A .
- CTS clear to send
- RTS request to send
- FIG. 3C depicts a flow diagram illustrating an exemplary embodiment of a broadcast CTS being received at a communications device, similar to the diagram from FIG. 3B .
- FIG. 3D depicts a flow diagram illustrating an exemplary embodiment of a plurality of CTS signals being sent, in response to a received CTS signal, similar to the diagram from FIG. 3C .
- FIG. 4 depicts a flowchart illustrating an exemplary embodiment of a process for sending a clear to send (CTS) signal followed by a request to send (RTS) signal, similar to the diagram from FIG. 3B .
- CTS clear to send
- RTS request to send
- FIG. 5 depicts a flowchart illustrating an exemplary embodiment of a process for sending a broadcast CTS that is received at a communications device, similar to the diagram from FIG. 3C .
- FIG. 6 depicts a flowchart illustrating an exemplary embodiment of a process for sending a plurality of CTS signals, in response to a received CTS signal, similar to the diagram from FIG. 3D .
- Embodiments disclosed herein may be configured to transmit a frame addressed to a recipient, followed by the RTS message addressed to the same recipient, wherein the endpoint of the duration field of a request to send (RTS) does not exceed that of a clear to send (CTS).
- some embodiments may be configured to transmit a clear to send (CTS) message addressed to a recipient, which is not a response to an RTS from that recipient.
- the recipient may transmit a CTS back to the sender of the first CTS.
- some embodiments may be configured to transmit a CTS addressed to the node and transmit a following RTS to the same recipient (referred to as a CTS-to-AP if the addressee is an access point).
- the CTS-to-AP configuration may be configured to set a non-resetting NAV (because updated from a CTS) at the other devices but not at the addressed node (e.g., the access point), so that the addressed device can still respond to a following RTS
- the RTS does not update the NAV at stations other than the addressed recipient when the endpoint of the duration field does not exceed that of the preceding CTS.
- FIG. 1 depicts a diagram illustrating an exemplary embodiment of a network configuration that may be utilized for wireless communications.
- network 100 may be coupled to access points 110 a and 110 b .
- the access points 110 a and 110 b can be configured to provide wireless communications to communications devices 102 a, 102 b, 102 c and/or 102 d. More specifically, depending on the particular configuration, access points 110 a and/or 110 b may be configured for providing voice over internet protocol (VoIP) services, wireless fidelity (WIFI) services, WiMAX services, wireless session initiation protocol (SIP) services, bluetooth services and/or other wireless communication services.
- VoIP voice over internet protocol
- WIFI wireless fidelity
- SIP wireless session initiation protocol
- bluetooth services wireless communication services
- the server 106 may be configured as a web server. SIP server, and/or other type of server.
- the network 100 may include a public switched telephone Network (PSTN), an integrated services digital Network (ISDN), the Internet, a cellular network, and/or other mediums for communicating data between communication devices. More specifically, as a nonlimiting example, while the communications devices 102 a and 102 d may be configured for VVIFI communications, communications devices 102 c, 102 d, and/or 106 may be coupled to the network 100 and may be configured for VoIP communications, bluetooth communications, WIFI communications, and/or other wireline and/or wireless communications.
- PSTN public switched telephone Network
- ISDN integrated services digital Network
- FIG. 2 depicts a functional block diagram illustrating a communications device, similar to the communications device 102 from FIG. 1 .
- the communications device 102 may include a processor 282 , a memory component 284 , a display interface 294 , a data storage component 295 , and one or more input and/or output (I/O) device interface(s) 296 that are communicatively coupled via a local interface 292 .
- the local interface 292 can include, for example but not limited to, one or more buses and/or other wired or wireless connections.
- the local interface 292 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable communications. Further, the local interface 292 may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.
- the processor 282 may be a hardware device for executing software, particularly software stored in the memory component 284 .
- the processor 282 can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the communications device 102 , a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, or generally any device for executing instructions.
- CPU central processing unit
- auxiliary processor among several processors associated with the communications device 102
- semiconductor based microprocessor in the form of a microchip or chip set
- macroprocessor or generally any device for executing instructions.
- the memory component 284 can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, VRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape. CD-ROM, etc.). Moreover, the memory component 284 may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that the memory component 284 can also have a distributed architecture, where various components are situated remotely from one another, but can be accessed by the processor 282 .
- the software in the memory component 284 may include one or more separate programs, each of which includes an ordered listing of executable instructions for implementing logical functions.
- the software in the memory component 284 may include communications logic 288 , as well as an operating system 286 .
- the communications logic 288 may include receiving logic 290 configured to receive, at a first communications device, without a prior request to send (RTS) signal being sent, a first clear to send (CTS) signal from a second communications device, addressed to the first communications device, the CTS signal indicating a data exchange duration.
- sending logic 293 configured to send a second CTS signal, from the first communications device, to the second communications device.
- Other components may also be included.
- logic components 290 , 291 , and 293 are each illustrated in this nonlimiting example as a single piece of logic, these components can include one or more separate software, hardware, and/or firmware modules. Similarly, one or more of these logical components can be combined to provide the desired functionality. Additionally, the operating system 286 may be configured to control the execution of other computer programs and may be configured to provide scheduling, input-output control, file and data management, memory management, and communication control and related services.
- a system component embodied as software may also be construed as a source program, executable program (object code), script, and/or any other entity that includes a set of instructions to be performed.
- the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the volatile and nonvolatile memory 284 , so as to operate properly in connection with the operating system 286 .
- the input/output devices that may be coupled to system I/O Interface(s) 296 may include input devices, for example but not limited to, a keyboard, mouse, scanner, microphone, camera, proximity device, receiver, etc. Further, the input/output devices may also include output devices, for example but not limited to, a printer, display, transmitter, etc. The input/output devices may further include devices that communicate both as inputs and outputs, for instance but not limited to, a modulator/demodulator (modem for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, WIFI communications device, WiMAX communications device, bluetooth communications device, etc.
- a modulator/demodulator modem for accessing another device, system, or network
- RF radio frequency
- a network interface 298 which is coupled to local interface 292 , can be configured to communicate with a communications network, such as the network from FIG. 1 . While this communication may be facilitated via the communications device 102 , this is not a requirement.
- the network interfaces 298 may be configured for facilitating communication with one or more other devices.
- the network interface 298 may include any component configured to facilitate a connection with another device.
- the client device 102 can include the network interface 298 that includes a Personal Computer Memory Card International Association (PCMCIA) card (also abbreviated as “PC card”) for receiving a wireless network card, this is a nonlimiting example.
- PCMCIA Personal Computer Memory Card International Association
- Other configurations can include the communications hardware within the client device 102 , such that a wireless network card is unnecessary for communicating wirelessly.
- other embodiments include the network interfaces 298 for communicating via a wired connection. Such interfaces may be configured with Universal Serial Bus (USB) interfaces, serial ports, and/or other interfaces.
- USB Universal Serial Bus
- the wireless network interfaces 298 may be configured to communicate with other client devices 102 , access points 110 , and other wireless devices via a wireless local area network (WLAN) or other wireless network.
- WLAN wireless local area network
- the software in the memory component 284 may further include a basic input output system (BIOS) (omitted for simplicity).
- BIOS is a set of software routines that initialize and test hardware at startup, start the Operating System 286 , and support the transfer of data among the hardware devices.
- the BIOS is stored in ROM so that the BIOS can be executed when the communications device 102 is activated.
- the processor 282 can be configured to execute software stored within the memory component 284 , to communicate data to with the memory component 284 , and to generally control operations of the communications device 102 pursuant to the software.
- Software in memory 284 in whole or in part, may be read by the processor 282 , perhaps buffered within the processor 282 , and then executed.
- other devices can also include the components described in FIG. 2 .
- the access point 110 (which may also be seen as a communications device) can be configured with one or more of the components and/or logic described above with respect to the communications device 102 . Additionally, the access point 110 , the communications device 102 , and/or other components of FIG. 1 can include other components and/or logic for facilitating the operations described herein. Additionally, depending on the particular configuration, the access point 110 may include both a wireless interface for communicating to the client devices and a second interface for communicating with the network. The access point 110 may be combined with other network services, (e.g., network address translation (NAT), dynamic host control protocol (DHCP), routing, firewall).
- NAT network address translation
- DHCP dynamic host control protocol
- FIG. 3A depicts a flow diagram illustrating an exemplary embodiment of a data exchange between two communications devices, such as in the network configuration of FIG. 1 .
- the communications device 102 c may be configured to send a CTS-to-Self signal 302 to an access point 110 .
- the CTS-to-Self message 302 may be a CTS that is sent by a communications device 102 and addressed to the communications device 102 that send the CTS.
- the CTS signal 302 may be broadcast to and received by a plurality of communications devices, including the access point 110 .
- the access point 110 Upon receiving the CTS-to-Self signal 302 , the access point 110 can set a network allocation vector (NAV) 304 that indicates a time for data exchange.
- the NAV 304 may be set for a plurality of devices, however this is not a requirement.
- the communications device 102 c can send a request to send (RTS) signal 306 to the access point 110 .
- RTS request to send
- the access point 110 may be unable to respond.
- the data exchanges disclosed herein may involve any of communications device (e.g., communications devices 102 , server 106 , and/or access point 110 ).
- FIG. 3B depicts a flow diagram illustrating an exemplary embodiment of a communication of a clear to send (CTS) signal followed by a request to send (RTS) signal, similar to the diagram from FIG. 3A .
- the communications device 102 c can transmit a CTS signal 308 (or other short frame that does not require a response), addressed to the communications device 102 a.
- the communications device 102 c can transmit an RTS signal 310 addressed to communications device 102 a (“A”).
- the CTS signal 308 may be configured to set a non-resetting NAV with other communications devices (not shown) who may receive the CTS.
- the communications device 102 a may send a CTS signal 314 addressed to communications device 102 c, indicating that a transmission channel is clear to send data.
- the communications device 102 c can then send the data 316 .
- the data 316 can use a PHY header, which may not be backward compatible with nearby legacy devices, because the nearby legacy devices set a NAV based on the receipt of the CTS 308 and/or CTS 314 , which (in at least one exemplary embodiment) cannot be reset.
- FIG. 3C depicts a flow diagram illustrating an exemplary embodiment of a broadcast CTS being received at a communications device, similar to the diagram from FIG. 3B .
- the access point 110 may send an unsolicited CTS signal 318 , addressed to communications device 102 a.
- a communications device that receives an unsolicited CTS cannot respond to the received signal.
- the communications device 102 a can send a CTS 233 addressed to the access point 110 in response to receipt of an unsolicited CTS addressed at the device 102 a .
- the access point 110 can then transmit data 324 to the communications device 102 a.
- the unsolicited CTS 318 replaces the RTS in an RTS/CTS exchange, so that a NAV can be set in the network, which does not reset according to the NAV reset rules of the IEEE 802.11 protocol.
- FIG. 3D depicts a flow diagram illustrating an exemplary embodiment of a plurality of CTS signals being sent, in response to a received CTS signal, similar to the diagram from FIG. 3C .
- the communications device 102 c can send an unsolicited CTS 326 to the access point 110 .
- the access point 110 can then send two CTS messages 330 , 332 to the communications device 102 c.
- the first CTS message 330 may be transmitted at a first modulation (e.g., for short range transmission).
- the second CTS message 332 may be transmitted at a second modulation (e.g., for longer range transmission).
- the communications device 102 c can then send data 334 to the access point 110 .
- the second CTS response message 332 may have a PHY header that (in at least one embodiment) cannot be decoded by legacy stations, which will not reset a NAV at the legacy stations, because the NAV was set by a CTS.
- FIG. 4 depicts a flowchart illustrating an exemplary embodiment of a process for sending a clear to send (CTS) signal followed by a request to send (RTS) signal, similar to the diagram from FIG. 3B .
- the communications device 102 a can send a CTS and an RTS to the communications device 102 b (block 432 ).
- the communications device 102 b can then send a CTS to the communications device 102 a (block 436 ).
- the communications device 102 a can then send data to the communications device 102 b (block 438 ).
- FIG. 5 depicts a flowchart illustrating an exemplary embodiment of a process for sending a broadcast CTS that is received at a communications device 102 , similar to the diagram from FIG. 3C .
- the communications device 102 a can send a CTS to the communications device 102 b (block 532 ).
- the communications device 102 b can additionally send a CTS to the communications device 102 a (block 536 ).
- the communications device 102 a can then send data to the communications device 102 b (block 538 ).
- FIG. 6 depicts a flowchart illustrating an exemplary embodiment of a process for sending a plurality of CTS signals, in response to a received unsolicited CTS signal, similar to the diagram from FIG. 3D .
- the communications device 102 a can send a CTS to the communications device 102 b (block 632 ).
- the communications device 102 b can send a first CTS and a second CTS to the communications device 102 a (block 636 ).
- the communications device 102 a can then send data to the communications device 102 b (block 638 ).
- the embodiments disclosed herein can be implemented in hardware, software, firmware, or a combination thereof. At least one embodiment disclosed herein may be implemented in software and/or firmware that is stored in a memory and that is executed by a suitable instruction execution system. If implemented in hardware, one or more of the embodiments disclosed herein can be implemented with any or a combination of the following technologies: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), afield programmable gate array (FPGA), etc.
- ASIC application specific integrated circuit
- PGA programmable gate array
- FPGA field programmable gate array
- each block can be interpreted to represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
- the functions noted in the blocks may occur out of the order and/or not at all. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
- any of the programs listed herein can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions.
- a “computer-readable medium” can be any means that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
- the computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device.
- the computer-readable medium could include an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical).
- the scope of the certain embodiments of this disclosure can include embodying the functionality described in logic embodied in hardware or software-configured mediums.
- conditional language such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more particular embodiments or that one or more particular embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
- This application claims the benefit of U.S. Provisional Application No. 60/969,847, filed Sep. 4, 2007, which is incorporated by reference in its entirety.
- As wireless communications have increased, utilization of IEEE 802.11 protocols has also increased. In IEEE 802.11 communications a network allocation vector (NAV) may be utilized to reduce the probability of interference. However, according to the IEE 802.11 protocol, a NAV that is updated by a request to send (RTS) message may be undesirably reset by receivers if a valid physical layer (PHY) header is not received within a certain timeout.
- Included are embodiments for network allocation. More specifically, one embodiment of a method includes receiving, at a first communications device, without a prior RTS signal being sent, a first clear to send (CTS) signal from a second communications device, addressed to the first communications device, the CTS signal indicating a data exchange duration and sending a second CTS signal, from the first communications device, to the second communications device.
- Additionally, embodiments of a computer readable medium are included. Some embodiments include receiving logic configured to receive, at a first communications device, without a prior request to send (RTS) signal being sent, a first clear to send (CTS) signal from a second communications device, addressed to the first communications device, the CTS signal indicating a data exchange duration and first sending logic configured to send a second CTS signal, from the first communications device, to the second communications device.
- Additionally, embodiments of a system are included. Some embodiments include means for receiving, at a first communications device, without a prior request to send (RTS) signal being sent, a first clear to send (CTS) signal from a second communications device, addressed to the first communications device, the CTS signal indicating a data exchange duration and means for sending a second CTS signal, from the first communications device, to the second communications device.
- Other embodiments and/or advantages of this disclosure will be or may become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description and be within the scope of the present disclosure.
- Many aspects of the disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views. While several embodiments are described in connection with these drawings, there is no intent to limit the disclosure to the embodiment or embodiments disclosed herein. On the contrary, the intent is to cover all alternatives, modifications, and equivalents.
-
FIG. 1 depicts a diagram illustrating an exemplary embodiment of a network configuration that may be utilized for wireless communications. -
FIG. 2 depicts a functional block diagram illustrating a communications device, similar to thecommunications device 102 fromFIG. 1 . -
FIG. 3A depicts a flow diagram illustrating an exemplary embodiment of a data exchange between two communications devices, such as in the network configuration ofFIG. 1 . -
FIG. 3B depicts a flow diagram illustrating an exemplary embodiment of a communication of a clear to send (CTS) signal followed by a request to send (RTS) signal, similar to the diagram fromFIG. 3A . -
FIG. 3C depicts a flow diagram illustrating an exemplary embodiment of a broadcast CTS being received at a communications device, similar to the diagram fromFIG. 3B . -
FIG. 3D depicts a flow diagram illustrating an exemplary embodiment of a plurality of CTS signals being sent, in response to a received CTS signal, similar to the diagram fromFIG. 3C . -
FIG. 4 depicts a flowchart illustrating an exemplary embodiment of a process for sending a clear to send (CTS) signal followed by a request to send (RTS) signal, similar to the diagram fromFIG. 3B . -
FIG. 5 depicts a flowchart illustrating an exemplary embodiment of a process for sending a broadcast CTS that is received at a communications device, similar to the diagram fromFIG. 3C . -
FIG. 6 depicts a flowchart illustrating an exemplary embodiment of a process for sending a plurality of CTS signals, in response to a received CTS signal, similar to the diagram fromFIG. 3D . - Embodiments disclosed herein may be configured to transmit a frame addressed to a recipient, followed by the RTS message addressed to the same recipient, wherein the endpoint of the duration field of a request to send (RTS) does not exceed that of a clear to send (CTS). Similarly, some embodiments may be configured to transmit a clear to send (CTS) message addressed to a recipient, which is not a response to an RTS from that recipient. In response, the recipient may transmit a CTS back to the sender of the first CTS.
- Similarly, some embodiments may be configured to transmit a CTS addressed to the node and transmit a following RTS to the same recipient (referred to as a CTS-to-AP if the addressee is an access point). The CTS-to-AP configuration may be configured to set a non-resetting NAV (because updated from a CTS) at the other devices but not at the addressed node (e.g., the access point), so that the addressed device can still respond to a following RTS The RTS does not update the NAV at stations other than the addressed recipient when the endpoint of the duration field does not exceed that of the preceding CTS. This means that surrounding devices can not reset their NAV if those devices do not receive a valid physical layer (PHY) header within a certain time after hearing the RTS. So after the CTS-to-AP/RTS/CTS exchange, there may be no need to transmit a frame that can be decoded by the surrounding stations, which is what happens, for instance, when Dual CTS is used (as described in 802.11 n draft 2.0 section 9.2.5.5a).
- Referring now to the drawings,
FIG. 1 depicts a diagram illustrating an exemplary embodiment of a network configuration that may be utilized for wireless communications. As illustrated in the nonlimiting example fromFIG. 1 ,network 100 may be coupled to accesspoints access points communications devices access points 110 a and/or 110 b may be configured for providing voice over internet protocol (VoIP) services, wireless fidelity (WIFI) services, WiMAX services, wireless session initiation protocol (SIP) services, bluetooth services and/or other wireless communication services. Additionally coupled to thenetwork 100 is aserver 106. Theserver 106 may be configured as a web server. SIP server, and/or other type of server. - The
network 100 may include a public switched telephone Network (PSTN), an integrated services digital Network (ISDN), the Internet, a cellular network, and/or other mediums for communicating data between communication devices. More specifically, as a nonlimiting example, while thecommunications devices communications devices network 100 and may be configured for VoIP communications, bluetooth communications, WIFI communications, and/or other wireline and/or wireless communications. -
FIG. 2 depicts a functional block diagram illustrating a communications device, similar to thecommunications device 102 fromFIG. 1 . As illustrated inFIG. 2 , in terms of hardware architecture, thecommunications device 102 may include aprocessor 282, amemory component 284, adisplay interface 294, adata storage component 295, and one or more input and/or output (I/O) device interface(s) 296 that are communicatively coupled via alocal interface 292. Thelocal interface 292 can include, for example but not limited to, one or more buses and/or other wired or wireless connections. Thelocal interface 292 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers to enable communications. Further, thelocal interface 292 may include address, control, and/or data connections to enable appropriate communications among the aforementioned components. Theprocessor 282 may be a hardware device for executing software, particularly software stored in thememory component 284. - The
processor 282 can be any custom made or commercially available processor, a central processing unit (CPU), an auxiliary processor among several processors associated with thecommunications device 102, a semiconductor based microprocessor (in the form of a microchip or chip set), a macroprocessor, or generally any device for executing instructions. - The
memory component 284 can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, VRAM, etc.)) and nonvolatile memory elements (e.g., ROM, hard drive, tape. CD-ROM, etc.). Moreover, thememory component 284 may incorporate electronic, magnetic, optical, and/or other types of storage media. Note that thememory component 284 can also have a distributed architecture, where various components are situated remotely from one another, but can be accessed by theprocessor 282. - The software in the
memory component 284 may include one or more separate programs, each of which includes an ordered listing of executable instructions for implementing logical functions. In the example ofFIG. 2 , the software in thememory component 284 may includecommunications logic 288, as well as anoperating system 286. As illustrated, thecommunications logic 288 may include receivinglogic 290 configured to receive, at a first communications device, without a prior request to send (RTS) signal being sent, a first clear to send (CTS) signal from a second communications device, addressed to the first communications device, the CTS signal indicating a data exchange duration. Also included is sendinglogic 293 configured to send a second CTS signal, from the first communications device, to the second communications device. Other components may also be included. - Additionally, while the
logic components operating system 286 may be configured to control the execution of other computer programs and may be configured to provide scheduling, input-output control, file and data management, memory management, and communication control and related services. - A system component embodied as software may also be construed as a source program, executable program (object code), script, and/or any other entity that includes a set of instructions to be performed. When constructed as a source program, the program is translated via a compiler, assembler, interpreter, or the like, which may or may not be included within the volatile and
nonvolatile memory 284, so as to operate properly in connection with theoperating system 286. - The input/output devices that may be coupled to system I/O Interface(s) 296 may include input devices, for example but not limited to, a keyboard, mouse, scanner, microphone, camera, proximity device, receiver, etc. Further, the input/output devices may also include output devices, for example but not limited to, a printer, display, transmitter, etc. The input/output devices may further include devices that communicate both as inputs and outputs, for instance but not limited to, a modulator/demodulator (modem for accessing another device, system, or network), a radio frequency (RF) or other transceiver, a telephonic interface, a bridge, a router, WIFI communications device, WiMAX communications device, bluetooth communications device, etc. Similarly, a
network interface 298, which is coupled tolocal interface 292, can be configured to communicate with a communications network, such as the network fromFIG. 1 . While this communication may be facilitated via thecommunications device 102, this is not a requirement. - More specifically, the network interfaces 298 may be configured for facilitating communication with one or more other devices. The
network interface 298 may include any component configured to facilitate a connection with another device. While in some embodiments, among others, theclient device 102 can include thenetwork interface 298 that includes a Personal Computer Memory Card International Association (PCMCIA) card (also abbreviated as “PC card”) for receiving a wireless network card, this is a nonlimiting example. Other configurations can include the communications hardware within theclient device 102, such that a wireless network card is unnecessary for communicating wirelessly. Similarly, other embodiments include the network interfaces 298 for communicating via a wired connection. Such interfaces may be configured with Universal Serial Bus (USB) interfaces, serial ports, and/or other interfaces. In operation, the wireless network interfaces 298 may be configured to communicate withother client devices 102,access points 110, and other wireless devices via a wireless local area network (WLAN) or other wireless network. - If the
communications device 102 is a personal computer, workstation, or the like, the software in thememory component 284 may further include a basic input output system (BIOS) (omitted for simplicity). The BIOS is a set of software routines that initialize and test hardware at startup, start theOperating System 286, and support the transfer of data among the hardware devices. The BIOS is stored in ROM so that the BIOS can be executed when thecommunications device 102 is activated. - When the
communications device 102 is in operation, theprocessor 282 can be configured to execute software stored within thememory component 284, to communicate data to with thememory component 284, and to generally control operations of thecommunications device 102 pursuant to the software. Software inmemory 284, in whole or in part, may be read by theprocessor 282, perhaps buffered within theprocessor 282, and then executed. Additionally, one should note that while the above description is directed to acommunications device 102, other devices can also include the components described inFIG. 2 . - One should note that the access point 110 (which may also be seen as a communications device) can be configured with one or more of the components and/or logic described above with respect to the
communications device 102. Additionally, theaccess point 110, thecommunications device 102, and/or other components ofFIG. 1 can include other components and/or logic for facilitating the operations described herein. Additionally, depending on the particular configuration, theaccess point 110 may include both a wireless interface for communicating to the client devices and a second interface for communicating with the network. Theaccess point 110 may be combined with other network services, (e.g., network address translation (NAT), dynamic host control protocol (DHCP), routing, firewall). -
FIG. 3A depicts a flow diagram illustrating an exemplary embodiment of a data exchange between two communications devices, such as in the network configuration ofFIG. 1 . As illustrated in the nonlimiting example ofFIG. 3A , thecommunications device 102 c may be configured to send a CTS-to-Self signal 302 to anaccess point 110. The CTS-to-Self message 302 may be a CTS that is sent by acommunications device 102 and addressed to thecommunications device 102 that send the CTS. TheCTS signal 302 may be broadcast to and received by a plurality of communications devices, including theaccess point 110. Upon receiving the CTS-to-Self signal 302, theaccess point 110 can set a network allocation vector (NAV) 304 that indicates a time for data exchange. TheNAV 304 may be set for a plurality of devices, however this is not a requirement. - Additionally, the
communications device 102 c can send a request to send (RTS) signal 306 to theaccess point 110. However, because of the rules of the IEEE 802.11 protocol, theaccess point 110 may be unable to respond. - One should note that, while the above listed exchange occurs between a
communications device 102 c and anaccess point 110, this is a nonlimiting example. More specifically, the data exchanges disclosed herein may involve any of communications device (e.g.,communications devices 102,server 106, and/or access point 110). -
FIG. 3B depicts a flow diagram illustrating an exemplary embodiment of a communication of a clear to send (CTS) signal followed by a request to send (RTS) signal, similar to the diagram fromFIG. 3A . As illustrated in the nonlimiting example ofFIG. 3B , thecommunications device 102 c can transmit a CTS signal 308 (or other short frame that does not require a response), addressed to thecommunications device 102 a. Additionally, followed by theCTS signal 308, thecommunications device 102 c can transmit anRTS signal 310 addressed tocommunications device 102 a (“A”). TheCTS signal 308 may be configured to set a non-resetting NAV with other communications devices (not shown) who may receive the CTS. Thecommunications device 102 a may send aCTS signal 314 addressed tocommunications device 102 c, indicating that a transmission channel is clear to send data. Thecommunications device 102 c can then send thedata 316. Thedata 316 can use a PHY header, which may not be backward compatible with nearby legacy devices, because the nearby legacy devices set a NAV based on the receipt of theCTS 308 and/orCTS 314, which (in at least one exemplary embodiment) cannot be reset. -
FIG. 3C depicts a flow diagram illustrating an exemplary embodiment of a broadcast CTS being received at a communications device, similar to the diagram fromFIG. 3B . As illustrated in the nonlimiting example ofFIG. 3C , theaccess point 110 may send anunsolicited CTS signal 318, addressed tocommunications device 102 a. As discussed above, according to IEEE 802.11 protocol, a communications device that receives an unsolicited CTS cannot respond to the received signal. However, if a change in IEEE 802.11 protocol occurs (and/or if operating in an non-IEEE 802.11 environment), thecommunications device 102 a can send a CTS 233 addressed to theaccess point 110 in response to receipt of an unsolicited CTS addressed at thedevice 102 a. Theaccess point 110 can then transmitdata 324 to thecommunications device 102 a. In this exemplary frame exchange, theunsolicited CTS 318 replaces the RTS in an RTS/CTS exchange, so that a NAV can be set in the network, which does not reset according to the NAV reset rules of the IEEE 802.11 protocol. -
FIG. 3D depicts a flow diagram illustrating an exemplary embodiment of a plurality of CTS signals being sent, in response to a received CTS signal, similar to the diagram fromFIG. 3C . As illustrated in the nonlimiting example ofFIG. 3D , thecommunications device 102 c can send anunsolicited CTS 326 to theaccess point 110. Theaccess point 110 can then send twoCTS messages communications device 102 c. Thefirst CTS message 330 may be transmitted at a first modulation (e.g., for short range transmission). Similarly, thesecond CTS message 332 may be transmitted at a second modulation (e.g., for longer range transmission). Thecommunications device 102 c can then senddata 334 to theaccess point 110. The secondCTS response message 332 may have a PHY header that (in at least one embodiment) cannot be decoded by legacy stations, which will not reset a NAV at the legacy stations, because the NAV was set by a CTS. -
FIG. 4 depicts a flowchart illustrating an exemplary embodiment of a process for sending a clear to send (CTS) signal followed by a request to send (RTS) signal, similar to the diagram fromFIG. 3B . As illustrated in the nonlimiting example ofFIG. 4 , thecommunications device 102 a can send a CTS and an RTS to thecommunications device 102 b (block 432). Thecommunications device 102 b can then send a CTS to thecommunications device 102 a (block 436). Thecommunications device 102 a can then send data to thecommunications device 102 b (block 438). -
FIG. 5 depicts a flowchart illustrating an exemplary embodiment of a process for sending a broadcast CTS that is received at acommunications device 102, similar to the diagram fromFIG. 3C . As illustrated in the nonlimiting example ofFIG. 5 , thecommunications device 102 a can send a CTS to thecommunications device 102 b (block 532). Thecommunications device 102 b can additionally send a CTS to thecommunications device 102 a (block 536). Thecommunications device 102 a can then send data to thecommunications device 102 b (block 538). -
FIG. 6 depicts a flowchart illustrating an exemplary embodiment of a process for sending a plurality of CTS signals, in response to a received unsolicited CTS signal, similar to the diagram fromFIG. 3D . As illustrated in the nonlimiting example ofFIG. 6 , thecommunications device 102 a can send a CTS to thecommunications device 102 b (block 632). Thecommunications device 102 b can send a first CTS and a second CTS to thecommunications device 102 a (block 636). Thecommunications device 102 a can then send data to thecommunications device 102 b (block 638). - The embodiments disclosed herein can be implemented in hardware, software, firmware, or a combination thereof. At least one embodiment disclosed herein may be implemented in software and/or firmware that is stored in a memory and that is executed by a suitable instruction execution system. If implemented in hardware, one or more of the embodiments disclosed herein can be implemented with any or a combination of the following technologies: a discrete logic circuit(s) having logic gates for implementing logic functions upon data signals, an application specific integrated circuit (ASIC) having appropriate combinational logic gates, a programmable gate array(s) (PGA), afield programmable gate array (FPGA), etc.
- One should note that the flowcharts included herein show the architecture, functionality, and operation of a possible implementation of software. In this regard, each block can be interpreted to represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order and/or not at all. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
- One should note that any of the programs listed herein, which can include an ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “computer-readable medium” can be any means that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer readable medium can be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a nonexhaustive list) of the computer-readable medium could include an electrical connection (electronic) having one or more wires, a portable computer diskette (magnetic), a random access memory (RAM) (electronic), a read-only memory (ROM) (electronic), an erasable programmable read-only memory (EPROM or Flash memory) (electronic), an optical fiber (optical), and a portable compact disc read-only memory (CDROM) (optical). In addition, the scope of the certain embodiments of this disclosure can include embodying the functionality described in logic embodied in hardware or software-configured mediums.
- One should also note that conditional language, such as, among others, “can,” “could,” “might,” or “may,” unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more particular embodiments or that one or more particular embodiments necessarily include logic for deciding, with or without user input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment.
- It should be emphasized that the above-described embodiments are merely possible examples of implementations. merely set forth for a clear understanding of the principles of this disclosure. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure.
Claims (21)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/431,889 US20120182984A1 (en) | 2007-09-04 | 2012-03-27 | Network allocation |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US96984707P | 2007-09-04 | 2007-09-04 | |
US12/106,878 US8144676B2 (en) | 2007-09-04 | 2008-04-21 | Network allocation |
US13/431,889 US20120182984A1 (en) | 2007-09-04 | 2012-03-27 | Network allocation |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/106,878 Continuation US8144676B2 (en) | 2007-09-04 | 2008-04-21 | Network allocation |
Publications (1)
Publication Number | Publication Date |
---|---|
US20120182984A1 true US20120182984A1 (en) | 2012-07-19 |
Family
ID=40407314
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/106,878 Active 2030-10-16 US8144676B2 (en) | 2007-09-04 | 2008-04-21 | Network allocation |
US13/431,889 Abandoned US20120182984A1 (en) | 2007-09-04 | 2012-03-27 | Network allocation |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/106,878 Active 2030-10-16 US8144676B2 (en) | 2007-09-04 | 2008-04-21 | Network allocation |
Country Status (5)
Country | Link |
---|---|
US (2) | US8144676B2 (en) |
EP (1) | EP2193688A4 (en) |
KR (1) | KR101159434B1 (en) |
CN (1) | CN101796878B (en) |
WO (1) | WO2009032878A1 (en) |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8605692B2 (en) * | 2009-01-15 | 2013-12-10 | Electronics And Telecommunications Research Institute | Method for setting transmission opportunity and for transmitting and receiving data in wireless LAN system using multiple channel |
US8576809B2 (en) * | 2010-10-07 | 2013-11-05 | Qualcomm Incorporated | Facilitating distributed channel access for a plurality of access terminals transmitting in a wireless communication environment |
KR101517321B1 (en) * | 2011-06-08 | 2015-05-04 | 엘지전자 주식회사 | Method and device for transmitting a frame using a multiple physical layer in a wireless lan system |
CN103037531B (en) * | 2011-10-09 | 2018-03-16 | 中兴通讯股份有限公司 | A kind of method and system of wireless site access channel |
US10021600B2 (en) * | 2013-01-02 | 2018-07-10 | Qualcomm Incorporated | Backhaul traffic reliability in unlicensed bands using spectrum sensing and channel reservation |
SG11201708918UA (en) * | 2015-05-08 | 2017-11-29 | Sony Corp | Communication device and communication method |
CN113115328B (en) * | 2015-07-17 | 2023-07-18 | 华为技术有限公司 | NAV setting method and related equipment in wireless communication system |
CN110266591A (en) * | 2019-06-14 | 2019-09-20 | 陕西瑞迅电子信息技术有限公司 | A kind of edge calculations gateway method for routing, apparatus and system |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050058151A1 (en) * | 2003-06-30 | 2005-03-17 | Chihsiang Yeh | Method of interference management for interference/collision avoidance and spatial reuse enhancement |
US20070226351A1 (en) * | 2006-03-24 | 2007-09-27 | Matthew Fischer | System and method for transmitting high throughput data between multiple devices |
US7496076B2 (en) * | 2004-01-09 | 2009-02-24 | Kabushiki Kaisha Toshiba | Communication apparatus, communication method, and communication system |
US7801096B2 (en) * | 2002-05-10 | 2010-09-21 | Cisco Technology, Inc. | Detecting, reporting and mitigating hidden stations in a wireless data network |
US7881313B2 (en) * | 2002-08-26 | 2011-02-01 | Hewlett-Packard Company | Space-time-power scheduling for wireless networks |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7133381B2 (en) * | 2001-03-02 | 2006-11-07 | At&T Corp | Interference suppression methods for 802.11 |
US6977944B2 (en) * | 2002-01-12 | 2005-12-20 | Conexant, Inc. | Transmission protection for communications networks having stations operating with different modulation formats |
US20060209771A1 (en) * | 2005-03-03 | 2006-09-21 | Extricom Ltd. | Wireless LAN with contention avoidance |
US20040071154A1 (en) * | 2002-10-08 | 2004-04-15 | Wentink Maarten Menzo | Achieving high priority and bandwidth efficiency in a shared communications medium |
US20040085992A1 (en) * | 2002-11-05 | 2004-05-06 | Wentink Maarten Menzo | Shared-medium contention algorithm exhibiting fairness |
US20040085993A1 (en) * | 2002-11-05 | 2004-05-06 | Wentink Maarten Menzo | Shared-medium contention algorithm exhibiting fairness |
US7321762B2 (en) * | 2003-03-26 | 2008-01-22 | Conexant Systems, Inc. | Mechanism for reserving multiple channels of a single medium access control and physical layer |
US8274961B2 (en) * | 2003-10-24 | 2012-09-25 | Sony Corporation | Apparatus and associated methodology of adjusting a RTS/CTS transmission protocol |
US7826472B2 (en) * | 2005-02-18 | 2010-11-02 | Avaya Inc. | Methods and systems for providing priority access to 802.11 endpoints using DCF protocol |
WO2006133414A2 (en) * | 2005-06-08 | 2006-12-14 | Avaya Technology Corp. | Avoiding hidden terminals in wireless local area networks |
US8031661B2 (en) * | 2005-11-08 | 2011-10-04 | Intellectual Ventures I Llc | Symmetric transmit opportunity (TXOP) truncation |
WO2007056747A2 (en) * | 2005-11-08 | 2007-05-18 | Conexant Systems | Collision avoidance systems and methods |
JP2009519690A (en) * | 2005-12-13 | 2009-05-14 | コネクサント システムズ インク | Dual CTS protection system and method |
KR100705584B1 (en) * | 2006-01-02 | 2007-04-09 | 삼성전자주식회사 | Wireless lan and method for transmitting frames thereof |
US8305948B2 (en) * | 2006-11-15 | 2012-11-06 | Qualcomm Incorporated | Transmissions to multiple stations in wireless communication systems |
US8654773B2 (en) * | 2006-11-30 | 2014-02-18 | Conexant Systems, Inc. | Systems and methods for coexistence of WLAN and bluetooth networks |
-
2008
- 2008-04-21 US US12/106,878 patent/US8144676B2/en active Active
- 2008-09-04 CN CN2008801056204A patent/CN101796878B/en not_active Expired - Fee Related
- 2008-09-04 KR KR1020107007307A patent/KR101159434B1/en not_active IP Right Cessation
- 2008-09-04 WO PCT/US2008/075182 patent/WO2009032878A1/en active Application Filing
- 2008-09-04 EP EP08799138A patent/EP2193688A4/en not_active Withdrawn
-
2012
- 2012-03-27 US US13/431,889 patent/US20120182984A1/en not_active Abandoned
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7801096B2 (en) * | 2002-05-10 | 2010-09-21 | Cisco Technology, Inc. | Detecting, reporting and mitigating hidden stations in a wireless data network |
US7881313B2 (en) * | 2002-08-26 | 2011-02-01 | Hewlett-Packard Company | Space-time-power scheduling for wireless networks |
US20050058151A1 (en) * | 2003-06-30 | 2005-03-17 | Chihsiang Yeh | Method of interference management for interference/collision avoidance and spatial reuse enhancement |
US7496076B2 (en) * | 2004-01-09 | 2009-02-24 | Kabushiki Kaisha Toshiba | Communication apparatus, communication method, and communication system |
US20070226351A1 (en) * | 2006-03-24 | 2007-09-27 | Matthew Fischer | System and method for transmitting high throughput data between multiple devices |
Also Published As
Publication number | Publication date |
---|---|
EP2193688A1 (en) | 2010-06-09 |
KR20100059939A (en) | 2010-06-04 |
CN101796878B (en) | 2013-02-13 |
WO2009032878A1 (en) | 2009-03-12 |
US20090059824A1 (en) | 2009-03-05 |
CN101796878A (en) | 2010-08-04 |
US8144676B2 (en) | 2012-03-27 |
KR101159434B1 (en) | 2012-06-22 |
EP2193688A4 (en) | 2013-01-02 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20120182984A1 (en) | Network allocation | |
JP5536051B6 (en) | Method and apparatus for managing data services in a multiprocessor computing environment | |
US20100290391A1 (en) | Apparatus and method for accessing multiple wireless networks | |
WO2017215215A1 (en) | Method for switching downloading mode, and control method and control system therefor | |
US8320346B2 (en) | Apparatus and methods for universal services interface networking | |
KR20090085115A (en) | Wireless wide area network(wwan) mobile gateway with communication protocol management | |
US8396015B2 (en) | Scanning threshold | |
US20140177615A1 (en) | Method for scanning a wireless fidelity (wi-fi) direct device and terminal device for the same | |
US20160028584A1 (en) | Electronic device and ims service providing method thereof | |
KR20160126892A (en) | Repeating method and corresponding communication network device, system, computer readable program product and computer readable storage medium | |
EP3334194A1 (en) | Connection information broadcast using beacon technology | |
CN111641565B (en) | Method, device and system for transmitting Ethernet message | |
US20080107113A1 (en) | Set/Reset Mechanism | |
US10880947B2 (en) | Control plane latency reduction in a wireless communications network | |
US20130344809A1 (en) | Multi-profile application framework | |
WO2016004557A1 (en) | Information transmitting method, access point and station | |
WO2016106598A1 (en) | Method and apparatus for selecting access network | |
WO2023040350A1 (en) | Communication method and apparatus between cloud and internet-of-things device, and medium and product | |
TWI486050B (en) | Dual-mode wireless communication apparatus and dual-mode wireless communication method | |
WO2021087909A1 (en) | Signal transmission method and device, and mobile terminal and storage medium | |
KR100675138B1 (en) | Apparatus and method for remote upgrade of VoIP wireless LAN phone by using wireless LAN | |
KR101688995B1 (en) | Method and device for communicating data based on asymmetric transmission time | |
KR20010057065A (en) | Method for transferring data in wireless communication system | |
KR101061577B1 (en) | Local network configuration system using wired / wireless integrated terminal | |
CN114557045A (en) | Communication method and related device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., I Free format text: SECURITY AGREEMENT;ASSIGNOR:CONEXANT SYSTEMS, INC.;REEL/FRAME:028177/0453 Effective date: 20100310 |
|
AS | Assignment |
Owner name: CONEXANT SYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WENTINK, MAARTEN MENZO;REEL/FRAME:028871/0823 Effective date: 20080418 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: BROOKTREE BROADBAND HOLDING, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.;REEL/FRAME:038631/0452 Effective date: 20140310 Owner name: CONEXANT SYSTEMS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.;REEL/FRAME:038631/0452 Effective date: 20140310 Owner name: CONEXANT SYSTEMS WORLDWIDE, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.;REEL/FRAME:038631/0452 Effective date: 20140310 Owner name: CONEXANT, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.;REEL/FRAME:038631/0452 Effective date: 20140310 |
|
AS | Assignment |
Owner name: LAKESTAR SEMI INC., NEW YORK Free format text: CHANGE OF NAME;ASSIGNOR:CONEXANT SYSTEMS, INC.;REEL/FRAME:038777/0885 Effective date: 20130712 |
|
AS | Assignment |
Owner name: CONEXANT SYSTEMS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LAKESTAR SEMI INC.;REEL/FRAME:038803/0693 Effective date: 20130712 |