System, method, and computer program for dynamically adapting to over-the-top (OTT) call routing

Abstract

A method for setting a policy for over-the-top (OTT) calls in a mobile network is provided. The method includes determining whether a cell of the mobile network has at least one neighboring cell of at least one roaming partner of the mobile network, and determining a bearer policy for routing OTT calls in the cell based on whether the cell is determined to have at least one neighboring cell of the at least one roaming partner. The determined bearer policy indicates whether the OTT calls in the cell should be routed over a dedicated bearer or a default bearer for connecting to an Internet Access Point Name (APN).

Description

Technical Field

[0001] The present disclosure generally relates to roaming interoperability for over-the-top (OTT) call routing.

Background Art

[0002] A roaming partner has specific policies for allowing or denying a bearer according to the packet data network (PDN) to which the bearer corresponds. One of the policies of the roaming operator can be to deny any bearer at the Internet access point name (APN) separate from the default bearer. Thus, existing sessions (e.g., over-the-top (OTT) application calls or sessions) routed over a non-default Internet APN bearer (e.g., a dedicated Internet APN bearer) of the home operator may have problems when migrating (or handing over) from a touch point or cell of the home operator to a touch point or cell of the roaming operator. Specifically, the roaming operator may deny the dedicated bearer, resulting in problems such as call mute and session disconnection. As a result, the user's perception deteriorates while moving between the home operator and the roaming operator.

Summary of the Invention

[0003] One or more exemplary embodiments provide a system and method for dynamically adapting a bearer to enhance interaction with a roaming touch point and to enhance the voice quality of an over-the-top (OTT) application during migration between home and roaming operator touch points.

[0004] According to one aspect of the present disclosure, a method for setting a policy for OTT calls in a mobile network is provided. The method may include determining whether a cell of the mobile network has at least one adjacent cell of at least one roaming partner of the mobile network, and determining a bearer policy for routing OTT calls in the cell based on whether the cell is determined to have at least one adjacent cell of at least one roaming partner. The determined bearer policy may indicate whether an OTT call in the cell should be routed on a dedicated bearer or a default bearer for connecting to an Internet access point name (APN).

[0005] According to one aspect of the present disclosure, a system for setting a policy for OTT calls in a mobile network is provided. The system may include a memory storing instructions, and a processor configured to execute the instructions to determine whether a cell of the mobile network has at least one adjacent cell of at least one roaming partner of the mobile network, and to determine a bearer policy for routing OTT calls in the cell based on whether the cell is determined to have at least one adjacent cell of at least one roaming partner. The determined bearer policy may indicate whether an OTT call in the cell should be routed on a dedicated bearer or a default bearer for connecting to an Internet APN.

[0006] According to one aspect of the present disclosure, a non-transitory computer-readable storage medium for setting a policy for OTT calls in a mobile network is provided. The storage medium may be connected to one or more processors and may be configured to store instructions that, when executed, cause the one or more processors to determine whether a cell of the mobile network has at least one adjacent cell of at least one roaming partner of the mobile network, and to determine a bearer policy for routing an OTT call in the cell based on whether the cell is determined to have at least one adjacent cell of at least one roaming partner. The determined bearer policy can indicate whether an OTT call in the cell should be routed on a dedicated bearer or a default bearer for connecting to an Internet APN.

[0007] Further aspects are described in part in the following description, and in part will be apparent from the description, or can be learned by practice of the presented embodiments of the present disclosure.

Brief Description of the Drawings

[0008] The above and other aspects, features, and aspects of the embodiments of the present disclosure will become apparent from the following description in conjunction with the accompanying drawings.

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Modes for Carrying Out the Invention

[0010] The following detailed description of the exemplary embodiments refers to the accompanying drawings. The same reference numbers in the various drawings may identify the same or similar elements.

