CPC H04L 51/214 (2022.05) [E21B 47/12 (2013.01); H04L 41/16 (2013.01); H04L 51/18 (2013.01); H04L 51/226 (2022.05)] | 17 Claims |
1. A method for managing notifications and tasks in a subterranean drilling, exploration, or production system, the method comprising:
receiving, at a message processor, a first event described by a first message from a publisher in a network environment, wherein:
the first message comprises an API request from the publisher,
the API request includes a security token,
the API request relates to a topic stored in the security token,
the topic is at least one of an identifier, a keyword, or a phrase describing an event related to subterranean drilling, exploration, or production, and
the publisher is at least one of a catalog and consumption management module (CCM) software, a production operations (ProdOps) software, a field development planning (FDPlan) software, or a well construction planning (DrillPlan) software;
extracting the topic from the first message by parsing the security token to identify a subject of the security token;
selecting, by the message processor using a subscription data store and further using the topic, a listener channel to which the first message is to be sent, wherein:
the listener channel is selected from among a plurality of listener channels based on the topic,
and the listener channel comprises a logical connection between the publisher and at least one of a plurality of subscribers comprising software applications that automatically use the first message;
receiving, at the listener channel, the first event described by the first message, wherein the first event comprises an action or occurrence automatically generated by the publisher;
determining, based on the topic, a first subscriber of the listener channel from among the plurality of subscribers, wherein the first subscriber subscribes to electronic communications that are associated with the topic;
determining, using a first delivery preference of the first subscriber, a priority level of the first event, and a first interaction type of a plurality of interaction types, a first adapter to deliver the first message,
wherein the first adapter is selected from among a plurality of adapters, and
wherein the plurality of adapters comprise different software applications usable to deliver the first message;
dispatching, via the first adapter, the first message to the first subscriber, wherein the first message includes an actionable notification, and wherein the actionable notification uses a framework to translate events into tasks; and
upon receiving, by the first subscriber, the actionable notification, triggering the first subscriber to perform at least one of the tasks.
|