Abstract: Described herein are systems and methods for managing releases of global services in a controlled manner. A computing environment may include a first release of a global service, a second release of the global service, and a manager service. The first and second release may be enabled and disabled. The first release may be enabled and the second release may be disabled. The second release may be ready for use in the computing environment after passing one or more checks. A manager service may enable use of the second release in the computing environment. The manager service may disable use of (but maintain execution of) the first release in the computing environment. The second release may be determined to have one or more issues. Responsive to determining the second release has issue(s), the manager service may disable use of the second release and re-enable use of the first release.

Abstract: Described embodiments provide systems and methods for hosting multiple cloud-based services at a common network address. The systems and methods receive a request addressed to a uniform resource identifier (“URI”) including a domain name that is one of a plurality of different domain names mapped to a common network address. The systems and methods identify each of a service name and a controller name embedded in the URI, and identify a controller service instance using the service name and controller name from the URI, from a mapping of a plurality of controller server instances to respective service names and controller names. The systems and methods invoke an interface to the identified service instance, and pass data from the received request to the identified service instance via the interface.

Abstract: Described embodiments provide systems and methods for routing service requests. The system includes a first network of computing devices including a server hosting a service. The system includes a release router in the first network, the release router configured to receive a request for the service, the request forwarded to the release router responsive to resolving a hostname specified in the request using a DNS mapping the hostname to the release router, the hostname associated with the service hosted by the server. The release router is configured to identify a relay agent registered with the release router for debugging the service, the relay agent executed by a test platform in a second network, and to forward the request to the test platform in the second network, wherein the test platform resolves the hostname specified in the request using a local DNS mapping the hostname to a localhost address.

Abstract: A technique for managing a read cache in an eventually-consistent data store includes, in response to a read request for a specified data element, receiving the specified data element from the read cache as well as a remaining TTL (time to live) of the data element, as indicated by a timer for that data element in the read cache. If the remaining TTL falls below a predetermined value, the technique triggers an early refresh of the specified data element, prior to its expiration. Consequently, later-arriving read requests to the same data element that arrive before the data element has been refreshed experience cache hits, thus avoiding the need to perform their own time-consuming refresh operations.

Abstract: Methods and systems for routing a user request for a service to a version of the service in a geographical region associated with the user are described herein. The service may be deployed in multiple geographical regions, and the service may have multiple versions in each of the geographical regions. A user device may send a request for a service to a first server in a geographical region. The first server may determine whether the user is associated with the geographical region. Responsive to determining that the user is not associated with the geographical region, the first server may ask one or more servers in other geographical regions whether the user is associated with any of the other geographical regions.

Abstract: Methods, systems, and non-transitory computer-readable media are described herein. In some embodiments, a computing platform may deploy a cloud application comprising a first instance of the cloud application. Further, the computing platform may direct a DNS to the first instance of the cloud application. Next, the computing platform may determine that a second instance of the cloud application should be deployed. Additionally, the computing platform may create a first global traffic manager configured with at least a first endpoint and a second endpoint, where the first endpoint is associated with the first instance and is enabled, and where the second endpoint is associated with the second instance, and is disabled. Subsequently, the computing platform may direct the DNS to the first global traffic manager. The computing platform may then direct the DNS to the first global traffic manager, enable the second endpoint.

Abstract: A method, system and computer program product are provided. A computing system collects information related to a patient's preparation for a medical procedure and provides information regarding the medical procedure and a medical condition of the patient to at least one member of a medical procedure team. Data pertaining to performance of the medical procedure in an operating room is collected from multiple sensors. Progress of the medical procedure is monitored in real time by analyzing the collected data, a procedure reference library, and a physician history to determine a status of the medical procedure. A schedule of one or more subsequent medical procedures for the operating room is adjusted in real time based on the monitored progress. Notifications of the adjusted schedule may be transmitted to participants of the one or more subsequent medical procedures.

Abstract: Described embodiments provide systems and methods for routing service requests. The system includes a first network of computing devices including a server hosting a service. The system includes a release router in the first network, the release router configured to receive a request for the service, the request forwarded to the release router responsive to resolving a hostname specified in the request using a DNS mapping the hostname to the release router, the hostname associated with the service hosted by the server. The release router is configured to identify a relay agent registered with the release router for debugging the service, the relay agent executed by a test platform in a second network, and to forward the request to the test platform in the second network, wherein the test platform resolves the hostname specified in the request using a local DNS mapping the hostname to a localhost address.

Abstract: Described embodiments provide systems and methods for hosting multiple cloud-based services at a common network address. The systems and methods receive a request addressed to a uniform resource identifier (“URI”) including a domain name that is one of a plurality of different domain names mapped to a common network address. The systems and methods identify each of a service name and a controller name embedded in the URI, and identify a controller service instance using the service name and controller name from the URI, from a mapping of a plurality of controller server instances to respective service names and controller names. The systems and methods invoke an interface to the identified service instance, and pass data from the received request to the identified service instance via the interface.

