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 .
Information Disclosure Statement
The information disclosure statement(s) was/were submitted on 3/12/24 and 10/21/25. The submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement(s) is/are being considered by the examiner.
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.
Claims 1,8, and 12-13are rejected under 35 U.S.C. 102(a) (1) as being anticipated by Hosokawa US 2005/0054338.
As per claim 1 and 12, Hosokawa teaches a method for registration, applied to a core network device, the method comprising ( Ref. Fig. 2,5-6, elements 111 and 114, para 0093-0109 and 0073-0074 comprises processing and storing section), acquiring a first registration request message sent by a first terminal device, wherein the first registration request message comprises a first identifier of the first terminal device ( Ref. Fig. 5-6, para 0095-0096) ; acquiring related information about a second terminal device associated with the first identifier( Ref. Fig. 5-6, para 0097) ; acquiring a second identifier of the first terminal device, in response to the related information about the second terminal device being in an active state (see ref. fig. 5-6 and para 0098); and performing a registration for the first terminal device according to the second identifier( Ref. Fig. 5-6, para 0102-0109) .
As per claims 8 and 13 Hosokawa teaches a method for registration and program executed by the processor applied to a first terminal device, the method comprising ( Ref. Fig. 5-6, para 0093-0109), sending a first registration request message to a core network device, wherein the first registration request message comprises a first identifier of the first terminal device( Ref. Fig. 5-6, para 0095) ; and sending a second identifier of the first terminal device to the core network device to complete a registration, in response to a satisfaction of a preset condition( Ref. Fig. 6, element 12 and 13, para 0107 and 0108) ; wherein the preset condition is directed to one of, an acquisition of an identifier request message sent by the core network device, or a failure in an acquisition of a message related to the registration sent by the core network device within a preset time ( Ref. Fig. 6, para 0105 and 0106).
3. 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.
4. 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.
5. 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.
6. Claims 2-7, 9-11 and 14-20 are rejected under 35 U.S.C. 103 as being unpatentable over US Publication to Hosokawa 2005/0054338 in view of "3rd Generation Partnership Project; Technical Specification Group Services and Systems Aspects; Security; Lawful Interception (LI) Implementation Guidance (Release 17)", 3GPP DRAFT; S3I210503, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE; 650, ROUTE DES LUCIOLES; F-06921 SOPHIA-ANTIPOLIS CEDEX; FRANCE, 21 July 2021 (2021-07-21), XP052031831 (herein after 3GPP).
As per dependent claims 2 to 7 and 9 to 11, Hosokawa teach all the limitation except additional features
Recited in these claims, however 3GPP teaches all the claimed limitations:
wherein the related information about the second terminal device comprises at least one of, a context of the second terminal device; a security context of the second terminal device; or a non-access stratum (NAS) security context of the second terminal device (see ref. paragraph 6.3.5.2);
wherein before acquiring the first registration request message sent by the first terminal device, the method further comprises acquiring a second registration request message sent by the second terminal device, wherein the second registration request message comprises a third identifier of the second terminal device, 12248270.1 and the third identifier is identical to the first identifier; and performing a registration for the second terminal device according to the third identifier (see in particular figure 6.3.5-2); wherein before acquiring the first registration request message sent by the first terminal device, the method further comprises, assigning a third identifier to the second terminal device after the registration for the second terminal device is completed, wherein the third identifier is identical to the first identifier (see in particular figure 6.3.5-2); wherein acquiring the second identifier comprises, sending an identifier request message to the first terminal device; and acquiring an identifier response message sent by the first terminal device, wherein the identifier response message comprises the second identifier (see in particular paragraph 6.3.6.1 and figure 6.3.6-1); wherein acquiring the second identifier comprises, acquiring a third registration request message sent by the first terminal device, wherein the third registration request message comprises the second identifier (see in particular paragraph 6.3.6.1 and figure 6.3.6-1); wherein before acquiring the third registration request message sent by the first terminal device, the method further comprises, acquiring a fourth registration request message sent by the first terminal device, wherein the fourth registration request message comprises the first identifier; acquiring related information about the second terminal device associated with the first identifier; and discarding the fourth registration request message in response to the related information about the second terminal device being in an active state (see in particular paragraph 6.3.6.1 and figure 6.3.6-1); wherein the preset condition is directed to the acquisition of the identifier request message sent by the core network device; and sending the second identifier to the core network device comprises, sending an identifier response message to the core network device, wherein the identifier response message comprises the second identifier (see in particular "Identity Request for UE" and "Identity Response" in figure 6.3.6-1); wherein the preset condition is directed to the failure in the acquisition of the message related to the registration sent by the core network device within the preset time; and sending the second identifier to the core network device comprises, sending a third registration request message to the core network device, wherein the third registration request message comprises the second identifier (see in particular "Identity
Request for UE" and "Identity Response" in figure 6.3.6-1); wherein before sending the third registration request message to the core network device, the method further comprises, setting a current iteration number K to 0, and sending a fourth registration request message to the core network device, wherein the fourth registration request message comprises the first identifier; and setting the current iteration number K as K=K+1, in response to the failure in the acquisition of the message related to the registration sent by the core network device within the preset time; and keeping sending the fourth registration request message to the core network device in response to the current iteration number K being less than a maximum iteration number, until the current iteration number K equals to the maximum iteration number (see in particular "Identity Request for UE" and "Identity Response" in figure 6.3.6-1).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify Hosokawa by incorporating the teachings of 3GPP because the method and device allows for better registration process of terminals. The motivation is that by applying a well-known standard or protocol or machine to a system of Hosokawa provides better registration process for terminals.
As per claims 14-20, they are similarly rejected as to the claims 1-13.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to AYAZ R SHEIKH whose telephone number is (571)272-3795. The examiner can normally be reached M-F 8 AM -5 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, Debbie Reynolds can be reached at 571-272-0734. 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.
/AYAZ R SHEIKH/Supervisory Patent Examiner, Art Unit 2476
Prosecution Insights