IP Library › Granted Patent US 12,262,446
Granted Patent B2
US 12,262,446 · App. 17/954,717 · Granted Mar 25, 2025

Providing a roaming policy federation in a third generation partnership project (3GPP) network environment

Inventors: Mark Grayson (Berkshire, GB); Timothy Peter Stammers (Raleigh, NC); Desmond Joseph O'Connor (London, GB); Bart A. Brinckman (Nevele, BE)
Assignee: CISCO TECHNOLOGY, INC.
H04W8/12
View Patent ↗
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 12,262,446
App. No.
17/954,717
Granted
Mar 25, 2025
Kind
B2
Abstract

Presented herein are techniques associated with replicating an OpenRoaming™ policy federation in a Third Generation Partnership Project (3GPP) network environment. For example, techniques herein provide a roaming policy federation architecture for a 3GPP network environment. In one example a method is provided that may include encoding at least one multi-bit roaming policy for an identity provider and a plurality of bit-wise combinatorial permutations of the at least one multi-bit roaming policy within each of a plurality of multi-bit 3GPP broadcast identifiers, wherein the at least one multi-bit roaming policy includes bit-wise roaming policy information for the identity provider and configuring the multi-bit 3GPP broadcast identifiers for a mobile device associated with the identity provider, wherein the multi-bit 3GPP broadcast identifiers indicate that the mobile device is to connect to a visited radio access network associated with a local Internet Protocol (IP) access service or a home routed access service.

Claims (36)

1. A method, comprising:

encoding at least one multi-bit roaming policy for an identity provider and a plurality of bit-wise combinatorial permutations of the at least one multi-bit roaming policy within each of a plurality of multi-bit Third Generational Partnership Project (3GPP) broadcast identifiers, wherein the at least one multi-bit roaming policy includes bit-wise roaming policy information for the identity provider; and

provisioning the plurality of multi-bit 3GPP broadcast identifiers for a mobile device associated with the identity provider, wherein the plurality of multi-bit 3GPP broadcast identifiers indicate that the mobile device is to connect to a visited radio access network associated with a local Internet Protocol (IP) access service or a home routed access service.

2. The method of claim 1 , wherein the identity provider supports both the local IP access service and the home routed access service.

3. The method of claim 2 , wherein the plurality of multi-bit 3GPP broadcast identifiers are configured for the mobile device in a prioritized order that identifies a preference of the identity provider for the mobile device to connect to a visited radio access network based on the prioritized order.

4. The method of claim 3 , wherein the prioritized order identifies a preference of the identity provider for the mobile device to connect to an access network that is configured to provide one of the local IP access service or the home routed access service.

5. The method of claim 4 , wherein detecting, by the mobile device, a first multi-bit 3GPP broadcast identifier of the plurality of multi-bit 3GPP broadcast identifiers being broadcast by a first visited radio access network and a second multi-bit 3GPP broadcast identifier of the plurality of multi-bit 3GPP broadcast identifiers being broadcast by a second visited radio access network triggers the mobile device to determine, a highest priority multi-bit 3GPP broadcast identifier of the first multi-bit 3GPP broadcast identifier and the second multi-bit 3GPP broadcast identifier based on the prioritized order of the plurality of multi-bit 3GPP broadcast identifiers.

6. The method of claim 5 , wherein determining the highest priority multi-bit 3GPP broadcast identifier being the first multi-bit 3GPP broadcast identifier triggers the mobile device to perform an authentication with the identity provider via the first visited radio access network or determining the highest priority multi-bit 3GPP broadcast identifier being the second multi-bit 3GPP broadcast identifier triggers the mobile device to perform an authentication with the identity provider via the second visited radio access network.

7. The method of claim 1 , wherein detecting, by the mobile device, at least one multi-bit 3GPP broadcast identifier of the plurality of multi-bit 3GPP broadcast identifiers being broadcast by a visited radio access network triggers the mobile device to perform an authentication with the identity provider.

8. The method of claim 1 , wherein the at least one multi-bit roaming policy is represented using a Roaming Consortium Organizational Identifier (RCOI).

9. The method of claim 1 , wherein the plurality of multi-bit 3GPP broadcast identifiers are one of:

a plurality of closed subscriber group (CSG) identifiers;

a plurality of network identifiers (NIDs);

a plurality of closed access group (CAG) identifiers; or

a plurality of group identifier for network selection (GIN) codes.

10. A plurality of non-transitory computer readable storage media encoded with instructions that, when executed by a plurality of processors, causes the plurality of processors to perform operations, comprising:

encoding at least one multi-bit roaming policy for an identity provider and a plurality of bit-wise combinatorial permutations of the at least one multi-bit roaming policy within each of a plurality of multi-bit Third Generational Partnership Project (3GPP) broadcast identifiers, wherein the at least one multi-bit roaming policy includes bit-wise roaming policy information for the identity provider; and

provisioning the plurality of multi-bit 3GPP broadcast identifiers for a mobile device associated with the identity provider, wherein the plurality of multi-bit 3GPP broadcast identifiers indicate that the mobile device is to connect to a visited radio access network associated with a local Internet Protocol (IP) access service or a home routed access service.

