Abstract: A system performs interoperable operations to unlock different wireless devices on different wireless networks. The system can receive requests to unlock wireless devices that are locked based on different restrictions, where unlocking requires performing different unlock processes that are normally exclusive to respective carriers, networks, or types of devices. The system can coordinate the interoperable operations to remove the restrictions based on requirements defined for the unlock processes. In particular, the system can identify a policy engine and a network resource to determine whether a particular wireless device is eligible for being unlocked and then utilize the network resource to unlock the wireless device. The system can unlock the different wireless devices by coordinating the same operations with different policy engines and network resources of different carriers, networks, or device manufacturers.

Abstract: A system performs interoperable operations to unlock different wireless devices on different wireless networks. The system can receive requests to unlock wireless devices that are locked based on different restrictions, where unlocking requires performing different unlock processes that are normally exclusive to respective carriers, networks, or types of devices. The system can coordinate the interoperable operations to remove the restrictions based on requirements defined for the unlock processes. In particular, the system can identify a policy engine and a network resource to determine whether a particular wireless device is eligible for being unlocked and then utilize the network resource to unlock the wireless device. The system can unlock the different wireless devices by coordinating the same operations with different policy engines and network resources of different carriers, networks, or device manufacturers.

Abstract: A system performs interoperable operations to unlock different wireless devices on different wireless networks. The system can receive requests to unlock wireless devices that are locked based on different restrictions, where unlocking requires performing different unlock processes that are normally exclusive to respective carriers, networks, or types of devices. The system can coordinate the interoperable operations to remove the restrictions based on requirements defined for the unlock processes. In particular, the system can identify a policy engine and a network resource to determine whether a particular wireless device is eligible for being unlocked and then utilize the network resource to unlock the wireless device. The system can unlock the different wireless devices by coordinating the same operations with different policy engines and network resources of different carriers, networks, or device manufacturers.

Abstract: A system performs interoperable operations to unlock different wireless devices on different wireless networks. The system can receive requests to unlock wireless devices that are locked based on different restrictions, where unlocking requires performing different unlock processes that are normally exclusive to respective carriers, networks, or types of devices. The system can coordinate the interoperable operations to remove the restrictions based on requirements defined for the unlock processes. In particular, the system can identify a policy engine and a network resource to determine whether a particular wireless device is eligible for being unlocked and then utilize the network resource to unlock the wireless device. The system can unlock the different wireless devices by coordinating the same operations with different policy engines and network resources of different carriers, networks, or device manufacturers.

Abstract: A network device may provide heartbeat requests to a plurality of network function producers, and may set states of the plurality of network function producers to suspended based on not receiving responses to the heartbeat requests after a predetermined time. The network device may receive, from a network function consumer, a discovery request requesting identification of network function producers providing a service or with a network function type, and may determine, based on the discovery request, that none of the plurality of network function producers are available based on the states of the plurality of network function producers being set to suspended. The network device may provide, to the network function consumer, a discovery response that includes a list of the plurality of network function producers with status indicators set to active.

Abstract: The present invention includes a mold neutralization system and process based on a hyper-excited mixture composed of a photoexcited carrier constituent within a physiologically inert solution. The efficacy of the system and process can be readily and quickly determined by physiological examination of the organism receiving the system and process.

Abstract: A system for ultrasonic profiling of a weld sample includes a carriage movable in opposite first and second directions. An ultrasonic sensor is coupled to the carriage to move over the sample as the carriage moves. An encoder determines the position of the carriage to determine the position of the sensor. A spring is connected at one end of the carriage. Upon the carriage being moved in the first direction toward the spring such that the carriage and the sensor are at a beginning position and the spring is compressed the spring decompresses to push the carriage back along the second direction to move the carriage and the sensor from the beginning position to an ending position. The encoder triggers the sensor to take the ultrasonic measurements of the sample when the sensor is at predetermined positions while the sensor moves over the sample between the beginning and positions.

Abstract: Local transactions are supported by an application view instance that can switch from a stateless session bean to a stateful session bean in order to open a connection for a local transaction. The state that the stateful session bean holds is ten the connection. The stateful session bean can hold the connection open across multiple requests in the local transaction interface allows a user to manage the transaction in the application view, and to switch the application view between a stateless session bean and a stateful session bean. A local transaction interface can contain a local transaction management contract, which enables an application server to provide an infrastructure and run-time environment for management of the transaction.

Abstract: Systems that use application view components to allow a user to exploit functionality in an EIS can utilize a shareable connection factory. Instead of having a connection factory for each application view, a single connection factory can be used that is simply referenced by each application view. Users can then choose to associate an application view with any available connection factory on the system, or can choose to create a new connection factory that can be available to any other application view or resource adapter.

