Abstract: In some implementations, a network device may receive an identifier associated with an application server. The network device may associate the identifier with a service profile associated with a network slice based on a quality of service associated with the network slice. The network device may provide, to a device associated with the application server, information indicating that the identifier is associated with the service profile. The network device may receive address information associated with the application server. The network device may associate the address information with the service profile. The network device may provide service profile information to a security device included in a core network to cause the security device to forward traffic transmitted by the application server toward a destination via the network slice. The service profile information may include an identifier associated with the service profile, the identifier, and the address information.

Abstract: A method may include identifying service requirements associated with a network service, identifying at least one analytics component to monitor the network service and identifying network functions to implement the network service. The method may also include deploying the network functions to monitor the network service, deploying the at least one analytics component and obtaining data associated with monitoring the network service. The method may further include forwarding, by the network functions, the data to the at least one analytics component and determining, by the least one analytics component, whether to take a control action with respect to the network service.

Abstract: A system described herein may provide a technique for the proactive failover of groups of Virtualized Network Functions (“VNFs”) based on monitoring Key Performance Indicators (“KPIs”) associated with the VNFs. KPIs associated with a particular VNF or a set of VNFs may be monitored, and a failover event indicating service degradation or imminent service degradation may be detected based on the KPIs associated with the particular VNF or set of VNFs. Additional VNFs, associated with the particular VNF or set of VNFs, may be further identified for failover from a first data center to a second data center. The additional VNFs may be identified for failover without necessarily monitoring KPIs associated with the additional VNFs, and/or based on factors in addition to KPIs associated with the additional VNFs. For example, the additional VNFs may be failed over based on the KPIs associated with the particular VNF or set of VNFs.

Abstract: A device may include a processor configured to: receive a request from a network function for establishing a session for the network function and a User Equipment device (UE); obtain an identifier corresponding to a network slice for providing the session; update the subscriber data with the network slice identifier; and set up the session, for the network function from the UE to the network slice.

Abstract: A network repository function (NRF) device may receive first locality and priority information concerning a first network function device from the first network function device and may receive second locality and priority information concerning a second network function device from the second network function device. The NRF device may update a data structure based on the first locality and priority information and the second locality and priority information. The NRF device may receive a query concerning a locality from a third network function device and may search the data structure based on the query to identify network function device information associated with the locality. The NRF device may send the network function device information to the third network function device.

Abstract: Systems and methods described herein provide an interface for an Network Data Analytics Function (NWDAF) to extract events from a Time Sensitive Communication Time Synchronization Function (TSCTSF) when operators deploy Time Sensitive Networking (TSN) for a given network slice. An NWDAF in a core network receives an information request for a TSN service and sends, to a TSCTSF, a data request based on the information request. The NWDAF receives event data responsive to the data request and generates an analytics report based on the event data.

Abstract: A method, a device, and a non-transitory storage medium are described in which a policy control event exposure service is provided. The service may include a policy control event exposure service that supports quality of service (QoS)-based event subscription and access and mobility (AM)-based event subscription. The service may notify network function consumers when a QoS-based event or an AM-based event occurs.

Abstract: A system described herein may identify Quality of Service (“QoS”) information associated with a User Equipment (“UE”) that is connected to a radio access network (“RAN”) of a wireless network. The QoS information may include or may be based on a network slice identifier, a QoS value, a Service Level Agreement (“SLA”), a model associated with UE attributes, or other suitable information. The system may determine a time division duplex (“TDD”) configuration for the UE based on the identified QoS information and/or models that associate UE attributes to TDD configurations. The system may implement the determined TDD configuration at the RAN. The UE and the RAN may communicate with each other according to the implemented TDD configuration, which may include particular timing information for uplink and downlink communications between the UE and the RAN.

Abstract: The present invention relates to an optical fiber having a core extending parallelly along a central axis of the optical fiber, an inner cladding surrounding the core and an outer cladding surrounding the inner cladding. In particular, the core is up-doped with first and second up-dopants and the inner cladding is up-doped with the second up-dopant. Moreover, the outer cladding is un-doped. Further, the optical fiber has an attenuation of less than 0.2 at a wavelength of 1625 nanometres (nm), the attenuation of less than 0.18 at a wavelength of 1550 nm, or the attenuation of less than 0.32 at a wavelength of 1310 nm and a cable cutoff in a range of 1186 nanometres (nm) to 1194 nm.

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 method may include identifying network slices associated with transmitting data in a network and determining, by a routing device, that a failure associated with a path used to transmit data has occurred. The method may also include determining, by the routing device, whether the failure is associated with one of the plurality of network slices. The method may further include prioritizing, by the routing device, a route selection process in response to determining that the failure is associated with one of the plurality of network slices.

