Patent Application 18172841 - SYSTEMS AND METHODS FOR PROVIDING INSTANT - Rejection

Patent Application 18172841 - SYSTEMS AND METHODS FOR PROVIDING INSTANT

Title: SYSTEMS AND METHODS FOR PROVIDING INSTANT PROVISIONING AND ACTIVATION OF A CLIENT DEVICE FOR A NETWORK

Application Information

• Invention Title: SYSTEMS AND METHODS FOR PROVIDING INSTANT PROVISIONING AND ACTIVATION OF A CLIENT DEVICE FOR A NETWORK
• Application Number: 18172841
• Submission Date: 2025-05-15T00:00:00.000Z
• Effective Filing Date: 2023-02-22T00:00:00.000Z
• Filing Date: 2023-02-22T00:00:00.000Z
• National Class: 709
• National Sub-Class: 229000
• Examiner Employee Number: 79426
• Art Unit: 2446
• Tech Center: 2400

Rejection Summary

• 102 Rejections: 0
• 103 Rejections: 2

Cited Patents

The following patents were cited in the rejection:

• US 0284301🔗
• US 0181419🔗
• US 2727952🔗
• US 0160253🔗

Office Action Text

    DETAILED ACTION

Claims 1-20 are presented for consideration.

Claim Rejections - 35 USC § 103

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.

2.	Claim(s) 1-5, 8-11, and 13-20 are rejected under 35 U.S.C. 103 as being unpatentable over Ahluwalla et al. [ US Patent Application No 2018/0160253 ], in view of Cui et al. [ US Patent Application No 2023/0284301 ], and further in view of Mistry et al. [ US Patent Application No 2015/0181419 ].

3.	As per claim 1, Ahluwalla discloses the invention as claimed including a method, comprising:
receiving, by a device, a request for provisioning and activating a client device for a network [ i.e. receive OTA message from UE ] [ paragraphs 0034, 0044, and 0045 ]; 
extracting, by the device, one or more key attributes from the request [ i.e. class 2 is phase 2-specifica nd caries SIM/UICC data ] [ paragraph 0044 ]; 
determining, by the device and based on the one or more key attributes, a type of device corresponding to the client device or a type of service requested by the client device [ i.e. SIM card and UICC contain unique information that identifies a UE to a wireless communication network with which enables the UE to operate ] [ Figures 4, and 5; and paragraphs 0031-0033, and 0040-0042 ] ;
determining, by the device, whether the type of device or the type of service is associated with provisioning and activating the client device using a first process; and provisioning, by the device, the network for the client device, and activating the client device using the first process based on determining that the type of device or the type of service is associated with provisioning and activating the client device using the first process [ i.e. register the SIM card or UICC and the MTC capability information can be employed by one or more provisioning servers to facilitate provisioning MTC services for the respective UEs ] [ 216, Figure 2; paragraphs 0027, 0030, and 0031 ].
Ahluwalla does not specifically disclose 
wherein provisioning the network for the client device, and activating the client device performed using a second process that is different from the first process, when the type of device or the type of service is not associated with provisioning and activating the device using the first process. 
	Cui discloses
wherein provisioning the network for the client device, and activating the client device performed using a second process that is different from the first process, when the type of device or the type of service is not associated with provisioning and activating the device using the first process [ i.e. select to assign the UE to the second type of mobile cellular architecture ] [ 263, 208, Figure 2D; and paragraphs 0040, 0042, and 0075 ].
	It would have been obvious to a person skill in the art before the effective filing date of the claimed invention to combine the teaching of Ahluwalla and Cui because the teaching of Cui would enable to provide advanced control functionality adapted to deliver increased efficiency and better radio resource management [ Cui, paragraph 0058 ].
	Ahluwalla in view of Cui does not specifically disclose
	wherein one or more real-time synchronous application programming interfaces are utilized to provision the network for the client device and activate the client device.
	Mistry discloses
wherein one or more real-time synchronous application programming interfaces are utilized to provision the network for the client device and activate the client device [ i.e. EAS server supports the self-activation procedure by receiving messages via the EAS API from the mobile device and by sending messages via the EAS API to the mobile device ] [ paragraphs 0023, 0029, and 0064 ]. 
It would have been obvious to a person skill in the art before the effective filing date of the claimed invention to combine the teaching of Ahluwalla, Cui and Mistry because the teaching of Mishra would configure to limit access prior to full activation to communications with only the one or more carrier systems supporting the self-activation service [ Mishra, paragraph 0012 ].


4.	As per claim 2, Ahluwalla, in view of Cui and Mistry discloses the method of claim 1, furthermore, Ahluwalla discloses identifying one or more network elements, of the network, to be provisioned based on the request [ i.e. provision server or billing/records server ] [ paragraph 0030 ], and Mistry discloses generating one or more provisioning commands and one or more activation commands for the one or more network elements based on the request; provisioning the one or more network elements with the one or more provisioning commands; and activating the client device based on the one or more activation commands and in near- real-time relative to receiving the request  [ i.e. based on this request, the billing system sends corresponding provisioning codes to provisioning system with an indicator that the activation request is self-activation ] [ Figure 4; and paragraphs 0067 and 0068 ].

