Arrangement for improving security in a communication system supporting user mobility

0001ARRANGEMENT FOR IMPROVING SECURITY IN A COMMUNICATION SYSTEM SUPPORTING USER MOBILITY

FIELD OF THE INVENTION

0003The present invention relates to an arrangement for improving security in a communications system, especially a telecommunications system, said system comprising distributed hardware and software components which interact in order to provide services to one or more users.

0004More specifically the present invention concerns a user access control for distributed systems that support user mobility, i.e. users are allowed to move and use different terminals to access services.

BACKGROUND OF THE INVENTION

0006The Access control is the procedure used by the telecom system domain to ensure that the user accesses the telecom system domain in accordance with the restrictions specified at subscription [1]. When mobility is sup- ported, every user will have the possibility to use any terminals at any access points. The access control procedure is also intended to limit the access capability of a user for the protection and privacy of third party. The third party can be the owner of the terminal or the access point, and must have the right to block or deblock, suspend or reset the service de- livery at his terminal or access point to a user.

0007When the user is allowed to move and access to the telecommunication services anywhere and at any time, the risk of threats increases dramatically at the same time as the mechanisms necessary to enforce security become more difficult to realise. In systems supporting general mobility, fraudulent use of anyone's subscription can be attempted from any terminal and at any network access point. In this way the user may be exposed to various forms of fraud as, for example, fraudulent use of the user "s resources by unauthorised parties who manage to take up the identity of the user, eavesdropping, unauthorised tapping or modification of information exchanged during communication, and disclosure of the user's physical location [4]. Another security problem arises because the user is allowed to use any terminal and at any network access point. Such a tem- porary usage may conflict with the use of the terminal by the terminal owners, also referred to as third parties [6]. In principle, third parties should not suffer in terms of loss of privacy or freedom of actions as a result of activities by the mobile user.

STATE OF THE ART

0009With mobility, users may make use of any existing and available terminals and network access points. However, this does not mean that the terminal owner (the third party) has to accept such actions on his termi- nal. He must have the rights to restrict the usage of the terminal, e.g. only allowing certain users while others are prohibited from using the terminal.

0010This may be done in many ways, e.g. by keeping the terminal in a se- cured place, use local password, etc., but such measures are cumbersome for the owner and often not secure enough. This is commonly referred as the protection of third parties. The UPT (Universal Personal Telecommunication) [4] system comprises some sort of access control mechanisms but they are limited to telephony services and to voice terminals or telephone.

0011Consequently, there is a need for an improved user access control for distributed systems supporting user mobility.

OBJECTS OF THE INVENTION

0013The present invention has for an objective to address any mobile distributed system, any types of applications, i.e. voice, data, image, video, interactive, multimedia, etc., for in such mobile distributed systems to introduce an improved access control.

0014A further object of the present invention is to introduce a generic access control in such distributed systems.

0015Still another object of the present invention is to introduce such a generic access control for distributed systems supporting user mobility which can be used in mobile distributed systems comprising public or private, local- area or wide-area, wireline or wireless networks.

BRIEF DISCLOSURE OF THE INVENTION

0017The above objects are achieved in an arrangement as stated in the preamble, which primarily is characterised by introducing in said system a user access control, for thereby enforcing security in communications systems. In other words, the invention also suggests that this type of generic access control is related to personal mobility.

0018Further features and advantages of the present invention will appear from the following description taken in conjunction with the enclosed drawings, as well as from the appending patent claims.

BRIEF DISCLOSURE OF THE DRAWINGS

0020Fig. 1 is a schematic diagram illustrating the main subject matter to which the present invention is related, namely by illustrating a user's access to the services in question.

0021Fig. 2 is a schematic diagram illustrating an embodiment of the present invention for carrying out access control, especially in relation to a information object Term_Profιle.

0022Fig. 3 is a schematic diagram illustrating an embodiment of a Termi- nal_Data object.

0023Fig. 4 illustrates a computational model of the access control of a user for use of a terminal.

0024Fig. 5 is a schematic diagram illustrating a user_registration object con- taining a list of allowed services.

0025Fig. 6 is a schematic diagram illustrating the relation between user domain, terminal domain and telecom system domain as well as an embodiment of access control on the access to the telecom system. Fig. 7 is a block diagram illustrating the relation between user domain, terminal domain and telecom system domain, as well as an embodiment of access control on the axis to the telecom system.

DETAILED DESCRIPTION OF EMBODIMENT

0027As stated previously, the present invention relates to user access control for distributed systems that support user mobility which means that the users are allowed to move and use different terminals to access services available to them.

0028In Fig. 1 there is illustrated a user which has access to a terminal which in turn is communicating with a telecom system which in turn is offering a plurality of services.

