ARRANGEMENT FOR IMPROVING THE ARCHITECTURE OF MOBILE COMMUNICATION SYSTEMS

Abstract: The present invention relates to an arrangement for improving the architecture of mobile communication systems, especially a telecommunications system, said system comprising distributed hardware and software components which interact in order to provide services to one or more users, and according to a main aspect of the present invention, this improvement is realised by letting said arrangement comprise a mobility layer grouping all the mobility mechanisms and functions. More specifically the present invention defines a functional separation architecture for supporting mobility in communication systems.

Description: ARRANGEMENT FOR IMPROVING THE ARCHITECTURE OF MOBILE COMMUNICATION SYSTEMS FIELD OF THE INVENTION The present invention relates to an arrangement for improving the architecture of communication systems supporting mobility. More specifically the present invention relates to a functional separation architecture supporting mobility. BACKGROUND OF THE INVENTION The present invention has been developed in connection with improving the architecture of a mobile communication system. More specifically the present invention has been devel- oped in order to introduce mobility, i.e. the capability to deliver telecommunication services to the user anywhere and at any time, to a communication system in a well -structured way. The present invention demonstrates that the mobility functions can be realised as a functional separated layer . In other words, this invention proposes a function sepa- ration architecture for communication systems that supports mobility. STATE OF THE ART TINA (Telecommunication Information Networking Architecture) Consortium [TIN95i] has proposed a functional sepa- ration architecture for telecommunication systems but the proposed architecture does not have any mobility layer. It is unclear where the functions to support mobility are allocated (i.e. in the DPE layer or the network resource layer) . Furthermore, TINA architecture does not consider three domains namely the user domain, the terminal domain and the telecom system domain. PROBLEMS RELATED TO PRIOR ART The existing communication system architectures do not consider mobility as separate layer but either allocate the mobility functions in the Network resource layer or the application/service layer. There are several consequences for the first case where the mobility functions are integrated on the network resource layer such as in GSM (Global Mobile System) . It is difficult to make any modification of the mobility functions without affecting the network functions. It is difficult to reuse the mobility functions designed for a network on another one since they are tight to the network characteristics and technology. In the second case where mobility is treated as a service such in UPT (Universal Personal Telecommunication) , the most severe disadvantage is the feature interaction which occurs due to multiple mobility implemen- tations at different places, e.g. in fixed network and also in the mobile network. OBJECTS OF THE INVENTION The object of the present invention is to propose a functional separation architecture for the telecommunication system in question, whereby mobility is supported in a far more efficient and economic manner. Another object of the present invention is to dedicate a functional layer to mobility functions and mechanisms. Still another object of the present invention is to introduce such mobility support in any open distributed processing (ODP) system or similar. SUMMARY OF THE INVENTION The above objects are achieved in an arrangement as suggested by the present invention, the characterizing features thereof being defined in the appending patent claims. In other words, according to the present invention there is suggested a functional separation architecture supporting mobility for communication systems. More specifically such an architecture may comprise a separate functional layer for mobility, called mobility layer, in addition to the network resource layer, the DPE layer and the application layer. Appropriately, such an architecture may comprise three domains, i.e. the user domain, the terminal domain and the telecom system domain. Further features and advantages of the present invention will appear from the following description taken in conjunction with the enclosed drawing, as well as from the appending patent claims . BRIEF DISCLOSURE OF THE DRAWING Fig. 1 is a block diagram illustrating the functional separation architecture supporting mobility, as defined in accordance with an embodiment of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS In the following there will be given a description of embodiments which can be implemented in accordance with the present invention. Fig. 1 illustrates in a schematical manner a first e - bodiment of a functional separation architecture according to the present invention, which functional separation architecture comprises appropriate mobility layers supporting and facilitating the mobility of the associated communications system. The whole communication system consisting of users, terminals and telecommunications system is represented by a model consisting of three domains: user domain, terminal domain and telecom system domain. In each domain, functions are grouped according to their nature into functional layers. These layers do not imply any hierarchical relationship but only a functional sepa- ration. An object in any layer can interact directly with any object in any other layer via offered interfaces. In the telecom system domain, we have defined five func- tional layers: Network resource layer, DPE (Distributed Processing Environment) layer, Mobility layer, Security layer and Application layer. • The network resource layer comprises the objects con- trolling/managing the transport network which is used in the establishment and release of stream flows. • The DPE layer comprises objects of the distributed computing infrastructure which implement the distribution transparencies. The DPE layer provides various DPE services to the applications. • The mobility layer comprises the objects which enable the support of mobility. • The security layer comprises objects which are dealing with security issues. • The application layer comprises the objects which make use of the functions offered by other layers to provide services to users . The objects in the different layers communicate internally in the layer as well as with objects in the other layers. The distinction between the application layer and the network resource layer reflects the call and connection separation principle introduced by the IN (Intelligent Network) architecture. Objects in the network resource layer use services from the DPE layer. Recipro- cally, the DPE layer can optionally use the network resource layer to establish a bearer for the kernel transport network (kTN) . The mobility layer uses services from the DPE layer, the network resource layer and the secu- rity layer. The security layer uses services from the DPE layer and the network resource layer. Finally, the application layer may use all other layers to realise its functions . It is worth noting that TINA-C defines only three layers: network resource layer, DPE layer and service layer [TIN95e] . The architecture presented here can be considered as an enhancement of the TINA architecture . In the terminal domain, there are four functional layers corresponding to the ones in the telecom system domain: network resource layer, DPE layer, mobility layer and security layer. The reason that there is no application layer in the terminal domain is because we choose to as- sociate the usage of a terminal with a user. In the user domain, there are two functional layers: security layer and application layer. The security layer comprises objects which assist the user in the security procedures such as authentication. It is worth noting that in order to communicate with the telecom system domain, the user domain always requires a terminal domain. In fact, the domain partitioning here is an administrative one which does not correspond to a technological one. Technologically, the two domains may be unified onto one domain. However, the analysis is independent of whether or not these domains are separate technology domains. Application objects of the user do- main are running on the terminal domain. The relationship between the user domain layers and the terminal domain layers is therefore similar to the relationship between layers of the same domain. Objects in the application layer of the user domain may use all the layers of the terminal domain. The relationship between the user domain layers and the telecom system domain layers and the relationship between the terminal domain layers and the telecom system domain layers are of peer-to-peer type, e.g. terminal domain network resource layer may communicate telecom system domain network resource layer, etc. MERITS OF THE INVENTION • The proposed Functional Separation Architecture yields a high level of modular: ty and flexibility. The layers are autonomous and can be designed and implemented separately. Any internal changes in one layer does not affect the other layers as long as its interfaces remain unchanged. • Another major advantage is the reuse possibility of the mobility layer in different communications using different network technologies such as GSM, DECT, etc. • Last but not least, by considering the user domain separately of the terminal domain, the architecture also covers the case where one user is using several terminals and the case where several users are sharing the same terminal . REFERENCES [TIN95e] TINA-C. Domain types and basic Reference Points in TINA, May 1995. [TIN95i] TINA-C. Overall Concepts and Principles of TINA, February 1995.

