Software Requirements Specification

For

Anonymous User Communication For Privacy Protection in Wireless Metropolitan Mesh Networks

Prepared by

Under the Guidance of

Table of Contents

Revision History

1. Introduction

1.1 Purpose 1.2 Project Scope 1.3 References

2. Overall Description

2.1 Product Perspective 2.2 Product Features 2.3 User Classes and Characteristics 2.4 Operating Environment 2.5 Design and Implementation Constraints

3. System Features

3.1 System Feature 1 3.2 System Feature 2 (and so on)

4. External Interface Requirements

4.1 User Interfaces 4.2 Hardware Interfaces 4.3 Software Interfaces 4.4 Communications Interfaces

5. Other Nonfunctional Requirements

5.1 Performance Requirements 5.2 Safety Requirements 5.3 Security Requirements 5.4 Software Quality Attributes

6. Other Requirements

Appendix A: Glossary
Appendix B: Analysis Models

1. Introduction

1. Purpose

The project is to make available security and privacy protection to the user credentials in wireless mesh networks (WMN) using group signature and pair wise secrets terms. 2. Project Scope In wireless mesh network, there is no restriction for public to access the internet or mobile services. So that the large numbers of attacks are might be happened like eavesdrop, inject or impersonate in WMN.All these attacks are great threat to the user credential, because the adversaries’ once disclosed the user’s credential means devastating the user consequences. We proposed two scheme for protect the user’s privacy in wireless mesh networks. The first scheme is basic protocol suite and another one is an advanced protocol suite. In the first protocol is used the group signature technique and another one is used for pair wise secret concept. The basic protocol suite to request each network user register the TTP(Trusted third party) after subscribing to the network service assigned the group public key and unique group private key .Then TTP only identify the actual signer communication between the group. Once register user message are delivered under session key protection to the destination. But this technique unable to provide the enough privacy protection to the user’s credential. Because the user identity details are stored in mesh router, the mesh router is backbone of mesh wireless network. So that the details are observed by the adversary. So we proposed the second protocol. The advanced protocol suite is based on the pseudonym registration, after subscribing the pseudonym the user messages are delivering through onion-routing based on the router-router message delivery technique. So that the network adversary could not able to observe the user details. Because the pseudonym concept is against the mesh router. So we have to provide the enough protection for user privacy. 3. References

1. I. F. Akyildiz, X. Wang, and W. Wang, “Wireless mesh networks: A
Survey,” Comput. Netw. vol. 47, no. 4, pp. 445–487, Mar. 2005.

2. D. Boneh, X. Boyen, and H. Shacham, “Short group signatures,” in Proc.
Adv. Cryptology–CRYPTO, vol. 3152, Lecture Notes in Computer Science,
2004, pp. 41–55.

3. A. Boukerche, K. El-Khatib, L. Xu, and L. Korba, “SDAR: A secure
Distributed anonymous routing protocol for wireless and mobile ad hoc
Networks,” in Proc. 29th Annu. IEEE Int. Conf. Local Comput. Netw.
Nov. 2004, pp. 618–624.

4. S. Capkun, J. Hubaux, and M. Jakobsson, “Secure and privacy preserving communication in hybrid ad hoc networks,” Swiss Fed. Inst. Technol.,-
DI-ICA, Lausanne, Switzerland, 2004.

5. D. Chaum and E. van Heyst, “Group signatures,” in Proc. Adv.
Cryptology—EUROCRYPT, vol. 547, LNCS, 1991, pp. 257–265.

2. Overall Description 1. Product Perspective

We proposed two scheme for protect the user’s privacy in wireless mesh networks. The first scheme is basic protocol suite and another one is an advanced protocol suite. In the first protocol is used the group signature technique and another one is used for pair wise secret concept. The basic protocol suite to request each network user register the TTP(Trusted third party) after subscribing to the network service assigned the group public key and unique group private key .Then TTP only identify the actual signer communication between the group. Once register user message are delivered under session key protection to the destination. But this technique unable to provide the enough privacy protection to the user’s credential. Because the user identity details are stored in mesh router, the mesh router is backbone of mesh wireless network. So that the details are observed by the adversary. The advanced protocol suite is based on the pseudonym registration, after subscribing the pseudonym the user messages are delivering through onion-routing based on the router-router message delivery technique. So that the network adversary could not able to observe the user details. Because the pseudonym concept is against the mesh router. So we have to provide the enough protection for user privacy.

2. Product Features In WMNs present a promising way to provide wireless connectivity everywhere, but only modest research efforts have been put into the privacy-protection problem. The main objective of their scheme is to provide anonymity and location privacy for mobile nodes in WMN.Temporary public key pairs are used by each mobile node to anonymously establish pair wise secrets with its neighbors. These pair wise secrets in turn are used to secure routes to the access point. Identifiers of mobile nodes have to be disclosed to access points so that some access points may be able to track a specific mobile user. An adversary is able to link messages by source and destination pseudonym, which keep unchanged within time slot. The attacker is assumed to have only partial knowledge but not global knowledge of the network. We proposed to “onion ring “is achieving the routing privacy in WMNs. This scheme uses “onion encryption “in a ring structure so that it’s impossible for an adversary, even global adversary, to distinguish the source node or the destination node. This scheme is able to identity the misbehaving nodes in order to evict.

