XML Interface DTD - Nomadix
XML Interface DTDConfidentialRelease 8.830851 Agoura Road, Suite 102Agoura Hills, CA 91301, USA 1.818.597.1500http://www.nomadix.com/
ContentsDisclaimer . 21. XML Command Authentication . 42. Radius Subscriber Administration Commands . 42.1 User Login Command for Radius Subscriber Login . 42.2 User Logout Command for Radius Subscriber Logout . 63. Subscriber Administration Commands . 73.1 User Add Command. 73.2 Device Add Command . 133.3 Group Add Command . 163.4 Update Cache Command . 193.5 Bandwidth Up Command. 203.6 Bandwidth Down Command . 213.7 Max Bandwidth Down Command . 223.8 Max Bandwidth Up Command. 233.9 User Payment Command . 243.10 User Delete Command. 283.11 Device Delete Command . 293.12 User Query Command . 313.13 Subscriber Query Current command . 343.14 Subscriber Query Auth Command . 423.15 User Authorize Command . 473.16 User Purchase Command . 493.17 PMS Pending Transaction Command . 514. Room Administration Commands. 544.1 Room Set Access Command . 544.2 Room Query Access Command. 555. Standard Response . 575.1 Standard OK/ERROR Response . 575.2 Response Errors for XML Command . 586. User Status Messages for Radius and 2-way PMS . 596.1 User Status Message for Radius Login/Logout . 596.2 PMS User Status . 617. PMS Redirector Status/Response Messages . 647.1 PMS Link Status. 647.2 PMS Transaction Response . 667.3 PMS Unsolicited Response . 688. WAN Status . 699. XML Format for DAT table . 7010. XML Format for Current Subscriber Table . 7211. XML Format for Subscribers in Authorized Database . 7512. XML Format for Group Bandwidth Policy List. 8013. XML Format for Individual Group Bandwidth Policy . 8114. XML Format for PMS Pending Transaction List. 8215. XML Format for Individual PMS Pending Transaction . 84Page 1 of 110Nomadix ConfidentialAugust 4, 2016
16. XML Format for PMS Completed Transaction List . 8517. XML Format for Individual PMS Completed Transaction . 8718. XML Format for Port-location List. 8819. XML Format for Getting Individual Port-location . 9120. XML Format for Setting Individual Port-location . 9421. XML Format for Removing Individual Port-location . 9722. Active Routing Tables Commands . 9822.1 Listing Active Routes . 9822.2 Deleting Active Routes. 9822.3 Table IDs . 9822.4 Route IDs . 9822.5 Active Route DTD . 9823. Persistent Routing Tables Commands. 10023.1 Listing Persistent Routes . 10023.2 Adding Persistent Routes . 10023.3 Deleting Persistent Routes. 10023.4 Table IDs . 10123.5 Route IDs . 10123.6 Persistent Route DTD . 10124. Static Routing Tables Commands . 10324.1 Listing Static Routes . 10324.2 Adding Static Routes . 10324.3 Deleting Persistent Routes. 10324.4 Table IDs . 10424.5 Route IDs . 10424.6 Persistent Route DTD . 10425. Class Based Queueing Commands. 10725.1 Listing Classes . 10725.2 Adding Classes . 10725.3 Deleting Classes . 10725.4 Interface IDs . 10725.5 Class IDs. 10725.6 Class DTD . 108Contact Information: . 110DisclaimerThere are a number of caveats that need to be expressly stated:1. Nomadix does not guarantee that following these guidelines will ensure theproblem-free interoperability between the web server running the XML scriptsand Nomadix technology.Page 2 of 110Nomadix ConfidentialAugust 4, 2016
2. To ensure accuracy for future releases, Nomadix reserves the right to change andadd to this specification without notice.Page 3 of 110Nomadix ConfidentialAugust 4, 2016
1. XML Command AuthenticationAll XML commands are authenticated before being acted upon. The NSE supports two methodsof authentication, each of which can be enabled/disabled via configuration. Authenticate via IP address – This legacy method of authentication verifies that the IPaddress of the peer (the sender of the XML command) matches one of the configuredpeer addresses (referred to as XML Server 1 through XML Server 4) Authenticate via user credentials – This method of authentication verifies the usercredentials supplied in the HTTP request used to transport the XML command.Commands that update the NSE’s operating state require a privilege level of“administrator” or “XML”. The “operator” privilege level is also allowed for commandsthat simply retrieve state.All XML commands are available via the HTTP port (80) or the HTTPS port (443). That is,commands that specify a port of 1111 or 1112 are also available on port 80 or 443.Commands that specify a port of 80 or 443 are only available on those ports (i.e. they are notavailable on ports 1111 or 1112).Both authentication methods described above are available on the HTTP port (80) and theHTTPS port (443).Only the first authentication method (Authenticate via IP address) is available on port 1111and port 1112.2. Radius Subscriber Administration CommandsNOTE: The commands listed in this section should be sent as a POST to one of thefollowing addresses:http://NSE URI:1111/usg/command.xmlhttps://NSE URI:1112/usg/command.xmlPlease note the port difference between standard and secure transmissions.2.1 User Login Command for Radius Subscriber LoginThe Portal Page web server can send this command to instruct the NSE to send a RADIUSauthentication request to the RADIUS server to authenticate a subscriber. This is the XMLcommand with the following DTD:Page 4 of 110Nomadix ConfidentialAugust 4, 2016
?xml version "1.0" encoding "UTF-8"? !-DTD defines Login command sent to NSE-- !ELEMENT SUB USER NAME (#PCDATA) !ELEMENT SUB PASSWORD (#PCDATA) !ELEMENT SUB MAC ADDR (#PCDATA) !ELEMENT PORTAL SUB ID (#PCDATA) !ELEMENT USG (SUB USER NAME, SUB PASSWORD, SUB MAC ADDR,PORTAL SUB ID?) !ATTLIST USG COMMAND CDATA #REQUIRED Where:COMMAND attribute: ‘RADIUS LOGIN’SUB USER NAME: Subscriber’s username (char [96])SUB PASSWORD: Subscriber’s password (char [128])SUB MAC ADDR: Subscriber’s MAC address (char [12])PORTAL SUB ID (optional): Unique identifier that the Portal Page web server can send to theNSE which will be sent back with status response (char [36])Sample command XML: USG COMMAND "RADIUS LOGIN" SUB USER NAME jsmith /SUB USER NAME SUB PASSWORD abc123 /SUB PASSWORD SUB MAC ADDR 1A2B3C4D5E6F /SUB MAC ADDR PORTAL SUB ID 12345678-1234-1234-1234-123456789012 /PORTAL SUB ID /USG Response for the Login CommandStandard: As a response to this command, the web server will get an acknowledgement XMLmessage from the NSE (OK or ERROR, see “Standard OK/ERROR Response” section for DTDdefinition).The NSE will send status message asynchronously if the “Portal XML POST URL” is enabled inthe AAA section of the NSE (see User Status Message section).Page 5 of 110Nomadix ConfidentialAugust 4, 2016
2.2 User Logout Command for Radius Subscriber LogoutThe Portal Page web server can send this command to instruct the NSE to logout the subscriber.This is the XML command with the following DTD: ?xml version "1.0" encoding "UTF-8"? !-DTD defines Logout command sent to NSE-- !ELEMENT SUB MAC ADDR (#PCDATA) !ELEMENT SUB USER NAME (#PCDATA) !ELEMENT USG (SUB MAC ADDR, SUB USER NAME) !ATTLIST USG COMMAND CDATA #REQUIRED Where:COMMAND attribute: ‘LOGOUT’SUB MAC ADDR: Subscriber’s MAC address (char [12], optional if username is present)SUB USER NAME: Subscriber’s username (char [96], optional if MAC address is present)Sample command XML: USG COMMAND "LOGOUT" SUB MAC ADDR 1A2B3C4D5E6F /SUB MAC ADDR SUB USER NAME jsmith /SUB USER NAME /USG Response for the Logout CommandStandard: As a response to this command, the web server will get an acknowledgement XMLmessage from the NSE (OK or ERROR, see “Standard OK/ERROR Response” section for DTDdefinition).The NSE will send status message asynchronously if the “Portal XML POST URL” is enabled inthe AAA section of the NSE (see User Status Message).Page 6 of 110Nomadix ConfidentialAugust 4, 2016
3. Subscriber Administration CommandsNOTE: Unless specified otherwise, the commands listed in this section should be sent as aPOST to one of the following addresses:http://NSE URI:1111/usg/command.xmlhttps://NSE URI:1112/usg/command.xmlPlease note the port difference between standard and secure transmissions.3.1 User Add CommandThe specified subscriber has been authorized for access and will be added to the NSE’s MACauthorization table. If the subscriber is in the ‘Current’ (active) memory table of the NSE then theUpdate Cache XML command must follow in order to correctly update the subscriber. This is theXML command with the following DTD:Page 7 of 110Nomadix ConfidentialAugust 4, 2016
?xml version "1.0" encoding "UTF-8"? !-DTD defines User Add command sent to NSE-- !ELEMENT USER NAME (#CDATA) !ELEMENT PASSWORD(#PCDATA) !ELEMENT EXPIRY TIME (#PCDATA) !ELEMENT COUNTDOWN (#PCDATA) !ELEMENT ROOM NUMBER (#PCDATA) !ELEMENT PAYMENT METHOD (#PCDATA) !ELEMENT PLAN (#PCDATA) !ELEMENT IP TYPE (#PCDATA) !ELEMENT DHCP SUBNET(#PCDATA) !ELEMENT CONFIRMATION (#PCDATA) !ELEMENT PAYMENT (#PCDATA) !ELEMENT USER DEF1 (#CDATA) !ELEMENT USER DEF2 (#CDATA) !ELEMENT SMTP REDIRECT (#PCDATA) !ELEMENT BANDWIDTH UP (#PCDATA) !ELEMENT BANDWIDTH DOWN (#PCDATA) !ELEMENT BANDWIDTH MAX UP (#PCDATA) !ELEMENT BANDWIDTH MAX DOWN (#PCDATA) !ELEMENT QOS POLICY (#PCDATA) !ELEMENT CLASS NAME (#PCDATA) !ELEMENT USG (USER NAME?, PASSWORD?, EXPIRY TIME?, COUNTDOWN?,ROOM NUMBER?, PAYMENT METHOD, PLAN?, IP TYPE?, DHCP SUBNET?,CONFIRMATION?, PAYMENT?, USER DEF1?, USER DEF2?, SMTP REDIRECT?,BANDWIDTH UP?, BANDWIDTH DOWN?, BANDWIDTH MAX UP?,BANDWIDTH MAX DOWN?, QOS POLICY?,CLASS NAME?) !ATTLIST USGCOMMAND CDATA #REQUIREDMAC ADDR CDATA !ATTLIST PASSWORD ENCRYPT (TRUE FALSE) #REQUIRED !ATTLIST EXPIRY TIMEUNITS (SECONDS MINUTES HOURS DAYS) #REQUIRED Where:COMMAND attribute: USER ADDMAC ADDR attribute (optional): Subscriber’s MAC address (char [12])USER NAME (optional): Subscriber’s username (char [96])PASSWORD (optional): Subscriber’s password (char [128])ENCRYPT attribute: Either TRUE or FALSEEXPIRY TIME (optional): Expiry timeUNITS attribute: Either SECONDS, MINUTES, HOURS or DAYSROOM NUMBER (optional): (char [8])Page 8 of 110Nomadix ConfidentialAugust 4, 2016
PAYMENT METHOD (optional but recommended): Either "RADIUS", "PMS","CREDIT CARD", or "ROOM OPEN"IP TYPE (optional): Either “PRIVATE” or “PUBLIC”DHCP SUBNET (optional): Subnet based on configured DHCP subnets in the NSECONFIRMATION (optional): Confirmation number/IDPAYMENT (optional): Amount charged for accessUSER DEF1 (optional): User definable string (char [128]), if not provided in the command, NSEwill empty it.USER DEF2 (optional): User definable string (char [128]), if not provided in the command, NSEwill empty it.COUNTDOWN (optional): 0 off, 1 enabled. If not present, it defaults to off. (NOTE: If a billingplan is specified and it is an X-over-Y billing plan, then the countdown element, if present, isirrelevant and is ignored.PLAN: (optional): This relates to the X over Y plan number in Billing Plans setup. If used for Xover Y, USER NAME and PASSWORD are required.SMTP REDIRECT: (optional): Either TRUE or FALSE for SMTP Redirection enabled for thatuser. If not included, the User will have this variable as TRUE for their profile.BANDWIDTH UP: (optional): This will set the Upstream Bandwidth for a user without havingto send the other Bandwidth XML command. Legacy element that is obsolete because ofBandwidth Max Up.BANDWIDTH DOWN: (optional): This will set the Downstream Bandwidth for a user withouthaving to send the other Bandwidth XML Command. Legacy element that is obsolete because ofBandwidth Max Down.BANDWIDTH MAX UP: (optional): This will set the Maximum Upstream bandwidth for theuser without having to send the other Bandwidth XML Command.BANDWIDTH MAX DOWN: (optional): This will set the Maximum Downstream bandwidthfor the user without having to send the other Bandwidth XML Command.QOS POLICY: (optional): Select and add the QoS Policy that is configured on the NSE to theprofile for the user.CLASS NAME: (optional): Class name (char [64]) indicates the class that traffic to/from thisuser should be assigned to for Class-Based Queuing purposes.Page 9 of 110Nomadix ConfidentialAugust 4, 2016
Sample command XML (Normal Plan): USG COMMAND "USER ADD" MAC ADDR "1A2B3C4D5E6F" USER NAME ![CDATA[jsmith]] /USER NAME PASSWORD ENCRYPT ”FALSE” JSMITH6 /PASSWORD EXPIRY TIME UNITS ”SECONDS” 60 /EXPIRY TIME COUNTDOWN 1 /COUNTDOWN ROOM NUMBER 1234 /ROOM NUMBER PAYMENT METHOD CREDIT CARD /PAYMENT METHOD IP TYPE PRIVATE /IP TYPE DHCP SUBNET 192.168.1.0 /DHCP SUBNET CONFIRMATION 123abc /CONFIRMATION PAYMENT 9.95 /PAYMENT USER DEF1 ![CDATA[meeting room]] /USER DEF1 USER DEF2 ![CDATA[whatever string]] /USER DEF2 SMTP REDIRECT TRUE /SMTP REDIRECT BANDWIDTH MAX UP 256 /BANDWIDTH MAX UP BANDWIDTH MAX DOWN 256 /BANDWIDTH MAX DOWN QOS POLICY QoSPolicy1 /QOS POLICY CLASS NAME Lobby /CLASS NAME /USG Sample command XML (X over Y Plan):Page 10 of 110Nomadix ConfidentialAugust 4, 2016
USG COMMAND "USER ADD" MAC ADDR "1A2B3C4D5E6F" USER NAME ![CDATA[jsmith]] /USER NAME PASSWORD ENCRYPT ”FALSE” JSMITH6 /PASSWORD PAYMENT METHOD CREDIT CARD /PAYMENT METHOD PLAN 0 /PLAN USER DEF1 ![CDATA[meeting room]] /USER DEF1 USER DEF2 ![CDATA[whatever string]] /USER DEF2 SMTP REDIRECT TRUE /SMTP REDIRECT BANDWIDTH MAX UP 256 /BANDWIDTH MAX UP BANDWIDTH MAX DOWN 256 /BANDWIDTH MAX DOWN QOS POLICY QoSPolicy1 /QOS POLICY /USG Page 11 of 110Nomadix ConfidentialAugust 4, 2016
Response for the User Add CommandStandard: As a response to this command, the web server will get an acknowledgement XMLmessage from the NSE (OK or ERROR, see “Standard OK/ERROR Response” section for DTDdefinition).Page 12 of 110Nomadix ConfidentialAugust 4, 2016
3.2 Device Add CommandIn which a specified Device is authorized for access, and is added to the NSE authorized MACaddress database. The device is furthermore guaranteed access at any time by reserving apermanent entry for it in the NSE Current (active) subscriber table. ?xml version "1.0" encoding "UTF-8"? !-DTD defines Device Add command sent to NSE-- !ELEMENT DEVICE NAME (#CDATA) !ELEMENT IP ADDR (#PCDATA) !ELEMENT DHCP SUBNET(#PCDATA) !ELEMENT PROXY ARP (#PCDATA) !ELEMENT VLAN (#PCDATA) !ELEMENT USER DEF1 (#CDATA) !ELEMENT USER DEF2 (#CDATA) !ELEMENT SMTP REDIRECT (#PCDATA) !ELEMENT BANDWIDTH MAX UP (#PCDATA) !ELEMENT BANDWIDTH MAX DOWN (#PCDATA) !ELEMENT QOS POLICY (#PCDATA) !ELEMENT CLASS NAME (#PCDATA) !ELEMENT USG (DEVICE NAME?,IP ADDR?, DHCP SUBNET?,PROXY ARP?, VLAN?,USER DEF1?, USER DEF1?,SMTP REDIRECT?,BANDWIDTH MAX UP?, BANDWIDTH MAX DOWN?,QOS POLICY?, CLASS NAME?) !ATTLIST USG COMMAND CDATA #REQUIREDMAC ADDR CDATA #REQUIRED Where:Attributes (mandatory)COMMANDDEVICE ADDMAC ADDRMAC address of the deviceShould a prior Device or User entry exists in the NSE databasefor this same MAC address, it will be overwritten by thiscommand.Page 13 of 110Nomadix ConfidentialAugust 4, 2016
Elements (optional)DEVICE NAMEA short name for the device (char[96]) to assist administratoror operator recognition of it.IP ADDRThe IP address associated with the device, if any.DHCP SUBNETThe IP subnet mask of an NSE DHCP address pool that thedevice shall draw its IP address from, should it need to.PROXY ARPEnable (TRUE) or disable (FALSE) Proxied ARP for thisdevice.Proxied ARP allows a device to communicate directly withother subscriber-side devices, similarly configured, regardlessof which VLAN those devices are attached to.VLAN802.1Q VLAN port that device is attached to (0 VLAN 4095).If omitted or zero, the device will be granted access no matterwhere it has attached; but if a non-zero VLAN is specified, thedevice will only be granted access when attached to thatVLAN.USER DEF1User-defined content associated with the device, comprisingany sequence of UTF-8 code points that does not exceed 128octets in length.USER DEF2User-defined content associated with the device, comprisingany sequence of UTF-8 code points that does not exceed 128octets in length.SMTP REDIRECTEnable (TRUE) or disable (FALSE) SMTP Redirection forthe device.BANDWIDTH MAX UPMaximum Upstream Bandwidth to be granted the device.BANDWIDTH MAX DOWN Maximum Downstream Bandwidth to be granted this device.QOS POLICYThe name of any NSE QoS Policy that should apply to thedevice.CLASS NAMEThe name of any NSE Bandwidth Class that should apply tothe device.Page 14 of 110Nomadix ConfidentialAugust 4, 2016
Sample command XML: USG COMMAND "DEVICE ADD" MAC ADDR "1A2B3C4D5E6F" DEVICE NAME ![CDATA[Erasmus]] /USER NAME IP ADDR 192.168.1.44 /IP ADDR DHCP SUBNET 192.168.1.0 /DHCP SUBNET PROXY ARP TRUE /PROXY ARP VLAN 14 /VLAN USER DEF1 ![CDATA[meeting room]] /USER DEF1 USER DEF2 ![CDATA[whatever string]] /USER DEF2 SMTP REDIRECT TRUE /SMTP REDIRECT BANDWIDTH MAX UP 256 /BANDWIDTH MAX UP BANDWIDTH MAX DOWN 256 /BANDWIDTH MAX DOWN QOS POLICY QoSPolicy1 /QOS POLICY CLASS NAME Lobby /CLASS NAME /USG Response for the Device Add CommandStandard: As a response to this command, the web server will get an acknowledgement XMLmessage from the NSE (OK or ERROR, see “Standard OK/ERROR Response” section for DTDdefinition).Page 15 of 110Nomadix ConfidentialAugust 4, 2016
3.3 Group Add CommandThe Specified Group is added to the authorized database of the NSE and utilizes the listedattributes for the group. This is the XML command with the following DTD: ?xml version "1.0" encoding "UTF-8"? !-DTD defines Group Add command sent to NSE-- !ELEMENT USER NAME (#CDATA) !ELEMENT PASSWORD(#PCDATA) !ELEMENT EXPIRY TIME (#PCDATA) !ELEMENT DHCP TYPE (#PCDATA) !ELEMENT DHCP SUBNET(#PCDATA) !ELEMENT PAYMENT (#PCDATA) !ELEMENT USER DEF1 (#CDATA) !ELEMENT USER DEF2 (#CDATA) !ELEMENT SMTP REDIRECT (#PCDATA) !ELEMENT BANDWIDTH MAX UP (#PCDATA) !ELEMENT BANDWIDTH MAX DOWN (#PCDATA) !ELEMENT QOS POLICY (#PCDATA) !ELEMENT GROUP USERS MAX (#PCDATA) !ELEMENT CLASS NAME (#PCDATA) !ELEMENT VALID UNTIL (#PCDATA) !ELEMENT USG (USER NAME, PASSWORD, EXPIRY TIME, DHCP TYPE?, DHCP SUBNET?,PAYMENT?, USER DEF1?, USER DEF1?, SMTP REDIRECT?, BANDWIDTH MAX UP?,BANDWIDTH MAX DOWN?, QOS POLICY?, GROUP USERS MAX?,CLASS NAME?,VALID UNTIL?) !ATTLIST USGCOMMAND CDATA #REQUIRED !ATTLIST PASSWORD ENCRYPT (TRUE FALSE) #REQUIRED !ATTLIST EXPIRY TIMEUNITS (SECONDS MINUTES HOURS DAYS) #REQUIRED Where:COMMAND attribute: GROUP ADDUSER NAME (Required): Group’s username (char [96])PASSWORD (Required): Group’s password (char [128])ENCRYPT attribute: Either TRUE or FALSEEXPIRY TIME (Required): Expiry timeUNITS attribute: Either SECONDS, MINUTES, HOURS or DAYSDHCP TYPE (optional): Either “PRIVATE” or “PUBLIC”DHCP SUBNET (optional): Subnet based on configured DHCP subnets in the NSEPAYMENT (optional): Amount charged for accessPage 16 of 110Nomadix ConfidentialAugust 4, 2016
USER DEF1 (optional): User definable string (char [128]), if not provided in the command, NSEwill empty it.USER DEF2 (optional): User definable string (char [128]), if not provided in the command, NSEwill empty it.SMTP REDIRECT: (optional): Either TRUE or FALSE for SMTP Redirection enabled for thatuser. If not included the User will have this variable as TRUE for their profile.BANDWIDTH MAX UP: (optional): This will set the Maximum Upstream bandwidth for theuser without having to send the other Bandwidth XML Command.BANDWIDTH MAX DOWN: (optional): This will set the Maximum Downstream bandwidthfor the user without having to send the other Bandwidth XML Command.QOS POLICY (optional): Select and add the QoS Policy that is configured on the NSE to theprofile for the user.GROUP USERS MAX (optional): This will set the maximum number of concurrent users thatcan utilize this Group account.CLASS NAME: (optional): Class name (char [64]) indicates the class that traffic to/from thisuser should be assigned to for Class-Based Queuing purposes.VALID UNTIL: (optional): The date/time at which this group will cease to exist. If non-empty,must be expressed in a valid ISO 8601 format. Absence of this element or an empty string meansthe group will have permanent (until administratively deleted) existence. A date/time that doesnot lie in the future (with respect to the NSE’s current time) will be rejected as an error. Thegranularity of this parameter is in minutes, so if the ISO 8601 string includes seconds they will beignored (i.e., treated as if submitted as “00”).Page 17 of 110Nomadix ConfidentialAugust 4, 2016
Sample command XML: USG COMMAND "GROUP ADD" USER NAME ![CDATA[Conference1]] /USER NAME PASSWORD ENCRYPT ”FALSE” users /PASSWORD EXPIRY TIME UNITS ”SECONDS” 600 /EXPIRY TIME DHCP SUBNET 192.168.1.0 /DHCP SUBNET DHCP TYPE PRIVATE /DHCP TYPE PAYMENT 9.95 /PAYMENT USER DEF1 ![CDATA[meeting room1]] /USER DEF1 USER DEF2 ![CDATA[whatever string]] /USER DEF2 SMTP REDIRECT TRUE /SMTP REDIRECT BANDWIDTH MAX UP 256 /BANDWIDTH MAX UP BANDWIDTH MAX DOWN 256 /BANDWIDTH MAX DOWN QOS POLICY QoSPolicy1 /QOS POLICY GROUP USERS MAX 25 /GROUP USERS MAX CLASS NAME Lobby /CLASS NAME VALID UNTIL 2014-08-15T11:00-07:00 /VALID UNTIL /USG Response for the Group Add CommandStandard: As a response to this command, the web server will get an acknowledgement XMLmessage from the NSE (OK or ERROR, see “Standard OK/ERROR Response” section for DTDdefinition).Page 18 of 110Nomadix ConfidentialAugust 4, 2016
3.4 Update Cache CommandThe memory authorization table entry specified by the MAC address will have its status changedfrom “pending” to “authorized”. NOTE: It is important to update the cache to enable properaccess for the subscriber. This is the XML command with the following DTD: ?xml version "1.0" encoding "UTF-8"? !-DTD defines Update Cache command sent to NSE-- !ELEMENT PAYMENT METHOD (#PCDATA) !ELEMENT USG (PAYMENT METHOD?) !ATTLIST USGCOMMAND CDATA #REQUIREDMAC ADDR CDATA #REQUIRED Where:COMMAND attribute: CACHE UPDATEMAC ADDR attribute: Subscriber’s MAC address (char [12])Sample command XML: USG COMMAND "CACHE UPDATE" MAC ADDR ”1A2B3C4D5E6F" /USG Response for the Update Cache CommandStandard: As a response to this command, the web server will get an acknowledgement XMLmessage from the NSE (OK or ERROR, see “Standard OK/ERROR Response” section for DTDdefinition).Page 19 of 110Nomadix ConfidentialAugust 4, 2016
3.5 Bandwidth Up CommandSet the Bandwidth Up for an authorized subscriber. This is the XML command with the followingDTD: ?xml version "1.0" encoding "UTF-8"? !-DTD defines Bandwidth Up command sent to NSE-- !ELEMENT BANDWIDTH UP (#PCDATA) !ELEMENT USG (BANDWIDTH UP) !ATTLIST USGCOMMAND CDATA #REQUIREDSUBSCRIBER CDATA #REQUIRED Where:COMMAND attribute: SET BANDWIDTH UPSUBSCRIBER attribute: Subscriber’s MAC address (char [12])BANDWIDTH UP: (number measured in Kbps (i.e. for 128,000 bits per second, enter 128))Sample command XML: USG COMMAND "BANDWIDTH UP" SUBSCRIBER "1A2B3C4D5E6F" BANDWIDTH UP 128 /BANDWIDTH UP /USG Response for the Bandwidth Up CommandStandard: As a response to this command, the web server will get an acknowledgement XMLmessage from the NSE (OK or ERROR, see “Standard OK/ERROR Response” section for DTDdefinition).Page 20 of 110Nomadix ConfidentialAugust 4, 2016
3.6 Bandwidth Down CommandSet the Bandwidth Down for an authorized subscriber. This is the XML command with thefollowing DTD: ?xml version "1.0" encoding "UTF-8"? !-DTD defines Bandwidth Down command sent to NSE-- !ELEMENT BANDWIDTH DOWN (#PCDATA) !ELEMENT USG (BANDWIDTH DOWN) !ATTLIST USGCOMMAND CDATA #REQUIREDSUBSCRIBER CDATA #REQUIRED Where:COMMAND attribute: SET BANDWIDTH DOWNSUBSCRIBER attribute: Subscriber’s MAC address (char [12])BANDWIDTH DOWN: (number measured in Kbps (i.e. for 128,000 bits per second, enter 128))Sample command XML: USG COMMAND "BANDWIDTH DOWN" SUBSCRIBER "1A2B3C4D5E6F" BANDWIDTH DOWN 256 /BANDWIDTH DOWN /USG Response for the Bandwidth Down CommandStandard: As a response to this command, the web server will get an acknowledgement XMLmessage from the NSE (OK or ERROR, see “Standard OK/ERROR Response” section for DTDdefinition).Page 21 of 110Nomadix ConfidentialAugust 4, 2016 page
2.2 User Logout Command for Radius Subscriber Logout The Portal Page web server can send this command to instruct the NSE to logout the subscriber. This is the XML command with the following DTD: ?xml version "1.0" encoding "UTF-8"? !-- DTD defines Logout command sent to NSE -- !ELEMENT SUB_MAC_ADDR (#PCDATA) !ELEMENT SUB_USER_NAME (# .
Uses of XML XML data comes from many sources on the web: web servers store data as XML files databasessometimes return query results as XML webservices use XML to communicate XML is the de facto universal format for exchange of data XML languages are used for music, math, vector graphics popular use: RSS for news feeds & podcasts CSC443: Web Programming
The design goals for XML are: 1. XML shall be straightforwardly usable over the Internet. 2. XML shall support a wide variety of applications. 3. XML shall be compatible with SGML. 4. It shall be easy to write programs which process XML documents. 5. The number of optional features in XML is to be kept to the absolute minimum, ideally zero. 6.
The number of optional features in XML is to be kept to the absolute minimum, ideally zero XML documents should be human-legible and reasonably clear The XML design should be prepared quickly The design of XML shall be formal and concise XML documents should be easy to create Terseness in XML markup is of minimal importance
C Provide the XML services more and more customers want, or C Watch your customer base shrink You can: C Learn to work with XML smoothly and easily, or C Fight XML tooth and nail You can: C Use XML content to make some of your processes easier C Let XML be an added step, added expense, and continual nuisance You can't make XML go away! Page 2
Overview XML More about XML We will talk about algorithms and programming techniques to efficiently manipulate XML data: I Regular expressions can be used to validate XML data, I finite state machines lie at the heart of highly efficient XPath implementations, I tree traversals may be used to preprocess XML trees in order to support XPath evaluation, to store XML trees in databases, etc.
2. Learn how to construct a valid XML Schema and associate it with an XML document. 3. Learn why XML Schemas are more powerful than DTDs. 1. amazon.dtdOpen files "amazon.xml", " " and "amazon.xsd" with EditX. The "amazon.xsd" is an XML Schema document that describes part of the structure of the " amazon.xml" XML document presented in Lab 1.1.1 .
development of XML code. In the first week, you'll learn a lot of the basics about XML itself: On Day 1, you'll get a basic introduction on what XML is and why it's so important. You will also see your first XML document. On Day 2, you will dissect an XML document to discover exactly what goes into making usable XML code.
cepté la motion du 18 février 2003 (03.3007 - Recherche sur l’être humain. Création d’une base constitutionnelle), la chargeant de préparer une disposition constitutionnelle concernant la re- cherche sur l’être humain. Pour sa part, la mise en chantier de la loi fédérale relative à la recher-che sur l’être humain a démarré en décembre 2003. La nouvelle disposition .
