Abstract: A processing system may obtain a request from a user device to activate an access credential locker for use in accessing at least one enterprise system of an enterprise via the processing system, the request comprising a token that identifies the access credential locker, obtain a first key from the user device, transmit, to the enterprise, a request for a second key, obtain the second key from the enterprise in response to the request, apply the first key and the second key to the access credential locker, the access credential locker being encrypted in accordance with the first and second keys and being decrypted via the applying of the first and second keys, and establish a communication session between the user device and the at least one enterprise system via the processing system using at least one access credential that is stored in the decrypted access credential locker.

Abstract: The described technology is generally directed towards network slicing for private cellular networks (PCNs). Network slicing can be leveraged as described herein to meet security requirements and/or other policies applicable to PCNs. Network slices implemented according to this disclosure can comprise a private network slice, a public network slice, and a public safety network slice. User equipment can be provisioned with slice identifiers for the network slices, and applications at the user equipment can specify an appropriate slice identifier for their network communications. Network equipment can be configured to route application traffic to a specified slice and to allocate network resources according to the specified slice, as well as to implement security and other policies according to the specified slice.

Abstract: A mobile edge computing (MEC) service area can utilize packet header source and/or destination internet protocol data and session initiation protocol source and/or destination internet protocol data to map internet protocol addresses associated with mobile devices. The MEC can comprise a translation component that translates service provider internet protocol addresses such that they are perceived as enterprise premises internet protocol addresses. Conversely, the translation component can translate enterprise premises internet protocol addresses such that they are perceived as service provider internet protocol addresses.

Abstract: A processing system including at least one processor executing a traffic management application may detect a proximity to a traffic zone for vehicular traffic, the dual-mode vehicle having two modes of operation, the two modes of operation comprising a surface mode of operation and an aerial mode of operation, and may verify a rule set for vehicular operations within the traffic zone. The processing system may then identify a leader traffic management application from among a plurality of traffic management applications of a plurality of dual-mode vehicles within or near the traffic zone, obtain at least one navigation instruction from the leader traffic management application, and perform at least one of: executing a navigation action in accordance with the at least one navigation instruction, or displaying at least a portion of a permitted route that is in conformance with the at least one navigation instruction.

Abstract: The described technology is generally directed towards communication network application programming interface (API) promulgation. Using the techniques herein, APIs can be hosted at different locations within a network in a transitory manner, shifting from one location to the next. Furthermore, API configurations can change over time, in order to provide enhanced API security and/or to meet different expected needs of client equipment. An API manager can select network equipment to host APIs, in order to move the APIs between different network locations. A floater application within the core network can support the movement of the APIs by creating secure tunnels between the selected network equipment and the core network.

Abstract: A mobile edge computing (MEC) service area can utilized packet header source and/or destination internet protocol data and session initiation protocol source and/or destination internet protocol data to map internet protocol addresses associated with mobile devices. The MEC can comprise a translation component that translates service provider internet protocol addresses such that they are perceived as enterprise premises internet protocol addresses. Conversely, the translation component can translate enterprise premises internet protocol addresses such that they are perceived as service provider internet protocol addresses.

Abstract: A mobile edge computing (MEC) service area can utilized packet header source and/or destination internet protocol data and session initiation protocol source and/or destination internet protocol data to map internet protocol addresses associated with mobile devices. The MEC can comprise a translation component that translates service provider internet protocol addresses such that they are perceived as enterprise premises internet protocol addresses. Conversely, the translation component can translate enterprise premises internet protocol addresses such that they are perceived as service provider internet protocol addresses.

Abstract: A computer-implemented method, system, and non-transitory computer-readable medium may provide event attendees of a network-accessible calendar with a way to generate collaborative notes for a meeting related to an event. In some embodiments, a calendar entry in a network-accessible calendar may be identified. The calendar entry may correspond to an event and may identify the event attendees. A collaborative document that capable of receiving modifications to the event from the event attendees may be created. The event attendees may further be provided access to the collaborative document.

Abstract: A collaborative content management system enables users to selectively create file-level comments, in addition to content level comments, in collaborative content items. A file-level comment can be created in a number of different ways, including creating a comment associated with a title, header, heading, or other designated portion of the content; by designating a message associated with sharing the content item as a file-level comment; by replaying via a messaging system to a message sharing the content item; or by including a file-level primitive in the content of a comment. A file-level comment may be indicated in the collaborative content item by visually distinguishing formatting of a title, header or other portion of the content item. A file-level comment may be displayed in a visually distinctive manner, such as with specified formatting or in a specific window pane apart from content level comments.

