Abstract: An SDN controller configures a network element as a service edge. The SDN controller configures a service flow associated with a service to receive a required service treatment. The SDN controller configures an entry point to add routing tags on a set of packets associated with the service. The set of packets are routed in accordance with the routing tags. The required service treatment is applied at the service edge and the tags are removed from the set of packets, which are then forwarded to the network.

Abstract: Node identifiers can be assigned to packet core policy nodes and directly routed to a diameter routing agent (DRA) and application functions (AFs) within a call processing message that is employed to establish an application service. Such a policy node identity will be received by Application Functions, UEs and/or intermediate message routers during the initial establishment of a packet data session so that they can refer to the policy node entity directly in the sub-sequent call processing flows related the established session, instead of querying a relational database which can be complex to maintain with multi-million correlation records. As an example, the policy node identifiers can be configurable and can comprise a hostname of the policy nodes, address data associated with the policy nodes, or a defined numerical value that maps to the hostname of the policy nodes.

Abstract: Control plane devices are selected by a Multimedia Broadcast Multicast Service Gateway (MGW) based on session exchange procedural triggers received from a Broadcast Multicast Service Center (BMSC). In one aspect, the MGW can employ a serving area-based Domain Name System (DNS) query/response exchange for control plane device selection that simplifies the overall complex broadcast core network architecture and design. Additionally or optionally, the MGW can employ other factors, such as, but not limited to, round trip time (RTT), load information, active/inactive link status, etc. to select the control plane devices that are to be utilized for establishing the end-to-end control plane message exchanges.

Abstract: A system that incorporates the subject disclosure may include, for example, receive a subscription from an application server where the subscription identifies a session event and/or sub-events occurring in a communication session for which the application server requests user location information, provide subscription information based on the subscription to core network nodes of the mobile communications network, receive user location information from the core network nodes responsive to a detection of a triggering event corresponding to the session event of the subscription, and provide the user location information to an IP multimedia subsystem network for delivery to the application server. Other embodiments are disclosed.

Abstract: Node identifiers can be assigned to packet core policy nodes and directly routed to a diameter routing agent (DRA) and application functions (AFs) within a call processing message that is employed to establish an application service. Such a policy node identity will be received by Application Functions, UEs and/or intermediate message routers during the initial establishment of a packet data session so that they can refer to the policy node entity directly in the sub-sequent call processing flows related the established session, instead of querying a relational database which can be complex to maintain with multi-million correlation records. As an example, the policy node identifiers can be configurable and can comprise a hostname of the policy nodes, address data associated with the policy nodes, or a defined numerical value that maps to the hostname of the policy nodes.

Abstract: The described technology is generally directed towards selectively steering wireless network data packet traffic to a network edge cloud, which reduces backhaul bandwidth and facilitates ultra-low latency communications. In one aspect, upon receiving a request for data communication by a user equipment in the wireless network, location information is used to override a centralized access point name (e.g., 4G serving gateway/packet gateway, S/PGW, or 5G user plane function) with an edge-located access point name (edge 4G S/PGW or edge 5G user plane function). This facilitates the data communication between the user equipment and an edge-located access point device associated with the edge-located access point name.

Abstract: Node identifiers can be assigned to packet core policy nodes and directly routed to a diameter routing agent (DRA) and application functions (AFs) within a call processing message that is employed to establish an application service. Such a policy node identity will be received by Application Functions, UEs and/or intermediate message routers during the initial establishment of a packet data session so that they can refer to the policy node entity directly in the sub-sequent call processing flows related the established session, instead of querying a relational database which can be complex to maintain with multi-million correlation records. As an example, the policy node identifiers can be configurable and can comprise a hostname of the policy nodes, address data associated with the policy nodes, or a defined numerical value that maps to the hostname of the policy nodes.

Abstract: A method includes receiving, at a server connected to a network, a plurality of emergency alerts from a plurality of devices connected to the network. The method also includes analyzing, by the server, the plurality of emergency alerts to determine an emergency type of each of the plurality of emergency alerts. The method includes categorizing, by the server, the plurality of emergency alerts based on the emergency type of each of the plurality of emergency alerts. The method includes prioritizing a first category of the plurality of emergency alerts and consolidating the plurality of emergency alerts of the first category into a consolidated alert. The method includes causing the consolidated alert to be provided to an emergency responder.

Abstract: Facilitating device contexts, operational modes, and policy driven enhancements for paging in advanced networks (e.g., 4G, 5G, 6G, and beyond) is provided herein. Operations of a network device can comprise analyzing a group of contextual data for a user equipment device, and mobility management behaviors historically implemented for the user equipment device and based on an indication that a page request is scheduled to be sent to the user equipment device. The operations can also comprise configuring a paging message for the user equipment device based on the contextual data and the mobility management behaviors. Further, the operations can comprise sending the paging message to the user equipment device.

Abstract: A wireless network for mobile communications has a connectionless framework using native internet protocol (IP). In this connectionless framework, packet routing may be based on user endpoint (UE) physical IP address, which is associated with the prefix of an associated access node (e.g. eNB). In addition to using the connectionless-IP framework for the traffic flow carried by one access point (e.g. eNB) at a time, advanced mobile call processing features, such as carrier aggregation and dual connectivity, are enhanced to leverage the packet-oriented connectionless radio access network and wireless core network architecture by using the SDN architecture and a wireless network specific software-defined network controller.

