<p>November 2014 doc.: IEEE 802.11-14/1519r2</p><p>IEEE P802.11 Wireless LANs</p><p>TGaq – ANQP update for Venue URL and Access Cost</p><p>Date: 2014-11-06</p><p>Author(s): Name Company Address Phone email Stephen 200 Bath Road, Slough, Berkshire, BlackBerry Ltd +44 1753 667099 [email protected] McCann SL1 3XE, UK m</p><p>Submission page 8 Stephen McCann, BlackBerry November 2014 doc.: IEEE 802.11-14/1519r2</p><p>Add the following reference to Annex A</p><p>[B56] ISO 4217 currency codes, <http://www.currency-iso.org/en/home/tables/table-a1.html></p><p>Modify the table in the following clause as shown:</p><p>* Access Network Query Protocol (ANQP) elements</p><p>T able 8 -2 59 AN Q P-el em ent defi ni ti ons</p><p>ANQP -el em ent name I nfo ID ANQ P-e le me nt (c la use)</p><p>R eserved 0 – 255 n /a</p><p>Q uery L i st 256 E r ror: R eference source not found</p><p>C apabil itL y i st 257 E r ror: R eference source not found</p><p>V enue Na me 258 E r ror: R eference source not found</p><p>E me rgency C alNu l mb er 259 E r ror: R eference source not found</p><p>N et wo rkAu thenti cati on T y pe 260 E r ror: R eference source not found</p><p>R oami ngC onsort ium 261 E r ror: R eference source not found</p><p>I P Ad dress T ype Av ai la bili ty 262 E r ror: R eference source not found</p><p>N AI Re al m 263 E r ror: R eference source not found</p><p>3 GP PC el lula Ne r tw ork 264 E r ror: R eference source not found</p><p>A PG eospat ia lLo cati on 265 E r ror: R eference source not found</p><p>A PC ivic L ocat ion 266 E r ror: R eference source not found</p><p>Submission page 8 Stephen McCann, BlackBerry November 2014 doc.: IEEE 802.11-14/1519r2</p><p>A PL ocat ion Public I dentif ie rUR L 267 E r ror: R eference source not found</p><p>D om aiNa n me 268 E r ror: R eference source not found</p><p>E me rgency A le rtI dentif ie rUR L 269 E r ror: R eference source not found</p><p>T DL C S a pabili ty 270 E r ror: R eference source not found</p><p>E me rgency N AI 271 E r ror: R eference source not found</p><p>N ei ghbor R eport 272 8 .4.4.18 (N ei ghbor Re port ANQP -ele me nt)</p><p>V enue UR L 273 8 .4.4.20 (V enue UR LA NQP -ele me nt)</p><p>A ccess C ost 274 8 .4.4.21 (Ac cess C o stA NQP -ele me nt)</p><p>R eserved 27 53 – 56796 n /a</p><p>V endor Speci fi c 5 6797 E r ror: R eference source not found</p><p>R eserved 5 6798 –65535 n /a</p><p>8.4.4.4 Venue Name ANQP-element</p><p>Insert the following paragraph after the last paragraph</p><p>A URL associated with the Venue can be specified by the Venue URL ANQP-element defined in 8.4.4.20</p><p>Insert the following new subclauses</p><p>8.4.4.20 Venue URL ANQP-element</p><p>The Venue URL ANQP-element specifies URLs which can be used for for webpage advertising services or providng information, particular to a venue, to a STA. The format of the Venue URL ANQP-element is defined in Figure 8-404aq</p><p>Info ID Length Venue URL Duples Octets: 2 2 variable</p><p>Figure 8-404aq – Venue URL ANQP-element format</p><p>The Info ID and Length fields are defined in 8.4.4.1 (General).</p><p>Submission page 8 Stephen McCann, BlackBerry November 2014 doc.: IEEE 802.11-14/1519r2</p><p>The format of the Venue URL Duple field is shown in Figure 8-404aq1</p><p>Venue Length Venue URL Number</p><p>Octets: 1 1 variable</p><p>Figure 8-404aq1 – Venue URL Duple field</p><p>The Length is a 1-octet field whose value is set to 1 plus the number of octets in the Venue URL field.</p><p>The Venue Number is a 1-octet field whose value corresponds to the implicit returned order value of the corresponding Venue Name Duple returned in an Venue Name ANQP-element, as defined in 8.4.4.4. If no Venue Name Duples were returned in the Venue Name ANQP-element then this value is 0.</p><p>The Venue URL field is a variable-length field that indicates the URL at which information relevant to the corresponding Venue Name Duple, indicated by the Venue Number, might be retrieved. This is further described in 10.25.3.2.11. If no Venue URL is provided this field is left empty. The Venue URL field is formatted in accordance with IETF RFC 3986.</p><p>8.4.4.21 Access Cost ANQP-element</p><p>The Access Cost ANQP-element provides financial access cost information to a STA. The format of the Access Cost ANQP-element is defined in Figure 8-405aq</p><p>Access Cost Info ID Length Duples</p><p>Octets: 2 2 variable</p><p>Figure 8-405aq – Access Cost ANQP-element format</p><p>The Info ID and Length fields are defined in 8.4.4.1 (General).</p><p>The format of the Access Cost Duple field is shown in Figure 8-405aq1</p><p>Length Access Cost Type Language Currency Code Plan Information</p><p>Octets: 1 1 3 3 variable</p><p>Figure 8-405aq1 – Access Cost Duple field</p><p>The Length field is a 1-octet field whose value is set to 7 plus the number of octets in the Plan Information field.</p><p>The Access Cost Type is a 1-octet field with the following values:</p><p>Table 8-405 Access Cost Type field values</p><p>Access Cost Type Value Description</p><p>0 Time-based 1 Data-volume-based 2 Time-and-data-volume-based</p><p>Submission page 8 Stephen McCann, BlackBerry November 2014 doc.: IEEE 802.11-14/1519r2</p><p>3 Unlimited 4 Unspecified 5-255 Reserved</p><p>The Language Code is a 3-octet ISO-14962-1997 [B45] encoded string field that defines the language used in the Cost Information field. The Language Code field is a two or three character language code selected from ISO-639 [B44]. A two character language code has 0 (“null” in ISO- 14962-1997) appended to make it 3 octets in length.</p><p>The Currency Code is a 3-octet string (e.g. “USD”) represening an ISO 4217 currency numeric code [B56]</p><p>The Plan Information is a variable length UTF-8 formatted field that carries an XML description of an access cost plan. The UTF-8 format is defined in IETF RFC 3629. The schema and semantics of this description are outside the scope of this standard.</p><p>As ANQP-elements are transmitted in the clear, prior to STA association, protected dual of public action frame should be used after association to verify this information.</p><p>Modify the text and table in the following clause:</p><p>1 0. 25.3 .2 A N Q procedures P</p><p>10.24.3.2.1 General</p><p>…</p><p>Tabl e 10-1 6 A N Q Pusage 0 0b522e7 5e3f f4 53083 e0989e8 bc521 c. docx</p><p>B S S IB SS</p><p>ANQP -el em ent Na me ANQP -el em ent (s ubcl ause) ANQ P-e le me ntT ype AP No n-A PST A S T A</p><p>Q uery L i st 8 .4.4.1 (Q uery L i stANQ P-el em ent ( 11u)) Q T R , T ,R T R ,</p><p>C apabil il tyL ist 8 .4.4.2 (C apabil il tyL Ais t NQP -ele me nt(11u)) S T R , T ,R T R ,</p><p>V enue Na me 8 .4.4.3 (V enue Na me A NQP -ele me nt (11u)) S T R —</p><p>E me rgency C alNu l mb er 8.4.4.4 ( E m ergency Ca llN um ber ANQ P-el em ent (11u)) S T R —</p><p>N et wo rkAu thenti cati on T y pe 8.4.4.5 ( Ne tw ork Au thenti cati onT ype ANQ P-el em ent( 11u)) S T R —</p><p>R oami ngC onsort ium 8.4.4.6 ( R o am ing C o nsorti um ANQ P-el em ent( 11u)) S T R —</p><p>V endor Speci fi c 8.4.4.7 ( Ve ndor Specif ic A NQP -ele me nt(11u)) Q ,S T R , T ,R T R ,</p><p>Submission page 8 Stephen McCann, BlackBerry November 2014 doc.: IEEE 802.11-14/1519r2</p><p>I P Ad dress T ype Av ai la bili ty 8.4.4.8 ( IP A ddress T y pe Av ai la bilit ANQ y P-el em ent (11u)) S T R , T ,R T R ,</p><p>N AI Re al m 8 .4.4.9 (N AI Re al m ANQP -ele me nt(11u)) S T R T R ,</p><p>3 GP PC el lula Ne r tw ork 8.4.4.10 ( 3G PP C e ll ular Ne tw ork ANQP -ele me nt(11u)) S T R —</p><p>A PG eospat ia lLo cati on 8.4.4.11 ( AP G eospat ia lL ocat ion ANQ P-el em ent( 11u)) S T R T R ,</p><p>A PC ivic L ocat ion 8.4.4.12 ( AP C ivic L ocat ion ANQ P-el em ent( 11u)) S T R T R ,</p><p>A PL ocat ion Public I dentif ie rUR L 8.4.4.13 ( AP L ocat ion Publi cI dentif ie rU R LA NQP -ele me nt(11 u)) S T R T R ,</p><p>D om aiNa n me 8.4.4.14 ( Dom aiNa n me A NQP -ele me nt(11u)) S T R —</p><p>E me rgency A le rtI dentif ie rUR L 8.4.4.15 ( E me rgency A le rtU R LA NQP -ele me nt(11u)) S T R T R ,</p><p>T DL C S a pabili ty 8.4.4.18 ( T DL SCa pabili tyA NQP -ele me nt) Q ,S T ,R T ,R T R ,</p><p>E me rgency N AI 8.4.4.16 ( E me rgency N AI ANQ P-el em ent( 11u)) S T R —</p><p>N ei ghbor R eport 8.4.4.19 ( Ne ighbor R eport ANQ P-el em ent) S T R -</p><p>V enue UR L 8.4.4.20 ( Ve nue UR L ANQ P-el em ent) S T R -</p><p>A ccess C ost 8.4.4.21 ( Ac cess C o st ANQP -ele me nt) S T R -</p><p>Symbols Q element is an ANQP query S element is an ANQP response T ANQP-element may be transmitted by MAC entity R ANQP-element may be received by MAC entity —ANQP-element is neither transmitted nor received by MAC entity</p><p>Insert the following new subclauses</p><p>Submission page 8 Stephen McCann, BlackBerry November 2014 doc.: IEEE 802.11-14/1519r2</p><p>10.25.3.2.11 Venue URL procedure</p><p>The Venue URL ANQP-element is used to transmit webpage advertising services or information particular to the venue between STAs.</p><p>This ANQP-element is to be used in conjuction with the Venue Name ANQP-element, to provide extra information about the venue. Typical operation would be to use the Venue Name ANQP-element to determine the list of available venues advertised by a STA, and then the Venue URL ANQP-element is used, if required, to determine a list of venue URLs, each entry corresponding to the Venue Name entry in the list returned by the Venue Name ANQP-element.</p><p>10.25.3.2.12 Access Cost procedure</p><p>The Access Cost ANQP-element is used to transmit financial cost advertisments between STAs in the form of access cost plan information. This information may be of benefit to a receiving STA, or user of a receiving STA, in assisting with a financial decision about proceeding with access.</p><p>The use and operation of the Plan information schema are outside the scope of this standard.</p><p>As ANQP-elements are transmitted in the clear, prior to STA association, protected dual of public action frame should be used after association to verify this information.</p><p>Submission page 8 Stephen McCann, BlackBerry</p>