[0011] FIG. 1 is a diagram of a system according to one embodiment. FIG. 1 includes a user device 110, a server device 120, and a network 130. The user device 110 and the server device 120 can be interconnected via a wired connection, a wireless connection, or a combination of a wired connection and a wireless connection.

[0012] The user device 110 can include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server device, etc.), a mobile phone (e.g., a smartphone, a wireless phone, etc.), a camera device, a wearable device (e.g., smart glasses or a smartwatch), or a similar device.

[0013] The server device 120 can include one or more devices. For example, the server device 120 can be a server device, a computer device, etc.

[0014] The network 130 can include one or more wired and / or wireless networks. For example, the network 130 can include a cellular network (e.g., a fifth generation (5G) network, a long term evolution (LTE) network, a third generation (3G) network, a code division multiple access (CDMA) network, etc.), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., a public switched telephone network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, an optical fiber-based network, etc., and / or a combination of these or other types of networks.

[0015] The number and arrangement of the devices and networks shown in FIG. 1 are provided as an example. In practice, additional devices and / or networks, fewer devices and / or networks, various devices and / or networks, or devices and / or networks with an arrangement different from those shown in FIG. 1 may exist. Further, two or more devices shown in FIG. 1 may be implemented within a single device, or a single device shown in FIG. 1 may be implemented as a plurality of distributed devices. In addition to or instead of this, a set of devices (e.g., one or more devices) may perform one or more functions described as being performed by another set of devices.

[0016] FIG. 2 is a diagram of components of one or more of the devices of FIG. 1 according to an embodiment. Device 200 can correspond to user device 110 and / or server device 120.

[0017] As shown in FIG. 2, device 200 may include bus 210, processor 220, memory 230, storage component 240, input component 250, output component 260, and communication interface 270.

[0018] Bus 210 may include components that enable communication between components of device 200. Processor 220 can be implemented in hardware, firmware, or a combination of hardware and software. Processor 220 can be a central processing unit (CPU), a graphics processing unit (GPU), an acceleration processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or another type of processing component. Process 220 can include one or more processors that can be programmed to perform functions.

[0019] Memory 230 may include a random access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) for storing information and / or instructions for use by processor 220.

[0020] Storage component 240 can store information and / or software related to the operation and use of device 200. For example, storage component 240, together with a corresponding drive, may include a hard disk (e.g., magnetic disk, optical disk, magneto-optical disk, and / or solid state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium.

[0021] Input component 250 may include components that enable device 200 to receive information via user input (e.g., touch screen display, keyboard, keypad, mouse, button, switch, and / or microphone), etc. Input component 250 may include sensors for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, and / or an actuator).

[0022] Output component 260 may include components that provide output information from device 200 (e.g., a display, a speaker, and / or one or more light emitting diodes (LEDs)).

[0023] The communication interface 270 may include components such as a transceiver (e.g., a transceiver and / or a separate receiver and transmitter) that enable the device 200 to communicate with other devices via, for example, a wired connection, a wireless connection, or a combination of a wired and a wireless connection. The communication interface 270 may enable the device 200 to receive information from and / or provide information to other devices. For example, the communication interface 270 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a universal serial bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

[0024] The device 200 may perform one or more of the processes described herein. The device 200 may operate based on a processor 220 that executes software instructions stored by a non-transitory computer-readable medium such as the memory 230 and / or the storage component 240. The computer-readable medium is defined herein as a non-transitory memory device. The memory device includes a memory space within a single physical memory device or a memory space spanning multiple physical memory devices.

[0025] The software instructions may be read into the memory 230 and / or the storage component 240 from another computer-readable medium or from another device via the communication interface 270. When executed, the software instructions stored in the memory 230 and / or the storage component 240 may cause the processor 220 to perform one or more of the processes described herein.

[0026] In addition to or instead of software instructions, hardwired circuitry may be used, either in place of or in combination with software instructions, to perform one or more of the processes described herein. Accordingly, the embodiments described herein are not limited to any particular combination of hardware circuitry and software.

