Abstract: A user device provides, to a network, information associated with the user device, and receives, from the network, a multi-bit network indication that indicates access technologies, services, and network capabilities provided by the network. The user device determines whether the user device is in a home network or a visited network based on the multi-bit network indication. The user device passes bits of the multi-bit network indication to an upper layer when the user device is in the home network or passes a portion of the bits of the multi-bit network indication to the upper layer when the user device is in the visited network. The user device receives a selection of one of the access technologies, the services, or the network capabilities, and receives, from the network, the one of the access technologies, the services, or the network capabilities for the user device based on the selection.

Abstract: A user device provides, to a network, information associated with the user device, and receives, from the network, a multi-bit network indication that indicates access technologies, services, and network capabilities provided by the network. The user device determines whether the user device is in a home network or a visited network based on the multi-bit network indication. The user device passes bits of the multi-bit network indication to an upper layer when the user device is in the home network or passes a portion of the bits of the multi-bit network indication to the upper layer when the user device is in the visited network. The user device receives a selection of one of the access technologies, the services, or the network capabilities, and receives, from the network, the one of the access technologies, the services, or the network capabilities for the user device based on the selection.

Abstract: A user device provides, to a network, information associated with the user device, and receives, from the network, a multi-bit network indication that indicates access technologies, services, and network capabilities provided by the network. The user device determines whether the user device is in a home network or a visited network based on the multi-bit network indication. The user device passes bits of the multi-bit network indication to an upper layer when the user device is in the home network or passes a portion of the bits of the multi-bit network indication to the upper layer when the user device is in the visited network. The user device receives a selection of one of the access technologies, the services, or the network capabilities, and receives, from the network, the one of the access technologies, the services, or the network capabilities for the user device based on the selection.

Abstract: A user device provides, to a network, information associated with the user device, and receives, from the network, a multi-bit network indication that indicates access technologies, services, and network capabilities provided by the network. The user device determines whether the user device is in a home network or a visited network based on the multi-bit network indication. The user device passes bits of the multi-bit network indication to an upper layer when the user device is in the home network or passes a portion of the bits of the multi-bit network indication to the upper layer when the user device is in the visited network. The user device receives a selection of one of the access technologies, the services, or the network capabilities, and receives, from the network, the one of the access technologies, the services, or the network capabilities for the user device based on the selection.

Abstract: A user device receives system information block data from a cell. The user device obtains, from the system information block data, cell metadata that includes a cellular parameter. The user device parses the cell metadata to identify the cellular parameter. The cellular parameter includes an upper layer indicator element, a public land mobile network (PLMN) information list element, and a network capability indicator element. The user device determines, based on the cellular parameter, that the cell is of a particular cell type of a plurality of cell types, and that the cell has a particular capability of a plurality of types of capabilities. The user device performs an action based on the particular cell type or the particular capability.

Abstract: A user device receives system information block data from a cell. The user device obtains, from the system information block data, cell metadata that includes a cellular parameter. The user device parses the cell metadata to identify the cellular parameter. The cellular parameter includes an upper layer indicator element, a public land mobile network (PLMN) information list element, and a network capability indicator element. The user device determines, based on the cellular parameter, that the cell is of a particular cell type of a plurality of cell types, and that the cell has a particular capability of a plurality of types of capabilities. The user device performs an action based on the particular cell type or the particular capability.

Abstract: A device may receive machine-to-machine (M2M) traffic associated with an M2M application. The device may determine parameters associated with managing the M2M traffic. The parameters may include information identifying a time window. The device may determine a weighted average traffic rate associated with the M2M traffic based on the parameters. The device may determine a holding time to be applied to the M2M traffic based on the weighted average traffic rate and the parameters. The device may determine an outgoing traffic rate to be applied to the M2M traffic based on the weighted average traffic rate and the parameters. The device may manage the M2M traffic based on the holding time and the outgoing traffic rate.

Abstract: Techniques described herein may provide for the organization and the control of nodes in an Machine to Machine (M2M) domain that is energy efficient and may provide for prioritized control of network traffic. Data may be received from of clusters of nodes in a M2M network, each of the clusters including one or more nodes to generate the data and a hub node to receive, from the one or more nodes, the generated data. The hub node may transmit the generated data. An update interval for the one or more nodes in each of the clusters may be set on a per-cluster basis and the update interval may define a period at which the one or more nodes in a particular cluster transmit data towards a corresponding hub node of the particular cluster. Additionally, an update interval for the hub node may be set, the update interval for the hub node being set on a per-cluster basis and defining a period at which the hub node transmits data.

Abstract: A device may receive machine-to-machine (M2M) traffic associated with two or more M2M applications. The M2M traffic may include information that identifies two or more priority levels associated with the M2M traffic. The device may determine parameters associated with managing the M2M traffic. The device may determine a traffic rate, an overall holding time, and an outgoing traffic rate associated with the M2M traffic. The device may determine a normalization factor based on the overall holding time and the parameters. The device may determine a set of priority level holding times based on the normalization factor, the overall holding time, and the parameters. Each priority level holding time may be associated with a priority level of the two or more priority levels. The device may manage the M2M traffic based on the set of priority level holding times and the outgoing traffic rate.

