Abstract: In an example embodiment, a new solution is provided for an in-memory database provided in a cloud as a service that enables “job cross running” instead of “parallel job running.” Specifically, job scripts are clustered based on a shared service. A primary job script in the cluster is compiled and executed, but secondary job scripts in the cluster are not compiled until after the execution of the primary job script has begun. A mock library is inserted into each of the secondary job scripts to cause service calls for the shared service in the secondary job scripts to be replaced with mock service calls. The secondary job scripts are then scheduled and executed, and upon completion the primary job script is permitted to delete the shared service.

Abstract: In an example embodiment, a solution is used to provide for a highly efficient image dispatch system for container-based in-memory databases in a database-as-a-service framework that provides storage and bandwidth cost savings and introduces advanced features of container techniques. This solution makes best use of the advantages of the concurrent and distributed capabilities of in-memory databases in a database-as-a-service framework. A container operator manager provides operators for various uses, such as the “diff” operator and the “merge” operator. A dispatch manager acts as a centralized service for diff content maintenance, patch publication and management of dispatch worker nodes. A patch worker on each node has the capabilities to execute the specified patching and validation between the images located on each side of the in-memory database in the database-as-a-service framework.

Abstract: In an example embodiment, a new solution is provided for an in-memory database provided in a cloud as a service that enables “job cross running” instead of “parallel job running.” Specifically, job scripts are clustered based on a shared service. A primary job script in the cluster is compiled and executed, but secondary job scripts in the cluster are not compiled until after the execution of the primary job script has begun. A mock library is inserted into each of the secondary job scripts to cause service calls for the shared service in the secondary job scripts to be replaced with mock service calls. The secondary job scripts are then scheduled and executed, and upon completion the primary job script is permitted to delete the shared service.

Abstract: In an example embodiment, a solution is used to provide for multiple and concurrent web application accessing of a database in a database-as-a-service (DBaaS) framework. More particularly, a cloud solution is provided on a DBaaS for leveraging Docker network functionality to provide a virtual Internet Protocol (IP) address pool, while utilizing in-memory database technology to set up an entire accessing solution for multiple and concurrent DBaaS users and web applications, which serve the data-intensive jobs to the in-memory database. This allows for improved functionality, performance, concurrency, and handling of network stress.

Abstract: In an example embodiment, a solution is used to provide for multiple and concurrent web application accessing of a database in a database-as-a-service (DBaaS) framework. More particularly, a cloud solution is provided on a DBaaS for leveraging Docker network functionality to provide a virtual Internet Protocol (IP) address pool, while utilizing in-memory database technology to set up an entire accessing solution for multiple and concurrent DBaaS users and web applications, which serve the data-intensive jobs to the in-memory database. This allows for improved functionality, performance, concurrency, and handling of network stress.

Abstract: The present disclosure relates to systems and methods for connecting to a wireless network. The methods may include obtaining, within a dwell time, at least one packet transmitting on a current channel among a plurality of predetermined channels, wherein the plurality of predetermined channels at least include a target channel on which a connection to the wireless network is to be established; determining a matching score of the current channel based on the at least one packet, wherein the matching score reflects a likelihood that the current channel is the target channel; and determining, based on the matching score, an additional dwell time for continuing dwelling on the current channel to further evaluate the likelihood that the current channel is the target channel.

Abstract: In an example embodiment, a hardware mechanism for protecting user-level software from privileged system software is leveraged to protect in-memory databases in container implementations in a cloud. This hardware mechanism takes the form of an enclave. An enclave is a portion of a CPU that shields application code and data from accesses by other software, including higher-privileged software. Memory pages belonging to an enclave reside in the enclave page cache (EPC), which cannot be accessed by code outside of the enclave. This helps ensure that (1) applications built on top of in-memory database are securely trusted, (2) and a trusted path architecture is provided for enclaves allowing in-memory databases to run securely on top of untrusted cloud platform.

Abstract: In an example embodiment, a hardware mechanism for protecting user-level software from privileged system software is leveraged to protect in-memory databases in container implementations in a cloud. This hardware mechanism takes the form of an enclave. An enclave is a portion of a CPU that shields application code and data from accesses by other software, including higher-privileged software. Memory pages belonging to an enclave reside in the enclave page cache (EPC), which cannot be accessed by code outside of the enclave. This helps ensure that (1) applications built on top of in-memory database are securely trusted, (2) and a trusted path architecture is provided for enclaves allowing in-memory databases to run securely on top of untrusted cloud platform.

Abstract: In an example embodiment, a hardware mechanism for protecting user-level software from privileged system software is leveraged to protect in-memory databases in container implementations in a cloud. This hardware mechanism takes the form of an enclave. An enclave is a portion of a CPU that shields application code and data from accesses by other software, including higher-privileged software. Memory pages belonging to an enclave reside in the enclave page cache (EPC), which cannot be accessed by code outside of the enclave. This helps ensure that (1) applications built on top of in-memory database are securely trusted, (2) and a trusted path architecture is provided for enclaves allowing in-memory databases to run securely on top of untrusted cloud platform.

Abstract: In an example embodiment, a new solution is provided for an in-memory database provided in a cloud as a service that enables “job cross running” instead of “parallel job running.” Specifically, job scripts are clustered based on a shared service. A primary job script in the cluster is compiled and executed, but secondary job scripts in the cluster are not compiled until after the execution of the primary job script has begun. A mock library is inserted into each of the secondary job scripts to cause service calls for the shared service in the secondary job scripts to be replaced with mock service calls. The secondary job scripts are then scheduled and executed, and upon completion the primary job script is permitted to delete the shared service.

