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 Amendment
This Office Action is in response to applicant’s amendment submitted on February 24, 2026.
Claims 1-20 are now currently pending in the present application.
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 1-12 and 15-19 are rejected under U.S.C. 103 as being unpatentable by Ebert et al. (US 2021/0365594 A1, hereinafter Ebert) in view of KUNZMANN et al. (US 2022/0360584 A1, hereinafter KUNZMANN).
Consider Claim 1, Ebert discloses an apparatus for a data repository Network Function (NF) of a 5G core network, comprising:
at least one processor; and (paragraph 0072, a single processor, module or other unit or device may fulfil the functions of several items recited in the claims
at least one memory; (Paragraph 0022, storage of the data stores and the metadata is provided by a single service, also referred to as “Crypto Cloud”).
the at least one memory storing a meta schema that describes a data structure of meta tags for records, wherein the meta schema includes one or more encryption indicators indicating encryption of the meta tags and/or blocks of the records; (Paragraph 0002, when storing data and in particular confidential data in a cloud service or on a server, a typical problem is data security. A well-known solution to this problem is to encrypt the data. Most of the current systems use symmetric key encryption, allowing a user to keep the key private, so that the data can be accessed if needed).
the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: (Paragraph 0021, storage of the data stores and the metadata is provided by a single service, also referred to as "Crypto Cloud". Paragraph 0033, In FIG. 1, a storage use case whereas a user of the system (1) is storing files into a data store is discussed).
receive a request, from a NF service consumer of the service-based architecture, for a service operation of the 3GPP data repository service regarding storage of a record, and containing meta and/or one or more blocks of the record; (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. Paragraph 0025, a partner/user can request a particular data store, upon which the respective owner/user of this data store is notified. The respective owner/user may then accept or reject the request).
Ebert discloses the claim invention in the limitations noted above but fails to teach at the data repository NF acting as a NF service producer of a service-based architecture in a 3GPP system providing a 3GPP data repository service.
However, KUNZMANN teaches at the data repository NF acting as a NF service producer of a service-based architecture in a 3GPP system providing a 3GPP data repository service (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
Ebert discloses the claim invention apply encryption to one or more of the meta tags of the meta and/or to the one or more blocks of the record based on the one or more encryption indicators included in the meta schema; and (paragraph 0012, one or more data stores are encrypted and the encrypted data stores are provided to a shared service system, e.g., a shared server or a cloud service. Paragraph 0013, a plurality of data stores are encrypted with different keys. In some embodiments, the non-encrypted meta data can be queried by a central server or system) but fails to teach at the NF service producer.
However, KUNZMANN teaches at the NF service producer (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
Ebert discloses the claim invention store the record with the one or more of the meta tags and/or the one or more blocks in encrypted format according to the meta schema. (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. (paragraph 0012, one or more data stores are encrypted and the encrypted data stores are provided to a shared service system, e.g., a shared server or a cloud service) but fails to teach at the NF service producer.
However, KUNZMANN teaches at the NF service producer (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
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, (Clam 1) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with the techniques for data management in a network entity to authorize data consumers in a communication network of KUNZMANN. The motivation to so would be to develop apparatus that has a memory for storing instructions executed by a processor to receive a request from a network function (NF) service consumer for service operation regarding storage of a record containing meta and/or multiple blocks of the record. Also, establishing a network entity of a communication network, data generated by a data producer in the communication network, and storing, at the network entity, the data generated by the data producer.
Consider Claim 2, Ebert discloses the apparatus of claim 1, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to:
receive another request from the same or another NF service consumer for a service operation of the 3GPP data repository service regarding retrieval of the record having the one or more of the meta tags and/or the one or more blocks stored in encrypted format; (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. Paragraph 0025, a partner/user can request a particular data store, upon which the respective owner/user of this data store is notified. The respective owner/user may then accept or reject the request).
send a response to the NF service consumer with the one or more of the meta tags and/or the one or more blocks in unencrypted format. (Paragraph 0046, note that different keys are used for some of the metadata like the ID of the entry. As seen in the aggregation use case in (18), the ID is transferred to another user in its unencrypted form).
Ebert discloses the claim invention decrypt the one or more of the meta tags and/or the one or more blocks of the record based on the encryption indicators included in the meta schema; and (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. Paragraph 0025, a partner/user can request a particular data store, upon which the respective owner/user of this data store is notified. The respective owner/user may then accept or reject the request) but fails to teach at the NF service producer.
However, KUNZMANN teaches at the NF service producer (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
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, (Claim 2) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with the techniques for data management in a network entity to authorize data consumers in a communication network of KUNZMANN. The motivation to so would be to develop apparatus that has a memory for storing instructions executed by a processor to receive a request from a network function (NF) service consumer for service operation regarding storage of a record containing meta and/or multiple blocks of the record. Also, establishing a network entity of a communication network, data generated by a data producer in the communication network, and storing, at the network entity, the data generated by the data producer.
Consider Claim 3, Ebert discloses the apparatus of claim 1, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to:
receive another request from the same or another NF service consumer for a service operation of the 3GPP data repository service regarding a search of records having the one or more of the meta tags stored in encrypted format; (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. Paragraph 0025, a partner/user can request a particular data store, upon which the respective owner/user of this data store is notified. The respective owner/user may then accept or reject the request).
send a response to the NF service consumer containing a search result. (Paragraph 0019, the result of one service data item in one or more data stores is a new row/entry in a database payload table as well as-after successful sealing-a new row/entry in a verification table).
Ebert discloses the claim invention perform a comparison of the one or more of the meta tags stored in encrypted format with a comparison value specified in filter criteria; and (paragraph 0024, the system can be set up to proactively alert partners/users when certain criteria is met. For example, a notification may be presented to the user/ owner of a data store when metadata of the respective data store is accessed. Paragraph 0058, Note that (17) has to use (16) to encrypt the ID, then use the encrypted value for querying) but fails to teach at the NF service producer.
However, KUNZMANN teaches at the NF service producer (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
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, (Claim 3) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with the techniques for data management in a network entity to authorize data consumers in a communication network of KUNZMANN. The motivation to so would be to develop apparatus that has a memory for storing instructions executed by a processor to receive a request from a network function (NF) service consumer for service operation regarding storage of a record containing meta and/or multiple blocks of the record. Also, establishing a network entity of a communication network, data generated by a data producer in the communication network, and storing, at the network entity, the data generated by the data producer.
Consider Claim 4, Ebert discloses the apparatus of claim 3, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to:
decrypt the one or more of the meta tags indicated in the filter criteria; and (paragraph 0026, respective data store owners may then choose to respond to the FDA's request or not, based on criteria, such as regulatory compliance rules that may or may not apply to said data store content and owners in this specific case).
compare the one or more of the meta tags in unencrypted format with the comparison value. (Paragraph 0046, note that different keys are used for some of the metadata like the ID of the entry. As seen in the aggregation use case in (18), the ID is transferred to another user in its unencrypted form. The number and kind of columns is configurable to the use case).
Consider Claim 5, Ebert discloses the apparatus of claim 3, wherein the instructions, when executed by the at least one processor, further cause the apparatus at least to:
encrypt the comparison value; and (paragraph 0058, Note that (17) has to use
(16) to encrypt the ID, then use the encrypted value for querying).
compare the one or more of the meta tags in encrypted format with the encrypted comparison value. (Paragraph 0029, upon receiving payment, the respective encryption keys for the data store, and/or a link to the data store for download by the requestor and decryption with the respective keys are pro-vided to the requestor partner/user).
Consider Claim 6, Ebert discloses the apparatus of claim 1, wherein:
the meta schema includes a block encryption indicator of the one or more encryption indicators indicating that the blocks of the records are stored in encrypted format. (Paragraph 0012, one or more data stores are encrypted and the encrypted data stores are provided to a shared service system, e.g., a shared server or a cloud service).
Consider Claim 7, Ebert discloses the apparatus of claim 6, wherein:
a meta schema data type of the meta schema includes the block encryption indicator. (Paragraph 0012, one or more data stores are encrypted and the encrypted data stores are provided to a shared service system, e.g., a shared server or a cloud service).
Consider Claim 8, Ebert discloses the apparatus of claim 1, wherein:
the meta schema includes a tag encryption indicator of the one or more encryption indicators indicating that tag values of a meta tag are stored in encrypted format. (Paragraph 0029, upon receiving payment, the respective encryption keys for the data store, and/or a link to the data store for download by the requestor and decryption with the respective keys are pro-vided to the requestor partner/user).
Consider Claim 9, Ebert discloses the apparatus of claim 8, wherein:
a tag type data type of the meta schema includes the tag encryption indicator. (Paragraph 0013, a plurality of data stores are encrypted with different keys. In some embodiments, the non-encrypted meta data can be queried by a central server or system).
Consider Claim 10, Ebert discloses the apparatus of claim 1, wherein:
the one or more encryption indicators refer to an encryption enumeration that indicates encryption methods for the records stored in the data repository NF. (Paragraph 0046, note that different keys are used for some of the metadata like the ID of the entry. As seen in the aggregation use case in (18), the ID is transferred to another user in its unencrypted form. The number and kind of columns is configurable to the use case).
Consider Claim11, Ebert discloses the apparatus of claim 1, wherein:
a supported features data type includes an encryption feature indicator indicating that the data repository NF supports encryption as a service. (Paragraph 0012, one or more data stores are encrypted and the encrypted data stores are provided to a shared service system, e.g., a shared server or a cloud service).
Consider Claim 12, Ebert discloses the claim invention in the limitations noted above but fails to teach register a encryption capability in an NF Repository Function (NRF).
However, KUNZMANN teaches wherein register a encryption capability in an NF Repository Function (NRF) (paragraph 0030, some of these other network functions 108 include, but are not limited to, a Data Collection and Coordination Function (DCCF), an Analytics Data Repository Function (ADRF), a Messaging Framework Adapter Function (MFAF), a Network Repository Function (NRF), Network Data Analytics Function (NWDAF), and other network functions that can act as service producers (NFp) and/or service consumers (NFc)).
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, (Clams 12) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with the techniques for data management in a network entity to authorize data consumers in a communication network of KUNZMANN. The motivation to so would be to develop apparatus that has a memory for storing instructions executed by a processor to receive a request from a network function (NF) service consumer for service operation regarding storage of a record containing meta and/or multiple blocks of the record. Also, establishing a network entity of a communication network, data generated by a data producer in the communication network, and storing, at the network entity, the data generated by the data producer.
Consider Claim 15, Ebert discloses the claim invention in the limitations noted above but fails to teach the data repository NF is implemented in an Analytics Data Repository Function (ADRF).
However, KUNZMANN teaches the data repository NF is implemented in an Analytics Data Repository Function (ADRF) (paragraph 0012, an analytics data repository function, is able to ensure that the data consumer is authorized to request the data from a particular data producer by the presence of metadata appended to the collected data).
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, (Clams 15) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with the techniques for data management in a network entity to authorize data consumers in a communication network of KUNZMANN. The motivation to so would be to develop apparatus that has a memory for storing instructions executed by a processor to receive a request from a network function (NF) service consumer for service operation regarding storage of a record containing meta and/or multiple blocks of the record. Also, establishing a network entity of a communication network, data generated by a data producer in the communication network, and storing, at the network entity, the data generated by the data producer.
Consider Claim 16, Ebert discloses a method of performing a data repository service in a 5G core network, the method comprising:
storing a meta schema that describes a data structure of meta tags for records, wherein the meta schema includes one or more encryption indicators indicating encryption of the meta tags and/or blocks of the records; (Paragraph 0002, when storing data and in particular confidential data in a cloud service or on a server, a typical problem is data security. A well-known solution to this problem is to encrypt the data. Most of the current systems use symmetric key encryption, allowing a user to keep the key private, so that the data can be accessed if needed).
receiving a requests from a NF service consumer of the service-based architecture, for a service operation of the 3GPP data repository service regarding storage of a record, and containing meta and/or one or more blocks of the record; (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. Paragraph 0025, a partner/user can request a particular data store, upon which the respective owner/user of this data store is notified. The respective owner/user may then accept or reject the request).
Ebert discloses the claim invention in the limitations noted above but fails to teach at the data repository NF acting as a NF service producer of a service-based architecture in a 3GPP system providing a 3GPP data repository service.
However, KUNZMANN teaches at the data repository NF acting as a NF service producer of a service-based architecture in a 3GPP system providing a 3GPP data repository service (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
Ebert discloses the claim invention apply encryption to one or more of the meta tags of the meta and/or to the one or more blocks of the record based on the one or more encryption indicators included in the meta schema; and (paragraph 0012, one or more data stores are encrypted and the encrypted data stores are provided to a shared service system, e.g., a shared server or a cloud service. Paragraph 0013, a plurality of data stores are encrypted with different keys. In some embodiments, the non-encrypted meta data can be queried by a central server or system) but fails to teach at the NF service producer.
However, KUNZMANN teaches at the NF service producer (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
Ebert discloses the claim invention store the record with the one or more of the meta tags and/or the one or more blocks in encrypted format according to the meta schema. (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. (paragraph 0012, one or more data stores are encrypted and the encrypted data stores are provided to a shared service system, e.g., a shared server or a cloud service) but fails to teach at the NF service producer.
However, KUNZMANN teaches at the NF service producer (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
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, (Clam 16) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with the techniques for data management in a network entity to authorize data consumers in a communication network of KUNZMANN. The motivation to so would be to develop apparatus that has a memory for storing instructions executed by a processor to receive a request from a network function (NF) service consumer for service operation regarding storage of a record containing meta and/or multiple blocks of the record. Also, establishing a network entity of a communication network, data generated by a data producer in the communication network, and storing, at the network entity, the data generated by the data producer.
Consider Claim 17, Ebert discloses the method of claim 16, further comprising:
receiving another request from the same or another NF service consumer for a service operation of the 3GPP data repository service regarding retrieval of the record having the one or more of the meta tags and/or the one or more blocks stored in encrypted format; (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. Paragraph 0025, a partner/user can request a particular data store, upon which the respective owner/user of this data store is notified. The respective owner/user may then accept or reject the request).
sending a response to the NF service consumer with the one or more of the meta tags and/or the one or more blocks in unencrypted format. (Paragraph 0019, the result of one service data item in one or more data stores is a new row/entry in a database payload table as well as-after successful sealing-a new row/entry in a verification table).
Ebert discloses the claim invention decrypt the one or more of the meta tags and/or the one or more blocks of the record based on the encryption indicators included in the meta schema; and (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. Paragraph 0025, a partner/user can request a particular data store, upon which the respective owner/user of this data store is notified. The respective owner/user may then accept or reject the request) but fails to teach at the NF service producer.
However, KUNZMANN teaches at the NF service producer (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
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, (Claim 17) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with the techniques for data management in a network entity to authorize data consumers in a communication network of KUNZMANN. The motivation to so would be to develop apparatus that has a memory for storing instructions executed by a processor to receive a request from a network function (NF) service consumer for service operation regarding storage of a record containing meta and/or multiple blocks of the record. Also, establishing a network entity of a communication network, data generated by a data producer in the communication network, and storing, at the network entity, the data generated by the data producer.
Consider Claim 18, Ebert discloses the method of claim 16, further comprising:
receiving another request from the same or another NF service consumer for a service operation of the 3GPP data repository service regarding a search of records having the one or more of the meta tags stored in encrypted format; (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. Paragraph 0025, a partner/user can request a particular data store, upon which the respective owner/user of this data store is notified. The respective owner/user may then accept or reject the request).
performing a comparison of the one or more of the meta tags stored in encrypted format with a comparison value specified in filter criteria; and (paragraph 0024, the system can be set up to proactively alert partners/users when certain criteria is met. For example, a notification may be presented to the user/ owner of a data store when metadata of the respective data store is accessed. Paragraph 0058, Note that (17) has to use (16) to encrypt the ID, then use the encrypted value for querying).
sending a response to the NF service consumer containing a search result. (Paragraph 0019, the result of one service data item in one or more data stores is a new row/entry in a database payload table as well as-after successful sealing-a new row/entry in a verification table).
Consider Claim 19, Ebert discloses a non-transitory computer readable medium embodying programmed instructions executed by a processor of a data repository Network Function (NF), wherein the instructions direct the processor to implement a method of performing a data repository service in a 5G core network, the method comprising:
storing a meta schema that describes a data structure of meta tags for records, wherein the meta schema includes one or more encryption indicators indicating encryption of the meta tags and/or blocks of the records; (Paragraph 0002, when storing data and in particular confidential data in a cloud service or on a server, a typical problem is data security. A well-known solution to this problem is to encrypt the data. Most of the current systems use symmetric key encryption, allowing a user to keep the key private, so that the data can be accessed if needed).
receiving a requests from a NF service consumer of the service-based architecture, for a service operation of the 3GPP data repository service regarding storage of a record, and containing meta and/or one or more blocks of the record; (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. Paragraph 0025, a partner/user can request a particular data store, upon which the respective owner/user of this data store is notified. The respective owner/user may then accept or reject the request).
Ebert discloses the claim invention in the limitations noted above but fails to teach at the data repository NF acting as a NF service producer of a service-based architecture in a 3GPP system providing a 3GPP data repository service.
However, KUNZMANN teaches at the data repository NF acting as a NF service producer of a service-based architecture in a 3GPP system providing a 3GPP data repository service (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
Ebert discloses the claim invention apply encryption to one or more of the meta tags of the meta and/or to the one or more blocks of the record based on the one or more encryption indicators included in the meta schema; and (paragraph 0012, one or more data stores are encrypted and the encrypted data stores are provided to a shared service system, e.g., a shared server or a cloud service. Paragraph 0013, a plurality of data stores are encrypted with different keys. In some embodiments, the non-encrypted meta data can be queried by a central server or system) but fails to teach at the NF service producer.
However, KUNZMANN teaches at the NF service producer (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
Ebert discloses the claim invention store the record with the one or more of the meta tags and/or the one or more blocks in encrypted format according to the meta schema. (Paragraph 0011, metadata is generated for each of the data stores. The metadata may then be stored in a searchable database, which simplifies data sharing of some information about the data stores. (paragraph 0012, one or more data stores are encrypted and the encrypted data stores are provided to a shared service system, e.g., a shared server or a cloud service) but fails to teach at the NF service producer.
However, KUNZMANN teaches at the NF service producer (paragraph 0030, note that any network function can be a service producer for one service and a service consumer for another service. Further, when the service being provided includes data, the data-providing NFp is referred to as a data producer, while the data-requesting NFc is referred to as a data consumer. A data producer may also be an NF that generates data by modifying or otherwise processing data produced by another NF).
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, (Clam 19) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with the techniques for data management in a network entity to authorize data consumers in a communication network of KUNZMANN. The motivation to so would be to develop apparatus that has a memory for storing instructions executed by a processor to receive a request from a network function (NF) service consumer for service operation regarding storage of a record containing meta and/or multiple blocks of the record. Also, establishing a network entity of a communication network, data generated by a data producer in the communication network, and storing, at the network entity, the data generated by the data producer.
Claims 13-14 and 20, are rejected under 103 as being unpatentable over Ebert et al. (US 2021/0365594 A1, hereinafter Ebert) in view of LI et al. (US 2020059761 A1, hereinafter LI).
Consider Claim 13, Ebert discloses the claim invention in the limitations noted above but fails to teach the data repository NF is implemented in an Unstructured Data Storage Function (UDSF).
However, LI teaches the data repository NF is implemented in an Unstructured Data Storage Function (UDSF) (paragraph 0073, the GMF 320 may store the group context or profile (including the multicast address associated to the LAN UE group) locally or in a separate network function such as UDR or UDM or UDSF (Unstructured Data Storage Function). When the context (or profile) is stored in a separate network function, the GMF 320 may interact with that network function).
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, (Claim 13) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with apparatuses for enabling private communication between user equipment (UEs) in a (LAN) UE group of LI. The motivation to so would be to develop an apparatus configuring the data repository NF to encrypt/decrypt certain data in the records based on encryption indicators embedded in the meta schema for the records, and specifies protection of data in the meta schema, thus enhancing same protection level across different data repository NFs. There by creating a field of network communications, and in particular to methods for enabling private communication within a user equipment (UE) group.
Consider Claim 14, Ebert discloses the claim invention in the limitations noted above but fails to teach the data repository NF is implemented in a Unified Data Repository (UDR).
However, LI teaches the data repository NF is implemented in a Unified Data Repository (UDR) (Paragraph 0073, the GMF 320 may store the group context or profile (including the multicast address associated to the LAN UE group) locally or in a separate network function such as UDR or UDM or UDSF (Unstructured Data Storage Function). When the context (or profile) is stored in a separate network function, the GMF 320 may interact with that network function).
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, (Claim 14) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with apparatuses for enabling private communication between user equipment (UEs) in a (LAN) UE group of LI. The motivation to so would be to develop an apparatus configuring the data repository NF to encrypt/decrypt certain data in the records based on encryption indicators embedded in the meta schema for the records, and specifies protection of data in the meta schema, thus enhancing same protection level across different data repository NFs. There by creating a field of network communications, and in particular to methods for enabling private communication within a user equipment (UE) group.
Consider Claim 20, Ebert discloses the claim invention in the limitations noted above but fails to teach the data repository NF is implemented in an Unstructured Data Storage Function (UDSF).
However, LI teaches the data repository NF is implemented in an Unstructured Data Storage Function (UDSF) (paragraph 0073, the GMF 320 may store the group context or profile (including the multicast address associated to the LAN UE group) locally or in a separate network function such as UDR or UDM or UDSF (Unstructured Data Storage Function). When the context (or profile) is stored in a separate network function, the GMF 320 may interact with that network function).
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, (Claim 20) to modify by incorporating the encryption for storing data and sharing in particular confidential data of Ebert with apparatuses for enabling private communication between user equipment (UEs) in a (LAN) UE group of LI. The motivation to so would be to develop an apparatus configuring the data repository NF to encrypt/decrypt certain data in the records based on encryption indicators embedded in the meta schema for the records, and specifies protection of data in the meta schema, thus enhancing same protection level across different data repository NFs. There by creating a field of network communications, and in particular to methods for enabling private communication within a user equipment (UE) group.
Response to Arguments
Applicant' s arguments/remarks made in an amendment filed February 24,2026 have been fully considered. In view of the amended claims and upon further consideration, a new ground(s) of rejection, necessitated by the amendments is made in view of different interpretation of the previously applied references as presented in this Office action. Applicant' s arguments with respect to claim(s) are therefore moot.
Conclusion
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.
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
/JEANETTE J PARKER/Supervisory Patent Examiner, Art Unit 2646
Prosecution Insights