WO2018001771A1 - Pilotage de trafic dans des réseaux d'accès - Google Patents

Pilotage de trafic dans des réseaux d'accès Download PDF

Info

Publication number
WO2018001771A1
WO2018001771A1 PCT/EP2017/064915 EP2017064915W WO2018001771A1 WO 2018001771 A1 WO2018001771 A1 WO 2018001771A1 EP 2017064915 W EP2017064915 W EP 2017064915W WO 2018001771 A1 WO2018001771 A1 WO 2018001771A1
Authority
WO
WIPO (PCT)
Prior art keywords
server
user equipment
access network
traffic flow
information
Prior art date
Application number
PCT/EP2017/064915
Other languages
English (en)
Inventor
Pradeep PUTHUSSERY
Original Assignee
British Telecommunications Public Limited Company
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by British Telecommunications Public Limited Company filed Critical British Telecommunications Public Limited Company
Publication of WO2018001771A1 publication Critical patent/WO2018001771A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/088—Load balancing or load distribution among core entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/02—Details
    • H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
    • H04L12/1403—Architecture for metering, charging or billing
    • H04L12/1407—Policy-and-charging control [PCC] architecture
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M15/00—Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
    • H04M15/66—Policy and charging system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/24—Accounting or billing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • the present invention relates to communications networks in general and to access network selection in a communications network.
  • the present invention accordingly provides, in a first aspect, a first server for operation in a communications network; in which the first server is configured to receive information specific to an individual traffic flow between the communications network and a user equipment over a first access network of a first access network type; in which the information received comprises information relating to the traffic type of the individual traffic flow and information relating to the first access network type; in which the information specific to an individual traffic flow is detected by a second server; in which the second server is arranged in communication with the user equipment and is configured to create managed data sessions with the user equipment; in which the information specific to an individual traffic flow is received at the first server over a direct link between the first server and the second server; in which the first server is further configured to instigate a determination of a specific one of the first access network and a second access network of a second access network type for selection for carrying the individual traffic flow between the communications network and the user equipment; in which the determination is based on the information received regarding the traffic flow and the information received regarding the first access network type and pre- programmed information on
  • the determination is carried out on the basis of a request made before the individual traffic flow commences; in which the information is received in the request.
  • the server is an Access Network Discovery and Selection Function or ANDSF.
  • the access networks comprise at least one 3GPP network and at least one non-3GPP network.
  • the invention accordingly provides in a second aspect, a method for operating a first server in a communications network; in which the method comprises the first server: receiving over a direct link between the first server and a second server, information specific to an individual traffic flow between the communications network and a user equipment over a first access network of a first access network type; in which the information received comprises information relating to the traffic type of the individual traffic flow and information relating to the first access network type; in which the second server is arranged in communication the user equipment and is configured to create a managed data session with the user equipment; in which the information specific to an individual traffic flow is detected by the second server; in which the method further comprises the first server: instigating a determination of a specific one of the first access network and a second access network of a second access network type for selection for carrying the individual traffic flow between the communications network and the user equipment; in which the determination is based on the information received regarding the traffic flow, the information received regarding the first access network type and preprogrammed information on the second access network type; and in which the method
  • the determination is carried out on the basis of a request made before the individual traffic flow commences; in which the information is received in the request.
  • the server is an Access Network Discovery and Selection Function or ANDSF.
  • the method further comprises the server obtaining from a data storage, at least one rule for determining a specific access network for selection for carrying a traffic flow between the communications network and the user equipment.
  • the method further comprises the server providing to the user equipment a policy derived from the rule.
  • the rule is an IFOM rule.
  • the method further comprises the server obtaining the at least one rule from the data storage in response to providing to the data storage, the information received regarding the individual traffic flow and the access network type.
  • the determination is based on a data type associated with the traffic flow.
  • the determination is based on a data-rate associated with the traffic flow.
  • the server is configured to communicate to the user equipment the identity of a WLAN access network in relation to a higher-bandwidth traffic flow.
  • the present invention accordingly provides, in a third aspect, a computer program element comprising computer program code to, when loaded into a computer system and executed thereon, cause the computer to perform the steps of the method set out above.
  • Figure 1 is a block diagram of a communications system suitable for the operation of embodiments of the present invention
  • Figures 2 to 3 show typical signal flows in the communications system of Figure 1 ;
  • Figure 4 is a block diagram of a data processing system suitable for the operation of embodiments of the present invention.
  • the arrangement proposed here improves current access-network selection by providing new functionality at a network server which receives information specific to an individual traffic flow between the communications network and a single user equipment over a first access network; instigates a determination of a specific one of the first and second access networks for selection for carrying the individual traffic flow and communicates to the user equipment the identity of the specific one of the first and second access networks for selection for carrying the traffic flow.
  • This solution can provide the user with improved data and voice traffic flows over various access technologies thereby improving user satisfaction. Network operators may be able to reduce capital and operational expenditure as fewer radio sites may be required to serve a given population of users.
  • the solution described here can improve network efficiency by enabling automatic and seamless offloading of traffic based on traffic type and enhancing the operator's influence over the access network selection.
  • Embodiments of the invention enhance the operator's influence over the access network selection by providing information, detected at a server in a mobile network, on an individual traffic flow, i.e. a traffic flow specifically involving a single user equipment. For example, by detecting, within the mobile network, high-bandwidth network traffic flows impinging on the user equipment and by monitoring, within the mobile network, the availability of Wi-Fi access-network connections to a specific user equipment, the network operator is able to influence access network selection at the user equipment, so that high-bandwidth network traffic may be diverted, as appropriate, away from an overloaded mobile access network, for example to an alternative access network better able to cope with the traffic.
  • load on the mobile network can be reduced, and faster data-transfer facilitated by moving the data to a higher-bandwidth WLAN connection, where appropriate, and may in this way reduce mobile-related costs to the user. According to a further embodiment, this is achieved automatically, without action being required by the user.
  • a user equipment 102 such as a mobile phone, mobile computing device or similar having wireless mobile telephony and data connections is in communication with a remote communications network 104 (e.g. a core IP network such as the Internet or a communications provider's public or proprietary core network) via a plurality of access networks. That is, the communications network is able to communicate with a user equipment via at least a first access network of a first type and via a second access network of a second type accessible to the user equipment.
  • Suitable wireless access networks include WWAN 106 and WLAN 108. That is, user equipment 102 has two or more wireless communications interfaces that allow it to communicate with the core network 104 using a choice of different protocols over functionally separated access networks 106, 108.
  • Each access network will have a different wireless termination point on the network side.
  • this can be e-Node B 1 16
  • this can be Wi-Fi access point (AP) 1 18.
  • PGW 124 connects the Evolved Packet Core (which includes the following elements from Figure 1 : MME 136, SGW 130, PCRF 125, PGW 124, TWAG 142, Epdg 144 and ANDSF 122) to the remote communications network 104 via SGi interface 145.
  • PGW 124 supports connection from access networks, such as WWAN 106 and WLAN 108.
  • An exemplary embodiment is shown in Figure 1 . According to this embodiment, PGW
  • S-GW 130 connects to the WWAN access network 106 over s5 link 131 and Serving Gateway (S-GW) 130.
  • S-GW 130 can be a function within the PGW 124.
  • PGW 124 connects to the WWAN access network 106 for control plane/signalling over Serving Gateway (S-GW) 130, connection s1 1 134, Mobility Management Node (MME) 136 and connection s1 -MME 138 and PGW 124 connects to the WWAN access network 106 for user plane/user payload over S-GW 130 and connection S1 -U 132.
  • S-GW Serving Gateway
  • PGW 124 connects to the WLAN access network 108 over s2b connection 141 through Trusted Wi-Fi Access Gateway (TWAG) 142 to trusted WLAN access networks and over an s2a connection 140 and ePDG 144 to untrusted WLAN access networks.
  • TWAG Trusted Wi-Fi Access Gateway
  • the PGW 124 creates managed data sessions from user equipments such as user equipment 102.
  • the PGW 124 receives requests for data sessions/bearer setup from user equipments and can accept or reject a request based on certain conditions. Before allowing a request, checks are performed, as described below, by the PGW 124, some of which can involve the PGW 124 interfacing with other nodes such as the PCRF 125 and the charging system (CGF 146 and OCS 148).
  • the Gx interface 152 towards the PCRF is used for policy control.
  • the Gy interface towards online charging system is used for real-time billing in which the credit balance of a user may be checked before allowing a data session. If the request is allowed, the data exchange (i.e. the user plane) is carried over the S1 -U link 132 using GPRS Tunneling Protocol GTP-U.
  • the user equipment 102 is also connected, via S14 link 120, over the Mobile access network with ANDSF 122.
  • ANDSF 122 is a network element in the 3GPP Evolved Packet Core (EPC) and is an enabler of selection between access networks using different technologies (e.g. 3GPP and non-3GPP access networks).
  • the ANDSF 122 provides a user equipment with operational information and operator-defined policies.
  • ANDSF 122 uses a standardized S14 interface 120 to distribute network selection information and policies to user equipments in the mobile network.
  • the S14 interface enables IP-level communication between the user equipment 102 and ANDSF 122 via pull or push mechanisms as defined in 3GPP TS 23.402. A combination of pull and push mechanisms may also be supported.
  • the ANDSF is provided with information specific to each individual traffic flow between the individual user equipment and the network, to allow improved access network selection.
  • information on access-network traffic monitored using DPI is processed at the ANDSF 122 to inform decisions as to the most advantageous access network for an individual user equipment 102 to use for a specific network traffic flow (i.e. data or voice traffic).
  • the information is provided by the PGW 124 to the ANDSF 122 by means of a new interface.
  • the new interface enables the PGW 124 to provide the ANDSF 122 with information on requested and detected real-time traffic flow of the individual user equipment in one or more access networks 106, 108
  • the new interface comprises a new connection, not found in conventional enhanced packet core, between the PGW 124 and the ANDSF 122 to facilitate sharing of the information processed by the PGW 124 from monitoring of network traffic at an individual user equipment 102 level.
  • the new interface may be implemented as a DIAMETER-based interface.
  • the ANDSF 122 can then communicate with the user equipment 102 (e.g. by pushing an ISRP rule) to share with the user equipment a determination, based on the information received from the PGW 124, as to the preferred access network for an individual traffic flow. Rules related to various traffic types can be pre provisioned in the ANDSF 122 by the mobile operator. The information and policies provided by ANDSF 122 are used by the user equipment 102 to select a suitable network for the specific type of traffic.
  • access network selection information and policies provided to the user equipment 102 by the ANDSF 122 takes precedence over any information affecting selection of access network pre-set by the operator on the user equipment 102.
  • the information and policies provided by ANDSF 122 to the user equipment 102 may comprise ISMP or ISRP information.
  • a secure connection is established over a connection s14 between the user equipment and the ANDSF using PSK TLS, which is a shared key-based mutual authentication scheme.
  • PSK TLS supports a push model, where the ANDSF 122 is able to push data to the user equipment 102 over the PSK TLS connection.
  • Information and policies provided to the user equipment 102 by the ANDSF regarding access networks that are available to the user equipment include: - the access technology type (e.g. WLAN, LTE);
  • the radio access network identifier e.g. the SSID of a WLAN
  • - validity conditions i.e. conditions indicating when the provided access network discovery information is valid (such conditions may include e.g. a location).
  • a server receives information about user equipment network traffic passing over different wireless networks, i.e.: wireless wide area networks (WWAN), which could include 3GPP, HSPA, LTE, etc. mobile wide area access networks - for example 3GPP cellular access-network connections 106 from eNodeB 1 16 to the user equipment 102; and wireless local area networks (WLAN), which could include Wi-Fi, WiMAX, CDMA, etc. - for example, Wi-Fi access-network connections 108 from Wi-Fi access points 1 18 to the user equipment 102.
  • WWAN wireless wide area networks
  • WLAN wireless local area networks
  • Wi-Fi access-network connections 108 from Wi-Fi access points 1 18 to the user equipment 102.
  • the invention uses a server (e.g.
  • DPI 128 is shown as a function of the PGW but can, alternatively, be implemented as a separate network element: i.e. a traffic detection function (TDF) - not shown.
  • DPF traffic detection function
  • DPI allows certain types of user traffic or IP flows to be detected and such information can be used in selecting and in applying certain policies.
  • the detailed information on individual user equipment-specific access-network traffic flows is exploited to improve communications efficiency through the access-networks.
  • the invention provides a new network connection, i.e. a new interface between the network server (e.g. PGW 124) and a network selection function (e.g. access network discovery and selection function - ANDSF 122) for sharing information relating to access network traffic flows.
  • the PGW 124 is a component of the evolved packet Core network (EPC).
  • the PGW 124 connects the EPC to the Internet and to IP networks that are external to the EPC.
  • the PGW 124 supports connection from 3GPP WWAN networks and non-3GPP WLAN networks.
  • the PGW 124 connects to the 3GPP access network through the S-GW (Serving Gateway) 130 which can be a function within the PGW or an external node and the MME (Mobility Management Node) 136.
  • the PGW 124 connects to the non-3GPP access network over the s2a 140 and TWAG 142 for trusted network connection.
  • the PGW 124 connects to the non-3GPP access network over the s2b for untrusted network connection through the evolved packet data gateway ePDG 144.
  • the main role of the ePDG is to provide security mechanisms such as IPsec tunnelling of connections with the user equipment over an untrusted non-3GPP access.
  • the PGW 124 creates and manages data sessions from the user equipments, such as user equipment 102.
  • the PGW 124 receives requests from the user equipments for bearer setup in the form of
  • a request may be received through either the S5 or S2A/S2B link, depending on the access being used by the user equipment at the time of requesting a bearer.
  • the PGW 124 can accept or reject a request based on certain conditions. Before allowing a bearer request, the PGW performs several actions to decide the acceptability of the Create Bearer request. These actions are performed by various functions within the PGW 124 and by interfacing with other external EPC nodes like the PCRF 125 and the Charging System 148. Once the bearer is established the user data is carried over GTP-U.
  • the PGW 124 also connects to the ANDSF 122 through opening a new connection over which to share detailed traffic flow information relating to traffic flows to and from an individual, single user equipment to enable the ANDSF to communicate to the user equipment, the identity of specific access networks for selection for carrying individual traffic flows between the communications network and the user equipment.
  • a PCC rule may be defined for a subscriber or for a corresponding bearer in the access network.
  • the PCC rules contain the QoS parameters to be applied, the pre-conditions that need to be met etc. If a PCC rule is defined for a bearer then it is applied whenever a request is received for that bearer from any subscriber. If the PCC rule is defined for a subscriber then it is only applied when a bearer request is received from that particular subscriber. PCC rules are checked at the time of setting up a bearer and then in the interim when there is a modification of the bearer for example when there are any changes to the conditions of the access such as radio access change etc.
  • PCC definition is performed by a part of the PGW known as the policy and charging enforcement function (PCEF) 127.
  • PCEF has the function of enforcing on user equipment, policies received over the Gx interface from the policy and charging rules function (PCRF) 124. Such policies can be related to QoS, PLMN change, access network (e.g. WWAN or WLAN), etc.
  • PCRF 125 provides details about active PCC rules to the PCEF, the PCEF determines if an existing bearer in the access network can be used. If no bearer exists with the corresponding combination of QoS Class Identifier (QCI) and allocation retention priority (ARP) values specified in the PCC rules, then the PCEF initiates the creation of new bearers.
  • QCI QoS Class Identifier
  • ARP allocation retention priority
  • the PGW 124 may host the important functions of PCEF 127 and DPI 128.
  • Other functions of the PGW normally include IP address allocation, where the PGW allocates IP addresses to the user equipment to establish packet data connections; packet routing and forwarding, where the PGW performs the required routing and forwarding of packets to and from the user equipment and the external IP network or Internet; on-line and off-line charging where the PGW triggers the on-line charging system (OCS) 148 over the Gy interface 154 for real-time charging and generating CDR's for off-line billing.
  • OCS on-line charging system
  • FIG. 2 shows signalling flows 21 -26 and payload (user plane) flows 27, 28 impinging on PGW 124 and ANDSF 122.
  • a request 21 for a specific Access Point Name (APN) arrives at the PGW from the user equipment 102 using any of the WWAN and ⁇ WLAN access networks.
  • the interface 202 shown in the Figure is a representational amalgamation of both 3GPP and non 3GPP access interfaces, including S2b, S2a, and S5.
  • the PGW does DPI on the request 21 and applies policy enforcement functions to the request 21 , as appropriate.
  • the PGW sends 22 a DIAMETER message over the new interface 126 between the PGW and ANDSF.
  • Access network selection criteria are contained in an ANDSF rules database 204.
  • PCC rules which are not used for access selection are contained in a PCRF rules database (not shown).
  • the ANDSF checks the information on the request against the rules database 204 and selects an appropriate IFOM rule from the rules database.
  • the ANDSF sends 23 the selected IFOM rule to the user equipment over the S14 interface.
  • the ANDSF responds 24 to the PGW DIAMETER message (22).
  • the PGW informs 25 the user equipment about the preferred access network for the requested traffic.
  • the user equipment switches access network and sends 26 the payload over the preferred access network to the destination (i.e. the desired APN) via the PGW and the SGi interface 145.
  • a response message 27 from the APN is received by the PGW and passed to the user equipment.
  • FIG. 3 shows in more detail the signalling flows using the proposed new interface 126 between PGW 124 and ANDSF 122.
  • Pre-requisites for these flows are that user equipment 102 is IFOM-capable to establish a Packet Data Network (PDN) connection over multiple (e.g. WWAN and WLAN) access networks.
  • PDN Packet Data Network
  • the PGW needs to also act as a Home Agent (HA) and support bearer binding and Evolved Packet System (EPS) bearer modification requests raised by the user equipment.
  • HA Home Agent
  • EPS Evolved Packet System
  • the PGW assigns to the user equipment, the home IP address (HoA) (i.e. the IP address for the WWAN session over 3GPP access 106) and the Home Network Prefix (HNP).
  • HoA home IP address
  • HNP Home Network Prefix
  • WLAN WLAN selection policies
  • WLANSP are the policies used by the user equipment to select a particular WLAN when more than one WLAN is available.
  • a mobile operator may, for example, have an agreement with certain ISP operators for use of their Wi-Fi hotspots.
  • User equipments with a subscription to that mobile operator may, as a result, have free access to Wi-Fi hotspots on that operator's WLAN, which will therefore be indicated as the preferred
  • the WLAN set in the WLANSP could also be influenced by other factors, such as load on the Wi-Fi network.
  • the user equipment uses the HNP to discover that it is on a foreign network (i.e. not the home network) and sends a binding update message to the PGW-HA (i.e. the PGW acting as Home Agent) with the Care of Address (CoA), i.e. the IP address on the WLAN.
  • the user equipment sends, in the binding update message, the IP address it receives for the WLAN session along with route filters, which are used to identify certain routes that can only be used via certain access networks.
  • the user equipment also indicates, in the binding update message, that it already has a HoA. This information is sent to the PGW-HA.
  • the binding update message also comprises indications that there is one binding associated with the HoA and another one associated with CoA and that the connection on the HoA is active.
  • the PGW then binds the CoA with the HoA and sends a Binding Acknowledgement.
  • the user equipment has essentially two data flows on the same PDN Connection: one over WWAN and another over WLAN.
  • IFOM requires support of the PGW for selective offload of data traffic between WWAN and WLAN access networks for certain data flows in a given PDN connection and thereafter for continuing the data flows simultaneously over WWAN and WLAN access networks. Support for IFOM is negotiated between the user equipment and ANDSF during the initial registration process of the user equipment. The user equipment and network will be aware of the IFOM capabilities at either side.
  • IFOM support is configured by the service provider dynamically using the ANSDF.
  • the configuration is implemented for a specific flow within the same APN or PDN connection.
  • the PGW can be configured with a specific APN that supports access from 3GPP and non 3GPP access networks and also supports IFOM.
  • IFOM rules need to be applied on a per-subscriber basis, the IFOM rules and related routing filters may be provisioned in the ANDSF by the service provider's business support system (BSS).
  • BSS business support system
  • a DPI rule for detecting the specific content, application or URL targeted in a request from the UE may be configured on the PCRF or directly on the PGW. In either case, the DPI rule is enforced by a part of the PGW known as the PCEF.
  • the IFOM capable user equipment is connected simultaneously to 3GPP and non 3GPP access networks and multiple bindings and multiple IP flows are registered at the PGW-HA, as mentioned above.
  • PGW supports PDN connection to a specific APN over both types of access network.
  • PGW allocates a HoA and CoA addresses and binds the two addresses together.
  • PGW uses the HNP to identify the non-3GPP access network so that the user equipment is ready to seamlessly transfer access between these connections.
  • the user equipment sends to PGW, a request for a specific content, application or URL.
  • the PGW performs DPI on the request and detects the specific APN.
  • the PGW sends to the PCRF, as a Gx modification request, a diameter CCR message indicating the detected APN, together with subscriber details, access network currently being used, etc., as per the configured DPI rule.
  • PCRF responds to the CCR message of step 5 with a diameter CCA message to the PGW comprising the user capabilities appropriate to the specific request and a policy that triggers the PGW to initiate communication with the ANDSF.
  • the PGW Upon the receiving the CCA from the PCRF, the PGW sends over the new interface 126 to the ANDSF a diameter CCR message comprising subscriber information, the currently used access network and the specific APN requested. This information is transferred in the CCR in the form of AVPs.
  • the main Attribute- Value Pairs include as Event Trigger AVP, Application Start, Application Identifier-AVP, Radio Access Technology (RAT)-type AVP, Application-Instance Identifier and Flow Information AVP along with other AVP's as per RFC 3588.
  • the ANDSF decides whether an access switch is required for that specific traffic or not.
  • the ANDSF checks the current access network indicated in the CCR RAT-type AVP and takes a decision (communicated in the CCA message in step 12, below) on a preferred access network (i.e. WWAN or WLAN). If the specific traffic is already flowing over the preferred access network, then the ANDSF does not need to communicate to the user equipment and will respond to the CCR indicating no change required to the access network.
  • the ANDSF has access to a database with IFOM rules configured by the operator.
  • the IFOM rules specify, among other things, a preferred access network.
  • the ANDSF checks the IFOM rules to select, based on the information provided in the CCR (see 7), the appropriate IFOM rule specifying the preferred access network (i.e. WWAN or WLAN) for the request.
  • the ANDSF sends the selected IFOM rule to the user equipment with an identifier derived from the Application Identifier-AVP for the APN requested by the user equipment in step 3 and the preferred access network type for that application.
  • the user equipment receives the IFOM rule and checks the rule against any known user preferences (e.g. whether to allow use of Wi-Fi or not). If no incompatibility is found between the received IFOM rule and any known user preferences, the user equipment accepts the IFOM rule, otherwise the IFOM rule is rejected. The user equipment initiates data-flow mobility procedures towards the PGW-HA in accordance with the IFOM rule.
  • any known user preferences e.g. whether to allow use of Wi-Fi or not.
  • step 10 user equipment sends IFOM rule acceptance or rejection ACK to the ANDSF.
  • ANDSF sends to the PGW, a diameter CCA, which is the response to the CCR message received in step 7.
  • a successful CCA message indicates that the user equipment has accepted the IFOM rule in step 1 1 . If the user equipment does not accept the IFOM rule then the CCA will contain a reject message with a cause code.
  • the user equipment sends, using the access network over which the user equipment is currently trying to access the specific APN, a bearer modification request to the PGW- HA with details of the user and the type of session.
  • the user equipment also sends to the PGW-HA over the same access network, a binding update with a modified routing rule to associate a particular traffic flow ID (FID) with a modified access binding ID (BID).
  • FID traffic flow ID
  • BID modified access binding ID
  • the PGW-HA updates to PCRF over the Gx interface to notify the PCRF, as appropriate, of the IP flow modification. If an on-line charging system (OCS) 148 update is required, the PGW also updates the OCS over the Gy interface in a diameter CCR message.
  • OCS on-line charging system
  • the PCRF (and OCS, as appropriate) sends to the PGW-HA a CCA in response to the modification request. If the PGW-HA receives a rejection in the CCA response from either PCRF or OCS, then the flow modification request will be rejected.
  • the PGW-HA sends to the user equipment, over the current access network, in a binding acknowledgment, acceptance or rejection of the modification request, as appropriate.
  • the PGW-HA will send, over the current access network, a rejection back to the user equipment.
  • the access to the specific APN proceeds without modification of the IP flow so as to reduce the end-user impact.
  • the user equipment On receipt of the rejection of the modification request in the binding acknowledgment, the user equipment does not retry modification and takes no further action in this regard.
  • the user equipment transfers the traffic for the specific APN to the new access network type as per the IFOM rule and the session continues seamlessly without any interruption or user intervention.
  • a software-controlled programmable processing device such as a microprocessor, digital signal processor or other processing device, data processing apparatus or system
  • a computer program for configuring a programmable device, apparatus or system to implement the foregoing described methods is envisaged as an aspect of the present invention.
  • the computer program may be embodied as source code or undergo compilation for implementation on a processing device, apparatus or system or may be embodied as data object code, for example.
  • FIG. 4 is a block diagram of a data processing system 40 suitable for the operation of embodiments of the present invention.
  • a central processor unit (CPU) 410 is communicatively connected to communications interface 408, a memory 412, a storage 414 and an input/output (I/O) interface 416 via a data bus 520.
  • the memory 412 can be any read/write storage device such as a random access memory (RAM) or a non-volatile storage device suitable for storing data for use by processor 412.
  • the storage 414 can be any read-only or read/write storage device such as a random access memory (RAM) or a non-volatile storage device suitable for the computer program for controlling the operation of processor 410.
  • Memory 412 and storage 414 may comprise the same device or devices.
  • the implementing computer program may be stored on a carrier medium in machine or device readable form, for example in solid-state memory, magnetic memory such as disk or tape, optically or magneto-optically readable memory such as compact disk or digital versatile disk etc., and the processing device utilises the program or a part thereof to configure it for operation.
  • the computer program may be supplied from a remote source embodied in a communications medium such as an electronic signal, radio frequency carrier wave or optical carrier wave.
  • a communications medium such as an electronic signal, radio frequency carrier wave or optical carrier wave.
  • carrier media are also envisaged as aspects of the present invention.
  • the user interface 416 is an interface to devices for the input or output of data provided to or received from a user or operator of computer system 40.
  • Examples of input/output devices connectable to user interface 416 include a keyboard, a mouse, a display (such as a monitor) and a network connection.
  • Communications interface 408 is an interface to other devices and may comprise one or more radio transmit interfaces and one or more wired or wireless core network interfaces.
  • the solution described here allows access selection policies to be deployed in the network and enforced by the network based on analysis of real-time traffic impinging on the user equipment 102.
  • This solution is user equipment 102 agnostic and is not reliant on any specific user equipment 102 decisionmaking capabilities for access selection.
  • This solution improves network efficiency. It is intended to switch the traffic between available access networks as a network function, which is transparent to the user. As a result user does not experience any interruption in the traffic during access switchover but provides the user with un-interrupted data and voice traffic over various access technologies thereby improving user satisfaction. Operators may be able to reduce CAPEX and OPEX as fewer radio sites may be required as a result of implementing the invention.
  • the solution described here provides service providers better control of the selection of access network.
  • DPI is described as yielding an APN
  • other traffic-related information may be detected through the DPI and may trigger the diameter CCR message to the PCRF indicating the detected traffic information as per the configured DPI rule.
  • Gx provides transfer of (QoS) policy and charging rules from PCRF to Policy and Charging Enforcement Function (PCEF) in the PDN GW.
  • QoS Quality of Service
  • PCEF Policy and Charging Enforcement Function
  • ISMP Inter-System Mobility Policy a set of operator-defined rules that affect access network selection decisions taken by the user equipment.
  • ISRP Inter System Routing Policy network selection rules for a user equipment with potentially more than one active access network connection (e.g., both LTE and Wi-Fi).
  • Such user equipment may employ IP flow mobility (IFOM)]
  • PCEF Policy and Charging Enforcement Function in PGW
  • PCRF Policy and Charging Rule Function in PGW
  • PDN Packet Data Network
  • the ANDSF communicates with the user equipment over the S14 reference point.
  • S5 S5 provides user plane tunnelling and tunnel management between SGW and PGW.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente invention concerne un serveur dans un réseau de communication configuré en vue de : recevoir des informations spécifiques à un flux de trafic individuel entre le réseau de communication et un équipement d'utilisateur sur un premier réseau d'accès d'un premier type de réseau d'accès ; les informations reçues comprenant des informations concernant le type de trafic du flux de trafic individuel et des informations relatives au premier type de réseau d'accès ; le serveur étant en outre configuré en vue de : lancer une détermination d'un réseau d'accès spécifique parmi le premier réseau d'accès et un second réseau d'accès d'un second type de réseau d'accès pour une sélection pour transporter le flux de trafic individuel entre le réseau de communication et l'équipement d'utilisateur ; la détermination étant fondée sur les informations reçues concernant le flux de trafic et le premier type de réseau d'accès et des informations préprogrammées sur le second type de réseau d'accès ; et le serveur étant en outre configuré en vue de : communiquer à l'équipement d'utilisateur l'identité du réseau d'accès spécifique parmi le premier ou le second réseau d'accès pour une sélection pour transporter le flux de trafic individuel entre le réseau de communication et l'équipement d'utilisateur.
PCT/EP2017/064915 2016-06-30 2017-06-19 Pilotage de trafic dans des réseaux d'accès WO2018001771A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
EP16177248 2016-06-30
EP16177248.8 2016-06-30

Publications (1)

Publication Number Publication Date
WO2018001771A1 true WO2018001771A1 (fr) 2018-01-04

Family

ID=56550685

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2017/064915 WO2018001771A1 (fr) 2016-06-30 2017-06-19 Pilotage de trafic dans des réseaux d'accès

Country Status (1)

Country Link
WO (1) WO2018001771A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2445266A1 (fr) * 2010-10-25 2012-04-25 Alcatel Lucent Contrôle de sélection de technologie d'accès/réseau d'accès pour le routage d'un trafic IP par un équipement d'utilisateur, et support QoS, dans un système de communication à accès multiple
US20130310030A1 (en) * 2012-05-21 2013-11-21 Tekelec, Inc. Methods, systems, and computer readable media for access network discovery and selection
EP2852223A1 (fr) * 2013-09-19 2015-03-25 Alcatel Lucent Accès au serveur andsf locale avec porteuse dédiée

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2445266A1 (fr) * 2010-10-25 2012-04-25 Alcatel Lucent Contrôle de sélection de technologie d'accès/réseau d'accès pour le routage d'un trafic IP par un équipement d'utilisateur, et support QoS, dans un système de communication à accès multiple
US20130310030A1 (en) * 2012-05-21 2013-11-21 Tekelec, Inc. Methods, systems, and computer readable media for access network discovery and selection
EP2852223A1 (fr) * 2013-09-19 2015-03-25 Alcatel Lucent Accès au serveur andsf locale avec porteuse dédiée

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for non-3GPP accesses (Release 13)", 3GPP STANDARD; 3GPP TS 23.402, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V13.6.0, 22 June 2016 (2016-06-22), pages 1 - 299, XP051123283 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP flow mobility and seamless Wireless Local Area Network (WLAN) offload; Stage 2 (Release 13)", 3GPP STANDARD; 3GPP TS 23.261, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V13.0.0, 15 December 2015 (2015-12-15), pages 1 - 22, XP051047181 *
"3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 13)", 3GPP STANDARD; 3GPP TS 23.203, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. V13.8.0, 22 June 2016 (2016-06-22), pages 1 - 245, XP051123382 *

Similar Documents

Publication Publication Date Title
US11888750B2 (en) Service flow processing method, communication method, and apparatus
US11438949B2 (en) Methods and apparatus to support network-based IP flow mobility via multiple wireless accesses for a wireless device
EP3399795B1 (fr) Système et procédé pour fournir une mobilité de flux de protocole internet dans un environnement de réseau
US9686317B2 (en) Network node and method to control routing or bypassing of deployed traffic detection function nodes
US10820359B2 (en) GPRS tunneling protocol (GTP) traffic hub and associated method of use
US9674764B2 (en) System and method for providing Internet protocol flow mobility in a network environment
US20140355536A1 (en) System and method providing fixed mobile convergence via bonded services
US10455626B2 (en) Terminal device and PCRF
EP2850786A1 (fr) Routage de trafic dans un réseau multi-domaines
US10841835B2 (en) Maximum bit rate control in a multi-access network
KR102303340B1 (ko) 트래픽 오프로딩 결정을 위한 방법 및 장치
CN102904856B (zh) 一种共享会话的控制方法及装置
US10277638B2 (en) Providing bonded services at a non-anchor node
US9629065B2 (en) Local access point name for use in accessing packet data networks
WO2016011832A1 (fr) Procédé et dispositif pour mettre en œuvre un déclenchement de mobilité de flux, et support d'informations
WO2012090401A1 (fr) Procédé pour la mobilité des flux ip et appareil associé
US20160277980A1 (en) Handing Over a Data Bearer Between Access Networks
Ahmed et al. Multi access data network connectivity and IP flow mobility in Evolved Packet System (EPS)
WO2018001771A1 (fr) Pilotage de trafic dans des réseaux d'accès
GB2551797A (en) Traffic sheering in access networks
CN106162801A (zh) 实现缺省路由决策的方法、核心网网元、用户设备及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17730193

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17730193

Country of ref document: EP

Kind code of ref document: A1