Sign In to Follow Application
View All Documents & Correspondence

Radio Resource Measurement Techniques In Directional Wireless Networks

Abstract: The present invention relates to a method, comprising:     transmitting a measurement request from a coordinator device to a station device, the measurement request directing the station device to perform an isolation measurement of one or more beams of a millimeter wave wireless channel;     receiving at the coordinator device, a response to the request, the response comprising an isolation value corresponding to the measurement; and     allocating wireless resource based at least on the isolation value,     wherein the measurement request includes at least one timing parameter for the measurement and an identifier of a device towards which the station device is to direct the measurement.

Get Free WhatsApp Updates!
Notices, Deadlines & Correspondence

Patent Information

Application #
Filing Date
27 September 2016
Publication Number
30/2017
Publication Type
INA
Invention Field
ELECTRONICS
Status
Email
ipo@iphorizons.com
Parent Application
Patent Number
Legal Status
Grant Date
2023-12-28
Renewal Date

Applicants

INTEL CORPORATION
2200 Mission College Boulevard, MS: RNB-4-150, Santa Clara, California 95052, United States of America

Inventors

1. CORDEIRO, Carlos
15168 NW Twinflower Dr, Portland, Oregon 97229, United States of America
2. GOPALAKRISHNAN, Praveen
2515 NW Overlook Dr, Apt 323, Hillsboro, Oregon 97124, United States of America

Specification

