CN100565458C - Security access manager in the middleware - Google Patents
Security access manager in the middleware Download PDFInfo
- Publication number
- CN100565458C CN100565458C CNB038252015A CN03825201A CN100565458C CN 100565458 C CN100565458 C CN 100565458C CN B038252015 A CNB038252015 A CN B038252015A CN 03825201 A CN03825201 A CN 03825201A CN 100565458 C CN100565458 C CN 100565458C
- Authority
- CN
- China
- Prior art keywords
- software
- request
- platform
- application domain
- application
- 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.)
- Expired - Lifetime
Links
Images
Abstract
Be used to control method and system to the visit of the platform of the platform of the portable terminal of radio telecommunications system or another product.This system comprises the platform with software services component and interface component, and this interface component has at least one interface, is used to provide the visit to software services component, so that can install, load and move application domain software in platform.Access controller control application domain software is via the visit of at least one interface to software services component.Access controller comprises blocking module, is used for receiving from application domain software the request of access software services component; And comprise security access manager, be used to determine whether permit license request.If security access manager is permitted this license request, then permit application domain software via at least one interface accessing software services component.
Description
Technical field
Relate generally to field of wireless telecommunications of the present invention more particularly, the present invention relates to be used to control the system and method to the visit of the platform of the portable terminal of radio telecommunications system.
Background technology
Since at first introducing cellular telecommunication system the eighties, the portable terminal that uses in this system (transfer table) is complicated just day by day.At first, the voiceband telephone service (promptly receiving and send Speech Communication) that provides mainly is provided portable terminal.In recent years, developed the portable terminal that also has the ability that transmits the user data that has nothing to do with speech phone call.This user data comprises and will connect the data that transmit by the Dial-up Network of initiating via personal computer (PC).
Current, developing (3G) system of what is called " third generation " that is used for following mobile communication system.The 3G system is the high-speed Internet access combination of communicating by letter with traditional voice, and makes the user can use following function except that Speech Communication: internet browsing, streaming audio/video, location, video conference and many other functions.
Set up third generation partnership projects (3GPP), with compatible between several 3G system that guarantees developing in the whole world.3GPP is developing universal mobile telephone system (UMTS), can transmit speech, data and multimedia land and satellite system in the whole world Anywhere in order to provide.
By the 3GPP standardization effort, the function that comprises in the cellular telecommunication system increases rapidly, and this developer to the portable terminal that will use in system has proposed a large amount of requirements.This requirement is this true aggravation of size, storer and power limited " resource need lack type " environment because of portable terminal.
Traditionally, portable terminal manufacturers design, manufacturing are also sold complete basically mobile terminal system, this system comprises all hardware and the software that basic terminal operation is required, and provides manufacturer or specific user based on its feature and function needed hardware and software desired to the understanding of the market demand.This method does not provide dirigibility, changes or satisfy multi-user's various demands rapidly with the fast adaptation market demand.
Recognize design and make the deficiency of the conventional procedure of portable terminal, developed the mobile-terminal platform device, it comprises and can be used as a plurality of software and hardware unit that have complementary functions that a plurality of users are sold in a unit.Each user can install, be loaded in this stage apparatus the application software of himself and operation subsequently, so that the plateform system of customization is provided for the portable terminal that satisfies user self specific needs.Describe mobile-terminal platform device and plateform system in detail in the common U.S. Patent application No.10/359911 and 10/359835 that transfers the possession of, the disclosure of these applications is incorporated herein by reference.
(wherein mobile-terminal platform device software and the application software exploitation separately respectively of aforesaid plateform system, then by in the mobile-terminal platform device, installing, load and the operation application software making up) non-the machine that may require to move on virtual machine use, as Javamidlet (Java mobile information apparatus small routine).Virtual machine is guaranteed illegal memory access not to take place.Yet, the function that this non-machine application-dependent provided in this machine code of mobile-terminal platform device.The integrality that may jeopardize portable terminal to the unrestricted access of this machine function in for example platform domain or the application domain for example causes the incident of expense and don't notifies the terminal user because of initiating.
Certificate of Origin (certificate of origin) is used for using,, visits the available service subclass that the mobile-terminal platform device provides thereby permit non-machine execution environment to determine trusting degree wherein.Yet above-mentioned situation changes because of the permission permitted may be moved the terminal user when the operation that this is true further complicated.
Therefore, need at any time (when for example moving) can the dynamic registration permission and this machine code of visit mobile-terminal platform device.
Summary of the invention
A kind of system that is used to control to the visit of platform comprises the platform with software services component and interface component, described interface component has at least one interface, be used to provide visit, so that can in platform, install, load and move the application domain program to software services component.Said system also comprises access controller, is used for control request application domain software via the visit of at least one interface to software services component.Access controller comprises: blocking module is used to receive the request of above-mentioned request application domain softward interview software services component; Judgement entity is used to determine whether permit request.If permit above-mentioned request, then permit request application domain software via the described software services component of at least one interface accessing.
A kind of method is used to control the visit to the platform with software services component and interface component, and it comprises the request that receives request application domain softward interview application software member.Interface component has at least one interface, is used to provide the visit to software services component, so that can install, load and move the application domain program on platform.Said method also comprises and determines whether permit above-mentioned request, if permit this request, then permits via the requested software services component of at least one interface accessing.
A kind of system is used to control the visit to the platform of the portable terminal of radio telecommunications system, and it comprises the platform with software services component and interface component.Interface component has at least one interface, is used to provide the visit to software services component, so that can install, load and move non-machine application software on platform.Said system also comprises access controller, is used to control non-machine application software via the visit of at least one interface to software services component.Access controller comprises: blocking module is used to receive the request of above-mentioned non-machine accessible with application software software services component; Judgement entity is used to determine whether permit request.If permit above-mentioned request, then permit non-machine application software via at least one interface accessing software services component.
According to such scheme of the present invention, software services component comprise a plurality of be used to provide service, structure perfect functions software unit, described service offers the user via interface component.
Description of drawings
Fig. 1 is the schematic block diagram that shows the plateform system of the portable terminal that is used for radio telecommunications system, is used for helping to explain principle of the present invention;
Fig. 2 is the schematic block diagram of configuration view of mobile-terminal platform device of the plateform system of displayed map 1, explains principle of the present invention with further help;
Fig. 3 is the schematic block diagram of software architecture that shows the mobile-terminal platform device of Fig. 1 and 2, explains principle of the present invention with further help;
Fig. 4 A is the logic diagram that shows the details of the middleware services layer of Fig. 1-3 of an example embodiment according to the present invention;
Fig. 4 B is the different piece that system is shown, i.e. the realization view of relation between application domain 500, middleware domain 501 and the platform domain 502;
Fig. 5 shows according to the present invention another example embodiment, the schematic block diagram of the details in the open application framework API territory of the middleware services layer of Fig. 4;
Fig. 6 A shows according to the principle of the invention, the schematic block diagram of the details of the message relevant with judgement with license request;
Fig. 6 B shows according to the present invention another example embodiment, the schematic block diagram of the details of the message relevant with judgement with license request;
Fig. 7 be explanation according to the principle of the invention, be used for receiving the process flow diagram of step of the method for permission decision to SAM 518 request visit and from it;
Fig. 8 A and 8B be explanation according to the present invention another example embodiment, with the visit of effective means request more and receive the process flow diagram of step of the method for permission decision;
Fig. 9 illustrates according to the principle of the invention, the schematic block diagram of the details of security access manager;
Figure 10 illustrates another example embodiment according to the present invention, the schematic block diagram of the details of blocking module.
Embodiment
Fig. 1 is the schematic block diagram that shows the plateform system of the portable terminal that is used for radio telecommunications system, is used for helping to explain principle of the present invention.Plateform system is usually with label 10 expressions, and it comprises mobile-terminal platform device 12 and one or more application (being application software) 14 that is mounted, is loaded in the mobile-terminal platform device 12 and move therein.Plateform system 10 is suitable for being combined in usually in the portable terminal with dotted line 16 expressions.
Mobile-terminal platform device 12 comprises software services component 22, hardware component 24 and interface component 26.Software services component 22 comprise a plurality of be used to provide service, structure perfect functions software unit, above-mentioned service offers the user via interface component 26.In demonstration system shown in Figure 1 10, described a plurality of software units comprise the functional software stacks 30-38 of a plurality of vertical direction.Hardware component 24 comprises one group of hardware cell, and this group hardware cell is associated with their functional software stacks separately and is controlled by their functional software stacks separately.In demonstration system shown in Figure 1 10, hardware cell is the different hardware piece 40-48 that is associated with software stack 30-38.
The mobile-terminal platform device 12 of plateform system 10 is suitable for designing, realize, assembling and test as the unit complete, that seal that separates with application software 14 (term used herein " application software " can be the software that any user of providing (for example manufacturer or terminal user) may wish the function except that the platform software function utilized).Correspondingly, the user can develop or obtain they self application software 14, and afterwards this software 14 is added in the mobile-terminal platform device 12, to adjust plateform system 10 according to its needs.Correspondingly, a plurality of different users can be sold or transferred to mobile-terminal platform device 12, wherein each user can customize plateform system 10 by the application software of installing, load and move themselves on this stage apparatus, with satisfy they self to the specific demand of plateform system.
Fig. 2 is the schematic block diagram of an example of configuration view of the platform system for mobile terminals 12 of displayed map 1, understands the present invention with further help.As shown in Figure 2, mobile-terminal platform device 12 is via the software control of carrying out in host CPU 50.Host CPU 50 can comprise one or more processors, as microprocessor, micro programmable processors or DSP (digital signal processor).The software stack 30-38 of software component 22 comprises the hardware driving software 60-68 of the hardware cell that operation is associated with each stack separately.The more details of mobile-terminal platform device 12 and plateform system 10 in the U.S. Patent application No.10/359835 of above-mentioned common transfer, have been provided.Be combined in the mobile-terminal platform device 12 software preferably so that the understandable mode of software organization dispose so that the easier design of this software, easier upgrading or modification.
Fig. 3 is the schematic block diagram that shows the software architecture of mobile-terminal platform device 12, explains principle of the present invention with further help.As shown in Figure 3, services component 22 is except being organized into as mentioned above among a plurality of vertical functional software stacks 30-38, also be arranged to a plurality of flat seams of definition, so that hierarchy of the common definition of the software of the software of middleware services layer and software services component 22 (usually with label 70 expressions), in this layered architecture, each layer arranged from the high-level service layer to the low level services layer with the order that falls progressively.
The difference of this software architecture and standard ISO/OSI (ISO open system interlink) model is that this software architecture comprises the functional software unit of a plurality of horizontal division of the software layer that replenishes a plurality of vertical division.Horizontal division helps to create independently modularizing member very much.
The top of hierarchy is middleware services layer.The level of software services component 22 comprises: the application-server layer 80 that application service is provided; The platform service layer 82 of particular platform service is provided for application; The protocol layer 84 of session protocol and application-specific agreement is provided; The transport layer 86 of audio access/control, data communication agreement, information receiving and transmitting agreement etc. is provided; The data access layer 88 of external data IF visit, structured storage service and other rudimentary platform support service is provided; The physical drivers layer 92 of logical drivers layer 90 and encapsulation hardware dependency.In addition, software services component 22 comprises provides the basic system services of the required general service of stage apparatus layer 94.
Two- layer 90 and 92 beneath formation hardware abstraction layers (HAL), the correlativity between its isolation software and the hardware.Have only physical drivers layer to relate to hardware details (that is, with which register in the addressing ASIC hardware).Logical drivers layer 90 is provided to the logical mappings of hardware, that is, this layer provides bridge joint between the hardware and software part of mobile-terminal platform device 12.
Software itself is organized into a plurality of software modules, as the module 102,104,106 that specifically illustrates among Fig. 3.In software services component 22, individual module only can reside in only flat seam in the vertical functional stack and in this stack.Every layer can comprise one or more modules, and all modules in the specific stack in the certain layer have identical abstraction hierarchy.The software base plate (Software back plane-SwBP) 112 that communication between each module is controlled by the primitive rule collection that is subjected to software module and module accesses is finished.These rules can be summarized as follows:
-software module can be invoked at the function in all following layer interface of its affiliated layer.
-there is not a restriction to direction of serialized data flows.Serial data stream can flow to any direction.
-software module never can be invoked at the function in the above layer interface (in SwBP 112) of its affiliated layer, belongs to which module with these layers and has nothing to do.
-software module can be called the function in the layer interface in its affiliated layer in the same vertical stack.
-software module can be called in another vertical stack the function in the software module in the identical layer (allowing the quantity of this ability with restriction vertical stack middle level).
There is not hard coupling (hardcoupling) between disparate modules in SwBP 112 and the interface.Therefore, can arbitrarily change the realization of module and/or interface, and can not influence the client of interface.The client be for example use, any other consumer of utility routine, plug-in card program or platform service.Lacking hard coupling is a kind of significant capability, does not influence other module in the stage apparatus because it allows increase, deletion or change individual module.
In the U.S. Patent application No.10/359911 of above-mentioned common transfer, described the more details of layered architecture, comprised and realize intercommunicating SwBP software configuration between the mobile-terminal platform device inner module.Middleware services layer is used for providing the clearly interface of definition between the software of mobile-terminal platform device 12 and the application software 14 that will install, load and move in this stage apparatus, and mobile-terminal platform device 12 is encapsulated, and this stage apparatus 12 is isolated with using, and provide various other services for application by self.
Fig. 4 A shows the schematic block diagram of the details of the middleware services layer of interface component 26 in accordance with the principles of the present invention.Shown in Fig. 4 A, middleware services layer comprises a plurality of API territory, comprises non-machine environment (for example Java carries out (Java ExE) environment) API territory 202, open application framework (OAF) API territory 204, open platform API (OPA) territory 206 and UI kit API territory 208.
By the API 202-208 in the middleware services layer, mobile-terminal platform device 12 is supported multiple applied environment.In the example embodiment of Fig. 4, middleware services layer supports this machine to use (that is, through the application of compiling to move by par-ticular processor and instruction set thereof) environment and the Fei Ben machine is used (as JAVA J2ME CLDC/MIDP (Java 2 miniature editions are connected limited equipment disposition/mobile information apparatus profile)) environment.Each applied environment has the characteristic of oneself aspect following:
The method of-Application and Development (programming language support, compiling and be connected).
The method that-execution is used (for example explaining or the execution of this machine code)
-function the service that provides.
Potential restriction in the-use.
By the plurality of optional applied environment is provided, help to provide a series of different far-ranging products that require at aspects such as for example cost, ease for use, Time To Market, function collection, size, portability.
Fig. 4 B illustrates the relation between the different piece of system by realizing view.Main territory is application domain 500, middleware domain 501 and platform domain 502.Module on the higher level is considered as having the dependence to lower-level modules among Fig. 4 B.Application domain 500 can be contained in non-machine application 506 (1)-(N) and this machine application 516 of encapsulation in non-the machine environment 504 (for example JAVA virtual machine).Yet application domain 500 not necessarily needs to hold any non-machine and uses.Before future, self-application 506 and 5 16 services request passed to low level services, these requests were by blocking module 508 control of accepting the interview.This bottom service can comprise insertion program (for example the UI kit 510) that comprises the advanced figure support and the more basic service of being represented by open platform API (OPA) in the middleware domain 501 512.By OPA 512, application can be communicated by letter with application manager (AM) 514 with the renewal of request access permission.In an example embodiment, AM 514 is notified to security access manager (SAM) 518 with any this request.The more details of middleware services layer 26 have been described in the common U.S. Patent application No.10/359772 that transfers the possession of.
Fig. 5 is the block diagram that shows according to the main software module in open application framework (OAF) the API territory 204 of example embodiment of the present invention.As shown in the figure, these modules comprise SAM 518 and access interception module (IM) 223.SAM 518 is responsible for permitting non-machine and uses as the visit of Java application to open platform API territory 206, so that monitor these application according to the certificate of these application.In other words, SAM 518 is responsible for determining whether allow calling from non-machine environment.SAM 518 holds and maintenance and the relevant security strategy of platform service visit.Thus, the visit of comparable the machine applied environment 516 of visit of 504 pairs of this machine platform services of Java Exe environment is more restricted.IM 223 is responsible for monitoring the services request of the application of operation in comfortable non-machine (for example Java) environment 504, in some cases, it is also conceivable that this machine execution environment is carried out the application service request to be monitored.
Generally speaking, AM 514 handle all application registration, installation, start, stop, unloading and delete.Non-machine application service request of IM 223 interception services from the EXE environment to this machine platform (with regard to Java used, interception occurred in the boundary of Java supporting layer) also visited SAM 518 so that this service access is permitted.If permit visit, then non-machine application service request is forwarded to open platform API (OPA) 206, and uses this non-machine application service request of processing as this machine.License request is the portfolio between IM 223 and the SAM 518.Services request is to use the portfolio between any software and platform domain 502 in 250 (referring to for example Fig. 6 A-B) or the application domain 500.Services request represents that the client wants the service in access platform territory 502.
SAM 518 can permit visiting the service of this machine platform in various manners, and one of them example has been shown among Fig. 6 A and Fig. 7.Specifically, Fig. 6 A relates to permit or the member of denial of service request and the block diagram of message, and Fig. 7 illustrates according to the present invention example embodiment, the process flow diagram that is associated with allowance or denial of service request.
With reference to figure 6A and Fig. 7, in step 280, non-machine used the service that 250 requests need the service of this machine platform of visit.In step 282, the above-mentioned services request of IM 223 interceptions, this services request comprises the ID mark of non-machine application 250 of request.In step 284, the ID mark that comprises in license request and this services request is sent to SAM 518 from IM 223.IM223 can also send the sign of this machine platform service of other visit information and non-machine application 250 expectation visits to SAM 518.SAM 518 checks that the security strategy of this machine platform service is to determine whether that can permit non-machine application 250 conducts interviews.In step 286, SAM518 forms permission decision and this judgement is forwarded to IM 223.If the allowance license request then is forwarded to one or more the machine platform services that non-machine used 250 requests in step 288 with this services request.Carry out institute's requested service in step 290 then, if the refusal license request then will be refused response in step 296 and send to non-machine application 250.
If one of ID mark 320 that comprises in the Visitor Logs 318 of ID mark 320 and location does not match, then in the above-mentioned request of step 292 refusal, and in step 296 this request of termination and with non-machine application 250 of its request of returning to, shown in Fig. 7 and 8A.
In alternative dispensing means, permission decision may need approval procedure (approvalprocedure).For example, shown in step 294, may require the user to ratify the visit that this machine platform is served.If ratify this visit, then in step 288, request is transmitted to the service of this machine platform step 294 user.Yet, if in step 294 denied access, refuse above-mentioned request, and end this request and it is returned to the client of the request of sending in step 296 in step 292.
Fig. 6 B, 8A and 8B illustrate another example, and wherein blocking module is made the judgement of permitting or refusing request in this locality, and SAM 518 upgrades the certificate of storing among the IM.According to Fig. 6 B, non-machine used 250 request services.IM 223 these services request of interception.IM 223 is in this locality allowance or refuse this request.Simultaneously, SAM 518 is according to each needs or send the request that IM 223 keeps the record of also permitting according to this of upgrading to IM 223 at set intervals.
Fig. 8 A is the process flow diagram that further specifies according to the process of allowance of Fig. 6 B example shown or denial of service request.As shown in the figure, in step 280 and 282, non-machine used 250 and called services request, and this services request and ID mark are tackled by IM 223.IM 223 enters a judgement in this locality, and will not send to SAM 518 from IM 223 with the license request of ID mark.In the present embodiment, IM 223 safeguards the Visitor Logs of this machine platform service.Each Visitor Logs comprises the ID mark of the application-specific that is licensed for access to this machine platform service of being asked.In step 301, the Visitor Logs of requested machine platform service of IM 223 search marks whether to be associated with above-mentioned Visitor Logs with the ID that determines non-machine application 250 of request in step 303, and therefore determines whether permit above-mentioned request.Use 250 ID mark if in Visitor Logs, find non-machine of request, then permit non-machine and use requested machine platform service of 250 visits in step 303.Be similar to the step 288 of Fig. 7, above-mentioned services request is forwarded to requested machine platform service, and carry out this service in step 290.Use 250 ID mark if in the Visitor Logs of this machine platform service of being asked, find non-machine of request, then refuse above-mentioned request, and end this request and it is returned to the client who sends this request in step 296 in step 292.
In alternative dispensing means, permission decision may need approval procedure.For example, may require the user to ratify the visit that this machine platform is served, shown in step 294.If in step 294 user grant access, then shown in step 288, request is transmitted to the service of this machine platform.Yet,, and end this request and it returned to the client who sends this request in step 296 if, refuse above-mentioned request in step 292 in the described visit of step 294 refusal.
When needed or every predetermined time interval, SAM 518 can the permission update request be distributed at least one IM 223.Shown in Fig. 8 B,, there is different situations for when carrying out this renewal.Run time between, the user can change via AM 514 and uses 250 permission (shown in step 412) for specific non-machine, thereby needs to upgrade the Visitor Logs (shown in step 414) that SAM 518 is safeguarded.Can be forwarded to IM (shown in step 416) by the permission that SAM will upgrade then.Other situation that must upgrade the record of SAM and IM is included in when adding new the application in the system (shown in step 404 and 406) and when using from deletion the system is existing (shown in step 408 and 410).In order further to accelerate permission decision, can use decision cache according to the embodiment of IM 223 as described below.
With reference now to Fig. 9,, it illustrates the details of SAM 518 according to an embodiment of the invention.As shown in the figure, SAM 518 comprises decision cache, is used to write down frequent and/or the most nearest services request, so that find out the permission decision that is associated with particular service request.Non-given machine uses 250 can repeatedly submit identical services request to.Therefore, the frequent services request of decision cache 310 records, and can in request early, search for the permission decision that is associated with particular service request to find.For example, Java uses and can repeatedly ask particular native platform service.The license request that receives comprises the ID mark of non-machine application 250 of request.
When non-machine application 250 sent services request first, SAM 518 access control tabulation (ACL) 312 was to determine whether and give requested machine platform service with permission.The some Visitor Logs of ACL 312 storages, these Visitor Logs come the certifcate of china origin of self-application.These records 314 use with non-machine of each registration and installation as specific Java application is associated.SAM 518 searching request use 314 may record, with the coupling of finding to use with specific request.If find specific request to use in record set, then search permission 316 is to determine whether permit visiting requested machine platform service.Generate permission decision based on the permission 316 that is associated and stores.This permission decision sends to IM 223, and can be stored in together in the decision cache 310 with license request.When next IM 223 intercepts when using 250 services request and it is forwarded to SAM 518 from identical non-machine, with regard to this license request search decision cache 310.When finding license request, the permission decision that will be associated with this license request is forwarded to IM 223.By utilizing decision cache 310, it is more effective that SAM 518 becomes when making permission decision.
Figure 10 illustrates the details of IM 223 in accordance with another embodiment of the present invention.Though it should be noted that ACL and decision cache are arranged in IM 223 in this example, if ACL and decision cache are arranged in SAM 518, identical principle also is suitable for.In Figure 10, the Visitor Logs of ACL 312 storages and Visitor Logs different-format shown in Figure 9.Specifically, in Figure 10, the Visitor Logs 318 of ACL 312 these machine platforms of memory mobile terminal service.Existence is corresponding to the Visitor Logs 318 of each this machine platform service (or service groups) of portable terminal.Each Visitor Logs 318 comprises the ID mark 320 of non-the machine application 250 that is allowed to visit the particular native platform service (or service groups) that is associated with Visitor Logs 318.When needs upgraded access list and record, SAM 518 sent request to IM 223.Update request comprises with the ID mark 320 that upgrades non-the machine application 250 that is associated and the sign that must change requested machine platform service when permitting.The Visitor Logs 318 of requested machine platform service among the IM 223 search ACL 312.In case find, IM 223 just determines whether the ID mark 320 of non-machine application 250 of request is included in the Visitor Logs 318 that finds.If ask non-machine to use 250 ID mark 320 and be included in one of ID mark 320 in the Visitor Logs 318 that finds coupling, use 250 then permission for non-machine of request, and services request is forwarded to this machine platform service processor.Can also permission decision be stored in the decision cache 310 with being similar to reference to the described mode of Fig. 9.
If ID mark 320 does not match with being included in one of ID mark 320 in the Visitor Logs 318 that finds, then in the request of step 292 refusal, and use 250, shown in Fig. 7 and 8A in step 296 abort request and with non-machine of its request of returning to.
Even when operation, also can permit update request to be distributed to the IM 223 of registration on-demand update request and periodicity from SAM 518.The renewable permission that licenses to specific non-machine application 250 of user, thus expired and wrong information is present among the SAM 518.Therefore, when needs or by the periodicity time interval, SAM 518 sends the Visitor Logs 318 of permission update request with renewal ACL 312 to IM 223, thereby safeguards correct permission and/or ID mark.The change that may need specific non-machine to be used 250 permission according to the user uses with this specific non-machine that 250 ID mark 320 adds some Visitor Logs 318 to or from wherein deletion.
In order further to simplify permission decision procedure, can be with such as classification of type such as ID mark 320, permissions 326, with the efficient of the ACL 312 that improves Searching I M 223 (perhaps search SAM 518 when SAM 518 modules are held ACL).For example, each this machine platform service can be assigned to specific security category, each security class is associated with specific permission.Then, based on security class but not individual native platform service is made permission decision.Under normal conditions, the quantity of security class will obviously be less than the quantity of this machine platform service, thereby reduce the search time relevant with definite permission decision.
Though described content constitutes example embodiment of the present invention, should be understood that and to revise the present invention with many kinds of modes, and do not break away from protection scope of the present invention.For example, though the main combining wireless telecommunication system of the present invention wireless terminal platform is described, also can use in conjunction with the other products platform.Owing to can revise the present invention with multiple mode, should be realized that the scope of the invention is only limited by appended claims.
Claims (40)
1. a control is to the system of platform access, and described system comprises:
Platform, it has software services component and interface component, and described interface component has at least one interface, is used to provide the visit to described software services component, so that can install, load and move the application domain program in described platform; And
Access controller is used for control request application domain software via the visit of described at least one interface to described software services component, and described access controller comprises:
Blocking module is used to receive the request of the described software services component of described request application domain softward interview; And
Judgement entity is used to determine whether permit described request; And
Wherein,, then permit described request application domain software via the described software services component of described at least one interface accessing if permit described request,
Described software services component comprises a plurality of functional software unit that are used to provide service, and described service offers the user via described interface component.
2. the system as claimed in claim 1, it is characterized in that: described judgement entity is a security access manager, described security access manager comprises visit and admission policy.
3. described system as claimed in claim 2 is characterized in that:
Described request comprises the sign of described request application domain software; And
Described security access manager comprises the record set of approved request application domain software, is used for determining whether permit based on described sign the described request of described request application domain software.
4. system as claimed in claim 3 is characterized in that:
Described record set comprises the access control collection;
Described security access manager comprises the permission collection that is associated; And
The described permission collection that is associated is used to determine whether permit the described request that included request application domain software is concentrated in described access control.
5. system as claimed in claim 2 is characterized in that: described security access manager comprises decision cache, is used for the request record of maintenance application territory software, so that determine before whether permission decision to have been licensed to described request application domain software.
6. system as claimed in claim 2 is characterized in that:
Described security access manager has the record of request application domain software; And
Described security access manager determines whether permit described request based on the sign that is stored in the described record.
7. system as claimed in claim 2 is characterized in that: if rejecting said request then sends to described request application domain software by described blocking module with refuse information.
8. system as claimed in claim 2 is characterized in that: described application domain software comprises non-machine application domain software.
9. system as claimed in claim 8 is characterized in that: described non-machine application domain software comprises the Java application software.
10. the system as claimed in claim 1, it is characterized in that: described application domain software comprises this machine application software.
11. the system as claimed in claim 1 is characterized in that: described interface component comprises middleware services layer.
12. system as claimed in claim 2 is characterized in that: described platform comprises the platform of the portable terminal that is used for radio telecommunications system.
13. the system as claimed in claim 1 is characterized in that: described judgement entity belongs to described blocking module.
14. system as claimed in claim 13 is characterized in that:
Described request comprises the sign of described request application domain software; And
Described blocking module comprises the record set of approved request application domain software, is used for determining whether permit based on described sign the described request of described request application domain software.
15. system as claimed in claim 14, it is characterized in that: described blocking module comprises decision cache, be used to safeguard application software identifier record, so that determine before whether permission decision to have been licensed to described request application domain software by this machine platform service packet.
16. system as claimed in claim 13 is characterized in that:
Described blocking module has the record of each platform service of described platform; And
Described blocking module determines whether permit described request based on the sign that is stored in the described record.
17. system as claimed in claim 13 is characterized in that: described application domain software comprises non-machine application software.
18. system as claimed in claim 13 is characterized in that: described application domain software comprises this machine application software.
19. the system as claimed in claim 1 is characterized in that also comprising:
System's access modules; And
Wherein said system access modules is suitable for using that to be used to determine to permit by described blocking module still be that the information of rejecting said request is upgraded described blocking module.
20. system as claimed in claim 19 is characterized in that: periodically upgrade by described system access modules.
21. system as claimed in claim 19 is characterized in that: described system access modules is upgraded according to update request.
22. a control is to the method for the visit of platform with software services component and interface component, described interface component has at least one interface, be used to provide visit to described software services component, so that can install on described platform, load and move application domain software, described method comprises:
Receive the request of the described software services component of request application domain softward interview;
Determine whether permit described request; And
If the allowance described request is then permitted via the described requested software services component of described at least one interface accessing,
Described software services component comprises a plurality of functional software unit that are used to provide service, and described service offers the user via described interface component.
23. method as claimed in claim 22 is characterized in that:
Described request comprises the sign of described request application domain software; And
Possible request application domain software assembly is used to determine whether permit the described step of described request.
24. method as claimed in claim 23 is characterized in that: described set comprises:
The access control collection; And
Wherein said determining step comprises the described access control collection of visit.
25. method as claimed in claim 22 is characterized in that: described determining step comprises determines before whether once judgement to have been licensed to described request application domain software.
26. method as claimed in claim 22 is characterized in that:
Store the record of described each platform service of platform; And
Described determining step comprises based on the sign that is stored in the described record and determines whether described request is licensed to described request application domain software.
27. method as claimed in claim 22 comprises:
If rejecting said request then sends to refuse information described request application domain software.
28. method as claimed in claim 22 is characterized in that: described application domain software comprises non-machine application software.
29. method as claimed in claim 28 is characterized in that: described non-machine application domain software comprises the Java application software.
30. method as claimed in claim 22 is characterized in that: described application domain software comprises this machine application software.
31. method as claimed in claim 22 is characterized in that: described platform comprises the platform of the portable terminal that is used for radio telecommunications system.
32. method as claimed in claim 22 is characterized in that also comprising: being used to determine permit still is the lastest imformation of rejecting said request.
33., it is characterized in that: periodically repeat described step of updating as method as described in the claim 32.
34. method as claimed in claim 32 is characterized in that: carry out described step of updating according to update request.
35. a system that is used to control to the visit of the platform of the portable terminal of radio telecommunications system, described system comprises:
Platform, it has software services component and interface component, and described interface component has at least one interface, is used to provide the visit to described software services component, so that can install, load and move non-machine application software on described platform; And
Access controller is used to control described non-machine application software via the visit of described at least one interface to described software services component, and described access controller comprises:
Blocking module is used to receive the request of described non-the described software services component of machine accessible with application software; And
Judgement entity is used to determine whether permit described request; And
Wherein,, then permit described non-machine application software via the described software services component of described at least one interface accessing if permit described request,
Described software services component comprises a plurality of functional software unit that are used to provide service, and described service offers the user via described interface component.
36. system as claimed in claim 35 is characterized in that: described judgement entity belongs to described blocking module.
37. system as claimed in claim 35 is characterized in that: described judgement entity belongs to security access manager.
38. system as claimed in claim 35 is characterized in that: described at least one interface comprises middleware services layer.
39. system as claimed in claim 35 is characterized in that: described non-machine application software comprises the Java application software.
40. system as claimed in claim 35 is characterized in that: can on described platform, load, install and this machine of operation application software.
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US41284402P | 2002-09-23 | 2002-09-23 | |
| US60/412,756 | 2002-09-23 | ||
| US60/412,844 | 2002-09-23 | ||
| US10/666,673 | 2003-09-19 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1802633A CN1802633A (en) | 2006-07-12 |
| CN100565458C true CN100565458C (en) | 2009-12-02 |
Family
ID=36811839
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB038252015A Expired - Lifetime CN100565458C (en) | 2002-09-23 | 2003-09-22 | Security access manager in the middleware |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100565458C (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20110126148A (en) * | 2009-02-27 | 2011-11-22 | 엘지전자 주식회사 | Architecture of a network device for processing applications, and control method for the network device |
| CN101924775B (en) * | 2010-09-08 | 2012-10-10 | 北京大学 | Android application component transparent loading method and system |
-
2003
- 2003-09-22 CN CNB038252015A patent/CN100565458C/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| CN1802633A (en) | 2006-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7149510B2 (en) | Security access manager in middleware | |
| CN100354828C (en) | Middleware services layer for platform system for mobile terminals | |
| CN100380325C (en) | Platform system for mobile terminals | |
| Corradi et al. | Context-based access control for ubiquitous service provisioning | |
| CN101237333B (en) | An universal service platform for supporting multiple services based on multi-network fusion | |
| JP4598354B2 (en) | COMMUNICATION SYSTEM, RELAY DEVICE, AND COMMUNICATION CONTROL METHOD | |
| US7481373B2 (en) | Triggering a proactive session from an applet in a smart card | |
| EP1271902B1 (en) | Method and device for limiting call accompanying execution of application | |
| IL202955A (en) | System and method for handshaking between wireless devices and servers | |
| US11825549B2 (en) | Electronic subscriber identity module (eSIM) profile provisioning | |
| CN102685303A (en) | Communication method and device | |
| JP4584718B2 (en) | System and method for selecting one communication network by one terminal | |
| CN101158898A (en) | Terminal system based on java | |
| CN100565458C (en) | Security access manager in the middleware | |
| US11503456B1 (en) | Maintaining electronic subscriber identity module (eSIM) profiles across multiple mobile network operators (MNOs) | |
| CN1164066C (en) | Processing environment decision device | |
| CN106576329A (en) | Context-based resource access mediation | |
| US11838985B2 (en) | Policy-based management of embedded subscriber identity module (eSIM) profiles | |
| Josifovska | The Queen of SIMs [mobile phones] | |
| KR100746640B1 (en) | Method for connecting blog inside blog mobile phone | |
| Onukwugha et al. | Critical analysis of mobile devices based end-User programming of smart-Spaces | |
| Lewis | From customization to ubiquitous personalization: digital identity and ambient network intelligence | |
| Constantinou et al. | An architecture for a distributed 3G mobile terminal | |
| Panagiotakis et al. | Location-based Service Differentiation | |
| CN116491141A (en) | System and method for making SIM card micro platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CX01 | Expiry of patent term |
Granted publication date: 20091202 |
|
| CX01 | Expiry of patent term |