Method with which a first application can access components of a second application over a logical interface

A device comprising

• a storage area,
• data processing means that can access said storage area, wherein said storage area stores a program that can be executed by said data processing means,
• a chip card reader for sending orders over a standardized API interface to a chip card, wherein
• said program contains instructions for triggering the sending of at least one intentionally misused data unit in order to access at least one component in the chip card for which no standardized order has been provided in the API interface between the chip card and the external device.

A device for communicating with an external device over a logical interface, said device comprising:

• one or more components;
• one or more additional components provided subsequently to said one or more components;
• an interface for communicating with said external device over the logical interface, wherein standardized data units are defined for said communication according to a standard;
• and
• a data handler for recognizing whether said standardized data unit has been formatted according to, or intentionally formatted contrary to, the standard, wherein
• at least a portion of said data unit is routed by said data handler to one or more of said one or more components if said data unit is formatted according to the standard, and wherein
• at least a portion of said data unit is instead routed by said data handler to one or more of said one or more additional components if said data unit is formatted contrary to the standard.

A method for implementing a set of new components without updating an APDU handler, said method comprising the steps of:

• providing a first set of components adapted to be accessed using a standardized APDU formatted according to a first APDU standard, each one of said first set of components for providing an associated desired functionality to a device;
• providing the APDU handler adapted for handling an APDU formatted according to the first APDU standard, but not formatted for handling an APDU according to a second APDU standard that is a later update to the first APDU standard;
• subsequent to providing the APDU handler, providing a second set of components adapted to be accessed using the second APDU standard, said second set of components being provided subsequent to providing said APDU handler, each one of said second set of components for providing an additional associated desired functionality to the device;
• providing an application adapted for providing the standardized APDU for use by said APDU handler for calling one or more of said first set of components;
• said application also being adapted for intentionally misusing an APDU in a manner contrary to the first APDU standard to provide an intentionally misused APDU that is associated with said second set of components;
• said application being further adapted for sending both a standardized APDU and said intentionally misused APDU to said APDU handler;
• said APDU handler determining whether it has received said standardized APDU and whether it has received said misused APDU;
• if said APDU has been determined by said APDU handler as not being intentionally misused, said APDU handler analyzing said APDU and calling one or more of said first set of components for execution based on said analysis;
• if said data unit has been determined as having been intentionally misused, said APDU handler analyzing said misused APDU and calling one or more of said second set of components for execution based on said analysis, wherein
• said one or more of said second set of components is different than said one or more of said first set of components.

A device comprising:

• means for storing and executing a first set of components adapted to be accessed using a standardized APDU formatted according to a first APDU standard, each one of said first set of components for providing an associated desired functionality to said device;
• means for storing and executing the APDU handler, said APDU handler being adapted for handling an APDU formatted according to the first APDU standard, but not formatted for handling an APDU according to a second APDU standard that is a later update to the first APDU standard;
• means for storing and executing, subsequent to storing the APDU handler, a second set of components adapted to be accessed using the second APDU standard, each one of said second set of components for providing an additional associated desired functionality to said device;
• means for storing and executing an application, said application being adapted for, when executed:
• providing the standardized APDU for use by said APDU handler for calling one or more of said first set of components,
• intentionally misusing an APDU in a manner contrary to the first APDU standard to provide an intentionally misused APDU that is associated with said second set of components, and
• sending both a standardized APDU and said intentionally misused APDU to said APDU handler;
• said APDU handler being further adapted for, when executed, determining whether it has received said standardized APDU and whether it has received said misused APDU, wherein
• if said APDU has been determined by said APDU handler as not being intentionally misused, said APDU handler analyzes said APDU and calls one or more of said first set of components for execution based on the analysis, and wherein
• if said data unit has been determined as having been intentionally misused, said APDU handler analyzes said misused APDU and calls one or more of said second set of components for execution based on said analysis.