Methods, systems, and computer readable media for resolution of inter-network domain names

Description

TECHNICAL FIELD

The subject matter described herein relates to communications between telecommunications networks. More particularly, the subject matter described herein relates to methods, systems, and computer readable media for resolution of inter-network domain names.

BACKGROUND

In fifth generation (5G) communications networks, the network node that provides service is referred to as a producer network function (NF). A network node that consumes services is referred to as a consumer NF. A network function can be both a producer NF and a consumer NF depending on whether it is consuming or providing service.

A given producer NF may have many service endpoints, where a service endpoint is the point of contact for one or more NF instances hosted by the producer NF. The service endpoint is identified by a combination of Internet protocol (IP) address and port number or a fully qualified domain name that resolves to an IP address and port number on a network node that hosts a producer NF. An NF instance is an instance of a producer NF that provides a service. A given producer NF may include more than one NF instance. It should also be noted that multiple NF instances can share the same service endpoint.

Producer NFs register with a network function repository function (NRF). The NRF maintains service profiles of available NF instances identifying the services supported by each NF instance. Consumer NFs can subscribe to receive information about producer NF instances that have registered with the NRF. In addition to consumer NFs, another type of network node that can subscribe to receive information about NF service instances is a service communications proxy (SCP). The SCP subscribes with the NRF and obtains reachability and service profile information regarding producer NF service instances. Consumer NFs connect to the service communications proxy, and the service communications proxy load balances traffic among producer NF service instances that provide the required service or directly routes the traffic to the destination producer NF instance.

The 3rd Generation Partnership Project (3GPP) mandates interPlmnFqdn to be used for inter public land mobile network (PLMN) routing (roaming scenarios) in 5G networks, which means an IP and interPlmnFqdn mapping is provided at a security edge protection proxy (SEPP) of the home network locally via DNS or other means, so that the home SEPP can route the 5G SBI request to the producer NF.

In light of these and other difficulties, there exists a need for methods, systems, and computer readable media for resolution of inter-network domain names.

SUMMARY

A method for resolution of inter-network domain names between telecommunications networks includes storing, at a security edge protection proxy (SEPP) of a home network, a mapping between a domain name and a network address of a producer network function of the home network. The method includes receiving, at the SEPP of the home network, a request message from a consumer network function of a visitor network. The method includes resolving, at the SEPP of the home network, a request message domain name of the request message using the mapping between the domain name and the network address of the producer network function of the home network.

According to another aspect of the subject matter described herein, the home network lacks a dedicated domain name service, and resolving the request message domain name includes resolving the request message domain name without accessing a domain name server.

According to another aspect of the subject matter described herein, storing the mapping between the domain name and the network address of the producer network function includes storing the mapping while acting as a proxy between the home network and the visitor network.

According to another aspect of the subject matter described herein, the acting as a proxy between the home network and the visitor network comprises receiving a discovery request from the consumer network function, forwarding the discovery request to a network function repository function (NRF), receiving a response message from the NRF, and forwarding the response message to the consumer network function.

According to another aspect of the subject matter described herein, storing the mapping between the domain name and the network address of the producer network function includes storing other topology information from a network function repository function (NRF), and resolving the request message domain name of the request message includes using the other topology information.

According to another aspect of the subject matter described herein, storing other topology information from the NRF includes extracting the other topology information from a subscription/notification request.

According to another aspect of the subject matter described herein, storing other topology information from the NRF includes extracting the other topology information from a network function management query.

According to another aspect of the subject matter described herein, the method includes forwarding the request message to the producer network function using the network address, receiving a response message from the producer network function, and forwarding the response message to the consumer network function.

According to another aspect of the subject matter described herein, the home network is a 5G network and the request message is a 5G service based interface (SBI) message.

According to another aspect of the subject matter described herein, a system for resolution of inter-network domain names between telecommunications networks includes at least one processor and a memory. The system further includes security edge protection proxy (SEPP) of a home network, the SEPP implemented by the at least one processor and configured for: storing a mapping between a domain name and a network address of a producer network function of the home network; receiving a request message from a consumer network function of a visitor network; and resolving a request message domain name of the request message using the mapping between the domain name and the network address of the producer network function of the home network.

According to another aspect of the subject matter described herein, storing the mapping between the domain name and the network address of the producer network function includes storing other topology information from a network function repository function (NRF), and resolving the request message domain name of the request message includes using the other topology information.

According to another aspect of the subject matter described herein, the SEPP is configured for forwarding the request message to the producer network function using the network address, receiving a response message from the producer network function, and forwarding the response message to the consumer network function.

According to another aspect of the subject matter described herein, the home network is a 5G network and the request message is a 5G service based interface (SBI) message.

According to another aspect of the subject matter described herein, a non-transitory computer readable medium having stored thereon executable instructions that when executed by a processor of a computer control the computer to perform steps is provided. The steps include storing, at a security edge protection proxy (SEPP) of a home network, a mapping between a domain name and a network address of a producer network function of the home network; receiving, at the SEPP of the home network, a request message from a consumer network function of a visitor network; and resolving, at the SEPP of the home network, a request message domain name of the request message using the mapping between the domain name and the network address of the producer network function of the home network.

The subject matter described herein can be implemented in software in combination with hardware and/or firmware. For example, the subject matter described herein can be implemented in software executed by a processor. In one example implementation, the subject matter described herein may be implemented using a computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer control the computer to perform steps.

Example computer readable media suitable for implementing the subject matter described herein include non-transitory devices, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. In addition, a computer readable medium that implements the subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.

BRIEF DESCRIPTION OF THE DRAWINGS

The subject matter described herein will now be explained with reference to the accompanying drawings of which:

FIG. 1 is a block diagram illustrating an example 5G system network architecture;

FIG. 2 is a message flow diagram illustrating an example scenario where a routing failure occurs in a home network for a discovery request from a visitor network;

FIG. 3 is a message flow diagram illustrating an example scenario where the home SEPP is configured for resolution of inter-network domain names between telecommunications networks;

FIG. 4 is a flow diagram of an example method for resolution of inter-network domain names between telecommunications networks.

DETAILED DESCRIPTION

The subject matter described herein relates to methods, systems, and computer readable media for resolution of inter-network domain names between telecommunications networks.

In 5G telecommunications networks, the network node that provides service is referred to as a producer network function (NF). A network node that consumes services is referred to as a consumer NF. A network function can be both a producer NF and a consumer NF depending on whether it is consuming or providing service. An NF instance is an instance of a producer NF that provides a service. A given producer NF may include more than one NF instance.

The 3^rdGeneration Partnership Project (3GPP) mandates interPlmnFqdn to be used for inter public land mobile network (PLMN) routing (roaming scenarios) in 5G networks, which means an IP and interPlmnFqdn mapping is provided at a security edge protection proxy (SEPP) of the home network locally via DNS or other means, so that the home SEPP can route the 5G SBI request to the producer NF. In contrast, for intra-PLMN routing, the 5G network can be created as internet protocol (IP) only without any local configuration via domain name service (DNS) or other means (e.g., network function repository function (NRF) provides IP for the producer NFs).

An operator may choose to not use DNS in their network for any of various reasons, for example, to mitigate DNS related security attacks, simplify operations by configuring FQDN/IP mapping only in the NRF, frequently changing 5G topology making DNS not feasible or other reasons. Similarly, provisioning the FQDN IP mapping locally can be cumbersome from an operational standpoint. This specification describes methods and systems where the home security edge protection proxy (SEPP) can route 5G service based interface (SBI) requests to producer NFs in absence of local configuration of interPlmnFqdn to IP mapping.

FIG. 1 is a block diagram illustrating an example 5G system network architecture. The architecture in FIG. 1 includes NRF 100 and SCP 101, which may be located in the same home public land mobile network (HPLMN). NRF 100 may maintain profiles of available producer NF service instances and their supported services and allow consumer NFs or SCPs to subscribe to and be notified of the registration of new/updated producer NF service instances.

SCP 101 may also support service discovery and selection of producer NF instances. SCP 101 may perform load balancing of connections between consumer and producer NFs. In addition, using the methodologies described herein, SCP 101 may perform preferred NF location based selection and routing.

NRF 100 is a repository for NF or service profiles of producer NF instances. In order to communicate with a producer NF instance, a consumer NF or an SCP must obtain the NF or service profile or the producer NF instance from NRF 100. The NF or service profile is a JavaScript object notation (JSON) data structure defined in 3GPP Technical Specification (TS) 29.510.

In FIG. 1, any of the nodes (other than NRF 100) can be either consumer NFs or producer NFs, depending on whether they are requesting or providing services. In the illustrated example, the nodes include a policy control function (PCF) 102 that performs policy related operations in a network, a user data management (UDM) function 104 that manages user data, and an application function (AF) 106 that provides application services.

The nodes illustrated in FIG. 1 further include a session management function (SMF) 108 that manages sessions between access and mobility management function (AMF) 110 and PCF 102. AMF 110 performs mobility management operations similar to those performed by a mobility management entity (MME) in 4G networks. An authentication server function (AUSF) 112 performs authentication services for user equipment (UEs), such as user equipment (UE) 114, seeking access to the network.

A network slice selection function (NSSF) 116 provides network slicing services for devices seeking to access specific network capabilities and characteristics associated with a network slice. A network exposure function (NEF) 118 provides application programming interfaces (APIs) for application functions seeking to obtain information about Internet of things (IoT) devices and other UEs attached to the network. NEF 118 performs similar functions to the service capability exposure function (SCEF) in 4G networks.

