U.S. patent application number 16/737475 was filed with the patent office on 2020-05-07 for dynamic provision of application related sponsored data connectivity.
This patent application is currently assigned to Alcatel Lucent. The applicant listed for this patent is Alcatel Lucent. Invention is credited to Praveen MULEY, Laurent THIEBAUT.
Application Number | 20200145796 16/737475 |
Document ID | / |
Family ID | 55177908 |
Filed Date | 2020-05-07 |
![](/patent/app/20200145796/US20200145796A1-20200507-D00000.png)
![](/patent/app/20200145796/US20200145796A1-20200507-D00001.png)
![](/patent/app/20200145796/US20200145796A1-20200507-D00002.png)
![](/patent/app/20200145796/US20200145796A1-20200507-D00003.png)
![](/patent/app/20200145796/US20200145796A1-20200507-D00004.png)
![](/patent/app/20200145796/US20200145796A1-20200507-D00005.png)
United States Patent
Application |
20200145796 |
Kind Code |
A1 |
THIEBAUT; Laurent ; et
al. |
May 7, 2020 |
DYNAMIC PROVISION OF APPLICATION RELATED SPONSORED DATA
CONNECTIVITY
Abstract
A Policy Enforcement Function such as PCEF or TDF is configured
to receive from a Policy Controller such as PCRF, over an interface
such as Gx or Sd interface, a command related to a User Equipment
UE, the command referring to a Sponsoring Context Identifier,
Sponsoring Context ID, the Sponsoring Context ID serving as an
identifier of a Sponsoring Context to be applied to
application-related data traffic to be sponsored for the UE, the
Sponsoring Context providing a list of data flows to be
sponsored.
Inventors: |
THIEBAUT; Laurent; (Antony,
FR) ; MULEY; Praveen; (Mountain View, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Alcatel Lucent |
Nozay |
|
FR |
|
|
Assignee: |
Alcatel Lucent
Nozay
FR
|
Family ID: |
55177908 |
Appl. No.: |
16/737475 |
Filed: |
January 8, 2020 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
16068502 |
Jul 6, 2018 |
|
|
|
PCT/EP2017/050274 |
Jan 6, 2017 |
|
|
|
16737475 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04L 12/1475 20130101;
H04M 15/09 20130101; H04L 67/02 20130101; H04L 67/2852 20130101;
H04M 15/8083 20130101; H04L 12/1407 20130101; H04L 67/2804
20130101; H04L 12/1496 20130101; H04M 2215/0192 20130101; H04L
41/0893 20130101; H04W 4/24 20130101; G06Q 30/0222 20130101; H04L
67/20 20130101 |
International
Class: |
H04W 4/24 20060101
H04W004/24; H04L 29/08 20060101 H04L029/08; H04L 12/14 20060101
H04L012/14; H04L 12/24 20060101 H04L012/24; H04M 15/00 20060101
H04M015/00 |
Foreign Application Data
Date |
Code |
Application Number |
Jan 8, 2016 |
EP |
16305015.6 |
Claims
1. An apparatus, comprising: at least one processor; and at least
one memory including computer program code, the at least one memory
and the computer program code configured to, with the at least one
processor, cause the apparatus at least to provide policy
enforcement functions in a mobile communication network, receive a
command containing a pointer to a list of sponsored data flows
defined by a third party service provider, fetch said list of
sponsored data flows from a repository storing said list, using
said pointer to said list, and provide said policy enforcement
functions based on said command and on said list of sponsored data
flows.
2. The apparatus according to claim 1, wherein the at least one
memory and the computer program code are configured to, with the at
least one processor, cause the apparatus at least to: fetch said
list by sending to said repository a hypertext transfer protocol
request on a hypertext transfer protocol uniform resource locator
pointing to said list.
3. The apparatus according to claim 1, wherein a caching time
controls how long said list is valid.
4. A method comprising: providing policy enforcement functions in a
mobile communication network, receiving a command containing a
pointer to a list of sponsored data flows defined by a third party
service provider, fetching said list of sponsored data flows from a
repository storing said list, using said pointer to said list, and
providing said policy enforcement functions based on said command
and on said list of sponsored data flows.
5. The method according to claim 4, wherein the fetching fetches
said list by sending to said repository a hypertext transfer
protocol request on a hypertext transfer protocol uniform resource
locator, pointing to said list.
6. The method according to claim 4, wherein a caching time controls
how long said list is valid.
7. The apparatus according to claim 1, wherein the at least one
memory and the computer program code are configured to, with the at
least one processor, cause the apparatus at least to: fetch said
list if said list has not already been fetched or if a caching time
controlling how long said list is valid has expired.
8. The apparatus according to claim 1, wherein said apparatus
comprises a policy and charging enforcement function and said
command comprises a policy and charging control rule.
9. The apparatus according to claim 1, wherein said apparatus
comprises a traffic detection function and said command comprises
an application detection and control rule.
10. The method according to claim 4, comprising: fetching said list
if said list has not already been fetched or if a caching time
controlling how long said list is valid has expired.
11. The method according to claim 4, wherein said policy
enforcement functions comprise policy and charging enforcement
functions and said command comprises a policy and charging control
rule.
12. The method according to claim 4, wherein said policy
enforcement functions comprise traffic detection functions and said
command comprises an application detection and control rule.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This is a continuation of U.S. application Ser. No.
16/068,502 filed on Jul. 6, 2018, which is a national phase under
35 U.S.C. .sctn. 371 of PCT International Application No.
PCT/EP2017/050274 which has an International filing date of Jan. 6,
2017, which claims priority to European Application No. 16305015.6
filed Jan. 8, 2016, the entire contents of each of which are hereby
incorporated by reference.
BACKGROUND
1. Field
[0002] The present invention generally relates to communication
networks and systems, in particular mobile communication networks
and systems.
2. Description of Related Art
[0003] Descriptions of mobile networks and systems can be found in
the literature, such as in particular in Technical Specifications
published by standardization bodies such as for example 3GPP
(3.sup.rd Generation Partnership Project).
[0004] In general, in a mobile communication system, a terminal
(also called User Equipment UE) has access to various application
services via a mobile network (PMN). In particular, a terminal has
access to IP-based application services via an IP-Connectivity
Access Network (IP-CAN). An example of IP-CAN is EPS (Evolved
Packet System) network, specified in particular in 3GPP TS 23.401
and TS 23.402. An EPS network comprises EPC (Evolved Packet Core)
that can be accessed by different Radio Access Networks (such as
for example E-UTRAN).
[0005] Policy and Charging Control (PCC) functionality is specified
in particular in 3GPP TS 23.203. PCC functions include in
particular: PCRF (Policy and Charging Rules Function), PCEF (Policy
and Charging Enforcement Function), TDF (Traffic Detection
Function), AF (Application Function), SPR (Subscriber Profile
Repository). Interfaces within PCC architecture include in
particular: Gx interface between PCRF and PCEF, Rx interface
between AF and PCRF, Sd interface between PCRF and TDF. An example
of PCC architecture is recalled in FIG. 1 taken from 3GPP TS
23.203.
[0006] A feature called Sponsored Data Connectivity has been
introduced in such systems. In particular, PCC usage for Sponsored
Data Connectivity has been specified in 3GPP TS 23.203. As defined
in particular in 3GPP TS 23.203, with sponsored data connectivity,
the Sponsor has a business relationship with the operator and the
Sponsor reimburses the operator for the user's data connectivity in
order to allow the user access to an associated Application Service
Provider's (ASP) services. An example of deployment for Sponsored
Data Connectivity is recalled in FIG. 2 taken from 3GPP TS
23.203.
[0007] As recognized by the inventors and as will be described with
more details later, there is a need to improve PCC usage for
Sponsored Data Connectivity.
SUMMARY
[0008] Embodiments of the present invention in particular address
such needs.
[0009] These and other objects are achieved, in one aspect, by a
Policy Enforcement Function such as PCEF or TDF, configured to:
[0010] receive from a Policy Controller such as PCRF, over an
interface such as Gx or Sd interface, a command related to a User
Equipment UE, said command referring to a Sponsoring Context
Identifier, Sponsoring Context ID, said Sponsoring Context ID
serving as an identifier of a Sponsoring Context to be applied to
application-related data traffic to be sponsored for said UE, said
Sponsoring Context providing a list of data flows to be
sponsored.
[0011] These and other objects are achieved, in another aspect, by
a Policy Controller, such as PCRF, configured to: [0012] send to a
Policy Enforcement Function such as PCEF or TDF, over an interface
such as Gx or Sd interface, a command related to a User Equipment
UE, said command referring to a Sponsoring Context Identifier,
Sponsoring Context ID, said Sponsoring Context ID serving as an
identifier of a Sponsoring Context to be applied to
application-related data traffic to be sponsored for said UE, said
Sponsoring Context providing a list of data flows to be
sponsored.
[0013] These and other objects are achieved, in another aspect, by
an application-related entity such as AF interfacing with a Policy
Controller such as PCRF, over an interface such as Rx interface,
said application-related entity configured to: [0014] send to said
Policy Controller a Sponsoring Context Identifier, Sponsoring
Context ID, for a user, said Sponsoring Context ID serving as an
identifier of a Sponsoring Context to be applied to
application-related data traffic to be sponsored for said user,
said Sponsoring Context providing a list of data flows to be
sponsored.
[0015] These and other objects are achieved, in another aspect, by
a Content Server, referred to as Sponsoring Context Repository,
configured to: [0016] provide a Sponsoring Context to be applied to
application-related data traffic to be sponsored for a User
Equipment UE, upon reception of a request including a Sponsoring
Context Identifier, Sponsoring Context ID, said Sponsoring Context
ID serving as a pointer to said Sponsoring Context stored in said
Sponsoring Context Repository, said Sponsoring Context providing a
list of data flows to be sponsored.
[0017] These and other objects are achieved, in another aspect, by
a OAM equipment of a mobile network, configured to: [0018] create
in a content server, referred to as Sponsoring Context Repository,
a Sponsoring Context document, identified by a Sponsoring Context
Identifier, Sponsoring Context ID, said Sponsoring Context ID
serving as information to build an identifier of a Sponsoring
Context stored in said Sponsoring Context document.
[0019] These and other objects are achieved, in another aspect, by
method for dynamic provision of application related sponsored data
connectivity, said method comprising at least one step performed by
at least one of a thus configured: Policy Enforcement Function such
as PCEF or TDF, Policy Controller such as PCRF, application-related
entity such as AF, content server referred to as Sponsoring Context
Repository, OAM entity of a mobile network.
BRIEF DESCRIPTION OF THE DRAWINGS
[0020] Some embodiments of apparatus and/or methods in accordance
with embodiments of the present invention are now described, by way
of example only, and with reference to the accompanying drawings,
in which:
[0021] FIG. 1 is intended to recall an example of PCC
architecture,
[0022] FIG. 2 is intended to recall an example of deployment for
Sponsored Data Connectivity,
[0023] FIG. 3 is intended to recall a signaling flow for IP-CAN
session establishment,
[0024] FIG. 4 is intended to recall a signaling flow for IP-CAN
session modification (PCRF initiated),
[0025] FIG. 5 is intended to illustrate an example of signaling
flow, according to embodiments of the invention.
[0026] ABBREVIATIONS [0027] ADC Application Detection and Control
[0028] AF Application Function [0029] APN Access Point Name [0030]
EPC Evolved Packet Core [0031] EPS Evolved Packet System [0032]
HTTP HyperText Transfer Protocol [0033] IP-CAN IP-Connectivity
Access Network [0034] MNO Mobile Network Operator [0035] OAM
Operation And Maintenance [0036] PCC Policy and Charging Control
[0037] PCEF Policy and Charging Enforcement Function [0038] PCRF
Policy and Charging Rules Function [0039] PGW PDN Gateway [0040]
SPR Subscription Profile Repository [0041] TDF Traffic Detection
Function [0042] UE User Equipment [0043] URL Uniform Resource
Locator
DETAILED DESCRIPTION
[0044] Following description of various aspects and/or embodiments
of the invention will be made by way of example for the case of the
usage of the Sponsoring Context ID in the case of a PGW (PCEF).
However, as understood by the skilled person, embodiments of the
invention are not limited to such case.
[0045] 3GPP as part of a Study on sponsored data connectivity
improvements (FS-SDCI, whose WID is in document SP-150627) is
working on improvements of the Sponsored data connectivity topic.
This study especially addresses the following: "This key issue
shall study: [0046] 1. How to support a dynamic provisioning of
Sponsored data flow beyond layers 3 and 4 (e.g. URLs) from
3rd-party service providers to operator networks."
[0047] The Sponsored data connectivity feature has been specified
as part of 3gpp Re110 and is documented in 3GPP TS 23.203 (for
example Annex N)
[0048] Note: in all this document the Third party may also
correspond to an internal application of the operator.
[0049] One of the usages of sponsored data connectivity is the
possibility for a Third party to sponsor advertisement. This kind
of sponsoring would apply to a collection of users (possibly to all
users).
[0050] The FS-SDCI study has thus following facets: [0051] Allowing
a 3.sup.rd party to define the sponsored data flows not only by
specifying 5 T-uples.sup.1 (as defined in current 3GPP TS 23.203)
but by giving higher layer information such as a list of sponsored
URL .sup.1 IP address and ports [0052] Avoiding overloading the Rx
and Gx interfaces by repeating the same list of sponsored URL over
a Rx and a Gx Diameter session set-up for each user (as defined in
current 3GPP TS 23.203, the list of sponsored data flows is
explicitly provided over a Rx and a Gx Diameter session set-up for
each user) [0053] Provide flexibility for the Third part capability
to change the list of sponsored flows [0054] Allow the operator to
control the feature.
[0055] In some embodiments:
[0056] The QoS requirements sent by the policy controller (e.g.
PCRF in EPC architecture defined in 3GPP TS 23.203) to the Policy
enforcement Function (e.g. PCEF located in the PGW or in the BNG as
defined in 3GPP TS 23.203 or TDF as defined in 3GPP TS 23.203) does
not contain the list of flows to be sponsored but a pointer
(actually an HTTP URL) to this list: the Sponsoring Context Id.
[0057] In some embodiments:
[0058] When the PCEF (PGW) or TDF receives a PCC/ADC rule referring
to a Sponsoring context Id, it fetches the Sponsoring Context i.e.
the list of flows that are sponsored (HTTP GET on the URL in the
Sponsoring Context Id). As HTTP is used, caching techniques ensure
that the PCEF/TDF does not need to fetch the list of flows that are
sponsored for each user (Gx) session associated with an already
known Sponsoring Context Id. The caching time may control how long
the list of sponsored flows is valid
[0059] In some embodiments:
[0060] The Sponsoring Context may correspond to a list of [0061]
URL that are sponsored [0062] Server name indication (SNI) as
specified in IETF RFC 6066 [0063] SNI is an extension to the TLS
protocol by which a client indicates which hostname it is
attempting to connect to at the start of the TLS handshaking
process. This allows a server to present multiple certificates on
the same IP address and TCP port number and hence allows multiple
secure (HTTPS) websites (or any other Service over TLS) to be
served off the same IP address without requiring all those sites to
use the same certificate [0064] . . .
[0065] In some embodiments:
[0066] The Sponsoring context Id may be dynamically passed from the
3rd party to the operator via Rx (in this case the 3rd party
selects which UE will benefit from the sponsoring context) or
statically configured in the PCRF (policy rules)(in that case the
Sponsoring context Id applies to a collection of users, for example
to the traffic of all users on a given APN or to the traffic of
some user categories on an APN). Based on policy rules (and/or on
information received on Rx) the PCRF decides whether to put a
Sponsoring Context Id in the Gx(/Sd) commands sent to a PCEF(/TDF)
about an UE and decides on the value of this Sponsoring Context
Id.
[0067] In some embodiments:
[0068] The Content server (Sponsoring context Repository) that
stores the Sponsoring Context (e.g. list of sponsored URL) belongs
to the operator so is under control of the operator but the Third
party may modify the list of sponsored flows as often as it desires
based on its own business needs. This is to be controlled by
business agreements between the operator and the Third party
[0069] FIG. 5 depicts an example of signaling flow for the case of
the usage of the Sponsoring Context Id in the case of a PGW
(PCEF).
[0070] In FIG. 5, the dotted lines correspond to optional
interactions.
[0071] Following operations may be distinguished:
[0072] Off Line Operations (Operations not Related with an User
Activity)
[0073] In some embodiments, part or all of following steps may be
provided: [0074] 0. The Third party and the operator (MNO)
negotiate a sponsoring agreement that is identified by a Sponsoring
Context Id which is an unique identifier (e.g. URL) that refers to
the Sponsoring Context i.e. to the actual list of Flows that the
Third party is ready to sponsor (i.e. the Sponsoring context).
[0075] The Sponsoring Context Id refers to a content server that is
hosted by the (OAM of the) operator. This allows the operator to
control the list of flows that Third party may sponsor. [0076] 1.
The operator [0077] a. Creates in the Sponsoring context Repository
a Sponsoring Context document identified by the Sponsoring Context
Id. [0078] b. May modify PCRF policies accordingly, e.g. may create
policy rules that associate an APN, an user category, a
subscription type, etc. . . . with one or more Sponsoring Context
Id. [0079] 2. The Third party updates the list of flows it is ready
to sponsor by e.g. adding/modifying/removing entries (URL, . . . )
in the Sponsoring Context stored in the Sponsoring context
Repository. These operations are controlled by the operator
OAM.
[0080] "on-line" operations (operations related with an user
activity): actions at an IP-CAN Session Establishment
[0081] In some embodiments, part or all of following steps may be
provided: [0082] 3. An UE sets up a PDN connection as described in
FIG. 3 corresponding to 3GPP TS 23.203 FIGS. 7.2-1: "IP-CAN Session
Establishment".
[0083] The PCEF/TDF request policies from the PCRF.
[0084] This is done via an indication of IP-CAN session
establishment. Steps 2 to 5 of FIG. 3 take place without
modification [0085] 4. (as part of step 7 of FIG. 3 in case of
PCEF) Based on policy rules the PCRF decides whether to put a
Sponsoring Context Id in the Gx(/Sd) commands to be sent to the
PCEF(/TDF) about an UE and decides on the value of this Sponsoring
Context Id. For example for this decision, the PCRF may use: [0086]
The APN of the target IPCAN session (in that case all UE are
associated with the same sponsoring context, e.g. corresponding to
ads). [0087] An user category received from the SPR (Subscriber
Policy repository) as defined in 3GPP TS 23.203 [0088] Or any
combination of these parameters [0089] Or any other parameter
[0090] 5. The PCRF provides the PCEF/TDF with PCC/ADC rules.
[0091] In case of a PCEF as part of the PCRF acknowledgement of the
IP-CAN session establishment (step 14 of FIG. 3) the PCRF may send
PCC rules related with Sponsoring Context.
[0092] In case of a TDF as part of the TDF Session establishment
request (step 8 of FIG. 3) the PCRF may send ADC rules related with
Sponsoring Context
[0093] The Sponsoring Context Id may be provided in a PCC/ADC rule
instead of an application ID. This allows associating flows
identified by the Sponsoring Context Id with existing PCC
information such as Rating Groups (charging), QoS, Usage
monitoring, etc . . . . [0094] 6. When the PCEF or TDF receives a
PCC/ADC rule referring to an unknown Sponsoring context Id (i.e. a
Sponsoring context Id that it has not yet resolved), it fetches
from the Sponsoring context Repository the Sponsoring Context i.e.
the list of flows that are sponsored (HTTP GET on the URL in the
Sponsoring Context Id). As HTTP is used, caching techniques ensure
that the PCEF/TDF does not need to fetch the list of flows that are
sponsored for each user (Gx/Sd) session associated with an already
known/resolved Sponsoring Context Id. The caching time may control
how long the list of sponsored flows is valid. [0095] 7. The
PCEF/TDF starts applying the PCC/ADC rule (charging, QoS control,
usage monitoring, etc. . . . ) to the flows identified by the
Sponsoring context Id (whose identifiers have been received in the
Sponsoring Context). [0096] 8. The IP-CAN Session Establishment is
further processed as in steps 15 to 19 of FIG. 3: [0097] "on-line"
operations (operations related with an user activity): actions at
an Rx request from the Third party application
[0098] In some embodiments, part or all of following steps may be
provided: [0099] 9. The Third party application may decide to apply
Sponsoring only for some users. In that case it may provide the
sponsoring context Id to the PCRF over an Rx session (invoking step
1a of FIG. 4 corresponding to 3GPP TS 23.203 FIG. 7.5: IP-CAN
Session Modification; PCRF initiated). Steps 2 to 11 of FIG. 4 may
take place [0100] 10. The PCRF provides the PCEF/TDF with updated
PCC/ADC rules
[0101] The PCRF may send to the PCEF the Policy and Charging Rules
Provision as in Step 12 of FIG. 4. As part of this step the PCRF
may provide Sponsoring context Id as part of the PCC rule
information sent over Gx.
[0102] The PCRF may send to the TDF updated ADC rules as part of a
Sd session modification (as in step 5 of FIG. 4). As part of this
step the PCRF may provide Sponsoring context Id as part of the ADC
rule information sent over Sd [0103] 11. The PCEF/TDF action is
similar to that described at step 6 [0104] 12. The PCEF/TDF action
is similar to that described at step 7
[0105] Such mechanism in particular avoids the PCC chain (Rx,
Gx/Sd) to have to pass long lists of URL that a Third party
provider is ready to sponsor. [0106] NOTE: The Sponsoring context
Id passed over Gx/Sd does not need to correspond to the full URL
that the PCEF/TDF uses in step 6/11 to fetch the sponsoring
Context: The Sponsoring Context ID may [0107] either include a HTTP
URL pointing to the Sponsoring Context [0108] or include
information to be used to build a HTTP URL pointing to the
Sponsoring Context. For example, the sponsoring context Id is
"OTT-x/sponsor-Ad" and the PCEF/TDF adds a fixed URL part like
"https://www.operator.com/sponsor-context/" to build the final
target
"https://www.operator.com/sponsor-context/OTT-x/sponsor-Ad"
[0109] Various aspects of the invention include (though not being
limited to) following aspects.
[0110] One aspect of the invention is a Policy Enforcement Function
such as PCEF or TDF
[0111] Various embodiments may be provided, including (though not
being limited to) following embodiments, which may be taken alone
or in combination, according to various combinations.
[0112] In an embodiment, said Policy Enforcement Function is
configured to: [0113] receive from a Policy Controller such as
PCRF, over an interface such as Gx or Sd interface, a command
related to a User Equipment UE, said command referring to a
Sponsoring Context Identifier, Sponsoring Context ID, said
Sponsoring Context ID serving as an identifier of a Sponsoring
Context to be applied to application-related data traffic to be
sponsored for said UE, said Sponsoring Context providing a list of
data flows to be sponsored.
[0114] In an embodiment, said Policy Enforcement Function is
configured to: [0115] fetch said Sponsoring Context from a content
server referred to as Sponsoring Context Repository, using said
Sponsoring Context ID as a pointer to said Sponsoring Context
stored in said Sponsoring Context Repository.
[0116] In an embodiment, said Policy Enforcement Function is
configured to: [0117] fetch said Sponsoring Context from a content
server referred to as Sponsoring Context Repository by sending to
said content server a HTTP request, such as HTTP GET, on an HTTP
URL corresponding to the content of said Sponsoring Context ID or
built using the content of said Sponsoring Context ID.
[0118] In an embodiment, said Policy Enforcement Function is
configured to: [0119] receive said Sponsoring Context ID with an
associated policy rule such as PCC or ADC rule.
[0120] In an embodiment, said Policy Enforcement Function is
configured to: [0121] receive said Sponsoring Context ID in a
command acknowledging establishment of an IP-CAN session
establishment for said UE, such as Acknowledge
[0122] IP-CAN Session Establishment.
[0123] Another aspect of the invention is a Policy Controller, such
as PCRF.
[0124] Various embodiments may be provided, including (though not
being limited to) following embodiments, which may be taken alone
or in combination, according to various combinations.
[0125] In an embodiment, said Policy Controller is configured to:
[0126] send to a Policy Enforcement Function such as PCEF or TDF,
over an interface such as Gx or Sd interface, a command related to
a User Equipment UE, said command referring to a Sponsoring Context
Identifier, Sponsoring Context ID, said Sponsoring Context ID
serving as an identifier of a Sponsoring Context to be applied to
application-related data traffic to be sponsored for said UE, said
Sponsoring Context providing a list of data flows to be
sponsored.
[0127] In an embodiment, said Policy Controller is configured to:
[0128] associate said Sponsoring Context ID with said UE, based on
at least one, or a combination of, parameters related to said UE
including: [0129] An APN of an IP-CAN session, [0130] A user
category, [0131] A subscription type.
[0132] In an embodiment, said Policy Controller is configured to:
[0133] store policy rules associating said APN and/or user category
and/or subscription Type with one or more Sponsoring Context
ID.
[0134] In an embodiment, said Policy Controller is configured to:
[0135] send said Sponsoring Context ID to said Policy Enforcement
Function in a command acknowledging establishment of an IP-CAN
session for said UE, such as Acknowledge IP-CAN Session
Establishment.
[0136] In an embodiment, said Policy Controller is configured to:
[0137] receive said Sponsoring Context ID from an
application-related entity such as an AF, over an interface such as
a Rx interface.
[0138] In an embodiment, said Policy Controller is configured to:
[0139] send said Sponsoring Context ID to said Policy Enforcement
Function in a command such as Policy and Charging Rules
Provision.
[0140] In an embodiment, said Policy Controller is configured to:
[0141] send said Sponsoring Context ID to said Policy Enforcement
Function in a command such as Sd session modification.
[0142] In an embodiment, said Policy Controller is configured to:
[0143] send said Sponsoring Context ID to said Policy Enforcement
Function with an associated policy rule such as PCC or ADC
rule.
[0144] In an embodiment: [0145] said Sponsoring Context ID includes
a HTTP URL pointing to said Sponsoring Context or includes
information to be used to build a HTTP URL pointing to said
Sponsoring Context.
[0146] Another aspect of the invention is an application-related
entity such as AF interfacing with a Policy Controller such as
PCRF, over an interface such as Rx interface.
[0147] Various embodiments may be provided, including (though not
being limited to) following embodiments, which may be taken alone
or in combination, according to various combinations.
[0148] In an embodiment, said application-related entity is
configured to: [0149] send to said Policy Controller a Sponsoring
Context Identifier, Sponsoring Context ID, for a user, said
Sponsoring Context ID serving as an identifier of a Sponsoring
Context to be applied to application-related data traffic to be
sponsored for said user, said Sponsoring Context providing a list
of data flows to be sponsored.
[0150] In an embodiment, said application-related entity is
configured to: [0151] invoke a session such as Rx session over said
interface such as Rx interface, for sending said Sponsoring Context
ID to said Policy Controller.
[0152] In an embodiment: [0153] said Sponsoring Context ID includes
a HTTP URL pointing to said Sponsoring Context or includes
information to be used to build a HTTP URL pointing to said
Sponsoring Context.
[0154] In an embodiment, said application-related entity is
configured to: [0155] update the content of the Sponsoring Context
under control of the OAM of the operator.
[0156] Another aspect of the invention is a Content Server,
referred to as Sponsoring Context Repository.
[0157] Various embodiments may be provided, including (though not
being limited to) following embodiments, which may be taken alone
or in combination, according to various combinations.
[0158] In an embodiment, said Content Server is configured to:
[0159] provide a Sponsoring Context to be applied to
application-related data traffic to be sponsored for a User
Equipment UE, upon reception of a request including a Sponsoring
Context Identifier, Sponsoring Context ID, said Sponsoring Context
ID serving as a pointer to said Sponsoring Context stored in said
Sponsoring Context Repository, said Sponsoring Context providing a
list of data flows to be sponsored.
[0160] In an embodiment, said Content Server is configured to:
[0161] receive said request from a Policy Enforcement Function such
as PCEF or TDF.
[0162] In an embodiment, said Content Server is configured to:
[0163] said Sponsoring Context ID including information to build a
HTTP URL pointing to said Sponsoring Context, provide said
Sponsoring Context upon reception of a HTTP request, such as HTTP
GET, on said HTTP URL.
[0164] Another aspect of the invention is a OAM equipment of a
mobile network.
[0165] Various embodiments may be provided, including (though not
being limited to) following embodiment.
[0166] In an embodiment, said OAM equipment is configured to:
[0167] create in a content server, referred to as Sponsoring
Context Repository, a Sponsoring Context document, identified by a
Sponsoring Context Identifier, Sponsoring Context ID, said
Sponsoring Context ID serving as information to build an identifier
of a Sponsoring Context stored in said Sponsoring Context
document.
[0168] Another aspect of the invention is a method for dynamic
provision of application related sponsored data connectivity, said
method comprising at least one step performed by at least one of a
thus configured: Policy Enforcement Function such as PCEF or TDF,
Policy Controller such as PCRF, application-related entity such as
AF, content server referred to as Sponsoring Context Repository,
OAM entity of a mobile network.
[0169] Other possible embodiments than described above are also
possible, e.g. where the Policy Controller is another entity than
the PCRF of 4G-EPC such as the function of the 5G Core Network
determining policies for the network or where the Policy
Enforcement Function may be any entity enforcing policies to user
plane traffic such as the PDN-GW-U and TDF-U defined in 3GPP TR
23.714 or the entity enforcing policies to user plane traffic in a
5G Core Network.
[0170] A person of skill in the art would readily recognize that
steps of various above-described methods can be performed by
programmed computers. Herein, some embodiments are also intended to
cover program storage devices, e.g., digital data storage media,
which are machine or computer readable and encode
machine-executable or computer-executable programs of instructions,
wherein said instructions perform some or all of the steps of said
above-described methods. The program storage devices may be, e.g.,
digital memories, magnetic storage media such as a magnetic disks
and magnetic tapes, hard drives, or optically readable digital data
storage media. The embodiments are also intended to cover computers
programmed to perform said steps of the above-described
methods.
* * * * *
References