0029Before allowing the user to access the services offered by the telecom system domain, he is subject to three types of access control

0030• access control concerning the use of the current terminal (protection of third party)

0031• access control concerning the access to the telecom system

0032• access control concerning the use of the service requested

0033SOLUTION We shall successively describe the three mentioned access controls.

0034Access control for use of the current terminal

0035With mobility, users may make use of any existing and available termi- nals and network access points. However, this does not mean that the terminal owner (the third party) has to accept such actions on his terminal. He must have the rights to restrict the usage of the terminal, e.g. only allowing certain users while other are prohibited from using the terminal. Of course, there are many ways to do this locally, e.g. keep the terminal in a secure place, use local password, etc. but they are cumbersome for the owner and often not secure enough. This is commonly referred as the protection of third parties [2].

0036Let us suppose that the mobile distributed system uses agent techniques to support mobility and has the following objects:

0037PD_UA (ProviderDomain_UserAgent) representing a user in the telecom system domain.

0038TA (TerminalAgenf) representing a terminal in the telecom system do main SPA (ServiceProvider Agent) representing the telecom system in the terminal domain

0039NAP representing a Network Access Point

0040TAP representing a Terminal Access Point

0041The information required for to carrying out the access control is contained in the Usage_Restriction component of the object Term_Profιle (see Figure 2) which contains information about the terminal. The attribute All_Barring is used to specify that only the terminal owner can use the terminal. The terminal owner may also prevent a particular user or group of users from using his terminal by specifying the attribute Bar- ring_List or to allow only certain user by specifying an Allowance_List. Modification of the Usage_restriction may be provided as an application where only the owner has the right to make access. The details of such an application and the specific layout of the Usage_Resfriction is a matter of implementation and will not be carried further here.

0042In order to support selective access control of the terminal, the object Terminal_Data which contains information required for the support ter- minal mobility such as state, NAPid, etc. may be equipped with a table of controlled and cleared users, called ClearedUserTable, as shown in Figure 3. The ClearedUserTable contains the references or CIIs (Computational Interface Identifier) of the PD_UAs whose access have been controlled.

0043The TA assumes the Access control Enforcement Function (AEF). The Access control Decision Function is allocated to an object called ADF. The access control Procedure for use of the terminal is shown in Figure 4.

00441. Every time an operation OpX arrives at the TA, the TA will check whether the identifier of the originating or addressed PD_UA is on the ClearedUserTable or not. If it is, TA will do the transfer of OpX If it is not, TA will initiate the access control Procedure.

00452. TA invokes Get(Usage_Resfriction) on Term_Profile to acquire the access control Decision Information (ADI).

00463. The TA invokes the operation Decision_Request on the ADF object. The arguments of this operation are the ADI obtained from the TermJProftle. The ADF makes the decision and returns the Ac- cess_Result to TA. The Access_result may be granted or not_granted.If the Access_Result is not_granted, TA returns an error message to the originator of the operation.

00474. If the Access_Result is granted, TA invokes the operation Up- date(CleareduserTable,PD_UARef) on Terminal_Data to register the PD_UA of the newly cleared user.

0048One way of removing entries from ClearedUserTable, i.e the identifier (reference) of a PD UA, is to restart a timer each time that entry is accessed. If the timer times out, the entry is removed. Some entries may be permanent, i.e. they are not associated with a timer.

0049This type of access confrol is only intended to other users than the terminal owner himself. In fact, the terminal owner should never be prevented to use his terminal. The access to the telecom system domain and the access to the services are different types of access controls which are applicable to all the users including the terminal owner.

0050In the object Usage_Resfriction it is therefore necessary to define an additional attribute called NoRestr_List containing the PD_UA identifiers of the users who are by default allowed to use the terminal. The identifier of the terminal owner's PD_UA is one of them. This list must not be ac- cessible to anyone but the telecom system domain operator itself, i.e. even not to the terminal owner. However, it may be possible to define an "emergency user", i.e. every call to an emergency number will be effectual without being checked by the access control service. Access control for access to the telecom system domain If the user is allowed to use the terminal, it does not necessarily mean that he is allowed to access the telecom system domain. He may be located outside the roaming area; his credit with the operator may have run out; the authentication mechanism used to authenticate him may also be too weak and he is allowed to access a limited set of services. The list of allowed services for a user at a terminal is hence equal to or smaller than the list of subscribed services. This list is a column in the User Registration object in Figure 5.