A radio access network (RAN) 120 connects user equipment (UE) 114 to the network via a wireless link. Radio access network 120 may be accessed using a g-Node B (gNB) (not shown in FIG. 1) or other wireless access point. A user plane function (UPF) 122 can support various proxy functionality for user plane services. One example of such proxy functionality is multipath transmission control protocol (MPTCP) proxy functionality.

UPF 122 may also support performance measurement functionality, which may be used by UE 114 to obtain network performance measurements. Also illustrated in FIG. 1 is a data network (DN) 124 through which UEs access data network services, such as Internet services.

SEPP 126 filters incoming traffic from another PLMN and performs topology hiding for traffic exiting the home PLMN. SEPP 126 may communicate with an SEPP in a visitor PLMN which manages security for the visitor PLMN. Thus, traffic between NFs in different PLMNs may traverse two SEPP functions, one for the home PLMN and the other for the visitor PLMN.

3GPP technical specification TS23003h00 section 28.5 describes network function FQDN format for inter-PLMN routing. 3GPP technical specification TS23003h00 section 28.5.1 mandates the FQDN of the target NF shall have the Home Network Domain. As a result of this requirement, FQDN is needed for inter PLMN routing at a visitor SEPP, V-SEPP. In particular, the specification states:

- For routing HTTP/2 request messages to NF in a different PLMN, the FQDN of the target NF shall have the Home Network Domain (see clause 28.2) as the trailing part.

3GPP technical specification TS29.573g50 Annex C explains end to end flows when SEPP is on path. SEPP performs resolution of FQDN into an IP address using DNS. TCP/TLS connection for sending the HTTP/2 messages is initiated towards the IP address obtained from DNS resolution. In particular, the specification states:

- Resolution of FQDN into an IP address using DNS. TCP/TLS connection for sending the HTTP/2 messages is initiated towards the IP address obtained from DNS resolution.

3GPP technical specification TS29.510h00 section 6.2.6.2.3 documents the NFProfile datastructure returned in the NF Discovery responses and suggests to use interPlmnFqdn only for inter PLMN discovery request. Such (inter-PLMN) discovery is done by V-SEPP and not by H-SEPP. The resolution of inter PLMN FQDN at H-SEPP remains a challenge. In particular, the specification states:

- If the requester-plmn in the query parameter is different from the PLMN of the discovered NF, then the fqdn attribute value shall contain the interPlmnFqdn value registered by the NF during NF registration (see clause 6.1.6.2.2). The requester-plmn is different from the PLMN of the discovered NF if it belongs to none of the PLMN ID(s) configured for the PLMN of the NRF.

SEPP 126 can be implemented by at least one processor and configured for resolution of inter-network domain names between telecommunications networks. SEPP 126 can be configured for storing a mapping between a domain name and a network address of a producer network function of the home network;

receiving a request message from a consumer network function of a visitor network; and resolving a request message domain name of the request message using the mapping between the domain name and the network address of the producer network function of the home network.

In some examples, the home network lacks a dedicated domain name service, and resolving the request message domain name includes resolving the request message domain name without accessing a domain name server.

In some examples, storing the mapping between the domain name and the network address of the producer network function includes storing the mapping while acting as a proxy between the home network and the visitor network.

Acting as a proxy between the home network and the visitor network can include receiving a discovery request from the consumer network function, forwarding the discovery request to a network function repository function (NRF), receiving a response message from the NRF, and forwarding the response message to the consumer network function. Storing the mapping between the domain name and the network address of the producer network function includes extracting the network address and domain name from the response message from the NRF.

In some examples, storing the mapping between the domain name and the network address of the producer network function includes storing other topology information from a network function repository function (NRF), and resolving the request message domain name of the request message includes using the other topology information. Storing other topology information from the NRF can include extracting the other topology information from a subscription/notification request. Storing other topology information from the NRF can include extracting the other topology information from a network function management query.

In some examples, SEPP 126 is configured for forwarding the request message to the producer network function using the network address, receiving a response message from the producer network function, and forwarding the response message to the consumer network function. The home network can be a 5G network and the request message can be a 5G service based interface (SBI) message.

FIG. 2 is a message flow diagram illustrating an example scenario 200 where a routing failure occurs in a home network 204 for a discovery request from a visitor network 206.

Inter PLMN FQDN is mandated for inter PLMN routing; however, no such restriction is made for intra PLMN routing. The operator of home network 204 has decided to configure home network 204 such that home network 204 lacks a dedicated domain name service.

Networks, such as home network 204, which do not support inter PLMN FQDN resolution to IP using DNS cannot support inter-PLMN traffic as H-SEPP cannot resolve/route to the FQDN received in the 5G SBI request. A local configuration of inter-PLMN FQDN to IP mapping via DNS or other means can be cumbersome and can present an operational challenge to keep up with always changing 5G topology.

Home network 204 includes an H-SEPP 208, an H-NRF 210, and a producer network function 212. Visitor network 206 includes a V-SEPP 214, a V-NRF 216, and a consumer network function 218.

Consumer network function 218 sends a discovery request message 220 to V-NRF 216. V-NRF 216 forwards the discovery request message 222 to V-SEPP 214. V-SEPP 214 forwards the discovery request message 224 to H-SEPP 208. H-SEPP 208 forwards the discovery request message 226 to H-NRF 210.

H-NRF 210 sends a discovery response message 228 to H-SEPP 208. The discovery response message 228 identifies producer network function 212. H-SEPP 208 forwards the discovery response message 230 to V-SEPP 214. V-SEPP 214 forwards the discovery response message 232 to V-NRF 216. V-NRF 216 forwards the discovery response message 234 to the consumer network function 218.

Consumer network function 218 sends a 5G SBI request message 236 to V-SEPP 214 and addressed to producer network function 212. V-SEPP 214 forwards the 5G SBI request message 238 to H-SEPP 208. Due to the requirement for using an Inter-PLMN FQDN, H-SEPP 208 will need to resolve the domain name of the 5G SBI request message 238. Since home network 204 lacks a domain name service to provide a mapping between the domain name and the IP address of producer network function 212, H-SEPP 208 will be unable to route 5G SBI request 238.

FIG. 3 is a message flow diagram illustrating an example scenario 300 where the home SEPP is configured for resolution of inter-network domain names between telecommunications networks. H-SEPP 208 is configured for storing a mapping between a domain name and a network address of a producer network function of the home network; receiving a request message from a consumer network function of a visitor network; and resolving a request message domain name of the request message using the mapping between the domain name and the network address of the producer network function of the home network.

Consumer network function 218 sends a discovery request message 302 to V-NRF 216. V-NRF 216 forwards the discovery request message 304 to V-SEPP 214. V-SEPP 214 forwards the discovery request message 306 to H-SEPP 208. H-SEPP 208 forwards the discovery request message 308 to H-NRF 210.

H-NRF 210 sends a discovery response message 310 to H-SEPP 208. The discovery response message 310 identifies producer network function 212. H-SEPP 208 forwards the discovery response message 230 to V-SEPP 214.

By forwarding the discovery request message 308 to H-NRF 210 and the discovery response message 312 to V-SEPP 214, H-SEPP 208 acts as a proxy between home network 204 and visitor network 206. While acting as a proxy between home network 204 and visitor network 206, H-SEPP stores the FQDN and IP address of producer network function 212 for later usage. For example, H-SEPP 208 can extract the domain name and network address for producer network function 212 from discovery response message 310.

H-SEPP 208 can store the FQDN and IP address as a mapping between the FQDN and the IP address. H-SEPP 208 can store various mappings between domain names and network addresses in an appropriate data structure, e.g., a table. H-SEPP 208 can then later resolve domain names by looking up the domain names in the table and retrieving the corresponding network address, even though home network 204 lacks a dedicated domain name service.

H-SEPP 208 can store any appropriate NRF request/response information related to topology information to be used later in FQDN resolution. For example, in some cases, H-SEPP 208 can store topology information from subscription/notification messages or management queries or both.

V-SEPP 214 forwards the discovery response message 232 to V-NRF 216. V-NRF 216 forwards the discovery response message 234 to the consumer network function 218.

H-SEPP 208 uses the previously stored mapping to resolve the FQDN for the 5G SBI request message 320, e.g., by looking up the FQDN in a table of mappings and retrieving the corresponding IP address. H-SEPP 208 forwards the 5G SBI request 322 to producer network function 212.

Producer network function 212 sends a 5G SBI response message 324 to H-SEPP 208. H-SEPP 208 forwards the 5G SBI response message 326 to V-SEPP 214. V-SEPP 214 forwards the 5G SBI response message 328 to consumer network function 218.

FIG. 4 is a flow diagram of an example method 400 for resolution of inter-network domain names between telecommunications networks. Method 400 can be performed, e.g., by the SEPP 126 of FIG. 1.

Method 400 includes storing, at a security edge protection proxy (SEPP) of a home network, a mapping between a domain name and a network address of a producer network function of the home network (402). Method 400 includes receiving, at the SEPP of the home network, a request message from a consumer network function of a visitor network (404). Method 400 includes resolving, at the SEPP of the home network, a request message domain name of the request message using the mapping between the domain name and the network address of the producer network function of the home network (406).

In some examples, method 400 includes forwarding the request message to the producer network function using the network address, receiving a response message from the producer network function, and forwarding the response message to the consumer network function. The home network can be a 5G network and the request message can be a 5G service based interface (SBI) message.

