Abstract: A wireless communication network serves wireless User Equipment (UEs) over producer Network Functions (NFs) and consumer NFs that use Network Repository Function (NRFs). The producer NFs determine their NF identities and status. The producer NFs indicate the NF identities and status to the NRFs. The consumer NFs request NF information from the NRFs. The NRFs indicate the NF identities and status to the consumer NFs. The consumer NFs select NF identities based on the NF status. The consumer NFs exchange network signaling with the producer NFs based on the selected NF identities to serve the wireless UEs. The producer NFs may comprise Charging Functions (CHFs).

Abstract: Architecture that allows a user to control the way a connection is made to a destination is described. A destination can be tagged with an attribute that defines how the connection to that destination should be routed. For example, a phone address book allows the user not only to enter the usual call recipient information such as name and telephone number, but also to add an attribute in the form of a network identifier associated with a network to be used when connecting to the destination. Where multiple networks are associated with the destination, the phone subsystem, recognizing that the destination now has multiple network IDs for connecting the call, can prompt the user to select the desired network pathway. The user can also tag the destination with a protocol that should be employed. Thus, not only will the phone be connected according to the network, but also the protocol.

Abstract: Architecture that allows a user to control the way a connection is made to a destination is described. A destination can be tagged with an attribute that defines how the connection to that destination should be routed. For example, a phone address book allows the user not only to enter the usual call recipient information such as name and telephone number, but also to add an attribute in the form of a network identifier associated with a network to be used when connecting to the destination. Where multiple networks are associated with the destination, the phone subsystem, recognizing that the destination now has multiple network IDs for connecting the call, can prompt the user to select the desired network pathway. The user can also tag the destination with a protocol that should be employed. Thus, not only will the phone be connected according to the network, but also the protocol.

Abstract: Architecture that allows a user to control the way a connection is made to a destination is described. A destination can be tagged with an attribute that defines how the connection to that destination should be routed. For example, a phone address book allows the user not only to enter the usual call recipient information such as name and telephone number, but also to add an attribute in the form of a network identifier associated with a network to be used when connecting to the destination. Where multiple networks are associated with the destination, the phone subsystem, recognizing that the destination now has multiple network IDs for connecting the call, can prompt the user to select the desired network pathway. The user can also tag the destination with a protocol that should be employed. Thus, not only will the phone be connected according to the network, but also the protocol.

Abstract: Architecture that allows a user to control the way a connection is made to a destination is described. A destination can be tagged with an attribute that defines how the connection to that destination should be routed. For example, a phone address book allows the user not only to enter the usual call recipient information such as name and telephone number, but also to add an attribute in the form of a network identifier associated with a network to be used when connecting to the destination. Where multiple networks are associated with the destination, the phone subsystem, recognizing that the destination now has multiple network IDs for connecting the call, can prompt the user to select the desired network pathway. The user can also tag the destination with a protocol that should be employed. Thus, not only will the phone be connected according to the network, but also the protocol.

Abstract: Architecture that allows a user to control the way a connection is made to a destination. A destination can be tagged with an attribute that defines how the connection to that destination should be routed. For example, a phone address book allows the user not only to enter the usual call recipient information such as name and telephone number, but also to add an attribute in the form of a network identifier associated with a network that should be used when connecting to the destination. Where multiple networks are associated with the destination, the phone subsystem, recognizing that the destination now has multiple network IDs for connecting the call, can prompt the user to select the desired network pathway. The user can also tag the destination with a protocol that should be employed. Thus, not only will the phone be connected according to the network, but according to the protocol.

Abstract: Architecture that allows a user to control the way a connection is made to a destination. A destination can be tagged with an attribute that defines how the connection to that destination should be routed. For example, a phone address book allows the user not only to enter the usual call recipient information such as name and telephone number, but also to add an attribute in the form of a network identifier associated with a network that should be used when connecting to the destination. Where multiple networks are associated with the destination, the phone subsystem, recognizing that the destination now has multiple network IDs for connecting the call, can prompt the user to select the desired network pathway. The user can also tag the destination with a protocol that should be employed. Thus, not only will the phone be connected according to the network, but according to the protocol.

Abstract: Architecture that allows a user to control the way a connection is made to a destination. A destination can be tagged with an attribute that defines how the connection to that destination should be routed. For example, a phone address book allows the user to not only enter the usual call recipient information such as name and telephone number, but also to add an attribute in the form of a network identifier associated with a network that should be used when connecting to the destination. Where multiple networks are associated with the destination, the phone subsystem, recognizing that the destination now has multiple network IDs for connecting the call, can prompt the user to select the desired network pathway. The user can also tag the destination with a protocol that should be employed. Thus, not only will the phone be connected according to the network, but according to the protocol.

Abstract: A device that enable users to send and receive a message in different formats may include a text message gateway, an audio message gateway, and a processor. The text message gateway may include a Short Message Service (SMS) gateway. The audio message gateway may include an Interactive Voice Response (IVR) unit and/or a client application interface that receives audio from a client application of a mobile communications device. The processor may be configured to convert text messages received at the text-message gateway into audio messages and then to send the audio messages via the audio message gateway. The processor may also be configured to convert audio messages received at the audio message gateway into text messages and then to send the text messages via the text message gateway.