0051The initiator of the access confrol service is User_a. The target is the telecom system domain. The AEF is assumed by the PD_UA_a. The ADF is assumed by the object ADF. The access of the user to the telecom system domain may be limited by some parameters such as Roam- ing_Resfriction, Credit_Limit, Time_Restriction, etc. which are contained in the Service_Resfriction attribute of the User_Profιle object. The Service_Restriction attribute contains also a list of subscribed services. The use of the services in this list may be conditioned by the strength of the method used to authenticate the user, the location of the terminal, the call destination, etc. The Service_Restriction attribute may thus be quite complex.

0052A computational model of the access control service for access to the telecom system domain is shown in Figure 6. The access control procedure is as follows:

00531. The PD_UAa object invokes a Get(Service_Restriction) on the User_Profιle to acquire the access control Decision Information (ADI). 2. The PD_UAa object invokes a Get(SecurityData) on the User_Regisfration object to acquire the contextual information (result from the authentication service).

00543. The PD_UA_a object invokes the operation Decision_Request on the ADF object. The arguments of this operation are the ADI obtained from User_Profιle and the contextual information obtained from User_Registration.

0055The ADF may use the access control services offered by the platform or a security system to obtain further contextual information such as time, system status, etc. and the access control policy rules. The ADF makes the decision and returns the Access_Result to PD_UAa together with Se- curityData and AllowedServices.

0056The Access_result may be granted, not_granted or suspended. If the Ac- cess_Result is Suspended, depending on the access confrol Policy the terminal will be, temporarily or permanently no longer allowed to access the telecom system domain.

0057If the Access_Result is not_granted, the SecurityData returned to the PD_UA_a from the ADF will contain a NoOfRefries field increased by one. The NoOfRefries field indicates the number of unsuccessful access attempts and is used as contextual information for the next access confrol service. The PD_UA_a will invoke the operation Set(SecurityData) on the User Registration object to save the updated SecurityData. Depending on the operation which initiated the access confrol procedure, the PD_UA_a will return the appropriate response containing a not_granted status. When the Access_Result is granted, the AllowedServices containing an updated list of allowed services is returned to the PD_UA_a. The PD_UAa will invoke the operation Set(AllowedServices) on the User_Regisfration object to save the updated AllowedServices. Depending on the operation which initiated the access control procedure, the PD_UA_a will return the appropriate response containing a granted status.

0058The user can now request the wanted service and is hence subject to the access confrol for the requested service.

0059Access control for the requested service

0060There are two types of services, outgoing and incoming. Outgoing services are initiated by the user himself while incoming services are delivered to him by other users or applications.

0061For outgoing services, the initiator of the access confrol service is Usera. For incoming services the initiator is some other user or application. The target is the requested service. The AEF is assumed by the PD_UA_a. The ADF is assumed by the object ADF. The access of the user to the re- quested service is limited by the information contained in the Allowed- Service list of the User_Registration object. Another resfriction originates from the Usage_Restriction contained in the object Terminal_Data and set by the terminal owner. The terminal owner may allow only one or both of the two service types to be performed on his terminal The attrib- utes OutBarring and InBarring of the Usage_Restriction is used to specify, respectively, the users who are not allowed to use outgoing services and incoming services on the terminal (or who are allowed).

0062The access confrol procedure is as follows: 1. The PD_UA_a object receives a ServiceReq(ServId) from either the user or an application.

00633. The PD_UAaobject invokes a Get(Usage_Resfriction) on the TA.

00643. The PD_UA_a object invokes a Get(AllowedService) on the User_Regisfration.

00652. The PD_UA_a object invokes the operation Decision_Request on the ADF object. The arguments of this operation are the ADI obtained from the User_Registration object and the TA.

0066The ADF makes the decision and returns the Access_Result to PD_UA_a. The Access result may be granted or not_granted. Depending on the operation which initiated the access control procedure, the PD_UA_a will return the appropriate response to the requester. The access control on the requested service is shown in Figure 7.

MERITS OF THE INVENTION

0068This invention has high level of flexibility in the sense that it can be used in different mobile distributed systems, public or private, local-area or wide-area, wireline or wireless.

0069It is a complete access control in the sense that it contains all the three types of access control.

0070Important features of the invention may be listed as follows: 1 : A user access control is introduced for distributed systems that supports personal mobility.

00712: Such a user access confrol consists of access confrol for the use of the terminal, access confrol to the telecom system and access confrol to the requested services.

REFERENCES

00731. ISO/IEC. Information technology - Open System INterconnection security frameworks in Open Systems: Part 1 : Access Confrol, Jun 93

00742. ETSI. NA:UPT: Service Requirements on protection of third parties. Version 1.0.0

00753. ITU-TS Draft recommendation F.851. Universal Personal Telecommunication (UPT) - Service Description. International Telecommunication Union-Telecommunication Stan- dardization Sector, (Version 10) Jan 94.

00764. ETSI. NA:UPT: Service Requirements on protection of thirdparties. Version 1.0.