The disclosure details a computer program enabling parties to litigation to produce a questionnaire through an internet-based website and enabling jurors to respond to the questionnaire through such website. The program comprises numerous code sequences that assist the court, a court reporter, the parties to litigation (and counsel), and the judge in the process of selecting and empaneling jurors from a plurality of candidates.

The disclosure details a computer program enabling parties to litigation to produce a questionnaire through an internet-based website and enabling jurors to respond to the questionnaire through such website. The program comprises numerous code sequences that assist the court, a court reporter, the parties to litigation (and counsel), and the judge in the process of selecting and empaneling jurors from a plurality of candidates.

Some embodiments provide a set of one or more network controllers that communicates with a wide range of devices, ranging from switches to appliances such as firewalls, load balancers, etc. The set of network controllers communicates with such devices to connect them to its managed virtual networks. The set of network controllers can define each virtual network through software switches and/or software appliances. To extend the control beyond software network elements, some embodiments implement a database server on each dedicated hardware. The set of network controllers accesses the database server to send management data. The hardware then translates the management data to connect to a managed virtual network.

The present disclosure relates to intent execution methods and apparatus. In one example method, an element management system (EMS) receives a first intent from a network management system (NMS). The first intent indicates the EMS to execute a first command on a first network element and execute a second command on a second network element, a second intent in an active state is maintained in the EMS, the second intent indicates the EMS to execute a third command on the first network element, and the first command and the third command are mutually exclusive. The EMS receives a first parameter and conflict policy information. The EMS determines whether to execute the second command on the second network element, and executes the first command or the third command on the first network element based on the conflict policy information.

The present disclosure relates to intent execution methods and apparatus. In one example method, an element management system (EMS) receives a first intent from a network management system (NMS). The first intent indicates the EMS to execute a first command on a first network element and execute a second command on a second network element, a second intent in an active state is maintained in the EMS, the second intent indicates the EMS to execute a third command on the first network element, and the first command and the third command are mutually exclusive. The EMS receives a first parameter and conflict policy information. The EMS determines whether to execute the second command on the second network element, and executes the first command or the third command on the first network element based on the conflict policy information.

A method for handling hacker intrusion in NF profile management at an NRF includes receiving, at the NRF and from a consumer NF, an NF register request message including an NF profile of the consumer NF, setting and storing an NF profile version number for the NF profile, and communicating the NF profile version number to the consumer NF. The consumer NF stores the NF profile version number and transmits a request for initiating an NF update or NF heart-beat service operation to the NRF. The NRF receives the request for initiating the NF update or NF heart-beat service operation, increments the NF profile version number, and communicates the incremented NF profile version number to the consumer NF. The consumer NF receives the incremented NF profile version number, determines that an NF profile version mismatch has occurred, and, in response, initiates an NF profile corrective action with the NRF.

A method for handling hacker intrusion in NF profile management at an NRF includes receiving, at the NRF and from a consumer NF, an NF register request message including an NF profile of the consumer NF, setting and storing an NF profile version number for the NF profile, and communicating the NF profile version number to the consumer NF. The consumer NF stores the NF profile version number and transmits a request for initiating an NF update or NF heart-beat service operation to the NRF. The NRF receives the request for initiating the NF update or NF heart-beat service operation, increments the NF profile version number, and communicates the incremented NF profile version number to the consumer NF. The consumer NF receives the incremented NF profile version number, determines that an NF profile version mismatch has occurred, and, in response, initiates an NF profile corrective action with the NRF.

In one embodiment, a service receives administration traffic data in a network associated with a remote administration session in which a control device remotely administers a client device. The service analyzes the administration traffic data to determine whether any portion of the administration traffic data is resulting from an administration session involving a trusted administrator. The service flags a first portion of the administration traffic data as authorized when the first portion of the administration traffic data is determined to result from an administration session involving a trusted administrator, and a second portion of the administration traffic data is non-flagged. The service assesses the second portion of the administration traffic data using a machine learning-based traffic classifier to determine whether the second portion of the administration traffic data is malicious.

In one embodiment, a service receives administration traffic data in a network associated with a remote administration session in which a control device remotely administers a client device. The service analyzes the administration traffic data to determine whether any portion of the administration traffic data is resulting from an administration session involving a trusted administrator. The service flags a first portion of the administration traffic data as authorized when the first portion of the administration traffic data is determined to result from an administration session involving a trusted administrator, and a second portion of the administration traffic data is non-flagged. The service assesses the second portion of the administration traffic data using a machine learning-based traffic classifier to determine whether the second portion of the administration traffic data is malicious.

A distributed security system can include instances of a compute engine that can execute either locally in security agents on client devices or as cloud instances in a security network. Event data can be processed by elements of the distributed security system according to centrally-defined ontological definitions and/or configurations. Bounding managers of local security agents can control how much event data is sent to the security network. A storage engine in the security network can store event data received from client devices, can route event data to other elements of the security network, including cloud instances of the compute engine. An experimentation engine of the security network can also at least temporarily adjust other elements of the distributed security system during experiments or tests.