The scope of the present disclosure includes any feature or combination of features disclosed in this specification (either explicitly or implicitly), or any generalization of features disclosed, whether or not such features or generalizations mitigate any or all of the problems described in this specification. Accordingly, new claims may be formulated during prosecution of this application (or an application claiming priority to this application) to any such combination of features.

In particular, with reference to the appended claims, features from dependent claims may be combined with those of the independent claims and features from respective independent claims may be combined in any appropriate manner and not merely in the specific combinations enumerated in the appended claims.

Claims

1. A method for resolution of inter-network domain names between telecommunications networks, the method comprising: storing, at a security edge protection proxy (SEPP) of a home network, a mapping between a domain name and a network address of a producer network function of the home network;receiving, at the SEPP of the home network, a request message from a consumer network function of a visitor network; andresolving, at the SEPP of the home network, a request message domain name of the request message using the mapping between the domain name and the network address of the producer network function of the home network;wherein storing the mapping between the domain name and the network address of the producer network function comprises storing the mapping while acting as a proxy between the home network and the visitor network; andwherein acting as a proxy between the home network and the visitor network comprises receiving a discovery request from the consumer network function, forwarding the discovery request to a network function repository function (NRF), receiving a response message from the NRF, and forwarding the response message to the consumer network function.
2. The method of claim 1, wherein the home network lacks a dedicated domain name service, and wherein resolving the request message domain name comprises resolving the request message domain name without accessing a domain name server.
3. The method of claim 1, wherein storing the mapping between the domain name and the network address of the producer network function comprises extracting the network address and domain name from the response message from the NRF.
4. The method of claim 1, wherein storing the mapping between the domain name and the network address of the producer network function comprises storing topology information from a network function repository function (NRF), and wherein resolving the request message domain name of the request message comprises using the topology information.
5. The method of claim 4, wherein storing topology information from the NRF comprises extracting the topology information from a subscription/notification request.
6. The method of claim 4, wherein storing topology information from the NRF comprises extracting the topology information from a network function management query.
7. The method of claim 1, comprising forwarding the request message to the producer network function using the network address, receiving a response message from the producer network function, and forwarding the response message to the consumer network function.
8. The method of claim 1, wherein the home network is a 5G network and the request message is a 5G service based interface (SBI) message.
9. A system for resolution of inter-network domain names between telecommunications networks, the system comprising: at least one processor and a memory; anda security edge protection proxy (SEPP) of a home network, the SEPP implemented by the at least one processor and configured for: storing a mapping between a domain name and a network address of a producer network function of the home network;receiving a request message from a consumer network function of a visitor network; andresolving a request message domain name of the request message using the mapping between the domain name and the network address of the producer network function of the home network;wherein storing the mapping between the domain name and the network address of the producer network function comprises storing the mapping while acting as a proxy between the home network and the visitor network; andwherein acting as a proxy between the home network and the visitor network comprises receiving a discovery request from the consumer network function, forwarding the discovery request to a network function repository function (NRF), receiving a response message from the NRF, and forwarding the response message to the consumer network function.
10. The system of claim 9, wherein the home network lacks a dedicated domain name service, and wherein resolving the request message domain name comprises resolving the request message domain name without accessing a domain name server.
11. The system of claim 9, wherein storing the mapping between the domain name and the network address of the producer network function comprises extracting the network address and domain name from the response message from the NRF.
12. The system of claim 9, wherein storing the mapping between the domain name and the network address of the producer network function comprises storing topology information from a network function repository function (NRF), and wherein resolving a request message domain name of the request message comprises using the topology information.
13. The system of claim 12, wherein storing topology information from the NRF comprises extracting the topology information from a subscription/notification request.
14. The system of claim 12, wherein storing topology information from the NRF comprises extracting the topology information from a network function management query.
15. The system of claim 9, wherein the SEPP is configured for forwarding the request message to the producer network function using the network address, receiving a response message from the producer network function, and forwarding the response message to the consumer network function.
16. A non-transitory computer readable medium having stored thereon executable instructions that when executed by a processor of a computer control the computer to perform steps comprising: storing, at a security edge protection proxy (SEPP) of a home network, a mapping between a domain name and a network address of a producer network function of the home network;receiving, at the SEPP of the home network, a request message from a consumer network function of a visitor network; andresolving, at the SEPP of the home network, a request message domain name of the request message using the mapping between the domain name and the network address of the producer network function of the home network;wherein storing the mapping between the domain name and the network address of the producer network function comprises storing the mapping while acting as a proxy between the home network and the visitor network; andwherein acting as a proxy between the home network and the visitor network comprises receiving a discovery request from the consumer network function, forwarding the discovery request to a network function repository function (NRF), receiving a response message from the NRF, and forwarding the response message to the consumer network function.

US Referenced Citations (298)

