Identity Extension Examples

The following sections provide examples of how HELD identity extensions may be used to assist with location determination for the correct end-point.

DHCP Example

 <heldDevice xmlns="http://sitacs.uow.edu.au/ns/location/heId:deviceldentifiers">    <dhcp>       <giaddr>192.168.5.9</giaddr>       <agentID>Netgear-1</agentID>       <circuitID>010/50</circuitID>    </dhcp> </heldDevice> 

The preceding sample describes DHCP-related information that may assist in identifying a Target. This may be employed in a DSL network where an ISP uses DHCP to allocate IP addresses but needs to send the circuit information to an RANP LIS in order to obtain the actual location. A HELD request containing this additional information would look similar to the following code fragment.

 <locationRequest    xmlns="http://sitacs.uow.edu.au/ns/location/held">    <heldDevice       xmlns="http://sitacs.uow.edu.au/ns/location/held:deviceIdentifiers">       <dhcp>          <giaddr>192.168.5.9</giaddr>          <agentID>Netgear-1</agentID>          <circuitID>010/50</circuitID>       </dhcp>     </heldDevice> </locationRequest> 

L2TP Example

 <heldDevice xmlns="http://sitacs.uow.edu.au/ns/location/held:deviceIdentifiers">    <l2tp>       <sourceIP>192.168.4.10</sourceIP>        <destinationIP>10.1.0.60</destinationIP>        <sessionID>528</sessionID>    </l2tp> </heldDevice> 

The preceding sample describes L2TP session information that may assist in identifying a Target. This may be used in a DSL network where an ISP is connected to an RANP BRAS over an L2TP link. A HELD request containing this additional information would look similar to the code fragment that follows.

 <locationRequest xmlns="http://sitacs.uow.edu.au/ns/location/held">    <heldDevice       xmlns="http://sitacs.uow.edu.au/ns/location/held:deviceIdentifiers">       <l2tp>          <sourceIP>192.168.4.10</sourceIP>          <destinationIP>10.1.0.60</destinationIP>          <sessionID>528</sessionID>       </l2tp>    </heldDevice> </locationRequest> 

LLDP Example

 <heldDevice xmlns="http://sitacs.uow.edu.au/ns/location/held:deviceIdentifiers">    <lldp>       <chassisType>211</chassisType>       <chassisID>10.1.0.60</chassisID>       <portType>10</portType>       <portID>192.168.55.7</portID>    </lldp> </heldDevice> 

The preceding sample describes switch and port information provided to an end-point using LLDP. A Target may provide this information to an LIS in an enterprise environment to assist in Target identification and location determination. A HELD request containing this additional information would look similar to the following code fragment.

 <locationRequest xmlns="http://sitacs.uow.edu.au/ns/location/held">    <heldDevice       xmlns="http://sitacs.uow.edu.au/ns/location/held:deviceldentifiers">       <lldp>          <chassisType>211</chassisType>          <chassisID>10.1.0.60</chassisID>          <portType>10</portType>          <portID>192.168.55.7</portID>       </lldp>    </heldDevice> </locationRequest>