Roaming support for software defined networking architecture in mobile network

A software defined networking controller can be provided to manage sharing of information relating to roaming requests for mobile devices that are roaming on visited networks. The software defined networking controller can be a sub-instance of a main software defined networking controller that manages traffic within the home network, and the software defined networking controller can sit at the edge of the home network and control edge routing elements. The edge software defined networking controller may communicate with roaming partner's edge software defined networking controller and/or with the roaming interconnect operator's software defined networking controller to exchange roaming related information.

TECHNICAL FIELD

The subject disclosure relates to roaming support on a software defined networking architecture mobile network.

BACKGROUND

Widespread proliferation of wireless broadband networks offers increased quality of experience for mobile users, but also renders management and maintenance of these networks a tedious and costly task. The network core, which facilitates mobile management and data transfer is traditionally comprised of individual server elements with each piece of hardware performing a dedicated task. Several of the server elements perform control plane functions of managing subscription information, traffic management and data routing. This routing can be especially complicated with roaming operations as information needs to be exchanged seamlessly between multiple operator domains. Additionally, once a roaming connection has been established, service sensitive routing may need to be established for end to end traffic.

As mobile device users travel, provision of mobile services across different operator domains will be provided. In order to support roaming services, mobile networks will need to exchange information with each other about subscription information related to the mobile device users.

DETAILED DESCRIPTION

A network core with a software defined networking (“SDN”) controller is provided to control routing of traffic within the network and between the network and the traffic destination. The SDN controller is merged with existing 3rdGeneration Partnership Project (“3GPP”) network architecture to enable service deliveries via open application programming interfaces (“APIs”) and move the network core towards an all internet protocol (“IP”), cloud based, and software driven telecom network. The SDN controller can work with, or take the place of policy and charging rules function (“PCRF”) network elements so that policies such as quality of service and traffic management and routing can be synchronized and managed end to end.

An SDN controller can be provided to manage sharing of information relating to roaming requests for mobile devices that are roaming on visited networks. The SDN controller can be a sub-instance of a main SDN controller that manages traffic within the home network, and the SDN controller can sit at the edge of the home network and control edge routing elements. The edge SDN controller may communicate with roaming partner's edge SDN controller and/or with the roaming interconnect operator's SDN controller to exchange roaming related information. This exchange mechanism will provides a consistent user experience while roaming and will provide operators flexibility in providing service chaining based on services, applications, network conditions, subscriber preferences, etc.

In an embodiment, the SDN controller on a home network can receive service profile requests from legacy PCRF network elements on a roaming network. The service profile request protocols from the PCRF may differ from a SDN protocol, and the SDN controller can translate the non-compatible protocol to match the SDN protocol. In other embodiments, the SDN controller can enable ‘local breakout’ which enables the roaming mobile device to use a packet data network gateway (“PGW”) on the roaming network while roaming. This allows the mobile device to experience home-style services while roaming.

For these considerations as well as other considerations, in one or more embodiments, a software defined networking controller includes a processor and a memory that stores executable instructions that when executed by the processor, facilitate performance of operations, including receiving a service profile request from another software defined networking controller of a visited mobile network, wherein the service profile request is associated with a mobile device that is roaming on the visited mobile network. The operations can also include retrieving service profile information from a policy data store of a home mobile network of the mobile device. The operations can further include initiating transmission of the service profile information about the mobile device to the other software defined networking controller.

In an embodiment, a method can comprise receiving, by a first software defined networking controller comprising a processor, a service profile request from a second software defined networking controller of a visited mobile network, wherein the service profile request is associated with a mobile device that is determined to be roaming on the visited mobile network. The method can also comprise collecting, by the first software defined networking controller, service profile information associated with the mobile device from a policy data store of a home mobile network for the mobile device. The method can also include sending, by the first software defined networking controller, the service profile information to the second software defined networking controller of the visited mobile network.

In another embodiment, a computer-readable storage device having instructions stored thereon that, in response to execution, cause a software defined networking controller comprising a processor to perform operations including receiving a service profile request of a mobile device from another second software defined networking controller of a roaming network on which the mobile device is roaming. The operations can also include collecting service profile information from a policy data store of a home network of the mobile device. The operations can further include sending the service profile information about the mobile device to the second software defined networking controller of the roaming network.

