IP Library Patent Application 18041861
Patent Application
App. No. 18/041,861

SOFTWARE ELIGIBILITY

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
18/041,861
Abstract

A method is for making sure that a piece of software to be installed on an end device is compatible with an existing software and especially the underlying hardware structure of the end device. Software components can be evaluated before installing them, thus preventing incompatible software components from being installed on an end device which would harm or destroy the same. A system arrangement is implemented in accordance with the suggested method along with a computer program product including control instructions for implementing the suggested method.

Claims (32)

1 .- 15 . (canceled)

16 . A method for ensuring eligibility of a piece of software to be installed on an end device, comprising the steps:

creating a requirements specification by evaluating a new piece of software regarding deployment requirements of the end device;

transmitting said requirements specification to the end device;

detecting actual deployment requirements on the end device and comparing the transmitted requirements specification with the detected actual deployment requirements; and

deploying the new piece of software on the end device in case it is determined that the requirements specification complies with the actual deployment requirements,

wherein a software currently installed on the end device comprises an upper software layer and a lower software layer and

creating the requirements specification comprises determining information about capabilities the new piece of software provides to the upper software layer and/or about requirements of the new piece of software for the lower software layer; and

detecting the actual deployment requirements comprises deter-mining information about capabilities the lower software layer provides to the new piece of software and/or about requirements of the upper software layer for the new piece of software.

17 . The method according to claim 16 , wherein

creating the requirements specification comprises determining information about capabilities the new piece of software provides to the end device and/or about requirements of the new piece of software for the end device; and

detecting the actual deployment requirements comprises determining information about capabilities the end device provides to the new piece of software and/or about requirements of the end device for the new piece of software.

18 . The method according to claim 16 , wherein creating the requirements specification comprises providing information about the new piece of software, and/or regarding java card packages in case the new piece of software relates to a Java Card operating system, and/or a version of the new piece of software, or a memory requirement, and/or a memory map, and/or a data format version, and/or a hardware information and/or deployment information.

19 . The method according to claim 16 , wherein that transmitting said requirements specification is performed along with transmitting the new piece of software to the end device or by using a file, the file comprising the requirements specification, a signature and/or the new operating system image.

20 . The method according to claim 16 , wherein the actual deployment requirements are detected by a detection software installed on the end device wherein, preferably, the detection software is integrated into the operating system of the end device.

21 . The method according to claim 16 , wherein deploying the new piece of software comprises unpacking an image file of the new piece of software, checking its integrity, amending currently installed software components, updating currently installed soft-ware components, exchanging currently installed software components, deleting currently installed software components and/or installing the new piece of software on the end device.

22 . The method according to claim 16 , wherein that the requirements specification complies with the actual deployment requirements in case the new operating system is compatible with the currently installed operating system and/or hardware of the end device.

23 . The method according to claim 16 , wherein compliance of the requirements specification with the actual deployment requirements is determined by evaluating a table indicating compatibility information.

24 . The method according to claim 16 , wherein the method is terminated in case the requirements specification does not comply with the actual deployment requirements.

25 . The method according to claim 16 , wherein eligibility of a piece of software is ensured that is to be installed on a mobile phone, a wearable, a portable end device, a tablet computer or notebook and/or on an end device comprising a Tamper Resistant Element.

26 . The method according to claim 16 , wherein a new operating system or operating system image is installed on the end device as the new piece of software.

27 . A system arrangement for ensuring eligibility of a piece of software to be installed on an end device, comprising:

an entity being arranged to create a requirements specification by evaluating a new piece of software regarding deployment requirements of the end device;

an interface entity being arranged to transmit said requirements specification to the end device;

a detection entity being arranged to detect actual deployment requirements on the end device and to compare the transmitted requirements specification with the detected actual deployment requirements; and

a deployment entity being arranged to deploy the new piece of software on the end device in case it is determined that the requirements specification complies with the actual deployment requirements,

wherein a software currently installed on the end device comprises an upper software layer and a lower software layer and the entity being arranged to create a requirements specification is configures to determine information about capabilities the new piece of software provides to the upper software layer and/or about requirements of the new piece of software for the lower software layer; and

the detection entity is configured to determine,

information about capabilities the lower software layer provides to the new piece of software and/or about requirements of the upper soft-ware layer for the new piece of software.

28 . System arrangement according to claim 27 , wherein the entities of the systems arrangement are realized by one or more computer program products,

whereas the detection entity preferably is realized by a detection software installed on the end device.

29 . A computer program product being arranged to detect actual deployment requirements on an end device as the detection step of a method according to claim 16 , when being installed on and executed by the end device.

Assignments (3)
NUNC PRO TUNC ASSIGNMENT Recorded Jul 21, 2024
From: GIESECKE+DEVRIENT EPAYMENTS GMBH
To: GIESECKE+DEVRIENT MOBILE SECURITY GERMANY GMBH
Reel/Frame 068037/0735 →
CHANGE OF NAME Recorded Jun 13, 2024
From: GIESECKE+DEVRIENT MOBILE SECURITY GMBH
To: GIESECKE+DEVRIENT EPAYMENTS GMBH
Reel/Frame 067715/0884 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 11, 2024
From: AMOROS, LUIS MIGUEL; BRAVO, HECTOR; DE ANTONIO, PABLO; GIFRE, CLARA; PATINO, DAVID
To: GIESECKE+DEVRIENT MOBILE SECURITY GMBH
Reel/Frame 067684/0476 →