Example implementations relate to changing a status of a device responsive to detecting an anomaly. A traffic pattern of a device may be monitored across a network. It may be determined that the monitored traffic pattern deviates from an expected traffic pattern of the group of devices by a threshold. Responsive to determining that the devices deviates from the expected traffic pattern, packet data transmitted by the device may be inspected. It may be determined that the inspected packet data transmitted by the device is anomalous. The status of the device may be changed responsive to determining that the packet data transmitted by the device is anomalous.

A method for repairing multicast/broadcast content via peer to peer communications, which includes receiving at least a part of a file transmitted by a wireless multicast/broadcast service (WMBS) session via an access ndownetwork; exchanging, via a peer to peer network, completion messages between the UE device and peer UE devices upon completion of the WMBS session; identifying an amount of the file received at the UE device, and amounts of the file received at each of peer UE devices based on the exchanged completion messages; sending repair data to repair the file on each peer UE devices in response to identifying that the UE device received the entire file; and sending repair data via the peer to peer network, obtained from the access network, in response to identifying that the UE device received less than the entire file and more of the file than each of the group of peer UE devices.

Systems, apparatuses, and methods are described for managing concurrent requests from clients for services. Client computing devices may be permitted to use available capacity beyond their assigned quotas. When backpressure exists, connections with a client exceeding a proportion of excess capacity may be closed before connections with a client not exceeding a proportion of excess capacity.

Systems, apparatuses, and methods are described for managing concurrent requests from clients for services. Client computing devices may be permitted to use available capacity beyond their assigned quotas. When backpressure exists, connections with a client exceeding a proportion of excess capacity may be closed before connections with a client not exceeding a proportion of excess capacity.

Traffic is received at an interface of a compute server. Identity information associated with the traffic is determined including an identifier of a customer to which the traffic is attributable. An egress policy configured for the first customer is used to determine whether the traffic is allowed to be transmitted to a destination where that destination is a resource of a second customer. If the traffic is allowed to be transmitted, the traffic and identity information is transmitted over a cross-customer GRE tunnel to a namespace of the second costumer on the compute server. An ingress policy configured for the second customer is used to determine whether the traffic is allowed to be transmitted to the destination, and if it is, then the traffic is transmitted.

Methods and systems for sharing a network link of a file in network storage for collaboration among multiple computing devices using end-to-end encryption may involve generating a link key associated with the file stored remotely in the network storage, being accessible by a first device, and to be accessible by a second device, encrypting a session key associated with the file to generate an encrypted session key using the link key, the file being encrypted with the session key and, generating a salt associated with the file, generating a verifier associated with the file using the link key, sending a message to a server computer with an identifier associated with the file, the salt, the verifier, and the encrypted session key, creating a first link to the file with a name associated with the first device, the identifier, and the link key, and transmitting the first link to second device.

Methods and systems for sharing a network link of a file in network storage for collaboration among multiple computing devices using end-to-end encryption may involve generating a link key associated with the file stored remotely in the network storage, being accessible by a first device, and to be accessible by a second device, encrypting a session key associated with the file to generate an encrypted session key using the link key, the file being encrypted with the session key and, generating a salt associated with the file, generating a verifier associated with the file using the link key, sending a message to a server computer with an identifier associated with the file, the salt, the verifier, and the encrypted session key, creating a first link to the file with a name associated with the first device, the identifier, and the link key, and transmitting the first link to second device.

A network repository function (NRF) receives, from an access and mobility management function (AMF), a discovery request for an address of a session management function (SMF), the discovery request comprising network slice isolation information for at least one network slice. The NRF sends, to the AMF and based on the discovery request, a discovery response comprising the address of the SMF.

A network repository function (NRF) receives, from an access and mobility management function (AMF), a discovery request for an address of a session management function (SMF), the discovery request comprising network slice isolation information for at least one network slice. The NRF sends, to the AMF and based on the discovery request, a discovery response comprising the address of the SMF.

Various embodiments provide for governing VPN access using a device remote from a VPN endpoint.