Abstract: A network device may maintain a list of existing slice identifiers, associated with slices of a core network, that are in use in active UE sessions, and may receive a slice identifier associated with a slice of the core network and provided in a request to establish a session between a UE and the slice of the core network. The network device may determine whether the slice identifier matches an existing slice identifier included in the list, and may create a new network address, with an address of the network device and the slice identifier, based on the slice identifier failing to match an existing slice identifier included in the list. The network device may utilize the new network address to establish the session between the UE and the slice of the core network.

Abstract: A device may receive, from a user device, a content selection, and may receive metadata associated with the content. The device may determine viewing options, for viewing the content, based on the metadata associated with the content, and may identify dimensions of the content based on the viewing options. The device may calculate points for each of the dimensions of the content, and may assign the points for each of the dimensions of the content to generate weighted dimensions of the content. The device may associate the weighted dimensions of the content with the viewing options to generate weighted viewing options, and may rank the weighted viewing options to determine a primary viewing option, a secondary viewing option, and remaining viewing options. The device may provide the primary viewing option, the secondary viewing option, and the remaining viewing options to the user device, for display.

Abstract: In some implementations, a device may receive a request to add a domain to a blockchain. The request may include data that indicates a public key associated with the domain and/or a unique identifier associated with the domain. The device may generate a domain information block, based on the request, that includes the public key associated with the domain and a blockchain identifier that is based on the unique identifier associated with the domain. The device may provide the domain information block to a set of blockchain nodes to add the domain information block to the blockchain.

Abstract: A system described herein may identify a particular service provided by a first Edge Computing (“EC”) device to a particular User Equipment (“UE”), and may monitor performance information associated with the first EC device and/or a second EC device. The system may determine, based on the monitoring, that the second EC device should provide the service to the particular UE in lieu of the first EC device; and may accordingly cause the service to be provided to the particular UE by the second EC device in lieu of the first EC device. The system may notify the first EC device that the second EC device has been selected to provide the service to the particular UE in lieu of the first EC device, and/or may notify the second EC device that the second EC device has been selected to provide the service to the particular UE.

Abstract: Techniques for determining a network health score for a network are disclosed. In one embodiment, a method is disclosed comprising obtaining network data associated with one or more user equipments (UEs) connected to a network, generating UE data for the one or more UEs using the network data, the generating comprising assigning each UE to a UE category from a set of UE categories, determining a set of UE category weights corresponding to the set of UE categories using the network data, determining at least one network health score for the one or more UEs using the network data, the generated UE data and the set of UE category weights and causing performance or at least one action in accordance with the determined at least one network health score.

Abstract: A device may store first data structures that include first data identifying computing resources provided at an edge of a network for a computing environment. The device may store second data structures that include second data identifying aggregations of portions of the first data, and may store a third data structure that includes third data identifying an aggregation of the second data. The device may receive, from a first client device, client data identifying an address and resources associated with the first client device, and may update a first data structure based on the client data. The device may update a second data structure based on updating the first data structure, and may update the third data structure based on updating the second data structure. The device may provide a notification indicating that the first client device has been added as a computing resource for the computing environment.

Abstract: A method includes retrieving first data from a first data store having a first database topology and second data from a second data store having a second database topology. The first data and the second data are stored in a load data set. The load data set is sorted based on a first identifier field. A first microdatabase is loaded with a first portion of the first data associated with a first value of the first identifier field and a first portion of the second data associated with the first value. A second microdatabase is loaded with a second portion of the first data associated with a second value of the first identifier field and a first portion of the second data associated with the second value. A first key map record for the first microdatabase is generated. A second key map record for the second microdatabase is generated.

Abstract: One or more devices may include a credentials server. The credentials server may be configured to: receive primary Standalone Non-Public Network (SNPN) credentials for a User Equipment device (UE) and SNPN information. The primary SNPN credentials and the SNPN information are associated with the UE and an SNPN. The devices may be configured to generate temporary SNPN credentials based on the primary SNPN credentials and the SNPNN information. The devices may forward the temporary SNPN credentials to the SNPN.

Abstract: A computer device may include a memory configured to store instructions and a processor configured to execute the instructions to receive a request from a user equipment (UE) device to resolve a Domain Name System (DNS) query for a Uniform Resource Locator (URL) and determine that the URL corresponds to a malicious URL. The processor may be further configured to select to not resolve the DNS query in response to determining that the URL corresponds to a malicious URL and send an indication to the UE device that the URL corresponds to a malicious URL.

Abstract: A device may determine a number of user equipments (UEs) connected to an inactive site during a first period of time and determine that the inactive site experienced a power outage during a second period of time. The device may determine that the UEs connected to a set of active sites during the second period of time. The device may determine one or more key performance indicator (KPI) changes to one or more KPIs, during the second period of time, for each of the set of active sites. The device may determine a plurality of weights associated with the inactive site experiencing the power outage; determine a set of impacts, of the inactive site, on the one or more KPI changes for the set of active sites based on the plurality of weights; and cause power to be restored to the inactive site based on the set of impacts.

