COMMUNICATION METHOD, NODE, DEVICE, COMMUNICATION SYSTEM, AND STORAGE MEDIUM

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 . Claim Rejections - 35 USC § 103 The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action: A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made. 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 nonobviousness. 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 – 6, 8, 9, 17, 18 and 29 are rejected under 35 U.S.C. 103 as being unpatentable over Yiu (US 2022/0078686 A1) in view of Bollapalli et al (US 2018/0063764 A1). Claim 1 (similarly Claim 29). Yiu shows a communication method (abstract), comprising: determining a target device according to a trigger message from a first node ([0032]: the UE may trigger handover (synchronization to target cell and random access) to the target cell); sending a visit message to the target device ([0100]: the UE may be triggered by the AMF with which the UE is registered by interacting with the NSSF, which may lead to a change of AMF… may communicate with another NSSF in a visited network via an N31 reference point; [0174]: a NAS Signaling Transport function for transporting or rerouting NAS messages between UE and AMF), wherein the visit message is used for instructing the target device to perform a corresponding operation ([0103]: interfaces/reference points may include an N5g-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network, and an N31 reference point between the NSSF in the visited network and the NSSF in the home network; [0209]: the source device can communicate with the target device of a target cell to reserve one or more resources associated with the target cell for the UE); and sending execution result information of the target device to the first node ([0209]: the source device can send an early handover request to the target cell and receive a handover acknowledgment from the target cell in response to the target cell accepting the handover; [0211]: the transmitting the signal can include transmitting a conditional HO command for a conditional handover of the UE to the target cell, where the conditional HO command can include a condition for the UE exiting the conditional handover).Yiu does not expressly describe that the communication method is applied to the second node, which comprises a base station or an access point, and wherein the first node comprises a core network and the target device comprises a device with a tag.Bollapalli shows, in figure 1, features of a base station sending setup information to a target device ([0037]: the UE 110 may obtain from information received from the network node 160 during setup of the communication session), the setup information instructs the target device to perform a corresponding operation ([0037]: session description protocol (SDP) information that indicates the single Codec used for existing dialog over the serving access and other parameters (e.g. the SDP information may be provided as a series of parameters, such as: m=audio [port number] RTP/SAVP 0 (a new SRTP key used for secure access over the target access)) and sending execution result information of the target device to the core network ([0037]: the specific parameters, information, and header fields identified above are provided for purposes of illustration, rather than by way of limitation, and that other header information and/or configurations may be utilized to establish a new media path for the handover of a communication session depending on a configuration of the network node 160, the core network 170, and/or the UE 110) wherein the target device comprises a tag ([0037]: includes a To-tag set to the To-tag of the existing dialog over the serving access, includes a From-tag set to the From-tag of the existing dialog over the serving access, which the UE 110 may obtain from information received from the network node 160 during setup of the communication session; [0040]: upon successful registration of the user/UE with the core network (e.g. including registration of the UE with the application server (AS)), the network entities (e.g. the AS, the core network, and the access SBC/P-CSCF) may transmit a series of SIP 200 OK messages 315 acknowledging the successful registration of the user/UE with the core network).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the visit message handling process of Yiu to that involving a base station, a core network and a target device with a tag as taught by Bollapalli to facilitate handovers between different access networks, specifically WiFi networks and cellular networks.Claim 2. Yiu shows the method of claim 1, wherein the trigger message comprises at least one of the following information about at least one device: a complete identifier or a partial identifier of the device ([0204]: a received signal from a source cell can be identified); all or part of data stored in the device ([0095]: this information may be stored at the NEF 523 as structured data, or at a data storage NF using standardized interfaces wherein the stored information can then be re-exposed by the NEF 523 to other NFs and AFs, and/or used for other purposes such as analytics); a change instruction for a selected flag or an inventory flag ([0100]: communicate with another NSSF 529 in a visited network via an N31 reference point); a selection message of the device ([0182]: the UDP/IP 952 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows); capability information of the device ([0184]: a logical instantiation of the CN 420 may be referred to as a network slice 1001, and individual logical instantiations of the CN 420 may provide specific network capabilities and network characteristics); auxiliary information of the device (n/a); an operation type ([0135]: the battery parameters may be used to determine actions that the platform may perform, such as transmission frequency, network operation, sensing frequency, and the like); operation content ([0135]: the battery parameters may be used to determine actions that the platform may perform, such as transmission frequency, network operation, sensing frequency, and the like); a password (n/a); an operation message ([0135]: the battery parameters may be used to determine actions that the platform may perform, such as transmission frequency, network operation, sensing frequency, and the like); a connection request ([0093]: upon request from an application server, the 5GC may trigger a specific application in the UE); resource information for transmitting data ([0188]: slice awareness in the NG-RAN is introduced at the PDU session level by indicating the S-NSSAI corresponding to a PDU session in all signaling that includes PDU session resource information); connection information ([0169]: RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release); or bearer information ([0080]: the S3 reference point between the MMEs 421 and the SGSN 425 may enable user and bearer information exchange for inter-3GPP access network mobility in idle and/or active states). Claim 3. Yiu shows the method of claim 1, after determining the target device according to the trigger message from the first node, further comprising: sending information about the target device to the first node ([0209]: the source device can send an early handover request to the target cell and receive a handover acknowledgment from the target cell in response to the target cell accepting the handover); wherein the information about the target device comprises at least one of: a complete identifier or a partial identifier of the target device ([0204]: a received signal from a source cell can be identified); all or part of data stored in the target device ([0095]: this information may be stored at the NEF 523 as structured data, or at a data storage NF using standardized interfaces wherein the stored information can then be re-exposed by the NEF 523 to other NFs and AFs, and/or used for other purposes such as analytics); a random code corresponding to the target device ([0206]: if the UE does not exit the conditional handover, the UE can perform synchronization and random access operations with a target device of the target cell in response to a measurement on the target cell satisfying a second measurement threshold); an instruction of an access result of the target device ([0032]: when the HO execution threshold condition is met, the UE may trigger handover (synchronization to target cell and random access) to the target cell); capability information of the target device ([0184]: a logical instantiation of the CN 420 may be referred to as a network slice 1001, and individual logical instantiations of the CN 420 may provide specific network capabilities and network characteristics); auxiliary information of the target device (n/a); a feedback message of the target device ([0133]: channel quality feedback); a connection request for the target device ([0093]: upon request from an application server, the 5GC may trigger a specific application in the UE); or resource information for transmitting data ([0188]: slice awareness in the NG-RAN is introduced at the PDU session level by indicating the S-NSSAI corresponding to a PDU session in all signaling that includes PDU session resource information). Claim 4. Yiu shows the method of claim 1, before sending the visit message to the target device, further comprising: receiving a visit instruction message from the first node ([0097]: the PCF 526 may communicate with the AMF 521 via an N15 reference point between the PCF 526 and the AMF 521, which may include a PCF 526 in a visited network and the AMF 521 in case of roaming scenarios), wherein the visit instruction message is used for instructing an operation performed on the target device ([0097]: the system 500 and/or CN 520 may also include an N24 reference point between the PCF 526 (in the home network) and a PCF 526 in a visited network); wherein the visit instruction message comprises at least one of the following information about the target device: a complete identifier or a partial identifier of the target device ([0204]: a received signal from a source cell can be identified); a random code corresponding to the target device ([0206]: if the UE does not exit the conditional handover, the UE can perform synchronization and random access operations with a target device of the target cell in response to a measurement on the target cell satisfying a second measurement threshold); an operation type ([0135]: the battery parameters may be used to determine actions that the platform may perform, such as transmission frequency, network operation, sensing frequency, and the like); operation content ([0135]: the battery parameters may be used to determine actions that the platform may perform, such as transmission frequency, network operation, sensing frequency, and the like); a password (n/a); an operation message ([0135]: the battery parameters may be used to determine actions that the platform may perform, such as transmission frequency, network operation, sensing frequency, and the like); a connection request for the target device ([0093]: upon request from an application server, the 5GC may trigger a specific application in the UE); resource information for transmitting data ([0188]: slice awareness in the NG-RAN is introduced at the PDU session level by indicating the S-NSSAI corresponding to a PDU session in all signaling that includes PDU session resource information); capability information of the target device ([0184]: a logical instantiation of the CN 420 may be referred to as a network slice 1001, and individual logical instantiations of the CN 420 may provide specific network capabilities and network characteristics); auxiliary information of the target device (n/a); connection information of the target device ([0169]: RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release); or bearer information of the target device ([0080]: the S3 reference point between the MMEs 421 and the SGSN 425 may enable user and bearer information exchange for inter-3GPP access network mobility in idle and/or active states). Claim 5. Yiu shows the method of claim 1, wherein the execution result information comprises at least one of: a complete identifier or a partial identifier of the target device ([0204]: a received signal from a source cell can be identified); all or part of data stored in the target device ([0095]: this information may be stored at the NEF 523 as structured data, or at a data storage NF using standardized interfaces wherein the stored information can then be re-exposed by the NEF 523 to other NFs and AFs, and/or used for other purposes such as analytics); a random code corresponding to the target device ([0206]: if the UE does not exit the conditional handover, the UE can perform synchronization and random access operations with a target device of the target cell in response to a measurement on the target cell satisfying a second measurement threshold); an instruction of an access result of the target device ([0032]: when the HO execution threshold condition is met, the UE may trigger handover (synchronization to target cell and random access) to the target cell); auxiliary information of the target device (n/a); a feedback message of the target device ([0133]: channel quality feedback); an operation type ([0135]: the battery parameters may be used to determine actions that the platform may perform, such as transmission frequency, network operation, sensing frequency, and the like); an execution result ([0210]: determining the conditional HO command can also include determining or generating a signal that includes and/or is based on the conditional HO command that includes the HO execution threshold); read content ([0098]: the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 527, PCF 526, and NEF 523 to access a particular set of the stored data, as well as to read, update (e.g. add, modify), delete, and subscribe to notification of relevant data changes in the UDR); a connection request for the target device ([0093]: upon request from an application server, the 5GC may trigger a specific application in the UE); resource information for transmitting data ([0188]: slice awareness in the NG-RAN is introduced at the PDU session level by indicating the S-NSSAI corresponding to a PDU session in all signaling that includes PDU session resource information); or an application layer data packet ([0073]: the SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages). Claim 6. Yiu shows the method of claim 1, wherein the target device is in one of the following states: an idle state in which the target device does not support a data transmission ([0133]: if there is no data traffic activity for an extended period of time, then the platform 700 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.); an access state in which the target device supports an access operation and does not support a visit operation ([0191]: admission or rejection of access to a slice may depend on factors such as support for the slice, availability of resources, support of the requested service by NG-RAN); a connected state in which the target device supports a visit operation ([0097]: the PCF 526 may communicate with the AMF 521 via an N15 reference point between the PCF 526 and the AMF 521, which may include a PCF 526 in a visited network and the AMF 521 in case of roaming scenarios); an inactive state in which the target device does not operate ([0133]: where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity); or a silent state in which the target device enters a power saving mode ([0133]: if the platform 700 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity wherein during this state, the platform 700 may power down for brief intervals of time and thus save power). Claim 8. Yiu shows the method of claim 1, before sending the visit message to the target device, further comprising: sending a request message to the target device ([0165] – [0167]: process requests from and provide indications to an instance of PDCP; [0209]: the source device can send an early handover request to the target cell and receive a handover acknowledgment from the target cell in response to the target cell accepting the handover), wherein the request message is used for instructing the target device to generate a random number ([0206]: if the UE does not exit the conditional handover, the UE can perform synchronization and random access operations with a target device of the target cell in response to a measurement on the target cell satisfying a second measurement threshold); and receiving the random number returned by the target device (see above). Claim 9. Yiu shows the method of claim 1, wherein the visit message comprises instruction information of at least one of a read operation ([0098]: the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 527, PCF 526, and NEF 523 to access a particular set of the stored data, as well as to read, update (e.g. add, modify), delete, and subscribe to notification of relevant data changes in the UDR); a write operation ([0098]: the Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 527, PCF 526, and NEF 523 to access a particular set of the stored data, as well as to read, update (e.g. add, modify), delete, and subscribe to notification of relevant data changes in the UDR); an inactivation operation ([0133]: then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity); a lock operation ([0156]: a delay-locked loop (DLL)); a visit operation ([0097]: the system 500 and/or CN 520 may also include an N24 reference point between the PCF 526 (in the home network) and a PCF 526 in a visited network); a block write operation (n/a); or a block erase operation (n/a). ---------- ---------- ---------- Claim 17. Yiu shows a communication method (abstract), comprising: receiving a visit message from a second node ([0097]: the PCF 526 may communicate with the AMF 521 via an N15 reference point between the PCF 526 and the AMF 521, which may include a PCF 526 in a visited network and the AMF 521 in case of roaming scenarios… the system 500 and/or CN 520 may also include an N24 reference point between the PCF 526 (in the home network) and a PCF 526 in a visited network), and performing a corresponding operation according to the visit message ([0100]: the selection of a set of network slice instances for the UE 501 may be triggered by the AMF 521 with which the UE 501 is registered by interacting with the NSSF 529, which may lead to a change of AMF 521; [0103]: interfaces/reference points may include an N5g-EIR service-based interface exhibited by a 5G-EIR, an N27 reference point between the NRF in the visited network and the NRF in the home network, and an N31 reference point between the NSSF in the visited network and the NSSF in the home network; [0209]: the source device can communicate with the target device of a target cell to reserve one or more resources associated with the target cell for the UE); and sending execution result information to the second node ([0209]: the source device can send an early handover request to the target cell and receive a handover acknowledgment from the target cell in response to the target cell accepting the handover; [0211]: the transmitting the signal can include transmitting a conditional HO command for a conditional handover of the UE to the target cell, where the conditional HO command can include a condition for the UE exiting the conditional handover).Yiu does not expressly describe that the communication method is applied to the second node, which comprises a base station or an access point, and wherein the first node comprises a core network and the target device comprises a device with a tag.Bollapalli shows, in figure 1, features of a base station sending setup information to a target device ([0037]: the UE 110 may obtain from information received from the network node 160 during setup of the communication session), the setup information instructs the target device to perform a corresponding operation ([0037]: session description protocol (SDP) information that indicates the single Codec used for existing dialog over the serving access and other parameters (e.g. the SDP information may be provided as a series of parameters, such as: m=audio [port number] RTP/SAVP 0 (a new SRTP key used for secure access over the target access)) and sending execution result information of the target device to the core network ([0037]: the specific parameters, information, and header fields identified above are provided for purposes of illustration, rather than by way of limitation, and that other header information and/or configurations may be utilized to establish a new media path for the handover of a communication session depending on a configuration of the network node 160, the core network 170, and/or the UE 110) wherein the target device comprises a tag ([0037]: includes a To-tag set to the To-tag of the existing dialog over the serving access, includes a From-tag set to the From-tag of the existing dialog over the serving access, which the UE 110 may obtain from information received from the network node 160 during setup of the communication session; [0040]: upon successful registration of the user/UE with the core network (e.g. including registration of the UE with the application server (AS)), the network entities (e.g. the AS, the core network, and the access SBC/P-CSCF) may transmit a series of SIP 200 OK messages 315 acknowledging the successful registration of the user/UE with the core network).It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the visit message handling process of Yiu to that involving a base station, a core network and a target device with a tag as taught by Bollapalli to facilitate handovers between different access networks, specifically WiFi networks and cellular networks. Claim 18. Yiu shows the method of claim 17, wherein a target device is in one of the following states: an idle state in which the target device does not support a data transmission ([0133]: the platform may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.); an access state in which the target device supports an access operation and does not support a visit operation (n/a); a connected state in which the target device supports a visit operation ([0100]: the NSSF 529 may interact with the AMF 521 via an N22 reference point between AMF 521 and NSSF 529, and may communicate with another NSSF 529 in a visited network via an N31 reference point); an inactive state in which the target device does not operate ([0133]: if the platform is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity); or a silent state in which the target device enters a power saving mode ([0133]: an additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval). ========== ========== ========== Response to Arguments Applicant’s arguments with respect to claims 1, 17 and 29 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument – see Bollapalli. The applicant is welcome to contact the examiner to discuss the case. ---------- ---------- ---------- Allowable Subject Matter Claims 7, 10, 11, 12, 19, 20, 21, 22 and 23 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims. ========== ========== ========== 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 Xavier Szewai Wong whose telephone number is 571.270.1780. The examiner can normally be reached on 11:30 am - 8:30 pm Mon to Fri. 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, Jeffrey Rutkowski can be reached on 571.270.1215. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /XAVIER S WONG/Primary Examiner, Art Unit 2415 23rd September 2026