Protocol stacks

• US 20030174731A1
• Filed: 05/07/2003
• Published: 09/18/2003
• Est. Priority Date: 05/17/2000
• Status: Abandoned Application

• Current Assignee: University of Surrey
• Original Assignee: University of Surrey
• Inventors: Vahid, Seiamak, Moessner, Klaus, Tafazolli, Rahim
• Application Number:
  US10/275,776
• Publication Number:
  US 20030174731A1
• Time in Patent Office: Days
• US Class Current: 370/469
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/321 Interlayer communication protocols or service data unit [SDU] definitions; Interfaces between layers
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 80/00 Wireless network protocols or protocol adaptations to wireless operation

Abstract

A protocol stack for a communications system has an architecture incorporating active programming interfaces capable of supporting reconfiguration of the stack. The stack has a plurality of layers (pro-layers) and a plurality of object-oriented interfaces (pro-interfaces) whose respective functionalities are defined by layer classes and programming interface classes. Execution of these functionalities is controlled by thread objects.

Claims

1. A protocol stack for a communications system wherein the stack has an architecture incorporating active programming interfaces capable of supporting reconfiguration of the stack.

2. A protocol stack as claimed in claim 1 comprising

a plurality of protocol layers and a plurality of said active programming interfaces interleaved with said protocol layers, wherein functionality of said protocol layers is defined by protocol layer classes and functionality of said active programming interfaces is defined by programming interface classes.

3. A protocol stack as claimed in claim 2 wherein execution of the respective functions of said protocol layer classes and said programming interface classes is controlled by thread objects defined by thread classes.

4. A protocol stack as claimed in claim 3 wherein said classes are stored in one or more class library.

5. A protocol stack as claimed in claim 2 wherein said protocol layer classes have functionalities derived from a generic layer class and said programming interface classes have functionalities derived from a generic interface class.

6. A protocol stack as claimed in claim 3 wherein said protocol layer classes, said programming interface classes and said thread classes are implemented and controlled by a protocol stack class.

7. A protocol stack as claimed in claim 6 wherein said protocol stack class facilitates exchange of said protocol layer, programming interface and thread classes during protocol reconfiguration.

8. A protocol stack as claimed in claim 7 wherein said protocol stack class defines the structure of the stack.

9. A protocol stack as claimed in any one of claims 1 to 8 wherein said protocol layers consist of a physical layer, a link control layer, a network control layer, a signalling application layer and an application layer.

10. A protocol stack as claimed in any one of claims 2 to 9 wherein said active programming interfaces are configured to enable direct signalling communication between different active programming interfaces without accessing implementation of said protocol layers.

11. A protocol stack as claimed in claim 5 wherein said generic interface class defines a plurality of basic control messages (primitives).

12. A protocol stack as claimed in claim 11 wherein there are four said primitives consisting of Service Request Messages, Request Responses, Layer State Information and Asynchronous Event Notification.

13. A protocol stack as claimed in any one of claims 2 to 4 wherein at least one of said classes depends on at least one other class.

14. A protocol stack as claimed in claim 4 wherein said one or more class library is a secure library.

15. A protocol stack as claimed in any one of claims 6 to 8 wherein said protocol stack class is publicly available.

16. A protocol stack as claimed in claim 1 wherein said active programming interfaces enable access to attributes within protocol layers of the stack either sequentially or non-sequentially.

27. A protocol stack as claimed in any one of claims 1 to 26 wherein each said layer class inherits functionality from a generic layer class common to all said layer classes and has additional functionality specific to the respective layer class.

30. A communications system comprising a network and at least one terminal respectively incorporating a protocol stack as claimed in any one of claims 1 to 29, each said protocol stack being independently reconfigurable.

31. A communications system as claimed in claim 30 wherein said at least one terminal is a software-reconfigurable radio.

17. A reconfigurable protocol stack for a communications system comprising,

a plurality of protocol layers and a plurality of active programming interfaces interleaved with said protocol layers, wherein each said protocol layer has functionality defined by a layer object selectable from a respective one of a plurality of different layer classes, each said active programming interface has functionality defined by an interface object selectable from a respective one of a plurality of different interface classes, and thread objects are selectable from a plurality of thread classes for controlling message sequences within the protocol stack.

18. A protocol stack as claimed in claim 17 wherein each said interface class inherits functionality from a generic interface class that is common to all said interface classes.

19. A protocol stack as claimed in claim 18 wherein each said interface class defines additional functionality specific to the respective interface class.

20. A protocol stack as claimed in claim 18 or claim 19 wherein said generic interface class defines a plurality of basic control message types.

21. A protocol stack as claimed in claim 20 wherein said basic control message types include Service Request Messages, Request Responses, Layer State Information and Asynchronous Event Notification.

22. A protocol stack as claimed in any one of claims 17 to 21 including a protocol stack class arranged to implement said layer classes, said interface classes and said thread classes.

23. A protocol stack as claimed in claim 22 wherein said protocol stack class is further arranged to exchange, during run-time, one said layer object for another said layer object from the same layer class and/or exchange one said interface object for another said interface object from the same interface class whereby to change functionality of a corresponding said protocol layer and/or a corresponding said active programming interface during protocol stack reconfiguration.

24. A protocol stack as claimed in any one of claims 17 to 23 wherein said layer classes, said interface classes and said thread classes are stored in, and selectable from a class library.

25. A protocol stack as claimed in claim 22 or claim 23 wherein said layer classes, said interface classes and said thread classes are stored in, and selectable from a class library, and implementation of said protocol stack class provides a public interface.

26. A protocol stack as claimed in any one of claims 17 to 25 wherein said active programming interfaces are so configured as to permit messages to pass directly between any two said active programming interfaces by-passing any intervening protocol layer.

28. A protocol stack as claimed in any one of claims 18 to 21 wherein a said layer class inherits functionality from said generic interface class.

29. A protocol stack as claimed in any one of claims 17 to 28 wherein said thread classes derive functionality from said layer and interface classes.

32. A method for reconfiguring a protocol stack for a communications system, the protocol stack comprising a plurality of protocol layers and a plurality of active programming interfaces interleaved with the protocol layers, each said protocol layer having functionality defined by a layer object selectable from a respective one of a plurality of different layer classes and each said active programming interface having functionality defined by an interface object selectable from a respective one of a plurality of different interface classes, the method including the step of exchanging one said layer object for another said layer object from the same layer class and/or exchanging one said interface object for another said interface object from the same interface class whereby to change functionality of the corresponding protocol layer and/or the corresponding active programming interface.

33. A protocol stack substantially as hereindescribed with reference to the accompanying drawings.

34. A communications system substantially as hereindescribed with reference to the accompanying drawings.