Claims: P a t e n t c l a i m s 1. Arrangement for improving the architecture of mobile communication systems, especially a telecommunications system, said system comprising distributed hardware and software components which interact in order to provide services to one or more users, c h a r a c t e r i z e d i n that said arrangement comprises the introduction of a separate layer for sup- porting mobility. 2. Arrangement as claimed in claim 1, c h a r a c t e r i z e d i n that said arrangement is supported by a functional separation architecture wherein any mobility function (s) is (are) separated both from the associated network layer and the associated application (service) layer. 3. Arrangement as claimed in claim 2, c h a r a c t e r i z e d i n that said mobility functions are preferably grouped into a specific layer, i.e. a so-called mobility layer. 4. Arrangement as claimed in any of the preceding claims, c h a r a c t e r i z e d i n that said functional separation architecture is represented by a model comprising a plurality of domains, specifically three domains, i.e. user domain, terminal domain and telecom sys- tern domain. 5. Arrangement as claimed in claim 4, c h a r a c t e r i z e d i n that said layers in each domain are grouped according to their nature into functional layers, i.e. with a functional separation. 6. Arrangement as claimed in claim 4 or 5 , c h a r a c t e r i z e d i n that an object in any layer can interact directly with any object in another layer via offered interfaces. 7. Arrangement as claimed in claim 4, 5 or 6 , c h a r a c t e r i z e d i n that in the telecom system domain there are defined a mobility layer in addition to a network resource layer, a DPE (Distributed Processing Environment) layer, a security layer and an application layer, whereby the mobility layer comprises the objects enabling support of mobility. 8. Arrangement as claimed in claim 7, c h a r a c t e r i z e d i n that the mobility layer is adapted to use services from the DPE Distributed Processing Engineering) layer, the network resource layer and the security layer, the application layer being able to use all layers to realise its functions. 9. Arrangement as claimed in claim 4 or 5 , c h a r a c t e r i z e d i n that in the terminal domain there are defined a mobility layer in addition to the network resource layer, DPE layer and security layer, the application layer being associated with the usage of a terminal with a user. 10. Arrangement as claimed in claim 4 or 5 , c h a r a c t e r i z e d i n that in the user domain there are defined two functional layers comprising the security layer and the application layer. 11. Arrangement as claimed in claim 4 or 5 , or 9 or 10, c h a r a c t e r i z e d i n that the user domain and the terminal domain are separated administratively, but may technologically be unified into one domain. 12. Arrangement as claimed in any of the preceding claims, c h a r a c t e r i z e d i n that the relationship between layers in any domain is of the peer-to-peer type, i.e. a terminal domain network resource layer being able to communicate with a telecom system domain network resource layer, etc. 13. Arrangement as claimed in any of the preceding claims, c h a r a c t e r i z e d i n that all layers are autonomous and can be designed and implemented separately, any internal changes thereof not effecting the others layers provided the interface in question remains unchanged. 1 . Arrangement as claimed in any of the preceding claims, c h a r a c t e r i z e d i n that said mobility layer is introduced with a reuse possibility in different communications using different network technologies, for example GSM, DECT, etc. 15. Arrangement as claimed in claim 11, c h a r a c t e r i z e d i n that by considering the user domain separately of the terminal domain, the functional separation architecture will also cover the case where one user is using several terminals, as well as the case where several users are sharing the same terminal . 16. Arrangement as claimed in any of the preceding claims, c h a r a c t e r i z e d i n that said separate layer is included in an arrangement comprising mobility transparency .

Inventors: THANH DO VAN, THANH, DO, VAN
Applicants: ERICSSON TELEFON AB L M, THANH DO VAN, TELEFONAKTIEBOLAGET LM ERICSSON, THANH, DO, VAN
Application year: 1998
Main classification: H04L12
IPC codes: G01C21, G06F9, G06F12, G06F15, G06F21, G08G1, H04B7, H04L9, H04L12, H04L29, H04M3, H04Q3, H04W8, H04W12, H04W80