Abstract: A system comprising a first expired drug usability device is provided. The first expired drug usability device comprises a first spectrometer and one or more first processors. The first processors are configured to: obtain at least one expired drug machine learning-artificial intelligence (ML-AI) model associated with a pharmaceutical drug; obtain drug expiration information of a sample of the pharmaceutical drug, wherein the drug expiration information comprises spectrometer data associated with using the first spectrometer on the sample; input the drug expiration information into the at least one expired drug ML-AI model to determine usability information associated with the sample of the pharmaceutical drug; and perform one or more actions based on the usability information.

Abstract: In a transaction between a merchant and a payer, approval of the transaction may be provided by a payment processing system using authentication information provided from a mobile device of the payer. The authentication information may include a location of the payer mobile device which may be compared to a location of a merchant payment device such that the transaction is approved if the payer mobile device is within a defined distance of the merchant payment device.

Abstract: Mobile agents can be deployed to mobile devices within specific regions of interest to achieve specific goals in respect of events occurring in the region of interest. In order to ensure that the agent can persist within the region of interest until the agent goals are achieved, the agent is configured to locate other devices within the region of interest and to propagate itself, by moving or copying itself, to those other devices. The region of interest may be a mobile and/or dynamic region of interest defined by, for example, a proximity to one or more mobile wireless access points or by an overlapping peer-to-peer communication range of a plurality of mobile devices that are configured to support the agent.

Abstract: In a transaction between a merchant and a payer, approval of the transaction may be provided by a payment processing system using authentication information provided from a mobile device of the payer. The authentication information may include a location of the payer mobile device which may be compared to a location of a merchant payment device such that the transaction is approved if the payer mobile device is within a defined distance of the merchant payment device.

Abstract: In order to enable a dynamic handshake procedure, a device may be configured with a list of handshake contributors. Contributors with connection handshake properties may be added to the contributor list. To perform handshake, the contributor list is processed to extract the connection handshake properties of each contributor to the handshake. Handlers for handling the connection handshake properties may also be dynamically added and invoked when a handshake is received.

Abstract: In order to enable a dynamic handshake procedure, a device may be configured with a list of handshake contributors. Contributors with connection handshake properties may be added to the contributor list. To perform handshake, the contributor list is processed to extract the connection handshake properties of each contributor to the handshake. Handlers for handling the connection handshake properties may also be dynamically added and invoked when a handshake is received.

Abstract: In a transaction between a merchant and a payer, approval of the transaction may be provided by a payment processing system using authentication information provided from a mobile device of the payer. The authentication information may include a location of the payer mobile device which may be compared to a location of a merchant payment device such that the transaction is approved if the payer mobile device is within a defined distance of the merchant payment device.

Abstract: Mobile agents can be deployed to mobile devices within specific regions of interest to achieve specific goals in respect of events occurring in the region of interest. In order to ensure that the agent can persist within the region of interest until the agent goals are achieved, the agent is configured to locate other devices within the region of interest and to propagate itself, by moving or copying itself, to those other devices. The region of interest may be a mobile and/or dynamic region of interest defined by, for example, a proximity to one or more mobile wireless access points or by an overlapping peer-to-peer communication range of a plurality of mobile devices that are configured to support the agent.

Abstract: In order to determine the location of wireless network devices without inherent location capabilities, a wireless network device such as an access point can receive geolocation information from transient data sources such as mobile devices requiring network access from the access point. The access point stores geolocation records including location coordinates received from the transient data sources. The geolocation records can be processed to determine the position and movement of the access point. The geolocation records and/or location information can be passed to other transient clients that do not have inherent location capability.

Abstract: In developing applications for a plurality of node types, a meta-data definition of the application can be captured into an application definition module. The meta-data definition can describe the application for the plurality of node types. A code generation module can then automatically generate the application code for the plurality of node types. The code can be compiled per node type and the packaging necessary to deploy the application to the plurality of node types can also be automatically generated.