[0027] For a home operator, an OTT session may be established by a user equipment (UE) or a terminal (e.g., the device 110 in FIG. 1) according to a policy defined by the home operator (e.g., a server of the home operator such as the server 120 in FIG. 1 or a server accessible by the home operator), and a call may be routed on any dedicated or default bearer riding on an Internet APN according to the policy. Thus, for example, in order to reject any bearer other than the default bearer established on the Internet APN, such a call or session routed on a dedicated bearer according to the home operator policy may be dropped during handover to a roaming operator during an active session due to a policy on the roaming operator core (e.g., a Mobility Management Entity (MME)).

[0028] To prevent dropped calls and sessions, the system may determine a site (e.g., a cell) having one or more roaming touch points and a site having only non-roaming touch points from an adjacent table (e.g., determine adjacent cells and determine whether the adjacent cells are roaming partners). The system can dynamically route calls according to the home operator's policy while on a non-roaming touch point. The system may re-route a call to the default bearer on the Internet APN at a site of the home PLMN determined to include a roaming touch point. The system can hand over an OTT session from a site of the home operator having a roaming touch point to a site of the roaming operator on the default bearer established on the Internet APN. Also, the system can start suppressing the triggering of an OTT call originated from a roaming partner area.

[0029] FIG. 3 is a diagram of a network according to an embodiment. The network may include a home operator 302 and a roaming partner 304. The home operator 302 may have a corresponding home operator non-roaming area 306 and a home operator roaming boundary 308. In the home operator non-roaming area 306 (i.e., an area determined to have no roaming touch points, for example, information maintained and updated at an external node or server 120 of the home operator 302, or information accessible by the home operator), the home operator 302 may operate with a default bearer (Internet APN) 310 and a dedicated bearer (Internet APN) 312. At the home operator roaming boundary 308, the home operator 302 may operate using the default bearer 310. The roaming partner 304 may operate using a default bearer (Internet APN) 314. The roaming partner 304 may include an area 316 disposed proximate to the home operator roaming border 308. A system and method for OTT call routing in the network shown in FIG. 3 are described below.

[0030] FIG. 4 is a flowchart of a method of OTT call routing according to an embodiment. In operation 402, a system (e.g., an external node or server 120 accessible by a home operator) determines a home operator node type. For example, the external node or server 120 may determine whether at least one neighboring cell of the current site (i.e., the home operator site for which a policy is to be determined according to operations 402, 404) belongs to a roaming PLMN from an existing neighboring table of the home operator site. Based on at least one neighboring cell belonging to a roaming PLMN, the system (e.g., server 120) can determine that the site has a roaming touch point and classify the site accordingly (e.g., as "having a roaming touch point"). If the system determines that none of the neighboring cells of the current site or cell belong to a roaming PLMN, the system can determine that the site or cell does not have a roaming touch point and classify the site accordingly (e.g., as "not having a roaming touch point"). The system can determine the home operator node type periodically, at a predetermined time interval, in response to a request to perform the determination, etc. (e.g., as set by an operator).

[0031] In operation 404, the system determines the home operator policy (e.g., bearer policy) for the OTT call of the current site. The operator policy for the OTT call may be obtained based on a policy for determining the quality of service (QoS) class indicator (QCI) (e.g., dedicated or default) to be established and a charging rule function (PCRF), from an application server corresponding to the OTT application and the reception of an RX trigger from the corresponding linked bearer for which the same QCI is to be established. For example, the operation may determine to have OTT media on dedicated bearers of QCI1 - QCI4 while having corresponding signaling on the default bearers of QCI6 - QCI9. In this example, QCI5 is the default bearer of the IP multimedia subsystem (IMS) PDN and is used for the voice over long term evolution (VoLTE) session, so it is not part of the list.