Number	Name	Date	Kind
5381413	Tobagi et al.	Jan 1995	A
6014558	Thomas	Jan 2000	A
6119000	Stephenson et al.	Sep 2000	A
6725278	Gonzalez	Apr 2004	B1
6748435	Wang et al.	Jun 2004	B1
7151945	Myles et al.	Dec 2006	B2
7535915	Collins	May 2009	B2
7706822	Emeott et al.	Apr 2010	B2
7782776	Shankar et al.	Aug 2010	B2
8023482	Gong et al.	Sep 2011	B2
8300637	Bennett, III et al.	Oct 2012	B1
8306034	Jang et al.	Nov 2012	B2
8620858	Backholm et al.	Dec 2013	B2
8645565	Sparks et al.	Feb 2014	B2
8767705	Göppner et al.	Jul 2014	B2
8811228	Lopez et al.	Aug 2014	B2
8811372	Li et al.	Aug 2014	B2
8824449	van der Wateren et al.	Sep 2014	B2
8879431	Ridel et al.	Nov 2014	B2
8954080	Janakiraman et al.	Feb 2015	B2
9124537	Kolze	Sep 2015	B2
9246762	Watkins	Jan 2016	B1
9386551	Zhou et al.	Jul 2016	B2
9667590	Yan et al.	May 2017	B2
9730156	Chamarty et al.	Aug 2017	B1
9781259	Kodaypak	Oct 2017	B1
9893939	Kim et al.	Feb 2018	B2
9894464	Jain et al.	Feb 2018	B2
9948646	Lai et al.	Apr 2018	B1
10097504	Backholm	Oct 2018	B2
10104567	Kodaypak	Oct 2018	B2
10129867	Shaw et al.	Nov 2018	B2
10194459	Kim et al.	Jan 2019	B2
10212639	Kodaypak	Feb 2019	B2
10231113	Huang et al.	Mar 2019	B1
10285155	Dodd-Noble et al.	May 2019	B1
10299128	Suthar et al.	May 2019	B1
10313362	Ahuja et al.	Jun 2019	B2
10313914	Huang et al.	Jun 2019	B2
10361843	Suthar et al.	Jul 2019	B1
10375530	Buckley et al.	Aug 2019	B2
10375548	Kodaypak et al.	Aug 2019	B2
10448243	Tanna	Oct 2019	B2
10470077	Kodaypak et al.	Nov 2019	B1
10517138	Starsinic et al.	Dec 2019	B2
10536211	Leroux	Jan 2020	B2
10542459	Hua et al.	Jan 2020	B2
10548000	Jain et al.	Jan 2020	B2
10548062	Cui et al.	Jan 2020	B2
10555202	Narayanan et al.	Feb 2020	B1
10575278	Kim et al.	Feb 2020	B2
10581623	Lu et al.	Mar 2020	B2
10588085	Kim et al.	Mar 2020	B2
10595256	Marupaduga et al.	Mar 2020	B1
10595268	Lee et al.	Mar 2020	B2
10601932	Kodaypak et al.	Mar 2020	B2
10602322	Palanisamy et al.	Mar 2020	B2
10602441	Palanisamy et al.	Mar 2020	B2
10609154	Talebi Fard et al.	Mar 2020	B2
10609530	Patil et al.	Mar 2020	B1
10616934	Talebi Fard et al.	Apr 2020	B2
10623161	Åström et al.	Apr 2020	B2
10631266	Park et al.	Apr 2020	B2
10637753	Taft et al.	Apr 2020	B1
10652085	Ryu et al.	May 2020	B2
10652098	Kim	May 2020	B2
10742744	Mahalank et al.	Aug 2020	B1
10772062	Albasheir et al.	Sep 2020	B1
10778527	Assali et al.	Sep 2020	B2
10791044	Krishan et al.	Sep 2020	B1
10791508	Park et al.	Sep 2020	B2
10805036	Ronneke et al.	Oct 2020	B2
10805178	Livanos et al.	Oct 2020	B2
10805841	Livanos et al.	Oct 2020	B2
10819636	Goel	Oct 2020	B1
10820231	Huang et al.	Oct 2020	B2
10833938	Rajput et al.	Nov 2020	B1
10880370	Seenappa et al.	Dec 2020	B2
10945120	Gupta et al.	Mar 2021	B2
10972368	Sapra et al.	Apr 2021	B2
11082393	Goel	Aug 2021	B2
11109307	Bartolome Rodrigo et al.	Aug 2021	B2
11159359	Goel	Oct 2021	B2
11224009	Krishan	Jan 2022	B2
11271846	Krishan	Mar 2022	B2
11290549	Krishan	Mar 2022	B2
11323413	Goel	May 2022	B2
11470544	Singh et al.	Oct 2022	B2
11483694	Krishan	Oct 2022	B2
11528334	Krishan	Dec 2022	B2
11570262	Sapra et al.	Jan 2023	B2
20030174649	Shankar et al.	Sep 2003	A1
20030223414	Wong	Dec 2003	A1
20040003069	Wong	Jan 2004	A1
20040062278	Hadzic et al.	Apr 2004	A1
20040141473	Buot	Jul 2004	A1
20040203744	Hicks et al.	Oct 2004	A1
20040208183	Balachandran et al.	Oct 2004	A1
20050193096	Yu et al.	Sep 2005	A1
20050232407	Craig et al.	Oct 2005	A1
20060010224	Sekar et al.	Jan 2006	A1
20070050331	Bauman et al.	Mar 2007	A1
20070242738	Park et al.	Oct 2007	A1
20080039132	Delibie et al.	Feb 2008	A1
20080165761	Goppner et al.	Jul 2008	A1
20090006652	Kasatani	Jan 2009	A1
20090024727	Jeon et al.	Jan 2009	A1
20090055835	Zhu	Feb 2009	A1
20090141625	Ghai et al.	Jun 2009	A1
20090222584	Josefsberg et al.	Sep 2009	A1
20100029301	Pyo et al.	Feb 2010	A1
20100118847	Lee et al.	May 2010	A1
20110078674	Ershov	Mar 2011	A1
20110202604	Craig et al.	Aug 2011	A1
20120320766	Sridhar	Dec 2012	A1
20130029708	Fox et al.	Jan 2013	A1
20130039176	Kanode et al.	Feb 2013	A1
20130198269	Fleischman et al.	Aug 2013	A1
20130272123	Lee et al.	Oct 2013	A1
20140040975	Raleigh et al.	Feb 2014	A1
20140075004	Van Dusen et al.	Mar 2014	A1
20140189151	Aviv et al.	Jul 2014	A1
20140379901	Tseitlin et al.	Dec 2014	A1
20150016266	Dumitrescu et al.	Jan 2015	A1
20150039560	Barker et al.	Feb 2015	A1
20150071074	Zaidi et al.	Mar 2015	A1
20150110000	Zhang et al.	Apr 2015	A1
20150263987	Klein et al.	Sep 2015	A1
20160142324	Vihtari et al.	May 2016	A1
20160156513	Zhang et al.	Jun 2016	A1
20160164788	Goel et al.	Jun 2016	A1
20160183156	Chin et al.	Jun 2016	A1
20160234119	Zaidi et al.	Aug 2016	A1
20160315743	Nagaraj et al.	Oct 2016	A1
20160330647	Iwai	Nov 2016	A1
20160344635	Lee et al.	Nov 2016	A1
20160350683	Bester et al.	Dec 2016	A1
20160352588	Subbarayan et al.	Dec 2016	A1
20160373591	Sharma et al.	Dec 2016	A1
20160380906	Hodique et al.	Dec 2016	A1
20170077751	Forbes	Mar 2017	A1
20170187673	Kaliski, Jr. et al.	Jun 2017	A1
20170195822	Watfa et al.	Jul 2017	A1
20170221015	June et al.	Aug 2017	A1
20170244629	Kodaypak et al.	Aug 2017	A1
20170347283	Kodaypak	Nov 2017	A1
20180035351	Kodaypak	Feb 2018	A1
20180039494	Lander et al.	Feb 2018	A1
20180083882	Krishan et al.	Mar 2018	A1
20180159780	Essigmann et al.	Jun 2018	A1
20180183724	Callard et al.	Jun 2018	A1
20180205637	Li	Jul 2018	A1
20180206093	Jain et al.	Jul 2018	A1
20180213391	Inoue	Jul 2018	A1
20180213991	Youk et al.	Aug 2018	A1
20180230556	Patterson	Aug 2018	A1
20180249281	McCann	Aug 2018	A1
20180262592	Zandi et al.	Sep 2018	A1
20180262625	McCarley et al.	Sep 2018	A1
20180263013	Jain et al.	Sep 2018	A1
20180285794	Gray-Donald et al.	Oct 2018	A1
20180324247	Hood et al.	Nov 2018	A1
20180324646	Lee et al.	Nov 2018	A1
20180324671	Palnati et al.	Nov 2018	A1
20180332462	Kim et al.	Nov 2018	A1
20180343567	Ashrafi	Nov 2018	A1
20180376417	Wang	Dec 2018	A1
20190007329	Velev et al.	Jan 2019	A1
20190007366	Voegele et al.	Jan 2019	A1
20190028337	Ryu et al.	Jan 2019	A1
20190036871	Lapidous et al.	Jan 2019	A1
20190037441	Liu et al.	Jan 2019	A1
20190045351	Zee et al.	Feb 2019	A1
20190069211	Ronneke et al.	Feb 2019	A1
20190069221	Virgile et al.	Feb 2019	A1
20190075552	Yu et al.	Mar 2019	A1
20190116486	Kim et al.	Apr 2019	A1
20190116521	Qiao et al.	Apr 2019	A1
20190140895	Ennis, Jr. et al.	May 2019	A1
20190141527	Krishan	May 2019	A1
20190158364	Zhang et al.	May 2019	A1
20190173740	Zhang et al.	Jun 2019	A1
20190174561	Sivavakeesar	Jun 2019	A1
20190182875	Talebi Fard et al.	Jun 2019	A1
20190191274	Fontaine	Jun 2019	A1
20190191348	Futaki et al.	Jun 2019	A1
20190191467	Dao et al.	Jun 2019	A1
20190222633	Howes et al.	Jul 2019	A1
20190223093	Watfa et al.	Jul 2019	A1
20190230492	Suzuki et al.	Jul 2019	A1
20190230556	Lee	Jul 2019	A1
20190238425	Mladin et al.	Aug 2019	A1
20190238642	Sesham et al.	Aug 2019	A1
20190253461	Bykampadi	Aug 2019	A1
20190253875	Vittal	Aug 2019	A1
20190261244	Jung et al.	Aug 2019	A1
20190268270	Fattah	Aug 2019	A1
20190306251	Talebi Fard et al.	Oct 2019	A1
20190306907	Andreoli-Fang et al.	Oct 2019	A1
20190313236	Lee et al.	Oct 2019	A1
20190313437	Jung et al.	Oct 2019	A1
20190313469	Karampatsis et al.	Oct 2019	A1
20190335002	Bogineni et al.	Oct 2019	A1
20190335534	Atarius et al.	Oct 2019	A1
20190342229	Khinvasara et al.	Nov 2019	A1
20190342921	Loehr et al.	Nov 2019	A1
20190349426	Smith et al.	Nov 2019	A1
20190349901	Basu Mallick et al.	Nov 2019	A1
20190357092	Jung et al.	Nov 2019	A1
20190380031	Suthar et al.	Dec 2019	A1
20190387460	Jonnala et al.	Dec 2019	A1
20190394284	Baghel et al.	Dec 2019	A1
20190394624	Karampatsis et al.	Dec 2019	A1
20190394833	Talebi Fard et al.	Dec 2019	A1
20200007632	Landais et al.	Jan 2020	A1
20200008069	Zhu et al.	Jan 2020	A1
20200021953	Mahalank	Jan 2020	A1
20200028920	Livanos et al.	Jan 2020	A1
20200028973	Livanos et al.	Jan 2020	A1
20200029197	Tandon et al.	Jan 2020	A1
20200037203	Lanev et al.	Jan 2020	A1
20200037226	Magadevan	Jan 2020	A1
20200045753	Dao et al.	Feb 2020	A1
20200045767	Velev et al.	Feb 2020	A1
20200053628	Wang et al.	Feb 2020	A1
20200053670	Jung et al.	Feb 2020	A1
20200053686	Edge et al.	Feb 2020	A1
20200053724	MolavianJazi et al.	Feb 2020	A1
20200053802	Li et al.	Feb 2020	A1
20200053828	Bharatia et al.	Feb 2020	A1
20200059420	Abraham	Feb 2020	A1
20200059856	Cui et al.	Feb 2020	A1
20200059927	Sun et al.	Feb 2020	A1
20200068047	Huang et al.	Feb 2020	A1
20200068626	Cakulev et al.	Feb 2020	A1
20200076764	Robitzsch et al.	Mar 2020	A1
20200077253	Kim et al.	Mar 2020	A1
20200077361	Huang et al.	Mar 2020	A1
20200084277	Somaraju	Mar 2020	A1
20200084663	Park et al.	Mar 2020	A1
20200084677	Yiu et al.	Mar 2020	A1
20200092423	Qiao et al.	Mar 2020	A1
20200092424	Qiao et al.	Mar 2020	A1
20200092706	Kawasaki et al.	Mar 2020	A1
20200100080	Mladin et al.	Mar 2020	A1
20200100088	Kim et al.	Mar 2020	A1
20200100291	Ravishankar et al.	Mar 2020	A1
20200106695	Rk et al.	Apr 2020	A1
20200106812	Verma et al.	Apr 2020	A1
20200120475	Gupta	Apr 2020	A1
20200120478	Kim	Apr 2020	A1
20200127916	Krishan	Apr 2020	A1
20200128566	Wei et al.	Apr 2020	A1
20200136911	Assali et al.	Apr 2020	A1
20200137174	Stammers et al.	Apr 2020	A1
20200137675	Park et al.	Apr 2020	A1
20200145309	Soderlund	May 2020	A1
20200146077	Li et al.	May 2020	A1
20200177629	Hooda et al.	Jun 2020	A1
20200229265	Wang et al.	Jul 2020	A1
20200275257	Gupta et al.	Aug 2020	A1
20200296665	Huang et al.	Sep 2020	A1
20200305033	Keller et al.	Sep 2020	A1
20200313996	Krishan et al.	Oct 2020	A1
20200314615	Patil et al.	Oct 2020	A1
20200314760	Ye et al.	Oct 2020	A1
20200322884	Di Girolamo et al.	Oct 2020	A1
20200336554	Deshpande et al.	Oct 2020	A1
20200344576	Li et al.	Oct 2020	A1
20200366577	Sapra et al.	Nov 2020	A1
20200404608	Albasheir et al.	Dec 2020	A1
20200412597	Goel et al.	Dec 2020	A1
20210000723	Strand et al.	Jan 2021	A1
20210007023	Umapathy et al.	Jan 2021	A1
20210044481	Xu et al.	Feb 2021	A1
20210067480	Goel	Mar 2021	A1
20210067485	Goel	Mar 2021	A1
20210076248	Kallam et al.	Mar 2021	A1
20210105214	Goel	Apr 2021	A1
20210136602	Pokkunuri et al.	May 2021	A1
20210168055	Lair	Jun 2021	A1
20210204200	Krishan et al.	Jul 2021	A1
20210235254	Farooq	Jul 2021	A1
20210273977	Karasaridis et al.	Sep 2021	A1
20210274392	Dao et al.	Sep 2021	A1
20210297935	Belling	Sep 2021	A1
20210367916	Belling et al.	Nov 2021	A1
20210385286	Wang et al.	Dec 2021	A1
20210385732	Reyes et al.	Dec 2021	A1
20220015023	De-Gregorio-Rodriguez et al.	Jan 2022	A1
20220038545	Krishan	Feb 2022	A1
20220060547	Krishan	Feb 2022	A1
20220131945	Sapra et al.	Apr 2022	A1
20220240171	Singh	Jul 2022	A1
20220330004	Sood	Oct 2022	A1
20230042219	Singh et al.	Feb 2023	A1
20230090068	Rajput et al.	Mar 2023	A1
20230099468	Khare et al.	Mar 2023	A1

