January 2017doc.: IEEE 802.11-16/1532r3

IEEE P802.11
Wireless LANs

Service Hash Response ANQP-element
Date: 2017-01-10
Author(s):
Name / Company / Address / Phone / email
Stephen McCann / BlackBerry Ltd / The Pearce Building, West Street, Maidenhead, Berkshire, SL6 1RL, UK / +44 1753 667099 /
9.4.5AccessNetworkQueryProtocol(ANQP)elements

9.4.5.1General

Insertnewrowsasfollowstotheendofthetable,withcorrespondingadjustmentto“Reserved”value:

Table9-271—ANQP-elementdefinitions

ANQP-elementname / InfoID / ANQP-element(subclause)
ServiceHashRequest / 288 / 9.4.5.27 (Service HashRequestANQP-element)
ServiceInformationRequest / 289 / 9.4.5.28 (Service Infor-mationRequest ANQP-element)
ServiceInformationResponse / 290 / 9.4.5.29 (Service Infor-mation Response ANQP-element)
Service Hash Response / 291 / 9.4.5.30 (Service Hash Response ANQP-element)

Insertthe newsubclauseasfollows:

9.4.5.29 ServiceInformationResponseANQP-element

TheServiceInformationResponseANQP-elementcontainsthedetailedserviceinformationinresponsetoaServiceHashRequestoraServiceInformationRequestANQP-element.

TheformatoftheServiceInformationResponseANQP-elementisshowninFigure9-625j(ServiceInfor-mationResponseANQP-elementformat).

Info ID / Length / Service Information Response Tuples

Octets:22variable

Figure9-625j—ServiceInformationResponseANQP-elementformat

TheInfoIDandLengthfieldsaredefinedin9.4.5.1(General).

TheServiceInformationResponseTuplesfieldcontainsoneormoreServiceInformationResponseTuplesubfields.

TheformatoftheServiceInformationResponseTuplesubfieldisshowninFigure9-625k(ServiceInforma-tionResponseTuplesubfieldformat).

ServiceNameLength / ServiceName / InstanceNameLength / InstanceName / ServiceInfor-mation QueryResponseLength / Service Informa-tion QueryResponse

Octets:1variable1variable2variable

Figure9-625k—ServiceInformationResponseTuplesubfieldformat

The Service Name Length subfield and the Service Name subfield are defined in 9.4.5.28 (Service Information Request ANQP-element).

The Instance Name Length subfield and the Instance Name subfield are defined in 9.4.5.28 (Service Information Request ANQP-element). The Instance Name Length subfield contains a nonzero value.

TheServiceInformationQueryResponseLengthsubfieldisthelengthoftheServiceInformationQueryResponsesubfield.IftheServiceInformationQueryResponseLengthsubfieldisequalto0,theServiceInformationQueryResponsesubfieldisnotincluded. When this subfield is included in the Service Hash Response ANQP-element it is set to 0 (also in the behaviour section below)

TheServiceInformationQueryResponsesubfieldisavariablelengthfield.ThecontentoftheServiceInformationQueryResponsesubfieldisservice-specificbasedontherequestedserviceinformationandisspecifiedin11.25a.3(SolicitedPADprocedure).

Insert new subclause as follows:

9.4.5.30 Service Hash Response ANQP-element

The Service Hash Response ANQP-element contains the detailed service information in response to a Service Hash Request ANQP-element.

The format of the Service Hash Response ANQP-element is shown in Figure 9-625xx (Service Hash Response ANQP-element format).

Info ID / Length / Service Information Response Tuples

Octets:22variable

Figure 9-625xx—Service Hash Response ANQP-element format

The Info ID and Length fields are defined in 9.4.5.1 (General).

The Service Information Response Tuples field is defined in 9.4.5.29 (Service Information Response ANQP-element)

11. MLME

11.25WLANinterworkingwithexternalnetworksprocedures
11.25.3Interworkingprocedures:genericadvertisementservice(GAS)

11.25.3.2ANQPprocedures11.25.3.2.1General

Insertnewrowstotableasfollows:

Table11-15—ANQPusage

BSS / IBSS
ANQP-elementname / ANQP-element(subclause) / ANQP-
element type / AP / Non-AP and non-PCPSTA / STA
ServiceHash Request / 9.4.5.27
(ServiceHashRequest ANQP- element) / Q / R / T / —
Service InformationRequest / 9.4.5.28
(ServiceInformationRequest ANQP- element) / Q / R / T / —
Service InformationResponse / 9.4.5.29
(ServiceInformationResponse ANQP-element) / S / T / R / —
Service Hash Response / 9.4.5.30
(Service Hash Request ANQP- element) / S / T / R / —
11.25a.3SolicitedPADprocedure

Whendot11SolicitedPADActivatedistrue,anon-APandnon-PCPSTAmaytransmittoanAPorPCPaServiceHashRequestANQP-element.Thiselementincludesoneormoreservicehashesgeneratedfromtheservicename(s)ofthe service(s) that thenon-APandnon-PCPSTA issearching, as wellasvalid combina-tions of services of interest. AnAPorPCPmightadvertise support for the Solicited PADprocedureby set-tingtheSolicitedPADfieldoftheExtendedCapabilitieselementto1initsBeaconandProbeResponseframes.

Whendot11SolicitedPADActivatedistrue,anAPorPCPshallusetheinformationfromtheServiceHashRequestANQP-element(thatitreceivesfromanon-APandnon-PCPSTA)todetermineifitcanprovidetherequestedservice(s)orcombinationofservices.DeterminationisbasedontheservicehashvaluesintheService Hashes field ofthe receivedService Hash RequestANQP-element, andvalidservicecombinationsspecified through theFlagsand ServiceCombinationfieldsofthe Service Hash RequestANQP-element.IftheAPorPCPdeterminesthatitcanprovidetherequestedservice(s)orcombinationofservices,itshallrespondbytransmittingaServiceHashInformationResponseANQP-elementthatcontainsaServiceInformationResponseTuplesubfieldforeachservicethatsatisfiestherequest.

NOTE—Forexample,anAPorPCPthatreceivesaServiceHashRequestANQP-elementframethatincludeshashval-uesfor4servicesS1,S2,S3andS4(inthatorder)andavalueof0xFEEEinitsServiceCombinationfield,respondstotherequestifandonlyifitcanprovideserviceS1orserviceS2orbothservicesS3andS4.TheServiceHash Information ResponseANQP-elementcancontainServiceInformationResponseTuplesubfieldsforanysetofavailableservicesthat satisfytheANQPrequest,e.g., S1,S3and S4.

Therequestingnon-APSTA and non-PCP shallprocesstheServiceHash Information ResponseANQP-elementinthereceivedANQPresponsetoselectaservicecombinationthatsatisfiesthenon-APandnon-PCPSTArequest.

Ifthereisamatchingservicename,thenon-APandnon-PCPSTAmightdecidetoproceedwiththeserviceinformationprocedure(see11.25.3.2.16(Serviceinformationprocedure)orauthenticationandassociationprocedure(see11.3(STAauthenticationandassociation))dependingonthenatureoftheservice(seeexam-plesillustratedinW.1(Pre-associationdiscoveryusagescenarios)).

Submissionpage 1Stephen McCann, BlackBerry