Abstract: Described embodiments provide systems and methods for stateless modification of operating system registry data across network boundaries. The system includes a processor coupled to memory and configured to execute instructions to receive, within a first network, a request to apply a modification to an operating system registry of a second device within a second network different from the first network. The processor queues data describing the requested modification, receives a polling request from the second device, and transmits, to the second device responsive to the polling request, the queued data describing the requested modification for the second device to apply to the operating system registry of the second device. For example, the requested modification may be to create a key, to create a value, to delete a key, or to delete a value.

Abstract: Described embodiments automatically and dynamically generate and update resource templates for deployable resources, utilizing composable parts that may be dynamically replaced. Common portions of the templates may be easily defined once and reused multiple times, reducing risk of error and ensuring stability and cross-resource compatibility. Each dynamic template may have replaceable parts, as well as replaceable parameters and values within the replaceable parts, as well as in common portions of the template. The replacement properties and values may be determined at runtime or during deployment, ensuring that configurations are always current.

Abstract: Techniques for implementing a non-relational database that makes efficient use of collections within the database. For one or more collections, two or more sub-collections can be created for storing documents. Each collection can be configured as a single partition entity or a partitioned entity within the database. Each sub-collection is identified by a sub-collection identifier. If the collection is configured as a partitioned entity, then a partition key can be determined for documents to be accessed in the collection. The partition key can be extended with the sub-collection ID to form a compound property (sub-collection ID, partition key) that determines placements of the respective documents in the identified sub-collection across partitions of the collection. If the collection is configured as a single partition entity, then a field for the partition key is ignored and the respective documents are placed in the identified sub-collection within the single partition of the collection.

Abstract: The present disclosure includes a combination sensor and pressure relief valve. The combination sensor and valve may be used with existing aircraft wheel systems. Wheel systems utilizing the combination sensor and valve are also disclosed.

Abstract: What is described is a tire pressure sensor for use in a wheel of aircraft landing gear. The tire pressure sensor includes a position sensor configured to detect a movement of the wheel and generate a wheel movement signal based on the movement. The tire pressure sensor also includes a processor coupled to the position sensor. The processor is configured to receive the wheel movement signal, determine a wheel rotational speed of the wheel based on the wheel movement signal and generate a wheel rotational speed signal based on the wheel rotational speed.

Abstract: A wheel monitoring system comprising a wheel, a bearing mechanically coupled to the wheel, an axle mechanically coupled to the bearing, and a wheel speed transducer (WST) disposed in the axle. The WST may be configured to detect vibrations. A method of monitoring a bearing is also provided and may comprise measuring a vibration of the bearing, comparing the vibration of the bearing to a predetermined vibration, and estimating a remaining useful life of the bearing.

Abstract: A connector assembly includes a first side connector and a second side connector. The first side connector includes a first protective housing, a first inductor including a first end face, and a first physical connector element. The second side connector includes a second protective housing, a second inductor including a second face, and a second physical connector element. The second physical connector element is engaged with the first physical connector element and physically connects the first side connector to the second side connector such that the first end face and the second end face are adjacent. The first inductor and the second inductor are axially spaced apart. The first inductor and the second inductor form an inductive telemetry connection between the first side connector and the second side connector.

Abstract: A handheld interrogation device includes a controller configured to generate a power signal. The controller is also configured to determine tire pressure data based on a signal received from a tire pressure sensor. The handheld interrogation device also includes a primary coil coupled to the handheld interrogation device and configured to transmit the power signal to a sensor coil of the tire pressure sensor and to receive a data signal from the sensor coil, via inductive coupling, in response to the primary coil being within a predetermined distance of the sensor coil.

Abstract: A handheld interrogation device includes a controller configured to generate a power signal. The controller is also configured to determine tire pressure data based on a signal received from a tire pressure sensor. The handheld interrogation device also includes a primary coil coupled to the handheld interrogation device and configured to transmit the power signal to a sensor coil of the tire pressure sensor and to receive a data signal from the sensor coil, via inductive coupling, in response to the primary coil being within a predetermined distance of the sensor coil.

Abstract: A wheel monitoring system comprising a wheel, a bearing mechanically coupled to the wheel, an axle mechanically coupled to the bearing, and a wheel speed transducer (WST) disposed in the axle. The WST may be configured to detect vibrations. A method of monitoring a bearing is also provided and may comprise measuring a vibration of the bearing, comparing the vibration of the bearing to a predetermined vibration, and estimating a remaining useful life of the bearing.

Abstract: What is described is a tire pressure sensor for use in a wheel of aircraft landing gear. The tire pressure sensor includes a position sensor configured to detect a movement of the wheel and generate a wheel movement signal based on the movement. The tire pressure sensor also includes a processor coupled to the position sensor. The processor is configured to receive the wheel movement signal, determine a wheel rotational speed of the wheel based on the wheel movement signal and generate a wheel rotational speed signal based on the wheel rotational speed.