Open communication systems and their flexible configurability will, eventually, facilitate data transport with a minimum of overhead across networks and, in particular, via the wireless link. However, on the way, if not properly implemented, network reconfigurability has the potential to introduce instability into communication networks.In a highly reconfigurable network the potential exists for confusion over the current configuration status of nodes to impinge upon the complete reconfigurable communication system. This could result in message and/or data collisions and could lead to system failure due to nonconformant states within a network node or between different network nodes, e.g. if the configured standard differs between terminal and base station. Reconfiguration management has to accommodate the internal configuration of network nodes/terminals and the external relations of such nodes; external reconfiguration management is required to coordinate the states of the reconfigurable nodes along a particular communications path, while its internal counterpart is needed to control and manage the reconfiguration within the reconfigurable device (or network node) itself. The major tasks of external reconfiguration management are to monitor current traffic requirements and settings between the communication end points and to ensure that the transport means between the terminal and the network gateway (or, if applicable, all the way through the network to the other communication end point) are synchronized (i.e. using the appropriate transmission standards). External reconfiguration management must also include the provision of additional, reconfiguration related, services. Within the approach developed by Mobile VCE, this latter role is undertaken by an AcA server (authentication/ authorization/ encryption – virtual configuration – accounting/billing), with associated databases used to store downloadable reconfiguration software. The architectural framework is shown in the figure.

The scope of internal and external reconfiguration management is depicted in figure below. Despite the formal separation, internal and external reconfiguration cannot in practice be completely separated; their decision making processes and reconfiguration software acquisition and installation procedures are interrelated. For example, software download and (internal) reconfiguration validation within a handset are tasks that require support from the network (i.e. from the AcA server and its associated software database). External reconfiguration management enables and supports the interactions between network nodes, including external (network originated) triggering of terminal (or network node) reconfiguration

see also :

"System Reconfigurability"

"THE ROLE OF THE CONFIGURATION CONTROL MODULE IN AN END TO END RECONFIGURABLE SYSTEM"

"Design of Generic and Adaptive Protocol Software (DGAPS)"

"Design, Implementation and Validation of a generic and reconfigurable Protocol Stack Framework for mobile Terminals"