[0032] In operation 406, the system determines the OTT call routing behavior. In operation 406, the system can determine whether the OTT call should be routed on a dedicated bearer or on a default bearer. For example, if it is determined that the home operator node type has a roaming touch point (i.e., it is determined that it "has a roaming touch point"), and the home operator policy for the OTT call corresponds to the OTT media on the dedicated bearer (e.g., Internet APN), and the OTT call routing operation is signaling on the default bearer, the system can receive the dedicated bearer details corresponding to the OTT media from the home operator policy for the OTT call (e.g., QCI3 / QCI4). The system can receive the activation state within the radio access network (RAN) corresponding to the dedicated bearer corresponding to the home operator policy. If the activation state indicates that the dedicated bearer is enabled to route the OTT call in the cell, the system can update the activation state on the RAN from enabled to disabled. If the activation state indicates that the dedicated bearer is disabled to route the OTT call in the cell, the system can determine that no further action is required.

[0033] On the one hand, if it is determined that the current site or cell's home operator node type does not have a roaming touch point (e.g., determined as "not having a roaming touch point"), and the home operator policy for OTT calls supports OTT media on a dedicated bearer (e.g., Internet APN), and the OTT call routing operation is signaling on the default bearer, the system can receive the dedicated bearer details corresponding to the OTT media from the home operator policy for OTT calls. The system can receive the activation state within the RAN corresponding to the dedicated bearer corresponding to the home operator policy. If the activation state indicates that the dedicated bearer is deactivated for routing OTT calls in the cell, the system can update the activation state on the RAN from deactivated to activated. If the activation state indicates that the dedicated bearer is activated for routing OTT calls in the cell, the system can determine that no further action is required.

[0034] In a further example, if it is determined that the home operator node type has a roaming touch point or does not have a roaming touch point, and the home operator policy for OTT calls supports OTT media on the default bearer (e.g., Internet APN), and the OTT call routing operation is signaling on the default bearer, the system can determine that no further action is required because the home operator policy for OTT calls is OTT media on the default bearer.

[0035] Before the policy change, the system may determine the active calls in the cell and the active calls where the user is between the home operator and the roaming operator. After the policy change, the system can use the existing policy for the active calls on the cell at the time of the policy change and can use the new policy for the active calls where the user is between the home operator and the roaming operator. For subsequent calls, the system can use the new policy.

[0036] In operation 408, the system can perform a handover between the home operator and the roaming touch point. For example, after operation 406, the system can hand over the OTT session from the home operator node classified as having a "roaming touch point" to the roaming partner.

[0037] In operation 410, the system generates an RX trigger to suppress OTT calls originated from the roaming partner area. In the case of a new call originated from the roaming partner area or the home network area, the OTT application server can initiate an EX trigger towards the PCRF of the home operator. However, this may cause a failure on the roaming operator where the policy is not set to activate a dedicated bearer on the Internet APN, resulting in call failure. To avoid this, the PCRF can determine whether the Mobile Country Code (MCC) / Mobile Network Code (MNC) in the RX trigger corresponds to the home PLMN. If the MCC / MNC in the RX trigger corresponds to the home PLMN, the system can proceed with dedicated bearer establishment. If the MCC / MNC in the RX trigger does not correspond to the home PLMN (e.g., if the call is originated from the roaming operator network or Wi-Fi), the system can suppress the RX trigger (e.g., for the Internet APN) to ensure that the call continues with the default bearer.