Abstract: Network and/or application resources can be dynamically instantiated based on service attributes and/or network capabilities. In one aspect, a customized and/or localized core slice can be selected that can deliver the requested service with target performance parameters. According to an aspect, dynamic selection, control, and/or management reporting can be provided for core network slices. Moreover, optimal core network slice selection can be performed to reduce network transport costs and efficiently deliver various services using an optimal core slice that matches a service profile being requested by an end user and/or device.

Abstract: The described technology is generally directed towards selectively steering wireless network data packet traffic to a network edge cloud, which reduces backhaul bandwidth and facilitates ultra-low latency communications. In one aspect, upon receiving a request for data communication by a user equipment in the wireless network, location information is used to override a centralized access point name (e.g., 4G serving gateway/packet gateway, S/PGW, or 5G user plane function) with an edge-located access point name (edge 4G S/PGW or edge 5G user plane function). This facilitates the data communication between the user equipment and an edge-located access point device associated with the edge-located access point name.

Abstract: A software defined network controller receives from a radio access network access point an attach request generated by a user equipment that includes a user equipment identification and an IP address for the radio access network access point. The controller assigns a temporary identification to the user equipment and sends a modified attach request including the temporary identification, and application server identification and an application server IP address to the radio access network access point. The controller configures a forwarding table associated with the radio access network access point so that the access point forwarding table matches the user equipment identification, the application server identification and the application server IP address.

Abstract: A system that incorporates the subject disclosure may include, for example, facilitating establishing a first interface between a processor and the system where the system performs a policy and charging rules function in a mobile communications network and where the first interface bypasses a packet data network gateway and a serving gateway, facilitating establishing a second interface between the processor and the system where the second interface utilizes the packet data network gateway and the serving gateway, providing a first message from the processor to the system via the first interface where the first message is associated with a quality of service authorization, and receiving a second message from the system via the first interface where the second message is associated with the quality of service authorization. Other embodiments are disclosed.

Abstract: Concepts and technologies disclosed herein are directed to an enhanced software-defined networking (“SDN”) controller to support ad-hoc radio access technologies (“RATs”). An SDN controller receives, from an ad-hoc radio access controller serving an ad-hoc radio access network (“RAN”), an attach request sent on behalf of a user equipment (“UE”) operating in communication with an ad-hoc RAT transceiver node. The attach request includes a physical IP address associated with the UE. The physical IP address includes an IP address sub-interface pre-fix broadcast to the UE by the ad-hoc RAT transceiver node combined with a physical address of the UE. In response to the attach request, the SDN controller can complete an attachment procedure for allowing the ad-hoc radio access controller to an SDN network. The SDN controller also can update one or more components operating within the SDN network to reflect how to reach the UE via the physical IP address.

Abstract: Network and/or application resources can be dynamically instantiated based on service attributes and/or network capabilities. In one aspect, a customized and/or localized core slice can be selected that can deliver the requested service with target performance parameters. According to an aspect, dynamic selection, control, and/or management reporting can be provided for core network slices. Moreover, optimal core network slice selection can be performed to reduce network transport costs and efficiently deliver various services using an optimal core slice that matches a service profile being requested by an end user and/or device.

Abstract: Tracking areas that comprise service cells capable of providing advanced long-term evolution (LTE-A) features, can be utilized to indicate to a mobile device that the mobile device can access the advanced features. For example, an LTE-A capable mobile device can display an LTE-A icon if the mobile device is in a geographic area that qualifies as an LTE-A tracking area. However, if the mobile device is not capable of receiving LTE-A services, then the mobile device can display an LTE icon instead of an LTE-A icon.

Abstract: Aspects describe renegotiation of quality of service parameters to resolve maximum bit rate mismatches and/or other quality of service parameter mismatching issues that might arise during an inter-radio access technology handover. At about the same time as a mobile device moves from a source network to a target network, the target network dynamically initiates a quality of service modification procedure. The quality of service modification procedure can help resolve the maximum bit rate mismatches and/or the other quality of service parameter mismatching issues.

Abstract: Concepts and technologies disclosed herein are directed to providing enhanced quality of service (“QoS”) in a software-defined network (“SDN”)-based connectionless mobility architecture. According to one aspect of the concepts and technologies disclosed herein, an SDN controller can receive service level requirements and can map the service level requirements to QoS requirements and attributes to be associated with a QoS tag. The SDN controller can configure a service entry point to insert the QoS tag into incoming packets so that one or more other service points can extract the QoS tag. The other service point(s) can determine, based upon the QoS tag, a QoS treatment to apply to the incoming packets. The other service point(s) can apply the QoS treatment to the incoming packets in accordance with the QoS tag.

Abstract: A method and apparatus for session management in a wireless network are disclosed. For example, a user endpoint (UE) device, sends a request for a session internet protocol (IP) address assignment using an interface IP address, configures the UE device with the session IP address, provides to a controller an association of the interface and session IP addresses, and receives packets addressed to the session IP address via an access network entity associated with the interface IP address. In one example, a controller receives an association of an interface IP address with a session IP address from an attached UE device, provides to a network node an update on a route to reach the session IP address through the interface IP address, identifies an active interface IP address to receive packets, and configures an open flow switch or router for routing the packets towards the active interface IP address.