In WMNs present a promising way to provide wireless connectivity everywhere, but only modest research efforts have been put into the privacy-protection problem. The main feature is in WMN is communication with one group to another group. The next feature is, if the user request to the web server and get the requested content.

3. User Classes and Characteristics
Ttpform- Node and Router register that information in TTP.

Data send – send information from source to destination via intermediate nodes and Router.

4. Operating Environment

2.4.1 Software Requirements:

▪ Windows Operating System 2000 and Above ▪ JDK 1.6 ▪ JavaFX 1.3 ▪ Tomcat 6.0

2. Hardware Requirements • Hard Disk: 10 GB and above • RAM: 512MB and above • Processor: Pentium III and above

1 Design and Implementation Constraints

3. Constraints in Analysis

• Constraints as Informal Text • Constraints as Operational Restrictions • Constraints Integrated in Existing Model Concepts • Constraints as a Separate Concept • Constraints Implied by the Model Structure

4. Constraints in Design

• Determination of the Involved Classes • Determination of the Involved Objects • Determination of the Involved Actions • Determination of the Require Clauses • Global actions and Constraint Realization

5. Constraints in Implementation

A hierarchical structuring of relations may result in more classes and a more complicated structure to implement. Therefore it is advisable to transform the hierarchical relation structure to a simpler structure such as a classical flat one. It is rather straightforward to transform the developed hierarchical model into a bipartite, flat model, consisting of classes on the one hand and flat relations on the other. Flat relations are preferred at the design level for reasons of simplicity and implementation ease. There is no identity or functionality associated with a flat relation. A flat relation corresponds with the relation concept of entity-relationship modeling and many object oriented methods.

System Features

We proposed to “onion ring “is achieving the routing privacy in WMNs. This scheme uses “onion encryption “in a ring structure so that it’s impossible for an adversary, even global adversary, to distinguish the source node or the destination node. In WMN , provide the feature like communication between the group and if the node request to the web services and the response from the web services.

3. External Interface Requirements

1. User Interfaces

1. All the contents in the project are implemented using Graphical User Interface (GUI) in Java through JavaFX concepts. 2. Every conceptual part of the projects is reflected using the JavaFX. 3. System gets the input and delivers through the GUI based.

Hardware Interfaces:

Ethernet

Ethernet on the AS/400 supports TCP/IP, Advanced Peer-to-Peer Networking (APPN) and advanced program-to-program communications (APPC).

ISDN

You can connect your AS/400 to an Integrated Services Digital Network (ISDN) for faster, more accurate data transmission. An ISDN is a public or private digital communications network that can support data, fax, image, and other services over the same physical interface. Also, you can use other protocols on ISDN, such as IDLC and X.25.

2. Software Interfaces

This software is interacted with the TCP/IP protocol, Socket and listening on unused ports. Server Socket and listening on unused ports and JDK 1.6

3. Communications Interfaces

1. TCP/IP protocol.

2. LAN settings.

5. Other Nonfunctional Requirements

5.1 Performance Requirements

The performance of the WMN process is, the data sent to the source mesh router, which’s the nearest mesh router to the source node. The messages sent along the route constructed from the source node to the source mesh router, which is protected with local session keys. Next, the source router finds out the correct destination router and routes the packet to the destination router. Every mesh router knows how to reach a specific node since each node has registered with the nearest mesh router. The destination mesh router dispatches the message to the destination node.

5.2 Safety Requirement

1. The software may be safety-critical. If so, there are issues associated with its integrity level
2. The software may not be safety-critical although it forms part of a safety-critical system. For example, software may simply log transactions.
3. If a system must be of a high integrity level and if the software is shown to be of that integrity level, then the hardware must be at least of the same integrity level.
4. There is little point in producing 'perfect' code in some language if hardware and system software (in widest sense) are not reliable.
5. If a computer system is to run software of a high integrity level then that system should not at the same time accommodate software of a lower integrity level.
6. Systems with different requirements for safety levels must be separated.
7. Otherwise, the highest level of integrity required must be applied to all systems in the same environment.

5.3 Security Requirements
Do not block the some available ports through the windows firewall.

4. Software Quality Attributes
Functionality: are the required functions available, including interoperability and security.

Reliability: maturity, fault tolerance and recoverability

Usability: how easy it is to understand, learn, and operate the software system

Efficiency: performance and resource behavior.

Maintainability: Maintaining the software.

Portability: can the software easily be transferred to another environment, including install ability

Appendix A: Glossary

IEEE - Institute of Electrical and Electronic Engineers.

LAN - Local Area Network.

TCP - Transmission Control Protocol.

Appendix B:

ACTIVITY DIAGRAM:

[pic]

SEQUENCE DIAGRAM:

[pic]

USECASE DIAGRAM:

[pic]

CLASS DIAGRAM:

[pic]

COLLABORATION DIAGRAM:

[pic]

DATA FLOW DIAGRAM

LEVEL – 1

[pic]

LEVEL – 2 [pic]

LEVEL- 3

[pic]

----------------------- TRUSTED THIRD PARTY

NODE

ROUTER

Sender

Data

Router

Receiver

Receiver

Sender

Data

Node

Router