DETAILED ACTION
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 § 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 non-obviousness.
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.
Claims 22-41 are rejected under U.S.C. 103 as being unpatentable by 3GPP (3GPP TR 23.758 V0.3.0 (2019-07), hereinafter 3GPP) in view of Liu et al. (US 12587592 B2, hereinafter Liu).
Consider Claim 22, 3GPP discloses the method comprising: transmitting an edge application server (EAS) discovery request to an edge data network (EDN), wherein the EAS discovery request comprises one or more EAS requirements; (Section 7.1.1 page 18 step 2, the Edge Enabler Client sends an Edge Application Server discovery request to the Edge Enabler Server. The discovery request may contain query filters).
receiving an EAS discovery response from the EDN, the EAS discovery response including a list of one or more EASs associated with an un-instantiated application that meets the one or more EAS requirements; (Section 7.1.1 page 18 step 4, the Edge Enabler Server retrieves the information of Edge Application Servers. The information includes a list of FQDN(s) along with a mapping to the IP address(es) of the Edge Application Servers running on the Edge Hosting Platforms in the Edge Data Network. For Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information. Further, the Edge Enabler Server applies any discovery policies or filters, including the filters received in the Edge Application Server discovery request to the retrieved information).
selecting an EAS from the list of one or more EASs; transmitting an EAS instantiation request to the EDN, the EAS instantiation request indicating the selected EAS; and (Section 7.1.1 page 18 step 6, upon receiving the Edge Application Server discovery response, the Edge Enabler Client uses the FQDN and/or IP address mapping to resolve the domain name requested by the Application Client for routing the outgoing application data traffic).
receiving an EAS instantiation response from the EDN, the EAS instantiation response indicating that the selected EAS has been instantiated at the EDN, wherein the EAS instantiation response comprises instantiation information associated with the selected EAS. (Section 7.1.1 page 17 line 3-6, the Edge Enabler Server allows the Edge Enabler Client to discover both, the Edge Application Servers running on the Edge Hosting Platform within the Edge Data Network and the Edge Application Servers which can be instantiated on the Edge Hosting Platform within the Edge Data Network. The Edge Enabler Server employs authorization checks and discovery filters and provide requested information to the Edge Enabler Client).
3GPP discloses the claimed invention but fails to teach a method implemented by a wireless transmit/receive unit (WTRU).
However, Liu teaches a method implemented by a wireless transmit/receive unit (WTRU), (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 22 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 23, 3GPP discloses the method of claim 22, wherein the instantiation information indicates whether the selected EAS has been synchronously instantiated or asynchronously instantiated. (Section 7.1.1 page 17 line 3-6, the Edge Enabler Server allows the Edge Enabler Client to discover both, the Edge Application Servers running on the Edge Hosting Platform within the Edge Data Network and the Edge Application Servers which can be instantiated on the Edge Hosting Platform within the Edge Data Network. The Edge Enabler Server employs authorization checks and discovery filters and provide requested information to the Edge Enabler Client).
Consider Claim 24, 3GPP discloses the method of claim 23, wherein the instantiation information indicates that the selected EAS has been synchronously instantiated, and the EAS instantiation response comprises EAS information associated with the selected EAS. (Section 7.1.1 page 18 step 4 & 6, for Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information. Further, the Edge Enabler Server applies any discovery policies or filters, including the filters received in the Edge Application Server discovery request to the retrieved information. Edge Enabler Client uses the FQDN and/or IP address mapping to resolve the domain name requested by the Application Client for routing the outgoing application data traffic and direct it to the instantiated Edge Application Server(s) in the Edge Data Network, as required).
Consider Claim 25, 3GPP discloses the method of claim 22, wherein the EAS instantiation response comprises an Internet Protocol (IP) address, fully qualified domain name (FQDN), or uniform resource locator (URL) of the selected EAS. (Section 7.1.1 page 18 step 6, upon receiving the Edge Application Server discovery response, the Edge Enabler Client uses the FQDN and/or IP address mapping to resolve the domain name requested by the Application Client for routing the outgoing application data traffic and direct it to the instantiated Edge Application Server(s) in the Edge Data Network, as required).
Consider Claim 26, 3GPP discloses the method of claim 25, wherein an application client (AC) residing on a unit accesses the selected EAS based on the IP address. (Section 7.1.1 page 18 step 4, the Edge Enabler Server retrieves the information of Edge Application Servers. The information includes a list of FQDN(s) along with a mapping to the IP address(es) of the Edge Application Servers running on the Edge Hosting Platforms in the Edge Data Network. For Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information. Further, the Edge Enabler Server applies any discovery policies or filters, including the filters received in the Edge Application Server discovery request to the retrieved information) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 26 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 27, 3GPP discloses the method of claim 22 further comprising: selecting, by an edge enabler client (EEC) residing on a unit the EAS from the list of one or more EASs. (Section 7.1.1 page 18 step 4, the Edge Enabler Server retrieves the information of Edge Application Servers. The information includes a list of FQDN(s) along with a mapping to the IP address(es) of the Edge Application Servers running on the Edge Hosting Platforms in the Edge Data Network. For Edge Application Servers that are available but not instantiated) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 27 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 28, 3GPP discloses the method of claim 22, wherein the EAS discovery request comprises one or more application client (AC) identifiers and EAS selection filters. (Section 7.1.1 page 18 step 4, for Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information. Further, the Edge Enabler Server applies any discovery policies or filters, including the filters received in the Edge Application Server discovery request to the retrieved information).
Consider Claim 29, 3GPP discloses the method of claim 22, wherein the EAS instantiation request comprises one or more of requester identifier, a unit identifier, security credentials, a unit location, requested service continuity (SC) support, requested SC planning, EAS characteristics, or EAS instantiation information. (Section 7.1.1 page 17 line 3-6, the Edge Enabler Server allows the Edge Enabler Client to discover both, the Edge Application Servers running on the Edge Hosting Platform within the Edge Data Network and the Edge Application Servers which can be instantiated on the Edge Hosting Platform within the Edge Data Network. The Edge Enabler Server employs authorization checks and discovery filters and provide requested information to the Edge Enabler Client) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 29 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 30, 3GPP discloses the method of claim 22, wherein the EAS receives the instantiation response from the EDN via a domain name system (DNS) response, an application programming interface (API) response, a function call return value, or an operating system (OS) call response. (Section 7.5.1 page 26 line 4-7, the Edge Enabler Server exposes UE Identifier API to the Edge Application in order to provide valid UE identifier for the capability exposure API(s) over EDGE-3. This API enables Edge Application to point to a user anonymously over different service API(s) exposed by the Edge Enabler Server. The UE Identifier provided by the UE Identifier API is called as Edge UE ID in this solution. The Edge Application uses Edge UE ID to identify the UE for service API(s). (Section 7.1.1 page 18 step 6, the domain name requested by the Application Client for routing the outgoing application data traffic and direct it to the instantiated Edge Application Server(s) in the Edge Data Network, as required).
Consider Claim 31, 3GPP discloses the method of claim 22, wherein the EAS discovery request comprises one or more of application usage, a unit platform state, or connectivity conditions. (Section 7.1.1 page 18 step 4, the Edge Application Servers running on the Edge Hosting Platforms in the Edge Data Network. For Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information. Further, the Edge Enabler Server applies any discovery policies or filters, including the filters received in the Edge Application Server discovery request to the retrieved information. Section 7.1.1 page 18 step 4establishment of PDU Session or PDN connectivity to the Edge Data Network, connecting to the Edge Enabler Sever for the first time, expiry of a periodic timer, entering or exiting a geographic area (i.e. Edge Data Network service area) etc., or a combination of configured trigger conditions met at the Edge Enabler Client) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 31 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 32, 3GPP discloses the processor configured to:
transmit an edge application server (EAS) discovery request to an edge data network (EDN), wherein the EAS discovery request comprises one or more EAS requirements; (Section 7.1.1 page 18 step 2, the Edge Enabler Client sends an Edge Application Server discovery request to the Edge Enabler Server. The discovery request may contain query filters).
receive an EAS discovery response from the EDN, the EAS discovery response including a list of one or more EASs associated with an un-instantiated application that meets the one or more EAS requirements; (Section 7.1.1 page 18 step 4, the Edge Enabler Server retrieves the information of Edge Application Servers. The information includes a list of FQDN(s) along with a mapping to the IP address(es) of the Edge Application Servers running on the Edge Hosting Platforms in the Edge Data Network. For Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information. Further, the Edge Enabler Server applies any discovery policies or filters, including the filters received in the Edge Application Server discovery request to the retrieved information).
select an EAS from the list of one or more EASs; transmitting an EAS instantiation request to the EDN, the EAS instantiation request indicating the selected EAS; and (Section 7.1.1 page 18 step 6, upon receiving the Edge Application Server discovery response, the Edge Enabler Client uses the FQDN and/or IP address mapping to resolve the domain name requested by the Application Client for routing the outgoing application data traffic).
receive an EAS instantiation response from the EDN, the EAS instantiation response indicating that the selected EAS has been instantiated at the EDN, wherein the EAS instantiation response comprises instantiation information associated with the selected EAS. (Section 7.1.1 page 17 line 3-6, the Edge Enabler Server allows the Edge Enabler Client to discover both, the Edge Application Servers running on the Edge Hosting Platform within the Edge Data Network and the Edge Application Servers which can be instantiated on the Edge Hosting Platform within the Edge Data Network. The Edge Enabler Server employs authorization checks and discovery filters and provide requested information to the Edge Enabler Client).
3GPP discloses the claimed invention but fails to teach a wireless transmit/receive unit (WTRU) comprising a processor and a memory.
However, Liu teaches a wireless transmit/receive unit (WTRU) comprising a processor and a memory, (paragraph 270, WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, non-removable memory 130, removable memory).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 32 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 33, 3GPP discloses a unit, wherein the instantiation information indicates whether the selected EAS has been synchronously instantiated or asynchronously instantiated. (Section 7.1.1 page 17 line 3-6, the Edge Enabler Server allows the Edge Enabler Client to discover both, the Edge Application Servers running on the Edge Hosting Platform within the Edge Data Network and the Edge Application Servers which can be instantiated on the Edge Hosting Platform within the Edge Data Network. The Edge Enabler Server employs authorization checks and discovery filters and provide requested information to the Edge Enabler Client) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 33 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 34, 3GPP discloses a unit, wherein the instantiation information indicates that the selected EAS has been synchronously instantiated, and the EAS instantiation response comprises EAS information associated with the selected EAS. (Section 7.1.1 page 18 step 4 & 6, for Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information. Further, the Edge Enabler Server applies any discovery policies or filters, including the filters received in the Edge Application Server discovery request to the retrieved information. Edge Enabler Client uses the FQDN and/or IP address mapping to resolve the domain name requested by the Application Client for routing the outgoing application data traffic and direct it to the instantiated Edge Application Server(s) in the Edge Data Network, as required) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 34 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 35, 3GPP discloses a unit, wherein the EAS instantiation response comprises an Internet Protocol (IP) address, fully qualified domain name (FQDN), or uniform resource locator (URL) of the selected EAS. (Section 7.1.1 page 18 step 6, upon receiving the Edge Application Server discovery response, the Edge Enabler Client uses the FQDN and/or IP address mapping to resolve the domain name requested by the Application Client for routing the outgoing application data traffic and direct it to the instantiated Edge Application Server(s) in the Edge Data Network, as required) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 35 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 36, 3GPP discloses a unit, wherein an application client (AC) residing on a unit accesses the selected EAS based on the IP address. (Section 7.1.1 page 18 step 4, the Edge Enabler Server retrieves the information of Edge Application Servers. The information includes a list of FQDN(s) along with a mapping to the IP address(es) of the Edge Application Servers running on the Edge Hosting Platforms in the Edge Data Network. For Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information. Further, the Edge Enabler Server applies any discovery policies or filters, including the filters received in the Edge Application Server discovery request to the retrieved information) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 36 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 37, 3GPP discloses a unit, further configured to: select, by an edge enabler client (EEC) residing on a unit the EAS from the list of one or more EASs. (Section 7.1.1 page 18 step 4, the Edge Enabler Server retrieves the information of Edge Application Servers. The information includes a list of FQDN(s) along with a mapping to the IP address(es) of the Edge Application Servers running on the Edge Hosting Platforms in the Edge Data Network. For Edge Application Servers that are available but not instantiated) but fails to teach the WTRU and processor.
However, Liu teaches a wireless transmit/receive unit (WTRU) comprising a processor and a memory, (paragraph 270, WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, non-removable memory 130, removable memory).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 37 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 38, 3GPP discloses a unit wherein the EAS discovery request comprises one or more application client (AC) identifiers and EAS selection filters. (Section 7.1.1 page 18 step 4, for Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information. Further, the Edge Enabler Server applies any discovery policies or filters, including the filters received in the Edge Application Server discovery request to the retrieved information) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 38 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 39, 3GPP discloses a unit, wherein the EAS instantiation request comprises one or more of requester identifier, a unit identifier, security credentials, a unit location, requested service continuity (SC) support, requested SC planning, EAS characteristics, or EAS instantiation information. (Section 7.1.1 page 17 line 3-6, the Edge Enabler Server allows the Edge Enabler Client to discover both, the Edge Application Servers running on the Edge Hosting Platform within the Edge Data Network and the Edge Application Servers which can be instantiated on the Edge Hosting Platform within the Edge Data Network. The Edge Enabler Server employs authorization checks and discovery filters and provide requested information to the Edge Enabler Client) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 39 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 40, 3GPP discloses a unit, wherein the EAS receives the instantiation response from the EDN via a domain name system (DNS) response, an application programming interface (API) response, a function call return value, or an operating system (OS) call response. (Section 7.5.1 page 26 line 4-7, the Edge Enabler Server exposes UE Identifier API to the Edge Application in order to provide valid UE identifier for the capability exposure API(s) over EDGE-3. This API enables Edge Application to point to a user anonymously over different service API(s) exposed by the Edge Enabler Server. The UE Identifier provided by the UE Identifier API is called as Edge UE ID in this solution. The Edge Application uses Edge UE ID to identify the UE for service API(s). (Section 7.1.1 page 18 step 6, the domain name requested by the Application Client for routing the outgoing application data traffic and direct it to the instantiated Edge Application Server(s) in the Edge Data Network, as required) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 40 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Consider Claim 41, 3GPP discloses a unit, wherein the EAS discovery request comprises one or more of application usage, a unit platform state, or connectivity conditions. (Section 7.1.1 page 18 step 4, the Edge Application Servers running on the Edge Hosting Platforms in the Edge Data Network. For Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information. Further, the Edge Enabler Server applies any discovery policies or filters, including the filters received in the Edge Application Server discovery request to the retrieved information. Section 7.1.1 page 18 step 4establishment of PDU Session or PDN connectivity to the Edge Data Network, connecting to the Edge Enabler Sever for the first time, expiry of a periodic timer, entering or exiting a geographic area (i.e. Edge Data Network service area) etc., or a combination of configured trigger conditions met at the Edge Enabler Client) but fails to teach the WTRU.
However, Liu discloses the WTRU, (Col 31 Lines 37-38 (paragraph 213), the communications system 100 may include wireless transmit/receive units (WTRUs).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which said subject matter pertains, to modify Claim 41 by incorporating/combining the teachings of 3GPP “Study on application architecture for enabling Edge” with the enhance edge application relocation wireless system of Liu. The motivation to do so would be to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
Response to Arguments
Applicant's arguments filed June 30, 2026 have been fully considered but they are not persuasive.
With regards to Applicant’s arguments (page 6 and 7) that cited reference 3GPP does not “teach of any such selection,” Examiner respectfully disagrees. 3GPP does in fact show the process of selection 3GPP teaches (Section 7.1.1 page 18 step 6, upon receiving the Edge Application Server discovery response, the Edge Enabler Client uses the FQDN and/or IP address mapping to resolve the domain name requested by the Application Client for routing the outgoing application data traffic),consequently in order for routing to be performed there must be a selection of data traffic.
With regards to Applicant’s arguments (page 6 and 7) that cited reference 3GPP does not “make no mention of an EAS instantiation request to the EDN,” Examiner respectfully disagrees. The cited reference 3GPP discloses a request to a (ED) from a EAS 3GPP teaches (Section 7.1.1 page 18 step 2, the Edge Enabler Client sends an Edge Application Server discovery request to the Edge Enabler Server. The discovery request may contain query filters). In addition, 3GPP discloses “un-instantiated EAS” teaches a (Section 7.1.1 page 18 step 4, the Edge Enabler Server retrieves the information of Edge Application Servers. The information includes a list of FQDN(s) along with a mapping to the IP address(es) of the Edge Application Servers running on the Edge Hosting Platforms in the Edge Data Network. For Edge Application Servers that are available but not instantiated, the Edge Enabler Server includes relevant information).
With regards to Applicant’s argument (page 7) that citied reference “Liu fails to cure the defects of 3GPP,” Examiner respectfully disagrees. The motivation to incorporate cited reference 3GPP with reference Liu is to develop a complete way to solve the problem of coupling EAS discovery with EAS instantiation causing unnecessary EAS instantiation and wastage of compute resources. Thus, enabling a wireless transmit/receive unit (WTRU)-based edge compute autoscaling to be fully implemented by WTRU edge communication system.
In as such Examiner respectfully rejects independent claims 22 and 32. In addition, depended claims 23-31 and 33-41, which depends therefrom independent claims 22 and 32 are also rejected by virtue of their dependence.
As a result, the claims are written such that they read upon the cited reference.
Conclusion
THIS ACTION IS MADE FINAL. 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 MICHELE CAMILLE DOUGLAS whose telephone number is (571)270-0458. The examiner can normally be reached Monday - Friday 6:30 am - 5:00 pm.
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, Jeanette J Parker can be reached at 571-270-3647. 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.
/MICHELE C DOUGLAS/Examiner, Art Unit 2646
/ABDERRAHIM MEROUAN/ Supervisory Patent Examiner, Art Unit 2683
Prosecution Insights