Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1-5, 7, 9, 11, 14-18, and 48 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claims 1-5, 7, 9, 11, 14-18, and 48 recite “a second function discovery request”. However, there is no “first function discovery request” required, therefore, it is unclear whether it is included or excluded from the claimed language.
Claim 48 recites “the first function”. There is insufficient antecedent basis for this limitation in the claim. Examiner will assume that this limitation refers to the “EAS search apparatus” as such would be reasonably equivalent to the recitations of a “first function” in claim 1.
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claim(s) 1-5, 7, 9, 11, 14-18, and 48 are rejected under 35 U.S.C. 103 as being unpatentable over US 20250030774 A1 to Tonesi et al. (“Tonesi”) in view of US 11729137 B2 to Lee et al. (“Lee”).
Regarding claim 1, Tonesi taught an Edge Application Server (EAS) search method, applied to a first function, comprising: sending at least one of first information or second information to a second function to perform an EAS search (“discovery”). (consider at least paragraph 0096, “The EASDF 425 facilitates discovery of EAS 450 and EASs of a network to which the EASDF 425 belongs (that is, a network with which the EASDF is associated). An EASDF 425 may be associated with a network if the EASDF 425 has discovery information (e.g., filtering information or a network address) for EASs belonging to the second network. The EASDF 425 may be configured by the SMF 410 to handle domain name system (DNS) lookup for a UE 120. For example, the SMF 410 may create and update a DNS context associated with the UE 120 for the EASDF 425. The EASDF 425 may receive a DNS query (sometimes referred to as a discovery message) from the UE 120. The EASDF 425 may refer to filtering information, configured by the SMF 410 or the AF 440, to ascertain or determine if a network address of the DNS query is associated with a shared EASDF 430 or an EASDF 425 of another network (such as the second network). The EASDF 425, or the SMF 410, may provide the DNS request to the shared EASDF 430 or the EASDF 425. The SMF 410 or the EASDF 425 may receive a DNS response and may provide the DNS response to the UE 120. The DNS response may include information for communicating with an EAS 450. Thus, the EASDF 425 may facilitate discovery of EASs in another network by the UE 120.”)
Tonesi may be interpreted as not expressly teaching wherein the method further comprises: discovering the second function through a third function, wherein the third function comprises a Network Repository Function (NRF) of a network to which the first function belongs, wherein discovering the second function through the third function comprises: requesting the NRF to search the second function by sending a second function discovery request to the NRF, wherein the request carries terminal location information and an application identifier.
However, in an analogous art related to EAS searches, Lee taught the discovering the second function through a third function, wherein the third function comprises a Network Repository Function (NRF) of a network to which the first function belongs, wherein discovering the second function through the third function comprises: requesting the NRF to search the second function by sending a second function discovery request to the NRF, wherein the request carries terminal location information and an application identifier. (consider column 19, lines 1-46, “Referring to FIG. 7, in operation 710, an NEF (EDR) 705, which processes EDR information, transmits, to an NRF 703, a registration request message for registering that the NEF (EDR) 705 is managing EAS domain configuration information. The registration request message transmitted from the NEF (EDR) 705 to the NRF 703 may include at least one of the following information. Endpoint address of NEF (EDR) 705 Differentiator for differentiating EAS domain configuration information Network and slice identifier, DNN/S-NSSAI, to provide EAS domain configuration information Name, ECAN and/or DNAI, of the data center providing EAS domain configuration information In operation 715, when the UE's PDU session is generated or changed, or when the UE moves, the SMF 701 transmits an association setup message to the EASDF 702. The association setup message transmitted from the SMF 701 to the EASDF 702 may include at least one of the following information. Information for identifying the data network and slice of UE 700 (e.g., DNN/S-NSSAI) Information for identifying UE 700 (e.g., the network address of UE 700, IPv4 address, IPv6 prefix/address, Ethernet MAC address, and/or identifier (SUPI and/or GPSI) of UE 700) List of DNAIs already connected with UE 700 through local UPF List of DNAIs connectable with UE 700 through local UPF In operation 720, the EASDF 702 discovers the address of the NEF (EDR) 705 based on information obtained through the NRF 703 or preset information. As an example, the EASDF 702 transmits a discovery request message for the NEF (EDR) 705 to the NRF 703 to discover the NEF (EDR) 705. The discovery request message transmitted from the EASDF 702 to the NRF 703 may include information about ECAN and/or DNN/S-NSSAI for discovery for the NEF (EDR) 705. In operation 725, the NRF 703 discovers the NEF (EDR) 705 storing EAS domain configuration information through information registered in operation 710. The NRF 703 transmits, to the EASDF 702, a response message including information about the endpoint address of the NEF (EDR) 705 requested for discovery by the EASDF 702, as a response to the discovery request message in operation 720.”)
It would have been obvious to one skilled in the art before the effective filing date of the claimed invention to combine the teachings of these references such that their combination includes every element as claimed. One skilled in the art could have combined the teachings by known methods such as integration of software routines with no changes to the operation of either reference such that, in combination, each element merely performs the same function as it does separately. Additionally, Examiner finds that, based on the references' analogous disclosure regarding EAS searching functionality, further demonstrates that a combination of their features would have been known and obvious. Therefore, such a combination of the teachings of the references would have yielded nothing more than predictable results to one of ordinary skill in the art.
Regarding claim 2, the combined teachings of Tonesi and Lee taught the method of claim 1.
Tonesi further taught the method further comprising at least one of:
acquiring the first information from a fourth function; or acquiring the second information from a fifth function. (again, consider paragraph 0096, specifically “An EASDF 425 may be associated with a network if the EASDF 425 has discovery information (e.g., filtering information or a network address) for EASs belonging to the second network. The EASDF 425 may be configured by the SMF 410 to handle domain name system (DNS) lookup for a UE 120. For example, the SMF 410 may create and update a DNS context associated with the UE 120 for the EASDF 425. The EASDF 425 may receive a DNS query (sometimes referred to as a discovery message) from the UE 120. The EASDF 425 may refer to filtering information, configured by the SMF 410 or the AF 440, to ascertain or determine if a network address of the DNS query is associated with a shared EASDF 430 or an EASDF 425 of another network (such as the second network).”) (consider further paragraph 0115, specifically “The SEASDF 625-1 and the pEASDF 625-2 may communicate with one another to facilitate discovery of the EAS 650 by the UE. For example, each of the first PLMN and the second PLMN may be associated with a respective EASDF 625. If more than two PLMNs are federated, then each of the federated PLMNs may be associated with a respective EASDF 625. The sSMF 610-1 of the first network may select the SEASDF 625-1 and the pEASDF 625-2 for discovery of the EAS 650. For example, an AF may configure a NEF or a UDR (not shown in FIG. 6 for simplicity) with filtering information. In some aspects, the filtering information may be included in EAS deployment information. The filtering information may include, for example, information indicating a PLMN of the EAS 650, information indicating a set of network addresses associated with the EAS 650 (such as a FQDN or a range of FQDNs, a set of IP addresses or a range of IP addresses associated with a data network access identifier (DNAI), a DNS server identifier associated with a DNAI, or other information…The sSMF 610-1 may select a pEASDF 625-2 for a DNS query received from the UE (such as from the SEASDF 625-1). For example the sSMF 610-1 may select, ascertain or determine a pEASDF 625-2 associated with a PLMN identifier based on matching an FQDN of the DNS query with an entry of an FQDN filter that corresponds to the PLMN identifier, and based on a DNS server address in the DNS query matching with an entry of the DNS server address filter that corresponds to the PLMN identifier.”)
Regarding claim 3, the combined teachings of Tonesi and Lee taught the method of claim 1.
Tonesi further taught wherein the first function comprises at least one of: an EAS Discovery Function (EASDF); a Session Management Function (SMF); Security Edge Protection Proxies (SEPP); or a Network Exposure Function (NEF). (“EASDF” or “SMF”; again, consider paragraph 0096, “The EASDF 425, or the SMF 410, may provide the DNS request to the shared EASDF 430 or the EASDF 425.”)
Regarding claim 4, the combined teachings of Tonesi and Lee taught the method of claim 1.
Tonesi further taught wherein the second function comprises at least one of:
an EAS Discovery Function (EASDF); a Session Management Function (SMF); Security Edge Protection Proxies (SEPP); or a Network Exposure Function (NEF). (“shared EASDF”; again, consider paragraph 0096, “The EASDF 425, or the SMF 410, may provide the DNS request to the shared EASDF 430 or the EASDF 425. The SMF 410 or the EASDF 425 may receive a DNS response and may provide the DNS response to the UE 120.”)
Regarding claim 5, the combined teachings of Tonesi and Lee taught the method of claim 1.
Tonesi further taught wherein the fourth function comprises at least one of:
a Session Management Function (SMF); an EAS Discovery Function (EASDF); a Policy Control Function (PCF); or a Radio Access Network (RAN), (“SMF”) (again, consider paragraph 0096, specifically “An EASDF 425 may be associated with a network if the EASDF 425 has discovery information (e.g., filtering information or a network address) for EASs belonging to the second network. The EASDF 425 may be configured by the SMF 410 to handle domain name system (DNS) lookup for a UE 120. For example, the SMF 410 may create and update a DNS context associated with the UE 120 for the EASDF 425”) and
wherein the fourth function comprises at least one of:
a terminal; a base station; a Radio Access Network (RAN); or a User Plane Function (UPF). (“UE”; again, consider paragraph 0096, specifically “The EASDF 425 may receive a DNS query (sometimes referred to as a discovery message) from the UE 120.”)
Regarding claim 7, the combined teachings of Tonesi and Lee taught the method of claim 1.
Tonesi further taught wherein the first information comprises at least one of:
a terminal Internet Protocol (IP) address; a terminal identifier; a Subscription Permanent Identifier (SUPI); a Generic Public Subscription Identifier (GPSI); a Public Land Mobile Network (PLMN) identifier; a notification endpoint; a terminal location; Domain Name System (DNS) message handling rules; an application identifier; or N6 transmission requirements, (again, consider paragraph 0096, specifically “An EASDF 425 may be associated with a network if the EASDF 425 has discovery information (e.g., filtering information or a network address) for EASs belonging to the second network. The EASDF 425 may be configured by the SMF 410 to handle domain name system (DNS) lookup for a UE 120. For example, the SMF 410 may create and update a DNS context associated with the UE 120 for the EASDF 425”) (consider further paragraph 0115, specifically “The SEASDF 625-1 and the pEASDF 625-2 may communicate with one another to facilitate discovery of the EAS 650 by the UE. For example, each of the first PLMN and the second PLMN may be associated with a respective EASDF 625. If more than two PLMNs are federated, then each of the federated PLMNs may be associated with a respective EASDF 625. The sSMF 610-1 of the first network may select the SEASDF 625-1 and the pEASDF 625-2 for discovery of the EAS 650. For example, an AF may configure a NEF or a UDR (not shown in FIG. 6 for simplicity) with filtering information. In some aspects, the filtering information may be included in EAS deployment information. The filtering information may include, for example, information indicating a PLMN of the EAS 650, information indicating a set of network addresses associated with the EAS 650 (such as a FQDN or a range of FQDNs, a set of IP addresses or a range of IP addresses associated with a data network access identifier (DNAI), a DNS server identifier associated with a DNAI, or other information).”)
and
wherein the second information comprises at least one of:
a Domain Name System (DNS) query; Extension mechanisms for DNS (EDNS); a Fully Qualified Domain Name (FQDN) of an EAS; a terminal Internet Protocol (IP) address; a terminal identifier; or a terminal location. (again, consider paragraph 0096, specifically “The EASDF 425 may receive a DNS query (sometimes referred to as a discovery message) from the UE 120.”) (consider further paragraph 0115, specifically “The sSMF 610-1 may select a pEASDF 625-2 for a DNS query received from the UE (such as from the SEASDF 625-1). For example the sSMF 610-1 may select, ascertain or determine a pEASDF 625-2 associated with a PLMN identifier based on matching an FQDN of the DNS query with an entry of an FQDN filter that corresponds to the PLMN identifier, and based on a DNS server address in the DNS query matching with an entry of the DNS server address filter that corresponds to the PLMN identifier.”)
Regarding claim 9, the combined teachings of Tonesi and Lee taught the method of claim 1.
Tonesi further taught wherein the first function is configured with third information, wherein the third information comprises at least one of:
an application identifier; a Public Land Mobile Network (PLMN) identifier; an Internet Protocol (IP) address of the first function; a Fully Qualified Domain Name (FQDN) of the first function; an IP address of an EAS Discovery Function (EASDF); an FQDN of the EASDF; a geographic location; an external group identifier; an internal group identifier; N6 transmission requirements; a Differentiated Services Code Point (DSCP); a Virtual Extensible Local Area Network (VXLAN); a Virtual Local Area Network (VLAN); or a service scope. (again, consider paragraph 0096, specifically “The EASDF 425 may be configured by the SMF 410 to handle domain name system (DNS) lookup for a UE 120.”) (consider further paragraph 0105, specifically “As shown by reference number 516 and 518, the SMF 502 may create a DNS context with the serving EASDF 506. For example, the SMF 502 and the serving EASDF 506 may exchange DNS context creation messages (shown as Neasdf_DNSContext_Create Request and Neasdf_DNSContext_CreateResponse). In some aspects, the DNS context may be associated with the UE. For example, the DNS context may indicate rules (such as filtering information) regarding how the serving EASDF 506 may handle DNS messages from the UE. As shown by reference number 520 and 522, the SMF 502 may optionally update the DNS context (such as by performing a DNS context update procedure). For example, the SMF 502 may modify the DNS context by exchanging DNS context update messages (shown as Neasdf_DNSContext_UpdateRequest and Neasdf_DNSContext_UpdateResponse) with the serving EASDF 506. In some aspects, by creating or updating the DNS context, the SMF 502 may provide filtering information to the serving EASDF 506. The filtering information may indicate a set of network addresses.”)
Regarding claim 11, the combined teachings of Tonesi and Lee taught the method of claim 1.
Tonesi further taught wherein at least one of the first information or the second information is sent to the second function by at least one of:
a user plane path; a control plane path; or invoking a service interface, wherein the user plane path at least comprises at least one of a fourth function or a fifth function, the fourth function is used to control and manage traffic in a first Public Land Mobile Network (PLMN), and the fifth function is used to control and manage traffic in a second PLMN. (consider paragraph 0055, specifically “Furthermore, techniques described herein enable communication between a UE connected to a first network and an EDN (such as an EAS hosted by the EDN) of a second network, such as by establishing a connection between a user plane function (UPF) of the first network associated with the UE and a network entity of the second network (such as a UPF of the second network or a network entity of the EDN).”) (also consider paragraph 0116, specifically “As mentioned, example 600 also shows data paths 660 and 665 between the first network and the second network. For example, the first network may implement data path 660, or may implement data path 665. As shown, example 600 may involve one or more federated UPFs. For example, the first network may include a federated serving UPF (shown as fsUPF). In examples using the data path 660, the second network may include a federated partner UPF (shown as fpUPF). A federated UPF is a UPF associated with providing a data path between networks to facilitate communication with an EAS. For example, a federated UPF may act as a gateway between federated PLMNs. A federated UPF may be associated with a specific DNAI. For example, a federated UPF may be associated with a DNAI designated for communication with an EAS. The SEASDF 625-1 may receive a DNAI from the pEASDF 625-2. The DNAI may correspond to the fpUPF 620-2 or may correspond to an EDN that includes the EAS 650. The sSMF 610-1 may configure a connection between the fsUPF 620-1 and a network entity associated with the received DNAI (which may be the fpUPF 620-2 or a network entity of the EDN).”)
Regarding claim 14, the combined teachings of Tonesi and Lee taught the method of claim 1.
Tonesi further taught wherein discovering the second function comprises at least one of:
discovering address information of the second function; discovering an Internet Protocol (IP) address of the second function; or discovering a Fully Qualified Domain Name (FQDN) of the second function. (again, consider paragraph 0102, “EAS 450 is an application server that resides in an edge hosting environment such as an EDN. EAS 450 may provide an application (such as a service). EAS 450 may be associated with a network address, such as an Internet Protocol address, which may be associated with a fully qualified domain name (FQDN). EASDF 425 or shared EASDF 430 may perform a DNS query (by transmitting a discovery message such as a DNS query), using the FQDN, to identify the network address of the EAS 450. EAS 450 may communicate with UE 120, such as via a UPF 420 associated with the UE 120 or a UPF 420 associated with EAS 450.”)
Regarding claim 15, the combined teachings of Tonesi and Lee taught the method of claim 1.
Tonesi further taught wherein the second function is discovered through third information of the third function. (consider paragraph 0097, specifically “The shared EASDF 430 facilitates discovery of EASs of a network to which the UE 120 does not belong. The shared EASDF 430 may enable users (such as UE 120) to connect to different home networks (such as home PLMNs (HPLMNs)) and discover EASs across the different networks. The shared EASDF may be associated with a plurality of operators, such as a plurality of mobile network operators (MNOs). In some examples, the plurality of operators may be federated. An operator, of the plurality of operators, may be capable of updating records associated with the operator on the shared EASDF 430 (such as based on a service level agreement). The plurality of operators may treat the shared EASDF 430 as a trusted external AF. A particular network, managed by a particular operator, may manage the shared EASDF 430. The particular network may be referred to as an anchor network. The anchor network may be the network that initiates sharing of the shared EASDF 430. Other EASs (such as EAS 450) may be made discoverable by the shared EASDF 430 based on configuration of the shared EASDF 430 via the anchor network. An operator of the anchor network may be referred to as an anchor operator. The anchor operator may manage the anchor network and the shared EASDF 430. Other networks, associated with other operators, may access the shared EASDF 430. In some aspects, the anchor operator may have service level agreements with the other operators such that the other operators can access the shared EASDF 430. In example 400, the anchor operator is associated with the second network (PLMN 2). As shown, the shared EASDF 430 may have connections with the EASDFs 425 and the SMFs 410.”) (consider further paragraph 0102, “EAS 450 is an application server that resides in an edge hosting environment such as an EDN. EAS 450 may provide an application (such as a service). EAS 450 may be associated with a network address, such as an Internet Protocol address, which may be associated with a fully qualified domain name (FQDN). EASDF 425 or shared EASDF 430 may perform a DNS query (by transmitting a discovery message such as a DNS query), using the FQDN, to identify the network address of the EAS 450. EAS 450 may communicate with UE 120, such as via a UPF 420 associated with the UE 120 or a UPF 420 associated with EAS 450.”) (consider further paragraph 0115, specifically “The SEASDF 625-1 and the pEASDF 625-2 may communicate with one another to facilitate discovery of the EAS 650 by the UE. For example, each of the first PLMN and the second PLMN may be associated with a respective EASDF 625. If more than two PLMNs are federated, then each of the federated PLMNs may be associated with a respective EASDF 625. The sSMF 610-1 of the first network may select the SEASDF 625-1 and the pEASDF 625-2 for discovery of the EAS 650. For example, an AF may configure a NEF or a UDR (not shown in FIG. 6 for simplicity) with filtering information. In some aspects, the filtering information may be included in EAS deployment information. The filtering information may include, for example, information indicating a PLMN of the EAS 650, information indicating a set of network addresses associated with the EAS 650 (such as a FQDN or a range of FQDNs, a set of IP addresses or a range of IP addresses associated with a data network access identifier (DNAI), a DNS server identifier associated with a DNAI, or other information).”)
Regarding claim 16, the combined teachings of Tonesi and Lee taught the method of claim 15.
Tonesi further taught wherein the third information comprises at least one of:
EAS Deployment Information (EDI); edge environment deployment information of another Public Land Mobile Network (PLMN); application information; EAS location information; third-party edge environment deployment information; a PLMN identifier; a Data Network Access Identifier (DNAI); N6 routing information; a Differentiated Services Code Point (DSCP); or a Service Level Agreement (SLA). (again, consider further paragraph 0115, specifically “The SEASDF 625-1 and the pEASDF 625-2 may communicate with one another to facilitate discovery of the EAS 650 by the UE. For example, each of the first PLMN and the second PLMN may be associated with a respective EASDF 625. If more than two PLMNs are federated, then each of the federated PLMNs may be associated with a respective EASDF 625. The sSMF 610-1 of the first network may select the SEASDF 625-1 and the pEASDF 625-2 for discovery of the EAS 650. For example, an AF may configure a NEF or a UDR (not shown in FIG. 6 for simplicity) with filtering information. In some aspects, the filtering information may be included in EAS deployment information. The filtering information may include, for example, information indicating a PLMN of the EAS 650, information indicating a set of network addresses associated with the EAS 650 (such as a FQDN or a range of FQDNs, a set of IP addresses or a range of IP addresses associated with a data network access identifier (DNAI), a DNS server identifier associated with a DNAI, or other information).”)
Regarding claim 17, the combined teachings of Tonesi and Lee taught the method of claim 15.
Tonesi further taught wherein the third information is configured by at least one of:
being pre-configured on the third function; or being configured on the third function by a fourth function. (again, consider paragraph 0097, “The shared EASDF 430 facilitates discovery of EASs of a network to which the UE 120 does not belong. The shared EASDF 430 may enable users (such as UE 120) to connect to different home networks (such as home PLMNs (HPLMNs)) and discover EASs across the different networks. The shared EASDF may be associated with a plurality of operators, such as a plurality of mobile network operators (MNOs). In some examples, the plurality of operators may be federated. An operator, of the plurality of operators, may be capable of updating records associated with the operator on the shared EASDF 430 (such as based on a service level agreement). The plurality of operators may treat the shared EASDF 430 as a trusted external AF. A particular network, managed by a particular operator, may manage the shared EASDF 430. The particular network may be referred to as an anchor network. The anchor network may be the network that initiates sharing of the shared EASDF 430. Other EASs (such as EAS 450) may be made discoverable by the shared EASDF 430 based on configuration of the shared EASDF 430 via the anchor network. An operator of the anchor network may be referred to as an anchor operator. The anchor operator may manage the anchor network and the shared EASDF 430. Other networks, associated with other operators, may access the shared EASDF 430. In some aspects, the anchor operator may have service level agreements with the other operators such that the other operators can access the shared EASDF 430. In example 400, the anchor operator is associated with the second network (PLMN 2). As shown, the shared EASDF 430 may have connections with the EASDFs 425 and the SMFs 410.”) (consider further paragraph 0115, specifically “The SEASDF 625-1 and the pEASDF 625-2 may communicate with one another to facilitate discovery of the EAS 650 by the UE. For example, each of the first PLMN and the second PLMN may be associated with a respective EASDF 625. If more than two PLMNs are federated, then each of the federated PLMNs may be associated with a respective EASDF 625. The sSMF 610-1 of the first network may select the SEASDF 625-1 and the pEASDF 625-2 for discovery of the EAS 650. For example, an AF may configure a NEF or a UDR (not shown in FIG. 6 for simplicity) with filtering information. In some aspects, the filtering information may be included in EAS deployment information. The filtering information may include, for example, information indicating a PLMN of the EAS 650, information indicating a set of network addresses associated with the EAS 650 (such as a FQDN or a range of FQDNs, a set of IP addresses or a range of IP addresses associated with a data network access identifier (DNAI), a DNS server identifier associated with a DNAI, or other information).”)
Regarding claim 18, the combined teachings of Tonesi and Lee taught the method of claim 17.
Tonesi further taught wherein the fourth function comprises at least one of:
Security Edge Protection Proxies (SEPP); a Session Management Function (SMF); a Network Exposure Function (NEF); or a NRF. (again, consider paragraph 0097, specifically “In example 400, the anchor operator is associated with the second network (PLMN 2). As shown, the shared EASDF 430 may have connections with the EASDFs 425 and the SMFs 410.”) (consider further paragraph 0115, specifically “The SEASDF 625-1 and the pEASDF 625-2 may communicate with one another to facilitate discovery of the EAS 650 by the UE. For example, each of the first PLMN and the second PLMN may be associated with a respective EASDF 625. If more than two PLMNs are federated, then each of the federated PLMNs may be associated with a respective EASDF 625. The sSMF 610-1 of the first network may select the SEASDF 625-1 and the pEASDF 625-2 for discovery of the EAS 650.”)
Regarding claim 48, Tonesi taught an Edge Application Server (EAS) search apparatus, comprising:
a transceiver, configured to send at least one of first information or second information to a second function to perform an EAS search, wherein the EAS search apparatus further comprises: a processor (consider at least paragraphs 0209 and 0212). (consider at least paragraph 0096, “The EASDF 425 facilitates discovery of EAS 450 and EASs of a network to which the EASDF 425 belongs (that is, a network with which the EASDF is associated). An EASDF 425 may be associated with a network if the EASDF 425 has discovery information (e.g., filtering information or a network address) for EASs belonging to the second network. The EASDF 425 may be configured by the SMF 410 to handle domain name system (DNS) lookup for a UE 120. For example, the SMF 410 may create and update a DNS context associated with the UE 120 for the EASDF 425. The EASDF 425 may receive a DNS query (sometimes referred to as a discovery message) from the UE 120. The EASDF 425 may refer to filtering information, configured by the SMF 410 or the AF 440, to ascertain or determine if a network address of the DNS query is associated with a shared EASDF 430 or an EASDF 425 of another network (such as the second network). The EASDF 425, or the SMF 410, may provide the DNS request to the shared EASDF 430 or the EASDF 425. The SMF 410 or the EASDF 425 may receive a DNS response and may provide the DNS response to the UE 120. The DNS response may include information for communicating with an EAS 450. Thus, the EASDF 425 may facilitate discovery of EASs in another network by the UE 120.”)
Tonesi may be interpreted as not expressly teaching wherein the processor is configured to discover the second function through a third function, wherein the third function comprises a Network Repository Function (NRF) of a network to which the first function belongs, wherein the processor is specifically configured to: request the NRF to search the second function by sending a second function discovery request to the NRF, wherein the request carries terminal location information and an application identifier.
However, in an analogous art related to EAS searches, Lee taught the use of an EAS search apparatus comprising a processor configured to discover a second function through a third function, wherein the third function comprises a Network Repository Function (NRF) of a network to which a first function belongs, wherein the processor is specifically configured to: request the NRF to search the second function by sending a second function discovery request to the NRF, wherein the request carries terminal location information and an application identifier. (consider column 19, lines 1-46, “Referring to FIG. 7, in operation 710, an NEF (EDR) 705, which processes EDR information, transmits, to an NRF 703, a registration request message for registering that the NEF (EDR) 705 is managing EAS domain configuration information. The registration request message transmitted from the NEF (EDR) 705 to the NRF 703 may include at least one of the following information. Endpoint address of NEF (EDR) 705 Differentiator for differentiating EAS domain configuration information Network and slice identifier, DNN/S-NSSAI, to provide EAS domain configuration information Name, ECAN and/or DNAI, of the data center providing EAS domain configuration information In operation 715, when the UE's PDU session is generated or changed, or when the UE moves, the SMF 701 transmits an association setup message to the EASDF 702. The association setup message transmitted from the SMF 701 to the EASDF 702 may include at least one of the following information. Information for identifying the data network and slice of UE 700 (e.g., DNN/S-NSSAI) Information for identifying UE 700 (e.g., the network address of UE 700, IPv4 address, IPv6 prefix/address, Ethernet MAC address, and/or identifier (SUPI and/or GPSI) of UE 700) List of DNAIs already connected with UE 700 through local UPF List of DNAIs connectable with UE 700 through local UPF In operation 720, the EASDF 702 discovers the address of the NEF (EDR) 705 based on information obtained through the NRF 703 or preset information. As an example, the EASDF 702 transmits a discovery request message for the NEF (EDR) 705 to the NRF 703 to discover the NEF (EDR) 705. The discovery request message transmitted from the EASDF 702 to the NRF 703 may include information about ECAN and/or DNN/S-NSSAI for discovery for the NEF (EDR) 705. In operation 725, the NRF 703 discovers the NEF (EDR) 705 storing EAS domain configuration information through information registered in operation 710. The NRF 703 transmits, to the EASDF 702, a response message including information about the endpoint address of the NEF (EDR) 705 requested for discovery by the EASDF 702, as a response to the discovery request message in operation 720.”)
It would have been obvious to one skilled in the art before the effective filing date of the claimed invention to combine the teachings of these references such that their combination includes every element as claimed. One skilled in the art could have combined the teachings by known methods such as integration of software routines with no changes to the operation of either reference such that, in combination, each element merely performs the same function as it does separately. Additionally, Examiner finds that, based on the references' analogous disclosure regarding EAS searching functionality, further demonstrates that a combination of their features would have been known and obvious. Therefore, such a combination of the teachings of the references would have yielded nothing more than predictable results to one of ordinary skill in the art.
Response to Arguments
Applicant’s arguments with respect to claim(s) 1-5, 7, 9, 11, 14-18, and 48 have been considered but are moot because the new grounds of rejection do not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument or are otherwise prompted by the instant amendments presented in the instant response.
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to G. C. Neurauter, Jr. whose telephone number is (571)272-3918. The examiner can normally be reached Monday-Friday 9am-5pm Eastern Time.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Tonia Dollinger, can be reached at 571-272-4170. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/G. C. Neurauter, Jr./Primary Examiner, Art Unit 2459
Prosecution Insights