Turning now toFIG. 1, illustrated is an exemplary a block diagram showing a software defined networking architecture100that provides roaming support in accordance with various aspects described herein. A home network102can be a mobility core network and can contain core network elements in the user plane and control plane that enable mobile devices on the network to transfer data to and from an external packet network.

One such element in the home network102is a packet data network gateway (“PGW”)104. POW104can receive packets or other data transmissions from one or more Evolved Node Bs that are the hardware that is communicably coupled to the mobile phone network that communicates directly with mobile devices. The PGW104can receive packets from the eNodeB via a serving gateway (“SGW”) (not shown) that is provided to route and forward data packets received from the mobile devices while PGW104is provided to facilitate connectivity between the mobile devices and the external packet data networks.

In an embodiment, a PGW104can provide services for a mobile device112, even when the mobile device112is connected to a visited network110. The visited network110can be a roaming network where the mobile device112is able to connect but the visited network110may not be a native network for the mobile device112.

The SDN controller106can provide traffic management control for packets received from the mobile device via visited network110at the PGW104, and can also provide traffic management for packets forwarded back to the mobile device112from an external packet network. The SDN controller106can apply rules and policies based on user related information and subscription material available in a policy database108.

In an embodiment, when mobile device112first accesses visited network110, visited network110can determine which network mobile device112belongs on (i.e., home network102). Visited network110will then send a service profile request to the home network102requesting service profile information such as subscription level, subscription service types, QoS levels for various applications such as voice and video, related network parameters, and service specific routing information such as lawful intercept. An SDN controller106that is specifically configured to be logically located on the edge of the home network102can intercept these service profile requests and retrieve the relevant service profile information from policy database108on home network102. SDN controller106can identify the relevant service profile information using mobile device identifiers in the service profile request, such as the international mobile subscriber identity (“IMSI”), or the mobile subscriber ISDN number (“MSISDN”).

Once the service profile information is retrieved from the policy database108, the service profile information can be transmitted by the SDN controller106to the visited network110. The service profile information can then be used by visited network110in facilitating the connection of the mobile device112the visited network. In an embodiment, PGW104can receive data sent from the mobile device112to the visited network110, and then provide the routing and data connection to an external packet network (e.g., Internet). In other embodiments, using local breakout, user plane functionality for the mobile device112can be provided by a PGW located at the visited network110.

Turning now toFIG. 2, illustrated is an example, non-limiting embodiment of a block diagram200showing a software defined networking architecture that provides roaming support in accordance with various aspects described herein.

A home network202can be a mobility core network and can contain core network elements in the user plane and control plane that enable mobile devices on the network to transfer data to and from an external packet network. A visited network204can be part of another mobility core network but the visited network204may allow mobile devices, such as mobile device210to roam on the visited network.

In an embodiment, when mobile device210first accesses visited network204, visited network204can determine which network mobile device210belongs to (i.e., home network202). Visited network204may then send a service profile request to the home network202requesting service profile information such as subscription level, subscription service types, QoS levels for various applications such as voice and video, related network parameters, and service specific routing information such as lawful intercept. An edge SDN controller206that is specifically configured to facilitate roaming operations can intercept these service profile requests and retrieve the relevant service profile information from a policy database on home network202. Edge SDN controller206can identify the relevant service profile information using mobile device identifiers in the service profile request, such as the international mobile subscriber identity (“IMSI”), or the mobile subscriber ISDN number (“MSISDN”).

Once the service profile information is retrieved from the policy database, the service profile information can be transmitted by the edge SDN controller206to an edge SDN controller208on the visited network204. The service profile information can then be used by visited network204in facilitating the connection of the mobile device210the visited network. In an embodiment, a PGW on the home network can receive data sent from the mobile device210to the visited network204, and then provide the routing and data connection to an external packet network (e.g., Internet). In other embodiments, using local breakout, user plane functionality for the mobile device210can be provided by a PGW located at the visited network204.

Turning now toFIG. 3, shown is an example, non-limiting embodiment of a block diagram300showing a software defined networking architecture that provides roaming support in accordance with various aspects described herein.

A home network302can be a mobility core network and can contain core network elements in the user plane and control plane that enable mobile devices on the network to transfer data to and from an external packet network. A visited network308can be part of another mobility core network but the visited network308may allow mobile devices, such as mobile device314to roam on the visited network.

