IP Library Patent Application 14369000
Patent Application
App. No. 14/369,000

ALLOWING ACCESS TO SERVICES DELIVERED BY A SERVICE DELIVERY PLATFORM IN A 3GPP HPLMN, TO AN USER EQUIPMENT CONNECTED OVER A TRUSTED NON-3GPP ACCESS NETWORK

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
14/369,000
Abstract

Embodiments of the present invention include a method for allowing access to services delivered by a service delivery platform in a 3GPP HPLMN, to an User Equipment UE connected over a trusted non-3GPP Access Network AN, said method comprising: allowing delivery of said services to said UE not involving a mobile Edge Router of a PLMN but using a HPLMN service proxy between said trusted non-3GPP AN and said service delivery platform, an entity of said non-3GPP AN signalling user identification information to said HPLMN service proxy.

Claims (53)

1 . A method for allowing access to services delivered by a service delivery platform in a 3GPP HPLMN, to an User Equipment UE connected over a trusted non-3GPP Access Network AN, said method comprising:

allowing delivery of said services to said UE not involving a mobile Edge Router of a PLMN but using a HPLMN service proxy between said trusted non-3GPP AN and said service delivery platform,

an entity of said non-3GPP AN signalling user identification information to said HPLMN service proxy.

2 . A method according to claim 1 , wherein:

user identification information signalled by an entity of said non-3GPP AN to said HPLMN service proxy includes an association between IP address information of said UE as allocated by said non-3GPP AN, and service level identifier information of said UE in said HPLMN.

3 . A method according to claim 1 , comprising:

a 3GPP AAA server in said HPLMN signalling delivery information to an entity of said non-3GPP AN, wherein said delivery information includes information for said non-3GPP AN to be able to signal user identification information to said HPLMN service proxy.

4 . A method according to claim 1 , wherein:

delivery information signalled by a 3GPP AAA server in said HPLMN to an entity of said non-3GPP AN includes service level identifier information of said UE in said HPLMN.

5 . A method according to claim 1 , wherein:

delivery information signalled by a 3GPP AAA server in said HPLMN to an entity of said non-3GPP AN includes forwarding information allowing said non-3GPP AN entity to forward IP traffic targeting said service delivery platform via said HPLMN service proxy.

6 . A method according to claim 1 , wherein:

delivery information signalled by a 3GPP AAA server in said HPLMN to an entity of said non-3GPP AN includes filtering rules information allowing said non-3GPP AN entity to identify IP traffic targeting said service delivery platform.

7 . A method according to claim 1 , comprising:

an entity of said non-3GPP AN signalling user identification information to said HPLMN service proxy, when said UE has been successfully authenticated over said non-3GPP AN and IP address information has been allocated by said non-3GPP AN to said UE.

8 . A method according to claim 1 , comprising:

a 3GPP AAA server in said HPLMN signalling delivery information to an entity of said non-3GPP AN, as part of authorization data sent once said UE has been successfully authenticated over said non-3GPP AN.

9 . A method according to claim 1 , comprising:

an entity of said non-3GPP AN indicating to a 3GPP AAA server in said HPLMN, during authentication of said UE over said non-3GPP Access Network, whether said non-3GPP AN entity supports signalling of user identification information to said HPLMN service proxy.

10 . A method according to claim 1 , comprising:

a 3GPP AAA server in said HPLMN taking a decision whether said non-3GPP AN can be trusted, taking into account whether said non-3GPP AN has indicated it supports signalling of user identification information to said HPLMN service proxy.

11 . A method according to claim 1 , comprising:

an entity of said non-3GPP AN issuing AAA accounting signalling containing user identification information towards said HPLMN service proxy.

12 . A method according to claim 1 , comprising:

an entity of said non-3GPP AN sending an AAA Accounting Start message towards said HPLMN service proxy, containing user identification information, when said non-3GPP AN has allocated IP address information to said UE.

13 . A method according to claim 1 , comprising:

an entity of said non-3GPP AN sending an AAA Accounting Stop message towards said HPLMN service proxy, containing user identification information, when an association between said UE and IP address information allocated to said UE is released.

14 . A method according to claim 1 , wherein:

delivery information signalled by a 3GPP AAA server in said HPLMN to an entity of said non-3GPP AN includes addressing information allowing said non-3GPP AN entity to send AAA accounting signalling towards said HPLMN service proxy.

15 . An entity of a non-3GPP Access Network AN, such as in particular Broadband Network Gateway BNG of a BBF Access Network, configured, for allowing access to services delivered by a service delivery platform in a 3GPP HPLMN to an User Equipment UE connected over said non-3GPP AN corresponding to a trusted non-3GPP AN, allowing delivery of said services to said UE not involving a mobile Edge Router of a PLMN but using a HPLMN service proxy between said trusted non-3GPP AN and said service delivery platform, for:

signalling user identification information to said HPLMN service proxy.

16 . An entity of a non-3GPP AN according to claim 15 , wherein:

user identification information signalled by said entity of a non-3GPP AN to said HPLMN service proxy includes an association between IP address information of said UE as allocated by said non-3GPP AN, and service level identifier information of said UE in said HPLMN.

17 . An entity of a non-3GPP AN according to claim 15 , configured for:

signalling user identification information to said HPLMN service proxy, when said UE has been successfully authenticated over said non-3GPP AN and IP address information has been allocated by said non-3GPP AN to said UE.

18 . An entity of a non-3GPP AN according to claim 15 , configured for:

indicating to a 3GPP AAA server in said HPLMN, during authentication of said UE over said non-3GPP Access Network, whether said non-3GPP AN entity supports signalling of user identification information to said HPLMN service proxy.

19 . An entity of a non-3GPP AN according to claim 15 , configured for:

issuing AAA accounting signalling containing user identification information towards said HPLMN service proxy.

20 . An entity of a non-3GPP AN according to claim 15 , configured for:

sending an AAA Accounting Start message towards said HPLMN service proxy, containing user identification information, when said non-3GPP AN has allocated IP address information to said UE.

21 . An entity of a non-3GPP AN according to claim 15 , configured for:

sending an AAA Accounting Stop message towards said HPLMN service proxy, containing user identification information, when an association between said UE and IP address information allocated to said UE is released.

22 . A 3GPP AAA server, configured, for allowing access to services delivered by a service delivery platform in a 3GPP HPLMN to an User Equipment UE connected over a trusted non-3GPP Access Network Access Network AN, allowing delivery of said services to said UE not involving a mobile Edge Router of a PLMN but using a HPLMN service proxy between said trusted non-3GPP AN and said service delivery platform, for:

signalling delivery information to an entity of said non-3GPP AN, wherein said delivery information includes information for said non-3GPP AN to be able to signal user identification information to said HPLMN service proxy.

23 . A 3GPP AAA server according to claim 22 , wherein:

delivery information signalled by said 3GPP AAA server in said HPLMN to an entity of said non-3GPP AN includes service level identifier information of said UE in said HPLMN.

24 . A 3GPP AAA server according to claim 22 , wherein:

delivery information signalled by said 3GPP AAA server in said HPLMN to an entity of said non-3GPP AN includes forwarding information allowing said non-3GPP AN entity to forward IP traffic targeting said service delivery platform via said HPLMN service proxy.

25 . A 3GPP AAA server according to claim 22 , wherein:

delivery information signalled by said 3GPP AAA server in said HPLMN to an entity of said non-3GPP AN includes filtering rules information allowing said non-3GPP AN entity to identify IP traffic targeting said service delivery platform.

26 . A 3GPP AAA server according to claim 22 , configured for:

taking a decision whether said non-3GPP AN can be trusted, taking into account whether said non-3GPP AN has indicated it supports signalling of user identification information to said HPLMN service proxy.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 3, 2015
From: THIEBAUT, LAURENT; LIVANOS, KONSTANTIN
To: ALCATEL LUCENT
Reel/Frame 036486/0613 →
RELEASE OF SECURITY INTEREST Recorded Aug 28, 2014
From: CREDIT SUISSE AG
To: ALCATEL LUCENT
Reel/Frame 033655/0304 →
SECURITY INTEREST Recorded Aug 7, 2014
From: ALCATEL LUCENT
To: CREDIT SUISSE AG
Reel/Frame 033500/0302 →