Abstract: Architecture that allows a user to control the way a connection is made to a destination. A destination can be tagged with an attribute that defines how the connection to that destination should be routed. For example, a phone address book allows the user to not only enter the usual call recipient information such as name and telephone number, but also to add an attribute in the form of a network identifier associated with a network that should be used when connecting to the destination. Where multiple networks are associated with the destination, the phone subsystem, recognizing that the destination now has multiple network IDs for connecting the call, can prompt the user to select the desired network pathway. The user can also tag the destination with a protocol that should be employed. Thus, not only will the phone be connected according to the network, but according to the protocol.

Abstract: Architecture that allows a user to control the way a connection is made to a destination. A destination can be tagged with an attribute that defines how the connection to that destination should be routed. For example, a phone address book allows the user to not only enter the usual call recipient information such as name and telephone number, but also to add an attribute in the form of a network identifier associated with a network that should be used when connecting to the destination. Where multiple networks are associated with the destination, the phone subsystem, recognizing that the destination now has multiple network IDs for connecting the call, can prompt the user to select the desired network pathway. The user can also tag the destination with a protocol that should be employed. Thus, not only will the phone be connected according to the network, but according to the protocol.

Abstract: A device that enable users to send and receive a message in different formats may include a text message gateway, an audio message gateway, and a processor. The text message gateway may include a Short Message Service (SMS) gateway. The audio message gateway may include an Interactive Voice Response (IVR) unit and/or a client application interface that receives audio from a client application of a mobile communications device. The processor may be configured to convert text messages received at the text-message gateway into audio messages and then to send the audio messages via the audio message gateway. The processor may also be configured to convert audio messages received at the audio message gateway into text messages and then to send the text messages via the text message gateway.

Abstract: Architecture that allows a user to control the way a connection is made to a destination. A destination can be tagged with an attribute that defines how the connection to that destination should be routed. For example, a phone address book allows the user to not only enter the usual call recipient information such as name and telephone number, but also to add an attribute in the form of a network identifier associated with a network that should be used when connecting to the destination. Where multiple networks are associated with the destination, the phone subsystem, recognizing that the destination now has multiple network IDs for connecting the call, can prompt the user to select the desired network pathway. The user can also tag the destination with a protocol that should be employed. Thus, not only will the phone be connected according to the network, but according to the protocol.

Abstract: A device that enable users to send and receive a message in different formats may include a text message gateway, an audio message gateway, and a processor. The text message gateway may include a Short Message Service (SMS) gateway. The audio message gateway may include an Interactive Voice Response (IVR) unit and/or a client application interface that receives audio from a client application of a mobile communications device. The processor may be configured to convert text messages received at the text-message gateway into audio messages and then to send the audio messages via the audio message gateway. The processor may also be configured to convert audio messages received at the audio message gateway into text messages and then to send the text messages via the text message gateway.

Abstract: A device that enable users to send and receive a message in different formats may include a text message gateway, an audio message gateway, and a processor. The text message gateway may include a Short Message Service (SMS) gateway. The audio message gateway may include an Interactive Voice Response (IVR) unit and/or a client application interface that receives audio from a client application of a mobile communications device. The processor may be configured to convert text messages received at the text-message gateway into audio messages and then to send the audio messages via the audio message gateway. The processor may also be configured to convert audio messages received at the audio message gateway into text messages and then to send the text messages via the text message gateway.

Abstract: A device that enable users to send and receive a message in different formats may include a text message gateway, an audio message gateway, and a processor. The text message gateway may include a Short Message Service (SMS) gateway. The audio message gateway may include an Interactive Voice Response (IVR) unit and/or a client application interface that receives audio from a client application of a mobile communications device. The processor may be configured to convert text messages received at the text-message gateway into audio messages and then to send the audio messages via the audio message gateway. The processor may also be configured to convert audio messages received at the audio message gateway into text messages and then to send the text messages via the text message gateway.

Abstract: The claimed subject matter provides systems and/or methods that facilitate sending a network initiated USSD message via a mixed network to user equipment. An application server component can communicate to user equipment. A location component can aggregate location data associated with the user equipment, wherein the location component can utilize the last known location data to send a network initiated USSD message to the user equipment via a mixed network.

Abstract: A device that enable users to send and receive a message in different formats may include a text message gateway, an audio message gateway, and a processor. The text message gateway may include a Short Message Service (SMS) gateway. The audio message gateway may include an Interactive Voice Response (IVR) unit and/or a client application interface that receives audio from a client application of a mobile communications device. The processor may be configured to convert text messages received at the text-message gateway into audio messages and then to send the audio messages via the audio message gateway. The processor may also be configured to convert audio messages received at the audio message gateway into text messages and then to send the text messages via the text message gateway.

Abstract: The claimed subject matter provides systems and/or methods that facilitate sending a network initiated USSD message via a mixed network to user equipment. An application server component can communicate to user equipment. A location component can aggregate location data associated with the user equipment, wherein the location component can utilize the last known location data to send a network initiated USSD message to the user equipment via a mixed network.

Abstract: The claimed subject matter provides systems and/or methods that facilitate sending a network initiated USSD message via a mixed network to user equipment. An application server component can communicate to user equipment. A location component can aggregate location data associated with the user equipment, wherein the location component can utilize the last known location data to send a network initiated USSD message to the user equipment via a mixed network.