Abstract: A method for providing network function (NF) discovery service enhancements includes receiving, by an NF repository function (NRF) from a consumer NF, a NF discovery request message that requests discovery of a network service hosted by producer NFs and includes at least one of a maximum payload size parameter and a profile count limit parameter and obtaining, by the NRF, NF profile objects corresponding to producer NFs that host the network service. The method further includes in response to determining that the consumer NF supports conditional limit features based on the at least one of the maximum payload size parameter and the profile count limit parameter, providing by the NRF to the consumer NF, a number of the NF profile objects that adheres to the at least one of the maximum payload size parameter and the profile count limit parameter indicated in the NF discovery request message.

Abstract: A method for providing for policy-based access and mobility management function (AMF) selection using network slice selection assistance information (NSSAI) availability information obtained from an NSSAI availability service includes, at a network slice selection function (NSSF) including at least one processor, obtaining, from an NSSAI availability service, NSSAI availability information regarding a plurality of AMFs. The method further includes receiving, from a first AMF, a network slice selection request specifying a network slice service requested by a user equipment (UE). The method further includes generating, based on the NSSAI availability information and the network slice service requested by the UE, a prioritized list including an identity of at least one AMF for supporting the network slice service. The method further includes communicating the prioritized list to the first AMF.

Abstract: According to one aspect, the subject matter described herein includes a method for service-specific group message delivery to narrowband Internet of things (IoT) devices. The method includes operations performed by a network node including at least one processor. The operations include receiving, on a first interface, a request for service-specific group message delivery to narrowband IoT devices supporting a specified service. The operations further include generating, by the network node, a message for service-specific group message delivery for transmission on a second interface, the message including a NB-IoT service information parameter for identifying a narrowband IoT service provided by the narrowband IoT devices supporting the specified service. The operations further include transmitting, from the network node and on the second interface the message for service-specific group message delivery to narrowband IoT devices.

Abstract: A method for detecting and mitigating effects of abnormal MTC device behavior includes, at a telecommunications network node comprising one of an MME, DRA, or SCEF, receiving CP information from which core network (CN) assistance information for tuning an evolved node B (eNB) to minimize MTC device state transitions is derivable, forwarding the CP information or CN assistance information derived from the CP information to another network node, deriving, from the CP information, a rule for policing behavior of the MTC device, storing the rule in memory of the telecommunications network node, monitoring uplink communications from the MTC device, determining, using the stored rule derived from the CP information, that the MTC device is not behaving in accordance with an expected behavior; and, in response performing a network security action that mitigates an effect of traffic from the MTC device on the network.

Abstract: A method for feedback-based network slice management includes steps performed at a network slice management function (NSMF) including at least one processor. The steps include subscribing, via a network data analytics function (NWDAF) subscription interface of the NSMF, directly with the NWDAF to create a subscription to be notified of network slice load information and specifying, as part of the subscription, network slice load information report generation criteria defined by the NSMF. The steps further include receiving, directly from the NWDAF, via the NWDAF subscription interface of the NSMF and in response to the NSMF-defined network slice load information report triggering criteria being met, network slice load information. The steps further include determining, based on the network slice load information, that a network slice resource allocation change is needed.

Abstract: A method for extending new radio (NR) usage indications to an application function (AF) includes, at a policy and charging rules function (PCRF) including at least one processor, receiving an indication of NR usage by a user equipment (UE). The steps further include determining that an AF is subscribed to receive indications of NR usage for the UE. The steps further include, in response to determining that an AF is subscribed to receive indications of NR usage for the UE, communicating the indication of NR usage to the AF. The steps further include receiving a message from the AF to effect a change in service provided to the UE based on the indication of NR usage. The steps further include effecting the change in service provided to the UE based on the indication of NR usage.

