System, method, and computer program for dynamically adapting over-the-top (OTT) call routing
The system addresses call disruptions by dynamically routing OTT calls based on roaming partner status, ensuring continuous connectivity and improved user experience during transitions between home and roaming operator networks.
Patent Information
- Application Number
- JP2024533315
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2021-12-09
- Filing Date
- 2022-02-11
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2042-02-11
AI Technical Summary
Roaming operators often reject dedicated bearers for over-the-top (OTT) application calls on non-default Internet Access Point Name (APN) bearers, leading to call muting and session disconnections during transitions between home and roaming operator touchpoints, resulting in poor user experience.
A system and method that dynamically adapt bearers by determining neighboring cells' roaming status and routing OTT calls on either dedicated or default bearers based on home operator policies, ensuring seamless handovers and maintaining session continuity.
Prevents call drops and session disconnections by dynamically adjusting bearer policies, allowing OTT calls to continue seamlessly across operator touchpoints without requiring IP address changes or re-registration, enhancing user experience.
Smart Images

Figure 2024545455000001_ABST
Abstract
Description
[Technical field]
[0001] This disclosure relates generally to roaming interoperability for over-the-top (OTT) call routing. [Background technology]
[0002] Roaming partners have specific policies to allow or reject bearers depending on the Packet Data Network (PDN) to which the bearer corresponds. One of the policies of a roaming operator may be to reject any bearer in an Internet Access Point Name (APN) apart from the default bearer. Thus, an existing session (e.g., an Over-the-Top (OTT) application call or session) routed on a non-default Internet APN bearer (e.g., a dedicated Internet APN bearer) of the home operator may have problems when transitioning (or handing over) from a home operator touch point or cell to a roaming operator touch point or cell. Specifically, the roaming operator may reject the dedicated bearer, resulting in problems like call muting and session disconnection. As a result, the user's perception is poor while moving between the home operator and the roaming operator. Summary of the Invention
[0003] One or more exemplary embodiments provide systems and methods for dynamically adapting bearers to enhance interaction with roaming touchpoints and to enhance voice quality for over-the-top (OTT) applications during transitions between home and roaming operator touchpoints.
[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 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 may indicate 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).
[0005] According to one aspect of the present disclosure, a system for setting a policy for an OTT call 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 neighboring 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 the cell is determined to have at least one neighboring cell of the at least one roaming partner. The determined bearer policy may indicate whether an OTT call in the cell should be routed over 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 an OTT call in a mobile network is provided. The storage medium may be coupled 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 neighboring 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 the cell is determined to have at least one neighboring cell of the at least one roaming partner. The determined bearer policy may indicate whether an OTT call in the cell should be routed over a dedicated bearer or a default bearer for connecting to an Internet APN.
[0007] Additional aspects will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of illustrative embodiments of the present disclosure. [Brief description of the drawings]
[0008] The above and other aspects, features, and aspects of embodiments of the present disclosure will become apparent from the following description taken in conjunction with the accompanying drawings.
[0009] [Figure 1] FIG. 2 is a diagram of devices of a system according to one embodiment. [Diagram 2] FIG. 2 is a diagram of components of the device of FIG. 1 according to one embodiment. [Diagram 3] FIG. 1 is a diagram of a network according to one embodiment. [Figure 4] 1 is a flowchart of a method of over-the-top (OTT) call routing according to an embodiment. [Diagram 5] FIG. 1 illustrates roaming interoperability for OTT calls according to one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0010] The following detailed description of the exemplary embodiments refers to the accompanying drawings, in which the same reference numbers in various drawings may identify the same or similar elements.
[0011] Figure 1 is a diagram of a system according to one embodiment, including a user device 110, a server device 120, and a network 130. The user device 110 and the server device 120 may be interconnected via a wired connection, a wireless connection, or a combination of wired and wireless connections.
[0012] The user device 110 may 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 smart watch), or a similar device.
[0013] The server device 120 may include one or more devices. For example, the server device 120 may be a server device, a computer device, etc.
[0014] Network 130 may include one or more wired and / or wireless networks. For example, network 130 may 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 devices and networks shown in Figure 1 are provided as an example. In practice, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged differently than those shown in Figure 1. Furthermore, two or more devices shown in Figure 1 may be implemented within a single device, or a single device shown in Figure 1 may be implemented as multiple distributed devices. Additionally or alternatively, 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]
[0023] Figure 2 is a diagram of components of one or more devices of Figure 1 according to one embodiment. Device 200 may correspond to user device 110 and / or server device 120.
[0017] As shown in FIG. 2, device 200 may include a bus 210, a processor 220, a memory 230, a storage component 240, an input component 250, an output component 260, and a communication interface 270.
[0018] Bus 210 may include components that enable communication between components of device 200. Processor 220 may be implemented in hardware, firmware, or a combination of hardware and software. Processor 220 may be a central processing unit (CPU), a graphics processing unit (GPU), an accelerated 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. Processor 220 may include one or more processors that can be programmed to perform functions.
[0019] Memory 230 may include random access memory (RAM), read-only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores 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 may include a hard disk (e.g., a magnetic disk, optical disk, magneto-optical disk, and / or solid-state disk), a compact disk (CD), a digital versatile disk (DVD), a floppy disk, cartridges, magnetic tape, and / or another type of non-transitory computer-readable medium along with a corresponding drive.
[0021] Input components 250 may include components that enable device 200 to receive information, such as through a user input (e.g., a touchscreen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone). Input components 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 components 260 may include components that provide output information from device 200 (eg, a display, a speaker, and / or one or more light emitting diodes (LEDs)).
[0023] Communications interface 270 may include transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that enable device 200 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communications interface 270 may enable device 200 to receive information from another device and / or provide information to another device. For example, communications 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] Device 200 may perform one or more of the processes described herein. Device 200 may perform operations based on processor 220 executing software instructions stored by a non-transitory computer-readable medium, such as memory 230 and / or storage component 240. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or across multiple physical storage devices.
[0025] The software instructions may be loaded into memory 230 and / or storage component 240 from another computer-readable medium or from another device via communications interface 270. When executed, the software instructions stored in memory 230 and / or storage component 240 may cause processor 220 to perform one or more processes described herein.
[0026] Additionally, or alternatively, hardwired circuitry may be used in place of or in combination with software instructions to implement one or more of the processes described herein. Thus, the embodiments described herein are not limited to any specific combination of hardware circuitry and software.
[0027] At the home operator, an OTT session may be established by a user equipment (UE) or terminal (e.g., device 110 in FIG. 1 ) according to policies defined by the home operator (e.g., a server of the home operator or a server accessible by the home operator, such as server 120 in FIG. 1 ), and calls may be routed on any dedicated or default bearer riding on the Internet APN depending on the policies. Thus, such calls or sessions routed on dedicated bearers according to home operator policies, e.g., to reject any bearers other than the default bearer established on the Internet APN, may be dropped during handover to the roaming operator during an active session due to policies on the roaming operator core (e.g., mobility management entity (MME)).
[0028] To prevent dropped calls and sessions, the system may determine sites (e.g., cells) that have one or more roaming touch points and sites that have only non-roaming touch points from a neighbor table (e.g., determining neighboring cells and determining whether the neighboring cells are roaming partners). The system may dynamically route the call according to the home operator's policies while on a non-roaming touch point. The system may reroute the call to a default bearer on the Internet APN at a site of the home PLMN determined to include a roaming touch point. The system may handover the OTT session from the home operator's site with the roaming touch point to the roaming operator's site on a default bearer established on the Internet APN. The system may also initiate trigger suppression of OTT calls originating from a roaming partner area.
[0029] FIG. 3 is a diagram of a network according to one 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 touchpoints, for example, according to 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. In the home operator roaming boundary 308, the home operator 302 may operate with the default bearer 310. The roaming partner 304 may operate with the default bearer (Internet APN) 314. The roaming partner 304 may include an area 316 located 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] 4 is a flow chart of a method of OTT call routing according to one embodiment. In operation 402, the system (e.g., an external node or server 120 accessible by the home operator) determines a home operator node type. For example, the external node or server 120 may determine from an existing neighbor table of the home operator site whether at least one neighbor cell of the current site (i.e., the home operator site for which a policy is being determined pursuant to operation 402, 404) belongs to a roaming PLMN. Based on at least one neighbor cell belonging to a roaming PLMN, the system (e.g., server 120) may 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 neighbor cells of the current site or cell belong to a roaming PLMN, the system may 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 may determine the home operator node type periodically, at predetermined time intervals, in response to a request to make a determination, etc. (eg, as set by an operator).
[0031] In operation 404, the system determines a home operator policy (e.g., bearer policy) for OTT calls at the current site. The operator's policy for OTT calls may be obtained from a Policy and Charging Rules Function (PCRF) that determines the Quality of Service (QoS) Class Indicator (QCI) (e.g., dedicated or default) to be established based on receiving an RX trigger from an application server corresponding to the OTT application and the corresponding linked bearer for which the same QCI should be established. For example, the operation may determine to have OTT media on dedicated bearers QCI1-QCI4 while having corresponding signaling on default bearers QCI6-QCI9. In this example, QCI5 is not part of the list since it is the default bearer for the IP Multimedia Subsystem (IMS) PDN and is used for Voice over Long Term Evolution (VoLTE) sessions.
[0032] In operation 406, the system determines an OTT call routing behavior. In operation 406, the system can determine whether the OTT call should be routed on a dedicated bearer or a default bearer. For example, if the home operator node type is determined to have a roaming touch point (i.e., determined to have a roaming touch point), the home operator policy of the OTT call corresponds to OTT media on a dedicated bearer (e.g., Internet APN), and the OTT call routing behavior is signaling on a default bearer, the system can receive dedicated bearer details corresponding to the OTT media from the home operator policy of the OTT call (e.g., QCI3 / QCI4). The system can receive an activation state in a radio access network (RAN) corresponding to the dedicated bearer corresponding to the home operator policy. If the activation state indicates that a 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 status indicates that the dedicated bearer is deactivated for routing OTT calls in the cell, the system may determine that no further action is required.
[0033] On the other hand, if the home operator node type of the current site or cell is determined to have no roaming touch point (e.g., determined to have "no roaming touch point"), the home operator policy of the OTT call supports OTT media on a dedicated bearer (e.g., Internet APN), and the OTT call routing behavior is signaling on a default bearer, the system may receive dedicated bearer details corresponding to the OTT media from the home operator policy of the OTT call. The system may receive an activation state in the RAN corresponding to the dedicated bearer corresponding to the home operator policy. If the activation state indicates that the dedicated bearer is disabled to route the OTT call in the cell, the system may update the activation state on the RAN from disabled to enabled. If the activation state indicates that the dedicated bearer is enabled to route the OTT call in the cell, the system may determine that no further action is required.
[0034] In a further example, if the home operator node type is determined to have a roaming touch point or to have no roaming touch point, the home operator policy for the OTT call supports OTT media on a default bearer (e.g., Internet APN), and the OTT call routing behavior is signaling on a default bearer, the system may determine that no further action is required because the home operator policy for the OTT call is OTT media on a 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 may use the existing policy for the active calls on the cell at the time of the policy change and may 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 may 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, the system can hand over an OTT session from a home operator node classified as "having a roaming touch point" after operation 406 to a roaming partner.
[0037] In operation 410, the system generates an RX trigger to suppress OTT calls originating from a roaming partner area. For new calls originating in a roaming partner area or a home network area, the OTT's application server can initiate an EX trigger towards the home operator's PCRF. However, this may cause a failure on the roaming operator where the policy is not configured to activate a dedicated bearer on the Internet APN, resulting in a call failure. To avoid this, the PCRF may determine whether the Mobile Carrier 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 may proceed with the dedicated bearer establishment. If the MCC / MNC in the RX trigger does not correspond to the home PLMN (e.g., the call originates from a roaming operator network or Wi-FI), the system may suppress the RX trigger to ensure that the call continues on the default bearer (e.g., Internet APN).
[0038] FIG. 5 illustrates roaming interoperability for OTT calls, according to one embodiment. In FIG. 5, an OTT call routing policy is shown determined or implemented by the system (e.g., server 120) for an OTT call by a user equipment (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 a non-roaming area may include a QCI 510 for VoLTE, a QCI 512 for the Internet, and other QCIs 514 for additional Internet connectivity or processing. The home operator 502 in a 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. For an OTT call initiated at a home operator 502 site having a roaming touchpoint (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 the policy determined by the system according to an embodiment. Thus, when the user equipment transitions to a roaming partner 502 site, the bearer is not rejected and the call can continue seamlessly. In contrast to previous methods where the core session is forcibly released, the IP address is changed, and a new re-registration to the application server is required, the method and system disclosed herein provides 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 the implementations to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practicing the implementations.
[0040] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible level of technical detail integration. The computer-readable media may include computer-readable non-transitory storage medium(s) having computer-readable program instructions for causing a processor to perform operations.
[0041] A computer-readable storage medium may be a tangible device capable of holding and storing instructions for use by an instruction execution device. A computer-readable storage medium may 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 computer-readable storage media includes portable computer diskettes, hard disks, random access memories (RAMs), read-only memories (ROMs), erasable programmable read-only memories (EPROMs or flash memories), static random access memories (SRAMs), portable compact disk read-only memories (CD-ROMs), digital versatile disks (DVDs), memory sticks, floppy disks, mechanically encoded devices such as punch cards or raised structures with instructions recorded in grooves, and any suitable combinations of the above. As used herein, computer-readable storage media should not be interpreted as being transitory signals per se, such as electric waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., light pulses passing through a fiber optic cable), or electrical signals transmitted through wires.
[0042] The computer-readable program instructions described herein can be downloaded to each computing / processing device from a computer-readable storage medium or via an external computer or external storage device over a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical transmission fiber, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing / processing device.
[0043] The computer readable program code / instructions for performing the operations may be either source code or object code written in any combination of one or more programming languages, including assembler instructions, instruction set architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state setting data, configuration data for an integrated circuit, or object oriented programming languages such as Smalltalk, C++, and procedural programming languages such as the "C" programming language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer, 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 wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) can execute computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry to perform an aspect or operation.
[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 manufacture a machine such that the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for performing the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams. These computer readable program instructions may also be stored on a computer readable storage medium capable of directing a computer, programmable data processing apparatus, and / or other device to function in a particular manner, such that a computer readable storage medium having instructions stored thereon includes an article of manufacture including instructions implementing aspects of the functions / operations specified in one or more blocks of the flowcharts and / or block diagrams.
[0045] The computer readable program instructions may also be loaded onto a computer, other programmable apparatus, or other device to cause the computer, other programmable apparatus, or other device to perform a series of operational steps to generate a computer-implemented process, such that the instructions executing on the computer, other programmable apparatus, or other device perform the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.
[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 flowcharts or block diagrams may represent a module, segment, or part of an instruction that includes one or more executable instructions for implementing the specified logical function. The methods, computer systems, and computer-readable media may include additional, fewer, different, or differently arranged blocks than those shown in the figures. In some alternative implementations, 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 in fact be executed simultaneously or substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. It should also be noted that each block of the block diagrams and / or flowchart diagrams, as well as combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by a dedicated hardware-based system that performs the specified functions or operations or executes a combination of dedicated hardware and computer instructions.
[0047] It will be apparent that the systems and / or methods described herein 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 is not intended to limit the implementation. Thus, the operation and behavior of the systems and / or methods are described herein without reference to any specific software code, and it will be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.
[0048] No element, act, or instruction used herein should be construed as critical or essential unless expressly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Additionally, as used herein, 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." When only one item is intended, the term "a" or similar term is used. Also, as used herein, terms such as "has," "have," and "having" are intended to be open-ended terms. Additionally, the phrase "based on" is intended to mean "based at least in part on," unless otherwise specified.
[0049] The description of various aspects and embodiments is presented for illustrative purposes, but is not intended to be exhaustive or limited to the disclosed embodiments. Although certain combinations of features are recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of possible implementations. Indeed, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, 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, practical applications or technical improvements to the technology found 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 neighboring 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 the cell is determined to have the at least one neighboring cell of the at least one roaming partner; Including, The determined bearer policy indicates whether the OTT calls in the cell should be routed on a dedicated bearer or a default bearer to connect to an Internet Access Point Name (APN). method.
2. Determining the bearer policy includes: determining, based on determining that the cell does not have any roaming partner neighbor cells, as the bearer policy, a first bearer policy for routing an OTT call on the dedicated bearer for connecting to the Internet APN; determining, based on determining that the cell has the at least one neighboring cell of the at least one roaming partner, as the bearer policy, a second bearer policy for routing the OTT call on the default bearer for connecting to the Internet APN; The method of claim 1 , comprising:
3. Determining the bearer policy includes: Obtaining a home operator policy for an OTT call; Based on the obtained home operator policy indicating that the OTT call should be routed on the dedicated bearer for connecting to the Internet APN, and based on determining that the cell has the at least one neighbor cell of the at least one roaming partner, obtaining a state of a dedicated bearer for the cell; and based on the obtained state indicating that the dedicated bearer is enabled for routing OTT calls in the cell, control to change the state of the dedicated bearer to be disabled for routing the OTT calls in the cell; The method of claim 1 , comprising:
4. Determining the bearer policy includes: Based on the obtained home operator policy indicating that the OTT call should be routed on the dedicated bearer for connecting to the Internet APN, and based on determining that the cell does not have any roaming partner neighbor cells, obtaining a state of the dedicated bearer for the cell; and based on the obtained state indicating that the dedicated bearer is not enabled for routing OTT calls in the cell, controlling to change the state of the dedicated bearer to be enabled for routing the OTT calls in the cell; The method of claim 3 further comprising:
5. Determining the bearer policy includes: determining, based on the obtained home operator policy indicating that the OTT call should be routed on the default bearer for connecting to the Internet APN, that the bearer policy for the OTT call in the cell is the same as the home operator policy; The method of claim 3 further comprising:
6. Determining the bearer policy includes: determining, based on the obtained home operator policy indicating that the OTT call should be routed on the default bearer for connecting to the Internet APN, that the bearer policy for the OTT call in the cell is the same as the home operator policy; The method of claim 3 , comprising:
7. 4. The method of claim 3, wherein obtaining the home operator policy includes obtaining the home operator policy upon receiving an RX trigger from a Policy and Charging Rules Function (PCRF) that determines a Quality of Service (QoS) Class Indicator (QCI) to be established from an application server corresponding to an OTT application and a corresponding linked bearer corresponding to the QCI.
8. storing, for each of a plurality of cells of the mobile network, information indicating whether there are any neighboring cells of any roaming partners; 2. The method of claim 1, wherein determining whether the cell has the at least one neighbor cell of the at least one roaming partner comprises determining whether the cell has the at least one neighbor cell of the at least one roaming partner based on the stored information.
9. The method of claim 8 further comprising updating the stored information at predetermined time intervals.
10. A system for setting a policy for over-the-top (OTT) calls in a mobile network, comprising: A memory for storing instructions; Executing the instructions, determining whether a cell of the mobile network has at least one neighboring 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 the cell is determined to have the at least one neighboring cell of the at least one roaming partner; a processor configured to: Equipped with The determined bearer policy indicates whether the OTT call in the cell should be routed on a dedicated bearer or a default bearer to connect to an Internet Access Point Name (APN). system.
11. The processor executes the instructions to determining, based on determining that the cell does not have any roaming partner neighbor cells, as the bearer policy, a first bearer policy for routing an OTT call on the dedicated bearer for connecting to the Internet APN; determining, based on determining that the cell has the at least one neighboring cell of the at least one roaming partner, as the bearer policy, a second bearer policy for routing the OTT call on the default bearer for connecting to the Internet APN; The system of claim 10 , configured to determine the bearer policy by:
12. The processor executes the instructions to Obtaining the home operator policy for OTT calls; Based on the obtained home operator policy indicating that the OTT call should be routed on the dedicated bearer for connecting to the Internet APN, and based on determining that the cell has the at least one neighbor cell of the at least one roaming partner, Obtaining a state of a dedicated bearer for the cell; based on the obtained state indicating that the dedicated bearer is enabled for routing OTT calls in the cell, control to change the state of the dedicated bearer to be disabled for routing the OTT calls in the cell; The system of claim 10 , configured to determine the bearer policy by:
13. The processor executes the instructions to further: Based on the obtained home operator policy indicating that the OTT call should be routed on the dedicated bearer for connecting to the Internet APN, and based on determining that the cell does not have any roaming partner neighbor cells, obtaining a state of the dedicated bearer for the cell; based on the obtained state indicating that the dedicated bearer is not enabled for routing OTT calls in the cell, control to change the state of the dedicated bearer to be enabled for routing the OTT calls in the cell. The system of claim 12 , configured to determine the bearer policy by:
14. The processor executes the instructions to further: determining that the bearer policy for the OTT call in the cell is the same as the home operator policy based on the obtained home operator policy indicating that the OTT call should be routed on the default bearer for connecting to the Internet APN; The system of claim 12 , configured to determine the bearer policy by:
15. The processor executes the instructions to determining that the bearer policy for the OTT call in the cell is the same as the home operator policy based on the obtained home operator policy indicating that the OTT call should be routed on the default bearer for connecting to the Internet APN; The system of claim 12 , configured to determine the bearer policy by:
16. 13. The system of claim 12, wherein the processor is configured to execute the instructions to obtain the home operator policy by obtaining the home operator policy upon receiving an RX trigger from a Policy and Charging Rules Function (PCRF) that determines a Quality of Service (QoS) Class Indicator (QCI) to be established from an application server corresponding to an OTT application and a corresponding linked bearer corresponding to the QCI.
17. The processor executes the instructions to and further configured to store, for each of a plurality of cells of the mobile network, information indicating whether there are any neighboring cells of any roaming partners; determining whether the cell has the at least one neighbor cell of the at least one roaming partner includes determining whether the cell has the at least one neighbor cell of the at least one roaming partner based on the stored information; The system of claim 10.
18. 20. The system of claim 17, wherein the processor is further configured to execute the instructions to update the stored information at predetermined time intervals.
19. 1. A non-transitory computer-readable storage medium for configuring a policy for over-the-top (OTT) calls in a mobile network, the non-transitory computer-readable storage medium being coupled to one or more processors and configured to store instructions that, when executed, cause the one or more processors to: determining whether a cell of the mobile network has at least one neighboring 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 the cell is determined to have the at least one neighboring cell of the at least one roaming partner; The determined bearer policy indicates whether the OTT call in the cell should be routed on a dedicated bearer or a default bearer to connect to an Internet Access Point Name (APN). A non-transitory computer-readable storage medium.
20. The instructions, when executed, cause the one or more processors to: determining, based on determining that the cell does not have any roaming partner neighbor cells, as the bearer policy, a first bearer policy for routing an OTT call on the dedicated bearer for connecting to the Internet APN; determining, based on determining that the cell has the at least one neighboring cell of the at least one roaming partner, as the bearer policy, a second bearer policy for routing the OTT call on the default bearer for connecting to the Internet APN; 20. The non-transitory computer-readable storage medium of claim 19, wherein the bearer policy is determined by:
Citation Information
Patent Citations
Service and capability negotiation in network using single numbering scheme
JP2008113465A
Parallel registration for offloading plmn with single sim
JP2016521522A
Method for QOS management in home and roaming scenarios based on location / APP server assistance
US20140068064A1
