DETAILED ACTION
This is in response to Applicant’s reply dated 8/4/26. Claims 1-30 have been examined.
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 (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.
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.
Claim(s) 1-30 are rejected under 35 U.S.C. 102(a)(1) as being unpatentable by Ferdi et al. (WO 2022/150538; hereafter Ferdi).
Regarding Claim 1 (Currently Amended),
A user equipment (UE), comprising: an antenna system that includes one or more antennas; and a processing system coupled with the antenna system that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the UE to:
receive first information indicative of a first internet protocol address; transmit a non-access stratum request that indicates the first internet protocol address on an internet protocol network to a core network service to establish a protocol data unit session using a user plane protocol stack [Ferdi: 0124; the remote WTRU may send a direct communication request (DCR) message (e.g., including a remote WTRU's subscription identity and/or network identity such as SUPI or GUTI), for example, based on the determination that the service code is associated with a DN that uses secondary A&A; 0126; at 5, the relay may trigger a network-controlled authorization of the remote WTRU (e.g., as described with respect to FIG.9 or FIG.14), for example, on the condition that the direct communication request (DCR) message includes an SUPI or GUTI; 0128; the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU; 0130; the relay may configure the ProSe link to allow data traffic between the remote WTRU and the network/DN … the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU (e.g., if none were allocated at 7) to be used with the established connectivity session (e.g., the established PDU session); 0133; at 1, a relay WTRU may decide to trigger a PDU session secondary A&A for the remote WTRU abased on conditions as determined in FIG.2; 0134; at 2, the relay may send a NAS message (e.g., a PDU session modification, establishment request, and/or a remote WTRU report), for example, to the SMF; the NAS message may include one or more of the following: remote WTRU user ID, remote WTRU addressing information, or other connectivity session (e.g., PDU session) parameters (e.g., S-NSSAI, DNN, and/or the like); 0196; at 2, the remote WTRU may determine (e.g., from the configuration provided at 0) that the relay service code and/or type discovered at 1 may be associated with an S-NSSAI that may be subject to NSSAA (e.g., based on an indication parameter for the S-NSSAI); the remote WTRU, e.g., based on this determination, may send a DCR message including one or more of a remote WTRU's subscription or network identity (e.g., SUPI or GUTI) and/or an indication of WTRU support for NSSAA];
Note:
A relay allocates an IP address (i.e. a first IP address) for a remote WTRU during a discovery operation.
receive, from the core network service using the user plane protocol stack, a non-access stratum response that indicates the first internet protocol address, the non-access stratum response comprising second information indicative of a second internet protocol address [Ferdi: 0135; at 3, the SMF may determine, e.g., based on subscription information, that the requested DN may be subject to secondary A&A and/or may trigger a PDU session secondary A&A of the remote WTRU via relay; 0136; at 4, the remote WTRU may perform a PDU session secondary A&A via a relay. Authentication message(s) may be transported using one or more NAS messages between the SMF and the relay. The one or more NAS messages may include an identity of the remote WTRU (e.g., GPSI, remote user ID, and/or the like) to indicate to the relay that authentication message(s) are for the remote WTRU. The relay may forward the message(s) (e.g., transparently) between the remote WTRU and the SMF. A DN-AAA may allocate and/or assign an IP address and/or IPv6 prefix for the remote WTRU during the procedure as described herein (e.g., as described with respect to FIG.8); 0138; at 6, the SMF may send a NAS message (e.g., PDU session modification, establishment response, and/or remote WTRU report acknowledgment) to the relay indicating the result of the PDU session secondary A&A. The NAS message may include an identity of the remote WTRU (e.g., GPSI and/or remote user ID) and/or an EAP success or failure message. The NAS message may include addressing and/or QoS information associated with the remote WTRU; 0175; at 6, the relay WTRU may update authorization information (e.g., any authorization information) associated with the remote WTRU with different information (e.g., new information) received from the SMF in case of successful secondary re-A&A of the remote WTRU]; and
Note:
DN-AAA allocates an IP address (i.e. second IP address) for a remote WTRU.
transmit non-access stratum information that indicates the first internet protocol address to the core network service using the user plane protocol stack, and first data information associated with the protocol data unit session that indicates the second internet protocol address using the user plane protocol stack [Ferdi: 0114; in examples, a remote WTRU may be authorized to access using an IPSec connection, session, and/or tunnel to a N3IWF, specific network slice(s) that may request NSSAA and/or a DN that may request a secondary A&A; the remote WTRU may be able to access a connectivity session and/or slice (e.g., a PDU session) to connect with the N3IWF to perform NSSAA and/or a secondary authentication; 0259; the remote WTRU may have registered with the network and established a security context, such as a 5G native security context; the remote WTRU may perform discovery (e.g., a discovery procedure) with the relay WTRU and decide to connect with the relay using its security context, which may be a 5G native security context; the remote WTRU may send a DCR message to the relay, for example, including one or more of the following parameters: … or the remote WTRU's NAS security capabilities; 0307; a request for a connectivity session associated with a network may be received from a remote WTRU; it may be determined that the connectivity session associated with the network is subject to a network-controlled authorization; 0130; the relay may configure the ProSe link to allow data traffic between the remote WTRU and the network/DN … the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU (e.g., if none were allocated at 7) to be used with the established connectivity session (e.g., the established PDU session); 0139; the relay WTRU may proceed with the rest of ProSe link setup (e.g., the PC5 link setup with relay), for example, using PDU session subject to secondary A&A as described with respect to FIG.2; A PDU session secondary A&A feature may include PDU session’s IP address allocation by a DN-AAA; 0179; in examples, a DN-AAA may provide a remote WTRU’s IP address to a SMF; the SMF may provide the remote WTRU’s IP address with the remote WTRU’s ID to a relay WTRU; the relay WTRU may perform IP allocation (e.g., an IP allocation procedure) for the remote WTRU (e.g., IP prefix advertisement)].
Note:
A second IP address is involved with an established connectivity session, which is subject to a network-controlled authorization in view of a request by a remote WTRU. Discovering relay involves a first IP address using remote WTRU’s NAS security capabilities.
Regarding Claim 2,
wherein the processing system is further configured to cause the UE to receive second data information associated with the protocol data unit session that indicates the second internet protocol address using the user plane protocol stack [Ferdi: 0179; in examples, a DN-AAA may provide a remote WTRU’s IP address to a SMF; the SMF may provide the remote WTRU’s IP address with the remote WTRU’s ID to a relay WTRU; the relay WTRU may perform IP allocation (e.g., an IP allocation procedure) for the remote WTRU (e.g., IP prefix advertisement)].
Regarding Claim 3,
wherein the first data information and the non-access stratum information are transmitted using a same wireless channel [Ferdi: wireless channel == ProSe (PC5); 0124; the remote WTRU may send a direct communication request (DCR) message (e.g., including a remote WTRU's subscription identity and/or network identity such as SUPI or GUTI), for example, based on the determination that the service code is associated with a DN that uses secondary A&A; 0130; the relay may configure the ProSe link to allow data traffic between the remote WTRU and the network/DN … the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU (e.g., if none were allocated at 7) to be used with the established connectivity session (e.g., the established PDU session); 0028; FIG.14 is a diagram illustrating an example of ProSe (e.g., PC5) link setup with relay using remote WTRU 5G native security context].
Regarding Claim 4,
wherein a first wireless channel carrying the non-access stratum request associated with non-access stratum signaling is associated with a first channel identifier [Ferdi: first channel identifier == GUTI; 0031; FIG.17 illustrates an example where a remote WTRU may determine whether to use the remote WTRU’s globally unique temporary identifier (GUTI) based on public land mobile network (PLMN) information received during a discovery procedure with a relay WTRU; 0032; FIG.18 illustrates an example where a relay WTRU may determine whether to use a remote WTRU's identifier (e.g., GUTI) received during a link establishment procedure (e.g., a DCR); 0033; FIG.19 illustrates an example where a relay WTRU may determine whether to use a remote WTRU's identifier (e.g., GUTI) received during a link establishment procedure (e.g., an identity request)].
Regarding Claim 5,
wherein the first information indicates the first channel identifier with the first internet protocol address [Ferdi: 0032; FIG.18 illustrates an example where a relay WTRU may determine whether to use a remote WTRU's identifier (e.g., GUTI) received during a link establishment procedure (e.g., a DCR); 0124; the remote WTRU may send a direct communication request (DCR) message (e.g., including a remote WTRU's subscription identity and/or network identity such as SUPI or GUTI), for example, based on the determination that the service code is associated with a DN that uses secondary A&A; 0126; at 5, the relay may trigger a network-controlled authorization of the remote WTRU (e.g., as described with respect to FIG.9 or FIG.14), for example, on the condition that the direct communication request (DCR) message includes an SUPI or GUTI; 0128; the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU].
Regarding Claim 6,
wherein the first channel identifier is a logical channel identifier, a radio link control channel identifier, an adaptation layer identifier, a radio link control entity identifier, a packet data convergence protocol entity identifier, or a layer two entity identifier, or any combination thereof [Ferdi: channel identifier == GUTI; 0031; FIG.17 illustrates an example where a remote WTRU may determine whether to use the remote WTRU’s globally unique temporary identifier (GUTI) based on public land mobile network (PLMN) information received during a discovery procedure with a relay WTRU; 0032; FIG.18 illustrates an example where a relay WTRU may determine whether to use a remote WTRU's identifier (e.g., GUTI) received during a link establishment procedure (e.g., a DCR)].
Regarding Claim 7,
wherein the processing system is further configured to cause the UE to receive, in response to the non-access stratum request, third information that indicates a second channel identifier associated with the protocol data unit session [Ferdi: second channel identifier == S-NSSAI; 0138; At 6, the SMF may send a NAS message (e.g., PDU session modification, establishment response, and/or remote WTRU report acknowledgment) to the relay indicating the result of the PDU session secondary A&A; the NAS message may include an identity of the remote WTRU (e.g., GPSI and/or remote user ID) and/or an EAP success or failure message; the NAS message may include addressing and/or QoS information associated with the remote WTRU, for example, in the case of successful secondary A&A; 0203; at 8, the AMF may send a response message (e.g., an NAS response message) that includes one or more of the remote WTRU ID (e.g., GPSI or SUPI), the generated key material, the S-NSSAI, and/or an indication for an NSSAA status (e.g., the current NSSAA status) based on a successful authentication procedure; the indication may indicate that NSSAA is to be performed, ongoing, or successful (e.g., if initiated or performed successfully from a previous registration) for the given S-NSSAI].
Regarding Claim 8,
wherein a second wireless channel carrying the first data information is associated with the second channel identifier [Ferdi: 0215; at 5, the AMF may update the S-NSSAI state associated with the remote WTRU in the relay WTRU context (e.g., mark the S-NSSAI as allowed for the remote WTRU) based on a successful NSSAA procedure; 0216; at 6, the AMF may send a message (e.g., an NAS message) to the relay indicating the result of the NSSAA (e.g., procedure), for example, including an identity of the remote WTRU and/or the S-NSSAI; the AMF may provide the authorization information for the remote WTRU's usage of the S-NSSAI as provided by the AAA-S].
Regarding Claim 9,
wherein the processing system is further configured to cause the UE to receive, using the user plane protocol stack, second data information associated with the protocol data unit session, wherein a second wireless channel carrying the second data information is associated with the second channel identifier [Ferdi: 0215; at 5, the AMF may update the S-NSSAI state associated with the remote WTRU in the relay WTRU context (e.g., mark the S-NSSAI as allowed for the remote WTRU) based on a successful NSSAA procedure; 0216; at 6, the AMF may send a message (e.g., an NAS message) to the relay indicating the result of the NSSAA (e.g., procedure), for example, including an identity of the remote WTRU and/or the S-NSSAI; the AMF may provide the authorization information for the remote WTRU's usage of the S-NSSAI as provided by the AAA-S; 0217; at 7, the relay may mark the remote WTRU as authorized for the S-NSSAI and/or store authorization information (e.g., any authorization information) for the remote WTRU's usage of the S- NSSAI on the condition of a successful NSSAA].
Regarding Claim 10,
wherein the first information is indicative of a first channel identifier associated with non-access stratum signaling and a second channel identifier associated with a protocol data unit transfer [Ferdi: first channel identifier == GUTI; second channel identifier == S-NSSAI; 0196; at 2, the remote WTRU may determine (e.g., from the configuration provided at 0) that the relay service code and/or type discovered at 1 may be associated with an S-NSSAI that may be subject to NSSAA (e.g., based on an indication parameter for the S-NSSAI); the remote WTRU, e.g., based on this determination, may send a DCR message including one or more of a remote WTRU's subscription or network identity (e.g., SUPI or GUTI) and/or an indication of WTRU support for NSSAA; 0203; at 8, the AMF may send a response message (e.g., an NAS response message) that includes one or more of the remote WTRU ID (e.g., GPSI or SUPI), the generated key material, the S-NSSAI, and/or an indication for an NSSAA status (e.g., the current NSSAA status) based on a successful authentication procedure].
Regarding Claim 11,
wherein the non-access stratum request comprises fourth information indicative of a first identifier of a network entity associated with the protocol data unit session, a second identifier of the UE, or both [Ferdi: identifier of a network entity == key shared with an AMF; 0259; the remote WTRU may send a DCR message to the relay, for example, including one or more of the following parameters: the remote WTRU's core network identity (e.g., a GUTI, which may be a 5G-GUTI), key set identifier (e.g., in 5G) (ngKSI) identifying the key (e.g., a KAMF, which may be a key shared with an AMF) being used, and/or the remote WTRU's NAS security capabilities; the parameters may be included in an integrity protected message (IPM), for example, protected using remote WTRU's security context, which may be 5G native security context, (e.g., with key K.sub.NASint)].
Regarding Claim 12,
wherein the non-access stratum response comprises fifth information indicative of a protocol data unit session identifier associated with the protocol data unit session [Ferdi: session identifier == session parameters (S-NSSAI); 0134; at 2, the relay may send a NAS message (e.g., a PDU session modification, establishment request, and/or a remote WTRU report), for example, to the SMF. The NAS message may include one or more of the following: remote WTRU user ID, remote WTRU addressing information, or other connectivity session (e.g., PDU session) parameters (e.g., S-NSSAI, DNN, and/or the like); 0310; in an example, a non-access stratum (NAS) message may be received from the network; the NAS message may comprise the S-NSSAI and/or an indication of an outcome of the NSSAA; on a condition that the outcome of the NSSAA is successful, the S-NSSAI may be stored, and a message may be sent to the network; the message sent to the network may comprise the S-NSSAI and an identifier of the remote WTRU].
Regarding Claim 13,
wherein the processing system is further configured to cause the UE to: transmit, via a connection establishing procedure, an indication of a UE identifier of the UE [Ferdi: 0259; the remote WTRU may send a DCR message to the relay, for example, including one or more of the following parameters: the remote WTRU's core network identity (e.g., a GUTI, which may be a 5G-GUTI), key set identifier (e.g., in 5G) (ngKSI) identifying the key (e.g., a KAMF, which may be a key shared with an AMF) being used, and/or the remote WTRU's NAS security capabilities; in examples, the remote WTRU may provide its core network identity in response to an identity request message from the relay and/or network]; and
receive, via the connection establishing procedure, an indication of a network entity identifier of a network entity associated with the user plane protocol stack [Ferdi: 0259; the remote WTRU may receive a message (e.g., a DSMC message) from the relay that may include a Krelay ID and/or a set of security parameters forwarded from the network (e.g., the AMF) that may include one or more of: a KAMF key change flag, an ngKSI identifying the KAMF to be used, or the remote WTRU's security capabilities (e.g., sent via the DCR)].
Regarding Claim 14 (Currently Amended),
A network node, comprising: an antenna system that includes one or more antennas; and a processing system coupled with the antenna system, that includes processor circuitry and memory circuitry that stores code, the processing system configured to cause the network node to:
transmit first information indicative of a first internet protocol address to a user equipment (UE); receive, on an internet protocol network, from the UE using a user plane protocol stack, a first protocol data unit comprising the first internet protocol address; transmit, to the UE, a second protocol data unit comprising the first internet protocol address [Ferdi: 0123; at 2, the remote WTRU and/or the relay WTRU may perform discovery (e.g., a discovery procedure). In examples, the remote WTRU and the relay WTRU may perform a discovery procedure whereby the remote WTRU may discover the connectivity service provided by the relay (e.g., based on a broadcasted service type and/or code); 0124; at 3, the remote WTRU may determine (e.g., from the configuration at 0) that the service code is associated with a DN that uses secondary A&A. The remote WTRU may send a direct communication request (DCR) message (e.g., including a remote WTRU's subscription identity and/or network identity such as SUPI or GUTI), for example, based on the determination that the service code is associated with a DN that uses secondary A&A; 0128; at 7, the relay may send a DCA message, for example, successful based on security establishment. The DCA message may include an indication that a PDU session with secondary A&A may be pending. The relay may allocate an IP address and/or IPv6 prefix for the remote WTRU. The relay may configure a traffic filter (e.g., as a default filter for IP or non-IP traffic) for the ProSe link (e.g., PC5 link) to prevent data traffic (e.g., any data traffic) until successful completion of a subsequent PDU session secondary A&A (e.g., as described with respect to 8)];
receive from a core network entity, a second internet protocol address and session tunnel information for a session tunnel for the UE; and receive, from the UE using the user plane protocol stack, a third protocol data unit comprising the second internet protocol address [Ferdi: 0134; at 2, the relay may send a NAS message (e.g., a PDU session modification, establishment request, and/or a remote WTRU report), for example, to the SMF; the NAS message may include one or more of the following: remote WTRU user ID, remote WTRU addressing information, or other connectivity session (e.g., PDU session) parameters (e.g., S-NSSAI, DNN, and/or the like); 0136; the relay may forward the message(s) (e.g., transparently) between the remote WTRU and the SMF; a DN-AAA may allocate and/or assign an IP address and/or IPv6 prefix for the remote WTRU during the procedure as described herein (e.g., as described with respect to FIG.8); the DN-AAA may authorize QoS parameter(s) (e.g., session AMBR) for the remote WTRU using the shared PDU session as described herein; 0170; at 1, a DN may initiate a re-authentication procedure for a remote WTRU using the shared PDU session, for example, by sending an SMF a message (e.g., a re-authorization request); the message may include an identity of the remote WTRU (e.g., GPSI) and/or addressing information (e.g., IP and/or Mac address); 0172; at 3, the SMF may initiate a PDU session secondary A&A (e.g., EAP authentication) of the remote WTRU via a relay (e.g., procedure), for example, as described with respect to FIG.3; 0179; in examples, a DN-AAA may provide a remote WTRU’s IP address to a SMF; the SMF may provide the remote WTRU’s IP address with the remote WTRU’s ID to a relay WTRU; the relay WTRU may perform IP allocation (e.g., an IP allocation procedure) for the remote WTRU (e.g., IP prefix advertisement); 0208; the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU (e.g., if none were allocated at 11) to be used with the established connectivity session (e.g., the established PDU session)].
Regarding Claim 15,
wherein the processing system is further configured to cause the network node to: receive, from the session tunnel, a fourth protocol data unit comprising the second internet protocol address; and transmit the fourth protocol data unit to the UE using the user plane protocol stack in accordance with the second internet protocol address [Ferdi: 0179; in examples, a DN-AAA may provide a remote WTRU’s IP address to a SMF; the SMF may provide the remote WTRU’s IP address with the remote WTRU’s ID to a relay WTRU; the relay WTRU may perform IP allocation (e.g., an IP allocation procedure) for the remote WTRU (e.g., IP prefix advertisement);].
Regarding Claim 16,
wherein the processing system is further configured to cause the network node to output the first protocol data unit to a core network service in accordance with the first protocol data unit comprising the first internet protocol address [Ferdi: 0126; at 5, the relay may trigger a network-controlled authorization of the remote WTRU (e.g., as described with respect to FIG.9 or FIG.14), for example, on the condition that the direct communication request (DCR) message includes an SUPI or GUTI; 0128; the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU; 0135; at 3, the SMF may determine, e.g., based on subscription information, that the requested DN may be subject to secondary A&A and/or may trigger a PDU session secondary A&A of the remote WTRU via relay; 0136; at 4, the remote WTRU may perform a PDU session secondary A&A via a relay. Authentication message(s) may be transported using one or more NAS messages between the SMF and the relay. The one or more NAS messages may include an identity of the remote WTRU (e.g., GPSI, remote user ID, and/or the like) to indicate to the relay that authentication message(s) are for the remote WTRU. The relay may forward the message(s) (e.g., transparently) between the remote WTRU and the SMF].
Regarding Claim 17,
wherein the processing system is further configured to cause the network node to obtain, from a core network service, the second protocol data unit comprising the first internet protocol address [Ferdi: core network service == network-controlled authorization; 0126; at 5, the relay may trigger a network-controlled authorization of the remote WTRU (e.g., as described with respect to FIG.9 or FIG.14), for example, on the condition that the DCR message includes an SUCI or GUTI; 0128; at 7, the relay may send a DCA message, for example, successful based on security establishment. The DCA message may include an indication that a PDU session with secondary A&A may be pending; the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU].
Regarding Claim 18,
wherein the processing system is further configured to cause the network node to output, to the session tunnel, the third protocol data unit in accordance with the second internet protocol address [Ferdi: 0307; a request for a connectivity session associated with a network may be received from a remote WTRU; it may be determined that the connectivity session associated with the network is subject to a network-controlled authorization; 0130; the relay may configure the ProSe link to allow data traffic between the remote WTRU and the network/DN … the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU (e.g., if none were allocated at 7) to be used with the established connectivity session (e.g., the established PDU session); 0139; the relay WTRU may proceed with the rest of ProSe link setup (e.g., the PC5 link setup with relay), for example, using PDU session subject to secondary A&A as described with respect to FIG.2; A PDU session secondary A&A feature may include PDU session’s IP address allocation by a DN-AAA.
Regarding Claim 19,
wherein the first protocol data unit and the third protocol data unit are received via a first wireless channel, and the second protocol data unit is transmitted via the first wireless channel [Ferdi: wireless channel == ProSe (PC5); 0124; the remote WTRU may send a direct communication request (DCR) message (e.g., including a remote WTRU's subscription identity and/or network identity such as SUPI or GUTI), for example, based on the determination that the service code is associated with a DN that uses secondary A&A; 0130; the relay may configure the ProSe link to allow data traffic between the remote WTRU and the network/DN … the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU (e.g., if none were allocated at 7) to be used with the established connectivity session (e.g., the established PDU session); 0028; FIG.14 is a diagram illustrating an example of ProSe (e.g., PC5) link setup with relay using remote WTRU 5G native security context].
Regarding Claim 20,
wherein the first protocol data unit is received with a first channel identifier, the second protocol data unit is transmitted with the first channel identifier [Ferdi: 0032; FIG.18 illustrates an example where a relay WTRU may determine whether to use a remote WTRU's identifier (e.g., GUTI) received during a link establishment procedure (e.g., a DCR); 0124; the remote WTRU may send a direct communication request (DCR) message (e.g., including a remote WTRU's subscription identity and/or network identity such as SUPI or GUTI), for example, based on the determination that the service code is associated with a DN that uses secondary A&A; 0126; at 5, the relay may trigger a network-controlled authorization of the remote WTRU (e.g., as described with respect to FIG.9 or FIG.14), for example, on the condition that the direct communication request (DCR) message includes an SUPI or GUTI; 0128; the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU], and
the third protocol data unit is received with a second channel identifier [Ferdi: second channel identifier == S-NSSAI; 0138; At 6, the SMF may send a NAS message (e.g., PDU session modification, establishment response, and/or remote WTRU report acknowledgment) to the relay indicating the result of the PDU session secondary A&A; the NAS message may include an identity of the remote WTRU (e.g., GPSI and/or remote user ID) and/or an EAP success or failure message; the NAS message may include addressing and/or QoS information associated with the remote WTRU, for example, in the case of successful secondary A&A; 0203; at 8, the AMF may send a response message (e.g., an NAS response message) that includes one or more of the remote WTRU ID (e.g., GPSI or SUPI), the generated key material, the S-NSSAI, and/or an indication for an NSSAA status (e.g., the current NSSAA status) based on a successful authentication procedure; the indication may indicate that NSSAA is to be performed, ongoing, or successful (e.g., if initiated or performed successfully from a previous registration) for the given S-NSSAI].
Regarding Claim 21,
wherein the processing system is further configured to cause the network node to: output the first protocol data unit to the core network entity in accordance with the first channel identifier [Ferdi: 0032; FIG.18 illustrates an example where a relay WTRU may determine whether to use a remote WTRU's identifier (e.g., GUTI) received during a link establishment procedure (e.g., a DCR); 0124; the remote WTRU may send a direct communication request (DCR) message (e.g., including a remote WTRU's subscription identity and/or network identity such as SUPI or GUTI), for example, based on the determination that the service code is associated with a DN that uses secondary A&A; 0126; at 5, the relay may trigger a network-controlled authorization of the remote WTRU (e.g., as described with respect to FIG.9 or FIG.14), for example, on the condition that the direct communication request (DCR) message includes an SUPI or GUTI; 0128; the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU]; and
output, the third protocol data unit to the session tunnel in accordance with the second channel identifier [Ferdi: second channel identifier == S-NSSAI; 0138; At 6, the SMF may send a NAS message (e.g., PDU session modification, establishment response, and/or remote WTRU report acknowledgment) to the relay indicating the result of the PDU session secondary A&A; the NAS message may include an identity of the remote WTRU (e.g., GPSI and/or remote user ID) and/or an EAP success or failure message; the NAS message may include addressing and/or QoS information associated with the remote WTRU, for example, in the case of successful secondary A&A; 0203; at 8, the AMF may send a response message (e.g., an NAS response message) that includes one or more of the remote WTRU ID (e.g., GPSI or SUPI), the generated key material, the S-NSSAI, and/or an indication for an NSSAA status (e.g., the current NSSAA status) based on a successful authentication procedure; the indication may indicate that NSSAA is to be performed, ongoing, or successful (e.g., if initiated or performed successfully from a previous registration) for the given S-NSSAI].
Regarding Claim 22,
wherein the first information is indicative of the first channel identifier [Ferdi: 0032; FIG.18 illustrates an example where a relay WTRU may determine whether to use a remote WTRU's identifier (e.g., GUTI) received during a link establishment procedure (e.g., a DCR); 0124; the remote WTRU may send a direct communication request (DCR) message (e.g., including a remote WTRU's subscription identity and/or network identity such as SUPI or GUTI), for example, based on the determination that the service code is associated with a DN that uses secondary A&A; 0126; at 5, the relay may trigger a network-controlled authorization of the remote WTRU (e.g., as described with respect to FIG.9 or FIG.14), for example, on the condition that the direct communication request (DCR) message includes an SUPI or GUTI].
Regarding Claim 23,
wherein the processing system is further configured to cause the network node to transmit, in response to the second protocol data unit, a fifth protocol data unit that indicates the second channel identifier [Ferdi: second channel identifier == S-NSSAI; 0138; At 6, the SMF may send a NAS message (e.g., PDU session modification, establishment response, and/or remote WTRU report acknowledgment) to the relay indicating the result of the PDU session secondary A&A; the NAS message may include an identity of the remote WTRU (e.g., GPSI and/or remote user ID) and/or an EAP success or failure message; the NAS message may include addressing and/or QoS information associated with the remote WTRU, for example, in the case of successful secondary A&A; 0203; at 8, the AMF may send a response message (e.g., an NAS response message) that includes one or more of the remote WTRU ID (e.g., GPSI or SUPI), the generated key material, the S-NSSAI, and/or an indication for an NSSAA status (e.g., the current NSSAA status) based on a successful authentication procedure; the indication may indicate that NSSAA is to be performed, ongoing, or successful (e.g., if initiated or performed successfully from a previous registration) for the given S-NSSAI].
Regarding Claim 24,
wherein the first channel identifier is a logical channel identifier, a radio link control channel identifier, an adaptation layer identifier, a radio link control entity identifier, a packet data convergence protocol entity identifier, or a layer two entity identifier, or any combination thereof [Ferdi: channel identifier == GUTI; 0031; FIG.17 illustrates an example where a remote WTRU may determine whether to use the remote WTRU’s globally unique temporary identifier (GUTI) based on public land mobile network (PLMN) information received during a discovery procedure with a relay WTRU; 0032; FIG.18 illustrates an example where a relay WTRU may determine whether to use a remote WTRU's identifier (e.g., GUTI) received during a link establishment procedure (e.g., a DCR)].
Regarding Claim 25,
wherein the first information is indicative of a first channel identifier associated with non-access stratum signaling and a second channel identifier associated with a protocol data unit transfer [Ferdi: first channel identifier == GUTI; second channel identifier == S-NSSAI; 0196; at 2, the remote WTRU may determine (e.g., from the configuration provided at 0) that the relay service code and/or type discovered at 1 may be associated with an S-NSSAI that may be subject to NSSAA (e.g., based on an indication parameter for the S-NSSAI); the remote WTRU, e.g., based on this determination, may send a DCR message including one or more of a remote WTRU's subscription or network identity (e.g., SUPI or GUTI) and/or an indication of WTRU support for NSSAA; 0203; at 8, the AMF may send a response message (e.g., an NAS response message) that includes one or more of the remote WTRU ID (e.g., GPSI or SUPI), the generated key material, the S-NSSAI, and/or an indication for an NSSAA status (e.g., the current NSSAA status) based on a successful authentication procedure].
Regarding Claim 26,
wherein the processing system is further configured to cause the network node to: receive, via a connection establishing procedure, an indication of a UE identifier of the UE [Ferdi: 0259; the remote WTRU may send a DCR message to the relay, for example, including one or more of the following parameters: the remote WTRU's core network identity (e.g., a GUTI, which may be a 5G-GUTI), key set identifier (e.g., in 5G) (ngKSI) identifying the key (e.g., a KAMF, which may be a key shared with an AMF) being used, and/or the remote WTRU's NAS security capabilities; in examples, the remote WTRU may provide its core network identity in response to an identity request message from the relay and/or network]; and
transmit, via the connection establishing procedure, an indication of a network entity identifier of a network entity associated with the user plane protocol stack [Ferdi: 0259; the remote WTRU may receive a message (e.g., a DSMC message) from the relay that may include a Krelay ID and/or a set of security parameters forwarded from the network (e.g., the AMF) that may include one or more of: a KAMF key change flag, an ngKSI identifying the KAMF to be used, or the remote WTRU's security capabilities (e.g., sent via the DCR)].
Regarding Claim 27,
wherein the first information is indicative of a first channel identifier associated with non-access stratum signaling and a second channel identifier associated with a protocol data unit transfer [Ferdi: first channel identifier == GUTI; second channel identifier == S-NSSAI; 0196; at 2, the remote WTRU may determine (e.g., from the configuration provided at 0) that the relay service code and/or type discovered at 1 may be associated with an S-NSSAI that may be subject to NSSAA (e.g., based on an indication parameter for the S-NSSAI); the remote WTRU, e.g., based on this determination, may send a DCR message including one or more of a remote WTRU's subscription or network identity (e.g., SUPI or GUTI) and/or an indication of WTRU support for NSSAA; 0203; at 8, the AMF may send a response message (e.g., an NAS response message) that includes one or more of the remote WTRU ID (e.g., GPSI or SUPI), the generated key material, the S-NSSAI, and/or an indication for an NSSAA status (e.g., the current NSSAA status) based on a successful authentication procedure].
Regarding Claim 28,
wherein the user plane protocol stack comprises a physical layer, a medium access control sub-layer, a radio link control sub-layer, a packet data convergence protocol sub-layer, a service data adaptation protocol sub-layer, or a security sub-layer, or any combination thereof [Ferdi: a medium access control sub-layer == L2; 0144; the SMF may release the user plane (UP) resource(s) used by the PDU session including the PDU session context; 0083; the UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices; the UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like; 0090; a ProSe Layer 3 (L3) WTRU-to-network relay (e.g., a 5G ProSe L3 WTRU-to-network relay) may be provided and/or supported; L2 and L3 WTRU-to-Network (U2NW) relay(s) may be provided and/or supported; 0092; a PDU session secondary authentication for a remote WTRU via a Layer 3 relay may be provided and/or supported. Network-controlled authorization of a remote WTRU to access via Layer 3 WTRU-to-Network relay may be provided and/or supported].
Regarding Claim 29, which recites the same claim limitations as those in claim 1 above, the same rationale of rejection as presented in claim 1 is applicable.
Regarding Claim 30, which recites the same claim limitations as those in claim 14 above, the same rationale of rejection as presented in claim 14 is applicable.
Response to Arguments
Applicant's arguments filed 8/4/26 have been fully considered but they are not persuasive.
Applicant argues regarding claims 1, 14, 29, and 30 on pages 9-10 of the Remarks section that Ferdi’s sending of the DCR message including remote WTRU’s subscription identity and/or network identity happens before the relay allocating an IP address. Second, the communication between relay and remote WTRU is through ProSe connection and not on an internet protocol network. Third, Ferdi’s discussion of a NAS message does not disclose that NAS message is sent on an internet protocol network. Therefore, Ferdi does not teach “transmit a non-access stratum request that indicates the first internet protocol address on an internet protocol network to a core network service to establish a protocol data unit session using a user plane protocol stack.”
Examiner’s Response:
The claim limitation merely recites “transmit a non-access stratum request that indicates the first internet protocol address on an internet protocol network to a core network service to establish a protocol data unit session using a user plane protocol stack.” First, a NAS request merely indicates to a core network service about the first IP address on an internet protocol network to establish a PDU session. Second, actual allocation or even use of the first IP address is not necessarily at the time of the NAS request from UE but may happen at a later time as appropriate for a PDU session. Third, an IP address, when used in a PDU session for addressing or routing, is inherently associated with an IP network. Fourth, the claim does not recite that the NAS request is transmitted on an IP network.
Given this claim interpretive context, Ferdi describes how a remote WTRU performs discovery procedure for a connectivity service (i.e. a PDU session) provided by a relay [Ferdi: 0123]. As part of this discovery process, the remote WTRU may send a direct communication request (DCR) message (e.g., including a remote WTRU's subscription identity and/or network identity such as SUPI or GUTI), for example, based on the determination that the service code is associated with a DN that uses secondary A&A [Ferdi: 0124]. Now, the relay may determine that a connectivity session subject to secondary A&A is to be used to meet the remote WTRU’s request, for example, based on receiving the DCR message [Ferdi: 0125]. The relay may trigger a network-controlled authorization of the remote WTRU (e.g., as described with respect to FIG.9 or FIG.14), for example, on the condition that the DCR message includes an SUCI or GUTI [Ferdi: 0126]. After successful network-controlled authorization, the relay may send a DCA message, for example, successful based on security establishment. The DCA message may include an indication that a PDU session with secondary A&A may be pending … relay may allocate an IP address and/or IPv6 prefix for the remote WTRU [Ferdi: 0128]. Moreover, the relay may configure the ProSe link to allow data traffic between the remote WTRU and the network/DN (e.g., remove the filter configured at 7) … the relay may allocate an IP address and/or IPv6 prefix for the remote WTRU (e.g., if none were allocated at 7) to be used with the established connectivity session (e.g., the established PDU session).
In Ferdi, a remote WTRU for establishing a PDU session goes through a discovery process with a relay and provides its subscription identity and/or network identity, such as SUPI or GUTI. This serves as an indication to a relay to establish a PDU session by performing network-controlled authorization and an allocation of IP address and/or IPv6 prefix for the remote WTRU. In other words, a remote WTRU’s request indicates to a relay and by extension a DN (i.e. core network service) to establish a PDU session with an IP address (i.e. the first IP address). An IP address so used in a PDU session is inherently associated with an IP network. Thus, Ferdi teaches the limitation at issue above.
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 SAAD A WAQAS whose telephone number is (571)270-5642. The examiner can normally be reached 8:30 - 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, Marcus Smith can be reached at (571) 270-1096. 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.
SAAD A. WAQAS
Primary Examiner
Art Unit 2468
/Saad A. Waqas/Primary Examiner, Art Unit 2468
