Abstract: When operational, a first node of an IMS network handles a registration of a UE on the IMS network, and receives a first request to reregister the UE with the IMS network. The first node creates a registration confirmation, and sends the registration confirmation to the UE. The second node of the IMS network receives a second request to reregister the UE with the IMS network and an indication that the first node has failed. The second node reduces IMS network congestion by avoiding reporting to the UE that the first node has failed, and by sending a message confirming reregistration. Upon receiving the message, the UE considers the registration valid for a predetermined period. Upon expiration of the predetermined period the UE sends a request to reregister. The message prevents the UE from congesting the IMS network.

Abstract: A method for preserving backward compatibility involves adding a new virtual method to a first version of a code package comprising a plurality of members to obtain a second version of the code package, wherein the plurality of members include a plurality of virtual methods having at least a first virtual method that is assigned a first token number and a second virtual method that is assigned a second token number sequentially after the first token number, converting a set of code that is part of the first version of the code package to obtain a converted file, modifying the converted file to include backward compatibility information associated with a plurality of token numbers assigned to the plurality of virtual methods in the first version of the code package, and adjusting the assigned first and second token numbers at one of linking time and runtime based on the backward compatibility information.

Abstract: A method for preserving backward compatibility involves adding a new virtual method to a first version of a code package comprising a plurality of members to obtain a second version of the code package, wherein the plurality of members include a plurality of virtual methods having at least a first virtual method that is assigned a first token number and a second virtual method that is assigned a second token number sequentially after the first token number, converting a set of code that is part of the first version of the code package to obtain a converted file, modifying the converted file to include backward compatibility information associated with a plurality of token numbers assigned to the plurality of virtual methods in the first version of the code package, and adjusting the assigned first and second token numbers at one of linking time and runtime based on the backward compatibility information.

Abstract: One particular implementation may take the form of a system or method for tracking application identification and application context in a context-isolated computing environment. The method may store such application information to reduce redundant information being stored on a stack. More particularly, the embodiment may store the application information in a context-specific marker frame. The context-specific marker frame may be stored once on the stack or it may be stored separately from the stack to maintain a small stack size. In another implementation, an invocation handler method may be called to store the redundant information about the executing application. The invocation handler may store the necessary information in a well-known location for later use by the virtual machine. The invocation handler may also provide further benefits, such as synchronization to ensure thread safety on shareable objects.

Abstract: A system and method for object deletion in persistent memory using bitmap windows representing memory chunks. In accordance with an embodiment, the system can generally be used with computing environments that use persistent memory, such as smart cards, Java Cards, and other resource-constrained environments. In accordance with an embodiment, the system comprises a processor or computational engine and a persistent memory for storage of software objects; and a data structure which can include one or more memory bitmap windows, each of which represents a chunk of addressable space in the persistent memory; wherein the system uses the one or more memory bitmap windows in deleting non-reachable objects from the persistent memory.

Abstract: A system and method for object deletion in persistent memory using bitmap windows representing memory chunks. In accordance with an embodiment, the system can generally be used with computing environments that use persistent memory, such as smart cards, Java Cards, and other resource-constrained environments. In accordance with an embodiment, the system comprises a processor or computational engine and a persistent memory for storage of software objects; and a data structure which can include one or more memory bitmap windows, each of which represents a chunk of addressable space in the persistent memory; wherein the system uses the one or more memory bitmap windows in deleting non-reachable objects from the persistent memory.

Abstract: To execute legacy smart card applications in a next generation smart card environment, a mechanism converts the applications into a format executable by the next generation smart card platforms. For instance, in a Java-based environment, a normalizer tool translates a CAP file into a Java Class file. Additional mechanisms recreate, on next generation smart cards, a specialized environment that allows the legacy applications to execute without impacting legacy and non-legacy application performance. For example, mechanisms create new instances of previously shared objects so that legacy applications can continue to expect exclusive access to those objects. Moreover, mechanisms manage the communication between a legacy application and non-legacy applications by controlling how and when calls are sent to the legacy application.

Abstract: One particular implementation may take the form of a system or method for tracking application identification and application context in a context-isolated computing environment. The method may store such application information to reduce redundant information being stored on a stack. More particularly, the embodiment may store the application information in a context-specific marker frame. The context-specific marker frame may be stored once on the stack or it may be stored separately from the stack to maintain a small stack size. In another implementation, an invocation handler method may be called to store the redundant information about the executing application. The invocation handler may store the necessary information in a well-known location for later use by the virtual machine. The invocation handler may also provide further benefits, such as synchronization to ensure thread safety on shareable objects.

Abstract: To execute legacy smart card applications in a next generation smart card environment, a mechanism converts the applications into a format executable by the next generation smart card platforms. For instance, in a Java-based environment, a normalizer tool translates a CAP file into a Java Class file. Additional mechanisms recreate, on next generation smart cards, a specialized environment that allows the legacy applications to execute without impacting legacy and non-legacy application performance. For example, mechanisms create new instances of previously shared objects so that legacy applications can continue to expect exclusive access to those objects. Moreover, mechanisms manage the communication between a legacy application and non-legacy applications by controlling how and when calls are sent to the legacy application.