[0038] FIG. 5 is a diagram showing the roaming interoperability of OTT calls according to an embodiment. FIG. 5 shows an OTT call routing policy determined or implemented by a system (e.g., server 120) for an OTT call by a user device (e.g., device 110). As shown, the network may include a home operator 502 site in a non-roaming area, a home operator 502 site in a roaming area, and a roaming partner 504 site (or touch point). The home operator 502 in the non-roaming area may include a QCI 510 for VoLTE, a QCI 512 for the Internet, and other QCIs 514 for additional Internet connections or processing. The home operator 502 in the non-roaming area may include a QCI 510 for VoLTE and a QCI 512 for the Internet. The roaming partner 504 may include a QCI 516 for VoLTE and a QCI 518 for the Internet. In the case of an OTT call initiated at a home operator 502 site having a roaming touch point (i.e., the home operator 502 site in the middle of FIG. 5), the OTT call is routed on the default bearer 512 according to a policy determined by the system according to an embodiment. Thus, when the user device moves to the roaming partner 502 site, the bearer is not rejected and the call can continue seamlessly. In contrast to previous methods where the core session was forcibly released, the IP address was changed, and a new re-registration to the application server was required, the methods and systems disclosed herein provide interoperability where the core session is not forcibly released, the IP address remains the same, and no re-registration to the application server is required.

[0039] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit to the exact form disclosed. Modifications and variations are possible in light of the above disclosure, or can be obtained from practice of the implementation forms.

[0040] Some embodiments can relate to systems, methods, and / or computer-readable media in the integration of any possible technical detail level. The computer-readable media can include computer-readable non-transitory storage media (s) having computer-readable program instructions for causing a processor to execute operations.

[0041] The computer-readable storage media can be a tangible device that can hold and store instructions for use by an instruction execution device. The computer-readable storage media can be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. A non-exhaustive list of more specific examples of the computer-readable storage media includes portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital versatile disc (DVD), memory stick, floppy (registered trademark) disk, punch cards, mechanically encoded devices such as a raised structure with instructions recorded in grooves, and any suitable combination of the foregoing. The computer-readable storage media as used herein should not be construed to be a transient signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., an optical pulse passing through an optical fiber cable), or an electrical signal transmitted through a wire.

[0042] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium or via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network, to respective computing / processing devices via an external computer or an external storage device. The network can include copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface within each computing / processing device receives the computer-readable program instructions from the network and transfers the computer-readable program instructions for storage on a computer-readable storage medium within each respective computing / processing device.

[0043] The computer-readable program code / instructions for performing the operations can be in any combination of one or more programming languages, including assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuits, or source code or object code written in an object-oriented programming language such as Smalltalk, C++, and a procedural programming language such as the "C" programming language or similar programming languages. The computer-readable program instructions can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, for example, an electronic circuit including a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) can execute the computer-readable program instructions by personalizing the electronic circuit using the state information of the computer-readable program instructions to perform the aspects or operations.

[0044] These computer-readable program instructions may be provided to a processor of a general purpose computer, a special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / operations specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer-readable storage medium storing the instructions comprises a manufacture including instructions which implement the aspects of the functions / operations specified in one or more blocks of the flowchart and / or block diagram.

[0045] The computer-readable program instructions may also be loaded onto a computer, other programmable apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions / operations specified in one or more blocks of the flowchart and / or block diagram.

[0046] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer-readable media according to various embodiments. In this regard, each block in the flowchart or block diagram can represent a module, segment, or portion of one or more executable instructions for implementing the specified logical function. The methods, computer systems, and computer-readable media can include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those shown in the figures. In some alternative embodiments, the functions described in the blocks may be performed in a different order than that described in the figures. For example, two blocks shown in succession may actually be performed simultaneously or substantially simultaneously, or the blocks may sometimes be performed in the reverse order depending on the related functions. It should also be noted that each block in the block diagram and / or flowchart diagram, and combinations of blocks in the block diagram and / or flowchart diagram, can be implemented by a dedicated hardware-based system that performs the specified function or operation, or a combination of dedicated hardware and computer instructions.

[0047] It is obvious that the systems and / or methods described in this specification may be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods does not limit the implementation form. Therefore, the operation and operation of the systems and / or methods are described herein without reference to specific software code, and it is understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0048] Elements, operations, or instructions used in this specification should not be construed as important or essential unless explicitly described as such. Also, as used in this specification, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more". Further, as used in this specification, the term "set" is intended to include one or more items (e.g., related items, unrelated items, combinations of related and unrelated items, etc.) and may be used interchangeably with "one or more". The term "one" or similar terms are used when only one item is intended. Also, as used in this specification, terms such as "has", "have", "having", etc. are intended to be non-limiting terms. Further, the phrase "based on" is intended to mean "at least partially based on" unless otherwise specified.

