Mobile network operator and data service provider interoperation
First Claim
1. A method comprising:
- receiving, from a user device, an authentication request at a home subscriber server (HSS)-front end (FE) of a mobile network, the HSS-FE configured to be user data-less;
accessing a user data repository (UDR) of the mobile network from the HSS-FE to identify user data and subscribe to notifications regarding changes to that user data;
receiving a request at the HSS-FE for the user device to access a network application function of a non-internet protocol multimedia subsystem (IMS) data provider;
accessing the UDR of the mobile network from the HSS-FE to determine authentication information for the user device; and
authenticating the user device to the non-IMS data provider based on the authentication information.
4 Assignments
0 Petitions
Accused Products
Abstract
Embodiments of computer-implemented methods, systems, computing devices, and computer-readable media are described herein for allowing a mobile network operator to perform services on behalf of a non-internet protocol multimedia subsystem (non-IMS) data provider. In various embodiments, an application server (“AS”) front end of the data provider is communicatively connected to a user data repository (“UDR”) and a home subscription server (“HSS”). The HSS is also connected to the UDR. Neither the non-IMS AS nor the HSS store user data, but instead communicate with the UDR across various reference points. The communication across the reference points facilitates the HSS performing various user services on behalf of the non-IMS AS. Other embodiments include user access and authentication procedures in such a network architecture, as well as corresponding policy and charging architecture.
5 Citations
26 Claims
-
1. A method comprising:
-
receiving, from a user device, an authentication request at a home subscriber server (HSS)-front end (FE) of a mobile network, the HSS-FE configured to be user data-less; accessing a user data repository (UDR) of the mobile network from the HSS-FE to identify user data and subscribe to notifications regarding changes to that user data; receiving a request at the HSS-FE for the user device to access a network application function of a non-internet protocol multimedia subsystem (IMS) data provider; accessing the UDR of the mobile network from the HSS-FE to determine authentication information for the user device; and authenticating the user device to the non-IMS data provider based on the authentication information. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A non-internet protocol multimedia subsystem (IMS) application server (AS) comprising:
-
an application module configured to provide one or more applications of the non-IMS AS for access by a user equipment (UE); and a front end coupled with user data convergence (UDC) components of a mobile network through an interface with a home subscriber server (HSS)—
front end (FE) of the UDC components, wherein the front end is configured to use the interface to exchange user profile information associated with the UE with the HSS-FE, and the HSS-FE and the non-IMS AS are configured to not store the user profile information. - View Dependent Claims (7, 8, 9, 10, 11, 12, 13)
-
-
14. One or more non-transitory computer readable media having instructions that, when executed, cause a home subscriber server-front end (HSS-FE) to:
-
receive, via a first interface, a user service request from a non-internet protocol multimedia subsystem (IMS) application server (AS) of a data provider, the user service request related to user authentication, user billing, and/or user charging; and perform, via a second interface, a user service with a user data repository (UDR) based on the user service request, wherein the HSS-FE and the non-IMS AS are configured to not store user data at the HSS-FE and the non-IMS AS. - View Dependent Claims (15, 16, 17, 18)
-
-
19. One or more non-transitory computer-readable media having instructions that, when executed, cause a trigger function to:
-
communicatively couple to a user equipment and to a policy and charging rules function (PCRF) such that the trigger function is logically positioned between the user equipment and the PCRF; and alter one or more aspects of traffic handling of a mobile network with respect to data provided to the user equipment from a non-internet protocol multimedia subsystem (IMS) application server (AS) of a data provider. - View Dependent Claims (20, 21, 22, 23, 24, 25, 26)
-
Specification