RADIO RESOURCE MEASUREMENT TECHNIQUES IN DIRECTIONAL
WIRELESS NETWORKS
This application is a Divisional out of Indian Patent Application No. 9217/DELNP/20 11 .
BACKGROUND
5 Wireless networks, such as wireless personal area networks (WPANs), wireless
local area networks (WLANs), and/or cellular telephony networks provide for a wide array
of mobile communications services. Currently, wireless networks are under development
for the 60 GHz radio frequency (RF) band. Such networks intend to provide higher data
rates, spatial reuse ( eqabled by the directional propagation properties of 60 GHz signals),
10 directional communications, enhanced interference mitigation, and network stability.
In addition, it is planned for 60 GHz wireless networks to employ scheduled media
access control (MAC) techniques, such as time division multiple access (TDMA).
However scheduled media access techniques are typically not as robust as contentionbased
media access techniques. For example, carrier sense multiple access with collision
15 avoidance (CSMA/CA) (which is currently employed in IEEE 802. 11 networks) is often
more robust in handling transmission interference.
Thus, it is desirable to ensure network robustness when scheduled MAC
techniques, such as TDMA, are employed. One way to promote robustness involves the
exchange of information between devices regarding the wireless environment. More
20 pati icularly, such information provides for scheduled allocations that promote robust
network operation.
BRIEF DESCRIPTION OF THE DRAWINGS
In the drawings, like reference numbers generally indicate identical, functionally
25 similar, and/or structurally similar elements. The drawing in which an element first
appears is indicated by the leftmost digit(s) in the reference number. The present
invention will be described with reference to the accompanying drawings, wherein:
FIG. 1 is a diagram of an exemplary operational environment;
FIG. 2 is a diagram of an exemplary transmission arrangement between two
30 devices;
FIG. 3 is a logic flow diagram;
2
5
wo 2010/151448 PCT IUS20 10/038499
FIG. 4 is a diagram of an exemplary channel quality histogram request format;
FIG. 5 is a diagram of an exemplary channel quality histogram report format; and
FIG. 6 is a diagram of an exemplary device implementation.
DETAILED DESCRIPTION
Embodiments provide techniques for radio resource measurement (RRM) that
support directionality, as well as scheduled media access techniques. For instance,
embodiments may transmit a measurement request from a first device to a second device
that direqs the second device to take one or more meas urements of a wireless channel.
I 0 This measurement request may include various characteristics for the one or more
measurements. For example, the measurement request may indicate at least one
directional parameter and at least one timing parameter for the one or more measurements.
In response to the request, the first device receives a meas ure report that includes
measured values for each of the one or more meas urements.
15
20
Conventional RRM techniques do not support directionality and scheduled access
(e.g., TDMA). For instance, the Institute of Electrical and Electronics Engineers (IEEE)
802 .11 k Amendment to the IEEE 802.11-2007 Standard prov ides RRM schemes.
However, these schemes were developed under the assumption of a CSMA/CA MAC and
an omni-directional transmission mode.
Reference throughout this specification to "one embodiment" or "an embodiment"
means that a particular feature, structure, or characteristic described in connection vvith the
embodiment is included in at least one embodiment. Thus, appearances of the phrases "in
one embodiment" or "in an embodiment" in vadous places throughout this specification
are not necessarily all referring to the same.embodiment. Furthermore, the particular
25 features, stru~tures, or characteristics may be combined in any suitable manner in one or
more embodime nts.
FIG. l is a diagram of an exemplary operational environment 100 that may
employ the techniques described herein. This environment includes a central controller
device (PCP) 102, and multiple stations (ST As) I 04a-d. These devices may be
30 implemented in any combination of hardware andior software. In general operation, these
devices may communicate wirelessly with each other. Moreover, in embodiments, these
3
wo 2010/151448 PCT/US2010/038499
devices may employ multiple beams and/or directional transmissions.
PCP I 02 performs various control operations, including resource allocations for
ST As 1 04a-d. In particular, PCP 102 may man~ge resources within a repeating period
calJed a TDMA frame (also known as Beacon Interval or Superframe). This may involve
5 allocating time slots within the TOM A frame to ST As 1 04a-d. Such allocations may
employ spatial reuse. More particularly, such allocations may overlap (completely or
partially) in time.
In embodiments, allocations made by PCP 102 may be based on requests received
from ST As I 04a-d. In making such allocations. PCP l 02 may consider characteristics
I 0 regarding the wireless environment of ST As 1 04a-d. Details involving the determination
of such characteristics are provided below.
ST As l 04a-d may wirelessly communicate in accordance with resource allocations
performed by PCP I 02. These communications may involve transmissions between ST As
104. Also, these communications may involve exchanging transmissions with PCP 102.
15 For example, PCP 102 may relay communications traffic between STAs. Furthe r, PCP
I 02 may provide ST As 1 04a-d with access to one or more wireless networks (e.g., the
Internet and/or wired telephony networks).
As described above, PCP I 02 may consider characteristics regarding the wireless
environment of STAs J04a- l 04d. To determine :-;uch characteristics, PCP I 02 may gather
20 information from STAs 104a-d. More particularly, PCP 102 may transmit reques ts to
ST As I 04a-d. Each of such requests may direct the receiving ST A to conduct particular
:;(~) measurements. In tum, the recipient ST A conducts the measurement("S) and transmits a
repo1i back to PCP 102. From such reports, PCP 102 may perform resource allocations
that consider factors, such as interference mitigation, network stability, and so forth. For
25 example, based on such received repo1i(s), PCP 102 may determine whether to make
allocations involving spatial reuse.
As example of such features, FIG. 1 shows PCP I 02 sending measurement
requests 120a and l20b to ST A 1 04a and 1 04b, respectively. In response, ST As I 04a and
I 04b send measurement reports 122a and l22b to PCP 102. These messages are shown
30 for purposes of illustration, an<.J not limitation. Thus, messages may be sent to any
combination of STAs I 04a-d in any number and/or sequence.
4
-""'
wo 2010{151448 PCTfUS2010/038499
In embodiments, a device (e.g., PCP 102) may make allocations based on the
amount of isolation among particular beams (as well as other information). For example,
a beam pairing must exhibit a sufficiently low amount of isolation to support a wireless
link. Further. the device may use such isolation information to ei- tablish multip le
5 allocations that reuse resources (e.g., time and/or frequency and/or space). More
particularly, information included in such measurement reports may be used .to establish a
high degree of isolation between each allocation (so that the interference is effectively
managed). Examples of varying isolation levels are illustrated below with reference to
FIG. 2.
10 FIG. 2 is a diagram showing an exemplary wireless arrangement between two
~:i:&!. devices. In particular, FIG. 2 shows a first station C'ST A A") and a second station ("ST A
B"). These s tations may be employed in the context ofFIG. I (e.g., each as one STAs
1 04a-d).
Between these stati ons are multip le beams. For instance, FIG. 2 shows that STA
15 A provides transmit beams 202a-c. Also, FIG. 2 shows that STA B provides receive
beams 204a-c. These features are shown for purpos~ of illustration and not limitat ion.
Through beams 202a-c. STA A may engage in one or more d irectional transmiss ions.
Similarly, through beams 204a-c, STA B may receive transmissions from different
directions.
20
25
FIG. 2 shows nine different pairings of transmit and receive beams between ST A
A and ST A B. Each of these pairings exhibits d iffcrcnt levels of isolation. For ins tance,
there is a low amount of isolation between beams 202a and 204a. This is because these
beams are substantially aligned (or overlapping). ln contras t, there is a high amount of
isolation between beams 202c and 204c. This is because these beams are unaligned (or
non-overlapping). In embodiments, such levels ofisolation may be determined th rough
measurements performed by stations (e.g., STAs I 04a-d). Such measurements may be
made in response to requests made by a controlling sta tion (e.g., PCP 102).
Operations for the embodiments may be further described with reference to the
following fi gures and accompanying examples. Some of the fi gures may include a log ic
30 flow. Although such figures prese nte d here in may in~lud e a particular logic flow, it can
be appreciated that the logic flow mere ly provides an example ofhow the general
functionality as described herein can be implemented. Further, the given logic flow docs
5
5
10
WO 2010/151448 PCT/US2010/038499
not necessarily have to be executed in the order presented unless otherwise indicated. In
addition, the given logic flow may be implemented by a hardware element, a software
element executed by a processor, or any combination thereof. The embodiments are not
limited to this context.
FIG. 3 illustrates an embodiment of a logic flow. In particular, FTG._3 illustrates a
logic flow 300, which may be representative of operations executed by one or more
embodiments. This flow is described in the context of FIG. 1. However, this flow may be
employed in other contexts.
At a block 302, a first device wirelessly sends a measurement request to a second
device. This request directs the second device to perform one or more measurements of a
wireless channel. The first device may be a coordinator device for a wireless network
(e.g., PCP 1 02), and the second device may be a user device (e.g., one of STAs 104a-d).
In embodiments, this request may be a quality histogram request, as described below with
reference to FIG. 4. However, embodiments may employ other request formats.
15 The request may specify one or more characteristics for these one or more
measurements. For ins tance, the request may indicate particular directional and timing
characteristics for the m easurement(s). Examples of directional characteristics include
(but are not limited to) a particular remote device to which the meas urement(s) are to be
directed, and a beam (e. g., a receive beam) through which the second device is to perform
20 the measurement(s). Examples of timing characteristics include (but are not limited to) a
measurement start time, a measurement period duration, and a number of measurements to
be taken during the measurement period.
25
30
FUiiher, the request may specify when the type ofmeasurement(s) to be taken.
Exemplary measurement types include a determination of an Average Noise plus
Interference Power Indicator (ANIPI), and/or determination of a Received Signal to Noise
Indicator (RSNI). Embodiments, however, are not limited to these measurement types
At a block 304, the second device wirelessly receives the measurement request.
Following this, at a block 306, the second device performs one or more measurements in
accordance with the request.
At a block 308, the remote device wirelessly sends a response (also referred to as a
measurement report) to the first device containing the measureme nt(s). In embodiments,
6
wo 2010il51448 PCT/US2010/038499
this res ponse may be a quality histogram report, as described below with reference to FIG.
5. However, embodiments may employ other response formats.
The first device receives the response at a block 310. Then, at a block 312, the
first device may make one or more resource allocations based on information provided in
5 the response. As described above with reference to FTG. 1, this may involve allocating
one or more time s lots within a TDMA frame. However, embod iments are not limited to
TDMA media access techniques.
FIG. 4 is a diagram showing an exemplary format 400 of a channel quality
histogram format request. This format includes multiple fields. For instance, a regu latory
I 0 class field 402 provides information regarding regulated para meters, such as channel
frequency, channel spacing, power limits, and so forth. A channel number field 404
provides information regarding the c hannel for which measurements are to be taken.
Embodiments may format fields 402 and 404 in accordance with Annex J of the IEEE
802.l lk Amendment to the IEEE 802. 11-2007 Standard. Each of fields 402 and 404 may
15 be one octet in size. However, other sizes may be employed.
As shown in FIG. 4, fonnat 400 further includes a STAID field 406 aad a Beam
' ID field 408. These fields introduce directiona lity support for RRM measurements.
More particularly, STAID fi eld 406 indicates a STA (e.g., by its MAC add ress)
towards which the RRM request applies. For example, if the mea.o;.uring ST A is
20 beamformed w ith the STA iden ti fied by STAID fi eld 406, then the measurement shall be
carried out direct ionally towards identified STA. In embodiments, STAID field 406 may
be set to a broadcast ID (BcastiD), in which case the measuring ST Kwill do so through an
omni direction al pattern. STAID fi e ld 406 may be in various formats. For example, in
embodiments, STAID filed 406 indicates a MAC address of a ST A. FIG. 4 shows that
25 STAID ID field 406 may be one octet in size, which may be an Association rD obtained
by the ST A once it associated with the PCP. However, other types of identifiers and s izes
may be employed.
~
Beam ID field 408 indicates a beam for which the corresponding measurement
request applies. For example, if source and destination ST As have multiple beams
30 between them, Beam TO fie ld 408 identifies one of them. A value uf zero (0) in this fielJ
indicates that any beam may be used for this measurement. As indicated in FIG. 4, Beam
7
wo 2010/151448 PCT!US2010/038499 -
ID field 408 may be one octet in size. However, other sizes may be employed.
Measurement method field 410 indicates the method to be used by the measuring
ST A in carrying the measurement request, as well as in reporting back to the PCP in the
corresponding measurement report. In embodiments, the c~nv en tions provided in the
5 TEEE 802_11 k Amendment to the TEEE 802.11-2007 Standard may be employed. For
example, when field 410 is set to zero (0), Average Noise plus Interference Power
Indicator (ANIPI) is designated. However, when this field is set to one (1 ), Received
Signal to Noise Indicator (RSNI) is designated. Other values of measurement field 4 10
may be reserved for other designat ions. Measurement method field 410 may be one octet
10 in size. However, other sizes may be employed. Moreover, embodiments are not limited
to ANIPI and RSNI. Thus, in embodime nts, measurement method field 4 10 may ind icate
other measurement types.
Measurement start time field 4 12 provides RRlvl suppo1i fo r scheduled access
MAC protocols (e.g., TDMA). In the IEEE 802.llk Amendment to the IEEE 802.1 1-
15 2007 Standard, no Measurement Start T ime is defined. Rather a Randomization Interval is
included which suits a CSMA/CA MAC protocol. However, for scheduled MAC
protocols, a speci fic Measurement Start Time field is required. Thus, measurement start
time fi eld 4 I 2 indicates a time when the requested measurement is to commence. In
embodiments, a value of 0 indicates that the requested measurement shall start
20
25
immediately. Measurement start time fie ld 412 may be eight octets in s ize. However,
other sizes may be employed.
Measurement duration fi eld 414 indicates a duration of the requested measurement.
ln embodiments, such duration may be either mandatory or preferred. As indicated in
FJG. 4, measurement duration field may be two octets in size.
Number of time blocks fi eld 4 16 provides a capability that is advantageous for .
spatial reuse and interference mitigation, but ·which is not currently supported in the IEEE
802.11 k Amendment to the IEEE 802. I I -2007 Standard. In particular, this field indicates
the number of time blocks within the total Measurement Duration. A ratio oetween the
measurement durati on and the number of time bloch (i.e., the measurement duration
30 divided by the number of Time blocks) provides a duration of each in dividual
measurement to be conducted (also refen-ed to as a measurement unit). As indicated in
FlG. 4, field 416 may be one octet in size. However, other sizes may be employed.
8
5
wo 2010/151448 PCT/US201 0/038499
ln additio n to the above fi elds, format 400 may include a fie ld 4 18 (of variable
size) to convey optional information sub-elements. In embodiments, this field may
employ the same c onvention, as provided by the IEEE 802. 11 k Amendment to the IEEE
R02 .11 -2007 Standard.
FTG. 5 is a diagram showing an exemplary format 500 of a channel qual ity
his to gra m format report. This fo rmat includes multiple fields. For instance, regula tory
class field 502 and channel number field 504 provide information, as described above with
reference to fields 402 and 404 of FJG. 4. TI1is infom1ation may be formatted as defi ned
in Annex J of the IEEE 802. 11 k Amendment to the IEEE 80 2.1 1-2007 Standard. Each of
10 fields 502 and 504 may be one octet in size. However, other s izes may be employed.
i::!J)
t;:T ST AID tield 506 and Beam ID tield 50~ indicate the directionality aspect of the
measureme nt report, as described above with reference to fie lds 406 and 408 of FIG. 4.
For ins tance, STAID fi eld 5 06 indicates the ST A towards which the measureme nt applies
and Beam ID fi eld 508 ind icates the beam that was used to perform the measu rement. As
15 indicated in FIG. 5, STAID field 506 and Beam ID field 508 may each be one octet in
size. However, other sizes may be employed.
M easurement meth od fi eld 510, measurement sta rt time field 512, measurement
duration field 514, and n umber of time blocks 5 16 are employed a" desc ribed above with
refere nce to fields 4 10-4 16 of FIG. 4.
20 F JG. 5 shows tha t format 500 includes mu ltiple measurement fie lds. In particH iar,
FJG. 5 shows measurement fi e lds 518I-5 18N that correspond to each of N time blocks
j~;J specified in the corresponding c hann el qu ality his togram request. Each of measurement
fi e lds 5 181-518)J canies an actu a l measured value (e.g., an ANIPl value or an average
RSNI value).
25 In addi tion to the above fi e1ds, format 500 may include a fie ld 518 (of variable
size) to convey optional information sub-clements. ln embodiments, this fie ld may
emp loy the same convention, as provided by the IEEE 802. II k Amendment to the IEEE
802.11 -2007 Standard.
F IG. 6 is a diagram of an implementation 600 that may be included in a wire less
30 device, such PCP i 02 and! or STAs I 04a-d of FIG. l. This implementation , however, may
be also employed in other contexts. Implementat ion 600 may include variOliS e lements.
9
·.:'·:-?>~
5
wo 2010/151448 PCT/US2010/038499
For example, FIG. 6 shows implementation 600 including multiple antennas 602a-c, a
transceiver module 604, a host module 606, a measurement module 607, and a resource
allocation module 608. These elements may be implemented in hardware, software, or
any combination thereof.
Antennas 602a-c provide for the exchange ofwireless signals with remote devices.
Although three antennas are depicted, any number of antennas may be employed. Also,
embodiments may employ one or more transmit antennas and one or more receive
antennas. Such multiple antenna arrangements may be employed for beamforming. For
instance, a weight may be set in each antenna may such that the combined output signal
l 0 . provides a corresponding beam.
"({J As shown in FIG. 6, transceiver module 604 includes a transmitter portion 6 10,
and a receiver portion 612. During operation, transc eiver module 604 provides an
interface between antennas 602a-c and other elements, such as h ost module 606,
measurement module 607, and/or resource allocation module 60 8. For instance,
15 trans mitter portion 6 10 receives symbols from such elements, and generates corresponding
signals for wireless trans mi ss ion by one or more of antennas 602a-c. This may involve
operations, S\tch as modulation, amplifica tion, and/or filterin g. However, other operati ons
may be emp loyed.
Conversely, receiver potiion 6 12 obtains s ignals received by one or more of
20 antennas 602a-c and generates conesponding symbols. In turn, these symbols may be
provided to clements, such as host module 606, measurement module 607, and/or resource
allocation module 608. This generation of symbols may involve operations, includ ing (but
not limited to) demodulation, amplification, and/or filtering.
The signals generated and received by transceiver module 604 may be in various
25 formats. For ins tance, these signals may be modulated in accordance with an orthogonal
frequency div is ion multiplexing (OFDM) scheme or a Single Carrier (SC) scheme.
However, other schemes and formats (e.g., QPSK, BPSK, FSK, etc.) may be employed.
~
T o p rov ide such features, transmitter portion 610 and receiver portion 612 may
each include various components, Sl.Jch as modulators, demodulators, amplifiers, filters ,
30 buffers, upconverte rs, a nd/or downconveters. Such components may be implemented in
hardware (e.g., el ectronics ), software, or any combination thereof.
10
wo 2010/151448 PCT /US20 I 0/038499
The symbols exchanged between transceiver module 604 and other elements may
form messages or information associated with one or more protocols, and/or with one or
more user applications. Thus, these elements may perform operations corresponding to
such protocol(s) and/or user application(s). Exemplary user applications include
5 telephony, messaging, e-mail, web browsing, content (e.g., video and audio)
distribution/reception, and so fo rth.
Moreover, in transmitting and receiving signals, transceiver module 604 may
employ various access techniques. For example, transceiver module 604 may employ a
scheduled MAC technique, such as TDMA. Embodiments, however, arc not limited to
10 such techniques.
0 f:J Measurement module 607 may perform measurements ofwireless resources. Such
resources may be specified in accordance with reques ts received (through transceiver
module 604 l from a remote device, such as PCP I 02 or an IEEE 802. 11 access point (AP).
As described above, such measureme nts may be of average noise plus interference power
15 (to provide an ANIPI), and/or of received signal to noise Indicator (to provide an RSNI).
However, embodiments are not limited to these measurements. Thus, other wireless
channel measurements (e.g., measurements involving any combination of signal power,
interfe re nce power, and/or noise power) may be made.
Measurements made by measurement module 607 may be from hard symbols
20 received f rom transceiver module 604 (e.g., based on a bit error rate determined through
comparison with a predetermined sequence). Also, such measurements may be based on
soft symbols generated by transceiver module 604 from received wireless signals.
Moreover, such measurements may be generated from un-demodulated signals provid ed
by transceiver module.
25 In addition, measurement module 607 may generate a report message that indicates
such measurements. This report may be transmitted to the remote device through
transceiver module 604.
ln embodiments, resource allocation module 608 may perform resource allocation
techniques described he rein. For example, based on received measurements, allocation
30 mmJyJe 608 may allocate portions of a communications resource (e.g., time slots within a
TDMA frame). Such alloca tion may include employ reuse that where sufficient isolation
I I
-·'-"'-.:-....
wo 20i0/151448 PCT/USlOI0/038499
exists. Such isolation may be determined through measurements received from remote
stations (through transceiver module 604). Allocations may becommunicated to remote
devices (through transceiver module 604) in control messages.
As described herein, various embodiments may be implemented using hardware
5 elements, software elements, or any combination thereof. Examples of hardware elements
may include processors, microprocessors, circuits, circuit elements (e.g., trans is tors,
resistors, capacitors, inductors, and so forth), integrated circuits, application specific
integrated circuits (ASIC), programmable logic devices (PLD). digital signal processors
(DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor
10 device, chips, microchips, chip sets, and so forth.
(Jf{) Examples of software may include software components, programs, applications,
computer programs, application programs, system programs, machine programs, operating
system software, middleware, firmware, software modules, routines, subroutines,
functions, methods, procedures, software interfaces, application program interfaces (API),
15 instruction sets, comput ing code, computer code, code segments, computer code segments,
words, values, symbols, or any combination thereof.
20
Some embodiments may be implemented, for example, using a storage medium or
article which is machine readable. The storage medi um may store an instruction or a set
of instructions that, if executed by a machine. may cause the machine to perform a method
and/or operations in accordance with the embodiments. Such a machine may include, for
example, any suitable processing platform, computing platform, computing device,
processing device, computing system, processing system, computer, processor, or the like,
and may be implemented using any suitable combination of hardware and/or software.
The sto rage medium or anicle may include, for example, any suitable type of
25 memory unit, memory device, memory article, memory medium, storage device, storage
article, storage medium and/or storage" unit, for example, memory, removable or nonremovable
media, erasable or non-erasable media, writeable or re-writeable media, digital
or analog media, hard disk, floppy disk, Compact Disk Read Only Memory-( CD-ROM),
Compact Disk Recordable (CD-R), Compact Disk Rewriteable (CD-RW), optical disk,
30 magnetic media, magneto-optical media, removab le memory cards or disks, various types
of Digital Versatile Disk (DVD), a tape, a cassette, or the like. The instructions may
include any suitable type of code, such as source code, compiled code, interpreted code,
12
wo 20Hl/151448 PCTIUS2010/038499
executable code, static code, dynamic code, encrypted code. and the like, irnplcmcntetl
using any suitable high-level. low-level. objcct-oJien tcd, visual, compiled and/or
interprered programming language.
While various embodiments of the present invention bave been described above. it
:) sh1)Uid be under:-. toot! that they have been rresentetl by way of example on ly, and not in
limitation. For example. the techniques described herein arc not limited to IEEE 802.11
networks. Thus, these techniques may be employed in other net:worh, such as ones that
employ any combination of directional transmissions, reuse, and/or scheduled media
access techniques.
10 Accordingly, it will be apparent to persons ski lled in the relevant art that various
changes in form and detail can be made therein without departing from the spirit and scope
of the invention. Thus, tl1c breadth and scope of the present invention should not be
limited by any of the above-described exemplary embodiments, but should be defined on ly
in accordance with the following claims a.nd their equivalents.

Claims:WE CLAIM:

1. A method, comprising:
transmitting a measurement request from a coordinator device to a station device, the measurement request directing the station device to perform an isolation measurement of one or more beams of a millimeter wave wireless channel;
receiving at the coordinator device, a response to the request, the response comprising an isolation value corresponding to the measurement; and
allocating a wireless resource based at least on the isolation value,
wherein the measurement request includes at least one timing parameter for the measurement and an identifier of a device towards which the station device is to direct the measurement.

2. The method of claim 1, wherein allocating the wireless resource comprises allocating one or more time slots within a time interval.

3. An apparatus, comprising:
a transceiver module to exchange wireless signals with one or more remote devices; and
a resource allocation module to:
transmit a measurement request to a remote device through the transceiver module, the measurement request directing the remote device to take one or more isolation measurements of one or more beams of a millimeter wave wireless channel;
receive a measure report in response to the request, the report comprising measured isolation values for each of the one or more measurements; and
allocating a wireless resource based at least on the isolation value,
wherein the measurement request includes at least one timing parameter for the measurement and an identifier of a device towards which the station device is to direct the measurement.
4. The apparatus of claim 3, wherein the wireless resource includes a time slot within a time interval.

5. The apparatus of claim 3, wherein the at least one timing parameter includes a start time for the one or more measurements.

6. A non-transitory computer readable medium including instructions stored thereon, which when executed by one or more processor(s), cause the device to perform operations of:
transmitting a measurement request from a coordinator device to a station device, the measurement request directing the station device to perform an isolation measurement of one or more beams of a millimeter wave wireless channel;
receiving at the coordinator device, a response to the request, the response comprising an isolation value corresponding to the measurement; and
allocating a wireless resource based at least on the isolation value,
wherein the measurement request includes at least one timing parameter for the measurement and an identifier of a device towards which the station device is to direct the measurement.

7. The non-transitory computer readable medium of claim 1, wherein allocating the wireless resource comprises allocating one or more time slots within a time interval.

Documents

Orders

Section Controller Decision Date

Application Documents

# Name Date
1 201618032927-IntimationOfGrant28-12-2023.pdf 2023-12-28
1 Priority Document [27-09-2016(online)].pdf 2016-09-27
2 201618032927-PatentCertificate28-12-2023.pdf 2023-12-28
2 Form 5 [27-09-2016(online)].pdf 2016-09-27
3 Form 3 [27-09-2016(online)].pdf 2016-09-27
3 201618032927-AMMENDED DOCUMENTS [01-11-2023(online)].pdf 2023-11-01
4 Form 20 [27-09-2016(online)].pdf 2016-09-27
4 201618032927-FORM 13 [01-11-2023(online)].pdf 2023-11-01
5 Form 18 [27-09-2016(online)].pdf_8.pdf 2016-09-27
5 201618032927-MARKED COPIES OF AMENDEMENTS [01-11-2023(online)].pdf 2023-11-01
6 Form 18 [27-09-2016(online)].pdf 2016-09-27
6 201618032927-PETITION UNDER RULE 137 [01-11-2023(online)].pdf 2023-11-01
7 Drawing [27-09-2016(online)].pdf 2016-09-27
7 201618032927-Written submissions and relevant documents [01-11-2023(online)].pdf 2023-11-01
8 Description(Complete) [27-09-2016(online)].pdf 2016-09-27
8 201618032927-FORM 3 [19-10-2023(online)].pdf 2023-10-19
9 201618032927-FORM-26 [16-10-2023(online)].pdf 2023-10-16
9 abstract.jpg 2016-10-14
10 201618032927-Correspondence to notify the Controller [06-10-2023(online)].pdf 2023-10-06
10 Other Patent Document [23-03-2017(online)].pdf 2017-03-23
11 201618032927-US(14)-HearingNotice-(HearingDate-17-10-2023).pdf 2023-10-06
11 Form 3 [27-03-2017(online)].pdf 2017-03-27
12 201618032927-Correspondence-130320.pdf 2021-10-17
12 201618032927-OTHERS-240317.pdf 2017-03-27
13 201618032927-Correspondence-240317.pdf 2017-03-27
13 201618032927-Correspondence-240620.pdf 2021-10-17
14 201618032927-Power of Attorney-130320.pdf 2021-10-17
14 201618032927-RELEVANT DOCUMENTS [29-12-2017(online)].pdf 2017-12-29
15 201618032927-MARKED COPIES OF AMENDEMENTS [29-12-2017(online)].pdf 2017-12-29
15 201618032927-Power of Attorney-240620.pdf 2021-10-17
16 201618032927-Annexure [29-12-2017(online)].pdf 2017-12-29
16 201618032927-FORM 13 [28-09-2021(online)].pdf 2021-09-28
17 201618032927-Response to office action [12-03-2020(online)].pdf 2020-03-12
17 201618032927-AMMENDED DOCUMENTS [29-12-2017(online)].pdf 2017-12-29
18 201618032927-Amendment Of Application Before Grant - Form 13 [29-12-2017(online)].pdf 2017-12-29
18 201618032927-FORM-26 [09-03-2020(online)].pdf 2020-03-09
19 201618032927-FER.pdf 2019-09-13
19 201618032927-FORM 3 [02-03-2020(online)].pdf 2020-03-02
20 201618032927 Form 1.pdf 2019-09-13
20 201618032927-PETITION UNDER RULE 137 [02-03-2020(online)].pdf 2020-03-02
21 201618032927-FORM 3 [30-10-2019(online)].pdf 2019-10-30
21 201618032927-RELEVANT DOCUMENTS [02-03-2020(online)].pdf 2020-03-02
22 201618032927-ABSTRACT [28-02-2020(online)].pdf 2020-02-28
22 201618032927-OTHERS [28-02-2020(online)].pdf 2020-02-28
23 201618032927-CLAIMS [28-02-2020(online)].pdf 2020-02-28
23 201618032927-FORM 3 [28-02-2020(online)].pdf 2020-02-28
24 201618032927-FER_SER_REPLY [28-02-2020(online)].pdf 2020-02-28
24 201618032927-COMPLETE SPECIFICATION [28-02-2020(online)].pdf 2020-02-28
25 201618032927-DRAWING [28-02-2020(online)].pdf 2020-02-28
26 201618032927-COMPLETE SPECIFICATION [28-02-2020(online)].pdf 2020-02-28
26 201618032927-FER_SER_REPLY [28-02-2020(online)].pdf 2020-02-28
27 201618032927-CLAIMS [28-02-2020(online)].pdf 2020-02-28
27 201618032927-FORM 3 [28-02-2020(online)].pdf 2020-02-28
28 201618032927-ABSTRACT [28-02-2020(online)].pdf 2020-02-28
28 201618032927-OTHERS [28-02-2020(online)].pdf 2020-02-28
29 201618032927-FORM 3 [30-10-2019(online)].pdf 2019-10-30
29 201618032927-RELEVANT DOCUMENTS [02-03-2020(online)].pdf 2020-03-02
30 201618032927 Form 1.pdf 2019-09-13
30 201618032927-PETITION UNDER RULE 137 [02-03-2020(online)].pdf 2020-03-02
31 201618032927-FER.pdf 2019-09-13
31 201618032927-FORM 3 [02-03-2020(online)].pdf 2020-03-02
32 201618032927-Amendment Of Application Before Grant - Form 13 [29-12-2017(online)].pdf 2017-12-29
32 201618032927-FORM-26 [09-03-2020(online)].pdf 2020-03-09
33 201618032927-AMMENDED DOCUMENTS [29-12-2017(online)].pdf 2017-12-29
33 201618032927-Response to office action [12-03-2020(online)].pdf 2020-03-12
34 201618032927-Annexure [29-12-2017(online)].pdf 2017-12-29
34 201618032927-FORM 13 [28-09-2021(online)].pdf 2021-09-28
35 201618032927-Power of Attorney-240620.pdf 2021-10-17
35 201618032927-MARKED COPIES OF AMENDEMENTS [29-12-2017(online)].pdf 2017-12-29
36 201618032927-RELEVANT DOCUMENTS [29-12-2017(online)].pdf 2017-12-29
36 201618032927-Power of Attorney-130320.pdf 2021-10-17
37 201618032927-Correspondence-240317.pdf 2017-03-27
37 201618032927-Correspondence-240620.pdf 2021-10-17
38 201618032927-Correspondence-130320.pdf 2021-10-17
38 201618032927-OTHERS-240317.pdf 2017-03-27
39 201618032927-US(14)-HearingNotice-(HearingDate-17-10-2023).pdf 2023-10-06
39 Form 3 [27-03-2017(online)].pdf 2017-03-27
40 201618032927-Correspondence to notify the Controller [06-10-2023(online)].pdf 2023-10-06
40 Other Patent Document [23-03-2017(online)].pdf 2017-03-23
41 201618032927-FORM-26 [16-10-2023(online)].pdf 2023-10-16
41 abstract.jpg 2016-10-14
42 201618032927-FORM 3 [19-10-2023(online)].pdf 2023-10-19
42 Description(Complete) [27-09-2016(online)].pdf 2016-09-27
43 201618032927-Written submissions and relevant documents [01-11-2023(online)].pdf 2023-11-01
43 Drawing [27-09-2016(online)].pdf 2016-09-27
44 201618032927-PETITION UNDER RULE 137 [01-11-2023(online)].pdf 2023-11-01
44 Form 18 [27-09-2016(online)].pdf 2016-09-27
45 201618032927-MARKED COPIES OF AMENDEMENTS [01-11-2023(online)].pdf 2023-11-01
45 Form 18 [27-09-2016(online)].pdf_8.pdf 2016-09-27
46 Form 20 [27-09-2016(online)].pdf 2016-09-27
46 201618032927-FORM 13 [01-11-2023(online)].pdf 2023-11-01
47 Form 3 [27-09-2016(online)].pdf 2016-09-27
47 201618032927-AMMENDED DOCUMENTS [01-11-2023(online)].pdf 2023-11-01
48 Form 5 [27-09-2016(online)].pdf 2016-09-27
48 201618032927-PatentCertificate28-12-2023.pdf 2023-12-28
49 Priority Document [27-09-2016(online)].pdf 2016-09-27
49 201618032927-IntimationOfGrant28-12-2023.pdf 2023-12-28

Search Strategy

1 201618032927_13-09-2019.pdf

ERegister / Renewals

3rd: 25 Mar 2024

From 14/06/2012 - To 14/06/2013

4th: 25 Mar 2024

From 14/06/2013 - To 14/06/2014

5th: 25 Mar 2024

From 14/06/2014 - To 14/06/2015

6th: 25 Mar 2024

From 14/06/2015 - To 14/06/2016

7th: 25 Mar 2024

From 14/06/2016 - To 14/06/2017

8th: 25 Mar 2024

From 14/06/2017 - To 14/06/2018

9th: 25 Mar 2024

From 14/06/2018 - To 14/06/2019

10th: 25 Mar 2024

From 14/06/2019 - To 14/06/2020

11th: 25 Mar 2024

From 14/06/2020 - To 14/06/2021

12th: 25 Mar 2024

From 14/06/2021 - To 14/06/2022

13th: 25 Mar 2024

From 14/06/2022 - To 14/06/2023

14th: 25 Mar 2024

From 14/06/2023 - To 14/06/2024

15th: 04 Jun 2024

From 14/06/2024 - To 14/06/2025

16th: 26 May 2025

From 14/06/2025 - To 14/06/2026