Abstract: In order to enable a dynamic handshake procedure, a device may be configured with a list of handshake contributors. Contributors with connection handshake properties may be added to the contributor list. To perform handshake, the contributor list is processed to extract the connection handshake properties of each contributor to the handshake. Handlers for handling the connection handshake properties may also be dynamically added and invoked when a handshake is received.

Abstract: In order to enable a dynamic handshake procedure, a client device is configured with a list of handshake contributors. The client device initiates a handshake by determining the handshake contributors and writing properties of the handshake contributors in a client handshake, which is then sent to a server device. The client handshake is processed at the server device by invoking an appropriate handler, which handles the handshake result. The server can also send its contributors and their properties to the client. Once the client receives the properties, the client can call an appropriate handler to handle the properties. Connections may be created based on the exchanged properties. New contributors and contributor handlers may be added to both the client and server devices.

Abstract: In order to determine the location of wireless network devices without inherent location capabilities, a wireless network device such as an access point can receive geolocation information from transient data sources such as mobile devices requiring network access from the access point. The access point stores geolocation records including location coordinates received from the transient data sources. The geolocation records can be processed to determine the position and movement of the access point. The geolocation records and/or location information can be passed to other transient clients that do not have inherent location capability.

Abstract: In a distributed object computing system, a server application may create multiple, uniquely identified, server contexts that each provide one or more services to a service consumer (client). Instead of creating a connection to a client for each server context, a single connection can be used. A service request handler may be configured to handle service requests for each server context. Service requests may be generated in the client with a service context identity. When a service request is received by the server application, the service request handler resolves the service context identity and forwards the service request to the appropriate server context.

Abstract: In distributed object computing, messages from a source node to a destination node are often required to be routed via one or more intermediate nodes. In order to enhance efficiency of the relay process, a message envelope of a message may include a node list field that specifies the routing path of the message. The communication protocol for communicating the message may specify that when a message is received into a particular node, the node analyzes the node list field. If the identity of the node is last in the node list field, then the node is the destination node and thus the node unmarshals the message. Otherwise, the node forwards the message to the next node in the field list without unmarshalling the message.

Abstract: Mobile agents can be deployed to mobile devices within specific regions of interest to achieve specific goals in respect of events occurring in the region of interest. In order to ensure that the agent can persist within the region of interest until the agent goals are achieved, the agent is configured to locate other devices within the region of interest and to propagate itself, by moving or copying itself, to those other devices. The region of interest may be a mobile and/or dynamic region of interest defined by, for example, a proximity to one or more mobile wireless access points or by an overlapping peer-to-peer communication range of a plurality of mobile devices that are configured to support the agent.

Abstract: In developing applications for a plurality of node types, a meta-data definition of the application can be captured into an application definition module. The meta-data definition can describe the application for the plurality of node types. A code generation module can then automatically generate the application code for the plurality of node types, including transaction aware code. The code can be compiled per node type and the packaging necessary to deploy the application to the plurality of node types can also be automatically generated.

Abstract: In developing applications for a plurality of node types, a meta-data definition of the application can be captured into an application definition module. The meta-data definition can describe the application for the plurality of node types. A code generation module can then automatically generate the application code for the plurality of node types. The code can be compiled per node type and the packaging necessary to deploy the application to the plurality of node types can also be automatically generated.

Abstract: Mobile agents can be deployed to location aware mobile devices within specific regions of interest to achieve specific goals in respect of events occurring in the region of interest. In order to ensure that the agent can persist within the region of interest until the agent goals are achieved, the agent is configured to locate other devices within the region of interest and to propagate itself, by moving or copying itself, to those other devices. When a device hosting the agent exits the region of interest, the agent is terminated, thereby freeing device resources.

Abstract: Mobile agents can be deployed to location aware mobile devices within specific regions of interest to achieve specific goals in respect of events occurring in the region of interest. In order to ensure that the agent can persist within the region of interest until the agent goals are achieved, the agent is configured to locate other devices within the region of interest and to propagate itself, by moving or copying itself, to those other devices. When a device hosting the agent exits the region of interest, the agent is terminated, thereby freeing device resources.