Abstract: A device may receive machine-to-machine (M2M) traffic associated with two or more M2M applications. The M2M traffic may include information that identifies two or more priority levels associated with the M2M traffic. The device may determine parameters associated with managing the M2M traffic. The device may determine a traffic rate, an overall holding time, and an outgoing traffic rate associated with the M2M traffic. The device may determine a normalization factor based on the overall holding time and the parameters. The device may determine a set of priority level holding times based on the normalization factor, the overall holding time, and the parameters. Each priority level holding time may be associated with a priority level of the two or more priority levels. The device may manage the M2M traffic based on the set of priority level holding times and the outgoing traffic rate.

Abstract: A device may receive machine-to-machine (M2M) traffic associated with an M2M application. The device may determine parameters associated with managing the M2M traffic. The parameters may include information identifying a time window. The device may determine a weighted average traffic rate associated with the M2M traffic based on the parameters. The device may determine a holding time to be applied to the M2M traffic based on the weighted average traffic rate and the parameters. The device may determine an outgoing traffic rate to be applied to the M2M traffic based on the weighted average traffic rate and the parameters. The device may manage the M2M traffic based on the holding time and the outgoing traffic rate.

Abstract: Techniques described herein may provide for the organization and the control of nodes in an Machine to Machine (M2M) domain that is energy efficient and may provide for prioritized control of network traffic. Data may be received from of clusters of nodes in a M2M network, each of the clusters including one or more nodes to generate the data and a hub node to receive, from the one or more nodes, the generated data. The hub node may transmit the generated data. An update interval for the one or more nodes in each of the clusters may be set on a per-cluster basis and the update interval may define a period at which the one or more nodes in a particular cluster transmit data towards a corresponding hub node of the particular cluster. Additionally, an update interval for the hub node may be set, the update interval for the hub node being set on a per-cluster basis and defining a period at which the hub node transmits data.

Abstract: Disclosed techniques provide enhanced security for a communications network. Access terminal devices intended for operation via the network are expected to have security agent functionality, e.g. in the form security agent software loaded into or otherwise enabled on each of the access terminal devices. Registration procedures include verification that such an agent is present/enabled on an access terminal and that the agent currently implemented on the terminal device provides adequate security for the communications network against malicious traffic from that device.

Abstract: Disclosed techniques provide enhanced security for a communications network. Access terminal devices intended for operation via the network are expected to have security agent functionality, e.g. in the form security agent software loaded into or otherwise enabled on each of the access terminal devices. Registration procedures include verification that such an agent is present/enabled on an access terminal and that the agent currently implemented on the terminal device provides adequate security for the communications network against malicious traffic from that device.

Abstract: The exemplary Multimedia Next Generation Network architecture disclosed herein covers the entire next generation system, e.g. for wireless communication services, including application, signaling and bearer functionalities. The architecture addresses unification of subscriber databases for both SIP services and non-SIP services in a Services Data Management Center (SDMC). A Security Center (SC) provides a central repository for all security related databases and functions. An Application Control Point (ACP) provides a single point of services control for all active SIP services for all subscribers via state information and services interaction management. Policy decisions are made at the packet layer, for example in an Advanced Bearer Control Point (ABCP) clustered with other functions to form a Bearer Services Control Point (BSCP). Policy enforcement is implemented at various nodes at the network or packet layer (L3) and above, e.g. including the BSCP and ACP.

Abstract: Disclosed techniques provide enhanced security for a communications network. Access terminal devices intended for operation via the network are expected to have security agent functionality, e.g. in the form security agent software loaded into or otherwise enabled on each of the access terminal devices. Registration procedures include verification that such an agent is present/enabled on an access terminal and that the agent currently implemented on the terminal device provides adequate security for the communications network against malicious traffic from that device.

Abstract: Disclosed techniques provide enhanced security for a communications network. Access terminal devices intended for operation via the network are expected to have security agent functionality, e.g. in the form security agent software loaded into or otherwise enabled on each of the access terminal devices. Registration procedures include verification that such an agent is present/enabled on an access terminal and that the agent currently implemented on the terminal device provides adequate security for the communications network against malicious traffic from that device.

Abstract: The exemplary Multimedia Next Generation Network architecture disclosed herein covers the entire next generation system, e.g. for wireless communication services, including application, signaling and bearer functionalities. The architecture addresses unification of subscriber databases for both SIP services and non-SIP services in a Services Data Management Center (SDMC). A Security Center (SC) provides a central repository for all security related databases and functions. An Application Control Point (ACP) provides a single point of services control for all active SIP services for all subscribers via state information and services interaction management. Policy decisions are made at the packet layer, for example in an Advanced Bearer Control Point (ABCP) clustered with other functions to form a Bearer Services Control Point (BSCP). Policy enforcement is implemented at various nodes at the network or packet layer (L3) and above, e.g. including the BSCP and ACP.