5.	As per claim 3, Mistry discloses receiving a response indicating that the client device is activated [ i.e. communicating to the user that activation is complete ] [ Abstract; and paragraph 0016 ]. 

6.	As per claim 4, Ahluwalla discloses wherein the client device is activated to utilize the one or more network elements of the network [ i.e. provisioning MTC servers for the respective UE ] [ paragraph 0027 ]. 

7.	As per claim 5, Ahluwalla discloses wherein the client device is one of a low latency device or an Internet of Things security monitoring device [ paragraphs 0021, and 0032 ]. 

8.	As per claim 8, it is rejected for similar reasons as stated above in claim 1.

9.	As per claim 9, Ahluwalla in view of Cui, and Mistry discloses the device of claim 8, furthermore, Ahluwalla discloses identify one or more first network elements, of the network, to be provisioned based on the request [ i.e. provisioning server ]; identify one or more second network elements, of the network, to be provisioned based on the request [ i.e. billing/records server ] [ Figure 2; and paragraphs 0029, and 0030 ]; provision the one or more first network elements for the client device and activate the client device using the first process [ i.e. register the SIM card or UICC and the MTC capability information can be employed by one or more provisioning servers to facilitate provisioning MTC services for the respective UEs ] [ 216, Figure 2; paragraphs 0027, 0030, and 0031 ]; and Cui discloses provision the one or more second network elements for the client device and activate the client device using the second process [ i.e. select to assign the UE to the second type of mobile cellular architecture ] [ 263, 208, Figure 2D; and paragraphs 0040, 0042, and 0075 ].

10.	As per claim 10, Ahluwalla discloses wherein the one or more first network elements include one or more of: a charging function, a uniform data repository, a subscriber profile controller, a unified data management device, a diameter routing agent, a subscription locator function, or a telephony application server [ Figure 2 ]. 

11.	As per claim 11, Ahluwalla discloses wherein the one or more first network elements are critical network elements and the one or more second network elements are noncritical network elements [ Figure 2; and paragraphs 0029, and 0039 ].

12.	As per claim 13, Ahluwalla discloses wherein the device is one of a provisioning system or a mobile telephony activation system [ Figure 1; and paragraph 0023 ].

13.	As per claim 14, Mistry discloses utilize the one or more real-time synchronous application programming interfaces to receive the request and to provision one or more network elements of the network for the client device [ i.e. provision SIM ] [ Figure 4; and paragraphs 0066-0068 ].

14.	As per claim 15, it is rejected for similar reasons as stated above in claims 1 and 2.

15.	As per claim 16, it is rejected for similar reasons as stated above in claim 3.

16.	As per claim 17, it is rejected for similar reasons as stated above in claim 5.

17.	As per claim 18, it is rejected for similar reasons as stated above in claim 10.

18.	As per claim 19, it is rejected for similar reasons as stated above in claim 13.

19.	As per claim 20, it is rejected for similar reasons as stated above in claim 14.



20.	Claim(s) 6, 7, and 12, are rejected under 35 U.S.C. 103 as being unpatentable over Ahluwalla et al. [ US Patent Application No 2018/0160253 ], in view of Cui et al. [ US Patent Application No 2023/0284301 ], and further in view of Mistry et al. [ US Patent Application No 2015/0181419 ], and Bimm et al. [ US Patent No 6,901,440 ].

21.	As per claim 6, Ahluwalla, in view of Cui and Mistry does not specifically disclose causing the request to bypass a processing queue of regular activation framework associated with the second process.  Bimm discloses causing the request to bypass a processing queue of regular activation framework associated with the second process [ i.e. bypass ] [ col 24, lines 1-4 ].   It would have been obvious to a person skill in the art before the effective filing date of the claimed invention to combine the teaching of Ahluwalla, Cui, Mistry and Bimm because the teaching of Bimm would enable to provide an effective universal service activation system and method for mapping services to a diverse element base having particular attributes [ Bimm, col 3, lines 21-26 ].

22.	As per claim 7, Ahluwalla in view of Cui, Mistry and Bimm discloses the method of claim 1, furthermore, Cui discloses identifying one or more network elements, of the network, to be provisioned based on the requests, generating one or more provisioning commands and one or more activation commands for the one or more network elements based on the request, and activating the client device based on the one or more activation commands [ i.e. select to assign the UE to the second type of mobile cellular architecture ] [ 263, 208, Figure 2D; and paragraphs 0040, 0042, and 0075 ], and Bimm discloses providing the request to a request queue for a time period; provisioning the one or more network elements with the one or more provisioning commands after the time period expires [ i.e. pending of orders to activate at some time in the future ] [ col 12, lines 11-13; and col 17, lines 40-57 ].

23.	As per claim 12, Bimm discloses wherein the first process provisions the network for the client device without providing the request to a queue [ i.e. bypass ] [ col 24, lines 1-4 ]. 

Response to Arguments

24.	Applicant’s arguments with respect to claim(s) 1-20 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument.

Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.

Conclusion

Any inquiry concerning this communication or earlier communications from the examiner should be directed to DUSTIN NGUYEN whose telephone number is (571)272-3971. The examiner can normally be reached Monday-Friday 9-6 PST.
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, Brian Gillis can be reached on 571-2727952. 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.





/DUSTIN NGUYEN/Primary Examiner, Art Unit 2446