In an embodiment, when mobile device314first accesses visited network308, visited network308can determine which network mobile device314belongs to (i.e., home network302). Visited network308may then send a service profile request to the home network302requesting service profile information such as subscription level, subscription service types, QoS levels for various applications such as voice and video, related network parameters, and service specific routing information such as lawful intercept. An edge SDN controller302that is specifically configured to facilitate roaming operations can intercept these service profile requests and forward the service profile requests to a main SDN controller304that can retrieve the relevant service profile information from a policy database on home network302. Main SDN controller304can identify the relevant service profile information using mobile device identifiers in the service profile request, such as the international mobile subscriber identity (“IMSI”), or the mobile subscriber ISDN number (“MSISDN”). In other embodiments, the edge SDN controller can identify and retrieve the relevant service profile information directly from the policy database.

Once the service profile information is retrieved from the policy database, the service profile information can be transmitted by the edge SDN controller306to an edge SDN controller312on the visited network308. The service profile information can then be used by main SDN controller310on visited network308in facilitating the connection of the mobile device314to the visited network.

Turning now toFIG. 4, illustrated is a example, non-limiting embodiment of a block diagram400showing a software defined networking architecture that provides roaming support with a roaming operator in accordance with various aspects described herein.

A home network402can be a mobility core network and can contain core network elements in the user plane and control plane that enable mobile devices on the network to transfer data to and from an external packet network. A visited network408can be part of another mobility core network but the visited network408may allow mobile devices, such as mobile device414to roam on the visited network.

In an embodiment, when mobile device414first accesses visited network408visited network408may then send a service profile request a roaming operator418that has an interconnect SDN controller416. Interconnect SDN controller416can determine that home network402is associated with mobile device414and forward the service profile request to the home network402requesting service profile information such as subscription level, subscription service types, QoS levels for various applications such as voice and video, related network parameters, and service specific routing information such as lawful intercept. An edge SDN controller406that is specifically configured to facilitate roaming operations can intercept these service profile requests and forward the service profile requests to a main SDN controller404that can retrieve the relevant service profile information from a policy database on home network402. Main SDN controller404can identify the relevant service profile information using mobile device identifiers in the service profile request, such as the international mobile subscriber identity (“IMSI”), or the mobile subscriber ISDN number (“MSISDN”). In other embodiments, the edge SDN controller can identify and retrieve the relevant service profile information directly from the policy database.

Once the service profile information is retrieved from the policy database, the service profile information can be transmitted by the edge SDN controller406to the interconnect SDN controller416at the roaming operator418, and then interconnect SDN controller416can forward the service profile information to edge SDN controller412on the visited network408. The service profile information can then be used by main SDN controller410on visited network408in facilitating the connection of the mobile device414to the visited network.

Turning now toFIG. 5, illustrated is a block diagram showing a software defined networking architecture that provides roaming support in accordance with various aspects described herein.

A home network502can be a mobility core network and can contain core network elements in the user plane and control plane that enable mobile devices on the network to transfer data to and from an external packet network. A visited network508can be part of another mobility core network but the visited network508may allow mobile devices, such as mobile device512to roam on the visited network.

In an embodiment, when mobile device512first accesses visited network508, visited network508can determine which network mobile device512belongs to (i.e., home network502). Visited network508may then send a service profile request to the home network502requesting service profile information such as subscription level, subscription service types, QoS levels for various applications such as voice and video, related network parameters, and service specific routing information such as lawful intercept.

In an embodiment, a legacy PCRF510on visited network508can send the service profile request in a non-SDN compatible protocol. The edge SDN controller506can translate the service profile request into a SDN compatible protocol and forward the request to the MAIN SDN controller504or execute the request at the edge SDN controller506. Once the service profile information is retrieved, edge SDN controller506can transmit the service profile information back to the PCRF510in a protocol compatible with the PCRF510.

Turning now toFIG. 6, illustrated is a block diagram600showing a software defined networking architecture that provides roaming support with a roaming operator in accordance with various aspects described herein.

A home network602can be a mobility core network and can contain core network elements in the user plane and control plane that enable mobile devices on the network to transfer data to and from an external packet network. A visited network608can be part of another mobility core network but the visited network608may allow mobile devices, such as mobile device612to roam on the visited network.