[0049] The descriptions of various aspects and embodiments are presented for illustrative purposes but are not intended to be exhaustive or limited to the disclosed embodiments. Specific combinations of features are described in the claims and / or disclosed herein, but these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or not disclosed in the specification. Each of the dependent claims listed below may directly depend on only one claim, but the disclosure of possible implementations includes each dependent claim in combination with all other claims in the claim set. Many modifications and variations will be apparent to those skilled in the art without departing from the scope of the described embodiments. The terms used in this specification are selected to best explain the principles of the embodiments, the practical application, or the technological improvement to the technology seen in the market, or to enable those skilled in the art to understand the embodiments disclosed herein.

Claims

1. A method for setting a policy for over-the-top (OTT) calls in a mobile network, comprising: determining whether a cell of the mobile network has at least one adjacent cell of at least one roaming partner of the mobile network; determining a bearer policy for routing an OTT call in the cell based on whether it is determined that the cell has the at least one adjacent cell of the at least one roaming partner; wherein the determined bearer policy indicates whether an OTT call within the cell should be routed on a dedicated bearer or a default bearer for connecting to an Internet access point name (APN); determining the bearer policy comprises determining, based on determining that the cell does not have an adjacent cell of any roaming partner, a first bearer policy for routing an OTT call on the dedicated bearer for connecting to the Internet APN as the bearer policy; and determining, based on determining that the cell has the at least one adjacent cell of the at least one roaming partner, a second bearer policy for routing the OTT call on the default bearer for connecting to the Internet APN as the bearer policy; A method as described above.

2. A system for setting a policy for over-the-top (OTT) calls in a mobile network, comprising: a memory for storing instructions; a processor configured to execute the instructions to determine whether a cell of the mobile network has at least one adjacent cell of at least one roaming partner of the mobile network, and determine a bearer policy for routing an OTT call in the cell based on whether it is determined that the cell has the at least one adjacent cell of the at least one roaming partner; wherein the determined bearer policy indicates whether an OTT call in the cell should be routed on a dedicated bearer or a default bearer for connecting to an Internet access point name (APN). ​ The processor executes the instructions to Based on determining that the cell does not have an adjacent cell of any roaming partner, as the bearer policy, determine a first bearer policy for routing an OTT call on the dedicated bearer for connecting to the Internet APN. Based on determining that the cell has at least one adjacent cell of the at least one roaming partner, as the bearer policy, determine a second bearer policy for routing the OTT call on the default bearer for connecting to the Internet APN. A system configured to determine the bearer policy in this way. **Claim 3** A non-transitory computer-readable storage medium for setting a policy for an over-the-top (OTT) call in a mobile network, connected to one or more processors and configured to store instructions, which when executed cause the one or more processors to Determine whether a cell of the mobile network has at least one adjacent cell of at least one roaming partner of the mobile network. Based on whether it is determined that the cell has at least one adjacent cell of the at least one roaming partner, determine a bearer policy for routing an OTT call in the cell. The determined bearer policy indicates whether the OTT call in the cell should be routed on a dedicated bearer or a default bearer for connecting to an Internet access point name (APN). The instructions, when executed, cause the one or more processors to Based on determining that the cell does not have an adjacent cell of any roaming partner, as the bearer policy, determine a first bearer policy for routing an OTT call on the dedicated bearer for connecting to the Internet APN. Based on determining that the cell has at least one adjacent cell of the at least one roaming partner, as the bearer policy, determine a second bearer policy for routing the OTT call on the default bearer for connecting to the Internet APN. A non-transitory computer-readable storage medium for causing the bearing policy to be determined.

Images