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 .
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 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.
This office action is in response to the communication filed on 11/19/2025.
Claims 1, 3-7, 9-11, 13-15, 17-20 are pending.
Response to Arguments
Applicant has argued that Li does not teach “determining, from subscription data, target synchronization data belonging to the second UDM comprises: acquiring a first data subset, wherein the first data subset is obtained according to a preset data classification rule and the subscription data, and the first data subset comprises subscription data belonging to the second UDM; and obtaining the target synchronization data according to a preset first policy and the first data subset” in claims 1, 9 and similarly “sending data requirement information, such that the first UDM acquires the target synchronization data from a first data subset according to the data requirement information, wherein the first data subset is obtained by the first UDM according to a preset data classification rule and the subscription data” in claim 6. The examiner respectfully disagrees and maintains that Li teaches these limitations (p. 22,
Optionally, the authentication request information includes a first type identifier and a second type identifier. Wherein the first type of identity comprises SUPI and DNN for indicating whether the public network UDM calculates authentication data for one or more private network terminals. The second type of identification comprises an identification parameter of the number of the authentication data and a statistical parameter of the number of the authentication data, and is used for indicating the public network UDM to specifically calculate the number of the authentication data for the private network terminal
It should be noted that, if the first type identifier included in the authentication request information is SUPI, it indicates that a single terminal requests the public network UDM to calculate the authentication data in the private network; and if the first-class identifier included in the authentication request information is DNN, the first-class identifier indicates that a plurality of terminals request the public network UDM to calculate the authentication data in the private network.
It should be noted that, if the second type identifier included in the authentication request information is the authentication data quantity identifier parameter, it indicates that one or more private network terminals corresponding to the first type identifier are accessed to the public network for the first time, and the public network UDM is required to calculate all authentication data that may be used by the one or more private network terminals for the aforementioned one or more private network terminals; if the second type identifier included in the authentication request information is the authentication data quantity statistical parameter, it indicates that one or more private network terminals corresponding to the first type identifier need the public network UDM to supplement partial authentication data for the private network terminals.
Here the first and second identifiers can be read as classification data which is in the request from the private network to the public network for authentication information (subscription data). The authentication data will be calculated by the public network based on rules pertaining the first and second identifiers. In case of the first identifier, if it is SUPI, the public network will calculate specific authentication data (first data subset) for terminals with the SUPI. If it is DNN, the public network will calculate all authentication data for all terminals. In case of the second identifier, if it is authentication data quantity identifier parameter, the public network will calculate all authentication data for the terminals indicated in the first identifier; whereas if it is authentication data quantity statistical parameter, the public network will calculate supplemental authentication data for the terminals.
Applicant argues that Li teaches the public network (read as the first UDM) passively identifies the first data subset (based on a request from the private network) while the claims require actively acquiring the first data subset at the first UDM. The examiner respectfully disagrees. The manner of “active” or “passive” acquiring of the first data subset is not disclosed in the specification. The claims do not require the first UDM to “actively” acquire the first data subset, nor do they require that the acquiring is independent from any communication from the second UDM (see at least claim 1, 9). In fact, claim 6 evens recites that the second UDM sends data requirement information such the first UDM acquires the target synchronization data from a first data subset according to the data requirement information.
Claim Rejections - 35 USC § 102
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.
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1, 3-4, 6, 9-11, 13-14, 17-18 is/are rejected under AIA 35 U.S.C. 102(a)(2) as being anticipated by Li et al. (CN 113453213 A, English translation provided by Google Patents, herein “Li”).
As to claim 1, Li discloses data synchronization method, applied to a first Unified Data Management (UDM) which is communicatively connected to a second UDM (p. 21, public network UDM and private network UDM), the data synchronization method comprising:
determining, from subscription data, target synchronization data belonging to the second UDM; and sending the target synchronization data to the second UDM, such that the second UDM performs data synchronization according to the target synchronization data (p. 21, Data network name, after the private network is disconnected from the public network and then restored to be connected, or when the private network is initially accessed to the public network, the authentication data stored in the database of the private network is not synchronized with the authentication data stored in the database of the public network, and at this time, the private network UDM may count the number of private network terminals that specifically require to supplement the authentication data and the number of authentication data required by each private network terminal, and send authentication request information to the public network UDM. After receiving the authentication request information, the public network UDM determines target authentication data according to the identification information carried in the authentication request information and sends the target authentication data to the private network UDM to supplement the required authentication data for the private network UDM);
wherein determining, from subscription data, target synchronization data belonging to the second UDM comprises: acquiring a first data subset, wherein the first data subset is obtained according to a preset data classification rule and the subscription data, and the first data subset comprises subscription data belonging to the second UDM; and obtaining the target synchronization data according to a preset first policy and the first data subset (p. 24-25, S202-203, determining target synchronization data according to parameters in the request, first type identifier and second type identifier, or rules and subscription data. Page 22, S202, the first and second identifiers can be read as classification data which is in the request from the private network to the public network for authentication information (subscription data). The authentication data will be calculated by the public network based on rules pertaining the first and second identifiers. In case of the first identifier, if it is SUPI, the public network will calculate specific authentication data (first data subset) for terminals with the SUPI. If it is DNN, the public network will calculate all authentication data for all terminals. In case of the second identifier, if it is authentication data quantity identifier parameter, the public network will calculate all authentication data for the terminals indicated in the first identifier; whereas if it is authentication data quantity statistical parameter, the public network will calculate supplemental authentication data for the terminals).
As to claim 3, Li discloses obtaining the target synchronization data according to a preset first policy and the first data subset comprises: performing data conversion on the first data subset according to a preset data conversion rule to obtain the target synchronization data (data conversion is broad and is read as calculated target synchronization data by Li, p. 24-25, S202-203, determining target synchronization data according to parameters in the request, first type identifier and second type identifier, or rules and subscription data, and a third type identifier indicating a level of authentication).
As to claim 4, Li discloses obtaining the target synchronization data according to a preset first policy and the first data subset comprises: acquiring data requirement information, the data requirement information belonging to the second UDM; and acquiring the target synchronization data from the first data subset according to the data requirement information (p. 24-25, S202-203, determining target synchronization data according to parameters in the request, first type identifier and second type identifier, or rules and subscription data, data requirement is in the request from the private UDM, such as all authentication data or supplement partial authentication data for the private network terminals).
As to claim 6, Li discloses a data synchronization method, applied to a second Unified Data Management (UDM) which is communicatively connected to a first UDM (p. 21, public (first) network UDM and private (second) network UDM), the data synchronization method comprising:
receiving target synchronization data sent by the first UDM, wherein the target synchronization data is determined from subscription data by the first UDM; and performing data synchronization according to the target synchronization data (p. 21, Data network name, after the private network is disconnected from the public network and then restored to be connected, or when the private network is initially accessed to the public network, the authentication data stored in the database of the private network is not synchronized with the authentication data stored in the database of the public network, and at this time, the private network UDM may count the number of private network terminals that specifically require to supplement the authentication data and the number of authentication data required by each private network terminal, and send authentication request information to the public network UDM. After receiving the authentication request information, the public network UDM determines target authentication data according to the identification information carried in the authentication request information and sends the target authentication data to the private network UDM to supplement the required authentication data for the private network UDM);
sending data requirement information, such that the first UDM acquires the target synchronization data from a first data subset according to the data requirement information, wherein the first data subset is obtained by the first UDM according to a preset data classification rule and the subscription data (p. 24-25, S202-203, determining target synchronization data according to parameters in the request, first type identifier and second type identifier, or rules and subscription data. Page 22, S202, the first and second identifiers can be read as classification data which is in the request from the private network to the public network for authentication information (subscription data). The authentication data will be calculated by the public network based on rules pertaining the first and second identifiers. In case of the first identifier, if it is SUPI, the public network will calculate specific authentication data (first data subset) for terminals with the SUPI. If it is DNN, the public network will calculate all authentication data for all terminals. In case of the second identifier, if it is authentication data quantity identifier parameter, the public network will calculate all authentication data for the terminals indicated in the first identifier; whereas if it is authentication data quantity statistical parameter, the public network will calculate supplemental authentication data for the terminals).
As to claim 9, Li discloses a Unified Data Management (UDM), comprising:
a memory, a processor, and a computer program stored in the memory and executable by the processor (p. 25), wherein the computer program, when executed by the processor, causes the processor to perform a data synchronization method, applied to a first Unified Data Management (UDM) which is communicatively connected to a second UDM, the data synchronization method comprising: determining, from subscription data, target synchronization data belonging to the second UDM; and sending the target synchronization data to the second UDM, such that the second UDM performs data synchronization according to the target synchronization data (p. 21, Data network name, after the private network is disconnected from the public network and then restored to be connected, or when the private network is initially accessed to the public network, the authentication data stored in the database of the private network is not synchronized with the authentication data stored in the database of the public network, and at this time, the private network UDM may count the number of private network terminals that specifically require to supplement the authentication data and the number of authentication data required by each private network terminal, and send authentication request information to the public network UDM. After receiving the authentication request information, the public network UDM determines target authentication data according to the identification information carried in the authentication request information and sends the target authentication data to the private network UDM to supplement the required authentication data for the private network UDM);
wherein determining, from subscription data, target synchronization data belonging to the second UDM comprises: acquiring a first data subset, wherein the first data subset is obtained according to a preset data classification rule and the subscription data, and the first data subset comprises subscription data belonging to the second UDM; and obtaining the target synchronization data according to a preset first policy and the first data subset (p. 24-25, S202-203, determining target synchronization data according to parameters in the request, first type identifier and second type identifier, or rules and subscription data. Page 22, S202, the first and second identifiers can be read as classification data which is in the request from the private network to the public network for authentication information (subscription data). The authentication data will be calculated by the public network based on rules pertaining the first and second identifiers. In case of the first identifier, if it is SUPI, the public network will calculate specific authentication data (first data subset) for terminals with the SUPI. If it is DNN, the public network will calculate all authentication data for all terminals. In case of the second identifier, if it is authentication data quantity identifier parameter, the public network will calculate all authentication data for the terminals indicated in the first identifier; whereas if it is authentication data quantity statistical parameter, the public network will calculate supplemental authentication data for the terminals).
As to claim 10, Li discloses a non-transitory computer-readable storage medium, storing a computer-executable instruction which, when executed by a processor, causes the processor to perform the data synchronization method of claim 1 (same rationale in claim 1, Li, p. 25).
As to claim 11, Li discloses a non-transitory computer-readable storage medium, storing a computer-executable instruction which, when executed by a processor, causes the processor to perform the data synchronization method of claim 6 (same rationale in claim 6, Li, p. 25).
As to claims 13, 14, the claims are rejected for the same rationale in claims 3, 4.
As to claims 17, 18, the claims are rejected for the same rationale in claims 3, 4.
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.
Claim(s) 5, 7, 15, 19, 20 is/are rejected under AIA 35 U.S.C. 103 as being unpatentable over Li in view of Zhou et al. (CN 110475247 A, herein “Zhou”).
As to claim 5, 15, 19, Li discloses sending the target synchronization data to the second UDM, such that the second UDM performs data synchronization according to the target synchronization data comprises: sending the target synchronization data to the second UDM, such that the second UDM performs data synchronization according to the target synchronization data (p. 21)
Li does not disclose encrypting the target synchronization data according to a preset encryption algorithm to obtain encrypted target synchronization data;
sending the encrypted target synchronization data to the second UDM, such that the second UDM decrypts the encrypted target synchronization data.
Zhou discloses encrypting the target synchronization data according to a preset encryption algorithm to obtain encrypted target synchronization data; sending the encrypted target synchronization data to the second UDM, such that the second UDM decrypts the encrypted target synchronization data and performs data synchronization according to the target synchronization data obtained by decryption (p. 30, UPI encryption uses asymmetric encryption techniques. Asymmetric encryption techniques require that the decrypter must decrypt the encrypted information using a private key corresponding to the encrypted public key. The asymmetric encryption technique allows each UDM to generate an unlimited number of public and private key pairs and manage the private keys separately. The management of the private key may be based on HPLMN or UDM. When the private key management is based on the HPLMN, one UDM may be allowed to possess all private keys, so that the SUCI may be decrypted collectively, and at this time, it is not necessary to include routing information in the SUCI. When the management of the private key is based on the UDM, that is, one UDM cannot possess the private keys of the other UDMs, a centralized SUCI decryption scheme will not be adopted at this time. Management for private keys is based on the UDM case, requiring the SUCI to provide additional routing information to support message routing in this scenario in order to route messages containing encrypted SUPIs to the target UDM.)
It would have been obvious to one skilled in the art before the effective filing date of the claimed invention to apply Zhou’s UDM traffic encryption/decryption to Li’s teachings in order to provide security to UDM transmission as a well-known benefit.
As to claims 7, 20, Li discloses receiving the target synchronization data sent by the first UDM (p. 21).
Li does not disclose after receiving the target synchronization data sent by the first UDM, the method further comprises: in response to the acquired target synchronization data being obtained by the first UDM through a preset encryption algorithm, decrypting the target synchronization data according to a preset decryption algorithm.
Li discloses in response to the acquired target synchronization data being obtained by the first UDM through a preset encryption algorithm, decrypting the target synchronization data according to a preset decryption algorithm (p. 30).
It would have been obvious to one skilled in the art before the effective filing date of the claimed invention to apply Zhou’s UDM traffic encryption/decryption to Li’s teachings in order to provide security to UDM transmission as a well-known benefit.
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 HIEU T HOANG whose telephone number is (571) 270-1253. The examiner can normally be reached Mon-Fri 9 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, Vivek Srivastava can be reached on 571-272-7304. 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.
/HIEU T HOANG/Primary Examiner, Art Unit 2449