Abstract: A collaborative content management system enables users to selectively create file-level comments, in addition to content level comments, in collaborative content items. A file-level comment can be created in a number of different ways, including creating a comment associated with a title, header, heading, or other designated portion of the content; by designating a message associated with sharing the content item as a file-level comment; by replaying via a messaging system to a message sharing the content item; or by including a file-level primitive in the content of a comment. A file-level comment may be indicated in the collaborative content item by visually distinguishing formatting of a title, header or other portion of the content item. A file-level comment may be displayed in a visually distinctive manner, such as with specified formatting or in a specific window pane apart from content level comments.

Abstract: A collaborative content management system enables users to selectively create file-level comments, in addition to content level comments, in collaborative content items. A file-level comment can be created in a number of different ways, including creating a comment associated with a title, header, heading, or other designated portion of the content; by designating a message associated with sharing the content item as a file-level comment; by replaying via a messaging system to a message sharing the content item; or by including a file-level primitive in the content of a comment. A file-level comment may be indicated in the collaborative content item by visually distinguishing formatting of a title, header or other portion of the content item. A file-level comment may be displayed in a visually distinctive manner, such as with specified formatting or in a specific window pane apart from content level comments.

Abstract: A collaborative content management system enables users to selectively create file-level comments, in addition to content level comments, in collaborative content items. A file-level comment can be created in a number of different ways, including creating a comment associated with a title, header, heading, or other designated portion of the content; by designating a message associated with sharing the content item as a file-level comment; by replaying via a messaging system to a message sharing the content item; or by including a file-level primitive in the content of a comment. A file-level comment may be indicated in the collaborative content item by visually distinguishing formatting of a title, header or other portion of the content item. A file-level comment may be displayed in a visually distinctive manner, such as with specified formatting or in a specific window pane apart from content level comments.

Abstract: A computer-implemented method, system, and non-transitory computer-readable medium may provide event attendees of a network-accessible calendar with a way to generate collaborative notes for a meeting related to an event. In some embodiments, a calendar entry in a network-accessible calendar may be identified. The calendar entry may correspond to an event and may identify the event attendees. A collaborative document that capable of receiving modifications to the event from the event attendees may be created. The event attendees may further be provided access to the collaborative document.

Abstract: Certain exemplary embodiments comprise a method comprising receiving, from a user-operated telecommunications device, a user-initiated communication to a non-911 communications address. The method can comprise automatically providing a user with a current location of a user-associated telecommunications device. The method can comprise requesting, from the user, verification of the current location of the user-associated telecommunications device.

Abstract: Certain exemplary embodiments comprise a method comprising receiving, from a user-operated telecommunications device, a user-initiated communication to a non-911 communications address. The method can comprise automatically providing a user with a current location of a user-associated telecommunications device. The method can comprise requesting, from the user, verification of the current location of the user-associated telecommunications device.

Abstract: Certain exemplary embodiments comprise a method comprising receiving, from a user-operated telecommunications device, a user-initiated communication to a non-911 communications address. The method can comprise automatically providing a user with a current location of a user-associated telecommunications device. The method can comprise requesting, from the user, verification of the current location of the user-associated telecommunications device.

Abstract: Certain exemplary embodiments comprise a method comprising receiving, from a user-operated telecommunications device, a user-initiated communication to a non-911 communications address. The method can comprise automatically providing a user with a current location of a user-associated telecommunications device. The method can comprise requesting, from the user, verification of the current location of the user-associated telecommunications device.

Abstract: Certain exemplary embodiments comprise a method comprising receiving, from a user-operated telecommunications device, a user-initiated communication to a non-911 communications address. The method can comprise automatically providing a user with a current location of a user-associated telecommunications device. The method can comprise requesting, from the user, verification of the current location of the user-associated telecommunications device.

Abstract: Certain exemplary embodiments comprise a method comprising receiving, from a user-operated telecommunications device, a user-initiated communication to a non-911 communications address. The method can comprise automatically providing a user with a current location of a user-associated telecommunications device. The method can comprise requesting, from the user, verification of the current location of the user-associated telecommunications device.

Abstract: Certain exemplary embodiments comprise a method comprising receiving, from a user-operated telecommunications device, a user-initiated communication to a non-911 communications address. The method can comprise automatically providing a user with a current location of a user-associated telecommunications device. The method can comprise requesting, from the user, verification of the current location of the user-associated telecommunications device.