IP Library Granted Patent US 12,507,051
Granted Patent B2
US 12,507,051 · App. 18/076,126 · Granted Dec 23, 2025

Service-based discovery in networks

Inventors: Dale Seed (Allentown, PA); Michael Starsinic (Newtown, PA); Guang Lu (Thornhill, CA); Kamel M. Shaheen (Camas, WA); Dorothy Gellert (Mountain View, CA); Zongrui Ding (Portland, OR); Lijun Dong (San Diego, CA); Chonggang Wang (Princeton, NJ)
Assignee: DRNC Holdings, Inc.
H04W4/70H04L67/51H04W4/38H04W72/51
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,507,051
App. No.
18/076,126
Granted
Dec 23, 2025
Kind
B2
Abstract

Systems, methods, and instrumentalities may implement service-based discovery in a network, such as a 3GPP or 3GPP2 network. A Discovery Server may be used to query and find services offered by the network or by entities that interface with the network. Situational context information or policy information, or both, may be communicated to the discovery server so that the Discovery Server can provide context-aware and policy-based discovery services. The Discovery Server may be used to control which of the entities that interface with the network can discover one another. The Discovery Server may support queries based on, for example, the type of MTC entity, the type of services hosted on the entity, the availability times of the entity, types of protocols supported, levels of Quality of Service (QoS) supported, and MTC-IWF services.

Claims (50)

1 . A method implemented by a server, the method comprising:

receiving a registration request, wherein the registration request is related to creating a discovery record;

sending a response to the registration request indicating that the discovery record was created;

receiving an update request related to the discovery record;

sending a response to the update request indicating that the discovery record was updated;

receiving a services request from a wireless receive transmit unit (WTRU), wherein the services request includes service provider information, wherein the discovery record is associated with the services request for the WTRU;

sending a request for context information about the WTRU;

receiving context information about the WTRU;

matching information included in the services request with information in one or more discovery records, wherein the information that matches is the service provider information; and

sending a response to the services request based on the information that matches and the context information about the WTRU.

2 . The method of claim 1 , wherein the registration request or update request further includes security credentials, a list of supported service types, or a network address.

3 . The method of claim 1 , wherein the context information about the WTRU includes location information about the WTRU.

4 . The method of claim 1 , further comprising receiving a request to delete the record of the server, and sending a response to the request to delete indicating that the discovery record has been deleted.

5 . The method of claim 1 , wherein the discovery record includes information that identifies a service that is offered by a services server, contact information for the services server, schedule information that indicates when the service is available, or a service provider identifier.

6 . A server, the server comprising:

a processor operatively connected to a transceiver, the processor and transceiver configured to receive a registration request, wherein the registration request is related to creating a discovery record;

the processor and transceiver configured to send a response to the registration request indicating that the discovery record was created;

the processor and transceiver configured to receive an update request related to the discovery record;

the processor and transceiver configured to send a response to the update request indicating that the discovery record was updated;

the processor and transceiver configured to receive a services request from a wireless receive transmit unit (WTRU), wherein the services request includes service provider information;

the processor and transceiver configured to send a request for context information about the WTRU;

the processor and transceiver configured to receive context information about the WTRU;

the processor and transceiver configured to match information included in the services request with information in one or more discovery records, wherein the information that matches is the service provider information; and

the processor and transceiver configured to send a response to the services request based on the information that matches and the context information about the WTRU.

7 . The server of claim 6 , wherein the registration request or update request further includes security credentials, a list of supported service types, or a network address.

8 . The server of claim 6 , wherein the context information about the WTRU includes location information about the WTRU.

9 . The server of claim 6 , wherein the processor and transceiver are configured to receive a request to delete the discovery record, and sending a response to the request to delete indicating that the discovery record has been deleted.

10 . The server of claim 6 , wherein the discovery record includes information that identifies a service that is offered by a services server, contact information for the services server, schedule information that indicates when the service is available, or a service provider identifier.

11 . A method implemented by a wireless transmit receive unit (WTRU), the method comprising:

sending a services request to a server,

wherein the services request includes service provider information,

wherein the sending of the services request prompts the server to determine the context information for the WTRU,

wherein the sending of the services request further prompts the server to match information included in the services request,

wherein the information that matches is the service provider information, and

wherein the services request further prompts the server to determine a response message to the services request based on the information that matches and the context information for the WTRU; and

receiving the response message to the services request.

12 . The method of claim 11 , wherein the response includes one or more network addresses for a services server.

13 . The method of claim 11 , wherein the context information for the WTRU is location information of the WTRU.

14 . The method of claim 11 , wherein the matched information was previously created at the server by a registration request and subsequently updated at the server.

15 . A wireless transmit receive unit (WTRU), the WTRU comprising:

a processor operatively connected to a transceiver, the processor and transceiver configured to send a services request to a server,

wherein the services request includes service provider information,

wherein the sending of the services request prompts the server to determine the context information for the WTRU,

wherein the sending of the services request further prompts the server to match information included in the services request,

wherein the information that matches is the service provider information, and

wherein the services request further prompts the server to determine a response message to the services request based on the information that matches and the context information for the WTRU; and

the processor and transceiver configured to receive the response message to the services request.

16 . The WTRU of claim 15 , wherein the response includes one or more network addresses for a services server.

17 . The WTRU of claim 15 , wherein the context information for the WTRU is location information of the WTRU.

18 . The WTRU of claim 15 , wherein the matched information was previously created at the server by a registration request and subsequently updated at the server.

