IP Library Granted Patent US 12,445,936
Granted Patent B2
US 12,445,936 · App. 18/013,066 · Granted Oct 14, 2025

Methods and devices for handling virtual domains

Inventors: Xavier De Foy (Kirkland, CA); Scott Hergenhan (Collegeville, PA); Michel Roy (Candiac, CA); Debashish Purkayastha (Collegeville, PA); Robert Gazda (Spring City, PA)
Assignee: InterDigital Patent Holdings, Inc.
H04W40/36
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,445,936
App. No.
18/013,066
Granted
Oct 14, 2025
Kind
B2
Abstract

A wireless transmit/receive unit, WTRU, connects to a first AP, receives domain identifiers, requests corresponding descriptors and receives a list of descriptors. An application on the WTRU requests a list of domains and attributes corresponding to service names or service sets, which is returned by the WTRU. The application selects one or more domains for communications, the WTRU selects corresponding network resources and the application connects to local services. After moving to a new location, the WTRU connects to a second AP and receives a second set of domain identifiers, selects the one matching the request from the application and provides these to the application that, with the aid of the WTRU connects to local services.

Claims (56)

1. A method, in a wireless transmit/receive unit (WTRU), the method comprising:

receiving provisioning domain identifiers corresponding to provisioning domains and first provisioning domain descriptors, each first provisioning domain descriptor comprising a service name or a service set;

receiving, from an application running on the WTRU, at least one requested service name or service set;

providing to the application provisioning domain identifiers matching the at least one requested service name or service set;

selecting first network resources based on a first provisioning domain selected by the application;

receiving, after WTRU relocation, second provisioning domain descriptors, each second provisioning domain descriptor comprising a service name or a service set;

providing, to the application, second provisioning domain descriptors matching the at least one requested service name or service set; and

selecting second network resources based on a second provisioning domain selected by the application.

2. The method of claim 1 , further comprising:

requesting the first provisioning domain descriptors corresponding to the first provisioning domain identifiers.

3. The method of claim 1 , wherein the first provisioning domain descriptors and the second provisioning domain descriptors further comprise at least one of an instance identifier and an authentication or authorization token.

4. The method of claim 1 , further comprising:

receiving from the application a first request for a first list of provisioning domains and provisioning domain attributes matching at least one service name or a service set in the request;

providing to the application, the first list of provisioning domains and provisioning domain attributes matching at least one service name or a service set in the first request.

5. The method of claim 4 , further comprising verifying, by the application, authenticity of at least one received service name or service set and selecting, by the application, at least one provisioning domain with which to communicate based on a verified service name or a service set.

6. The method of claim 5 , further comprising:

receiving from the application a notification of the at least one selected provisioning domain.

7. The method of claim 1 , further comprising:

connecting to a second network element different from a first network element that provided the first provisioning domain descriptors to the WTRU;

wherein the second provisioning domain descriptors are received after connecting to the second network element.

8. The method of claim 1 , further comprising:

connecting, by the application using the first network resources, to a first service instance corresponding to the requested service name or service set; and

connecting, by the application using the second network resources, to a second service instance corresponding to the requested service name or service set.

9. The method of claim 8 , wherein the first service instance is the same as the second service instance.

10. The method of claim 8 , wherein each of the first provisioning domain descriptors and the second provisioning domain descriptors further comprises an instance identifier, and wherein the method further comprises determining, based on the service name or the service set and the corresponding instance identifier whether to connect, using the second network resources, to a service instance with the first service identifier or to a service instance with a new instance identifier.

11. A wireless transmit/receive unit (WTRU) comprising:

memory storing processor-executable program instructions; and

at least one hardware processor configured to execute the program instructions to:

receive provisioning domain identifiers corresponding to provisioning domains and first provisioning domain descriptors, each first provisioning domain descriptor comprising a service name or a service set;

receive, from an application running on the WTRU, at least one requested service name or service set;

provide to the application provisioning domain identifiers matching the at least one requested service name or service set;

select first network resources based on a first provisioning domain selected by the application;

receive, after WTRU relocation, second provisioning domain descriptors, each second provisioning domain descriptor comprising a service name or a service set;

provide to the application, second provisioning domain descriptors matching the at least one requested service name or service set; and

select second network resources based on a second provisioning domain selected by the application.

12. The WTRU of claim 11 , wherein the at least one hardware processor is further configured to execute the program instructions to request the first provisioning domain descriptors corresponding to the first provisioning domain identifiers.

13. The WTRU of claim 11 , wherein the first provisioning domain descriptors and the second provisioning domain descriptors further comprise at least one of an instance identifier and an authentication or authorization token.

14. The WTRU of claim 11 , wherein the at least one hardware processor is further configured to execute the program instructions to:

receive from the application running on the WTRU, a first request for a first list of provisioning domains and provisioning domain attributes matching at least one service name or a service set in the request; and

provide to the application, the first list of provisioning domains and provisioning domain attributes matching at least one service name or a service set in the first request.

15. The WTRU of claim 14 , wherein the at least one hardware processor is further configured to execute the application to verify authenticity of at least one received service name or service set and select at least one verified provisioning domain with which to communicate based on a verified service name or a service set.

