GB2353918A - Access rights in a mobile communications system - Google Patents
Access rights in a mobile communications system Download PDFInfo
- Publication number
- GB2353918A GB2353918A GB9920703A GB9920703A GB2353918A GB 2353918 A GB2353918 A GB 2353918A GB 9920703 A GB9920703 A GB 9920703A GB 9920703 A GB9920703 A GB 9920703A GB 2353918 A GB2353918 A GB 2353918A
- Authority
- GB
- United Kingdom
- Prior art keywords
- software component
- host
- emulator
- mobile
- mobile host
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45504—Abstract machines for programme code execution, e.g. Java virtual machine [JVM], interpreters, emulators
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/52—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow
- G06F21/53—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems during program execution, e.g. stack integrity ; Preventing unwanted data erasure; Buffer overflow by executing in a restricted environment, e.g. sandbox or secure virtual machine
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2115—Third party
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
A method of testing an executable software component which may be downloaded over a mobile telecommunications network 1 to a mobile host 3 for execution in the mobile host 3. The method comprises transferring a copy of the executable software component from a memory 6,7 in which it resides to an emulator 3 or 8, the emulator 3,8 being able to at least approximately emulate the operation of a mobile host 3 which wishes to run the software component. The software component is executed in the emulator 3,8 and the security exceptions resulting from execution of the software component are identified.
Description
2353918 ACCESS RIGHTS IN A MOBILE COMMUNICATIONS SYSTEM
Field of the Invention
The present invention relates to access rights in a mobile communications system and more particularly to a method and apparatus for allowing the access permissions, required by an executable software component to run in a mobile host, to be determined prior to full execution of the component.
Backaround to the invention
Recent years have seen a rapid growth in the use of mobile telecommunications systems. This growth has been accompanied by an ever increasing range of services and functions available to mobile telecommunication network subscribers. At least a proportion of these added services and functions have been made available by the possibility to download software components from a mobile network to a mobile host (e. g. telephone or communicator) over the air interface. Typically, downloaded components are executable in the mobile host.
The volume and range of downloadable software components is likely to grow rapidly in the near future due at least in part to the introduction of new mobile telecommunication standards such as GPRS and LJMTS. The introduction of added communication interfaces (such as BLUETOOTH) for facilitating communication between a mobile host and devices such as televisions, vending machines, etc, over a local network is likely to add further to this growth.
Execution of many of the proposed downloadable software components will result in costs being incurred, host flinctionality being altered, private files being accessed and confidential information disclosed, or other actions being carried out which are likely to be of concern to a subscriber. It is important therefore that a subscriber be able to maintain control over the types of actions which a software component may carry out.
2 In practice, this is likely to be achieved by attaching to each software component a certificate which is known to the mobile host and which authenticates the source and/or nature of the component to the host. It is also possible that the software component may be accompanied by a set of required "access permissions" which identify to the mobile host the actions which will be taken by the component when it is executed. The required access permissions are likely to be "encapsulated" in the certificate and will be compared by the host against a set of pre-set (or granted) access permissions defined by the user.
Summary of the Present Invention.
The inventor of the present invention has recognised that a mobile host user may wish to execute a downloaded software component even if the component is accompanied by a permission or set of permissions which have not been pre-set at the host. He has further recognised that to execute such a downloaded component in the host may result in faults at the host if it attempts to perform actions which are not permitted or if it requires data which is unavailable, i.e. if the component gives rise to security exceptions.
It is an object of the present invention to overcome or at least mitigate the disadvantage noted in the preceding paragraph. This and other objects are achieved by providing a host emulator in which the executable software component may be run or tested in isolation.
According to a first aspect of the present invention there is provided a method of testing an executable software component which may be downloaded over a mobile telecommunications network to a mobile host for execution in the mobile host, the method comprising:
transferring a copy of the executable software component from a memory in which it resides to an emulator, the emulator being able to at least substantially emulate the operation of a mobile host which wishes to run the software component; and 3 executing the software component in the emulator and identifying any security exceptions resulting from execution of the software component.
Embodiments of the present invention allow the "testing" of a software component prior to its real time execution in a mobile host. This allows errors and insufficiencies to be predicted and therefore faults, including run-time errors, to be avoided.
Preferably, the method comprises the step of identifying access permissions which are not pre-set for the destination mobile host and which are required to avoid said security exceptions. The mobile host is notified of these identified access permissions, and the host user may be given the opportunity to authorise or deny the identified permissions.
In certain embodiments of the present invention the emulator may be located at the mobile host which wishes to run the software component. In other embodiments, the emulator may be located within the mobile telecominunications network, e.g. at a network node.
Preferably, the host emulator has access to a set of commonly occurring call-stack scenarios which enable the emulator to execute the software component in a suitable simulated environment.
The host emulator is preferably provided with details of the currently defined or pre-set access permissions for the mobile host (or associated subscriber). These may be permanently available to the emulator or may be provided to the emulator each time a request is made to download a software component.
Preferably, said software component is transferred together with a set of required access permissions. The method of the invention may comprise an initial step of comparing the required permissions against the pre-set permissions of the destination host. The emulation step is only carried out if one or more of the required permissions are not preset in the host. In certain embodiments of the invention, the required access permissions may be contained in an authentication certificate attached to or contained in the software component.
Examples of executable software components which may be tested with the present invention include Java written service code and Java applets.
According to a second aspect of the present invention there is provided apparatus for testing an executable software component which may be downloaded over a mobile telecommunications network to a mobile host for execution in the mobile host, the apparatus comprising: means for transferring a copy of the executable software component from a memory in which it resides to an emulator, the emulator being able to at least substantially emulate the operation of a mobile host which wishes to run the software component; and means for executing the software component in the emulator and identifying security exceptions resulting from the execution of the software component.
According to a third aspect of the present invention there is provided a mobile host comprising: a memory arranged in use to store a set of access permissions; means for executing a software component which may be downloaded into said memory from a remote location over a mobile telecommunications network; means for making said access permissions available to an emulator which is able to at least substantially emulate the operation of said executing means, the emulation means being arranged in use to receive and execute said software component for the purpose of identifying security exceptions resulting from the execution of the software component; and means for receiving from the host emulator an identification of access permissions required to overcome any security exceptions identified by the emulator.
In certain embodiments of the present invention, the mobile host comprises means for providing said host emulator. This means may comprise for example a microprocessor which also provides said means for executing the software component.
In other embodiments of the present invention, the host emulator is provided by a means located within the mobile telecommunications network.
According to a fourth aspect of the present invention there is provided a method of testing an executable software component which may be downloaded over a mobile telecommunications network to a mobile host for execution in the mobile host, the method comprising:
analysing the source code of the software component prior to executing it in the mobile host to identify any security exceptions likely to result from execution of the component; and identifying the access permission(s) required to overcome the security exceptions.
In certain embodiments of the present invention, the step of analysing the source code of the software component is carried out at the mobile host. Iii other embodiment of the invention, that step is carried out at a node of the mobile telecommunications network.
According to a fifth aspect of the present invention there is provided apparatus for testing an executable software component which may be downloaded over a mobile telecommunications network to a mobile host for execution in the mobile host, the apparatus comprising:
means for analysing the source code of the software component prior to executing it in the mobile host to identify any security exceptions likely to result from execution of the component; and means for identifying the access permission(s) required to overcome the security exceptions.
Brief Description of the Drawings
6 Figure I illustrates schematically a telecommunications system; Figure 2 is a flow diagram illustrating a method of testing and downloading an executable software component over the telecommunications network of Figure 1; and Figure 3 is a flow diagram illustrating an alternative method of testing and downloading an executable software component over the telecommunications network of Figure 1.
Detailed Description of Preferred Embodiments
There is illustrated in Figure I a telecommunications system comprising a mobile telecommunications network 1. This network may for example be a Universal Mobile Telecommunications System (UMTS) network which supports both voice and data services using packet switched data transmission. The architecture and functionality of a UMTS network will not be described in detail here but rather reference should be made to the recommendations and standards of the European Telecommunications Standards Institute (ETSI). Figure 1 illustrates an access node 2 of the UMTS network I which acts as a local switching centre for mobile hosts such as the host 3 illustrated in the Figure (intermediate base stations and base station controllers may couple the mobile host 3 to the access node 2). Figure 1 also illustrates a gateway node 4 of the LJMTS network 1 which represents a gateway between the UMTS network I and foreign networks. In this example, the gateway node 4 is coupled to the Internet 5.
The mobile host 3 comprises a microprocessor and digital memory (not shown). In normal use, the microprocessor executes software code permanently stored in the memory to enable the host 3 to perform general purpose operations, e.g. telephone services, Short Message Service, as well as local services such as updating time and calendar information, diary, etc. In addition to these operations, the mobile host 3 is capable of performing additional tasks when appropriate executable software components are downloaded into its memory. These additional operations could include for example an ability to automatically update a host diary with local sporting/arts events over the wireless interface. The configuration of the mobile host 3 may also be altered by downloading executable software components.
7 The user of the mobile host 3 is able to request from the UMTS network I the downloading of specified software components, for example using a display and keypad of the host 3 or using voice commands. In some cases, a menu of software components available for downloading may be sent to the mobile host 3 by the access node 2. The software components may reside either within the UMTS network I or outside of that network and may be Java applets (or jar files). Figure I illustrates a service node 6 of the UMTS network I and which provides a repository for software components. Software components may alternatively be retrieved, via the gateway node 4, from a remote server 7 which is coupled to the Internet 5. In either case, a requested executable software component is received by the access node 2.
It will be appreciated that the execution of a software component in the mobile host 3 may cause alterations in the state and operability of the mobile host, and may result in additional costs being incurred to the host's user (e.g. as a result of calls being initiated or data being transferred). It is therefore important for the user to maintain control of what "access permissions" are granted to executable software components. For this purpose, the mobile host 3 maintains in its memory a list of access permissions. For example, the user may set an access permission which allows entries to be made into his host's electronic diary, the sending of data messages, etc. If an access permission is not set, then an executed software component requiring that permission to run will most likely fail during execution. Following the downloading of a software component into the memory of the mobile host 3, the required access permissions, which accompany the component (for example contained within an authentication certificate), are inspected by the host to determine if they are all currently set by the hosts user. If the answer is yes, then the component can be executed by the host's microprocessor in the normal manner.
In order to avoid possible run-time errors, components which are accompanied by required access permissions not pre-set by the user are tested in a host emulator following the downloading of the component from the access node 2 into the memory of the mobile host 3. The emulator runs on the mobile host's microprocessor according to 8 software code pre-stored in the host's memory. The emulator is not allowed to reconfigure any of the host's settings, nor is it allowed to initiate any external communications, e.g. with the UMTS network 1. Rather, the memory contains simulated data (for example experimentally derived approximations regarding access requests) which allows the emulator to run in isolation, i.e. the emulator acts as a "sandbox". When a downloaded software component is executed in the emulator, the emulator identifies all security exceptions raised by non-permitted access requests attempted during execution.
Assuming that one or more such security exceptions are identified, these are interpreted and the access permissions required to overcome the exceptions are presented to the user, for example by displaying them on the host's display. The user then has the opportunity to grant the relevant permissions, in which case the component will be executed for real, or to deny the permissions in which case the component will be discarded. Additional permissions may be granted on a permanent or temporary basis.
The testing and downloading method described above is further illustrated in the flow diagram of Figure 2.
The flow diagram of Figure 3 illustrates an alternative method of testing a software component prior to executing the component in real time in the mobile host 3. In this scenario, the mobile host 3 delegates the emulation task to a network node 8 of the UMTS network 1, the network node 8 being associated with the access node 2 and comprising a suitable microprocessor and memory containing emulation code. The mobile host 3 encapsulates its (use defined) access permissions in a so-called mobile "agent" and sends these to the network node 8. When the host 3 requests the downloading of a software component via the access node 2, the software component is initially routed from the service node 6, or an external node such as the remote Internet server 7, to the network node 8. Assuming that the software component is accompanied by access permissions which are not pre-set by the host user, the emulator is run on the network node 8.
9 The network node 8 is provided with a large set of commonly occurring call-stack scenarios (of service runs) which have been experimentally derived using test runs. The test runs may have concentrated on typical service types offered in the majority of networks. The network node 8 runs the host emulator using as its operating environment the access permissions received in the mobile agent and the call-stack scenarios. As with the previous embodiment, any security exceptions identified during the emulation are identified and interpreted to determine the required access permissions. These permissions are then presented to the user (by encapsulating them in a mobile agent which is returned to the host 3), who then has the opportunity to grant or deny the relevant permissions.
The advantages of this second embodiment include the greater memory and processing power available at a network node which allow for faster emulation with a greater number of predefined call-stack scenarios, as well as a reduction in the computational load placed on the mobile host. A disadvantage is a potential increase in the volume of signalling traffic.
It will be appreciated by the person of skill in the art that various modifications may be made to the above described embodiments without departing from the scope of the present invention. For example, security exceptions may be identified by analysing: the associated code (if available) prior to its execution in the mobile host 3 to identify the required permissions.
Claims (17)
1. A method of testing an executable software component which may be downloaded over a mobile telecommunications network to a mobile host for execution in the mobile host, the method comprising: transferring a copy of the executable software component from a memory in which it resides to an emulator, the emulator being able to at least substantially emulate the operation of a mobile host which wishes to run the software component; and executing the software component in the emulator and identifying any security exceptions resulting from execution of the software component.
2. A method according to claim I and comprising the step of identifying access permissions which are not pre-set for the destination mobile host and which are required to avoid said security exceptions.
3. A method according to claim 2 and comprising notifying the mobile host of these identified access permissions, and giving the host user the opportunity to authorise or deny the identified permissions.
4. A method according to any one of the preceding claims, wherein the emulator is located at the mobile host which wishes to run the software component.
5. A method according to any one of claims 1 to 3, wherein the emulator is located within the mobile telecommunications network.
6. A method according to any one of the preceding claims, wherein the host emulator has access to a set of commonly occurring call-stack scenarios which enable the emulator to execute the software component in a suitable simulated environment.
7. A method according to any one of the preceding claims, wherein the host emulator is provided with details of the currently defined or pre- set access pen-nissions for the mobile host or associated subscriber.
11
8. A method according to any one of the preceding claims, wherein said software component is transferred together with a set of required access permissions.
9. A method according to claim 8 and comprising an initial step of comparing the required permissions against the pre-set permissions of the destination host and carrying out the emulation step only if one or more of the required permissions are not pre-set in the host.
10. Apparatus for testing an executable software component which may be downloaded over a mobile telecommunications network to a mobile host for execution in the mobile host, the apparatus comprising: means for transferring a copy of the executable software component from a memory in which it resides to an emulator, the emulator being able to at least substantially emulate the operation of a mobile host which wishes to run the software component; and means for executing the software component in the emulator and identifying security exceptions resulting from the execution of the software component.
11. A mobile host comprising: a memory arranged in use to store a set of access permissions; means for executing a software component which may be downloaded into said memory from a remote location over a mobile telecommunications network; means for making said access permissions available to an emulator which is able to at least substantially emulate the operation of said executing means, the emulation means being arranged in use to receive and execute said software component for the purpose of identifying security exceptions resulting from the execution of the software component; and means for receiving from the host emulator an identification of access permissions required to overcome any security exceptions identified by the emulator.
12 12. A mobile host according to claim 11, wherein the mobile host comprises means for providing said host emulator.
13. A mobile host according to claim 11, wherein the host emulator is provided by a means located within the mobile telecommunications network.
14. A method of testing an executable software component which may be downloaded over a mobile telecommunications network to a mobile host for execution in the mobile host, the method comprising: analysing the source code of the software component prior to executing it in the mobile host to identify any security exceptions likely to result from execution of the component; and identifying the access permission(s) required to overcome the security exceptions.
15. A method according to claim 14, wherein the step of analysing the source code of the software component is carried out at the mobile host.
16. A method according to claim 14, wherein the step of analysing the source code of the software component is carried out at a node of the mobile telecommunications network.
17. Apparatus for testing an executable software component which may be downloaded over a mobile telecommunications network to a mobile host for execution in the mobile host, the apparatus comprising: means for analysing the source code of the software component prior to executing it in the mobile host to identify any security exceptions likely to result from execution of the component; and means for identifying the access pennission(s) required to overcome the security exceptions.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB9920703A GB2353918B (en) | 1999-09-03 | 1999-09-03 | Access rights in a mobile communications system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB9920703A GB2353918B (en) | 1999-09-03 | 1999-09-03 | Access rights in a mobile communications system |
Publications (3)
Publication Number | Publication Date |
---|---|
GB9920703D0 GB9920703D0 (en) | 1999-11-03 |
GB2353918A true GB2353918A (en) | 2001-03-07 |
GB2353918B GB2353918B (en) | 2003-12-31 |
Family
ID=10860189
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
GB9920703A Expired - Fee Related GB2353918B (en) | 1999-09-03 | 1999-09-03 | Access rights in a mobile communications system |
Country Status (1)
Country | Link |
---|---|
GB (1) | GB2353918B (en) |
Cited By (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1313335A1 (en) * | 2001-11-19 | 2003-05-21 | Siemens Aktiengesellschaft | Method, apparatus and program for determining and checking a permission to set up a connection |
GB2386503A (en) * | 2002-03-12 | 2003-09-17 | Toshiba Res Europ Ltd | Generating and downloading platform specific code |
WO2004008434A1 (en) * | 2002-07-17 | 2004-01-22 | Nokia Corporation | Mobile device having voice user interface, and a methode for testing the compatibility of an application with the mobile device |
US7006964B2 (en) | 2000-12-21 | 2006-02-28 | Nokia Corporation | Communication terminals |
WO2007110105A1 (en) * | 2006-03-27 | 2007-10-04 | Telecom Italia S.P.A. | Method and system for mobile network security, related network and computer program product |
US20080046886A1 (en) * | 2006-08-21 | 2008-02-21 | Research In Motion Limited | Auditing Application Activities |
US20120266157A1 (en) * | 2011-04-18 | 2012-10-18 | Samsung Electronics Co., Ltd. | Broadcast receiving apparatus and method of installing service |
US8321837B2 (en) * | 2006-01-23 | 2012-11-27 | Microsoft Corporation | Techniques for minimum permissions detection and verification |
EP2533150A1 (en) * | 2011-06-07 | 2012-12-12 | Research In Motion Limited | Methods and devices for controlling access to computing resources |
US8650550B2 (en) | 2011-06-07 | 2014-02-11 | Blackberry Limited | Methods and devices for controlling access to computing resources |
US8763080B2 (en) | 2011-06-07 | 2014-06-24 | Blackberry Limited | Method and devices for managing permission requests to allow access to a computing resource |
US9053337B2 (en) | 2011-06-07 | 2015-06-09 | Blackberry Limited | Methods and devices for controlling access to a computing resource by applications executable on a computing device |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9603192B2 (en) | 2013-01-16 | 2017-03-21 | Ncore Communications, Inc. | Methods and apparatus for hybrid access to a core network |
JP2017532889A (en) * | 2014-09-25 | 2017-11-02 | モヘビー、ベザード | Method and apparatus for hybrid access to core network based on proxied authentication |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1996024231A1 (en) * | 1995-01-30 | 1996-08-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Flexible downloading of software |
EP0767426A1 (en) * | 1995-10-05 | 1997-04-09 | Siemens Aktiengesellschaft | Method for programming an apparatus |
EP0930793A1 (en) * | 1997-12-22 | 1999-07-21 | Texas Instruments Inc. | Mobile equipment with a plurality of processors |
-
1999
- 1999-09-03 GB GB9920703A patent/GB2353918B/en not_active Expired - Fee Related
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1996024231A1 (en) * | 1995-01-30 | 1996-08-08 | Telefonaktiebolaget Lm Ericsson (Publ) | Flexible downloading of software |
EP0767426A1 (en) * | 1995-10-05 | 1997-04-09 | Siemens Aktiengesellschaft | Method for programming an apparatus |
EP0930793A1 (en) * | 1997-12-22 | 1999-07-21 | Texas Instruments Inc. | Mobile equipment with a plurality of processors |
Cited By (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7006964B2 (en) | 2000-12-21 | 2006-02-28 | Nokia Corporation | Communication terminals |
US7448082B2 (en) | 2001-11-19 | 2008-11-04 | Nokia Siemens Networks Gmbh & Co. Kg | Method for defining and checking a connection establishment authorisation, associated program data packet, associated device and associated program |
WO2003045090A3 (en) * | 2001-11-19 | 2003-12-11 | Siemens Ag | Method for defining and checking a connection establishment authorisation, associated program data packet, associated device and associated program |
EP1313335A1 (en) * | 2001-11-19 | 2003-05-21 | Siemens Aktiengesellschaft | Method, apparatus and program for determining and checking a permission to set up a connection |
GB2386503A (en) * | 2002-03-12 | 2003-09-17 | Toshiba Res Europ Ltd | Generating and downloading platform specific code |
GB2386503B (en) * | 2002-03-12 | 2004-04-21 | Toshiba Res Europ Ltd | Code modification systems |
US7809578B2 (en) | 2002-07-17 | 2010-10-05 | Nokia Corporation | Mobile device having voice user interface, and a method for testing the compatibility of an application with the mobile device |
WO2004008434A1 (en) * | 2002-07-17 | 2004-01-22 | Nokia Corporation | Mobile device having voice user interface, and a methode for testing the compatibility of an application with the mobile device |
US8321837B2 (en) * | 2006-01-23 | 2012-11-27 | Microsoft Corporation | Techniques for minimum permissions detection and verification |
WO2007110105A1 (en) * | 2006-03-27 | 2007-10-04 | Telecom Italia S.P.A. | Method and system for mobile network security, related network and computer program product |
US8443439B2 (en) | 2006-03-27 | 2013-05-14 | Telecom Italia S.P.A. | Method and system for mobile network security, related network and computer program product |
US20080046886A1 (en) * | 2006-08-21 | 2008-02-21 | Research In Motion Limited | Auditing Application Activities |
US8990929B2 (en) * | 2006-08-21 | 2015-03-24 | Blackberry Limited | Auditing application activities |
US20120266157A1 (en) * | 2011-04-18 | 2012-10-18 | Samsung Electronics Co., Ltd. | Broadcast receiving apparatus and method of installing service |
EP2515231A1 (en) * | 2011-04-18 | 2012-10-24 | Samsung Electronics Co., Ltd. | Broadcast receiving apparatus and method of installing service |
EP2533150A1 (en) * | 2011-06-07 | 2012-12-12 | Research In Motion Limited | Methods and devices for controlling access to computing resources |
US8650550B2 (en) | 2011-06-07 | 2014-02-11 | Blackberry Limited | Methods and devices for controlling access to computing resources |
US8763080B2 (en) | 2011-06-07 | 2014-06-24 | Blackberry Limited | Method and devices for managing permission requests to allow access to a computing resource |
US9053337B2 (en) | 2011-06-07 | 2015-06-09 | Blackberry Limited | Methods and devices for controlling access to a computing resource by applications executable on a computing device |
US9112866B2 (en) | 2011-06-07 | 2015-08-18 | Blackberry Limited | Methods and devices for controlling access to computing resources |
Also Published As
Publication number | Publication date |
---|---|
GB9920703D0 (en) | 1999-11-03 |
GB2353918B (en) | 2003-12-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6591095B1 (en) | Method and apparatus for designating administrative responsibilities in a mobile communications device | |
JP4598354B2 (en) | COMMUNICATION SYSTEM, RELAY DEVICE, AND COMMUNICATION CONTROL METHOD | |
US8272030B1 (en) | Dynamic security management for mobile communications device | |
AU2003293434C1 (en) | System and method for handshaking between wireless devices and servers | |
EP3627321A1 (en) | Mobile terminal with middleware security access manager | |
EP2272232B1 (en) | Method and system for executing applications in wireless telecommunication networks | |
US20060068786A1 (en) | Dialing services on a mobile handset and remote provisioning therefor | |
US20060009204A1 (en) | Telephone functionality for generic applications in a mobile handset | |
EP1338161B1 (en) | Reconfiguration management architectures for mobile communication systems | |
US20050073982A1 (en) | Connector gateway | |
RU2339076C2 (en) | Execution of non-verified programs in radio communication device | |
KR100478474B1 (en) | Method and apparatus for limiting call origination accompanied by executing application | |
CN100489767C (en) | Communicating device | |
GB2353918A (en) | Access rights in a mobile communications system | |
JP2010538499A (en) | Interactive control of mobile device capabilities and access to services | |
US20050005099A1 (en) | Communication device and program | |
EP2356805B1 (en) | Method and system for service management of mobile stations | |
KR101305968B1 (en) | Method for controlling telephone conversation remotely, and terminal thereof | |
CN101170733A (en) | An authentication and charging control method, device and system for WAP service | |
KR100608150B1 (en) | Wireless contents download system and method thereof for wireless internet service system | |
JP4358478B2 (en) | COMMUNICATION TERMINAL ACCESS CONTROL METHOD, CONTENT PROVIDING METHOD, COMMUNICATION SYSTEM, AND RELAY DEVICE | |
CN1965556A (en) | Method and module for software updating of a gateway between a network operator and a local area network | |
EP1533975A2 (en) | Method and System for communication between a multi-modal device and a Web Application | |
EP4192060A1 (en) | Management of subscriber profiles on an euicc | |
JP4580164B2 (en) | Electronic equipment and programs |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PCNP | Patent ceased through non-payment of renewal fee |
Effective date: 20090903 |