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 .
Claims 35 – 54 are pending in this application.
Information Disclosure Statement
The information disclosure statements (IDS) submitted on 02/05/2025, 11/11/2025 and 08/24/2026 were filed in compliance with the provisions of 37 CFR 1.97 and 1.98. Accordingly, the information disclosure statement is being considered by the examiner.
Applicants have not provided an explanation of relevance of cited document(s) discussed below.
Ying et al. (U.S PreGrant Publication No. 2019/0335332 A1) provides an authorization and verification method including receiving, by a mobility management entity of a remote device, an initial device message sent by a base station, where the initial device message comprises a non-access stratum message of the remote device and an identifier of a relay device, triggering, by the mobility management entity of the remote device based on the initial device message, verification on an association relationship between the remote device and the relay device, and sending, by the mobility management entity of the remote device after determining that the association relationship is verified, an initial context setup request message to the base station.
Vanderveen et al. (U.S PreGrant Publication No. 2019.0223008 A1) is related to a system, method, and device for establishing a secure link for vehicle-to-vehicle (V2V) communication. A device may send a service announcement message to at least one other device via sidelink signaling. The service announcement message indicates a capability of the device to perform a service and includes at least a security certificate of the device. The device establishes a secure link with the at least one other device corresponding to the service by establishing a device key between the device and the at least one other device. The device then communicates service data for the service between the device and the at least one other device via the secure link based on the established device key. Other aspects, embodiments, and features are also claimed and described.
Ericsson Telefon (JP 2018523950A) teaches a method performed by a user equipment (UE) to obtain a key for direct communication with a device via an air interface, wherein the UE is a bootstrap server function in a generic bootstrap architecture (GBA) procedure A method is provided in which a transaction identifier received from (BSF) has been previously obtained. The method includes storing a transaction identifier, sending the transaction identifier to the device, and requesting generation of a key for direct communication with the device. If the transaction identifier is invalid, the method receives a device identifier and key generation information from the device, derives a session shared key from at least the key generation information, and direct communication key at least the session shared key and the device. Deriving from the identifier.
NTT Docomo Inc. (JP 2016219955 A) teaches a radio communication system CS including a first radio terminal STA1 having subscriber identification information SID in a mobile communication network MNW; a second radio terminal STA2 not having subscriber identification information SID; and an access point AP which relays communication between the first radio terminal STA1 and the mobile communication network MNW. The second radio terminal STA2 transmits to the first radio terminal STA1 a first authentication request which requests the first radio terminal STA1 to acquire in proxy authentication information to be used in the second radio terminal STA2 to connect to the access point AP. On receiving the first authentication request, the first radio terminal STA1 requests authentication information using the subscriber identification information SID, and transmits the authentication information, acquired according to the request, to the second radio terminal STA2.
Zhou (CN 114915407) claims a PC5 key processing method, device, AUSF and remote terminal, the method comprises: the AUSF receives the relay key request message sent by the relay terminal; according to the relay key request message, obtaining the PC5 key of the remote terminal; generating a first random number, according to the first random number and PC5 key, generating a relay key; sending the relay key response message to the relay terminal through the target network element of the relay terminal; The PC5 key in the embodiment of the invention is generated by the AUSF of the remote terminal, the AUSF is generated by using the AUSF key of the remote terminal after finishing the authentication to the remote terminal, it is in accordance with the positioning of the AUSF in the 5 G system. The PC5 key generated by AUSF is stored in the UDM, the entity of the PC5 key can be obtained by using the identification of the PC5 key by the AUSF, no need to re-generate each time, improving the system efficiency.
Basu et al. (U.S PreGrant Publication No. 2019/0159018) teaches a ProSe (Proximity-based Services) Direct Discovery that is defined as a procedure used by a ProSe-enabled UE to discover other ProSe-enabled UE(s) in its proximity using E-UTRA direct radio signals via the PC5 interface, wherein the ProSe direct one-to-one communication is realized by establishing a secure layer-2 link over PC5 between two UEs. Each UE has a Layer-2 ID for unicast communication that is included in the Source Layer-2 ID field of every frame that it sends on the layer-2 link and in the Destination Layer-2 ID of every frame that it receives on the layer-2 link. The UE needs to ensure that the Layer-2 ID for unicast communication is at least locally unique. So the UE should be prepared to handle Layer-2 ID conflicts with adjacent UEs using unspecified mechanisms (e.g., self-assign a new Layer-2 ID for unicast communication when a conflict is detected). The layer-2 link for ProSe direct communication one-to-one is identified by the combination of the Layer-2 IDs of the two UEs. This means that the UE can engage in multiple layer-2 links for ProSe direct communication one-to-one using the same Layer-2 ID.
Adrangi et al. (U.S PG Publication No. 2016/0286395 A1) teaches, as an example, a combined use of ECCI-based authentication and DH key agreement, e.g., as described above, may be used in the context of Rel-13 3GPP one-to-one ProSe direct communication over the PC5, e.g., UE-to-UE, reference point, for example, for ECCI-based authentication and Sakai-Kasahara Key Encryption (SAKKE) based key agreement, for example, when establishing a one-to-one communication over PC5.
Choyi (U.S PG Publication No. 2014/0050320 A1) teaches a method on a multi-RAT wireless transmit/receive unit (WTRU) of establishing secure communications, said method may include determining security parameters for the WTRU to use for the secure communications using a first RAT with a first access point (AP). Said method also include authenticating the WTRU with the first AP, wherein authenticating generates a pairwise master key (PMK). Said method includes determining temporal keys to use for the secure communication. Said method also include using at least one of: the determined security parameters, the PMK, or the determined temporal keys, for establishing secure communications between a second RAT of the multi-RAT WTRU and at least one of the first AP or a second AP.
Watfa et al. (U.S PreGrant Publication No. 2016/0374104 A1) teaches a method (e.g., a method, abstract), implemented by a first wireless transmit/receive unit (WTRU) (e.g., realized by a first WTRU, ¶0027), comprising: authenticating, via a second WTRU, the WTRU with a network (e.g., authenticating the first WTRU with a network via a second WRTU, ¶0156, ¶0166, Fig. 3, Fig. 7); determining a second key from the authenticating of the first WTRU (e.g., determining a second key based on a first key acquired from the authenticated first WTRU, ¶0146); receiving a first message (e.g., receiving a first message/signal from the second WRTU, ¶0051, ¶0076, ¶0133 - ¶0136); determining one or more third keys based on the second key (e.g., determining supported, security or encrypted keys based on the second key, ¶0141, ¶0146); and sending a second message (e.g., the second WTRU as recipient, receive a second message/signal, ¶0089), wherein the second message is protected using the one or more third keys (e.g., wherein the second message/signal is protected involving the security or encrypted keys, ¶0147, ¶0165 - ¶0166, ¶0168).
Stojanovski et al. (U.S PreGrant Publication No. 2016/0344726 A1) teaches: a second key is determined based on a first key obtained from authenticating a first WTRU (e.g., a root is provided from a master session key, ¶0039 - ¶0041); a first message is received from a second WTRU; and a second message is sent back to the second WTRU (e.g., messages are received from (or sent to) the second WTRU, ¶0033 - ¶0034, ¶0049, ¶0065, Fig. 4).
Adjakple et al. (U.S PreGrant Publication No. 2022/0132603 A1 (PCT/US2020/018114) teaches a method, implemented by a first wireless transmit/receive unit (WTRU) (e.g., a method initiated by a UE-1 (initiated UE), ¶0256 - ¶0258, Fig. 3), comprising: authenticating, via a second WTRU, the first WTRU with a network (e.g., authenticating, via a UE-2 (targeted UE), said UE-1 (initiated UE) with a network, ¶0257 - ¶0258); determining PC5 data based on key(s) obtained from a key obtained from the authenticating of the first WRTU (e.g., determining if peers (both UEs) are willing to communicate over PC5 interface involving a PC5 link setup or/and PC5 security mode control procedures when said UE-1 (initiated UE) behaves/acts as a master, ¶0258, ¶0601 - ¶0607, ¶0614, ¶0630 - ¶0631, Fig. 16A); receiving, from the second WTRU, a direct security mode command message protected using the PC5 root key (e.g., receiving, from the UE-2, a direct security mode command, ¶0564, ¶0571, ¶0575); determining one or more third keys, including an encryption key and/or an integrity key, based on the PC5 data (e.g., security requirements should be defined in order to perform a security procedure, Fig. 16A – Fig. 16B, ¶0559, ¶0563); and sending, to the second WTRU, a direct security mode complete message, wherein the direct security mode complete message is protected using the one or more third keys (e.g., sending a direct security mode complete signal/message to the UE-2 (targeted) after performing the security procedure, ¶0571, ¶0575).
Targali et al. (U.S PreGrant Publication No. 2013/0298209 A1) teaches determining a root key based on a master key after authenticating a first apparatus (e.g., defining a root key based on a master key (e.g., EMSK) obtained from the authenticating of the first device, ¶0028 with ¶0041).
Lehtovirta et al. (U.S PreGrant Publication No. 2017/0055149 A1) teaches a relay storing a direct communication key DC_K and sends a direct security mode command message to the Remote UE 20m over PC5 (e.g., message 1314m). This message comprises at least the GPI and the identity of the Relay 30m. In a preceding message exchange 1313bm the Relay may also generate a session key (SK) from the direct communication key DC_K, Nonce-UE-remote and a nonce generated by the Relay 30m (Nonce-UE-relay) as follows; SK=KDF(DC_K, Nonce-UE-remote, Nonce-UE-relay.
Kim et al. (U.S PreGrant Publication No. 2020/0100088 A1) teaches a security association for a direct link between two ProSe-Enabled UEs is established by exchanging message contents associated
with direct security mode establishment during the direct link setup procedure or a direct link rekeying procedure. After the direct security mode control procedure is successfully completed, the selected security algorithm and key are used for integrity protection and encryption of all PC5 signaling messages exchanged between UEs. In addition, the selected security algorithm and key are used for encrypting all data plane traffic exchanged between the UEs.
Watfa et al. (U.S PreGrant Publication No. 2016/0381491 A1) discloses systems, methods, and instrumentalities for priority handling for ProSe Communications. A relay wireless transmit/receive unit (WTRU) may act as a relay between the network and the remote WTRU. The relay WTRU may receive a temporary mobile group identity (TMGI) request message from a remote WTRU. The TMGI request message may include a TMGI, a ProSe per packet priority level associated with the TMGI, etc. The relay WTRU may receive an evolved multimedia broadcast multicast service (eMBMS) data packet from a network. The eMBMS may be associated with the TMGI. The relay WTRU may apply the received ProSe per packet priority level associated with the TMGI to the received eMBMS data packet. The relay WTRU may relay the eMBMS data packet to the remote WTRU based on the ProSe per packet priority level. The relay WTRU may forward the eMBMS data packet to the remote WTRU via a PC5 interface.
Samian et al. (CN-107211297 A) provides procedures for dynamically activating and deactivating proximity services (ProSe) enabled WTRU-to-Network (NW) relays are described. Control plane procedures to establish a link between remote WTRUs and WTRU-NW relays are described. Procedures for performing mobility from infrastructure mode to relay mode and relay mode to infrastructure mode are described. Procedures for performing session continuity and IP address preservation are described. Triggers for session continuity are defined for use by the WTRU. Methods to support multicast relay for an out-of-coverage WTRU, including determining Temporary Mobile Group Identities (TMGIs) are also described. Methods to register and update multimedia broadcast multicast services (MBMS) session refresh timers in a relay WTRU when a new WTRU is added, when a WTRU leaves the group, or when a session is updated in the network are also described. Methods for supporting system information block (SIB) forwarding are also described.
Li et al. (CN-109997334 A) provides application that is at least directed to a core network including a non-transitory memory including instructions stored thereon for transferring infrequent small data to a service capability or application server on a 5G network. The core network also includes a processor operably coupled to the non-transitory memory. The processor is configured to execute the instructions of detecting a relay user equipment (UE) sending a data transfer request message to the core network based on uplink traffic generated at a remote UE and control information of the remote UE. The processor is also configured to execute the instructions of querying a database in the core network for subscription information of the remote UE based on the control information. The processor is also configured to execute the instructions of receiving the subscription information from the database. The processor is further configured to execute the instructions of processing the received subscription information. The processor is even further configured to execute the instructions of selecting a network function for transmitting the uplink traffic to the server based on the processing instruction.
Huawei Tech (WO 2019051776 A1) is related to a key transmission method and device. The method comprises: a network device obtaining a discovery key for a remote terminal to discover a relay terminal; acquiring a first key and generic bootstrapping architecture pushing information (GPI), or acquiring an authentication vector (AV); generating a third key according to the first key or a second key in the AV, and encrypting first information by using the third key, wherein the first information comprises the discovery key; sending the encrypted first information and the GPI to the remote terminal by means of the relay terminal, or sending the encrypted first information and RAND information and AUTN information in the AV to the remote terminal by means of the relay terminal, wherein the GPI or the RAND information and AUTN information in the AV are used for the remote terminal to generate a symmetric key of the third key; and decrypting the encrypted first information by using the symmetric key of the third key to acquire the discovery key. By means of this solution, the discovery key is securely sent to a legitimate remote terminal.
Specification
The title of the invention is not descriptive. A new title is required that is clearly indicative of the invention to which the claims are directed.
Double Patenting
A rejection based on double patenting of the “same invention” type finds its support in the language of 35 U.S.C. 101 which states that “whoever invents or discovers any new and useful process... may obtain a patent therefor...” (Emphasis added). Thus, the term “same invention,” in this context, means an invention drawn to identical subject matter. See Miller v. Eagle Mfg. Co., 151 U.S. 186 (1894); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); and In re Ockert, 245 F.2d 467, 114 USPQ 330 (CCPA 1957).
A statutory type (35 U.S.C. 101) double patenting rejection can be overcome by canceling or amending the claims that are directed to the same invention so they are no longer coextensive in scope. The filing of a terminal disclaimer cannot overcome a double patenting rejection based upon 35 U.S.C. 101.
Claims 35 – 38, 40 – 48 and 50 - 54 are rejected under 35 U.S.C. 101 as claiming the same invention as that of at least claim 1 of prior U.S. Patent No. 12,231,885 B2. This is a statutory double patenting rejection.
It is clear that all the elements of the parent claim 1 is to be found in instant claim (as the parent claim 1 fully encompasses the instant claim 35).
No difference between the instant application claim 35 and the patent claim 1 is found. However, the invention of instant claim 1 is in effect a “species” of the “generic” invention of the parent application claim 1.
It has been held that the generic invention is “anticipated” by the “species”. See In re Goodman, 29 USPQ2d 2010 (Fed. Cir. 1993). Since parent application claim 1 is anticipated by claim 35 of the instant application, it is not patentably distinct from claim 1 the instant claims.
Below is a side-by-side comparison (bolded where significant different, and underlined where limitation is mentioned in subsequent dependent claims):
Instant Application 18/963,052
12,231,885
Claim 35
A method, implemented by a first wireless transmit/receive unit (WTRU), comprising:
authenticating, via a second WTRU, the first WTRU with a network;
determining a PC5 root key based on a master key obtained from the authenticating of the first WTRU;
receiving, from the second WTRU, a first PC5 message, wherein the first PC5 message is a direct security mode command message;
determining an encryption key and/or an integrity key based on the PC5 root key; and
sending, to the second WTRU, a second PC5 message, wherein the second PC5 message is a direct security mode complete message protected using at least one of the encryption key and the integrity key.
Claim 1
A method, implemented by a first wireless transmit/receive unit (WTRU), comprising:
authenticating, via a second WTRU, the first WTRU with a network;
determining a PC5 root key based on a master key obtained from the authenticating of the first WTRU;
receiving, from the second WTRU, a first PC5 message protected based on the PC5 root key, wherein the first PC5 message is a direct security mode command message;
determining one or more third keys, including an encryption key and/or an integrity key, based on the PC5 root key; and
sending, to the second WTRU, a second PC5 message, wherein the second PC5 message is a direct security mode complete message is protected using at least one of the one or more third keys.
Claim 36
The method of claim 35, wherein the master key is derived from the authenticating of the first WTRU.
Claim 2
The method of claim 1, wherein any of: (1) the master key is derived from the authenticating of the first WTRU, (2) the PC5 root key is derived based on the master key, and/or (3) the one or more third keys are derived based on the PC5 root key.
Claim 37
The method of claim 35, further comprising: determining an identifier (ID) of the PC5 root key based on the master key obtained from the authenticating of the first WTRU, wherein the determining of at least one of the encryption key and/or the integrity key is based on the PC5 root key and the ID of the PC5 root key.
Claim 3
The method of claim 1, further comprising: determining an identifier (ID) of the PC5 root key based on the master key obtained from the authenticating of the first WTRU, wherein the determining of the one or more third keys is based on the PC5 root key and the ID of the PC5 root key.
Claim 38
The method of claim 35, further comprising: before the authenticating of the first WTRU with the network, sending, to the second WTRU, a direct communication request message to establish a PC5 link with the second WTRU.
Claim 4
The method of claim 1, further comprising: before the authenticating of the first WTRU with the network, sending, to the second WTRU, a direct communication request message to establish a PC5 link with the second WTRU.
Claim 40
The method of claim 38, further comprising:
after sending the direct security mode complete message, receiving, from the second WTRU, a direct communication accept message indicating establishment of the PC5 link with the second WTRU.
Claim 5
The method of claim 4, further comprising: after sending the direct security mode complete message, receiving, from the second WTRU, a direct communication accept message indicating establishment of the PC5 link with the second WTRU.
Claim 41
The method of claim 40, further comprising: after receiving the direct communication accept message, communicating, with the network via the second WTRU, using the PC5 link.
Claim 6
The method of claim 5, further comprising: after receiving the direct communication accept message, communicating, with the network via the second WTRU, using the PC5 link.
Claim 42
The method of claim 35, wherein the PC5 root key is derived based on the master key.
Limitations are mentioned in claim 2.
Claim 43
The method of claim 35, wherein the encryption key and the integrity key are derived based on the PC5 root key.
Limitations are mentioned in claim 1.
Claim 44
The method of claim 35, wherein the first PC5 message is protected based on the PC5 root key.
Limitations are mentioned somewhere in claim 1.
Claim 45
A first wireless transmit/receive unit (WTRU) comprising: a processor and a transceiver which are configured to:
authenticate, via a second WTRU, the first WTRU with a network, determine a PC5 root key based on a master key obtained from the authenticating of the first WTRU,
receive, from the second WTRU, a first PC5 message, wherein the first PC5 message is a direct security mode command message,
determine an encryption key and/or an integrity key based on the PC5 root key, and
send, to the second WTRU, a second PC5 message,
wherein the second PC5 message is a direct security mode complete message protected using at least one of the encryption key and the integrity key.
Claim 7
A first wireless transmit/receive unit (WTRU) comprising: a processor and a transceiver which are configured to:
authenticate, via a second WTRU, the first WTRU with a network, determine a PC5 root key based on a master key obtained from the authenticating of the first WTRU,
receive, from the second WTRU, a first PC5 message protected based on the PC5 root key, wherein the first PC5 message is a direct security mode command message,
determine one or more third keys, including an encryption key and/or an integrity key, based on the PC5 root key, and
send, to the second WTRU, a second PC5 message,
wherein the second PC5 message is a direct security mode complete message protected using at least one of the one or more third keys.
Claim 46
The first WTRU of claim 45, wherein the master key is derived from the authenticating of the first WTRU.
Claim 8
The first WTRU of claim 7, wherein any of: (1) the master key is derived from the authentication of the WTRU, (2) the PC5 root key is derived based on the master key, and/or (3) the one or more third keys are derived based on the PC5 root key.
Claim 47
The first WTRU of claim 45, wherein the processor is configured to: determine an identifier (ID) of the PC5 root key based on the master key obtained from the authenticating of the first WTRU, wherein at least one of the encryption key and/or the integrity key are determined based on the PC5 root key and the ID of the PC5 root key.
Claim 9
The first WTRU of claim 7, wherein the processor is further configured to: determine an identifier (ID) of the PC5 root key based on the master key obtained from the authenticating of the first WTRU, wherein the determining of the one or more third keys is based on the PC5 root key and the ID of the PC5 root key.
Claim 48
The first WTRU of claim 45, wherein the processor is configured to: before the authentication of the first WTRU with the network, send, to the second WTRU, a direct communication request message to establish a PC5 link with the second WTRU.
Claim 10
The first WTRU of claim 7, wherein the processor and the transceiver are configured to: before the authentication of the first WTRU with the network, send, to the second WTRU, a direct communication request message to establish a PC5 link with the second WTRU.
Claim 50
The first WTRU of claim 48, wherein the processor is configured to: after the direct security mode complete message is sent, receive, from the second WTRU, a direct communication accept message indicating establishment of the PC5 link with the second WTRU.
Claim 11
The first WTRU of claim 10, wherein the processor and the transceiver are configured to: after sending the direct security mode complete message, receive, from the second WTRU, a direct communication accept message indicating establishment of the PC5 link with the second WTRU.
Claim 51
The first WTRU of claim 50, wherein the processor is configured to:
after the direct communication accept message is received, communicate, with the network via the second WTRU, using the PC5 link.
Claim 12
The first WTRU of claim 11, wherein the processor and the transceiver are configured to:
after receiving the direct communication accept message, communicate, with the network via the second WTRU, using the PC5 link.
Claim 52
The first WTRU of claim 45, wherein the PC5 root key is derived based on the master key.
Limitations are mentioned in claim 8.
Claim 53
The first WTRU of claim 45, wherein the encryption key and the integrity key are derived based on the PC5 root key.
Limitations are mentioned in claim 7.
Claim 54
The first WTRU of claim 45, wherein the first PC5 message is protected based on the PC5 root key.
Limitations are mentioned somewhere in claim 7.
Claims 39 and 49 of instant application are rejected on the ground of nonstatutory obviousness-type double patenting as being unpatentable over Patent No. 12,231,885 (e.g., claims 1 and 7) in view of claims 12 and 5 of Aghili et al. (Provisional Application No. 62,888,109, refer to U.S PreGrant Publication No. 2022/0345894 A1, hereinafter ‘Aghili’).
Although the claims at issue are not identical, they are not patentably distinct from each other because: The subject matter claimed in the instant application is fully disclosed in the patent and is covered by the patent since the patent and the application are claiming common subject matter, as follows:
It is clear that all the elements of the parents claim 1 and 7 are to be found in instant claims (e.g., as the parent claims 39 and 49, where claims 12 and 5 (of Ahili) fully encompasses the instant claims 39 and 49).
The difference between the instant application claim 39 and the patent claim 1 lies in the fact that the instant claim 39 or 49 include an additional element (e.g., communication request message includes a subscription concealed identifier (SUCI) of a WTRU, etc.) and is thus much more specific. Thus, the invention of instant claim 39 and/or 49 is in effect a “Species” of the “generic” invention of parent claims 1 or 7.
It has been held that the generic invention is “anticipated” by the “species”. See In re Goodman, 29 USPQ2d 2010 (Fed. Cir. 1993). Since parent application claim 1 is anticipated by claim 16 of the instant, it is not patentably distinct from claim 16 the instant claims.
Below is a side-by-side comparison (bolded where significant different, and underlined where limitation is mentioned somewhere):
Instant Application 18/963,052
U.S Patent No. 2022/0345894
Claim 39
The method of claim 38, wherein the direct communication request message includes a subscription concealed identifier (SUCI) of the WTRU.
Claim 14
The method of claim 8, wherein the request message comprises: a first subscription concealed identifier (SUCI) associated with the first subscriber identity module, and a multiple universal subscriber identity module (MUSIM) for MUSIM authentication.
Claim 49
The first WTRU of claim 48, wherein the direct communication request message includes a subscription concealed identifier (SUCI) of the WTRU.
Claim 5
The WTRU of claim 1, wherein the request message comprises: a first subscription concealed identifier (SUCI) associated with the first subscriber identity module, and a second SUCI associated with the second subscriber identity module.
Claims 1 or 7 of the Patent No. 12,231,885 does not disclose “wherein the direct communication request message includes a subscription concealed identifier (SUCI) of the WTRU”.
However, the aforementioned limitations can be found in Aghili. In particular, Aghili teaches a request message comprising a subscription concealed identifier (SUCI) (e.g. a request message comprising a SUCI, ¶0006, ¶0106, ¶0109, claims 5 or/and 12).
Therefore, it would have been obvious to a person of ordinary skill in the art at the time of invention was made to combine ¶0006 and ¶0106 - ¶0109 and claims 5 or 12 of Aghili into Patent No. 12,231,885 that such modification of having SUCI would prevent unknown access or leakage during network registration in order to increase security and protect user identities.
Conclusion
The prior art made of record and not relied upon are considered pertinent to applicant's disclosure:
Di Girolamo et al. (U.S Patent No. 12,004257 B2)1
Ly et al. (U.S Patent No. 12,484,005 B2)2
Abraham et al. (U.S Patent No. 10,582,372 A1)3
1This reference teaches a Subscription Concealed Identifier (SUCI) including a privacy preserving identifier containing a concealed SUPI.
2This reference teaches a UE that provide a CN an identifier such as a SUCI that the CN uses to authenticate the UE in step S510 during initial registration.
3This reference teaches receiving a registration request message which includes a Subscription Concealed Identity (SUCI) associated with a UE.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to JUAN M GUILLERMETY whose telephone number is (571)270-3481. The examiner can normally be reached 9:00AM - 5:00PM.
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, Benny Q TIEU can be reached at 571-272-7490. 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.
/JUAN M GUILLERMETY/Primary Examiner, Art Unit 2682
Prosecution Insights