Abstract: A method for providing for policy-based access and mobility management function (AMF) selection using network slice selection assistance information (NSSAI) availability information obtained from an NSSAI availability service includes, at a network slice selection function (NSSF) including at least one processor, obtaining, from an NSSAI availability service, NSSAI availability information regarding a plurality of AMFs. The method further includes receiving, from a first AMF, a network slice selection request specifying a network slice service requested by a user equipment (UE). The method further includes generating, based on the NSSAI availability information and the network slice service requested by the UE, a prioritized list including an identity of at least one AMF for supporting the network slice service. The method further includes communicating the prioritized list to the first AMF.

Abstract: A method for dynamically provisioning and using PLMN location mappings includes, in an SCEF or NEF, receiving, from a PLMN network node, a message containing a PLMN location identifier and a non-PLMN location identifier, extracting the PLMN location identifier and the non-PLMN location identifier from the message and storing, in a PLMN location mapping database in the SCEF or NEF, a mapping between the PLMN location identifier and the non-PLMN location identifier. The method further includes receiving, via a monitoring interface of the SCEF or NEF, a monitoring request message requesting IoT device information and including a non-PLMN location identifier.

Abstract: A method for extending new radio (NR) usage indications to an application function (AF) includes, at a policy and charging rules function (PCRF) including at least one processor, receiving an indication of NR usage by a user equipment (UE). The steps further include determining that an AF is subscribed to receive indications of NR usage for the UE. The steps further include, in response to determining that an AF is subscribed to receive indications of NR usage for the UE communicating the indication of NR usage to the AF. The steps further include receiving a message from the AF to effect a change in service provided to the UE based on the indication of NR usage. The steps further include effecting the change in service provided to the UE based on the indication of NR usage.

Abstract: A method for group device triggering for IoT devices includes receiving, from a requesting node, a device trigger request message. The method further includes determining that the device trigger request message requests group IoT device triggering. The method further includes, in response to determining that the device trigger request message requests group IoT device triggering, resolving an external group identifier in the device trigger request message to individual international mobile station identifiers (IMSIs) corresponding to target IoT devices of the device trigger request message. The method further includes signaling a downstream node to trigger the target IoT devices.

Abstract: According to one aspect, the subject matter described herein includes a method for service-specific group message delivery to narrowband Internet of things (IoT) devices. The method includes operations performed by a network node including at least one processor. The operations include receiving, on a first interface, a request for service-specific group message delivery to narrowband IoT devices supporting a specified service. The operations further include generating, by the network node, a message for service-specific group message delivery for transmission on a second interface, the message including a NB-IoT service information parameter for identifying a narrowband IoT service provided by the narrowband IoT devices supporting the specified service. The operations further include transmitting, from the network node and on the second interface the message for service-specific group message delivery to narrowband IoT devices.

Abstract: Methods, systems, and computer readable media for machine type communications/Internet of things (MTC/IoT) device updating are described. One method for machine type communications (MTC) device software updating includes receiving, by a control plane network node including at least one processor and via non-Internet protocol data delivery (NIDD) or non-access stratum (NAS) messaging, hardware and software version information regarding an MTC device. The method includes identifying, by the control plane network node, that a software update is available for the MTC device. The method further includes, in response determining that a software update is available for the MTC device, transmitting, by the control plane network node and via NIDD or NAS messaging, the software update to the MTC device.

Abstract: A method for dynamically provisioning and using PLMN location mappings includes, in an SCEF or NEF, receiving, from a PLMN network node, a message containing a PLMN location identifier and a non-PLMN location identifier, extracting the PLMN location identifier and the non-PLMN location identifier from the message and storing, in a PLMN location mapping database in the SCEF or NEF, a mapping between the PLMN location identifier and the non-PLMN location identifier. The method further includes receiving, via a monitoring interface of the SCEF or NEF, a monitoring request message requesting IoT device information and including a non-PLMN location identifier.

Abstract: Methods, systems, and computer readable media for MTC/IoT device updating are described. One method for MTC device software updating includes receiving, by a control plane network node including at least one processor and via non-IP data delivery (NIDD) or non-access stratum (NAS) messaging, hardware and software version information regarding an MTC device. The method includes identifying, by the control plane network node, that a software update is available for the MTC device. The method further includes, in response determining that a software update is available for the MTC device, transmitting, by the control plane network node and via NIDD or NAS messaging, the software update to the MTC device. The method further includes receiving, at the control plane network node and via NIDD or NAS messaging, status information regarding delivery of the software update to the MTC device or installation of the software update by the MTC device.

