A network controller provides proactive notification of a wireless client device's address rotation to layer 2 (L2) and/or layer 3 (L3) devices. Traditional methods of device address discovery rely on broadcasting of address queries across a plurality of links until a path to a device having the queried address responds. As device address changes become more frequent in an effort to improve user privacy, traditional methods of address discovery impose a large burden on networks, reducing their performance and efficiency. By proactively propagating address changes to upstream devices, the need for broadcast oriented address discovery techniques is reduced, resulting in improved network performance.

A network controller provides proactive notification of a wireless client device's address rotation to layer 2 (L2) and/or layer 3 (L3) devices. Traditional methods of device address discovery rely on broadcasting of address queries across a plurality of links until a path to a device having the queried address responds. As device address changes become more frequent in an effort to improve user privacy, traditional methods of address discovery impose a large burden on networks, reducing their performance and efficiency. By proactively propagating address changes to upstream devices, the need for broadcast oriented address discovery techniques is reduced, resulting in improved network performance.

A method for conducting a velocity check for outbound subscribers roaming to neighboring countries includes receiving, by a network gateway associated with a home country from an MSC associated with a neighboring country, an ingress signaling message related to a mobile device roaming in the neighboring country, sending, to an HLR in the home country, an interrogation request message containing a mobile subscriber identifier, and receiving an interrogation response message containing age of location information and cell identifier information corresponding to the mobile subscriber identifier. The method further includes utilizing the cell identifier information and a country code identifier included in the ingress signaling message to determine two latitude-longitude positions, determining an estimated transit time of the mobile device using the two latitude-longitude reference positions, and comparing age of location information with the estimated transit time to determine if the ingress signaling message is to be forwarded to the HLR.

A method for conducting a velocity check for outbound subscribers roaming to neighboring countries includes receiving, by a network gateway associated with a home country from an MSC associated with a neighboring country, an ingress signaling message related to a mobile device roaming in the neighboring country, sending, to an HLR in the home country, an interrogation request message containing a mobile subscriber identifier, and receiving an interrogation response message containing age of location information and cell identifier information corresponding to the mobile subscriber identifier. The method further includes utilizing the cell identifier information and a country code identifier included in the ingress signaling message to determine two latitude-longitude positions, determining an estimated transit time of the mobile device using the two latitude-longitude reference positions, and comparing age of location information with the estimated transit time to determine if the ingress signaling message is to be forwarded to the HLR.

Methods, systems, and computer readable media for supporting mobile originated data multicasting in a communications network.in a communications network are disclosed. One method includes receiving, from a consumer network function (NF) in a communications network, a deliver request message containing mobile originated (MO) data corresponding to a protocol data unit (PDU) session, wherein NIDD context information stored at NEF and referred by a context identifier in the deliver request message includes a subscriber identifier and a data network identifier associated with a user device requesting the PDU session and determining that a rule entry belonging to a plurality of rule entries contained in a multicasting ruleset matches at least one of the subscriber identifier and the data network identifier included in the NIDD context information that is stored at the NEF and referred by the context identifier in the deliver request message. The method further includes accessing a list of NF identity objects in the rule entry in response to determining the rule entry matches at least one of the subscriber identifier and/or the data network identifier and delivering the MO data to each of a plurality of NF endpoints specified in the rule entry in accordance with a routing condition indicated in each of the NF identity objects respectively associated with each of the NF endpoints.

Methods, systems, and computer readable media for supporting mobile originated data multicasting in a communications network.in a communications network are disclosed. One method includes receiving, from a consumer network function (NF) in a communications network, a deliver request message containing mobile originated (MO) data corresponding to a protocol data unit (PDU) session, wherein NIDD context information stored at NEF and referred by a context identifier in the deliver request message includes a subscriber identifier and a data network identifier associated with a user device requesting the PDU session and determining that a rule entry belonging to a plurality of rule entries contained in a multicasting ruleset matches at least one of the subscriber identifier and the data network identifier included in the NIDD context information that is stored at the NEF and referred by the context identifier in the deliver request message. The method further includes accessing a list of NF identity objects in the rule entry in response to determining the rule entry matches at least one of the subscriber identifier and/or the data network identifier and delivering the MO data to each of a plurality of NF endpoints specified in the rule entry in accordance with a routing condition indicated in each of the NF identity objects respectively associated with each of the NF endpoints.

Methods and apparatus are disclosed for the propagation of data over a network. Data packets are transmitted with identifiers (e.g. multicast addresses) for devices or groups of devices which are to receive the data. The data packets are further transmitted with propagation indicators, indicating the cells over which the data is to be propagated (or how widely the data is to be propagated from its source). Thus only those devices 10 which are both addressed by the data packets and within the cells identified by the propagation indicator receive the data.

Methods and apparatus are disclosed for the propagation of data over a network. Data packets are transmitted with identifiers (e.g. multicast addresses) for devices or groups of devices which are to receive the data. The data packets are further transmitted with propagation indicators, indicating the cells over which the data is to be propagated (or how widely the data is to be propagated from its source). Thus only those devices 10 which are both addressed by the data packets and within the cells identified by the propagation indicator receive the data.

A RAN node (2) receives, from a core network node (6, 7, 8), a first identifier that is used by a service, an application, or an edge server (5) to identify a radio terminal (1) connected to the RAN node (2), and associates the first identifier with a second identifier that is used by the RAN node (2) to identify the radio terminal (1). Further, the RAN node (2) communicates with the edge server (5) using the first identifier. It is thus, for example, possible to allow an MEC server (or an MEC application hosted on the MEC server) and a radio access network (RAN) node to directly exchange therebetween a control message regarding a specific radio terminal.

A RAN node (2) receives, from a core network node (6, 7, 8), a first identifier that is used by a service, an application, or an edge server (5) to identify a radio terminal (1) connected to the RAN node (2), and associates the first identifier with a second identifier that is used by the RAN node (2) to identify the radio terminal (1). Further, the RAN node (2) communicates with the edge server (5) using the first identifier. It is thus, for example, possible to allow an MEC server (or an MEC application hosted on the MEC server) and a radio access network (RAN) node to directly exchange therebetween a control message regarding a specific radio terminal.