Implementation Considerations

General System Model

An overview of LSNS is given in Figure 7, which we will refer to below. Figure 8 presents the details of this Wireless Data & Voice network and is essentially a more detailed and less abstract version of Figure 8 (Chapter ). The shaded areas are the focus of this document.

The following functional breakdowns and their respective requirements from Figure 7 are:

• Network Agent for Location and Status

  The functions of the Network Agent for Location and Status are carried out via a Location Directory. The Location Directory maintains an information base of the current forwarding address for each M-ES in its home area.

  A necessary enhancement to the Network Agent for Location and Status is a Notification Request Directory that keeps track of which M-ESs the C-ES seeks information. They can be implemented as an extension to the location directory.

  Overall, the Network Agent for Location and Status must be capable of:

  • Providing the LSNS with the current location of an M-ES.

  • Registering those C-ESs which seek information on an M-ES, and conveying this information to the LSNS when necessary.

• LSNS

  The LSNS needs to interact with the Network Agent for Location and Status , C-ESs, M-ESs, and the System Management. With the Network Agent for Location and Status , the LSNS should be able of determining the current location of an M-ES, as well as the list of C-ESs wishing to communicate with an M-ES. With System Management, interaction is as specified above. With the C-ES, the LSNS needs to be capable of providing it with a Status Notification Report on one or more M-ESs. With the M-ES the LSNS needs to be able to relay the desire to communicate of a C-ES to it.

• System Management

  At any given point in time, system management must be aware of, capable of performing, and/or regulating a number of system parameters. These could be the capability of:

  • Determining the number of users that are active,
  • The general activity level of the network (LSNS + C-ES + M-ES),
  • Authentication of the C-ES, etc.

  System management must interact continuously with the LSNS to furthermore determine

  • Determine the load on the system,
  • Gauge its performance over time through monitoring its response to requests for status notification and communication
  • Enable or disable security and access control mechanisms between the LSNS and the M-ES or C-ES
  • Ensure that the LSNS is running within accepted limits of operation.

  

Figure 7: System Model Block Diagram

2#2