Abstract: Systems and methods described herein allow mobile network operators to provide an adaptive quality of service (QoS) approach for application providers. A network device in a core network receives a QoS monitoring report based on QoS monitoring by an access station. The QoS monitoring report includes data for QoS parameters for network services in a default QoS flow supporting a protocol data unit (PDU) session. Based on the QoS monitoring report, the network device determines if the default QoS flow supports a required service level for the PDU session. When the network device determines that the default QoS flow does not support the required service level for the PDU session, the network device automatically activates a dedicated QoS flow to support the PDU session with the required service level.

Abstract: A method may include receiving, from a user device, a request to establish a packet data unit (PDU) session; determining that the PDU session should be established as an always-on PDU session; determining whether subscription data associated with the user device indicates that the user device is allowed to establish the always-on PDU session; and establishing the PDU session as an always-on PDU session in response to determining that the subscription data indicates that the user device is allowed to establish the always-on PDU session.

Abstract: A system described herein may identify a requested communication session between a UE and a network, such as a core of a wireless network. The system may identify Quality of Service (“QoS”) information associated with the UE and/or the requested communication session. The QoS information may include or may be based on a network slice identifier, a QoS value, a Service Level Agreement (“SLA”), one or more models associated with UE attributes, or other suitable information. The system may determine a maximum transmission unit (“MTU”) configuration for the UE based on the identified QoS information and/or models that associate UE attributes to MTU configurations. The system may implement the determined MTU configuration, including providing the MTU configuration to one or more gateways or endpoints of the network and/or to the UE. The UE and the network may accordingly use the MTU configuration when communicating via the requested communication session.

Abstract: A system described herein may identify Quality of Service (“QoS”) information associated with a User Equipment (“UE”) that is connected to a radio access network (“RAN”) of a wireless network. The QoS information may include or may be based on a network slice identifier, a QoS value, a Service Level Agreement (“SLA”), a model associated with UE attributes, or other suitable information. The system may determine a time division duplex (“TDD”) configuration for the UE based on the identified QoS information and/or models that associate UE attributes to TDD configurations. The system may implement the determined TDD configuration at the RAN. The UE and the RAN may communicate with each other according to the implemented TDD configuration, which may include particular timing information for uplink and downlink communications between the UE and the RAN.

Abstract: A system described herein may provide a technique for the differentiated Quality of Service (“QoS”) treatment of different traffic types associated with the same application (e.g., a “multi-persona” application) by a wireless network, without the exposure of an application identifier of the application to the wireless network. The application may provide a traffic type indication, based on which a User Equipment (“UE”) may establish one or more QoS flows or other types of communication sessions with the wireless network, where the QoS flows or other types of communication sessions are associated with a network slice that is associated with the traffic type. The communication sessions may include Data Radio Bearers (“DRBs”), backhaul links, protocol data unit (“PDU”) sessions, or other suitable types of communication sessions.

Abstract: Embodiments described herein may provide for the return (e.g., reconnection) of a User Equipment (“UE”) to a first radio access network (“RAN”) to which the UE was connected, after the UE has been redirected to a second RAN based on the occurrence of an event. The event may include a voice call placed by or to the UE. The return of the UE to the first RAN may occur based on the occurrence of another event, such as the voice call being terminated.

Abstract: A method, a device, and a non-transitory storage medium are described in which a network analytics model service is provided. The service may include ingesting customized models and non-customized models by a network analytics device. The ingestion procedure may include receiving the model and model specification data. The service may include provisioning the model and registering the model for discovery by other network devices. The service may include specifying customized identifiers to be used prospective subscribing network devices for the analytics information. The service may also facilitate the use of the analytics information by the subscribing network devices.

Abstract: Systems and methods relate to: receiving a request for session, from a first device over a wireless link, for a service, wherein the request includes a Single-Network Slice Selection Assistance Information (S-NSSAI) that is associated with the service; determine a priority for the session based on the S-NSSAI; and performing, based on the determined priority, an uplink procedure or a downlink procedure for the session. A network include the network component that receives the request for session.

Abstract: A method, a device, and a non-transitory storage medium are described in which a dual connectivity path selection service is provided. The service may select a network path for dual connectivity. The service may use mapping information that may correlate network parameters and values to dual connectivity configurations. The service may compare parameters included in a configuration request pertaining to end devices with the mapping information for selection of a dual connectivity configuration.