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 .
Response to Arguments
Initially, it is noted that Applicant’s amendments to the independent claims change the number of SDK static resources present in the system from one to two. This is not merely an antecedent basis issue. The amendment from the to an results in a change of scope of the independent claims, as this change redefines how many SDK static resources are present in the claim. Therefore, any addition of new grounds of rejection based on this amendment necessitates a final rejection.
Applicant argues that Lin in view of Wang fail to teach “a first resource address and a second resource address, the first resource address points to an SDK static resource on a content delivery network (CDN) server, and the second resource address points to an SDK static resource on a source server.”
The office action cited Wang for teaching “the second resource address points to an SDK static resource on a source server.” Applicant appears to argue that the combination of Lin and Wang failed to teach “a first resource address and a second resource address, the first resource address points to an SDK static resource on a content delivery network (CDN) server, and the second resource address points to an SDK static resource on a source server.”
In response to applicant’s argument that there is no teaching, suggestion, or motivation to combine the references, the examiner recognizes that obviousness may be established by combining or modifying the teachings of the prior art to produce the claimed invention where there is some teaching, suggestion, or motivation to do so found either in the references themselves or in the knowledge generally available to one of ordinary skill in the art. See In re Fine, 837 F.2d 1071, 5 USPQ2d 1596 (Fed. Cir. 1988), In re Jones, 958 F.2d 347, 21 USPQ2d 1941 (Fed. Cir. 1992), and KSR International Co. v. Teleflex, Inc., 550 U.S. 398, 82 USPQ2d 1385 (2007). In this case, one of ordinary skill in the art is well aware of the need for a backup server in case a primary server fails for the purposes of redundancy.
In response to applicant's arguments against the references individually, one cannot show nonobviousness by attacking references individually where the rejections are based on combinations of references. See In re Keller, 642 F.2d 413, 208 USPQ 871 (CCPA 1981); In re Merck & Co., 800 F.2d 1091, 231 USPQ 375 (Fed. Cir. 1986).
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.
Claims 18-26 are rejected under 35 U.S.C. 103 as being unpatentable over Lin et al. (CN 110489276 A) in view of Wang et al. (CN 111510312 A)
In regard to claim 18, Lin disclosed a service disaster tolerance method, comprising:
sending, by a terminal device, a first request message to a service server, wherein the first request message requests a resource required for displaying a service page, the resource comprises a software development kit (SDK) static resource, and the SDK static resource is used to implement an SDK function associated with the service page; (Lin, In order to solve the above problem, the present invention provides a disaster recovery method based on verification of the service page service. in the method, the terminal wants to service page associated with access of a verification function of the third party, the background server to the third party server for verification interface resource provides the verification function by pulling. SDK (Software Development Kit, software development kit) linked to the terminal if the verification interface resource fails, background server returns the service page and with function of validating. terminal link, according to the SDK to the CDN (Content Delivery Network, content distribution network) downloaded from the server corresponding to the SDK, and invoke SDK obtaining the interface resource. The verification interface resource loading verification interface and rendering service page) and
obtaining, by the terminal device, a response message that is returned by the service server in response to the first request message, wherein the response message comprises a first resource address and a second resource address, the first resource address points to an SDK static resource on a content delivery network (CDN) server, ... (Lin, step 205, the background server sends the service page data and the SDK link to send to the terminal)
Lin failed to disclose the second resource address points to an SDK static resource on a source server. However, Wang disclosed the second resource address points to an SDK static resource on a source server. (Wang, The core network disaster-tolerant backup service recovery method and core network provided by the embodiment of the invention, through setting the routing table of the data exchange module stores and updates the downlink data route of each static UE, and periodically broadcast to the adjacent routing device for updating the downlink data link of each static UE through the user interface data interface, so as to quickly recover the communication abnormality of static UE and service server caused by gateway address change, improving the service recovery efficiency and disaster recovery capability of the system.)
It would have been obvious to one of ordinary skill in the art to have a link to a backup server in Lin in order to properly implement disaster recovery methods in Lin.
In regard to claim 19, Wang disclosed the second resource address is a standby address. (Wang, The core network disaster-tolerant backup service recovery method and core network provided by the embodiment of the invention, through setting the routing table of the data exchange module stores and updates the downlink data route of each static UE, and periodically broadcast to the adjacent routing device for updating the downlink data link of each static UE through the user interface data interface, so as to quickly recover the communication abnormality of static UE and service server caused by gateway address change, improving the service recovery efficiency and disaster recovery capability of the system.)
In regard to claim 20, Lin disclosed:
sending, by the terminal device, a second request message to the CDN server based on the first resource address, wherein the second request message requests the SDK static resource on the CDN server; (Lin, step 205, the background server sends the service page data and the SDK link to send to the terminal. step 206: the terminal said service page data receiving returned by the background server and a software development tool with function of validating packet SDK link. Step 207: the terminal The SDK link, from the content distribution network CDN server is, downloading corresponding SDK)
receiving, by the terminal device, a response message that is sent by the CDN server in response to the second request message; (Lin, step 205, the background server sends the service page data and the SDK link to send to the terminal. step 206: the terminal said service page data receiving returned by the background server and a software development tool with function of validating packet SDK link. Step 207: the terminal The SDK link, from the content distribution network CDN server is, downloading corresponding SDK)
if the response message comprises request failure information:
sending, by the terminal device, a third request message to the source server based on the second resource address, wherein the third request message requests the SDK static resource on the source server; (Lin, when the third party server downtime or verification function provides a function of validating the third party is not available, also according to the SDK link, downloading the corresponding SDK from a CDN server, and finishing the verification function of the third party, so that the user can normally access service page.) and
receiving, by the terminal device, a response message that is sent by the source server in response to the third request message, wherein the response message of the third request message comprises the SDK static resource. (Lin, when the third party server downtime or verification function provides a function of validating the third party is not available, also according to the SDK link, downloading the corresponding SDK from a CDN server, and finishing the verification function of the third party, so that the user can normally access service page.)
In regard to claim 21, Lin disclosed a service disaster tolerance method, comprising:
receiving, by an SDK server, a fourth request message sent by a service server, (Lin, receiving a request of session access service page sent by the terminal) wherein the fourth request message requests an SDK static resource, and the SDK static resource can be used to implement an SDK function associated with a service page; (Lin, the said service page data and link sending the SDK to the terminal so that the terminal according to the service generating the service page of the page data, and according to the obtained the SDK link SDK and transferring the SDK obtains the verification interface resource and loading the verification interface to the service page, the SDK for completing the authentication function.) and
returning, by the SDK server, a response message to the service server in response to the fourth request message, wherein the response message comprises a first resource address … the first resource address points to an SDK static resource on a CDN server... (Lin, step 205, the background server sends the service page data and the SDK link to send to the terminal)
Lin failed to disclose the second resource address points to an SDK static resource on a source server. However, Wang disclosed the second resource address points to an SDK static resource on a source server. (Wang, The core network disaster-tolerant backup service recovery method and core network provided by the embodiment of the invention, through setting the routing table of the data exchange module stores and updates the downlink data route of each static UE, and periodically broadcast to the adjacent routing device for updating the downlink data link of each static UE through the user interface data interface, so as to quickly recover the communication abnormality of static UE and service server caused by gateway address change, improving the service recovery efficiency and disaster recovery capability of the system.)
It would have been obvious to one of ordinary skill in the art to have a link to a backup server in Lin in order to properly implement disaster recovery methods in Lin.
In regard to claim 22, Wang disclosed the second resource address is a standby address. (Wang, The core network disaster-tolerant backup service recovery method and core network provided by the embodiment of the invention, through setting the routing table of the data exchange module stores and updates the downlink data route of each static UE, and periodically broadcast to the adjacent routing device for updating the downlink data link of each static UE through the user interface data interface, so as to quickly recover the communication abnormality of static UE and service server caused by gateway address change, improving the service recovery efficiency and disaster recovery capability of the system.)
In regard to claim 23, Wang disclosed: updating, by the SDK server, the first resource address or the second resource address. (Wang, periodically broadcast to the adjacent routing device for updating the downlink data link of each static UE through the user interface data interface)
Claim 24 is rejected for substantially the same reasons as claim 18.
Claim 25 is rejected for substantially the same reasons as claim 19.
Claim 26 is rejected for substantially the same reasons as claim 20.
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 Jeffrey R. Swearingen whose telephone number is (571)272-3921. The examiner can normally be reached M-F 8:00 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, Oscar Louie can be reached at 571-270-1684. 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.
Jeffrey R. Swearingen
Primary Examiner
Art Unit 2445
/Jeffrey R Swearingen/Primary Examiner, Art Unit 2445
Prosecution Insights