Abstract: An orchestration system may receive, from a subscriber management system, a request indicating a subscriber intent for a connectivity service or a cloud service. The orchestration system may identify, based on subscriber information associated with the request, a managed service. The orchestration system may automatically discover subscriber network devices configured to access the managed service and configure network connectivity of the subscriber network devices. The orchestration system may allocate infrastructure and network resources for the managed service. The orchestration system may configure, based on the resources, infrastructure hardware components, software components, and applications of the managed service. The orchestration system may configure managed service components associated with the managed service. The orchestration system may connect the infrastructure hardware components, the software components, the applications, and the managed service components to service assurance systems.

Abstract: In some implementations, a management system may receive service information from a plurality of service providers. A plurality of network devices, of the plurality of service providers, may be blockchain nodes of a blockchain. The service information, of a service provider, may identify network services provided by a network device of the service provider and identifies a location of the network device. The management system may receive, via the blockchain, information regarding a service-level agreement associated with a subset of service providers, of the plurality of service providers, providing network services for an application. The management system may receive, via the blockchain, an approval of the service-level agreement from each service provider of the subset of service providers. The management system may perform an action based on the service-level agreement and based on the network services provided by the subset of service providers for the application.

Abstract: A vehicle device may receive audio data and other vehicle data associated with a vehicle and may transform the audio data to transformed audio data in a frequency domain. The vehicle device may segment the transformed audio data into a plurality of audio segments and may process the plurality of audio segments, with different feature extraction techniques, to extract a plurality of feature vectors. The vehicle device may merge the plurality of feature vectors into a merged feature vector and may create an audio signature for the audio data based on the merged feature vector. The vehicle device may process the audio signature and the other vehicle data, with a model, to determine a classification of the audio signature and may perform one or more actions based on the classification of the audio signature.

Abstract: A Multi-Access Edge Computing (MEC) device, associated with a base station, may include a processor configured to receive a request to send data to a plurality of user equipment (UE) devices. The MEC device may be further configured to determine that the data is to be delivered to the plurality of UE devices by the base station via multicast; determine signal quality values for the plurality of UE devices; select a subset of the plurality of UE devices based on the determined signal quality values; and send, using the base station, the data to the selected subset of the plurality of UE devices via multicast, and delaying or terminating delivery of the requested data to UE devices, of the plurality of UE devices, that are not in the selected subset.

Abstract: A method, a device, and a non-transitory storage medium are described in which a cellular device-satellite communications service is provided. The service may provide establishment, maintenance, and termination of uplink and downlink connections via a satellite network, a terrestrial network, and both based on network information and satellite information. The service may also provide scheduling for user plane traffic via the uplink and downlink connections.

Abstract: A system described herein may receive an authentication request from a User Equipment (“UE”). The authentication request may include a particular identifier, such as an application group identifier. The system may determine whether a token is available (e.g., has been previously generated) for the UE and the particular identifier. If such token is not available, the system may initiate an authentication procedure that includes receiving input from the UE, and may generate the token, indicating that the authentication procedure has been completed. If the token is available, then the system may forgo initiating the authentication procedure. The system may output the token, such that a service provider system authenticates the UE based on the generated token and provides services to the UE based on authenticating the UE.

Abstract: A network device may delegate a first prefix length to a primary WAN interface and delegate a second prefix length to a backup WAN interface. The network device may assign a first primary prefix and a first backup prefix to a first VLAN interface and may assign a second primary prefix and a second backup prefix to a second VLAN interface. The network device may provide egress traffic from host devices, connected to the first VLAN interface and to the second VLAN interface, to the primary WAN interface and without prefix translation, when the primary WAN interface is available. The network device may provide ingress traffic to the host devices, via the primary WAN interface and without prefix translation, when the primary WAN interface is available.

Abstract: A network device may receive a subscription request to subscribe to a multimedia priority service (MPS) for a user device, and may generate an MPS profile for the user device based on the subscription request. The network device may store the MPS profile in a data structure, and may receive, from the user device, a request to generate an MPS token for the user device. The network device may retrieve the MPS profile from the data structure based on the request to generate the MPS token, and may generate the MPS token based on the MPS profile. The network device may provide the MPS token to the user device.

Abstract: A device may receive content from an application server based on a user equipment (UE) generating a request to view the content over a unicast bearer, and may store the content in a temporary data structure. The device may receive a redirected request to view the content from the UE, and may provide the content over the unicast bearer to the UE based on the redirected request. The device may receive, from the UE, a unicast consumption of the content by the UE and a location of the UE, and may determine whether interest in the content for the location satisfies a threshold based on the unicast consumption. The device may initiate multicast and broadcast service (MBS) core functions with computing resources to utilize for an MBS for the content at the location based on the interest in the content for the location satisfying the threshold.

Abstract: A device may receive, from a fiber sensor device, sensing data associated with a fiber optic cable, the sensing data being produced by an activity that poses a threat of damage to the fiber optic cable, and the sensing data identifying: amplitudes of vibration signals, frequencies of the vibration signals, patterns of the vibration signals, times associated with the vibration signals, and locations along the fiber optic cable associated with the vibration signals. The device may process, with a machine learning model, the sensing data to determine a threat level of the activity to the fiber optic cable, the machine learning model having been trained based on historical information regarding detected vibrations, historical information regarding sources of the detected vibrations, and historical information regarding threat levels to the fiber optic cable. The device may perform one or more actions based on the threat level to the fiber optic cable.