Arrangement for improving availability of services in a communication system
Abstract
(57) [Summary] The present invention relates to a configuration for improving the architecture of a mobile communication system, particularly a remote communication system. The communication system includes distributed hardware and software that interact with each other to serve one or more users. According to the main features of the present invention, the present configuration is improved by including a mobility layer that incorporates all the mobility mechanisms and functions. In particular, the present invention specifies a functional separation architecture for supporting mobility in communication systems.
Term
Term ended
Projected expiry passed 2 April 2018, 8.5 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
1 claim: 1 independent, 0 dependent
- 1【特許請求の範囲】 1. 移動通信システム、特に1個または複数のユーザにサービスを提供するた めに相互に作用し合う分散型ハードウェアとソフトウェアとを含む遠隔通信シス テム、のアーキテクチャを改良するための構成であって、 該構成は移動度を支持するための独立した層を導入することを含むことを特徴 とする構成。 2. 請求項1記載の構成において、前記構成は任意の移動度機能(1個または 複数)が付随するネットワーク層と付随するアプリケーション層(サービス層) の両方から独立している機能分離アーキテクチャにより支持されている、ことを 特徴とする構成。 3. 請求項2記載の構成において、前記移動度機能は好ましくは特定の層、す なわちいわゆる移動度層、に組み入れられていることを特徴とする構成。 4. 請求項1~3記載のいずれか一つの構成において、前記機能分離アーキテ クチャは複数個のドメイン、特に3個のドメイン、すなわちユーザドメイン、端 末ドメインおよび遠隔通信システムドメインを含むモデルにより表されることを 特徴とする構成。 5. 請求項4記載の構成において、各ドメインにおける前記層はそれらの性質 にしたがって、すなわち機能的に分離されて、複数の機能層に組み入れられるこ とを特徴とする構成。 6. 請求項4または5記載の構成において、任意の層のオブジェクトは提供さ れているインターフェイスを介して、他の層の任意のオブジェクトと直接に相互 作用することができることを特徴とする構成。 7. 請求項4,5または6記載の構成において、前記遠隔通信システムドメイ ンでは、ネットワーク資源層、DPE(分散処理環境)層、保証層、およびアプリ ケーション層に加えて移動度層が定義されていて、該移動度層は移動度の支持を 可能にするオブジェクトを含むことを特徴とする構成。 8. 請求項7記載の構成において、前記移動度層は前記DPE(分散処理技術) 層、前記ネットワーク資源層および前記保証層から提供されるサービスを利用す るようになっていて、前記アプリケーション層はその機能を実現するためにすべ ての層を使用することができることを特徴とする構成。 9. 請求項4または5記載の構成において、前記端末ドメインでは、前記ネッ トワーク資源層、前記DPE層および前記保証層に加えて移動度層が定義されてい て、前記アプリケーション層はユーザが端末を使用することに関連していること を特徴とする構成。 10.請求項4または5記載の構成において、前記ユーザドメインでは、前記保 証層と前記アプリケーション層とを含む2個の機能層が定義されていることを特 徴とする構成。 11.請求項4または5、または9または10記載の構成において、前記ユーザ ドメインと前記端末ドメインとは管理的に分離されているが、技術的には1個の ドメインに統合することができることを特徴とする構成。 12.請求項1から11記載のいずれか一つの構成において、任意のドメインに おける層間の関係はピアツーピア型になっている、すなわち端末ドメインのネッ トワーク資源層は遠隔システムドメインのネットワーク資源層と通信することが できる、などを特徴とする構成。 13.請求項1から12記載のいずれか一つの構成において、すべての層は自律 的で個別に設計具体化されていて、ある層においてどんな内部の変更をしても、 そのインターフェイスが変わらない限り、他の層には影響しないことを特徴とす る構成。 14.請求項1から13記載のいずれか一つの構成において、前記移動度層はた とえばGSM、DECTなどのような種々のネットワーク技術を使う種々の通信におい て再使用することができるように導入されることを特徴とする構成。 15.請求項11記載の構成において、前記ユーザドメインと前記端末ドメイン とを分離して考えることによって、前記機能分離アーキテクチャは1個のユーザ がいくつかの端末を使用している場合と、いくつかのユーザが同じ端末を共有し ている場合をも含むことを特徴とする構成。 16.請求項1から15記載のいずれか一つの構成において、前記分離層は移動 度のトランスペアレンシーを含む構成に含まれることを特徴とする構成。
2 paragraphs, as filed
Description: TECHNICAL FIELD [Detailed description of the invention]
Configuration to improve the architecture of mobile communication systems Field of invention The present invention is a structure for improving the architecture of a communication system that supports mobility. It is about the formation. In particular, the present invention relates to a functional separation architecture that supports mobility. Background of the invention The present invention has been developed with respect to improving the architecture of mobile communication systems. It is. In particular, the present invention provides mobility, that is, a remote communication service to the user at any place and at any time. Introducing the ability to supply screws into communication systems in a well-structured manner It was developed for this purpose. In the present invention, the mobility function can be realized as a functionally separated layer. Show that. In other words, the present invention is a functional separation architect for communication systems that support mobility. It proposes Kucha. Current state of technology TINA (Remote Communication Information Network Architecture) Consortium (TINA95i) ) Proposed a function separation architecture for remote communication systems. -The architecture has no mobility layer at all. Where are the features that support mobility assigned? Is it in the DPE layer or in the network resource layer? Is it not clear? In addition, the TINA architecture is a user domain, terminal Not considering three domains, domain and remote communication system domain .. Problems with conventional technology Existing communication system architectures do not consider mobility as an independent layer The mobility function is either in the network resource layer or in the application / service layer. Assigned to someone. Mobility function GSM (Global Mobile System) In the first case, which is incorporated into the network resource layer like To. It is difficult to modify the mobility function without affecting the network function. is there Difficult to reuse mobility features designed for one network on another network I'm sorry. Because those mobility functions are related to network performance and technology. Because it is dense. UPT (Universal Personal Telecommunication) In the second case where mobility is treated as a service as in), the most severe drawback Has multiple mobilities in different locations, such as fixed and mobile networks The coexistence of the characteristics is that the characteristics are influenced by each other. Purpose of the invention An object of the present invention is a function separation architect for a remote communication system in question. Propose Cha, thereby supporting mobility in a much more efficient and economical way It is to be. Another object of the present invention is to provide a function of mobility and a functional layer dedicated to the mechanism. Yet another object of the present invention is any open distributed processing system (ODP) or similar. It is to introduce such mobility support into the thing. Abstract of the invention The above object is realized by the configuration proposed by the present invention. Its characteristic is It is described in the range of request. In other words, the functional separator supporting mobility for communication systems according to the present invention. Texture is proposed. In particular, this architecture has a network resource layer, a DPE layer and an application. In addition to the mobility layer, a separation function layer for mobility called a mobility layer is included. This architecture has three domains: user domain and terminal domain. And remote communication system domains are appropriate. Further features and advantages of the present invention are described in the claims and with reference to the drawings. It will be clarified by the following explanations. A brief description of the drawing FIG. 1 shows a functional separation architecture that supports mobility according to an embodiment of the present invention. It is a block diagram which shows. Detailed description of the examples Hereinafter, examples that can be realized by the present invention will be described. FIG. 1 is a schematic diagram of a first embodiment of the function separation architecture according to the present invention. This separation architecture supports and promotes the mobility of the remote communication systems involved. Includes the appropriate mobility layer to advance. The entire remote communication system consisting of users, terminals, and remote communication systems is It consists of three domains: The Domain, Terminal Domain, and Remote Communication System Domain. It is represented by the model. In each domain, various functions are incorporated into multiple functional layers due to their nature. Can be done. These layers are not in any hierarchical relationship, but are functionally separated It's just done. Objects of any layer are provided interfaces You can talk directly to any object in any other layer through. In the remote communication system domain, network resource layer, DPE (distributed processing environment) It defines five functional layers: layer, mobility layer, guarantee layer, and application layer. To. -The network resource layer is the transport used to set and open the stream flow. Contains objects that control / manage the network. DPE layer is a distributed computing infrastructure that realizes distributed transparency Includes objects of. The DPE layer provides various DPEs for the application. The mobility layer contains objects that allow mobility support. -The guarantee layer includes objects dealing with guarantee issues. -Application layer is provided by other layers to provide services to users Includes objects that utilize the functions that are used. Objects in different layers are objects in your own layer as well as objects in other layers. Also communicates with. The distinction between the application layer and the network resource layer is IN. Calls and connections introduced by the Terrigent Network) architecture It is done by the principle of separation. Objects in the network resource layer are provided from the DPE layer Use the services provided. Reciprocally, the DPE layer is the kernel transport Selectively use the network resource layer to determine the handle of the network (kTN) Can be Mobility layer is supplied from DPE layer, network resource layer and guarantee layer Use the services that are provided. Guarantee layer is supplied from DPE layer and network resource layer Use the service. Finally, the application layer releases its functionality All other layers are available. TINA-C defines only three layers: network resource layer, DPE layer, and service layer [ TIN95e] is worth noting. The architecture proposed here is TINA You can think of it as an advanced version of the texture. In the terminal domain, the network corresponds to the functional layer of the remote communication system domain. There are four functional layers: resource layer, DPE layer, mobility layer, and guarantee layer. In the terminal domain The reason why there is no application layer is that we select the use of the terminal in relation to the user. Because it does. The user domain has two functional layers, a guarantee layer and an application layer. Protect The certificate layer contains objects that help the user in assurance procedures such as authentication. To communicate with the remote communication system domain, the user domain is always the terminal domain It is worth noting that it requires a computer. In fact, the domains we are segmenting here Is an administrative domain and does not match the technical domain. Technically Two domains may be merged into one domain. But the analysis is these de It is irrelevant whether the main is a separate technical domain. User domain app The application object runs on the terminal domain. Therefore, you The relationship between the domain layer and the terminal domain layer is similar to the relationship between layers of the same domain. .. The application layer objects of the user domain are all of the terminal domain Layers can be used. Relationship between user domain layer and remote communication system domain layer, terminal domain layer And the relationship between the remote communication system domain layers is peer-to-peer. is there. For example, the network resource layer of the terminal domain is a remote communication system domain. It is possible to communicate with the network resource layer of the network, and so on. Advantages of the invention High degree of modularity and flexibility can be obtained by the proposed function separation architecture. Is done. Layers are autonomous and can be individually designed and embodied. In a certain layer No matter what internal changes you make, as long as the interface doesn't change Does not affect the layer of. Another big advantage is various network technologies such as GSM, DECT, etc. The possibility is that the mobility layer can be reused in the various communications used. -Finally, this is also important, but separate the user domain and the terminal domain. By thinking, this architecture allows one user to use several terminals Applicable when using and when several users share the same device To.<img file="JP2001521687A_D0001.tif" />
49 members in 7 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 971605 | Norway | A | |
| 971605 | Norway | A | |
| 971605 | Norway | – | |
| 9800105 | Norway | W | |
| 9800105 | Norway | W | |
| 1997971605 | – | – | – |
| 199800105 | – | – | – |
| NO19970001605 | – | – | – |
| WO1998NO00105 | – | – | – |
Members49
| Document | Office | Kind | |
|---|---|---|---|
| NO971605D0 | Norway | D0 | |
| NO971605L | Norway | L | |
| WO9845982A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO9845985A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO9845986A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO9845987A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO9845988A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO9845989A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO9846036A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU6857098A | Australia | A | |
| AU6857198A | Australia | A | |
| AU6857298A | Australia | A | |
| AU6857398A | Australia | A | |
| AU6857498A | Australia | A | |
| AU6857598A | Australia | A | |
| AU6857698A | Australia | A | |
| WO9845982A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO9845988A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO9845989A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO9845986A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO9845987A3 | World Intellectual Property Organization (WIPO) | A3 | |
| EP0974214A1 | European Patent Office (EPO) | A1 | |
| EP0974233A2 | European Patent Office (EPO) | A2 | |
| EP0974235A2 | European Patent Office (EPO) | A2 | |
| EP0976222A2 | European Patent Office (EPO) | A2 | |
| EP0980629A2 | European Patent Office (EPO) | A2 | |
| EP0981876A2 | European Patent Office (EPO) | A2 | |
| EP0981921A1 | European Patent Office (EPO) | A1 | |
| US6233446B1 | United States of America | B1 | |
| US6275709B1 | United States of America | B1 | |
| JP2001519062A | Japan | A | |
| JP2001521686A | Japan | A | |
| JP2001521687AThis record | Japan | A | |
| JP2001521688A | Japan | A | |
| JP2001521689A | Japan | A | |
| JP2001521690A | Japan | A | |
| US6332081B1 | United States of America | B1 | |
| US6336130B1 | United States of America | B1 | |
| JP2002510440A | Japan | A | |
| US6389037B1 | United States of America | B1 | |
| US6490613B1 | United States of America | B1 | |
| US6964050B1 | United States of America | B1 | |
| EP0974233B1 | European Patent Office (EPO) | B1 | |
| DE69837040D1 | Germany | D1 | |
| DE69837040T2 | Germany | T2 | |
| JP4234210B2 | Japan | B2 | |
| JP4267708B2 | Japan | B2 | |
| EP0981921B1 | European Patent Office (EPO) | B1 | |
| DE69841308D1 | Germany | D1 |
9 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Decision of refusalJAPANESE INTERMEDIATE CODE: A02A02 | A02 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written amendmentJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Written request for application examinationJAPANESE INTERMEDIATE CODE: A621A621 | A621 |
Numbers
- Publication
- 2001-521687
- Publication, DOCDB
- 2001521687
- Publication, EPODOC
- JP2001521687
- Application
- 54263398
- Application, DOCDB
- 54263398
- Application, EPODOC
- JP19980542633
Titles2
- Japanese
- 【発明の名称】移動通信システムのアーキテクチャを改良するための構成
- English
- Description: A configuration for improving the architecture of a mobile communication system.
Classification
- CPC, 17
- H04W8/18
- H04L63/10
- H04Q3/005
- H04Q3/0095
- H04W80/04
- H04L67/303
- H04L67/306
- H04L67/04
- H04L67/10
- H04L69/03
- H04L69/329
- H04W12/084
- H04L67/51
- H04L67/52
- H04L69/32
- H04L9/40
- H04L67/01
- IPC, 16
- G01C21 00
- G06F9 46
- G06F12 14
- G06F15 00
- G06F15 16
- G08G1 123
- H04B7 26
- H04L9 32
- H04L12 56
- H04L29 06
- H04L29 08
- H04M3 46
- H04Q3 00
- H04W8 18
- H04W12 00
- H04W80 04