Lines Matching full:may

105 …pty). When a requestType value is specified, device descriptor information may be optional or requ…
106 …may require that the device provide this list before servicing the device requests. If the databas…
112 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
118 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
119 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…
124 …Depending on device type and regulatory domain, the characteristics of the antenna may be required.
127 …equired depends on the device type and the regulatory domain. Note that the height may be negative.
129 …e spectrum request, but its use depends on applicable regulatory rules. It may be used, for exampl…
130 …may be used by a device to provide additional information to the database that may help it to dete…
134 …"channelId": "A String", # The database may include a channel identifier, when applicable. When it…
136 …ng on the context in which the frequency-range element appears, this value may be required. For ex…
140 …out geolocation capability), the rules of the applicable regulatory domain may require the master …
141 …may require that the device provide this list before servicing the device requests. If the databas…
147 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
153 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
154 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…
156 … may allow the anticipated position of the master device to be given instead. If the location spec…
157 …"confidence": 42, # The location confidence level, as an integer percentage, may be required, depe…
171 …the major and minor axes represent the uncertainty. The uncertainty values may be required, depend…
172 …at expresses the location uncertainty along the major axis of the ellipse. May be required by the …
177 …at expresses the location uncertainty along the minor axis of the ellipse. May be required by the …
181 … regulatory domains may require additional parameters. # Depending on device type and regulatory d…
191 …: # The vCard contact information for the device operator is optional, but may be required by spec…
254 …may require that the device provide this list before servicing the device requests. If the databas…
260 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
266 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
267 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…
273 … to notify devices of an upcoming change to the database URI. # A database may include the databas…
281 …may be empty if spectrum is not available. The database may return more than one spectrum schedule…
289 …m messages representing the usable profile. It will always be present, but may be empty when there…
291 …ation would require two specifications, at 0.1MHz and 8MHz. This parameter may be empty if there i…
292 …": [ # The list of frequency ranges and permissible power levels. The list may be empty if there i…
295 …"channelId": "A String", # The database may include a channel identifier, when applicable. When it…
297 …ng on the context in which the frequency-range element appears, this value may be required. For ex…
304 …z": 3.14, # The database may return a constraint on the allowed maximum contiguous bandwidth (in H…
306 …he database may return a constraint on the allowed maximum total bandwidth (in Hertz), which need …
308 …at least one applicable ruleset in the initialization response. The device may use the ruleset ide…
330 …pty). When a requestType value is specified, device descriptor information may be optional or requ…
331 …may require that the device provide this list before servicing the device requests. If the databas…
337 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
343 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
344 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…
349 … domain. # Depending on device type and regulatory domain, antenna characteristics may be required.
352 …equired depends on the device type and the regulatory domain. Note that the height may be negative.
354 …quest, but its use depends on applicable regulatory rules. For example, It may be used to request …
355 …tenna. If a location specifies a region, rather than a point, the database may return an UNIMPLEME…
357 …locations included in a available spectrum batch request, but the database may restrict the number…
359 …"confidence": 42, # The location confidence level, as an integer percentage, may be required, depe…
373 …the major and minor axes represent the uncertainty. The uncertainty values may be required, depend…
374 …at expresses the location uncertainty along the major axis of the ellipse. May be required by the …
379 …at expresses the location uncertainty along the minor axis of the ellipse. May be required by the …
384 …may be used by a device to provide additional information to the database that may help it to dete…
388 …"channelId": "A String", # The database may include a channel identifier, when applicable. When it…
390 …ng on the context in which the frequency-range element appears, this value may be required. For ex…
394 …out geolocation capability), the rules of the applicable regulatory domain may require the master …
395 …may require that the device provide this list before servicing the device requests. If the databas…
401 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
407 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
408 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…
410 … regulatory domains may require additional parameters. # Depending on device type and regulatory d…
420 …: # The vCard contact information for the device operator is optional, but may be required by spec…
481 …z": 3.14, # The database may return a constraint on the allowed maximum contiguous bandwidth (in H…
484 …may require that the device provide this list before servicing the device requests. If the databas…
490 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
496 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
497 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…
503 … to notify devices of an upcoming change to the database URI. # A database may include the databas…
511 …may be empty if spectrum is not available. The database may return more than one geo-spectrum sche…
513 …e schedule must be included (though it may be empty if there is no available spectrum). More than …
521 …m messages representing the usable profile. It will always be present, but may be empty when there…
523 …ation would require two specifications, at 0.1MHz and 8MHz. This parameter may be empty if there i…
524 …": [ # The list of frequency ranges and permissible power levels. The list may be empty if there i…
527 …"channelId": "A String", # The database may include a channel identifier, when applicable. When it…
529 …ng on the context in which the frequency-range element appears, this value may be required. For ex…
537 …"confidence": 42, # The location confidence level, as an integer percentage, may be required, depe…
551 …the major and minor axes represent the uncertainty. The uncertainty values may be required, depend…
552 …at expresses the location uncertainty along the major axis of the ellipse. May be required by the …
557 …at expresses the location uncertainty along the minor axis of the ellipse. May be required by the …
564 …atabase may return a constraint on the allowed maximum total bandwidth (in Hertz), which does not …
566 …at least one applicable ruleset in the initialization response. The device may use the ruleset ide…
589 …may require that the device provide this list before servicing the device requests. If the databas…
595 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
601 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
602 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…
608 …"confidence": 42, # The location confidence level, as an integer percentage, may be required, depe…
622 …the major and minor axes represent the uncertainty. The uncertainty values may be required, depend…
623 …at expresses the location uncertainty along the major axis of the ellipse. May be required by the …
628 …at expresses the location uncertainty along the minor axis of the ellipse. May be required by the …
642 … to notify devices of an upcoming change to the database URI. # A database may include the databas…
658 …at least one applicable ruleset in the initialization response. The device may use the ruleset ide…
678 …may require that the device provide this list before servicing the device requests. If the databas…
684 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
690 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
691 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…
697 …"confidence": 42, # The location confidence level, as an integer percentage, may be required, depe…
711 …the major and minor axes represent the uncertainty. The uncertainty values may be required, depend…
712 …at expresses the location uncertainty along the major axis of the ellipse. May be required by the …
717 …at expresses the location uncertainty along the minor axis of the ellipse. May be required by the …
724 …may be empty if the device decides not to use any of spectrum. For consistency, the psdBandwidthHz…
726 …ation would require two specifications, at 0.1MHz and 8MHz. This parameter may be empty if there i…
727 …": [ # The list of frequency ranges and permissible power levels. The list may be empty if there i…
730 …"channelId": "A String", # The database may include a channel identifier, when applicable. When it…
732 …ng on the context in which the frequency-range element appears, this value may be required. For ex…
764 …may require that the device provide this list before servicing the device requests. If the databas…
770 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
776 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
777 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…
782 …equired depends on the device type and the regulatory domain. Note that the height may be negative.
784 …nformation required as part of device registration. The regulatory domains may require additional …
794 …: # The vCard contact information for the device operator is optional, but may be required by spec…
849 …"confidence": 42, # The location confidence level, as an integer percentage, may be required, depe…
863 …the major and minor axes represent the uncertainty. The uncertainty values may be required, depend…
864 …at expresses the location uncertainty along the major axis of the ellipse. May be required by the …
869 …at expresses the location uncertainty along the minor axis of the ellipse. May be required by the …
883 … to notify devices of an upcoming change to the database URI. # A database may include the databas…
912 …may require that the device provide this list before servicing the device requests. If the databas…
918 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
924 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
925 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…
941 … to notify devices of an upcoming change to the database URI. # A database may include the databas…
956 …g", # If the device identifier is not valid, the database may include a reason. The reason may be …
958 …may require that the device provide this list before servicing the device requests. If the databas…
964 …th should not exceed 32 characters. Note that, in practice, a valid FCC ID may be limited to 19 ch…
970 …"manufacturerId": "A String", # The manufacturer's ID may be required by the regulatory domain. Th…
971 …"modelId": "A String", # The device's model ID may be required by the regulatory domain. The strin…