16. The wireless transmit/receive unit of claim 11 , wherein the at least one hardware processor is further configured to execute the program instructions to connect to a second network element different from a first network element that provided the first provisioning domain descriptors to the WTRU;

wherein the second provisioning domain descriptors are received after connecting to the second network element.

17. The WTRU of claim 11 , further comprising:

connecting, by the application using the first network resources, to a first service instance corresponding to the requested service name or service set; and

connecting, by the application using the second network resources, to a second service instance corresponding to the requested service name or service set.

18. The WTRU of claim 17 , wherein the first service instance is the same as the second service instance.

19. The WTRU of claim 17 , wherein each of the first provisioning domain descriptors and the second provisioning domain descriptors further comprises an instance identifier, and wherein the method further comprises determining, based on the service name or the service set and the corresponding instance identifier whether to connect, using the second network resources, to a service instance with the first service identifier or to a service instance with a new instance identifier.

20. A non-transitory computer-readable storage medium storing instructions that, when executed, cause at least one hardware processor of a wireless transmit/receive unit, WTRU, to:

receive provisioning domain identifiers corresponding to provisioning domains and first provisioning domain descriptors, each first provisioning domain descriptor comprising a service name or a service set;

receive, from an application running on the WTRU, at least one requested service name or service set;

provide to the application provisioning domain identifiers matching the at least one requested service name or service set;

select first network resources based on a first provisioning domain selected by the application;

receive, after WTRU relocation, second provisioning domain descriptors, each second provisioning domain descriptor comprising a service name or a service set;

provide to the application, second provisioning domain descriptors matching the at least one requested service name or service set; and

select second network resources based on a second provisioning domain selected by the application.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 27, 2022
From: DE FOY, XAVIER; ROY, MICHEL; PURKAYASTHA, DEBASHISH
To: INTERDIGITAL PATENT HOLDINGS, INC.
Reel/Frame 062210/0135 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 27, 2022
From: HERGENHAN, SCOTT
To: INTERDIGITAL PATENT HOLDINGS, INC.
Reel/Frame 062210/0183 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 27, 2022
From: GAZDA, ROBERT
To: INTERDIGITAL PATENT HOLDINGS, INC.
Reel/Frame 062210/0222 →
Continuity (2)
Provisional Application 63046823 · Jul 1, 2020
Related Publication 20230308985A1 · Sep 28, 2023
References Cited (16)
US 20110078229A1 · Qiu · 2011 [cited by examiner]
US 20140086177A1 · Adjakple · 2014 [cited by examiner]
US 20190223093A1 · Watfa et al. · 2019 [cited by applicant]
US 20230379985A1 · De Foy · 2023 [cited by examiner]
CN 102365847A · 2012 [cited by applicant]
CN 107646191A · 2018 [cited by applicant]
IN 201937010914A · 2019 [cited by applicant]
Anipko et al., “Multiple Provisioning Domain Architecture”, Internet Engineering Task Force (IETF), Request for Comments: #7556, Category : Informational, ISSN: 2070-1721, Jun. 2015, 25 pages. [cited by applicant]
Anonymous, “Technical Specification Group Services and System Aspects; Study on enhancement of support for Edge Computing in 5G Core network (5GC)”, 3rd Generation Partnership Project (3GPP), Release 17, Document: 3GPP … [cited by applicant]
Trammell et al., “An Abstract Application Layer Interface to Transport Services—draft-ietf-taps-interface-05”, Internet Engineering Task Force (IETF), Taps Working Group, Internet-Draft, Intended Status : Standards Trac… [cited by applicant]
Pfister et al., “Discovering Provisioning Domain Names and Data—Draft ietf intrea provisioning domains 11”, Internet Engineering Task Force (IETF), Network Working Group, Internet Draft, Intended Status : Standards Trac… [cited by applicant]
Shao et al., “Multi-PvD Development Environment”, Open Source : GitHub—IPv6-mPvD/pvd-dev, Jul. 16, 2018, URL: https://github.com/IPv6-mPvD/pvd-dev , 16 pages. [cited by applicant]
Anonymous, “Multi-access Edge Computing (MEC); Device application interface”, Multi-access Edge Computing (MEC) ETSI Industry Specification Group (ISG), Document: ETSI GS MEC 016 V2.1.1, Apr. 2019, 22 pages. [cited by applicant]
Anonymous, “Technical Specification Group Services and System Aspects; Study on enhancement of support for Edge Computing in 5G Core network (5GC)”, 3rd Generation Partnership Project (3GPP), Release 17, Document: 3GPP … [cited by applicant]
Cheshire et al., “DNS-Based Service Discovery”, Internet Engineering Task Force (IETF), Request for Comments: 6763, Category: Standards Track, ISSN: 2070-1721, Feb. 2013, 49 pages. [cited by applicant]
Nortel, “VCC for IMS Emergency Alternative 1 Editors Notes”, 3GPP TSG SA WG2 Meeting #69, Td S2-087798, Nov. 17-21, 2008, Miami, Florida, USA, 15 pages. [cited by applicant]