Abstract: Methods, systems, and computer readable media for sharing identification information of network nodes in an IMS network are disclosed. One method includes determining, by a packet data network gateway (PGW), policy and charging rules function (PCRF) identification information corresponding to a PCRF node designated to support an IMS-based subscriber session requested by a user equipment device and establishing, by the PGW, a subscriber Gx session with the PCRF node corresponding to the determined PCRF identification information. The method further includes determining, by the PGW, application function (AF) identification information corresponding to an AF server designated to support the IMS-based subscriber session and generating, by the PGW, a create session response message including at least the PCRF identification information and the AF identification information. The method also includes sending, by the PGW, the create session response message containing the at least the PCRF identification inform.

Abstract: A method for detecting and mitigating effects of abnormal MTC device behavior includes, at a telecommunications network node comprising one of an MME, DRA, or SCEF, receiving CP information from which core network (CN) assistance information for tuning an evolved node B (eNB) to minimize MTC device state transitions is derivable, forwarding the CP information or CN assistance information derived from the CP information to another network node, deriving, from the CP information, a rule for policing behavior of the MTC device, storing the rule in memory of the telecommunications network node, monitoring uplink communications from the MTC device, determining, using the stored rule derived from the CP information, that the MTC device is not behaving in accordance with an expected behavior; and, in response performing a network security action that mitigates an effect of traffic from the MTC device on the network.

Abstract: Methods, systems, and computer readable media for dynamically provisioning subscriber based session timeout information are disclosed. One method includes method includes receiving, from a packet data network gateway (PGW), a request message containing session information parameters corresponding to a session requested by a user equipment device and deriving an absolute timeout period value and an idle timeout period value based on input comprising one or more of the session information parameters. The method further includes generating a response message containing the determined absolute timeout period value and the determined idle timeout period value and sending the generated response message to the PGW, wherein the PGW is configured to apply the absolute timeout period value and the idle timeout period value to the session requested by the user equipment device.

Abstract: Methods, systems, and computer readable media for priority routing of Diameter messages are disclosed. In some examples, a method includes determining a Diameter Routing Message Priority (DRMP) priority value for a Diameter message. The method includes marking each of one or more Internet protocol (IP) packets carrying the Diameter message with an IP quality of service (QoS) value for the Diameter message based on the DRMP priority value. The method includes sending the one or more IP packets carrying the Diameter message to a destination Diameter node by way of an IP router on a data communications network providing quality of service using IP QoS values.

Abstract: A method includes establishing, by a machine type communication (MTC) accumulator, a first direct communication path tunnel with a eNodeB and a second direct communication path tunnel with a MTC application server (AS), receiving, by the eNodeB, radio resource control (RRC) packet containing MTC data as a payload from a MTC UE device over an established radio bearer link, and locating, by the eNodeB, a MTC data forwarding indicator included in the RRC packet. In response to locating the MTC data forwarding indicator included in the RRC packet, forwarding the MTC Data to the MTC accumulator and facilitating, by the MTC accumulator, a MTC communication session between the MTC UE device and the MTC application server identified by a MTC application server identifier contained in the MTC data over the established first and second direct communication paths.

Abstract: Methods, systems, and computer readable media for validating a redirect address in a Diameter message are disclosed. One method occurs at a Diameter node, e.g., a Diameter routing agent (DRA) node, a packet data network (PDN) gateway, a policy and charging enforcement function (PCEF) node, or a Diameter edge agent (DEA) node. The method includes receiving a message containing a redirect address that appears to be associated with a top-up server for facilitating a subscriber to recharge or top-up an account balance. The method also includes determining whether the redirect address is valid by querying, using a subscriber related identifier, a data structure containing one or more addresses. The method further includes performing at least one action based on the determining.