Foreign Referenced Citations (28)

Number	Date	Country
101366311	Feb 2009	CN
101512971	Aug 2009	CN
105635345	Feb 2019	CN
109788078	May 2019	CN
114930902	Aug 2022	CN
ZL201980067968.7	Sep 2022	CN
202080023004.5	Apr 2023	CN
2020800910053	May 2023	CN
2 575 303	Apr 2013	EP
4022875	Jul 2022	EP
WO 2017143915	Aug 2017	WO
WO 2018174021	Sep 2018	WO
WO 2018174516	Sep 2018	WO
WO 2019034609	Feb 2019	WO
WO 2019062596	Apr 2019	WO
WO 2019076273	Apr 2019	WO
WO 2019144321	Aug 2019	WO
WO 2019220172	Nov 2019	WO
WO 2020091934	May 2020	WO
WO 2020171899	Aug 2020	WO
WO 2020176172	Sep 2020	WO
WO 2020210026	Oct 2020	WO
WO 2020263486	Dec 2020	WO
WO 2021040827	Mar 2021	WO
WO 2021055998	Mar 2021	WO
WO 2021138074	Jul 2021	WO
WO 2022025987	Feb 2022	WO
WO 2022093319	May 2022	WO

Non-Patent Literature Citations (235)

Entry
Office Action for Japanese Application No. 2021-523374 dated Mar. 14, 2023.
Notification to Grant Patent Rights for Chinese Patent Application Serial No. 202080091005.3 (dated Feb. 25, 2023).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application Serial No. 20842464.8 (dated Oct. 12, 2022).
First Examination Report for Indian Patent Application Serial No. 20224703624 (dated Nov. 17, 2022).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 17/082,871 (dated Sep. 28, 2022).
Notification to Grant Patent Right for Chinese Patent Application Serial No. 201980067968.7 (dated Aug. 25, 2022).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/945,794 (dated Aug. 2, 2022).
Notification of the First Office Action for Chinese Patent Application Serial No. 202080023004.5 (dated Jul. 4, 2022).
Notice of Publication for European Patent Application Serial No. 20733169.5 (dated Jun. 9, 2022).
Notice of Allowance for U.S. Appl. No. 17/009,725 (dated Jun. 13, 2022).
Final Office Action for U.S. Appl. No. 17/082,871 (dated Jun. 6, 2022).
Notice of Allowance for U.S. Appl. No. 17/156,149 (dated May 24, 2022).
Advisory Action and Examiner-Initiated Interview Summary for U.S. Appl. No. 16/945,794 (dated May 20, 2022).
Notice of Allowance for U.S. Appl. No. 17/156,149 (dated Apr. 19, 2022).
Communication of European Publication No. and Information on the Application of Article 67(3) EPC for European Patent Application Serial No. 20732441.9 (dated Apr. 6, 2022).
Non-Final Office Action for Chinese Patent Application Serial No. 201980067968.7 (dated Mar. 3, 2022).
First Examination Report for Indian Patent Application Serial No. 202147011137 (dated Mar. 9, 2022).
Final Office Action for U.S. Appl. No. 16/945,794 (dated Feb. 8, 2022).
Non-Final Office Action for U.S. Appl. No. 17/082,871 (dated Feb. 7, 2022).
Commonly-assigned, co-pending U.S. Appl. No. 17/497,879 for “Methods, Systems, and Computer Readable Media for Routing Inter-Public Land Mobile Network (Inter-PLMN) Messages Related to Existing Subscriptions with Network Function (NF) Repository Function (NRF) Using Security Edge Protection Proxy (SEPP)” (Unpublished, filed Oct. 21, 2021).
Commonly-assigned, co-pending U.S. Appl. No. 17/481,004 for Methods, Systems, and Computer Readable Media for Providing for Optimized Service-Bases Interface (SBI) Communications by Preforming Network Function (NF) Fully Qualified Domain Name (FQDN) Resolution at NF Repository Function (NRF) (Unpublished, filed Oct. 1, 2021).
Commonly-Assigned, co-pending U.S. Appl. No. 17/543,989 for “Methods, Systems, and Computer Readable Media for Dynamic Adjustment to Network Function Profile for Discovery Responses” (Unpublished, filed Dec. 17, 2021).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 17/074,553 (dated Dec. 29, 2021).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 17/001,599 (dated Nov. 17, 2021).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 17/102,404 (dated Oct. 7, 2021).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2021/033031 (dated Sep. 16, 2021).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system (Release 17),” 3GPP TS 33.501, V17.3.0, pp. 1-258 (Sep. 2021).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 17),” 3GPP TS CN, V17.3.0, pp. 1-271 (Sep. 2021).
“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.2.0, pp. 1-542 (Sep. 2021).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 17),” 3GPP TS 29.500, V17.4.0, pp. 1-109 (Sep. 2021).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/356,446 (dated Sep. 30, 2021).
“Implementing Quality of Service Policies with DSCP,” Cisco, pp. 1-7 (Feb. 15, 2008).
Mockapetris, “Domain Names—Implementation and Specification,” Network Working Group, Request for Comments 1035, pp. 1-55 (Nov. 1987).
First Examination Report for European Patent Application Serial No. 19 791 391.6 1213 (dated Dec. 16, 2022).
Notification to Grant for Chinese Patent Application Serial No. 202080023004.5 (dated Jan. 29, 2023).
First Examination Report for Indian Patent Application Serial No. 202147053057 (dated Dec. 30, 2022).
First Examination Report for Indian Patent Application Serial No. 202147036462 (dated Dec. 29, 2022).
Non-Final Office Action for U.S. Appl. No. 16/945,794 (dated Sep. 15, 2021).
Non-Final Office Action for U.S. Appl. No. 17/481,004 (dated Jun. 7, 2023).
Notice of Publication for European Patent Application No. 21713526.8 (dated May 10, 2023).
Intention to Grant for European Patent Application 20 838 308.3 (dated Apr. 19, 2023).
Intent to Grant for European Patent Application No. 20733169.5 (dated Jun. 9, 2023).
Notice of Publication for European Patent Application No. 21718460.5 (dated Jun. 14, 2023).
Notice of Publication for European Patent Application No. 21714723.0 (dated Jun. 1, 2023).
Non-Final Office Action for U.S. Appl. No. 17/074,553 (dated Aug. 18, 2021).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/730,799 (dated Aug. 16, 2021).
Communication of European publication No. and information on the application of Article 67(3) EPC for European Patent Application Serial No. 19791391.6 (dated Aug. 11, 2021).
Commonly-Assigned, co-pending U.S. Appl. No. 17/392,288 for “Methods, Systems, and Computer Readable Media for Optimized Routing of Service Based Interface (SBI) Request Messages to Remote Network Function (NF) Repository Functions Using Indirect Communications via Service Communications Proxy (SCP)” (Unpublished, filed Aug. 3, 2021).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/730,799 (dated Jul. 30, 2021).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2021/024000 (dated Jun. 24, 2021).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for U.S. Patent Application Serial No. PCT/US2021/020120 (dated Jun. 1, 2021).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for U.S. Patent Application Serial No. PCT/US2021/020122 (dated Jun. 1, 2021).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 17),” 3GPP TS 29.500, V17.2.0, pp. 1-100 (Mar. 2021).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 17),” 3GPP TS 29.510, V17.1.0, pp. 1-243 (Mar. 2021).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification; (Release 17),” 3GPP TS 23.003, V17.1.0, pp. 1-143 (Mar. 2021).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Public Land Mobile Network (PLMN) Interconnection; Stage 3 (Release 17),” 3GPP TS 29.573, V17.0.0, pp. 1-100 (Mar. 2021).
Nokia et al., “Discussion paper on authorization for Model D Indirect communications”, 3GPP TSG SA WG3; S3-194380 (Nov. 11, 2019).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/697,021 (dated Jun. 21, 2021).
Non-Final Office Action for U.S. Appl. No. 16/356,446 (dated Jun. 16, 2021).
Notice of Publication for International Application Serial No. PCT/US2020/061885 (dated Jun. 3, 2021).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 17/001,599 (dated May 17, 2021).
Advisory Action for U.S. Appl. No. 16/697,021 (dated May 7, 2021).
Applicant-Initiated Interview Summary for U.S. Appl. No. 17/001,599 (dated May 5, 2021).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application Serial No. PCT/US2020/065765 (dated Apr. 15, 2021).
Ex Parte Quayle Action for U.S. Appl. No. 16/730,799 (Apr. 7, 2021).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/555,817 (dated Mar. 24, 2021).
International Search Report and Written Opinion for Patent Cooperation Treaty Application Serial No. PCT/US2020/061885 (dated Feb. 4, 2021).
International Search Report and Written Opinion for Patent Cooperation Treaty Application Serial No. PCT/US2020/057712 (dated Feb. 2, 2021).
Cheshire, S. et al., “Apple's DNS Long-Lived Queries protocol draft-sekar-dns-llq-06,” Internet Engineering Task Force (IETF), pp. 1-26 (Aug. 23, 2019).
Final Office Action for U.S. Appl. No. 16/697,021 (dated Feb. 2, 2021).
Applicant-Initiated Interview Summary for U.S. Appl. No. 16/697,021 (dated Jan. 26, 2021).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16),” 3GPP TS 23.502, V16.7.0, pp. 1-603 (Dec. 2020).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16),” 3GPP TS 23.501, V16.7.0, pp. 1-450 (Dec. 2020).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 17),” 3GPP TS 29.510, V17.0.0, pp. 1-245 (Dec. 2020).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 17),” 3GPP TS 29.500, V17.1.0, pp. 1-90 (Dec. 2020).
Advisory Action for U.S. Appl. No. 16/356,446 (dated Dec. 22, 2020).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/555,817 (dated Dec. 3, 2020).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/415,758 (dated Dec. 2, 2020).
Commonly-Assigned, co-pending U.S. Continuation-in-Part U.S. Appl. No. 17/102,404 for “Methods, Systems, and Computer Readable Media for Policing Access Point Name-Aggregate Maximum Bit Rate (APN-AMBR) Across Packet Data Network Gateway Data Plane (P-GW DP) Worker Instances,” (Unpublished, filed Nov. 23, 2020).
Commonly-Assigned, co-pending U.S. Appl. No. 17/156,149 for “Methods, Systems, and Computer Readable Media for Optimized Routing of Messages Relating to Existing Network Function (NF) Subscriptions Using an Intermediate Forwarding NF Repository Function (NRF),” (Unpublished, filed Nov. 9, 2020).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/287,808 (dated Nov. 4, 2020).
Commonly-Assigned, co-pending U.S. Appl. No. 17/082,871 for “Methods, Systems, and Computer Readable Media for Rank Processing for Network Function Selection,” (Unpublished, filed Oct. 28, 2020).
Applicant-Initiated Interview Summary for U.S. Appl. No. 16/415,758 (dated Oct. 20, 2020).
Commonly-Assigned, co-pending U.S. Continuation-in-Part U.S. Appl. No. 17/074,553 for “Methods, Systems, and Computer Readable Media for Actively Discovering and Tracking Addresses Associated with 4G Service Endpoints,” (Unpublished, filed Oct. 19, 2020).
“p. GW Administration Guide, StarOS Release 21.20,” Cisco, pp. 1-1164 (Oct. 11, 2020).
Commonly-Assigned, co-pending U.S. Appl. No. 17/102,404 for “Methods, Systems, and Computer Readable Media for Policing Access Point Name-Aggregate Maximum Bit Rate (APN-AMBR) Across Packet Data Network Gateway Data Plane (P-GW DP) Worker Instances,” (Unpublished, filed Sep. 23, 2020).
“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.0.0, pp. 1-585 (Sep. 2020).
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 16), 3GPP TS 23.682, V16.8.0, pp. 1-135 (Sep. 2020).
Non-Final Office Action for U.S. Appl. No. 16/697,021 (dated Sep. 29, 2020).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/527,988 (dated Sep. 17, 2020).
Final Office Action for U.S. Appl. No. 16/356,446 (dated Sep. 8, 2020).
Commonly-Assigned, co-pending U.S. Appl. No. 17/009,725 for “Methods, Systems, and Computer Readable Media for Service Communications Proxy (SCP)-Specific Prioritized Network Function (NF) Discovery and Routing,” (Unpublished, filed Sep. 1, 2020).
Notice of Allowance and Fee(s) Due and Examiner-Initiated Interview Summary for U.S. Appl. No. 16/453,955 (dated Aug. 26, 2020).
Commonly-Assigned, co-pending U.S. Appl. No. 17/001,599 for “Methods, Systems, and Computer Readable Media for Optimized Network Function (NF) Discovery and Routing Using Service Communications Proxy (SCP) And NF Repository Function (NRF),” (Unpublished, filed Aug. 24, 2020).
Notification of the Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2020/034723 (dated Aug. 17, 2020).
Non-Final Office Action for U.S. Appl. No. 16/555,817 (dated Aug. 7, 2020).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16),” 3GPP Ts 23.501 V16.5.1, pp. 1-440 (Aug. 2020).
Commonly-Assigned, co-pending U.S. Appl. No. 16/945,794 for “Methods, Systems, And Computer Readable Media For Preferred Network Function (NF) Location Routing Using Service Communications Proxy (SCP),” (Unpublished, filed Jul. 31, 2020).
Commonly-Assigned, co-pending U.S. Appl. No. 16/932,226 for “Methods, Systems, and Computer Readable Media for Monitoring Machine Type Communications (MTC) Device Related Information,” (Unpublished, filed Jul. 17, 2020).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application Serial No. PCT/US2020/024518 (dated Jul. 10, 2020).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application Serial No. PCT/US2020/035004 (dated Jul. 7, 2020).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 16),” 3GPP TS 29.510 V16.4.0, pp. 1-206 (Jul. 2020).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Location Services (LCS); Diameter-based SLh interface for Control Plane LCS (Release 16),” 3GPP TS 29.173 V16.0.0, pp. 1-19 (Jul. 2020).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 16),” 3GPP Ts 23.682 V16.7.0, pp. 1-134 (Jul. 2020).
Non-Final Office Action for U.S. Appl. No. 16/287,808 (dated Jun. 16, 2020).
Ex Parte Quayle Action for U.S. Appl. No. 16/527,988 (Jun. 1, 2020).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications (Release 16),” 3GPP TS 29.336 V16.2.0, pp. 1-79 (Jun. 2020).
“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 based on Diameter protocol (Release 16),” 3GPP TS 29.272 V16.3.0, pp. 1-177 (Jun. 2020).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; T8 reference point for Northbound APIs; (Release 16),” 3GPP TS 29.122 V16.6.0, pp. 1-360 (Jun. 2020) ..........
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 16),” 3GPP TS 29.500 V16.4.0 pp. 1-79 (Jun. 2020).
Non-Final Office Action for U.S. Appl. No. 16/415,758 (dated May 26, 2020).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/369,691 (dated May 12, 2020).
Non-Final Office Action for U.S. Appl. No. 16/356,446 (dated May 11, 2020).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application Serial No. PCT/US2020/013960 (dated Apr. 20, 2020).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/176,920 (dated Apr. 16, 2020).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/399,428 (dated Apr. 6, 2020).
Applicant-Initiated Interview Summary for U.S. Appl. No. 16/176,920 (dated Apr. 1, 2020).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application Serial No. PCT/US2020/013961 (dated Mar. 31, 2020).
Non-Final Office Action for U.S. Appl. No. 16/176,920 (dated Mar. 6, 2020).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications (Release 16),” 3GPP TS 29.128 V16.1.0, pp. 1-51 (Mar. 2020).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16),” 3GPP TS 23.502 V16.4.0, pp. 1-582 (Mar. 2020).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 16),” 3GPP TS 23.501 V16.4.0, pp. 1-430 (Mar. 2020).
Commonly-Assigned, co-pending International Application Serial No. PCT/US20/13961 for “Methods, Systems, and Computer Readable Media for Dynamically Provisioning and Using Public Land Mobile Network (PLMN) Location Mappings in Service Capability Exposure Function (SCEF) or Network Exposure Function (NEF),” (Unpublished, filed Jan. 16, 2020).
Commonly-Assigned, co-pending International Application Serial No. PCT/US20/13960 for “Methods, Systems, and Computer Readable Media for Monitoring Internet of Things (IoT) Device State Through Service Capability Exposure Function (SCEF),” (Unpublished, filed Jan. 16, 2020).
“Oracle® Communications Diameter Signaling Router Service Capability Exposure Function User's Guide,” Release 8.4, F12301-02, Oracle, pp. 1-150 (Jan. 2020).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application Serial No. PCT/US2019/053912 (dated Dec. 18, 2019).
Commonly-Assigned, co-pending U.S. Appl. No. 16/697,021 for “Methods, Systems, and Computer Readable Media for Diameter-Peer-Wide Egress Rate Limiting at Diameter Relay Agent (DRA),” (Unpublished, filed Nov. 27, 2019).
“5G; System architecture for the 5G System (5GS) (3GPP TS 23.501 version 15.6.0 Release 15),” ETSI TS 123 501, V15.6.0, pp. 1-168 (Oct. 2019).
“5G; 5G System; Network function repository services; Stage 3 (3GPP TS 29.510 version 15.5.1 Release 15),” ETSI TS 129 510, V15.5.1, pp. 1-132 (Oct. 2019).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G Systems; Network Function Repository Services; Stage 3 (Release 16),” 3GPP TS 29.510 V.16.1.1, pp. 1-150 (Oct. 2019).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 16/280,672 (dated Sep. 25, 2019).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 16),” 3GPP TS 29.500 V16.1.0, pp. 1-43 (Sep. 2019).
“3rd Generation Partnership Project; Technical Specification Group Service and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 16),” 3GPP TS 23.501 V16.2.0, pp. 1-391 (Sep. 2019).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 16),” 3GPP TS 23.682, V16.4.0, pp. 1-30 (Sep. 2019).
“5G; 5G System; Technical Realization of Service Based Architecture; Stage 3 (3GPP TS 29.500 version 15.5.0 Release 15),” ETSI TS 129 500, V15.5.0, pp. 1-40 (Sep. 2019).
Cheshire et al., “Apple's DNS Long-Lived Queries protocol,” Network Working Group, Apple, Inc., pp. 1-26 (Aug. 22, 2019).
“Diameter and Diameter Applications,” Alcatel-Lucent, http://infodoc.alcatel-lucent.com/html/0_add-h-f/93-0098-HTML/7750_SR_OS_Triple_Play_Guide/GX-PolicyMgmt.html, pp. 1-40 (Aug. 22, 2019).
Commonly-Assigned, co-pending U.S. Appl. No. 16/527,988 for “Methods, Systems, and Computer Readable Media for Network Function (NF) Topology Synchronization,” (Unpublished, filed Jul. 31, 2019).
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP) (Release 15),” 3GPP TS 38.413, V15.4.0, pp. 1-328 (Jul. 2019).
Commonly-Assigned, co-pending U.S. Appl. No. 16/453,955 for “Methods, Systems, and Computer Readable Media for Producer Network Function (NF) Service Instance Wide Egress Rate Limiting at Service Communication Proxy (SCP),” (Unpublished, filed Jun. 26, 2019).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 16),” 3GPP TS 29.510, V16.0.0, pp. 1-135 (Jun. 2019).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Network Function Repository Services; Stage 3 (Release 15),” 3GPP TS 29.510, V15.4.0, pp. 1-127 (Jun. 2019).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 5G System; Restoration Procedures (Release 16),” 3GPP TS 23.527, V16.0.0, pp. 1-19 (Jun. 2019).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification (Release 15),” 3GPP TS 23.003, V15.7.0, pp. 1-131 (Jun. 2019).
Commonly-Assigned, co-pending U.S. Appl. No. 16/415,758 for “Methods, Systems, and Computer Readable Media for Providing Reduced Signaling Internet of Things (Iot) Device Monitoring,” (Unpublished, filed May 17, 2019).
Commonly-Assigned, co-pending U.S. Appl. No. 16/399,428 for “Methods, Systems, and Computer Readable Media for Monitoring Lightweight Machine to Machine (LWM2M) Internet of Things (IoT) Devices Through Service Capability Exposure Function (SCEF) T8 Interface,” (Unpublished, filed Apr. 30, 2019).
Huawei, “eSBA: reselection of producer instance,” 3GPP TSG-SA2 Meeting #132, pp. 1-2 (Apr. 12, 2019).
“Class of Service Feature Guide (Routers and EX9200 Switches),” Junos® OS, Juniper Networks, pp. 1-1530 (Apr. 10, 2019).
Commonly-Assigned, co-pending U.S. Appl. No. 16/369,691 for “Methods, System, and Computer Readable Media for Handling Multiple Versions of Same Service Provided by Producer Network Functions (NFs),” (Unpublished, filed Mar. 29, 2019).
Commonly-Assigned, co-pending U.S. Appl. No. 16/356,446 for “Methods, Systems, and Computer Readable Media for Locality-Based Selection and Routing of Traffic TO Producer Network Functions (NFs),” (Unpublished, filed Mar. 18, 2019).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture and 5G; Stage 2 (Release 16),” 3GPP TS 23.501, V16.0.0, pp. 1-318 (Mar. 2019).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications (Release 15),” 3GPP TS 29.336, V15.6.0, pp. 1-79 (Mar. 2019).
“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 based on Diameter protocol (Release 15),” 3GPP TS 29.272, V15.7.0, pp. 1-179 (Mar. 2019).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 16),” 3GPP TS 23.682, V16.2.0, pp. 1-126 (Mar. 2019).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; T8 reference point for Northbound APIs; (Release 16),” 3GPP TS 29.122, V16.1.0, pp. 1-288 (Mar. 2019).
Commonly-Assigned, co-pending U.S. Appl. No. 16/287,808 for “Methods, Systems, and Computer Readable Media for Dynamically Provisioning and Using Public Land Mobile Network (PLMN) Location Mappings in Service Capability Exposure Function (SCEF) or Network Exposure Function (NEF),” (Unpublished, filed Feb. 27, 2019).
Commonly-Assigned, co-pending U.S. Appl. No. 16/280,672 for “Methods, Systems, And Computer Readable Media for (IoT) Device State Through Service Capability Exposure Function (SCEF),” (Unpublished, filed Feb. 20, 2019).
Penttinen, “5G Explained: Security and Deployment of Advanced Mobile Communications,” Chapter 6, Section 6.3.8 NRF, 2 pages (Feb. 2019).
“OMA Lightweight Machine to Machine Requirements,” Candidate Version 1.2, Open Mobile Alliance, pp. 1-20 (Jan. 24, 2019).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 16),” 3GPP TS 23.682, V16.1.0, pp. 1-126 (Dec. 2018).
“Oracle Communications Diameter Signaling Router,” Release Notice, Release 8.3, E93179 Revision 02, Oracle, pp. 1-98 (Dec. 2018).
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-Utran); S1 Application Protocol (S1AP) (Release 15),” 3GPP TS 36.413, V15.4.0, pp. 1-383 (Dec. 2018).
“3rd Generation Partnership Project; Technical Specification Group Network and Terminals; 5G Systems; Network Function Repository Services; Stage 3 (Release 15),” 3GPP TS 29.510, V15.2.0, pp. 1-113 (Dec. 2018).
“3rd Generation Partnership Project; Technical Specification Group Network and Terminals; 5G Systems; Principles and Guidelines for Services Definition; Stage 3 (Release 15),” 3GPP TS 29.501, V15.2.0, pp. 1-66 (Dec. 2018).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications (Release 15),” 3GPP TS 29.336, V15.5.0, pp. 1-74 (Dec. 2018).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications (Release 15),” 3GPP TS 29.128, V15.4.0, pp. 1-52 (Dec. 2018).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; T8 reference point for Northbound APIs; (Release 15),” 3GPP TS 29.122, V15.2.0, pp. 1-297 (Dec. 2018).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobile Application Part (MAP) specification (Release 15),” 3GPP TS 29.002, V15.4.0, pp. 1-1021 (Dec. 2018).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhancements to the Service-Based Architecture (Release 16),” 3GPP TR 23.742, V16.0.0, pp. 1-131 (Dec. 2018).
Commonly-Assigned, co-pending U.S. Appl. No. 16/176,920 for “Methods, Systems, and Computer Readable Media for Providing a Service Proxy Function in a Telecommunications Network Core Using a Service-Based Architecture,” (Unpublished, filed Oct. 31, 2018).
“Addressing 5G Network Function Requirements,” Intel® FPGAs and Intel PAC 5G QoS and IPSec Benchmarking, White Paper, pp. 1-8 (Oct. 2018).
“5G; 5G System; Network function repository services; Stage 3 (3GPP TS 29.510 version 15.1.0 Release 15),” ETSI TS 129 510, V15.1.0, pp. 1-87 (Oct. 2018).
“5G; 5G System; Unified Data Repository Services; Stage 3 (3GPP TS 29.504 version 15.1.0 Release 15),” ETSI TS 129 504, V15.1.0, pp. 1-26 (Oct. 2018).
“Diameter Signaling Router SCEF User's Guide,” Release 8.3, E93572, Oracle® Communications, pp. 1-110 (Sep. 2018).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Universal Geographical Area Description (GAD) (Release 15),” 3GPP TS 23.032, pp. 1-32 (Sep. 2018).
“CPS vDRA Configuration Guide,” Release 18.3.0 (Restricted Release)(1), Cisco, pp. 1-130 (Sep. 14, 2018).
“How to Do Rate Limiting of Diameter Messages Using NetScaler,” Citrix Systems Inc., pp. 1-3 (Sep. 4, 2018).
“Lightweight Machine to Machine Technical Specification: Transport Bindings,” Approved Version: 1.1, Open Mobile Alliance, pp. 1-68 (Aug. 6, 2018).
“5G; 5G System; Technical Realization of Service Based Architecture; Stage 3 (3GPP TS 29.500 version 15.0.0 Release 15),” ETSI TS 129 500, V15.0.0, pp. 1-29 (Jul. 2018).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhancements to the Service-Based Architecture (Release 16),” 3GPP TR 23.742, V0.3.0, pp. 1-64 (Jul. 2018).
“Universal Mobile Telecommunications System (UMTS); LTE; Tsp interface protocol between the MTC Interworking Function (MTC-IWF) and Service Capability Server (SCS),” 3GPP TS 29.368, V15.0.0, pp. 1-35 (Jul. 2018).
“3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 signalling transport (Release 15),” 3GPP TS 36.412, V15.0.0, pp. 1-8 (Jun. 2018).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Enhancements to the Service-Based Architecture (Release 16),” 3GPP TR 23.742, V0.2.0, pp. 1-39 (Jun. 2018).
“5G; Procedures for the 5G System (3GPP TS 23.502 version 15.2.0 Release 15),” ETSI TS 123 502 V15.2.0, pp. 1-46 (Jun. 2018).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 (Release 15),” 3GPP TS 23.078, V15.0.0, pp. 1-750 (Jun. 2018).
“Lightweight Machine to Machine Technical Specification: Transport Bindings,” Candidate Version: 1.1, Open Mobile Alliance, pp. 1-67 (Jun. 12, 2018).
“Lightweight Machine to Machine Technical Specification: Core,” Candidate Version: 1.1, Open Mobile Alliance, pp. 1-142 (Jun. 12, 2018).
Docomo, “Update Solution 4 for implicit registration,” SA WG2 Meeting #129, pp. 1-2 (Oct. 15- 19, 2018).
“Cisco Ultra 5G Packet Core Solution,” Cisco, White paper, https://www.cisco.com/c/dam/en/US/products/collateral/routers/network-convergence-system-500-series-routers/white-paper-c11-740360.pdf, pp. 1-11 (2018).
Li et al., “Mobile Edge Computing Platform Deployment in 4G LTE Networks: A Middlebox Approach,” https://www.usenix.org/system/files/conference/hotedge18/hotedge18-papers-li.pdf, 6 pages (2018).
Mayer, “RESTful APIs for the 5G Service Based Architecture,” Journal of ICT, vol. 6_1&2, pp. 101-116 (2018).
“5G Service Based Architecture (SBA),” 5G, pp. 1-61 (downloaded Dec. 24, 2018).
Scholl et al., “An API First Approach to Microservices Development,” Oracle, https://blogs.oracle.com/developers/an-api-first-approach-to-microservices-development, pp. 1-12 (Nov. 8, 2017).
Mayer, Georg (Huawei), “3GPP 5G CoreNetwork Status,” 3GPP a Global Initiative, pp. 1-23 (Nov. 2017).
Brown et al., “Service-Based Architecture for 5G Core Networks,” Huawei, Heavy Reading, https://www.3g4g.co.uk/5G/5Gtech_6004_2017_11_Service-Based-Architecture-for-5G-Core- Networks_HR_Huawei.pdf, pp. 1-12 (Nov. 2017).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15),” 3GPP TS 23.501, V1.5.0, pp. 1-170 (Nov. 2017).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 15),” 3GPP TS 23.682, V15.2.0, pp. 1-122 (Sep. 2017).
“Pseudo-CR on Service Discovery and Registration using NRF service,” Ericsson, 3GPP TSG CT4 Meeting #79, 3GPP TR 29.891—v0.3.0, pp. 1-4 (Aug. 21-25, 2017).
Carlton et al., “HTTP and DNS in a 5G World,” https://www.computerworld.com/article/3204594/http-and-dns-in-a-5g-world.html, pp. 1-5 (Jun. 30, 2017).
Benacer et al., “A High-Speed Traffic Manager Architecture for Flow-Based Networking,” pp. 1-4 (2017).
Hoglund et al., “Overview of 3GPP Release 14 Enhanced NB-IoT,” in IEEE Network, vol. 31, No. 6, pp. 16-22 (Nov./Dec. 2017).
Kafle et al., “Scalable Directory Service for IoT Applications,” in IEEE Communications Standards Magazine, vol. 1, No. 3, pp. 58-65 (Sep. 2017).
Kouzayha et al., “Measurement-Based Signaling Management Strategies for Cellular IoT,” in IEEE Internet of Things Journal, vol. 4, No. 5, pp. 1434-1444 (Oct. 2017).
Yu, “The Mobile Network Capability Exposure Friendly to the Mobile Internet Applications,” 2017 IEEE Wireless Communications and Networking Conference (WCNC), pp. 1-6 (2017).
Bormann et al., “Block-Wise Transfers in the Constrained Application Protocol (CoAP),” RFC 7959, pp. 1-37 (Aug. 2016).
“Dynamically Reconfigurable Optical-Wireless Backhaul/Fronthaul with Cognitive Control Plane for Small Cells and Cloud-RANs: D3.1 Analysis of state of the art on scalable control plane design and techniques for user mobility awareness. Definition of 5G-XHaul control plane requirements,” European Commission, 5G-XHaul, pp. 1-107 (Jun. 31, 2016).
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Domain Name System Procedures; Stage 3 (Release 13),” 3GPP TS 29.303 V13.4.0, pp. 1-69 (Jun. 2016).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 13),” 3GPP TS 23.682, V13.6.0, pp. 1-91 (Jun. 2016).
“Multi-Layer Security Protection for Signaling Networks,” Oracle Communications, Oracle white paper, pp. 1-9 (Jan. 2016).
Kantola et al., “Policy-based communications for 5G mobile with customer edge switching,” Security and Communication Networks, vol. 9, pp. 3070-3082 (2016).
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements to facilitate communications with packet data networks and applications (Release 13),” 3GPP TS 23.682, V13.4.0, pp. 1-81 (Dec. 2015).
Hartke, “Observing Resources in the Constrained Application Protocol (CoAP),” RFC 7641, pp. 1-30 (Sep. 2015).
ZTE, “Reporting the No. of UEs in Certain Geographic Area,” SA WG2 Meeting #107, pp. 1-4 (Jan. 30, 2015).
Ratasuk et al., “Overview of LTE Enhancements for Cellular IoT,” 2015 IEEE 26th International Symposium on Personal, Indoor and Mobile Radio Communications—(PIMRC): Workshop on M2M Communications: Challenges, Solutions and Applications, pp. 1-5 (2015).
Hawilo et al., “NFV: State of the Art, Challenges, and Implementation in Next Generation Mobile Networks (vEPC),” IEEE Network, pp. 1-9 (Nov./Dec. 2014).
Abdullah et al., “Femtocell Geo-location Challenge: DSL Approach as Solution,” 2014 IEEE 5th Control and System Graduate Research Colloquium, pp. 239-241 (Aug. 11, 2014).
Fielding et al. “Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content”, Internet Engineering Taskforce (IETF) Request for Comments: 7231, IEFT RFC 7231, pp. 1-102 (Jun. 2014).
Shelby et al., “The Constrained Application Protocol (CoAP),” RFC 7252, pp. 1-112 (Jun. 2014).
Abley et al., “A Mechanism for Remote-Triggered DNS Cache Flushes (DNS FLUSH),” Network Working Group, Google, pp. 1-12 (Jun. 24, 2013).
Preston-Werner, “Semantic Versioning 2.0.0”, Oracle, pp. 1-5 (Jun. 2013).
“LTE and Beyond,” https://ytd2525.wordpress.com/2013/03/06/lte-and-beyond/, 3 pages (2013).
Fajardo et al., “Diameter Based Protocol,” Internet Engineering Task Force (IETF) Request for Comments: 6733, pp. 1-152 (Oct. 2012).
China Mobile, “Supporting legacy HLR in Architecture for MTC usage,” SA WG2 Meeting #90, pp. 1-9 (Apr. 10, 2012).
Le et al., “Cross-Layer Mobility Management based on Mobile IP and SIP in IMS,” 2007 International Conference on Wireless Communications, Networking and Mobile Computing, pp. 803-806 (2007).
Bertrand, “The IP Multimedia Subsystem in Next Generation Networks” Network, Multimedia and Security Department (RSM), pp. 1-9 (May 30, 2007).
Faccin et al., “IP multimedia services: analysis of mobile IP and SIP interactions in 3G networks,” in IEEE Communications Magazine, vol. 42, No. 1, pp. 113-120 (Jan. 2004).
Gulbrandsen et al., “A DNS RR for specifying the location of services (DNS SRV),” RFC 2782, pp. 1-12 (Feb. 2000).
Nichols et al., “Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPV6 Headers,” Internet Engineering Task Force (IETF) Network Working Group Request for Comments (RFC) 2474, The Internet Society, pp. 1-20 (Dec. 1998).
First Office Action for Chinese Patent Application Serial No. 202180052441.4 (dated Aug. 30, 2023).
Decision to Grant for European Patent Application Serial No. 20838308.3 (dated Aug. 31, 2023).
Notice of Publication for European Patent Application Serial No. 21731870.8 (dated Aug. 9, 2023).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 17/392,288 (dated Jul. 27, 2023).
Notice of Allowance for U.S. Appl. No. 17/497,879 (dated Jul. 26, 2023).
First Examination Report for Indian Patent Application Serial No. 202247065596 (dated May 30, 2023).
Intent to Grant for Japanese Patent Application No. 2021-523374 (dated Jun. 27, 2023).

Related Publications (1)

	Number	Date	Country
	20220417204 A1	Dec 2022	US

Methods, systems, and computer readable media for resolution of inter-network domain names

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

CPC

International Classifications