Source: https://patents.google.com/patent/US9332451B2/en
Timestamp: 2019-10-14 06:50:57
Document Index: 368716378

Matched Legal Cases: ['Application No. 60', 'Application No. 200910005364', 'art 11', 'art 11', 'Application No. 20055955', 'Application No. 2', 'Application No. 2', 'Application No. 08168068', 'Application No. 10154548', 'Application No. 10179384', 'Application No. 10', 'Application No. 10', 'Application No. 4964', 'Application No. 4964', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 100105695', 'Application No. 200910005364', 'Application No. 200910005364', 'Application No. 200910005364', 'Application No. 200910005364', 'Application No. 08168068', 'Application No. 10154548', 'Application No. 10179384', 'Application No. 10179384', 'Application No. 10', 'Application No. 10', 'Application No. 10', 'Application No. 2012', 'Application No. 20055955', 'Application No. 103137414', 'Application No. 2', 'Application No. 08', 'Application No. 10', 'Application No. 200910005364', 'Application No. 200910005364', 'Application No. 20055955', 'Application No. 200910005364', 'Application No. 04752031']

US9332451B2 - Method and apparatus of requesting a beacon report - Google Patents
Method and apparatus of requesting a beacon report Download PDF
US9332451B2
US9332451B2 US13/572,087 US201213572087A US9332451B2 US 9332451 B2 US9332451 B2 US 9332451B2 US 201213572087 A US201213572087 A US 201213572087A US 9332451 B2 US9332451 B2 US 9332451B2
US13/572,087
US20120307663A1 (en
2012-08-10 Application filed by Intel Corp filed Critical Intel Corp
2012-12-06 Publication of US20120307663A1 publication Critical patent/US20120307663A1/en
2013-02-22 Assigned to INTEL CORPORATION reassignment INTEL CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: INTERDIGITAL TECHNOLOGY CORPORATION
2016-05-03 Publication of US9332451B2 publication Critical patent/US9332451B2/en
230000000737 periodic Effects 0 description 55
This application is a continuation of U.S. application Ser. No. 12/763,360 filed on Apr. 20, 2010, which is a continuation of U.S. application Ser. No. 10/845,822 filed on May 14, 2004, now U.S. Pat. No. 7,710,930, which claims priority from U.S. Provisional Application No. 60/470,256 filed on May 14, 2003, which is hereby incorporated by reference.
TABLE 1 Beacon Request
TABLE 4 Reporting Condition Definitions for Beacon Request Element Reporting Condition Description Condition Report to be issued after each measurement. 0 Report to be issued when the RCPI level of the measured AP 1 crosses above an absolute threshold with hysteresis. Report to be issued when the RCPI level of the measured AP 2 crosses below an absolute threshold with hysteresis. Report to be issued when the PSNI level of the measured AP 3 crosses above an absolute threshold with hysteresis. Report to be issued when the PSNI level of the measured AP 4 crosses below an absolute threshold with hysteresis. Report to be issued when the RCPI level of the measured AP 5 crosses above a threshold defined by an offset (with hysteresis) from the serving AP's RCPI. Report to be issued when the RCPI level of the measured AP 6 crosses below a threshold defined by an offset (with hysteresis) from the serving AP's RCPI. Report to be issued when the PSNI level of the measured AP 7 crosses above a threshold defined by an offset (with hysteresis) from the serving AP's PSNI. Report to be issued when the PSNI level of the measured AP 8 crosses below a threshold defined by an offset (with hysteresis) from the serving AP's PSNI. Periodic reports (one per measurement) to begin when the 9 RCPI level of the measured AP enters and remains in a range bound by the serving AP's RCPI and an offset (with hysteresis) from the serving AP's RCPI. Periodic reports (one per measurement) to begin when the 10 PSNI level of the measured AP enters and remains in a range bound by the serving AP's PSNI and an offset (with hysteresis) from the serving AP's PSNI. Reserved 11-255
1. A method to be performed by an access point (AP), the method comprising:
transmitting a request to provide a beacon report, wherein the request comprises a reporting condition element representing a transmission condition for transmitting the beacon report, and wherein the reporting condition element is an 8 bit integer; and
receiving the beacon report in response to satisfaction of the transmission condition, wherein receiving the beacon report includes receiving the beacon report based on a periodically performed measurement when the reporting condition element has a value of 0.
receiving the beacon report in response to a measured received channel power indicator (RCPI) value that is above a threshold when the reporting condition element has a value of 1.
receiving the beacon report in response to a measured received channel power indicator (RCPI) value that is below a threshold when the reporting condition element has a value of 2.
receiving the beacon report in response to a measured signal to noise indicator (SNI) value that is greater than a threshold when the reporting condition element has a value of 3.
receiving the beacon report in response to a measured signal to noise indicator (SNI) value that is below a threshold when the reporting condition element has a value of 4.
receiving the beacon report in response to a measured received channel power indicator (RCPI) value that is above a threshold defined by an offset from an RCPI value of a serving AP when the reporting condition element has a value of 5.
receiving the beacon report in response to a measured received channel power indicator (RCPI) value that is below a threshold defined by an offset from an RCPI value of a serving AP when the reporting condition element has a value of 6.
receiving the beacon report in response to a measured signal to noise indicator (SNI) value that is above a threshold defined by an offset from an SNI value of a serving AP when the reporting condition element has a value of 7.
receiving the beacon report in response to a measured signal to noise indicator (SNI) value that is below a threshold defined by an offset from an SNI value of a serving AP when the reporting condition element has a value of 8.
receiving the beacon report in response to a measured received channel power indicator (RCPI) value that is in a range bound by an RCPI value of a serving AP and an offset reference value when the reporting condition element has a value of 9.
receiving the beacon report in response to a measured signal to noise indicator (SNI) value that is in a range bound by an SNI value of a serving AP and an offset reference value when the reporting condition element has a value of 10.
a transmitter configured to transmit a request to provide a beacon report in response to a measured received channel power indicator (RCPI) value based on a threshold, wherein the request comprises a reporting condition element that represents a transmission condition for transmitting the beacon report, and wherein the reporting condition element is an 8 bit integer; and
a receiver configured to receive the beacon report in response to satisfaction of the transmission condition.
13. The AP of claim 12, wherein the beacon report is in response to a measured received channel power indicator (RCPI) value that is below a threshold.
14. The AP of claim 12, wherein the beacon report is in response to a measured received channel power indicator (RCPI) value that is above a threshold defined by an offset from an RCPI value of a serving AP.
15. The AP of claim 12, wherein the beacon report is in response to a measured received channel power indicator (RCPI) value that is below a threshold defined by an offset from an RCPI value of a serving AP.
a transmitter configured to transmit a request to provide a beacon report, wherein the request comprises a reporting condition element that represents a transmission condition for transmitting the beacon report, and wherein the reporting condition element is an 8 bit integer; and
a receiver configured to receive the beacon report in response to satisfaction of the transmission condition, wherein the beacon report is in response to a measured signal to noise indicator (SNI) value that is greater than a threshold, when the transmission condition has a value of 3.
17. The AP of claim 16, wherein when the reporting condition element has a value of 1 the beacon report is in response to a measured received channel power indicator (RCPI) value that is above a threshold.
18. The AP of claim 16, wherein when the reporting condition element has a value of 5 the beacon report is in response to a measured received channel power indicator (RCPI) value that is above a threshold defined by an offset from an RCPI value of a serving AP.
19. The AP of claim 16, wherein when the reporting condition element has a value of 7 the beacon report is in response to a measured signal to noise indicator (SNI) value that is above a threshold defined by an offset from an SNI value of a serving AP.
20. The AP of claim 16, wherein when the reporting condition element has a value of 9 the beacon report is periodically in response to a measured received channel power indicator (RCPI) value that is in a range bound by an RCPI value of a serving AP and an offset reference value.
21. An access point (AP) comprising:
a receiver configured to receive the beacon report in response to satisfaction of the transmission condition, wherein the beacon report is in response to a measured signal to noise indicator (SNI) value that is below a threshold when the reporting condition has value of 4.
22. The AP of claim 21, wherein when the reporting condition element has a value of 0 the beacon report is based on a periodically performed measurement.
23. The AP of claim 21, wherein when the reporting condition element has a value of 2 the beacon report is in response to a measured received channel power indicator (RCPI) value that is below a threshold.
24. The AP of claim 21, wherein when the reporting condition element has a value of 4 the beacon report is in response to a measured signal to noise indicator (SNI) value that is below a threshold.
25. The AP of claim 21 wherein when the reporting condition element has a value of 6 the beacon report is in response to a measured received channel power indicator (RCPI) value that is below a threshold defined by an offset from an RCPI value of a serving AP.
26. The AP of claim 21, wherein the reporting condition element has a value of 8 the beacon report is in response to the measured signal to noise indicator (SNI) value is below a threshold defined by an offset from an SNI value of a serving AP.
27. The AP of claim 21, wherein when the reporting condition element has a value of 10 the beacon report is periodically in response to the measured signal to noise indicator (SNI) value that is in a range bound by an SNI value of a serving AP and an offset reference value.
US13/572,087 2003-05-14 2012-08-10 Method and apparatus of requesting a beacon report Active US9332451B2 (en)
US20120307663A1 US20120307663A1 (en) 2012-12-06
US9332451B2 true US9332451B2 (en) 2016-05-03
JP2009509374A (en) * 2005-09-16 2009-03-05 ノキア コーポレイション Technology to provide a measurement pilot transmission information in a wireless network
JP2009515402A (en) * 2005-11-04 2009-04-09 ノキア コーポレイション Multicast delivery quality monitoring mechanism
EP3518602A1 (en) * 2017-12-01 2019-07-31 LG Electronics Inc. -1- Method for transmitting or receiving channel measurement information in wireless lan system and apparatus therefor
Court Decision for Chinese Patent Application No. 200910005364.8, mailed on Dec. 31, 2015, 24 pages (Including 11 pages of English translation).
Draft Supplement to Standard for Telecommunications and Information Exchange Between Systems-LAN/MAN Specific Requirements-Part 11: Wireless Medium Access Control (MAC) and physical layer (PHY) specifications: Specification for Radio Resource Measurement. IEEE Std 802.11k/D0.1, Mar. 2003.
Draft Supplement to Standard for Telecommunications and Information Exchange Between Systems-LAN/MAN Specific Requirements-Part 11: Wireless Medium Access Control (MAC) and physical layer (PHY) specifications: Specification for Radio Resource Measurement. IEEE Std 802.11k/D02, May 2003.
Ericsson, 'UE Measurement Concept for Intra-Frequency Measurements,' TSG-RAN Working Group 2 (Radio Layer 2 and Radio Layer 3), TSGR2#4(99) 419, Berlin, Germany, 1999.5.25-28, 11 pages.
Examination Report for Norwegian Patent Application No. 20055955 mailed Mar. 27, 2012, 6 pages.
Examiner's Report for Canadian Patent Application No. 2,820,104 mailed Mar. 20, 2014, 5 pages.
Examiner's Report for Canadian Patent Application No. 2,820,104 mailed Sep. 24, 2014, 2 pages.
Extended European Search Report for European Patent Application No. 08168068.8, mailed on Jan. 30, 2009, 9 pages.
Extended European Search Report for European Patent Application No. 10154548.1, mailed on May 6, 2010, 9 pages.
Extended European Search Report for European Patent Application No. 10179384.2, mailed on Feb. 4, 2011, 9 pages.
Final Notice of Preliminary Rejection for Korean Patent Application No. 10-2012-7009593 mailed Feb. 14, 2013, 1 page.
Final Notice of Preliminary Rejection for Korean Patent Application No. 10-2012-7021250 mailed Jul. 29, 2014, 4 pages.
First Examination Report for Indian Patent Application No. 4964/DELNP/2005 mailed Jan. 22, 2009, 2 pages.
Hearing Notice for Indian Patent Application No. 4964/DELNP/2005 mailed Mar. 6, 2013, 2 pages.
Hoima et al. "WCDMA for UMTS, The Radio Resource Control Protocol," John Wiley and Sons, pp. 135-151 (Jan. 2001).
IEEE Wireless LAN Edition: A Compilation Based on IEEE Standard 802.11-1999 (R2003) and its Amendments.
International Preliminary Report on Patentability and Written Opinion for International Patent Application No. PCT/US2004/014901, mailed on Nov. 18, 2005, 7 pages.
International Preliminary Report on Patentability for International Patent Application No. PCT/US04/14901, mailed on Sep. 12, 2006, 19 pages.
International Search Report and Written Opinion for International Patent Application No. PCT/US2004/014901, mailed on Jul. 6, 2005, 4 pages.
Kaaranan et al. "UMTS Networks: Architecture, Mobility and Services," pp. 6-13, 50-57, 71-99, and 181-207. (Jun. 2001).
Non-Final Office Action for U.S. Appl. No. 10/845,822 mailed Dec. 28, 2007, 6 pages.
Non-Final Office Action for U.S. Appl. No. 10/845,822 mailed Oct. 14, 2008, 5 pages.
Non-Final Office Action for U.S. Appl. No. 12/763,360 mailed Jan. 20, 2012, 5 pages.
Non-Final Office Action for U.S. Appl. No. 12/763,360 mailed Nov. 12, 2010, 5 pages.
Notice of Allowance for Korean Patent Application No. 10-2011-7028428 mailed Nov. 28, 2012, 3 pages.
Notice of Allowance for Korean Patent Application No. 10-2012-7009593 mailed Aug. 27, 2013, 3 pages.
Notice of Allowance for U.S. Appl. No. 10/845,822 mailed Apr. 3, 2009, 6 pages.
Notice of Allowance for U.S. Appl. No. 10/845,822 mailed Nov. 16, 2009, 6 pages.
Notice of Allowance for U.S. Appl. No. 12/763,360 mailed Jul. 9, 2012, 5 pages.
Notice of Allowance for U.S. Appl. No. 12/763,360 mailed Mar. 22, 2011, 5 pages.
Notice of Preliminary Rejection for Korean Patent Application No. 10-2012-7021250 mailed Aug. 29, 2013, 2 pages.
Office Action & Search Report for Taiwan Patent Application No. 100105695 mailed May 22, 2014, 13 pages.
Office Action for Chinese Patent Application No. 200910005364.8, mailed on Jul. 6, 2011, 12 pages, including 7 pages of English translation.
Office Action for Chinese Patent Application No. 200910005364.8, mailed on Mar. 8, 2010, 10 pages, including 6 pages of English translation.
Office Action for Chinese Patent Application No. 200910005364.8, mailed on May 3, 2012, 17 pages, including 8 pages of English translation.
Office Action for Chinese Patent Application No. 200910005364.8, mailed on Nov. 1, 2011, 12 pages, including 7 pages of English translation.
Office Action for European Patent Application No. 08168068.8, mailed on Oct. 27, 2011, 7 pages.
Office Action for European Patent Application No. 10154548.1, mailed on Dec. 6, 2011, 6 pages.
Office Action for European Patent Application No. 10179384.2, mailed on Dec. 6, 2011, 6 pages.
Office Action for European Patent Application No. 10179384.2, mailed on Jan. 27 2016, 5 pages.
Office Action for Korean Patent Application No. 10-2011-7028428 mailed Feb. 13, 2012, 19 pages.
Office Action for Korean Patent Application No. 10-2011-7028428 mailed May 30, 2012, 5 pages.
Office Action for Korean Patent Application No. 10-2012-7021250 mailed Oct. 17, 2012, 8 pages.
Office Action for Korean Patent Application No. 2012-7021250, mailed on Nov. 25, 2014, 5 pages, including 2 pages of English translation.
Office Action for Korean Patent Application Serial No. 2015-7007456, mailed on Jun. 22, 2015, 7 pages, including 3 pages of English translation.
Office Action for Norwegian Patent Application No. 20055955 mailed Oct. 20, 2012, 4 pages.
Office Action for Taiwanese Patent Application No. 103137414, mailed on Jan. 12, 2015, 8 pages (Including 4 pages of English translation).
Office Action for U.S. Appl. No. 14/588,437, mailed on Feb. 26 2016, 36 pages.
Office Action in Canadian Application No. 2,820,104, mailed Oct. 30, 2015, 3 pages.
Office Action in European Application No. 08 168 068.8, mailed Oct. 15, 2015, 7 pages.
Office Action in European Application No. 10 154 548.1, mailed Nov. 10, 2015, 4 pages.
Re-Examination Decision for Chinese Patent Application No. 200910005364.8, mailed on Dec. 10, 2014, 22 pages, including 12 pages of English translation.
Reexamination Notice for Chinese Application No. 200910005364.8 mailed Mar. 5, 2014, 12 pages.
Search and Examination Report for Norwegian Patent Application No. 20055955 mailed Oct. 21, 2010, 5 pages.
Second Reexamination Notice for Chinese Application No. 200910005364.8 mailed Jul. 25, 2014, 6 pages.
Soomro et al. "Measurement/Quiet Request Element for DFS in Tgh," IEEE 802.11-02/215rO (Mar. 2002).
Supplementary European Search Report for European Patent Application No. 04752031.7, mailed on May 17, 2006, 2 pages.
Universal Mobile Telecommunications Systems (UMTS); Radio Resource Control (RRCO protocol specification (3GPP TS 25.331 version 5.4.0 Release 5), ETSI TS 125331 V5.4.0 (Mar. 2003).