11. The media of claim 10 , wherein the identity provider supports both the local IP access service and the home routed access service.

12. The media of claim 11 , wherein the plurality of multi-bit 3GPP broadcast identifiers are configured for the mobile device in a prioritized order that identifies a preference of the identity provider for the mobile device to connect to a visited radio access network based on the prioritized order.

13. The media of claim 12 , wherein the prioritized order identifies a preference of the identity provider for the mobile device to connect to an access network that is configured to provide one of the local IP access service or the home routed access service.

14. The media of claim 13 , wherein detecting, by the mobile device, a first multi-bit 3GPP broadcast identifier of the plurality of multi-bit 3GPP broadcast identifiers being broadcast by a first visited radio access network and a second multi-bit 3GPP broadcast identifier of the plurality of multi-bit 3GPP broadcast identifiers being broadcast by a second visited radio access network triggers the mobile device to determine, a highest priority multi-bit 3GPP broadcast identifier of the first multi-bit 3GPP broadcast identifier and the second multi-bit 3GPP broadcast identifier based on the prioritized order of the plurality of multi-bit 3GPP broadcast identifiers.

15. The media of claim 14 , wherein determining the highest priority multi-bit 3GPP broadcast identifier being the first multi-bit 3GPP broadcast identifier triggers the mobile device to perform an authentication with the identity provider via the first visited radio access network or determining the highest priority multi-bit 3GPP broadcast identifier being the second multi-bit 3GPP broadcast identifier triggers the mobile device to perform an authentication with the identity provider via the second visited radio access network.

16. A system comprising:

at least one memory element for storing data; and

at least one processor for executing instructions associated with the data, wherein executing the instructions causes the system to perform operations, comprising:

encoding at least one multi-bit roaming policy for an identity provider and a plurality of bit-wise combinatorial permutations of the at least one multi-bit roaming policy within each of a plurality of multi-bit Third Generational Partnership Project (3GPP) broadcast identifiers, wherein the at least one multi-bit roaming policy includes bit-wise roaming policy information for the identity provider; and

provisioning the plurality of multi-bit 3GPP broadcast identifiers for a mobile device associated with the identity provider, wherein the plurality of multi-bit 3GPP broadcast identifiers indicate that the mobile device is to connect to a visited radio access network associated with a local Internet Protocol (IP) access service or a home routed access service.

17. The system of claim 16 , wherein the identity provider supports both the local IP access service and the home routed access service.

18. The system of claim 17 , wherein the plurality of multi-bit 3GPP broadcast identifiers are configured for the mobile device in a prioritized order that identifies a preference of the identity provider for the mobile device to connect to a visited radio access network based on the prioritized order.

19. The system of claim 18 , wherein the prioritized order identifies a preference of the identity provider for the mobile device to connect to an access network that is configured to provide one of the local IP access service or the home routed access service.

20. The system of claim 18 , wherein the plurality of multi-bit 3GPP broadcast identifiers are one of:

a plurality of closed subscriber group (CSG) identifiers;

a plurality of network identifiers (NIDs);

a plurality of closed access group (CAG) identifiers; or