Continuity (5)
Continuation 16258274 · Jan 25, 2019
Continuation 15481436 · Apr 6, 2017
Continuation 14410666
Provisional Application 61666256 · Jun 29, 2012
Related Publication 20230179976A1 · Jun 8, 2023
References Cited (51)
US 8650619B2 · Sundaram et al. · 2014 [cited by applicant]
US 20010014911A1 · Doi · 2001 [cited by examiner]
US 20030143988A1 · Jamadagni · 2003 [cited by examiner]
US 20040156372A1 · Hussa · 2004 [cited by examiner]
US 20040242329A1 · Blackburn · 2004 [cited by examiner]
US 20050027871A1 · Bradley et al. · 2005 [cited by applicant]
US 20070153812A1 · Kemp · 2007 [cited by examiner]
US 20070226774A1 · Pardo-Blazquez · 2007 [cited by examiner]
US 20080065656A1 · Theeten · 2008 [cited by examiner]
US 20080253322A1 · So · 2008 [cited by examiner]
US 20090080387A1 · Dell'Uomo · 2009 [cited by examiner]
US 20100048161A1 · He · 2010 [cited by examiner]
US 20100285816A1 · Vos et al. · 2010 [cited by applicant]
US 20110280184A1 · Diachina et al. · 2011 [cited by applicant]
US 20110294474A1 · Barany et al. · 2011 [cited by applicant]
US 20120004003A1 · Shaheen et al. · 2012 [cited by applicant]
US 20120157050A1 · Kang et al. · 2012 [cited by applicant]
US 20120203905A1 · Lee et al. · 2012 [cited by applicant]
US 20120207094A1 · Liao · 2012 [cited by applicant]
US 20120220326A1 · Li et al. · 2012 [cited by applicant]
US 20130003576A1 · Segura et al. · 2013 [cited by applicant]
US 20130155905A1 · Sampath · 2013 [cited by examiner]
US 20130188515A1 · Pinheiro et al. · 2013 [cited by applicant]
US 20130226998A1 · Heo et al. · 2013 [cited by applicant]
US 20130288668A1 · Pragada et al. · 2013 [cited by applicant]
US 20140059594A1 · Stein · 2014 [cited by examiner]
US 20140075488A1 · Christudass · 2014 [cited by examiner]
US 20140089478A1 · Seed et al. · 2014 [cited by applicant]
US 20140149794A1 · Shetty · 2014 [cited by examiner]
US 20140206348A1 · Johnsson et al. · 2014 [cited by applicant]
US 20140335791A1 · Kim et al. · 2014 [cited by applicant]
US 20150017917A1 · Guo et al. · 2015 [cited by applicant]
WO 2011054299 · 2011 [cited by applicant]
WO 2011112683 · 2011 [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 22.368 V11.5.0, “Technical Specification Group Services and System Aspects, Service Requirements for Machine-Type-Communications (MTC), Stage 1 (Release 11),” Jun. 2012, pp.… [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.008 V11.4.0, “Technical Specification Group Core Network and Terminals, Organization of Subscriber Data (Release 11),” Jun. 2012, pp. 1-109. [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.141 V10.0.0, “Technical Specification Group Services and System Aspects, Presence Service, Architecture and Functional Description (Release 10),” Mar. 2011, pp. 1-36. [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.402 V11.3.0, “Technical Specification Group Services and System Aspects, Architecture Enhancements for Non-3GPP Accesses (Release 11),” Jun. 2012, pp. 1-252. [cited by applicant]
3rd Generation Partnership Project (3GPP), TS 23.682 V11.1.0, “Technical Specification Group Services and System Aspects, Architecture Enhancements to Facilitate Communications with Packet Data Networks and Applications… [cited by applicant]
3 [cited by applicant]
European Telecommunications Standards Institute (ETSI), ETSI/M2M(11)0109, “M2M SCL Discovery Procedures,” InterDigital Communications, M2M#14bis Meeting, Mar. 28-Apr. 1, 2011, 8 pages. [cited by applicant]
European Telecommunications Standards Institute (ETSI), TS 102 690 V1.1.1, “Machine-to-Machine Communications (M2M), Functional Architecture,” Oct. 2011, pp. 1-280. [cited by applicant]
European Telecommunications Standards Institute (ETSI), TS 102 690 V0.9.7, “Machine-to-Machine Communications (M2M), Functional Architecture,” Dec. 2010, pp. 1-191. [cited by applicant]
Lif, “Mobile Location Protocol,” Location Inter-Operability Forum (LIF), TS 101 V2.0.0, Nov. 20, 2001, 70 pages. [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 11),” 3GPP TS … [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; Organization of subscriber data (Release 11),” 3GPP TS 23.008 V11.8.1 (Jun. 2013). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Core Network and Terminals; Organization of subscriber data (Release 12),” 3GPP TS 23.008 V12. [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Presence Service; Architecture and functional description (Release 11),” 3GPP TS 23.141 V11.0.0 (Sep. 2012). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Architecture enhancements for non-3GPP accesses (Release 11),” 3GPP TS 23.402 V11.7.0 (Jun. 2013). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Architecture enhancements for non-3GPP accesses (Release 12),” 3GPP TS 23.402 V12.1.0 (Jun. 2013). [cited by applicant]
Third Generation Partnership Project, “Technical Specification Group Services and System Aspects; Service requirements for Machine-Type Communications (MTC); Stage 1 (Release 12),” 3GPP TS 22.368 V12.2.0 (Mar. 2013). [cited by applicant]