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 9, 13, 15-18, 44, 46, and 62 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.
Claim 13, dependent from claim 1, recites “discovering the second function through at least one of an eighth function or a ninth function”. However, there are no intervening “third”, “fourth”, “fifth”, “sixth”, or “seventh” “functions”. Therefore, to enumerate these elements sequentially without properly reciting the intervening elements is unclear since it is not clear whether these elements are actually recited.
The same is applied to claim 15, dependent from claim 13, which recites “fourth information of the eighth function”. There is no “third information” required, therefore, it is unclear whether it is included or excluded from the claimed language.
The same is applied to claim 16, dependent from claim 15, which recites “the fourth information”. There is no “third information” required, therefore, it is unclear whether it is included or excluded from the claimed language.
The same is applied to claim 17, dependent from claim 15, which recites “the fourth information”, “the eighth function” and “a tenth function”.
The same is applied to claim 18, dependent from claim 17, which recites “the tenth function”.
The same is applied to claim 44, an independent claim, which recites “an eleventh function” and then later recites a “third function” and then even later a “first function”. This discontinuous introduction of enumerated elements is also unclear.
The same is applied to claim 46, dependent from claim 44, which recites “the third function”.
The same is applied to claim 62, an independent claim and references claim 44 to which all limitations are imported, which recites “a fifth processor” and “a fifth memory”. It also recites “an eleventh function” which is unclear as to whether it refers to the “eleventh function” recited in imported claim 44.
Claim 9 recites “being configured with third information”. It is unclear what element in the claim is “being configured”.
Claim Rejections - 35 USC § 102
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 the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 1-5, 7, 9, 11, 13-18, 44-48, and 62 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by US 20250030774 A1 to Tonesi et al. (“Tonesi”).
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.”)
Regarding claim 2, Tonesi taught the method of claim 1, further comprising at least one of:
acquiring the first information from a third function; or acquiring the second information from a fourth 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, Tonesi taught the method of claim 1, 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, Tonesi taught the method of claim 1, 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, Tonesi taught the method of claim 2, wherein the third 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, Tonesi taught the method of claim 1, 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, Tonesi taught the method of claim 1, further comprising:
being 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, Tonesi taught the method of claim 1, 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 fifth function or a sixth function, the fifth function is used to control and manage traffic in a first Public Land Mobile Network (PLMN), and the sixth 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 13, Tonesi taught the method of claim 1, further comprising:
discovering the second function through at least one of an eighth function or a ninth function. (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.”) (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 14, Tonesi taught the method of claim 13, 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, Tonesi taught the method of claim 13, wherein the second function is discovered through fourth information of the eighth 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, Tonesi taught the method of claim 15, wherein the fourth 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, Tonesi taught the method of claim 15, wherein the fourth information is configured by at least one of:
being configured on the eighth function by a tenth 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, Tonesi taught the method of claim 17, wherein the tenth function comprises at least one of:
Security Edge Protection Proxies (SEPP); a Session Management Function (SMF); a Network Exposure Function (NEF); or a Network Repository Function (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 44, Tonesi taught an Edge Application Server (EAS) search method, applied to an eleventh function, comprising:
acquiring a first indication, wherein the first indication is used to select a third function, and the third function is used to provide first information to a first function to perform an EAS search. (consider paragraphs 00026-0027, specifically “The method may include selecting a unified data repository associated with a first network. The method may include transmitting, to the unified data repository, EAS deployment information including at least one of a public land mobile network (PLMN) identifier associated with a second network having an EAS or filtering information indicating a network address associated with the EAS. In some implementations, the EAS deployment information is usable by a session management function for configuring an EAS discovery function of the first network to discover the EAS or an EAS discovery function of the second network.”) (consider further paragraph 0054, “In some cases, ECSPs may share edge computing resources (such as EDNs) with one another. For example, a first ECSP and a second ECSP may share edge computing resources. If the first ECSP and the second ECSP share edge computing resources, a UE associated with the first ECSP may be capable of accessing the first ECSP's edge computing resources and the second ECSP's edge computing resources. Sharing of edge computing resources may be facilitated by cross-ECSP discovery of resources across operators. For example, an ECSP may discover edge computing resources available with a partner ECSP associated with a different operator. Furthermore, an ECSP with resources on another network (for example, a visited network) may provide information regarding a partner ECSP's services to a UE roaming to the other network.”) (consider further paragraph 0106, specifically “In some aspects, the SMF 502 may receive the filtering information. For example, the SMF 502 may obtain the filtering information from a network exposure function (NEF) or a unified data repository (UDR) (not shown in FIG. 5 for simplicity). A UDR is a database that stores subscription-related data, such as subscription data, policy data, structured data for exposure, and application data.”)
Regarding claim 45, Tonesi taught the method of claim 44, wherein acquiring the first indication comprises at least one of: acquiring the first indication in a terminal registration process; or acquiring the first indication from Unified Data Management (UDM). (again, consider paragraphs 00026-0027, specifically “The method may include selecting a unified data repository associated with a first network. The method may include transmitting, to the unified data repository, EAS deployment information including at least one of a public land mobile network (PLMN) identifier associated with a second network having an EAS or filtering information indicating a network address associated with the EAS. In some implementations, the EAS deployment information is usable by a session management function for configuring an EAS discovery function of the first network to discover the EAS or an EAS discovery function of the second network.”) (again, consider further paragraph 0054, “In some cases, ECSPs may share edge computing resources (such as EDNs) with one another. For example, a first ECSP and a second ECSP may share edge computing resources. If the first ECSP and the second ECSP share edge computing resources, a UE associated with the first ECSP may be capable of accessing the first ECSP's edge computing resources and the second ECSP's edge computing resources. Sharing of edge computing resources may be facilitated by cross-ECSP discovery of resources across operators. For example, an ECSP may discover edge computing resources available with a partner ECSP associated with a different operator. Furthermore, an ECSP with resources on another network (for example, a visited network) may provide information regarding a partner ECSP's services to a UE roaming to the other network.”) (again, consider further paragraph 0106, specifically “In some aspects, the SMF 502 may receive the filtering information. For example, the SMF 502 may obtain the filtering information from a network exposure function (NEF) or a unified data repository (UDR) (not shown in FIG. 5 for simplicity). A UDR is a database that stores subscription-related data, such as subscription data, policy data, structured data for exposure, and application data.”)
Regarding claim 46, Tonesi taught the method of claim 44, further comprising at least one of: acquiring the first indication from the third function in a session creation process; selecting the third function according to the first indication; or reselecting the third function according to the first indication. (consider paragraph 0103-0104, specifically “A UL CL is a functionality supported by a UPF 504 that can apply a matching traffic filter provided by an SMF 502. For example, the SMF 502 may insert, into the data path of a PDU session, a UPF 504 supporting the UL CL functionality during or after PDU session establishment. The PSA is the anchor of the PDU session. The anchor of the PDU session is the end point to the data network. If a local UPF is added (such as a UL CL or IPv6 multi-homing BP), the traffic through the local UPF may go through a local PSA UPF, which is the end point to the local data network (in this case, the EDN). The local PSA UPF may be connected to the UL CL or the IPV6 multi-homing branching point. [0104] As shown in example 500, and by reference number 512, the UE and the SMF 502 may perform a PDU session establishment procedure. For example, the UE and the SMF may exchange signaling such that the UE establishes a PDU session with the SMF 502. As shown by reference number 514, the SMF 502 may select an EASDF. For example, the SMF may select the serving EASDF 506 to serve as a serving EASDF of the UE. Acting as a serving EASDF may entail the serving EASDF 506 handling DNS queries of the UE, such as with regard to the shared EASDF 508.”)
Regarding claim 47, Tonesi taught the method of claim 44, wherein the first indication indicates that at least one of a terminal or a session supports EAS access across operator networks. (again, consider further paragraph 0054, “In some cases, ECSPs may share edge computing resources (such as EDNs) with one another. For example, a first ECSP and a second ECSP may share edge computing resources. If the first ECSP and the second ECSP share edge computing resources, a UE associated with the first ECSP may be capable of accessing the first ECSP's edge computing resources and the second ECSP's edge computing resources. Sharing of edge computing resources may be facilitated by cross-ECSP discovery of resources across operators. For example, an ECSP may discover edge computing resources available with a partner ECSP associated with a different operator. Furthermore, an ECSP with resources on another network (for example, a visited network) may provide information regarding a partner ECSP's services to a UE roaming to the other network.”)
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. (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.”)
Regarding claim 62, Tonesi taught an eleventh function, comprising a fifth processor and a fifth memory configured to store a computer program runnable on a processor, wherein the fifth processor is configured to, when running the computer program, perform operations of the method of claim 44. (consider paragraphs 00026-0027, specifically “The method may include selecting a unified data repository associated with a first network. The method may include transmitting, to the unified data repository, EAS deployment information including at least one of a public land mobile network (PLMN) identifier associated with a second network having an EAS or filtering information indicating a network address associated with the EAS. In some implementations, the EAS deployment information is usable by a session management function for configuring an EAS discovery function of the first network to discover the EAS or an EAS discovery function of the second network.”) (consider further paragraph 0054, “In some cases, ECSPs may share edge computing resources (such as EDNs) with one another. For example, a first ECSP and a second ECSP may share edge computing resources. If the first ECSP and the second ECSP share edge computing resources, a UE associated with the first ECSP may be capable of accessing the first ECSP's edge computing resources and the second ECSP's edge computing resources. Sharing of edge computing resources may be facilitated by cross-ECSP discovery of resources across operators. For example, an ECSP may discover edge computing resources available with a partner ECSP associated with a different operator. Furthermore, an ECSP with resources on another network (for example, a visited network) may provide information regarding a partner ECSP's services to a UE roaming to the other network.”) (consider further paragraph 0106, specifically “In some aspects, the SMF 502 may receive the filtering information. For example, the SMF 502 may obtain the filtering information from a network exposure function (NEF) or a unified data repository (UDR) (not shown in FIG. 5 for simplicity). A UDR is a database that stores subscription-related data, such as subscription data, policy data, structured data for exposure, and application data.”)
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. The cited prior art is directed to EAS search and discovery methodologies.
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