Abstract: An adapter can be deployed into a system in a single step without recycle. An adapter can contain components, such as an integration adapter, event router, and resource adapter, which all conform to a given specification such that these components use some of the same classes. A class loader allows these components to share common classes, instead of having separate classes. A single Enterprise archive file contains files necessary to deploy the adapter, such as Web archive files, resource adapter archive files, event router Web application files, and shared Java archive files. The inclusion of these files in an Enterprise archive file allows all components for the adapter to be deployed in a single step without the need to recycle. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Abstract: A system for ultrasonic profiling of a weld sample includes a carriage movable in opposite first and second directions. An ultrasonic sensor is coupled to the carriage to move over the sample as the carriage moves. An encoder determines the position of the carriage to determine the position of the sensor. A spring is connected at one end of the carriage. Upon the carriage being moved in the first direction toward the spring such that the carriage and the sensor are at a beginning position and the spring is compressed the spring decompresses to push the carriage back along the second direction to move the carriage and the sensor from the beginning position to an ending position. The encoder triggers the sensor to take the ultrasonic measurements of the sample when the sensor is at predetermined positions while the sensor moves over the sample between the beginning and positions.

Abstract: Highly-available processing of an asynchronous request can be accomplished in a single transaction. A distributed request queue receives a service request from a client application or application view client. A service processor is deployed on each node of a cluster containing the distributed request queue. A service processor pulls the service request from the request queue and invokes the service for the request, such as to an enterprise information system. If that service processor fails, another service processor in the cluster can service the request. The service processor receives a service response from the invoked service and forwards the service response to a distributed response queue. The distributed response queue holds the service response until the response is retrieved for the client application.

Abstract: An integration component such as an application integration engine can be bundled as a single, self-contained J2EE Enterprise archive (EAR) file. The bundling of the component into an EAR file enables the component to be deployed to any valid system domain that is running and available. A recycling of the server then may be necessary only if a Java archive file is added to the classpath for non-system domains. This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Abstract: A vision system for a vehicle includes a light source generating an illumination beam, a receiver having a pixel array for capturing an image in response to at least a reflected portion of the illumination beam, the image corresponding to a first horizontal field of view (FOV) angle, and a controller coupled to the light source and the receiver. The controller receives a vehicle speed input and, in response, selects a portion of the image as a non-linear function of the vehicle speed to generate a second horizontal FOV angle for displaying to the vehicle operator. The displayed angular FOV decreases, non-linearly, as the vehicle speed increases.

Abstract: A vision system for a vehicle includes a light source generating an illumination beam, a receiver having a pixel array for capturing an image in response to at least a reflected portion of the illumination beam, the image corresponding to a first horizontal field of view (FOV) angle, and a controller coupled to the light source and the receiver. The controller receives a vehicle speed input and, in response, selects a portion of the image as a non-linear function of the vehicle speed to generate a second horizontal FOV angle for displaying to the vehicle operator. The displayed angular FOV decreases, non-linearly, as the vehicle speed increases.

Abstract: Systems that use application view components to allow a user to exploit functionality in an EIS can utilize a shareable connection factory. Instead of having a connection factory for each application view, a single connection factory can be used that is simply referenced by each application view. Users can then choose to associate an application view with any available connection factory on the system, or can choose to create a new connection factory that can be available to any other application view or resource adapter.

Abstract: Local transactions are supported by an application view instance that can switch from a stateless session bean to a stateful session bean in order to open a connection for a local transaction. The state that the stateful session bean holds is then the connection. The stateful session bean can hold the connection open across multiple requests in the local transaction for the duration of the transaction. A local transaction interface allows a user to manage the transaction in the application view, and to switch the application view between a stateless session bean and a stateful session bean. A local transaction interface can contain a local transaction management contract, which enables an application server to provide an infrastructure and run-time environment for management of the transaction.

Abstract: An integration component such as an application integration engine can be bundled as a single, self-contained J2EE Enterprise archive (EAR) file. The bundling of the component into an EAR file enables the component to be deployed to any valid system domain that is running and available. A recycling of the server then may be necessary only if a Java archive file is added to the classpath for non-system domains.

Abstract: An adapter can be deployed into a system in a single step without recycle. An adapter can contain components, such as an integration adapter, event router, and resource adapter, which all conform to a given specification such that these components use some of the same classes. A class loader allows these components to share common classes, instead of having separate classes. A single Enterprise archive file contains files necessary to deploy the adapter, such as Web archive files, resource adapter archive files, event router Web application files, and shared Java archive files. The inclusion of these files in an Enterprise archive file allows all components for the adapter to be deployed in a single step without the need to recycle.

Abstract: A method of using an amorphous carbon-based coating to extend the operating life of a fuel injector having a needle operating within a valve body, the valve body, the valve and body having steel surfaces subject to repeated impact and sliding friction contact over the operating life of the injector. The method comprises (a) providing the steel surfaces of at least one of the needle and body with an ion implanted stabilized amorphous carbon-based coating in a thickness of 1-10 micrometers, the coating having low internal stresses and low coefficient of friction independent of humidity and being stabilized by the presence of up to 30% by weight of carbide forming material selected from the group of silicon, titanium and tungsten, and (b) repeatedly and rapidly actuating the fuel injector in time periods of 0.5-1.