In an embodiment, when mobile device612first accesses visited network608visited network608may then send a service profile request a roaming operator616that has an interconnect SDN controller614. The service profile request can be sent by a legacy PCRF610on visited network608using a non-SDN compatible protocol. Interconnect SDN controller can translate the request to a SDN compatible protocol, and then forward the service profile request to the home network602requesting service profile information. An edge SDN controller606that is specifically configured to facilitate roaming operations can intercept these service profile requests and forward the service profile requests to a main SDN controller604that can retrieve the relevant service profile information from a policy database on home network602. Main SDN controller604can identify the relevant service profile information using mobile device identifiers in the service profile request, such as the international mobile subscriber identity (“IMSI”), or the mobile subscriber ISDN number (“MSISDN”). In other embodiments, the edge SDN controller can identify and retrieve the relevant service profile information directly from the policy database.

Once the service profile information is retrieved from the policy database, the service profile information can be transmitted by the edge SDN controller606to the interconnect SDN controller614at the roaming operator616, and then interconnect SDN controller614can forward the service profile information to PCRF610after translating it back to the PCRF610compatible protocol. The service profile information can then be used by PCRF610on visited network608in facilitating the connection of the mobile device612to the visited network.

FIG. 7illustrates a flow diagram of an example, non-limiting embodiment of a method700for performing traffic control management. At702, the method comprises receiving, by a first software defined networking controller comprising a processor, a service profile request from a second software defined networking controller of a visited mobile network, wherein the service profile request is associated with a mobile device that is determined to be roaming on the visited mobile network. At704the method includes collecting, by the first software defined networking controller, service profile information associated with the mobile device from a policy data store of a home mobile network for the mobile device.

At706, the method can include sending, by the first software defined networking controller, the service profile information to the second software defined networking controller of the visited mobile network.

FIG. 8illustrates a flow diagram of an example, non-limiting embodiment of a method800for performing traffic control management. At802, the method comprises receiving, by the first software defined networking controller, a second service profile request in a format confirming to a non-software defined networking protocol applied by a policy charging and rules function network element on the visited mobile network. At804, the method comprises translating, by the first software defined networking controller, a protocol of the non-software defined networking protocol, to which the second service profile request conforms, to a software defined networking protocol.

At806, the method can comprise collecting, by the first software defined networking controller, second service profile information based on the translated second service profile request. At808, the method can include sending, by the first software defined networking controller, the second service profile information according to the non-software defined networking protocol to the policy charging and rules function network element of the visited mobile network.

Referring now toFIG. 9, there is illustrated a block diagram of a computing environment in accordance with various aspects described herein. For example, in some embodiments, the computer can be or be included within the radio repeater system disclosed in any of the previous systems200,300,400,500,600and/or700.

Computing devices typically include a variety of media, which can include computer-readable storage media and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data or unstructured data.

With reference again toFIG. 9, the example environment900for implementing various embodiments of the aspects described herein includes a computer902, the computer902including a processing unit904, a system memory906and a system bus908. The system bus908couples system components including, but not limited to, the system memory906to the processing unit904. The processing unit904can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures can also be employed as the processing unit904.

The system bus908can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory906includes ROM910and RAM912. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer902, such as during startup. The RAM912can also include a high-speed RAM such as static RAM for caching data.

The computer902further includes an internal hard disk drive (HDD)914(e.g., EIDE, SATA), which internal hard disk drive914can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD)916, (e.g., to read from or write to a removable diskette918) and an optical disk drive920, (e.g., reading a CD-ROM disk922or, to read from or write to other high capacity optical media such as the DVD). The hard disk drive914, magnetic disk drive916and optical disk drive920can be connected to the system bus908by a hard disk drive interface924, a magnetic disk drive interface926and an optical drive interface928, respectively. The interface924for external drive implementations includes at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

A number of program modules can be stored in the drives and RAM912, including an operating system930, one or more application programs932, other program modules934and program data936. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM912. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer902through one or more wired/wireless input devices, e.g., a keyboard938and a pointing device, such as a mouse940. Other input devices (not shown) can include a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, touch screen or the like. These and other input devices are often connected to the processing unit904through an input device interface942that can be coupled to the system bus908, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR interface, etc.

A monitor944or other type of display device can be also connected to the system bus908via an interface, such as a video adapter946. In addition to the monitor944, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

The computer902can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s)948. The remote computer(s)948can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically includes many or all of the elements described relative to the computer902, although, for purposes of brevity, only a memory/storage device950is illustrated. The logical connections depicted include wired/wireless connectivity to a local area network (LAN)952and/or larger networks, e.g., a wide area network (WAN)954. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer902can be connected to the local network952through a wired and/or wireless communication network interface or adapter956. The adapter956can facilitate wired or wireless communication to the LAN952, which can also include a wireless AP disposed thereon for communicating with the wireless adapter956.

