Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claims 1-2, 4-10, 12-17, 19-23, 25-31 are pending.
Response to Arguments
Applicant’ arguments presented in the Remarks of 11/10/2025 is/are fully considered but they are not persuasive.
Specifically:
Applicant’s primary arguments are as quoted below:
In amended claim 1, first signalling that request for a MCG configuration associated with a wireless device to be modified is received. The first signalling indicates that the request for the MCG configuration modification is based at least on a change in SCG configuration associated with the wireless device. The MCG configuration is modified based at least on the change in the SCG configuration. The change in the SCG configuration corresponds to adding a SCG, removing a SCG or modifying a SCG.
Zhou discloses that gNB-DUl receives a request message to
reconfigure the source MCG to the target SCG based on the gNB-CU's decision of an intra gNB handover process, and generates the cell group configuration information of the target SCG to include the cell group configuration information of the source MCG. That is, the request received by the gNB-DU, as well as the resulting configuration modification, is based on the gNB-CU's decision.
In contrast, the feature (1) requires that the MCG configuration is modified based on the change in the SCG configuration. As detailed in paragraphs [0129] to [0141] of the published specification of the present application, when an SCG is added, a change or limitation of the MCG configuration may be caused (e.g., to reduce the amount of resources/features/UE capabilities utilized by the MN). When an SCG is modified, the MN may have to change the UE's MCG configuration (e.g., to optimize the amount of resources/features/UE capabilities utilized by the MN). When an SCG is removed, the MN may choose to configure additional or better features in the UE's MCG configuration. In other words, different modifications of the MCG configuration are performed based on the change in the SCG configuration. Zhou says nothing about "the request for the MCG configuration modification is based at least on a change in secondary cell group, SCG, configuration; and modifying the MCG configuration based at least on the change in the SCG configuration".
The examiner respectfully disagrees. Applicant’s assertion does not reflect accurate reading of the reference Zhou.
Per step 1 of Fig. 12 (page 16), Step 1 mentions of a change in configuration that occurs: namely the gNB-DU2 configures a switched target MCG, and at the same time, the source MCG is reconfigured toward the target SCG (i.e. in other words, the target SCG is reconfigured to take role as the new MCG). This switch at this time has already happened in step 1. And in response to this change, step 2 happens, which includes the sending of the configuration modification request to the gNB-DU1 with configuration of source MCG is now indicative of the target SCG (i.e. reflecting the change in step 1 that the target SCG is the new source MCG).
Thus clearly, the request for modification in Zhou is based on the change in configuration occurred in step 1 of Fig. 12, thus meeting the limitation (1). And also, that change namely includes the promotion of the target SCG to be indicated as the new source MCG. Since the target SCG is now the new MCG, it is no longer part of the SCG configuration (i.e. removed), and secondly, the SCG itself is modified by virtue of being appointed as the new MCG. In this regards, Zhou satisfies at least one of the alternatives as listed: “adding a SCG to the SCG configuration, removing a SCG from the SCG configuration, and modifying a SCG associated with the SCG configuration.”
It is further noted Applicant relies on the Specification paragraphs [0129] to [0141] of the published specification of the present application. The examiner asserts that while the Specification can be consulted for purpose of understanding the invention, it is improper to read limitations in the Specifications into the claims.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 1, 2, 4-7, 9-10, 12-15, 17, 19-21, 23, 25-27, 30, and 31 is/are rejected under 35 U.S.C. 102(a)(1) as being unpatentable over Zhou (CN 111510934).
As to claim 1:
Zhou discloses:
A network node including a master node- distributed unit, MN-DU, and a MN-centralized unit, MN-CU, in communication with each other, (page 9, the node can be a wireless access network in the base station network device, also can be one entity in the network device, such as the CU/DU separating architecture in the central unit CU or distributed unit DU and so on. Page 16, gNB under the CU/DU separation framework)
the network node comprising processing circuitry configured to: receive, at the MN-DU, first signaling that request for a master cell group, MCG, configuration associated with a wireless device to be modified, the first signaling indicating that the request for the MCG configuration modification is based at least on a change in secondary cell group, SCG, configuration associated with the wireless device ;
(Fig. 12, page 16-17, step 2: gNB-CU sends a user terminal context modification request message to gNB-DU1, wherein the request message comprises the source MCG reconfiguration indicative of the target SCG. gNB-DU1 generates the cell group configuration information of the target SCG after switching, wherein the cell group identification information of the source MCG is included to indicate that the configuration information is the increment configuration information based on the source MCG configuration information. In other words, the MCG reconfiguration comprises the indication of the target SCG (SCG is being promoted to MCG, and replaces the original MCG reconfiguration). The DU receives signaling that directly reflects this change and applies the configuration updates based on the target SCG)
and modify, at the MN-DU, the MCG configuration based at least on the change in the SCG configuration associated with the wireless device. (Page 16-17, step 2-3 of Fig. 12, gNB-DU1 generates the cell group configuration information of the target SCG after switching, wherein the cell group identification information of the source MCG is included to indicate that the configuration information is the increment configuration information. The new MCG is deprived from the SCG config)
As to claim 9:
Zhou discloses all limitations of claim a method implemented by a network node including a master node-distributed unit, MN-DU, and a MN-centralized unit, MN-CU, in communication with each other, the method comprising: receiving, at the MN-DU, first signaling that request for a master cell group, MCG, configuration associated with a wireless device to be modified, the first signaling indicating that the request for the MCG configuration modification is based at least on a change in secondary cell group, SCG, configuration associated with the wireless device; (Fig. 12, page 16-17, gNB-CU sends a user terminal context modification request message to gNB-DU1, wherein it comprises the source MCG reconfiguration is the indication of the target SCG. gNB-DU1 generates the cell group configuration information of the target SCG after switching, wherein the cell group identification information of the source MCG is included to indicate that the configuration information is the increment configuration information based on the source MCG configuration information. In other words, the MCG reconfiguration comprises the indication of the target SCG (SCG is being promoted to MCG, and replaces the original MCG reconfiguration). The DU receives signaling that directly reflects this change and applies the configuration updates based on the target SCG) and modifying, at the MN-DU, the MCG configuration based at least on the change in the SCG configuration associated with the wireless device. (Page 16-17, step 2-3 of Fig. 12, gNB-DU1 generates the cell group configuration information of the target SCG after switching, wherein the cell group identification information of the source MCG is included to indicate that the configuration information is the increment configuration information. The new MCG is deprived from the SCG config)
As to claims 17, 23:
Zhou discloses:
A method and a network node including a master node- distributed unit, MN-DU, and a MN-centralized unit, MN-CU, in communication with each other, (page 9, the node can be a wireless access network in the base station network device, also can be one entity in the network device, such as the CU/DU separating architecture in the central unit CU or distributed unit DU and so on. Page 16, gNB under the CU/DU separation framework) the network node comprising processing circuitry configured to perform the method:
receive, at the MN-CU, an indication of a change in a secondary cell group, SCG, configuration associated with the wireless device ; (Fig. 12, step 1, Page 16, changes in SCG configuration associated with UE, which lead to transmission of reconfiguration in step 2)
and cause, at the MN-CU, transmission of first signaling to the MN-DU, the first signaling requesting for a master cell group, MCG, configuration associated with a wireless device to be modified, the first signalling indicating that the request for the MCG configuration modification is based at least on the change in the SCG configuration that is associated with the wireless device Fig. 12, page 16-17, gNB-CU sends a user terminal context modification request message to gNB-DU1, wherein it comprises the source MCG reconfiguration is the indication of the target SCG. gNB-DU1 generates the cell group configuration information of the target SCG after switching, wherein the cell group identification information of the source MCG is included to indicate that the configuration information is the increment configuration information based on the source MCG configuration information. In other words, the MCG reconfiguration comprises the indication of the target SCG (SCG is being promoted to MCG, and replaces the original MCG reconfiguration). The DU receives signaling that directly reflects this change and applies the configuration updates based on the target SCG)
As to claims 2, 10:
Zhou discloses all limitations of claim 1/9, wherein the first signaling is received from the MN-CU. (page 16, “gNB-CU sends a user terminal context modification request message to gNB-DU1”)
As to claims 4, 12, 19, 25:
Zhou discloses all limitations of claim 1/9/17/23, wherein the modification of the MCG configuration includes one of: modifying a quantity of resources utilized by the network node for at least one communication channel used by the wireless device ; and modifying a quantity of wireless device capabilities utilized by the network node for at least one communication channel used by the wireless device. (See page 2, “configuration information mainly comprises the three parameters: measurement configuration, radio bearer configuration information and cell group configuration information. wherein the measurement configuration information is used for indicating which measurement is required by the network side to the terminal; the radio bearer configuration information is used for indicating which bearer should be configured by the terminal, and the bearer should configure the PDCP layer and the SDAP resource; and the cell group configuration information is used for indicating how to configure physical layer, MAC layer and RLC layer resource”. See Page 16-17, notable step 2, sthe reconfiguration message such configuration, including the bearers. Since MCG and SCG exchange roles, thus implicating the resources they were using)
As to claims 5, 13, 20, 26:
Zhou discloses all limitations of claim 1/9/17/23, wherein the modification of the MCG configuration includes a reconfiguration of a layer 1/layer 2, L1/L2, configuration. (L1 and L2 correspond directly to physical layers, MAC layers, and RLC layers. ]See page 2, “configuration information mainly comprises (…) the radio bearer configuration information is used for indicating which bearer should be configured by the terminal, and the bearer should configure the PDCP layer and the SDAP resource; and the cell group configuration information is used for indicating how to configure physical layer, MAC layer and RLC layer resource”. See Page 16-17, notable step 2, sthe reconfiguration message such configuration, including the bearers. Since MCG and SCG exchange roles, thus implicating the resources they were using)
As to claims 6, 14, 21, 27:
Zhou discloses all limitations of claim 1/9/17/23, wherein the request includes an information element, IE, that is configured to provide the indication that the request for the modification of the MCG configuration is based at least on the change in the SCG configuration. (page 7, indication information (i.e. read as IE) is used for indicating the third node to modify the cell group identification information of the cell group controlled by the first node. See also Fig. 12, step 2)
As to claims 7, 15:
Zhou discloses all limitations of claim 1/9, wherein the processing circuitry is further configured to receive second signaling indicating at least one parameter of the SCG configuration is being modified. (See page 16-17, (…)indicate it continues to use the existing cell group configuration, only change the cell group identification information (CellGroup ID) of the cell group. so that the Cell Group ID can be changed by means of incremental reconfiguration. In addition, the participant in the wireless access system also needs to perform some additional operations to ensure that the change operation of the Cell Group ID can be performed correctly and efficiently. See also step 2, step 6 and 7 of Fig. 12’s description)
As to claim 30:
Zhou discloses all limitations of claim 1, wherein the change in the SCG configuration corresponds to removing a SCG from the SCG configuration. (Zhou, page 12, step 1, the change in configuration occurred in step 1, wherein that change namely includes the promotion of the target SCG to be indicated as the new source MCG. Since the target SCG is now the new MCG, it is no longer part of the SCG configuration (i.e. removed), and secondly, the SCG itself is modified by virtue of being appointed as the new MCG)
As to claim 31:
Zhou discloses all limitations of claim 1, wherein the change in the SCG configuration corresponds to modifying a SCG associated with the SCG configuration. (Zhou, page 12, step 1, the change in configuration occurred in step 1, wherein that change namely includes the promotion of the target SCG to be indicated as the new source MCG. Since the target SCG is now the new MCG, it is no longer part of the SCG configuration and is modified by virtue of being appointed as the new MCG)
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
Claim(s) 29 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhou (CN1150934) in view of Xu et al. (US 2020/0359450).
As to claim 29:
Zhou discloses all limitations of claim 1, wherein the cell group reconfiguration in in responses a change pertaining in the SCG per Fig. 12, however does not explicitly disclose one possible change corresponds to adding a SCG to the SCG configuration.
Xu, in a related field of cell group management, discloses in scenarios when a change occurs, namely when the MN adds, modifies, and releases (removes) a particular SCG, a configuration update request is made to ensure bearer context, UE context, and SCG configuration are updated to reflect said change (¶0117). (It is noted that, Xu covers all possible scenarios in original claim 3)
It would have been obvious to one of ordinary skill in the art before the effective filing time of the invention that the update of configuration pertaining a SCG in Zhou to include a trigger that corresponds to the adding of a SCG. This implementation ensures system transparency in both ends where network and user contexts are always up-to-date of real time changes responsive to network/mobility changes.
Claim(s) 8, 16, 22, and 28 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhou (CN1150934) in view of Teyeb et al. (US 2020/0128454).
As to claims 8, 16, 22, and 28:
Zhou discloses all limitations of claim 1/9/17/23, however is silent on the change in the SCG configuration indicates one of: a different subset of wireless device capabilities is being implemented; and that the MCG configuration is no longer restricted to at least one band combination.
Teyeb, in a related field of endeavor, discloses on the change in the SCG configuration indicates one of: a different subset of wireless device capabilities is being implemented; and that the MCG configuration is no longer restricted to at least one band combination, see ¶0228 and Table 10 of CG Config message, gNB to request the SgNB to perform certain actions e.g. to establish, modify or release an SCG. The message may include additional information e.g. to assist the SgNB to set the SCG configuration. It can also be used by a CU to request a DU to perform certain actions, e.g. to establish, modify or release an MCG or SCG”, also “ue-Capabilityinfo” which contain UE capability-container list which hold features of UE to be used adaptively.
It would have been obvious to one of ordinary skill in the art before the effective filing time of the invention that Zhou’s system to include at least one of: a different subset of wireless device capabilities is being implemented; and that the MCG configuration is no longer restricted to at least one band combination in manner disclosed by Teyeb. Both references aim to solve adjustment in MCG behavior without significant overhead/service interruption, such implementation advantageously lead to more resource allocation with the smart role swapping between SCG and MCG.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Futaki et al. (US 2019/0182716) - A radio access network (RAN) node (11) is configured to send, to another RAN node (12), first control information regarding at least one of one or more bandwidth parts (BWPs) configured in a system bandwidth. It is thus, for example, possible to contribute to inter-radio access network (RAN) node (e.g., inter-gNB) signaling enhanced to handle bandwidth parts.
THIS ACTION IS MADE FINAL. 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 QUAN M HUA whose telephone number is (571)270-7232. The examiner can normally be reached 10:30-6:30.
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, Anthony Addy can be reached at 571-272-7795. 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.
/QUAN M HUA/Primary Examiner, Art Unit 2645