Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Response to Arguments
Applicant’s Amendments and Arguments filed 01/08/2026 have been considered for examination. Claims 1-20 are pending in the instant application.
With regard to the 103 rejections, Applicant’s arguments filed 01/08/2026 (see pages 11-15 of Remarks) in view of the amendments have been fully considered but are not persuasive. Examiner notes that Applicant’s amendments necessitated the new ground(s) of rejection presented in the instant Office Action.
Regarding claims 1, Applicant argued:
Regarding the amended claim 1, Paul and Chin fail to disclose “triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability …” which requires that the PDU session be a 5GS PDU session and the medication procedure of the triggered PDU session be performed, in an asynchronous manner, in response to the MBS session being activated.
Further, Kim discloses converting 5GS multicast to evolved packet system (EPS) unicast as EPS does not support MBS. To the extent Kim mentions a "Linked PDU Session" by a combination of DNN and S-NSSAI, the aim is still EPS interworking. Applicant notes that the EPS is a component of a 4G system, and is not part of a SGS. In contrast, amended claim 1 requires maintaining service in SGS when the SGS target base station (NG-RAN) lacks MBS capability (e.g., amended claim 1 recites "the target base station being a node operating in a 5th-Generation System (SGS)" and "the PDU session being a SGS PDU session"). Moreover, Kim is completely silent on performing, in an asynchronous manner relative to the PDU session establishment, a modification procedure of the triggered PDU session in response to the MBS session being activated, as recited in amended claim 1.
Thus, combination Paul, Chin, and Kim fail to disclose the amended claim 1.
In response to Applicant’s argument, Examiner respectfully disagrees.
Applicant argues that amended independent claim 1, recited as "triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, … wherein no MBS session is established on the target base station side," is failed to disclose by Paul, Chin, and Kim,
In the previous office action, Paul and Chin does not disclose regarding this part and Kim disclose this part. In the argument, Applicant argue that although 5G MBS session is performed by EPS unicast system and EPS is a component of a 4G system, Kim fails to disclose the amended claim 1, recited in the above.
Instead, Sung-pyo Hong (USPub. No.: US 20230082017 A1, hereinafter, “Hong”) teaches that in Paragraph [0255], [0257], [0261], [0294], [0307], and [0303]-[0304], when the target based station does not support the MBS session, as described in [0307], the target base station determine a transmission scheme or cast type (e.g. multicast/broadcast transmission, unicast transmission) for the corresponding MBS session requested by the source base station. Due to lack MBS capability as described [0255] and [0257], it supports the MBS session by using unicast session. Here, the unicast session is configured as a dedicated PDU session mapped to one-to-one to the MBS session. As described in Paragraph [0304], it is performed by the PDU session establishment based on the MBS context information (described in Paragraph [0294]).
Thus, clearly, combination of Paul, Chin, and Hong disclose the amended claim 1.
By the similar reasoning, the amended claim 10 and 19 are disclosed by combination Paul, Chin and Hong.
Since this amendment give a new scope or a limitation for the claims, the new rejection is made in the present office action in the below.
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.
Claims 1, 6-10, 15-18, and 19 are rejected under U.S.C. 103 as being unpatentable over Schliwa-Bertling, Paul and et. al. (Int. Pub. No.: WO 2021234635 A1, hereinafter “Paul”) in a view of Chin, Hengli and et. al. (Int. Pub. No.: WO 2022028546 A1, hereinafter “Chin”) and further in a view of Sung-pyo Hong (USPub. No.: US 20230082017 A1, hereinafter, “Hong”).
Regarding claim 1, Paul teaches that a method for implementing multi-cast broadcast service handover, applied to a user equipment, (Paul, in Fig. 6 and in Paragraph [0074] and [0082], teaches that in the step 1, the source NG-RAN (Next Generation Radio Access Network) sends an Xn Handover Request to Target NG-RAN and the UE (User Equipment) Context contains MB (Multicast Broadcast) Session information. In the step 5, the source NG-RAN sends a Uu Handover Command (MBS handover) to UE and the UE starts to access and synchronizes to the new cell. Therefore, it is clear that the multicast broadcast service (MBS) handover can be applied to the UE.) a source base station that the user equipment accesses before handover supporting a multi- cast broadcast service (MBS), and the user equipment, before handover, having established and not activated an MBS session at the source base station, (Paul, in Paragraph [0057], teaches that systems and methods for session continuity of Multicast Broadcast (MB) Sessions are provided. In some embodiments, a method performed by a base station for session continuity of MB Sessions includes at least one of: providing at least one MB Session to a wireless device connected in 5G; determining that the wireless device is handed over to a target Next Generation Radio Access Network (NG-RAN) and providing session continuity of the at least one MB Session to the wireless device. In Paragraph [0059], Paul teaches that Resources in Target NG-RAN may optionally be established in the Xn Handover Execution phase (see step 10 description of "Option 2''). This Option 2 may be an alternative way to do it, but it may also be a complementary way to do it, e.g., when moving from a Source NG-RAN that does not support 5MBS (5G MBS) to a Target NG-RAN that do support 5MBS, or for better system robustness. Therefore, it is clear that before handover, the source base station may support the MBS for the UE and/or may establish but not activated the MBS for UE.) the method comprising: receiving a handover complete indication transmitted by a target base station, the handover complete indication being used for indicating that the user equipment has been handed over from the source base station to the target base station; (Paul, in Fig. 8 and in Paragraphs [0168] and [0169], teaches that 7. T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (Handover Complete indication for PDU Session ID, UE presence in LADN (local area data network) service area, N2 SM (Session Management) Information (Secondary RAT usage data)). The N2 SM Information here is the one received at step 6b when applicable. Handover Complete indication is sent per each PDU (protocol data unit) Session to the corresponding SMF to indicate the success of the N2 Handover. Therefore, it is clear that the target base station (T-AMF: a target AMF related to the target base station) sends the handover complete indication per each PDU, to indicate the success of handover.)
However, Paul does not teach that receiving a system information block (SIB) broadcast by the target base station; determining that the target base station lacks MBS capability based on the received SIB, the target base station being a node operating in a 5th-Generation System (5GS); triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, the PDU session being a 5GS PDU session; and performing, in an asynchronous manner relative to the PUD session establishment, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session, wherein no MBS session is established on the target base station side.
Chin teaches that receiving a system information block (SIB) broadcast by the target base station; determining that the target base station lacks MBS capability based on the received SIB, the target base station being a node operating in a 5th-Generation System (5GS); (Chin, in Paragraphs [00136], and [00145]-[00153], teaches that as described in Paragraphs [0136] and [00145], the UE may release the NR broadcast/multicast service (5G MBS) radio bearer that was established at the old/source cell (e.g., the cell I) when entering a new/target cell (e.g., the cell 2) and the new/target cell does not support MBS (lack MBS capability). As described in Paragraph [00146]-[00148],the new/target cell may indicate a capability/assistance information to the served UE with a flag (true: support MBS, false: not support MBS), either via a broadcast system information (SIB1, SIB2, SIB20, etc.) or via dedicated signaling such as RRC signaling when UE in RRC_Connected state, where the capability/assistance information indicates whether the network supports MBS or not. Based on that (described [0151]), when a UE enters a new/target cell, the UE determine whether the new/target cell support MBS or not. Otherwise, the absence of a specific broadcast system information at the new/target cell implies that MBS is not supported in the target cell. Thus, based on the SIB, the NR base station (5G base station) determines whether the target cell supports the 5G MBS or not.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul and Chin to include the technique receiving a system information block (SIB) broadcast by the target base station; determining that the target base station lacks MBS capability based on the received SIB, the target base station being a node operating in a 5th-Generation System (5GS) of Chin in the system of Paul to provide a method to improve service continuity of NR broadcast/multicast service(s) via LTE-based SC-PTM (Single Cell Point to Multipoint) by releasing the NR broadcast/multicast service radio bearer (MBS radio bearer) (Chin, see Paragraph [00127])).
However, combination of Paul and Chin does not explicitly teach that triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, the PDU session being a 5GS PDU session; and performing, in an asynchronous manner relative to the PUD session establishment, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session, wherein no MBS session is established on the target base station side.
Hong teaches that triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, the PDU session being a 5GS PDU session; wherein no MBS session is established on the target base station side (Hong, in Paragraphs [0255] and [0257], teaches that when the cell to which the UE hands over is a cell which does not support 5G MBS, a MBS radio bearer for the MBS session is mapped to the unicast radio bearer (data radio bearer) mapped to the associated PDU session and configured in the UE. In this case, as described in [0307], the target base station may determine a transmission scheme/cast type (e.g., multicast/broadcast transmission, unicast transmission) for the corresponding MBS session requested by the source base station for the corresponding terminal. Here, as described in Paragraph [0214], MBS data is individually transmitted from the 5G core network to the UE through the unicast PDU session associated with the MBS session. Thus, based on the decision regarding the MBS capability, the target base station trigger 5G PDU session establishment.) so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, and performing, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session (Hong, in Paragraphs [0294] and [0304]-[0305], The MBS context information may include one or more of MBS session information, QoS flow information included in the MBS session, where the MBS session information may include at least one of the MBS service ID, MBS session ID, IP multicast address, slice information (e.g., S-NSSAI) associated with the MBS session, MBS service area identifier, and MBS service cell identification information and the QoS flow information may include one or more of QoS information on the MBS session (e.g., 5QI/QCI, QoS flow Identifier, and GBR QoS flow information). As described in Paragraph [0303], the unicast session may be configured as a dedicated PDU session that is mapped one-to-one to the MBS session. Alternatively, the unicast session may be configured as a dedicated PDU session mapped one-to-many/many-to one to one or more MBS sessions. As described in Paragraph [0304], based on the MBS context information, the message included in the PDU session setup procedure (e.g. any PDU session setup procedure-related message, such as PDU Session Establishment Request between UE and AMF, PDU SESSION RESOURCE SETUP REQUEST, PDU SESSION RESOURCE SETUP RESPONSE between base station and AMF, Nsmf_PDUSession_ CreateSMContex Request, Nsmf_PDUSession_CreateSMContex Response between AMF and SMF, Session Establishment/Modification Request, Session Establishment/Modification Response between SMF/MB-SMF and UPF/MB-UFP) may include at least one of information for identifying the associated MBS session (MBS service ID, MBS session ID, TMGI, session ID), TNL information (e.g. IP address for the download tunnel between AMF and base station, GTP TEID), QoS flow information, session/cast type (information for distinguishing between one or more among the multicast session, broadcast session, and unicast session) and MBS session type (information for distinguishing between one or more
among IPv4, IPv6, IPv4IPv6, ethernet, and unstructured). Based on these message and information, the PUD session is established and modified.) in an asynchronous manner relative to the PUD session establishment, (Hong, in Paragraphs [0044] and [0055], teaches that since, based on various application and conditions for 5G described in [0044] and [0055], the method in this art is proposed, the asynchronous manner is covered, too.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, and Hong to include the technique triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, the PDU session being a 5GS PDU session; and performing, in an asynchronous manner relative to the PUD session establishment, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session, wherein no MBS session is established on the target base station side of Hong in the system of combination of Paul and Chin to provide a method for receiving MBS data by a UE, for flexibly providing a multicast/broadcast service (MBS) based on new radio (NR), to support an enhanced mobile broadband (eMBB) scenario in terms of services, a massive machine-type communication (mMTC)
scenario in which UEs spread over a broad region at a high UE density, thereby requiring low data rates and asynchronous connections, and an ultra-reliability and low-latency (URLLC) scenario that requires high responsiveness and reliability and supports high-speed mobility. (Hong, see Paragraphs [0005]-[0007]and [0044]).
Regarding claim 6, combination of Paul, Chin, and Hong teaches the features defined in the claim 1, -refer to the indicated claim for reference(s).
Paul further teaches that further comprising: registering the user equipment with a network in response to a determination that the user equipment changes to a new tracking area, (Paul, in Fig. 7 and 8 and in Paragraphs [0191] and [0192], teaches that in Fig. 7, before the handover request, the UE may decide to trigger relocation via N2 and the step 12 in Fig. 8 may proceed the registration procedure after UE confirm handover and the PDU session is established or updated. Therefore, it is clear that the registration procedure can be done after UE may changes to a new tracking area after the completion of the handover.) the operation of triggering establishment of the PDU session on the target base station side being performed before or after a registration procedure (Paul, in Fig. 7 and 8 and in Paragraphs [0192] and [0193], teaches that the registration procedure can be done after all the PDU session establishment or update processing may be done on the target NG-RAN (target base station). Therefore, it is clear that the operation of triggering establishment of the PDU session on the target base station side can be done before or after the registration procedure.).
Regarding claim 7, combination of Paul, Chin, and Hong teaches the features defined in the claim 1, -refer to the indicated claim for reference(s).
Chin further teaches that further comprising: obtaining a target service area of the MBS, and determining, further according to the target service area, that the target base station lacks the MBS capability (Chin, in Paragraphs [00136], and [00145]-[00153], teaches that as described in Paragraphs [0136] and [00145], the UE may release the NR broadcast/multicast service (5G MBS) radio bearer that was established at the old/source cell (e.g., the cell I) when entering a new/target cell (e.g., the cell 2) and the new/target cell does not support MBS (lack MBS capability). As described in Paragraph [00146]-[00148],the new/target cell may indicate a capability/assistance information to the served UE with a flag (true: support MBS, false: not support MBS), either via a broadcast system information (SIB1, SIB2, SIB20, etc.) or via dedicated signaling such as RRC signaling when UE in RRC_Connected state, where the capability/assistance information indicates whether the network supports MBS or not. Based on that (described [0151]), when a UE enters a new/target cell, the UE determine whether the new/target cell support MBS or not. Otherwise, the absence of a specific broadcast system information at the new/target cell implies that MBS is not supported in the target cell. Thus, based on the SIB, the NR base station (5G base station) determines whether the target cell supports the 5G MBS and obtain the service area.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, and Hong to include the further comprising: obtaining a target service area of the MBS, and determining, further according to the target service area, that the target base station lacks the MBS capability of Chin in the system of combination of Paul and Chin to provide a method to improve service continuity of NR broadcast/multicast service(s) via LTE-based SC-PTM (Single Cell Point to Multipoint) by releasing the NR broadcast/multicast service radio bearer (MBS radio bearer) (Chin, see Paragraph [00127]))
Regarding claim 8, combination of Paul, Chin, and Hong teaches the features defined in the claim 1, -refer to the indicated claim for reference(s).
Paul further teaches that further comprising: triggering a service request procedure, so that the user equipment enters a connected state (Paul, in Fig. 6 and Paragraphs [0082] and [0083], teaches that when triggering the joining request of MBS session by UE, the target RAN determine that the new UE in the cell should receive media for one or more MB session and provide PTM/PTP (Point-To-Mulitpoint/Point-To-Point) transmissions to the new UE. Therefore, it is clear that when triggering a service request procedure (joining the MBS session on the target RAN), the UE enters a connected state based on the response of the target RAN.).
Regarding claim 9, combination of Paul, Chin, and Hong teaches the features defined in the claim 1, -refer to the indicated claim for reference(s).
Paul further teaches that further comprising: performing a registration procedure of a registration type of mobility registration update, so that the user equipment enters a connected state (Paul, in Fig. 7 and In Paragraphs [0107], teaches that in inter PLMN (Public Land Mobile Network) mobility case, UE context information includes HPLMN (Home PLMN) S-NSSAIs corresponding to the Allowed NSSAI for each Access Type, without Allowed NSSAI of source PLMN. The target AMF may determine the Allowed NSSAI based on the HPLMN S-NSSAIs received in step 3 in Fig. 7, or else the target AMF queries the NSSF by invoking Nnssf_NSSelection_Get service operation with the HPLMN S-NSSAIs and PLMN ID of SUPI (Subscription Permanent Identifier). The target AMF may trigger AMF re-allocation when Mobility Registration Update is performed during the Handover execution phase. Therefore, it is clear that the user equipment enters a connected state by performing a registration procedure of a registration type of mobility registration update.).
Regarding claim 10, Paul teaches that a user equipment, comprising: a memory storing computer program instructions; and a processor coupled to the memory and configured to execute the computer program instructions and (Paul, in Fig. 12 and in Paragraph [0220], teaches that As illustrated, the wireless communication device 1200 includes one or more processors 1202 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1204, and one or more transceivers 1206 each including one or more transmitters 1208 and one or more receivers 1210 coupled to one or more antennas 1212.) performing a method for implementing multi-cast broadcast service handover, applied to a user equipment, (Paul, in Fig. 6 and in Paragraph [0074] and [0082], teaches that in the step 1, the source NG-RAN (Next Generation Radio Access Network) sends an Xn Handover Request to Target NG-RAN and the UE (User Equipment) Context contains MB (Multicast Broadcast) Session information. In the step 5, the source NG-RAN sends a Uu Handover Command (MBS handover) to UE and the UE starts to access and synchronizes to the new cell. Therefore, it is clear that the multicast broadcast service (MBS) handover can be applied to the UE.) a source base station that the user equipment accesses before handover supporting a multi- cast broadcast service (MBS), and the user equipment, before handover, having established and not activated an MBS session at the source base station, (Paul, in Paragraph [0057], teaches that systems and methods for session continuity of Multicast Broadcast (MB) Sessions are provided. In some embodiments, a method performed by a base station for session continuity of MB Sessions includes at least one of: providing at least one MB Session to a wireless device connected in 5G; determining that the wireless device is handed over to a target Next Generation Radio Access Network (NG-RAN) and providing session continuity of the at least one MB Session to the wireless device. In Paragraph [0059], Paul teaches that Resources in Target NG-RAN may optionally be established in the Xn Handover Execution phase (see step 10 description of "Option 2''). This Option 2 may be an alternative way to do it, but it may also be a complementary way to do it, e.g., when moving from a Source NG-RAN that does not support 5MBS (5G MBS) to a Target NG-RAN that do support 5MBS, or for better system robustness. Therefore, it is clear that before handover, the source base station may support the MBS for the UE and/or may establish but not activated the MBS for UE.) the method comprising: receiving a handover complete indication transmitted by a target base station, the handover complete indication being used for indicating that the user equipment has been handed over from the source base station to the target base station; (Paul, in Fig. 8 and in Paragraphs [0168] and [0169], teaches that 7. T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (Handover Complete indication for PDU Session ID, UE presence in LADN (local area data network) service area, N2 SM (Session Management) Information (Secondary RAT usage data)). The N2 SM Information here is the one received at step 6b when applicable. Handover Complete indication is sent per each PDU (protocol data unit) Session to the corresponding SMF to indicate the success of the N2 Handover. Therefore, it is clear that the target base station (T-AMF: a target AMF related to the target base station) sends the handover complete indication per each PDU, to indicate the success of handover.)
However, Paul does not teach that receiving a system information block (SIB) broadcast by the target base station; determining that the target base station lacks MBS capability based on the received SIB, the target base station being a node operating in a 5th-Generation System (5GS); triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, the PDU session being a 5GS PDU session; and performing, in an asynchronous manner relative to the PUD session establishment, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session, wherein no MBS session is established on the target base station side.
Chin teaches that receiving a system information block (SIB) broadcast by the target base station; determining that the target base station lacks MBS capability based on the received SIB, the target base station being a node operating in a 5th-Generation System (5GS); (Chin, in Paragraphs [00136], and [00145]-[00153], teaches that as described in Paragraphs [0136] and [00145], the UE may release the NR broadcast/multicast service (5G MBS) radio bearer that was established at the old/source cell (e.g., the cell I) when entering a new/target cell (e.g., the cell 2) and the new/target cell does not support MBS (lack MBS capability). As described in Paragraph [00146]-[00148],the new/target cell may indicate a capability/assistance information to the served UE with a flag (true: support MBS, false: not support MBS), either via a broadcast system information (SIB1, SIB2, SIB20, etc.) or via dedicated signaling such as RRC signaling when UE in RRC_Connected state, where the capability/assistance information indicates whether the network supports MBS or not. Based on that (described [0151]), when a UE enters a new/target cell, the UE determine whether the new/target cell support MBS or not. Otherwise, the absence of a specific broadcast system information at the new/target cell implies that MBS is not supported in the target cell. Thus, based on the SIB, the NR base station (5G base station) determines whether the target cell supports the 5G MBS or not.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul and Chin to include the technique receiving a system information block (SIB) broadcast by the target base station; determining that the target base station lacks MBS capability based on the received SIB, the target base station being a node operating in a 5th-Generation System (5GS) of Chin in the system of Paul to provide a method to improve service continuity of NR broadcast/multicast service(s) via LTE-based SC-PTM (Single Cell Point to Multipoint) by releasing the NR broadcast/multicast service radio bearer (MBS radio bearer) (Chin, see Paragraph [00127])).
However, combination of Paul and Chin does not explicitly teach that triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, the PDU session being a 5GS PDU session; and performing, in an asynchronous manner relative to the PUD session establishment, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session, wherein no MBS session is established on the target base station side.
Hong teaches that triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, the PDU session being a 5GS PDU session; wherein no MBS session is established on the target base station side (Hong, in Paragraphs [0255] and [0257], teaches that when the cell to which the UE hands over is a cell which does not support 5G MBS, a MBS radio bearer for the MBS session is mapped to the unicast radio bearer (data radio bearer) mapped to the associated PDU session and configured in the UE. In this case, as described in [0307], the target base station may determine a transmission scheme/cast type (e.g., multicast/broadcast transmission, unicast transmission) for the corresponding MBS session requested by the source base station for the corresponding terminal. Here, as described in Paragraph [0214], MBS data is individually transmitted from the 5G core network to the UE through the unicast PDU session associated with the MBS session. Thus, based on the decision regarding the MBS capability, the target base station trigger 5G PDU session establishment.) so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, and performing, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session (Hong, in Paragraphs [0294] and [0304]-[0305], The MBS context information may include one or more of MBS session information, QoS flow information included in the MBS session, where the MBS session information may include at least one of the MBS service ID, MBS session ID, IP multicast address, slice information (e.g., S-NSSAI) associated with the MBS session, MBS service area identifier, and MBS service cell identification information and the QoS flow information may include one or more of QoS information on the MBS session (e.g., 5QI/QCI, QoS flow Identifier, and GBR QoS flow information). As described in Paragraph [0303], the unicast session may be configured as a dedicated PDU session that is mapped one-to-one to the MBS session. Alternatively, the unicast session may be configured as a dedicated PDU session mapped one-to-many/many-to one to one or more MBS sessions. As described in Paragraph [0304], based on the MBS context information, the message included in the PDU session setup procedure (e.g. any PDU session setup procedure-related message, such as PDU Session Establishment Request between UE and AMF, PDU SESSION RESOURCE SETUP REQUEST, PDU SESSION RESOURCE SETUP RESPONSE between base station and AMF, Nsmf_PDUSession_ CreateSMContex Request, Nsmf_PDUSession_CreateSMContex Response between AMF and SMF, Session Establishment/Modification Request, Session Establishment/Modification Response between SMF/MB-SMF and UPF/MB-UFP) may include at least one of information for identifying the associated MBS session (MBS service ID, MBS session ID, TMGI, session ID), TNL information (e.g. IP address for the download tunnel between AMF and base station, GTP TEID), QoS flow information, session/cast type (information for distinguishing between one or more among the multicast session, broadcast session, and unicast session) and MBS session type (information for distinguishing between one or more
among IPv4, IPv6, IPv4IPv6, ethernet, and unstructured). Based on these message and information, the PUD session is established and modified.) in an asynchronous manner relative to the PUD session establishment, (Hong, in Paragraphs [0044] and [0055], teaches that since, based on various application and conditions for 5G described in [0044] and [0055], the method in this art is proposed, the asynchronous manner is covered, too.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, and Hong to include the technique triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, the PDU session being a 5GS PDU session; and performing, in an asynchronous manner relative to the PUD session establishment, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session, wherein no MBS session is established on the target base station side of Hong in the system of combination of Paul and Chin to provide a method for receiving MBS data by a UE, for flexibly providing a multicast/broadcast service (MBS) based on new radio (NR), to support an enhanced mobile broadband (eMBB) scenario in terms of services, a massive machine-type communication (mMTC)
scenario in which UEs spread over a broad region at a high UE density, thereby requiring low data rates and asynchronous connections, and an ultra-reliability and low-latency (URLLC) scenario that requires high responsiveness and reliability and supports high-speed mobility. (Hong, see Paragraphs [0005]-[0007]and [0044]).
Regarding claim 15, combination of Paul, Chin, and Hong teaches the features defined in the claim 10, -refer to the indicated claim for reference(s).
Paul further teaches that wherein the method further includes: registering the user equipment with a network in response to a determination that the user equipment changes to a new tracking area, (Paul, in Fig. 7 and 8 and in Paragraphs [0191] and [0192], teaches that in Fig. 7, before the handover request, the UE may decide to trigger relocation via N2 and the step 12 in Fig. 8 may proceed the registration procedure after UE confirm handover and the PDU session is established or updated. Therefore, it is clear that the registration procedure can be done after UE may changes to a new tracking area after the completion of the handover.) the operation of triggering establishment of the PDU session on the target base station side being performed before or after a registration procedure (Paul, in Fig. 7 and 8 and in Paragraphs [0192] and [0193], teaches that the registration procedure can be done after all the PDU session establishment or update processing may be done on the target NG-RAN (target base station). Therefore, it is clear that the operation of triggering establishment of the PDU session on the target base station side can be done before or after the registration procedure.).
Regarding claim 16, combination of Paul, Chin, and Hong teaches the features defined in the claim 10, -refer to the indicated claim for reference(s).
Chin further teaches that further comprising: obtaining a target service area of the MBS, and determining, further according to the target service area, that the target base station lacks the MBS capability (Chin, in Paragraphs [00136], and [00145]-[00153], teaches that as described in Paragraphs [0136] and [00145], the UE may release the NR broadcast/multicast service (5G MBS) radio bearer that was established at the old/source cell (e.g., the cell I) when entering a new/target cell (e.g., the cell 2) and the new/target cell does not support MBS (lack MBS capability). As described in Paragraph [00146]-[00148],the new/target cell may indicate a capability/assistance information to the served UE with a flag (true: support MBS, false: not support MBS), either via a broadcast system information (SIB1, SIB2, SIB20, etc.) or via dedicated signaling such as RRC signaling when UE in RRC_Connected state, where the capability/assistance information indicates whether the network supports MBS or not. Based on that (described [0151]), when a UE enters a new/target cell, the UE determine whether the new/target cell support MBS or not. Otherwise, the absence of a specific broadcast system information at the new/target cell implies that MBS is not supported in the target cell. Thus, based on the SIB, the NR base station (5G base station) determines whether the target cell supports the 5G MBS and obtain the service area.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, and Hong to include the further comprising: obtaining a target service area of the MBS, and determining, further according to the target service area, that the target base station lacks the MBS capability of Chin in the system of combination of Paul and Chin to provide a method to improve service continuity of NR broadcast/multicast service(s) via LTE-based SC-PTM (Single Cell Point to Multipoint) by releasing the NR broadcast/multicast service radio bearer (MBS radio bearer) (Chin, see Paragraph [00127])).
Regarding claim 17, combination of Paul, Chin, and Hong teaches the features defined in the claim 10, -refer to the indicated claim for reference(s).
Paul further teaches that wherein the method further includes: triggering a service request procedure, so that the user equipment enters a connected state (Paul, in Fig. 6 and Paragraphs [0082] and [0083], teaches that when triggering the joining request of MBS session by UE, the target RAN determine that the new UE in the cell should receive media for one or more MB session and provide PTM/PTP (Point-To-Mulitpoint/Point-To-Point) transmissions to the new UE. Therefore, it is clear that when triggering a service request procedure (joining the MBS session on the target RAN), the UE enters a connected state based on the response of the target RAN.).
Regarding claim 18, combination of Paul, Chin, and Hong teaches the features defined in the claim 10, -refer to the indicated claim for reference(s).
Paul further teaches that wherein the method further includes: performing a registration procedure of a registration type of mobility registration update, so that the user equipment enters a connected state (Paul, in Fig. 7 and In Paragraphs [0107], teaches that in inter PLMN (Public Land Mobile Network) mobility case, UE context information includes HPLMN (Home PLMN) S-NSSAIs corresponding to the Allowed NSSAI for each Access Type, without Allowed NSSAI of source PLMN. The target AMF may determine the Allowed NSSAI based on the HPLMN S-NSSAIs received in step 3 in Fig. 7, or else the target AMF queries the NSSF by invoking Nnssf_NSSelection_Get service operation with the HPLMN S-NSSAIs and PLMN ID of SUPI (Subscription Permanent Identifier). The target AMF may trigger AMF re-allocation when Mobility Registration Update is performed during the Handover execution phase. Therefore, it is clear that the user equipment enters a connected state by performing a registration procedure of a registration type of mobility registration update.).
Regarding claim 19, Paul teaches that a non-transitory computer-readable storage medium storing computer program instructions executable by at least one processor to perform a method for implementing multi-cast broadcast service handover, applied to a user equipment, (Paul, in Fig. 12 and in Paragraph [0220], teaches that As illustrated, the wireless communication device 1200 includes one or more processors 1202 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 1204, and one or more transceivers 1206 each including one or more transmitters 1208 and one or more receivers 1210 coupled to one or more antennas 1212. In addition, in Fig. 6 and in Paragraph [0074] and [0082], Paul teaches that in the step 1, the source NG-RAN (Next Generation Radio Access Network) sends an Xn Handover Request to Target NG-RAN and the UE (User Equipment) Context contains MB (Multicast Broadcast) Session information. In the step 5, the source NG-RAN sends a Uu Handover Command (MBS handover) to UE and the UE starts to access and synchronizes to the new cell. Therefore, it is clear that the multicast broadcast service (MBS) handover can be applied to the UE.) a source base station that the user equipment accesses before handover supporting a multi- cast broadcast service (MBS), and the user equipment, before handover, having established and not activated an MBS session at the source base station, (Paul, in Paragraph [0057], teaches that systems and methods for session continuity of Multicast Broadcast (MB) Sessions are provided. In some embodiments, a method performed by a base station for session continuity of MB Sessions includes at least one of: providing at least one MB Session to a wireless device connected in 5G; determining that the wireless device is handed over to a target Next Generation Radio Access Network (NG-RAN) and providing session continuity of the at least one MB Session to the wireless device. In Paragraph [0059], Paul teaches that Resources in Target NG-RAN may optionally be established in the Xn Handover Execution phase (see step 10 description of "Option 2''). This Option 2 may be an alternative way to do it, but it may also be a complementary way to do it, e.g., when moving from a Source NG-RAN that does not support 5MBS (5G MBS) to a Target NG-RAN that do support 5MBS, or for better system robustness. Therefore, it is clear that before handover, the source base station may support the MBS for the UE and/or may establish but not activated the MBS for UE.) the method comprising: receiving a handover complete indication transmitted by a target base station, the handover complete indication being used for indicating that the user equipment has been handed over from the source base station to the target base station; (Paul, in Fig. 8 and in Paragraphs [0168] and [0169], teaches that 7. T-AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (Handover Complete indication for PDU Session ID, UE presence in LADN (local area data network) service area, N2 SM (Session Management) Information (Secondary RAT usage data)). The N2 SM Information here is the one received at step 6b when applicable. Handover Complete indication is sent per each PDU (protocol data unit) Session to the corresponding SMF to indicate the success of the N2 Handover. Therefore, it is clear that the target base station (T-AMF: a target AMF related to the target base station) sends the handover complete indication per each PDU, to indicate the success of handover.)
However, Paul does not teach that receiving a system information block (SIB) broadcast by the target base station; determining that the target base station lacks MBS capability based on the received SIB, the target base station being a node operating in a 5th-Generation System (5GS); triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, the PDU session being a 5GS PDU session; and performing, in an asynchronous manner relative to the PUD session establishment, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session, wherein no MBS session is established on the target base station side.
Chin teaches that receiving a system information block (SIB) broadcast by the target base station; determining that the target base station lacks MBS capability based on the received SIB, the target base station being a node operating in a 5th-Generation System (5GS); (Chin, in Paragraphs [00136], and [00145]-[00153], teaches that as described in Paragraphs [0136] and [00145], the UE may release the NR broadcast/multicast service (5G MBS) radio bearer that was established at the old/source cell (e.g., the cell I) when entering a new/target cell (e.g., the cell 2) and the new/target cell does not support MBS (lack MBS capability). As described in Paragraph [00146]-[00148],the new/target cell may indicate a capability/assistance information to the served UE with a flag (true: support MBS, false: not support MBS), either via a broadcast system information (SIB1, SIB2, SIB20, etc.) or via dedicated signaling such as RRC signaling when UE in RRC_Connected state, where the capability/assistance information indicates whether the network supports MBS or not. Based on that (described [0151]), when a UE enters a new/target cell, the UE determine whether the new/target cell support MBS or not. Otherwise, the absence of a specific broadcast system information at the new/target cell implies that MBS is not supported in the target cell. Thus, based on the SIB, the NR base station (5G base station) determines whether the target cell supports the 5G MBS or not.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul and Chin to include the technique receiving a system information block (SIB) broadcast by the target base station; determining that the target base station lacks MBS capability based on the received SIB, the target base station being a node operating in a 5th-Generation System (5GS) of Chin in the system of Paul to provide a method to improve service continuity of NR broadcast/multicast service(s) via LTE-based SC-PTM (Single Cell Point to Multipoint) by releasing the NR broadcast/multicast service radio bearer (MBS radio bearer) (Chin, see Paragraph [00127])).
However, combination of Paul and Chin does not explicitly teach that triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, the PDU session being a 5GS PDU session; and performing, in an asynchronous manner relative to the PUD session establishment, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session, wherein no MBS session is established on the target base station side.
Hong teaches that triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, the PDU session being a 5GS PDU session; wherein no MBS session is established on the target base station side (Hong, in Paragraphs [0255] and [0257], teaches that when the cell to which the UE hands over is a cell which does not support 5G MBS, a MBS radio bearer for the MBS session is mapped to the unicast radio bearer (data radio bearer) mapped to the associated PDU session and configured in the UE. In this case, as described in [0307], the target base station may determine a transmission scheme/cast type (e.g., multicast/broadcast transmission, unicast transmission) for the corresponding MBS session requested by the source base station for the corresponding terminal. Here, as described in Paragraph [0214], MBS data is individually transmitted from the 5G core network to the UE through the unicast PDU session associated with the MBS session. Thus, based on the decision regarding the MBS capability, the target base station trigger 5G PDU session establishment.) so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, and performing, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session (Hong, in Paragraphs [0294] and [0304]-[0305], The MBS context information may include one or more of MBS session information, QoS flow information included in the MBS session, where the MBS session information may include at least one of the MBS service ID, MBS session ID, IP multicast address, slice information (e.g., S-NSSAI) associated with the MBS session, MBS service area identifier, and MBS service cell identification information and the QoS flow information may include one or more of QoS information on the MBS session (e.g., 5QI/QCI, QoS flow Identifier, and GBR QoS flow information). As described in Paragraph [0303], the unicast session may be configured as a dedicated PDU session that is mapped one-to-one to the MBS session. Alternatively, the unicast session may be configured as a dedicated PDU session mapped one-to-many/many-to one to one or more MBS sessions. As described in Paragraph [0304], based on the MBS context information, the message included in the PDU session setup procedure (e.g. any PDU session setup procedure-related message, such as PDU Session Establishment Request between UE and AMF, PDU SESSION RESOURCE SETUP REQUEST, PDU SESSION RESOURCE SETUP RESPONSE between base station and AMF, Nsmf_PDUSession_ CreateSMContex Request, Nsmf_PDUSession_CreateSMContex Response between AMF and SMF, Session Establishment/Modification Request, Session Establishment/Modification Response between SMF/MB-SMF and UPF/MB-UFP) may include at least one of information for identifying the associated MBS session (MBS service ID, MBS session ID, TMGI, session ID), TNL information (e.g. IP address for the download tunnel between AMF and base station, GTP TEID), QoS flow information, session/cast type (information for distinguishing between one or more among the multicast session, broadcast session, and unicast session) and MBS session type (information for distinguishing between one or more
among IPv4, IPv6, IPv4IPv6, ethernet, and unstructured). Based on these message and information, the PUD session is established and modified.) in an asynchronous manner relative to the PUD session establishment, (Hong, in Paragraphs [0044] and [0055], teaches that since, based on various application and conditions for 5G described in [0044] and [0055], the method in this art is proposed, the asynchronous manner is covered, too.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, and Hong to include the technique triggering establishment of a protocol data unit (PDU) session on a target base station side in response to the determination that the target base station lacks the MBS capability, so that a session management function (SMF) subscribes to a multicast broadcast-unified data manager (MB-UDM), single network slice selection assistance information (S-NSSAI) of the PDU session being the same as S-NSSAI of the MBS session, and a data network name (DNN) of the PDU session being the same as a DNN of the MBS session, the PDU session being a 5GS PDU session; and performing, in an asynchronous manner relative to the PUD session establishment, a modification procedure of the triggered PDU session in response to the MBS session being activated, so that the SMF acquires quality of service flow (QoS) information corresponding to the activated MBS session, to establish a QoS flow corresponding to the MBS session in the PDU session, wherein no MBS session is established on the target base station side of Hong in the system of combination of Paul and Chin to provide a method for receiving MBS data by a UE, for flexibly providing a multicast/broadcast service (MBS) based on new radio (NR), to support an enhanced mobile broadband (eMBB) scenario in terms of services, a massive machine-type communication (mMTC)
scenario in which UEs spread over a broad region at a high UE density, thereby requiring low data rates and asynchronous connections, and an ultra-reliability and low-latency (URLLC) scenario that requires high responsiveness and reliability and supports high-speed mobility. (Hong, see Paragraphs [0005]-[0007]and [0044]).
Claims 2, 3, 11, 12, and 20 are rejected under U.S.C. 103 as being unpatentable over Schliwa-Bertling, Paul and et. al. (Int. Pub. No.: WO 2021234635 A1, hereinafter “Paul”) in a view of Chin, Hengli and et. al. (Int. Pub. No.: WO 2022028546 A1, hereinafter “Chin”) and further in a view of Sung-pyo Hong (USPub. No.: US 20230082017 A1, hereinafter, “Hong”) and further in a view of Youngkyo Baek and et. al. (USPub. No.: US 20220053455 A1, hereinafter “Baek”).
Regarding claim 2, combination of Paul, Chin, and Hong teaches the features defined in the claim 1, -refer to the indicated claim for reference(s).
However, combination of Paul, Chin, and Hong does not teach that further comprising: transmitting a non-access stratum message to an access and mobility management function (AMF), the non-access stratum message carrying a request type, the request type indicating an existing MBS session, so that the AMF may select, according to a value of the request type, the SMF for newly establishing the PDU session.
Baek further teaches that further comprising: transmitting a non-access stratum message to an access and mobility management function (AMF), the non-access stratum message carrying a request type, the request type indicating an existing MBS session, (Baek, in Paragarphs [0089] and [0090]), teaches that the UE may transmit a NAS (Non-Access Stratum) message to AMF in the joint request message (it can be considered as the request type) and the message include at least one of the ID of multicast group to which UE belongs, the MBS service session ID, and DNN information, etc. Therefore, it is clear that the AMF may receive the NAS message to join the multicast session.) so that the AMF may select, according to a value of the request type, the SMF for newly establishing the PDU session (Baek, in Paragraphs [0089], [0090], and [0091], teaches that AMF may select an appropriate MS-SMF and transfer a joint request message for the multicast session received from the UE to the selected MB-SMF (SMF for MB (Multicast Broadcast) session). Then, the NAS message may be implemented as a separate NAS message, a PDU session establishment request message, or a PDU session modification request message. Therefore, it is clear that the AMF, according to the join request message, may select the appropriate MB-SMF and it may use for the PDU session establishment based on the NAS message.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, Hong, and Baek to include the technique further comprising: transmitting a non-access stratum message to an access and mobility management function (AMF), the non-access stratum message carrying a request type, the request type indicating an existing MBS session, so that the AMF may select, according to a value of the request type, the SMF for newly establishing the PDU session of Baek in the system of combination of Paul, Chin, and Hong to provide the efficient switching scheme between a local MBS service and a global MBS service when a specialized MBS service is provided in a local area, to transmit data through multicast/broadcast for resource efficiency. (Baek, see Paragraphs [0010] and [0011])).
Regarding claim 3, combination of Paul, Chin, Hong, and Baek teaches the features defined in the claim 2, -refer to the indicated claim for reference(s).
Baek further teaches that wherein the non-access stratum message further carries the S-NSSAI, the DNN, and an MBS session identity of the MBS session, and triggering the establishment of the protocol data unit (PDU) session comprises: (Baek, in Fig. 2A, 2B, 7A, and 7B and Paragraphs [0182], [0089]-[0092], teaches that after MBS service announcement (sending to UE TMGI (Temporary Mobile Group ID , MBS session ID, MBS service type, MBS area , AF (Application Function)’s FQDN (Fully Qualified Domain Name), S-NSSAI information, and DNN information), the UE may request the joining by sending UL NAS message. The NAS message may carry the S-NSSAI, the DNN, and the MBS session ID and the NAS message can be implemented as a separate NA message, a PDU session establishment request message or a PDU session modification request message. Therefore, it is clear that the NAS message carry the S-NSSAI, the DNN and the MBS session ID and may trigger the PDU session establishment.) establishing the PDU session through the selected SMF according to the S-NSSAI, the DNN, and the MBS session identity, so that the SMF subscribes to the MB-UDM (Baek, in in Fig. 2A, 2B, 7A, and 7B and Paragraphs [0182], [0089]-[0092], teaches that based the PDU session establishment can be requested based on the S-NSSAI, the DNN, the MBS session ID according to the NAS message and the MB-SMF 24 may request and obtain, from the UDM, SM subscription data, determining whether the UE is able to receive an MBS service through the multicast group ID. Therefore, based on the NAS message, the PDU session establishment can be requested with the S-NSSAI, the DNN, and the MBS session ID and the MB-SMF can obtain the subscription information from UDM or subscribe to UDM.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, Hong, and Baek to include the technique wherein the non-access stratum message further carries the S-NSSAI, the DNN, and an MBS session identity of the MBS session, and triggering the establishment of the protocol data unit (PDU) session comprises: establishing the PDU session through the selected SMF according to the S-NSSAI, the DNN, and the MBS session identity, so that the SMF subscribes to the MB-UDM of Baek in the system of combination of Paul, Chin, and Hong to provide the efficient switching scheme between a local MBS service and a global MBS service when a specialized MBS service is provided in a local area, to transmit data through multicast/broadcast for resource efficiency. (Baek, see Paragraphs [0010] and [0011])).
Regarding claim 11, combination of Paul, Chin, and Hong teaches the features defined in the claim 10, -refer to the indicated claim for reference(s).
However, combination of Paul, Chin, and Hong does not teach that wherein the method further includes: transmitting a non-access stratum message to an access and mobility management function (AMF), the non-access stratum message carrying a request type, the request type indicating an existing MBS session, so that the AMF may select, according to a value of the request type, the SMF for newly establishing the PDU session.
Baek further teaches that further comprising: transmitting a non-access stratum message to an access and mobility management function (AMF), the non-access stratum message carrying a request type, the request type indicating an existing MBS session, (Baek, in Paragarphs [0089] and [0090]), teaches that the UE may transmit a NAS (Non-Access Stratum) message to AMF in the joint request message (it can be considered as the request type) and the message include at least one of the ID of multicast group to which UE belongs, the MBS service session ID, and DNN information, etc. Therefore, it is clear that the AMF may receive the NAS message to join the multicast session.) so that the AMF may select, according to a value of the request type, the SMF for newly establishing the PDU session (Baek, in Paragraphs [0089], [0090], and [0091], teaches that AMF may select an appropriate MS-SMF and transfer a joint request message for the multicast session received from the UE to the selected MB-SMF (SMF for MB (Multicast Broadcast) session). Then, the NAS message may be implemented as a separate NAS message, a PDU session establishment request message, or a PDU session modification request message. Therefore, it is clear that the AMF, according to the join request message, may select the appropriate MB-SMF and it may use for the PDU session establishment based on the NAS message.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, Hong, and Baek to include the technique wherein the method further includes: transmitting a non-access stratum message to an access and mobility management function (AMF), the non-access stratum message carrying a request type, the request type indicating an existing MBS session, so that the AMF may select, according to a value of the request type, the SMF for newly establishing the PDU session of Baek in the system of combination of Paul, Chin, and Hong to provide the efficient switching scheme between a local MBS service and a global MBS service when a specialized MBS service is provided in a local area, to transmit data through multicast/broadcast for resource efficiency. (Baek, see Paragraphs [0010] and [0011])).
Regarding claim 12, combination of Paul, Chin, Hong, and Baek teaches the features defined in the claim 11, -refer to the indicated claim for reference(s).
Baek further teaches that wherein the non-access stratum message further carries the S-NSSAI, the DNN, and an MBS session identity of the MBS session, and triggering the establishment of the protocol data unit (PDU) session includes: (Baek, in Fig. 2A, 2B, 7A, and 7B and Paragraphs [0182], [0089]-[0092], teaches that after MBS service announcement (sending to UE TMGI (Temporary Mobile Group ID , MBS session ID, MBS service type, MBS area , AF (Application Function)’s FQDN (Fully Qualified Domain Name), S-NSSAI information, and DNN information), the UE may request the joining by sending UL NAS message. The NAS message may carry the S-NSSAI, the DNN, and the MBS session ID and the NAS message can be implemented as a separate NA message, a PDU session establishment request message or a PDU session modification request message. Therefore, it is clear that the NAS message carry the S-NSSAI, the DNN and the MBS session ID and may trigger the PDU session establishment.) establishing the PDU session through the selected SMF according to the S-NSSAI, the DNN, and the MBS session identity, so that the SMF subscribes to the MB-UDM (Baek, in in Fig. 2A, 2B, 7A, and 7B and Paragraphs [0182], [0089]-[0092], teaches that based the PDU session establishment can be requested based on the S-NSSAI, the DNN, the MBS session ID according to the NAS message and the MB-SMF 24 may request and obtain, from the UDM, SM subscription data, determining whether the UE is able to receive an MBS service through the multicast group ID. Therefore, based on the NAS message, the PDU session establishment can be requested with the S-NSSAI, the DNN, and the MBS session ID and the MB-SMF can obtain the subscription information from UDM or subscribe to UDM.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Liang and Baek to include the technique wherein the non-access stratum message further carries the S-NSSAI, the DNN, and an MBS session identity of the MBS session, and triggering the establishment of the protocol data unit (PDU) session includes: establishing the PDU session through the selected SMF according to the S-NSSAI, the DNN, and the MBS session identity, so that the SMF subscribes to the MB-UDM of Baek in the system of combination of Paul and Liang to provide the efficient switching scheme between a local MBS service and a global MBS service when a specialized MBS service is provided in a local area, to transmit data through multicast/broadcast for resource efficiency. (Baek, see Paragraphs [0010] and [0011])).
Regarding claim 20, combination of Paul, Chin, and Hong teaches the features defined in the claim 19, -refer to the indicated claim for reference(s).
However, combination of Paul, Chin, and Hong does not teach that wherein the method further includes: transmitting a non-access stratum message to an access and mobility management function (AMF), the non-access stratum message carrying a request type, the request type indicating an existing MBS session, so that the AMF may select, according to a value of the request type, the SMF for newly establishing the PDU session.
Baek further teaches that wherein the method further includes: transmitting a non-access stratum message to an access and mobility management function (AMF), the non-access stratum message carrying a request type, the request type indicating an existing MBS session, (Baek, in Paragarphs [0089] and [0090]), teaches that the UE may transmit a NAS (Non-Access Stratum) message to AMF in the joint request message (it can be considered as the request type) and the message include at least one of the ID of multicast group to which UE belongs, the MBS service session ID, and DNN information, etc. Therefore, it is clear that the AMF may receive the NAS message to join the multicast session.) so that the AMF may select, according to a value of the request type, the SMF for newly establishing the PDU session (Baek, in Paragraphs [0089], [0090], and [0091], teaches that AMF may select an appropriate MS-SMF and transfer a joint request message for the multicast session received from the UE to the selected MB-SMF (SMF for MB (Multicast Broadcast) session). Then, the NAS message may be implemented as a separate NAS message, a PDU session establishment request message, or a PDU session modification request message. Therefore, it is clear that the AMF, according to the join request message, may select the appropriate MB-SMF and it may use for the PDU session establishment based on the NAS message.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, Hong, and Baek to include the technique wherein the method further includes: transmitting a non-access stratum message to an access and mobility management function (AMF), the non-access stratum message carrying a request type, the request type indicating an existing MBS session, so that the AMF may select, according to a value of the request type, the SMF for newly establishing the PDU session of Baek in the system of combination of Paul, Chin, and Hong to provide the efficient switching scheme between a local MBS service and a global MBS service when a specialized MBS service is provided in a local area, to transmit data through multicast/broadcast for resource efficiency. (Baek, see Paragraphs [0010] and [0011])).
Claims 4 and 13 are rejected under U.S.C. 103 as being unpatentable over Schliwa-Bertling, Paul and et. al. (Int. Pub. No.: WO 2021234635 A1, hereinafter “Paul”) in a view of Chin, Hengli and et. al. (Int. Pub. No.: WO 2022028546 A1, hereinafter “Chin”) and further in a view of Sung-pyo Hong (USPub. No.: US 20230082017 A1, hereinafter, “Hong”) and further in a view of Jinguo Zhu and et. al. (USPub. No.: US 20230017217 A1, hereinafter “Zhu”)
Regarding claim 4, combination of Paul, Chin, and Hong teaches the features defined in the claim 1, -refer to the indicated claim for reference(s).
However, combination of Paul, Chin, and Hong does not teach that wherein the non-access stratum message further carries a PDU session identity of the PDU session and an N1 session management container, the N1 session management container carrying a PDU session establishment request for establishing the PDU session.
Zhu teaches that wherein the non-access stratum message further carries a PDU session identity of the PDU session and an N1 session management container, the N1 session management container carrying a PDU session establishment request for establishing the PDU session (Zhu, in Paragraph [0077], teaches that the UE requests a PDU Session establishment procedure by the transmission of a NAS message containing a PDU Session Establishment Request within the N1 SM (Session Management) container. The PDU Session Establishment Request includes a PDU Session identify (ID), Requested PDU Session Type, Request Single-Network Slicing Selection Assistant Information (S-NSSAI) indicating the network slicing, Requested Date Network Name (DNN), etc. Therefore, it is clear that the NAS message can include the PDU session ID and the N1 SM container and the N1 SM container can include a PDU session establishment request.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, Hong, and Zhu to include the technique wherein the non-access stratum message further carries a PDU session identity of the PDU session and an N1 session management container, the N1 session management container carrying a PDU session establishment request for establishing the PDU session of Zhu in the system of combination of Paul, Chin, and Hong to provide the techniques that enable flexible multicast or broadcast session establishment and management, providing operational efficiency for Internet of Things and Vehicle to Everything communication with the development of 5G New Radio. (Zhu, see Paragraphs [0004] and [0025])).
Regarding claim 13, combination of Paul, Chin, and Hong teaches the features defined in the claim 10, -refer to the indicated claim for reference(s).
However, combination of Paul, Chin, and Hong does not teach that wherein the non-access stratum message further carries a PDU session identity of the PDU session and an N1 session management container, the N1 session management container carrying a PDU session establishment request for establishing the PDU session.
Zhu teaches that wherein the non-access stratum message further carries a PDU session identity of the PDU session and an N1 session management container, the N1 session management container carrying a PDU session establishment request for establishing the PDU session (Zhu, in Paragraph [0077], teaches that the UE requests a PDU Session establishment procedure by the transmission of a NAS message containing a PDU Session Establishment Request within the N1 SM (Session Management) container. The PDU Session Establishment Request includes a PDU Session identify (ID), Requested PDU Session Type, Request Single-Network Slicing Selection Assistant Information (S-NSSAI) indicating the network slicing, Requested Date Network Name (DNN), etc. Therefore, it is clear that the NAS message can include the PDU session ID and the N1 SM container and the N1 SM container can include a PDU session establishment request.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, Hong, and Zhu to include the technique wherein the non-access stratum message further carries a PDU session identity of the PDU session and an N1 session management container, the N1 session management container carrying a PDU session establishment request for establishing the PDU session of Zhu in the system of combination of Paul, Chin, and Hong to provide the techniques that enable flexible multicast or broadcast session establishment and management, providing operational efficiency for Internet of Things and Vehicle to Everything communication with the development of 5G New Radio. (Zhu, see Paragraphs [0004] and [0025])).
Claims 5 and 14 are rejected under U.S.C. 103 as being unpatentable over Schliwa-Bertling, Paul and et. al. (Int. Pub. No.: WO 2021234635 A1, hereinafter “Paul”) in a view of Chin, Hengli and et. al. (Int. Pub. No.: WO 2022028546 A1, hereinafter “Chin”) and further in a view of Sung-pyo Hong (USPub. No.: US 20230082017 A1, hereinafter, “Hong”) and further in a view of Liang, Shuang and et. al. (Int. Pub. No.: WO 2021098123 A1, hereinafter “Liang”).
Regarding claim 5, combination of Paul, Chin, and Hong teaches the features defined in the claim 1, -refer to the indicated claim for reference(s).
Combination of Paul, Chin, and Hong does not explicitly teach that wherein a corresponding PDU session is established for each MBS session in response to a determination that the user equipment, before handover, has established and not activated a plurality of MBS sessions at the source base station, S- NSSAI of each MBS session being the same as S-NSSAI of the corresponding PDU session, and a DNN of each MBS session being the same as a DNN of the corresponding PDU session.
Liang further teaches that wherein a corresponding PDU session is established for each MBS session in response to a determination that the user equipment, before handover, has established and not activated a plurality of MBS sessions at the source base station, (Liang, in Fig. 6 and in Page 9, Lines 16-20, teaches that at the step 601, the S-RAN sends to the AMF a handover required message including a target identifier, a source to target transparent container, an SM N2 information list, PDU Session identifiers, and an intra-system handover indication. The source to target transparent container includes NG-RAN information created by the S-RAN to be used by T-RAN which is transparent to the 5G core (5GC). In Page 10, Lines 26-31 and Page 11, Lines 1-3 and Lines 10-11, Liang teaches that the source to target transparent container is forwarded as received from S-RAN to the T-RAN. If the contexts included in the source to target transparent container include an indication of multicast service, the T-RAN checks whether an MBS session for the same MBS service has been established or not based on the TMGI, MBS session identifier, MBS flow identifier, or MBS service identifier. If the MBS session for the same MBS service has been established, (e.g. the UE is joining a group that is already being served the multicast service via T-RAN), the T-RAN binds a shared tunnel for the MBS session and flow (sometimes referred to as a dummy flow) linked in the unicast PDU session. If the MBS session for the MBS service hasn't been established, (e.g. no users being served by the T-RAN are served the same multicast service by the T-RAN), the T-RAN allocates an MBS DL shared tunnel for the MBS service (In this process, the PDU session establishment is included). In order to avoid packet loss and support direct data forwarding, the T-RAN may allocate a tunnel for data forwarding. For an MBS service, the flow (dummy) linked in the unicast PDU session which is related with the MBS session may be revoked at the T-RAN to transfer the forwarded data. If the UE has multiple MBS services, T-RAN may allocate multiple shared tunnels for the MBS services separately. Therefore, it is clear that for each MBS session in the source RAN (that may be established but may not be activated in the source RAN, as shown in the above), the corresponding PDU session may be established in the targe RAN.) S-NSSAI of each MBS session being the same as S-NSSAI of the corresponding PDU session, and a DNN of each MBS session being the same as a DNN of the corresponding PDU session (Liang, in Fig. 4 and In Page 5, Lines 26-29 teaches that during the PDU establishment process at 410 in Fig 4, an MBS-SMF supporting unicast and multicast is selected based on a specific DNN and single network slice selection assistance information (S-NSSAI). Upon completion of the establishment process, the UE may retrieve a multicast service configuration associated with MBSF (MBS function). Therefore, it is clear that in this process, S-NSSAI and DNN are corresponding to the S-NSSAI and DNN of MBS session.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul, Chin, Hong, and Liang to include the technique wherein a corresponding PDU session is established for each MBS session in response to a determination that the user equipment, before handover, has established and not activated a plurality of MBS sessions at the source base station, S-NSSAI of each MBS session being the same as S-NSSAI of the corresponding PDU session, and a DNN of each MBS session being the same as a DNN of the corresponding PDU session of Liang in the system of combination of Paul, Chin and Hong to provide the efficient techniques for managing and providing continuity of service for multicast broadcast services when a user equipment (UE) is handed over form one radio access node to another, to reduce the energy consumption and latency in mobile communication. (Liang, see Page 1, Lines 15-18 and Page 3, Lines 5-10)).
Regarding claim 14, combination of Paul, Chin, and Hong teaches the features defined in the claim 10, -refer to the indicated claim for reference(s).
Combination of Paul, Chin, and Hong does not explicitly teach that wherein a corresponding PDU session is established for each MBS session in response to a determination that the user equipment, before handover, has established and not activated a plurality of MBS sessions at the source base station, S- NSSAI of each MBS session being the same as S-NSSAI of the corresponding PDU session, and a DNN of each MBS session being the same as a DNN of the corresponding PDU session.
Liang further teaches that wherein a corresponding PDU session is established for each MBS session in response to a determination that the user equipment, before handover, has established and not activated a plurality of MBS sessions at the source base station, (Liang, in Fig. 6 and in Page 9, Lines 16-20, teaches that at the step 601, the S-RAN sends to the AMF a handover required message including a target identifier, a source to target transparent container, an SM N2 information list, PDU Session identifiers, and an intra-system handover indication. The source to target transparent container includes NG-RAN information created by the S-RAN to be used by T-RAN which is transparent to the 5G core (5GC). In Page 10, Lines 26-31 and Page 11, Lines 1-3 and Lines 10-11, Liang teaches that the source to target transparent container is forwarded as received from S-RAN to the T-RAN. If the contexts included in the source to target transparent container include an indication of multicast service, the T-RAN checks whether an MBS session for the same MBS service has been established or not based on the TMGI, MBS session identifier, MBS flow identifier, or MBS service identifier. If the MBS session for the same MBS service has been established, (e.g. the UE is joining a group that is already being served the multicast service via T-RAN), the T-RAN binds a shared tunnel for the MBS session and flow (sometimes referred to as a dummy flow) linked in the unicast PDU session. If the MBS session for the MBS service hasn't been established, (e.g. no users being served by the T-RAN are served the same multicast service by the T-RAN), the T-RAN allocates an MBS DL shared tunnel for the MBS service (In this process, the PDU session establishment is included). In order to avoid packet loss and support direct data forwarding, the T-RAN may allocate a tunnel for data forwarding. For an MBS service, the flow (dummy) linked in the unicast PDU session which is related with the MBS session may be revoked at the T-RAN to transfer the forwarded data. If the UE has multiple MBS services, T-RAN may allocate multiple shared tunnels for the MBS services separately. Therefore, it is clear that for each MBS session in the source RAN (that may be established but may not be activated in the source RAN, as shown in the above), the corresponding PDU session may be established in the targe RAN.) S-NSSAI of each MBS session being the same as S-NSSAI of the corresponding PDU session, and a DNN of each MBS session being the same as a DNN of the corresponding PDU session (Liang, in Fig. 4 and In Page 5, Lines 26-29 teaches that during the PDU establishment process at 410 in Fig 4, an MBS-SMF supporting unicast and multicast is selected based on a specific DNN and single network slice selection assistance information (S-NSSAI). Upon completion of the establishment process, the UE may retrieve a multicast service configuration associated with MBSF (MBS function). Therefore, it is clear that in this process, S-NSSAI and DNN are corresponding to the S-NSSAI and DNN of MBS session.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Paul and Liang to include the technique wherein a corresponding PDU session is established for each MBS session in response to a determination that the user equipment, before handover, has established and not activated a plurality of MBS sessions at the source base station, S-NSSAI of each MBS session being the same as S-NSSAI of the corresponding PDU session, and a DNN of each MBS session being the same as a DNN of the corresponding PDU session of Liang in the system of Paul to provide the efficient techniques for managing and providing continuity of service for multicast broadcast services when a user equipment (UE) is handed over form one radio access node to another, to reduce the energy consumption and latency in mobile communication. (Liang, see Page 1, Lines 15-18 and Page 3, Lines 5-10)).
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 JAEYOUNG KWAK whose telephone number is (703)756-1768. The examiner can normally be reached Monday-Friday 9 AM -5 PM.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Kevin Bates can be reached at 571-272-3980. 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.
/JAEYOUNG KWAK/Examiner, Art Unit 2472
/KEVIN T BATES/Supervisory Patent Examiner, Art Unit 2472