a plurality of group identifier for network selection (GIN) codes.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 28, 2022
From: GRAYSON, MARK; STAMMERS, TIMOTHY PETER; O'CONNOR, DESMOND JOSEPH; BRINCKMAN, BART A.
To: CISCO TECHNOLOGY, INC.
Reel/Frame 061242/0805 →
Continuity (3)
Continuation In Part 17315581 · May 10, 2021
Provisional Application 63073642 · Sep 2, 2020
Related Publication 20230021642A1 · Jan 26, 2023
References Cited (50)
US 8638749B2 · Cherian · 2014 [cited by examiner]
US 8924535B2 · Horn et al. · 2014 [cited by applicant]
US 10813042B1 · Gundavelli et al. · 2020 [cited by applicant]
US 11337147B2 · Gundavelli et al. · 2022 [cited by applicant]
US 20120084834A1 · Brown · 2012 [cited by examiner]
US 20150148033A1 · Kim et al. · 2015 [cited by applicant]
US 20150312824A1 · Thalanany · 2015 [cited by examiner]
US 20160183169A1 · Horn et al. · 2016 [cited by applicant]
US 20170201938A1 · Kim et al. · 2017 [cited by applicant]
US 20170295540A1 · Gupta · 2017 [cited by applicant]
US 20170339634A1 · Fine · 2017 [cited by examiner]
US 20190191470A1 · Joseph et al. · 2019 [cited by applicant]
US 20200120481A1 · Grayson et al. · 2020 [cited by applicant]
US 20200163013A1 · Grayson et al. · 2020 [cited by applicant]
US 20200228967A1 · Chan et al. · 2020 [cited by applicant]
US 20220060893A1 · Gundavelli et al. · 2022 [cited by applicant]
US 20220070652A1 · Grayson et al. · 2022 [cited by applicant]
US 20230021642A1 · Grayson · 2023 [cited by examiner]
WO 2021035499A1 · 2021 [cited by applicant]
Telecompedia, “SIB1 in LTE”, https://telecompedia.net/sib1-in-lte/, downloaded Feb. 4, 2021, 8 pages. [cited by applicant]
Techplayon, “PLMN Selection in LTE (Idle Mode Action)”, http://www.techplayon.com/plmn-selection-in-lte-idle-mode-action/, Apr. 25, 2019, 8 pages. [cited by applicant]
MulteFire Alliance, “MulteFire Release 1.0 Technical Paper”, Jan. 2017, 25 pages. [cited by applicant]
Wikipedia, “List of DNS record types”, Feb. 23, 2021, https://en.wikipedia.org/wiki/List_of_DNS_record_types, 13 pages. [cited by applicant]
Cisco, “Hotspot 2.0”, https://www.cisco.com/c/en/US/td/docs/wireless/controller/9800/17-2/config-guide/b_wl_17_2_cg/hotspot_2_0.pdf, downloaded May 6, 2021, 14 pages. [cited by applicant]
Cisco, “DNS Resource Records”, https://www.cisco.com/c/en/us/support/docs/ip/domain-name-system-dns/12684-dns-resource.html, Sep. 11, 2018, 7 pages. [cited by applicant]
3GPP, “5G for Industry 4.0”, https://www.3gpp.org/news-events/2122-tsn_v_lan, May 13, 2020, 4 pages. [cited by applicant]
CBS Alliance, “CBRS Alliance Identifier Guidelines for Shared HNI”, CBRSA-TR-0100, V1.0.0, Nov. 27, 2018, 18 pages. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related Interfaces … [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16)”, 3GPP TS 38.331 V16.3.1, Jan. 2021, 932 pages. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhanced support of non-public networks (Release 17)”, 3GPP TR 23.700-07 V1.2.0, Nov. 2020, 247 pages. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17)”, 3GPP TS 23.501 V17.0.0, Mar. 2021, 489 pages. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17)”, 3GPP TS 23.003 V17.0.0, Dec. 2020, 142 pages. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the 5G system; Stage 1 (Release 18)”, 3GPP TS 22.261 V18.1.1, Jan. 2021, 85 pages. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service accessibility (Release 17)”, 3GPP TS 22.011 V17.3.0, Dec. 2020, 34 pages. [cited by applicant]
Hughes Systique, “OpenRoaming—A Global Wi-Fi Roaming Enabler,” https://hsc.com/Resources/Blog/OpenRoaming-A-Global-Wi-Fi-Roaming-Enabler, Jul. 13, 2020, 8 pages. [cited by applicant]
Jerome Henry, “Boost Your WLAN Efficiency with Device-Specific Tuning,” Cisco, BRKEWN-2178, Apr. 21, 2020, 86 pages. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Characteristics of the Universal Subscriber Identity Module (USIM) application (Release 17),” 3GPP TS 31.102 V17.1.0, … [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 (Release 17),” 3GPP TS 24.301 V17.2.0, Mar.… [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode (Release 17),” 3GPP TS 23.122 V17.2.0, … [cited by applicant]
CBRS Alliance, “CBRS Network Services Stage 2 and 3 Specification”, V3.0.0, Feb. 18, 2020, XP055867207, 55 pages. [cited by applicant]
Motorola Mobility, “Preferred Realm/OUI in ANDSF Policies”, 3GPP Draft, S2-120792 ANDSF REALM, 3rd Generation Partnership Project (3GPP), vol. SA WG2, XP050576656, Jan. 31, 2012, 6 pages. [cited by applicant]
AT&T et al., “Use of OPI within ANDSF”, 3GPP Draft, S2-141831_OPI_CR, vol. SA WG2, XP050805182, May 19, 2014, 4 pages. [cited by applicant]
International Search Report and Written Opinion in counterpart International Application No. PCT/US2021/047715, mailed Dec. 21, 2021, 18 pages. [cited by applicant]
“Local Breakout,” Science Direct, https://www.sciencedirect.com/topics/engineering/local-breakout, retrieved May 27, 2022, 23 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.501 V17.5.0, Jun. 2022, 568 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17),” 3GPP TS 23.003 V17.6.0, Jun. 2022, 147 pages. [cited by applicant]
“Draft RRC CR: Non-Public Network enhancements,” 3GPP TSG-RAN WG2 Meeting #116 Electronic, Nokia, Nokia Shanghai Bell, R2-2111399, R2-2110365, CR38.331, Version: 16.6.0 Nov. 1-12, 2021, 22 pages. [cited by applicant]
“Draft Stage 2 CR: Non-Public Network enhancements,” 3GPP TSG-RAN WG2 Meeting #116 Electronic, Nokia, Nokia Shanghai Bell, R2-2111398, R2-2110364, CR38.300, Version: 16.7.0, Nov. 1-12, 2021, 13 pages. [cited by applicant]
“Adding a priority bit into the Access Technology Identifier,” 3GPP TSG-CT WG6 Meeting #89, C6-180215, CR31.102, Version 15.0.0, May 21-25, 2018, 4 pages. [cited by applicant]
Non-Final Office Action for U.S. Appl. No. 17/315,581, filed Oct. 5, 2022, 13 pages. [cited by applicant]
Cited By (1)
US 12,621,647