When used in a WAN networking environment, the computer902can include a modem958or can be connected to a communications server on the WAN954or has other means for establishing communications over the WAN954, such as by way of the Internet. The modem958, which can be internal or external and a wired or wireless device, can be connected to the system bus908via the input device interface942. In a networked environment, program modules depicted relative to the computer902or portions thereof, can be stored in the remote memory/storage device950. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

In an embodiment of the subject application, the computer902can provide the environment and/or setting in which one or more of the core mobility networks disclosed inFIGS. 1-6can be operated from. For instance, the edge SDN controllers disclosed herein can be applications932stored in hard drive914and executed by processing unit904.

FIG. 10illustrates a high-level block diagram that depicts an example LTE network architecture1000that can employ the disclosed communication architecture. The evolved RAN for LTE consists of an eNodeB (eNB)1002that can facilitate connection of MS1004to an evolved packet core (EPC) network. In one aspect, the MS1004is physical equipment or Mobile Equipment (ME), such as a mobile phone or a laptop computer that is used by mobile subscribers, with a Subscriber identity Module (SIM). The SIM is associated with a CTN, an International Mobile Subscriber Identity (IMSI), IMEI, and/or MSISDN, which is a unique identifier of a subscriber. The MS1004includes an embedded client that receives and processes messages received by the MS1004. As an example, the embedded client can be implemented in JAVA. It is noted that MS1004can be substantially similar mobile devices412and414or512and514.

The connection of the MS1004to the evolved packet core (EPC) network is subsequent to an authentication, for example, a SIM-based authentication between the MS1004and the evolved packet core (EPC) network. In one aspect, the MME1006provides authentication of the MS1004by interacting with the HSS1008. The HSS1008contains a subscriber profile and keeps track of which core network node is currently handling the subscriber. It also supports subscriber authentication and authorization functions (AAA). In networks with more than one HSS1008, a subscriber location function provides information on the HSS1008that contains the profile of a given subscriber.

As an example, the eNB1002can host a PHYsical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Control Protocol (PDCP) layers that include the functionality of user-plane header-compression and encryption. In addition, the eNB1002can implement at least in part Radio Resource Control (RRC) functionality (e.g., radio resource management, admission control, scheduling, cell information broadcast, etc.). The eNB1002can be coupled to a serving gateway (SGW)1010that facilitates routing of user data packets and serves as a local mobility anchor for data bearers when the MS1004moves between eNBs. In addition, the SGW1010can act as an anchor for mobility between LTE and other 3GPP technologies (GPRS, UMTS, etc.). When MS1004is in an idle state, the SGW1010terminates a downlink (DL) data path and triggers paging when DL data arrives for the MS1004. Further, the SGW1010can perform various administrative functions in the visited network such as collecting information for charging and lawful interception.

In one aspect, the SGW1010can be coupled to a Packet Data Network Gateway (PDN GW)1012that provides connectivity between the MS1004and external packet data networks such as IP service(s)/network(s)1014. Moreover, the PDN GW1012is a point of exit and entry of traffic for the MS1004. It is noted that the MS1004can have simultaneous connectivity with more than one PDN GW (not shown) for accessing multiple PDNs.

The PDN GW1012performs IP address allocation for the MS1004, as well as QoS enforcement and implements flow-based charging according to rules from a Policy Control and Charging Rules Function (PCRF)1016. The PCRF1016can facilitate policy control decision-making and control flow-based charging functionalities in a Policy Control Enforcement Function (PCEF), which resides in the PDN GW1012. The PCRF1016can store data (e.g., QoS class identifier and/or bit rates) that facilitates QoS authorization of data flows within the PCEF. In one aspect, the PDN GW1012can facilitate filtering of downlink user IP packets into the different QoS-based bearers and perform policy enforcement, packet filtering for each user, charging support, lawful interception and packet screening. Further, the PDN GW acts as the anchor for mobility between 3GPP and non-3GPP technologies such as WiMAX and 3GPP2 (CDMA1X and EvDO). Although a LTE network architecture1000is described and illustrated herein, it is noted that most any communication network architecture can be utilized to implement the disclosed embodiments.

Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.