Abstract: The invention provides a cathode for the nitrogen reduction reaction, comprising an electrically conductive substrate and an electrocatalytic composition on the substrate, wherein the electrocatalytic composition comprises: a support material present in one or more crystalline phases; and metallic clusters dispersed on the support material, the metallic clusters comprising at least one metal selected from ruthenium, iron, rhodium, iridium and molybdenum, wherein at least 80 mass % of the support material is present in a semiconductive crystalline phase having a conduction band minimum energy below (more positive than) ?0.3 V relative to the normal hydrogen electrode (NHE).

Abstract: This disclosure describes a trace debugger (TDB) that is used for database workload replay and database debugging. The TDB maintains consistency through synchronization of the state between the database and a corresponding database trace replay. The TDB can provide a sliding window environment for code block execution and global context sharing. The TDB can be used to interactively analyze and troubleshoot various types of database problems by debugging the database itself, query code (e.g., SQL), performance, end-to-end execution, and plan traces, which can be recorded using scripts. In some implementations, the TDB also provides reverse debugging for historical database state analysis, and/or incremental debugging for dynamic editing and debugging within a session without the need to exit the debugger and perform a full rebuild of the code.

Abstract: In an example embodiment, a solution is used to provide container volume replication via a container storage replication log and volume buffer synchronization, which is built on top of a container cloud platform whose container metadata and replication runtime configuration are all managed by a storage manager (a service orchestrated by its job scheduler and service orchestrator). This container volume replication ensures the data security for a long-running service in the container. In the case of any disaster, the in-memory database and application data inside of the container can be recovered via volume replication. This provides container volume replication for long-running containerized applications whose states keep changing.

Abstract: In an example embodiment, a solution is used to provide container volume replication via a container storage replication log and volume buffer synchronization, which is built on top of a container cloud platform whose container metadata and replication runtime configuration are all managed by a storage manager (a service orchestrated by its job scheduler and service orchestrator). This container volume replication ensures the data security for a long-running service in the container. In the case of any disaster, the in-memory database and application data inside of the container can be recovered via volume replication. This provides container volume replication for long-running containerized applications whose states keep changing.

Abstract: In an example embodiment, a solution is used to provide for a highly efficient image dispatch system for container-based in-memory databases in a database-as-a-service framework that provides storage and bandwidth cost savings and introduces advanced features of container techniques. This solution makes best use of the advantages of the concurrent and distributed capabilities of in-memory databases in a database-as-a-service framework. A container operator manager provides operators for various uses, such as the “diff” operator and the “merge” operator. A dispatch manager acts as a centralized service for diff content maintenance, patch publication and management of dispatch worker nodes. A patch worker on each node has the capabilities to execute the specified patching and validation between the images located on each side of the in-memory database in the database-as-a-service framework.

Abstract: In an example embodiment, a solution is used to provide for multiple and concurrent web application accessing of a database in a database-as-a-service (DBaaS) framework. More particularly, a cloud solution is provided on a DBaaS for leveraging Docker network functionality to provide a virtual Internet Protocol (IP) address pool, while utilizing in-memory database technology to set up an entire accessing solution for multiple and concurrent DBaaS users and web applications, which serve the data-intensive jobs to the in-memory database. This allows for improved functionality, performance, concurrency, and handling of network stress.

Abstract: Disclosed is a framework for providing microservices for database with embedded container service in a container cloud platform. The framework includes a container cloud manager for performing distributed management of resources in a data center. The container cloud manager includes an orchestrator with a flexible job scheduler and operator pool. The flexible job scheduler and container cloud master form a flexible job management platform for managing jobs of the data center. The flexible job management framework can isolate various types of jobs as well as mix various jobs for efficient usage of hosts or resources in the data center. The operator pool includes optional components of a database. The orchestrator facilitates quick customization and release of database products, such as a HANA database with optional services, as requested by a user in the container cloud platform.

Abstract: In an example embodiment, a solution is used to provide container volume replication via a container storage replication log and volume buffer synchronization, which is built on top of a container cloud platform whose container metadata and replication runtime configuration are all managed by a storage manager (a service orchestrated by its job scheduler and service orchestrator). This container volume replication ensures the data security for a long-running service in the container. In the case of any disaster, the in-memory database and application data inside of the container can be recovered via volume replication. This provides container volume replication for long-running containerized applications whose states keep changing.

Abstract: Disclosure is a framework for providing microservices for database with embedded container service in a container cloud platform. The framework includes a container cloud manager for performing distributed management of resources in a data center. The container cloud manager includes an orchestrator with a flexible job scheduler and operator pool. The flexible job scheduler and container cloud master form a flexible job management platform for managing jobs of the data center. The flexible job management framework can isolate various types of jobs as well as mix various jobs for efficient usage of hosts or resources in the data center. The operator pool includes optional components of a database. The orchestrator facilitates quick customization and release of database products, such as HANA database with optional services, as requested by a user in the container cloud platform.

Abstract: This invention relates to a movable article inspection system and inspection method, wherein the inspection system comprises: a first automated guided vehicle, a radiation source and a detection mechanism; said radiation source and said detection mechanism are both mounted on said first automated guided vehicle, said first automated guided vehicle is able to move to a preset scanning inspection position, such that scanning inspection of said article to be scanned is effectuated by means of relative movement between an article to be scanned and the first automated guided vehicle. Such movable inspection system based on an automated guided vehicle is capable of making full use of an existing automated guided vehicle and its control system to make a movement path of the inspection system more flexible, and capable of effectuating centralized control and management of the inspection system, so that it can improve inspection efficiency, and save labor cost.