|Publication number||US7957287 B2|
|Application number||US 11/464,449|
|Publication date||Jun 7, 2011|
|Filing date||Aug 14, 2006|
|Priority date||Aug 14, 2006|
|Also published as||US20080037480|
|Publication number||11464449, 464449, US 7957287 B2, US 7957287B2, US-B2-7957287, US7957287 B2, US7957287B2|
|Original Assignee||Intel Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (32), Non-Patent Citations (4), Referenced by (9), Classifications (14), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention pertains to wireless communication systems. Some embodiments relate to broadcasting content in broadband wireless access (BWA) networks. Some embodiments relate to non-single-frequency network (SFN) operations. Some embodiments relate to internet protocol (IP) multicasting using an internet group management protocol (IGMP).
In some conventional wireless access networks, each base station independently communicates with associated mobile stations. Each mobile station generally communicates with one base station at a time and may receive broadcast content from that one base station.
One problem with these conventional networks is that is difficult for a mobile station to join a multicast session. Another problem with these conventional networks is that when a mobile station roams between base stations, a handover is performed. The handover may interrupt the flow of the broadcast content.
Thus, there are general needs for wireless access networks and methods that allow mobile stations to easily join multicast sessions and perform handovers among base stations without interrupting the flow of the broadcast content.
The following description and the drawings sufficiently illustrate specific embodiments of the invention to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments of the invention set forth in the claims encompass all available equivalents of those claims. Embodiments of the invention may be referred to herein, individually or collectively, by the term “invention” merely for convenience and without intending to limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed.
In some embodiments, base stations 104 may be non-SFN base stations. In these embodiments, each base station 102 may operate independently from the other base stations 104 for multicast transmissions and there is no requirement for base stations 104 to synchronize the time and frequency of their multiple-access transmissions, as is the case in SFN operations.
CSN 110 may include multicast session directory 111 which may be stored on a directory server. Multicast session directory 111 may be used by mobile station 102 to determine the multicast IP address of a multicast session that mobile station 102 wishes to join. In some embodiments, ASN 120 may also include session description protocol (SDP) proxy 113. In these embodiments, mobile station 102 may use primitives of the SDP to contact SDP proxy 113 and browse the current contents of multicast session directory 111, although the scope of the invention is not limited in this respect. As illustrated in
In some embodiments, routers 118 may establish multicast groups, such as multicast group 103. A multicast group may include mobile stations 102 that have joined a multicast session. This is described in more detail below.
Base stations 104 may include one or more antennas for transmitting to mobile stations 102. The one or more antennas may comprise one or more directional or omnidirectional antennas, including, for example, dipole antennas, monopole antennas, patch antennas, loop antennas, microstrip antennas or other types of antennas suitable for transmission of RF signals. In some multiple-input, multiple-output (MIMO) embodiments, two or more antennas may be used. In some embodiments, instead of two or more antennas, a single antenna with multiple apertures may be used. In these embodiments, each aperture may be considered a separate antenna. In some embodiments, each antenna may be effectively separated to take advantage of spatial diversity and the different channel characteristics that may result between each of antennas and another wireless communication device.
As illustrated in
Mobile station 102 may send a dynamic service addition request message (DSA-REQ), such as DSA-REQ 202, to serving base station 104 to obtain a data connection identifier (CID) from serving base station 104. The data CID may be provided by base station 104 in a dynamic service addition response message (DSA-RSP), such as DSA-RSP 203. Messages 202 and 203 are an optional part of procedure 200 and may be performed when a mobile station does not already have a CID.
When mobile station 102 wishes to join an existing multicast session, mobile station 102 may send a request to join message, such as IGMP join message 204, requesting to join a multicast session. The request to join message may be received on an open data CID, such as the data CID discussed above, and the request to join message may include a multicast IP address of the existing multicast session or group mobile station 10 is requesting to join.
Prior to transmitting the request to join message, mobile station 102 may have been allowed to browse the contents of session directory 111 (
When serving base station 104 doesn't have IGMP router functionality, message 204 may be blindly forwarded as IGMP join message 206 to an ASN gateway which may have IGMP router functionality. When serving base station 104 does have IGMP router functionality, it may perform the operations of an IGMP router.
At serving base station 104, a dynamic service addition request message, such as DSA-REQ message 208 may be received from mobile station 102 on a primary management CID. The dynamic service addition request message indicates to serving base station 104 that mobile station 102 is requesting a multicast CID. In response, serving base station 104 may establish a multicast CID for use on the airlink between mobile station 102 and serving base station 104. The multicast CID, previously sent by mobile station 102, may be used for mapping packets of the existing multicast session to the multicast IP address to mobile station 102. In these embodiments, DSA-REQ message 208 is used for obtaining a multicast CID, rather than a unicast CID. The multicast CID may be provided to mobile station 102 in response message 210, which may be a DSA-RSP message or a multicast allocation response (MCA-RSP) message.
After receipt of message 206 by router 118, IP multicast data 222, which may be sent on a multicast IP address from multicast source 112, may be routed by router 118 to serving base station 104 as IP multicast data 224. Serving base station 104, in operation 225, may encapsulate the packets in the multicast CID established above for transmission to mobile station 102 as IP multicast data 226. In some embodiments, IP multicast data 226 may be transmitted to one or more mobile stations that are part of the current multicast session. These mobile stations may be associated to the same base station or may be associated with different base stations.
In some embodiments, the multicast CID may be created as a new multicast CID when mobile station 102 is a first mobile station served by serving base station 104 requesting to join the multicast session. In these embodiments, serving base station 104 may refrain from creating a new multicast CID for use in mapping packets to the multicast IP address when one or more other mobile stations currently being served by serving base station 104 are part of the multicast session. In these embodiments, serving base station 104 may provide an existing multicast CID to mobile station 102 within response message 210.
During data flow portion 320, mobile station 102 may continue to receive IP multicast data 226 sent on a multicast CID as discussed above. In operation 302, a handover procedure may be initiated by either mobile station 102 or serving base station 104A. The handover procedure may include the initiating party sending a handover request and the other party responding with a handover response. As part of operation 302, a target base station, such as target base station 104B, is identified.
As part of the handover procedure, operation 304 is performed. In operation 304, router 118 may add or update an entry in its multicast routing table so that packets having the IP multicast address of the current IP multicast session associated with serving base station 104A, are subsequently also routed to the IP address (e.g., the R6 interface) of target base station 104B.
In addition, router 118 may check if there are any other mobile stations that are currently receiving packets of the IP multicast session after the handover of mobile station 102. In some embodiments, router 118 may send a query message, such as an IGMP query message, to each mobile station associated with serving base station 104A. Mobile stations currently receiving the IP multicast session may respond with an IGMP report message. When router 118 receives any IGMP report messages from mobile stations currently receiving the IP multicast session, it may refrain from making further changes to its routing table. When router 118 does not receive any IGMP report messages from mobile stations, an entry may be removed from its routing table so that packets having the IP multicast address of the current IP multicast session will no longer be routed to serving base station 104A. In other words, the R6 interface of serving base station 104A may be pruned.
After the completion of operation 304, IP multicast data 306 of the current IP multicast session may be routed from router 118 to target base station 104B as IP multicast data 308. In operation 310, target base station 104B may encapsulate the IP multicast data with the same multicast CID as IP multicast data 226. Accordingly, encapsulated IP multicast data 312 may be received by mobile station 102.
In operation 402, a handover procedure is performed to handover mobile station 102 from serving gateway 108A to target gateway 108B. Serving gateway 108A and target gateway 108B may be gateways within the same ASN, such as ASN 120 (
In operation 404, the multicast routing table of an IGMP router associated with target gateway 108B is updated allowing gateway 108B to become the serving gateway. In some embodiments, this is achieved by sending IGMP-proxy-join message 406 by serving gateway 108A to target gateway 108B. The multicast routing table of the IGMP router associated with serving gateway 108A may be pruned to remove routing of the IP multicast session for mobile station 102 so that gateway 108A is no longer the serving gateway. Pruning the IP multicast session is performed at serving gateway 108A (i.e., the prior serving gateway) in the event that there are no other mobile stations listening to the IP multicast session through any of the base stations associated with prior serving gateway 108A. Prior to pruning, the router may use query and response messages as discussed above to determine if there are mobile stations receiving the IP multicast session. In these embodiments, no interface updates are needed for serving base station 104 because base station 104 will continue to receive IP multicast data 410 with the same multicast CID as IP multicast data 224 prior to the handover. In these embodiments, no interface updates are needed for mobile station 102 because mobile station 102 will continue to receive IP multicast data 414 with the same multicast CID as IP multicast data 224 prior to the handover. As illustrated in data flow portion 430, target gateway 108B (now the serving gateway) directly receives IP multicast data 408 from multicast source 112, and sends IP multicast data 410 on the multicast CID to serving base station 104. As part of operation 412, serving base station 104 may encapsulate the packets in the multicast CID for transmission to mobile station 102 as IP multicast data 412.
In some embodiments, mobile stations 102 may be part of a portable wireless communication device, such as a personal digital assistant (PDA), a laptop or portable computer with wireless communication capability, a web tablet, a wireless telephone, a wireless headset, a pager, an instant messaging device, a digital camera, an access point, a television, a medical device (e.g., a heart rate monitor, a blood pressure monitor, etc.), or other device that may receive and/or transmit information wirelessly.
In some embodiments, the frequency spectrums for the communication signals communicated by base stations 104 and mobile stations 102 may comprise either a 5 gigahertz (GHz) frequency spectrum or a 2.4 GHz frequency spectrum. In these embodiments, the 5 gigahertz (GHz) frequency spectrum may include frequencies ranging from approximately 4.9 to 5.9 GHz, and the 2.4 GHz spectrum may include frequencies ranging from approximately 2.3 to 2.5 GHz, although the scope of the invention is not limited in this respect, as other frequency spectrums are also equally suitable. In some BWA network embodiments, the frequency spectrum for the communication signals may comprise frequencies between 2 and 11 GHz, although the scope of the invention is not limited in this respect.
In some broadband wireless access network embodiments, base stations 104 and mobile stations 102 may communicate in accordance with the IEEE 802.16-2004 and the IEEE 802.16(e) standards for wireless metropolitan area networks (WMANs) including variations and evolutions thereof, although the scope of the invention is not limited in this respect as they may also be suitable to transmit and/or receive communications in accordance with other techniques and standards. For more information with respect to the IEEE 802.16 standards, please refer to “IEEE Standards for Information Technology—Telecommunications and Information Exchange between Systems”—Metropolitan Area Networks—Specific Requirements—Part 16: “Air Interface for Fixed Broadband Wireless Access Systems,” May 2005 and related amendments/versions.
Unless specifically stated otherwise, terms such as processing, computing, calculating, determining, displaying, or the like, may refer to an action and/or process of one or more processing or computing systems or similar devices that may manipulate and transform data represented as physical (e.g., electronic) quantities within a processing system's registers and memory into other data similarly represented as physical quantities within the processing system's registers or memories, or other such information storage, transmission or display devices. Furthermore, as used herein, a computing device includes one or more processing elements coupled with computer-readable memory that may be volatile or non-volatile memory or a combination thereof.
Some embodiments of the invention may be implemented in one or a combination of hardware, firmware and software. Some embodiments of the invention may also be implemented as instructions stored on a computer-readable storage medium, which may be read and executed by at least one processor to perform the operations described herein. A computer-readable storage medium may include any mechanism for storing information in a form readable by a machine (e.g., a computer). For example, a computer-readable storage medium may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, and flash-memory devices.
The Abstract is provided to comply with 37 C.F.R. Section 1.72(b) requiring an abstract that will allow the reader to ascertain the nature and gist of the technical disclosure. It is submitted with the understanding that it will not be used to limit or interpret the scope or meaning of the claims.
In the foregoing detailed description, various features are occasionally grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments of the subject matter require more features than are expressly recited in each claim. Rather, as the following claims reflect, invention may lie in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate preferred embodiment.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US7424283||Apr 22, 2004||Sep 9, 2008||Sprint Spectrum L.P.||Method and system for billing for multicast communications to wireless terminals|
|US7454518 *||Sep 12, 2000||Nov 18, 2008||Nortel Networks Limited||System, device, and method for receiver access control in a multicast communication network|
|US7489977||Dec 19, 2006||Feb 10, 2009||Fieldbus Foundation||System and method for implementing time synchronization monitoring and detection in a safety instrumented system|
|US20050010676||Jun 30, 2003||Jan 13, 2005||Muthaiah Venkatachalam||Time-based transmission queue for traffic management of asynchronous transfer mode virtual circuits on a multi-threaded, multi-processor system|
|US20050013280||Jul 14, 2003||Jan 20, 2005||Buddhikot Milind M.||Method and system for mobility across heterogeneous address spaces|
|US20050129020||Dec 11, 2003||Jun 16, 2005||Stephen Doyle||Method and system for providing data communications over a multi-link channel|
|US20050129054||Dec 16, 2003||Jun 16, 2005||Muthaiah Venkatachalam||Method and apparatus to implement operation and maintenance (OAM) functions on a network processor|
|US20050149602||Dec 16, 2003||Jul 7, 2005||Intel Corporation||Microengine to network processing engine interworking for network processors|
|US20060221978||Mar 31, 2005||Oct 5, 2006||Muthaiah Venkatachalam||Backlogged queue manager|
|US20060239265 *||Apr 25, 2006||Oct 26, 2006||Samsung Electronics Co., Ltd.||System and method for providing broadcast service in a mobile communication system|
|US20070086434||Oct 19, 2005||Apr 19, 2007||Muthaiah Venkatachalam||Efficient mechanisms for supporting VoIp in a wireless network|
|US20070087767||Oct 17, 2005||Apr 19, 2007||Sameer Pareek||Techniques to manage paging operations for idle mode mobile stations|
|US20070097205||Oct 31, 2005||May 3, 2007||Intel Corporation||Video transmission over wireless networks|
|US20070099635||Oct 31, 2005||May 3, 2007||Shantidev Mohanty||Method and apparatus to implement efficient paging in a wireless network|
|US20070104129||Nov 4, 2005||May 10, 2007||Xiangying Yang||Systems and techniques for improved data throughput in a wireless network|
|US20070104130||Nov 4, 2005||May 10, 2007||Muthaiah Venkatachalam||Uplink throughput for wireless network interfaces|
|US20070104131||Nov 4, 2005||May 10, 2007||Puthenkulam Jose P||Dynamic packet error management for wireless communications|
|US20070104132||Nov 7, 2005||May 10, 2007||Bala Rajagopalan||Techniques capable of providing efficient scheduling of packet data traffic in wireless data networks|
|US20070104221||Nov 4, 2005||May 10, 2007||Venkatachaiam Muthaiah||Base station and method for allocating bandwidth in a broadband wireless network with reduced latency|
|US20070105567||Nov 8, 2005||May 10, 2007||Shantidev Mohanty||Techniques for location management and paging in a communication system|
|US20070105600||Nov 8, 2005||May 10, 2007||Shantidev Mohanty||Techniques to communicate information between foreign agents and paging controllers|
|US20070121567||Nov 15, 2005||May 31, 2007||Intel Corporation||Method and apparatus for improving RF coverage area in a wireless network|
|US20070133530||Jan 18, 2006||Jun 14, 2007||Stefano Previdi||Acknowledgement-based rerouting of multicast traffic|
|US20070191031||Feb 13, 2006||Aug 16, 2007||Shantidev Mohanty||Protocols for communication between paging controllers and paging agents during idle mode paging operations in a wireless network|
|US20070230326||Mar 31, 2006||Oct 4, 2007||Puneet Pandoh||Method constructing a downlink frame for a communication system|
|US20070245025||Apr 17, 2006||Oct 18, 2007||Muthaiah Venkatachalam||Methods and apparatus for resource management architectures for Internet protocol based radio access networks|
|US20070253351||May 1, 2006||Nov 1, 2007||Oswal Anand K||Automatically Discovering Devices Of A Wimax Network System|
|US20070259692||May 9, 2006||Nov 8, 2007||Muthaiah Venkatachalam||Radio resource management architectures for internet protocol based radio access networks with radio resource control in base stations|
|US20070268863||May 19, 2006||Nov 22, 2007||Muthaiah Venkatachalam||Wireless access network and method for handover of mobile terminals in idle mode|
|US20070298806||Jun 26, 2006||Dec 27, 2007||Muthaiah Venkatachalam||Methods and apparatus for location based services in wireless networks|
|US20080019312||Jul 18, 2006||Jan 24, 2008||Muthaiah Venkatachalam||Efficient mechanisms for mapping harq connections to mac layer connections and scheduling in the presence of harq|
|US20080056219||Aug 29, 2006||Mar 6, 2008||Muthaiah Venkatachalam||Broadband wireless access network and methods for joining multicast broadcast service sessions within multicast broadcast service zones|
|1||"U.S. Appl. No. 11/468,210 Non Final Office Action Mailed Jul. 23, 2009", 22 pgs.|
|2||"U.S. Appl. No. 11/468,210, Final Office Action mailed Jan. 28, 2010", 22 pgs.|
|3||"U.S. Appl. No. 11/468,210, Response filed Apr. 21, 2010 to Final Office Action mailed Jan. 28, 2010", 11 pgs.|
|4||"U.S. Appl. No. 11/468,210, Response filed Oct. 7, 2009 to Non Final Office Action mailed Jul. 23, 2009", 12 pgs.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US8208444 *||Jul 23, 2009||Jun 26, 2012||Huawei Technologies Co., Ltd.||Method, communication system, and network entity for group nodes handover|
|US8599683 *||Mar 16, 2012||Dec 3, 2013||Fujitsu Limited||System and method for changing a delivery path of multicast traffic|
|US9137045 *||Nov 14, 2012||Sep 15, 2015||Huawei Technologies Co., Ltd.||Ethernet multicast method and device|
|US20080056219 *||Aug 29, 2006||Mar 6, 2008||Muthaiah Venkatachalam||Broadband wireless access network and methods for joining multicast broadcast service sessions within multicast broadcast service zones|
|US20090285182 *||Jul 23, 2009||Nov 19, 2009||Guohui Zou||Method, communication system, and network entity for group nodes handover|
|US20120263035 *||Mar 16, 2012||Oct 18, 2012||Fujitsu Limited||System and method for changing a delivery path of multicast traffic|
|US20130070767 *||Nov 14, 2012||Mar 21, 2013||Huawei Technologies Co., Ltd.||Ethernet multicast method and device|
|CN103797729A *||Mar 30, 2012||May 14, 2014||Lg电子株式会社||Method for receiving multicast service and terminal employing same|
|CN103797729B *||Mar 30, 2012||Oct 26, 2016||Lg电子株式会社||接收多播服务的方法和采用该方法的终端|
|U.S. Classification||370/232, 370/217, 370/432, 709/244, 370/390, 709/249, 709/250|
|International Classification||H04W4/06, H04L12/56, H04W36/08|
|Cooperative Classification||H04W72/005, H04W36/08, H04L12/185|
|Mar 5, 2008||AS||Assignment|
Owner name: INTEL CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VENKATACHALAM, MUTHAIAH;REEL/FRAME:020606/0116
Effective date: 20060928
|Aug 2, 2011||CC||Certificate of correction|
|Nov 19, 2014||FPAY||Fee payment|
Year of fee payment: 4