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 09/11/2025 have been considered for examination. Claims 1, 3-6, 8, and 10-13 are pending in the instant application.
Note that the contingent limitation is still existed in Claims 1, and 3-6. The detail is in the below instant Office action.
With regard to the 102/103 rejections, Applicant’s arguments filed 03/31/2025 (see pages 12-16 of Remarks) in view of the amendments have been fully considered but are not persuasive at least in view of the reasons set forth below. Further, Examiner notes that Applicant’s amendments necessitated the new ground(s) of rejection presented in the instant Office Action.
Regarding claims 1 and 8, Applicant argued:
Claim 1, as amended, renders the rejection moot because Guorong as cited in the Office Action does not teach or suggest at least to "based on a determination that the PRACH occasions are not configured for the active UL BWP and the second initial UL BWP related to the RedCap UE is configured by the second configuration information, switching the active UL BWP to the second initial UL BWP related to the RedCap UE" as recited in Claim 1 (This part of claim 1 can be found in the Specification as filed such as in paragraph [0152]-[0162] (Page 9 of Remark)).
In the cited portion in Guorong, Paragraph [0099], “For example, if the Redcap UE deems that the initial DL BWP …that the Redcap UE uses the initial DL BWP separately configured for the Redcap UE, …. as an initial DL BWP with a BWP-id of 0 of its own”, Guorong discloses that the Redcap UE uses the DL BWP configured to the Redcap UE. This does not teach or suggest that two step conditions, as recited in Claim 1, require: (i) a determination that "PRACH occasions are not configured for the active UL BWP," and (ii) a determination that "the second initial UL BWP related to the RedCap UE is configured" as recited in Claim 1. Under the assumption, as the Office Action alleged, that the "initial DL BWP" as cited in Guorong constitutes the ""initial UL BWP" as recited in Claim 1, a RedCap UE always uses the initial UL BWP designated for RedCap UEs if configured; otherwise, the RedCap UE always uses the initial UL BWP for normal UEs. While Guorong discloses the limitation and restriction for the RedCap UE, Guorong fails to teach or suggest the step of determining whether both of these specific conditions are satisfied.
In the TABLE 2, as shown in Page 10 of Remarks, Guorong explains that the UE switches directly to the initial UL BWP for a normal UE as soon as condition (i) (e.g., as recited in claim 1) is met. This is sufficiently distinct from the operational sequence of the UE as recited in Claim 1. Claim 1 recites the two steps condition for the RedCap UE's operation.
As provided in Guorong, Paragraph [0097], Guorong discloses that an initial uplink (UL) BWP separately configured for the Redcap UE is used. In other words, it refers to as "a second initial uplink BWP." Guorong fails to disclose the specific scenario as recited in Claim 1 reciting two steps of operation indicating a first initial UL BWP (for normal UEs) and a second initial UL BWP (for RedCap UEs) that are configured for the UEs.
Claim 1 recites "receiving, from a base station, first configuration information … on a second initial UL BWP related to the RedCapUE." And Claim 1 recites that the UE switches to the second initial UL BWP, instead of the first initial UL BWP, upon satisfaction of conditions (i) and (ii) even if the first initial UL BWP has been configured. However, Guorong never discloses the explicit criteria how a RedCap UE determines which BWP to switch to in this situation as recited in Claim 1. Paragraph [0116] of Guorong merely discloses that a UE uses the "relevant configuration of the random access" within an initial BWP configuration. This act of using a configuration is different from the affirmative step of performing a switch of the active UL BWP to either the first or the second initial UL BWP as recited in Claim 1.
The Examiner indicated that "[c]laim 1 can be summarized: when the random access procedure is initiated on a serving cell; … switch the active UL BWP to the first initial UL BWP (the second condition)." Office Action, p. 4. However, prior to the effective filing date of this application, the specific details concerning the introduction and management of a dedicated initial UL BWP for RedCap UEs had not been substantially discussed or developed in the art. Therefore, the claimed elements of Claim 1 ( e.g., two initial UL BWPs being configured simultaneously) – the determination based on at least two conditions and the corresponding sequence of UE's operations - would not have been obvious. (see, pages 8-12 of Remarks).
In response to Applicant’s argument, Examiner respectfully disagrees.
In the argument, Applicant argued with various points, Guorong does not disclose Claim 1. However, Examiner respectfully disagrees.
First, instead of Specification Paragraphs [0152]-[0162] of Application, Claim 1 is better represented by Paragraphs [0118]-[0129] of Specification of Application. As described in Paragraphs [0092]-[0108] of Specification of Application (that is specified in TS 38.321, Section 5.1.2 and 5.15), the procedure Paragraphs [0100]-[0108] is defined for the normal UE. Based on this, it is modified for the RedCap UE in [0119]–[0129]. This modification pretty much represents Claim 1, specifically, the part “based on the determination … to the RedCap UE,”
Although the explanation is not provided by step-by-step like Paragraphs [0119]-[0120] of Specification of Application, this modification is already described in Paragraphs [0096]-[0099] of Guorong. Note that the first initial downlink BWP and the first initial uplink BWP is for the RedCap UE, namely, “first” is corresponding to “second” in Claim 1. Guorong teaches that when the initial downlink BWP and the initial uplink BWP is configured for the normal UE and the first initial downlink BWP and the first initial uplink BWP is configured for the RedCap UE, separately, the method described in steps 1> to 3> before step 1> else in Table 2 of Guorong (originally coming from Sec. 5.15 of TS 38.321 (can find in version 16.5.0 (2021-06)) can be directly applied for both a normal UE and a RedCap UE. Only difference is that the initial Downlink BWP and the initial Uplink BWP is used for normal UE, while, for RedCap UE, the initial Downlink BWP and the initial Uplink BWP in Table 2 are replaced by the first initial Downlink BWP and the first initial Uplink BWP, respectively, as mentioned in Paragraphs [0096]-[0099] of Guorong, specifically, in Paragraph [0099], “if the Redcap UE deems … with a BWP-id of 0 of its own.” In addition, based on the configuration, the switching steps between a normal UE and a RedCap UE is described in Paragraphs [0102] and [0103]. Based on this observation, the description of Guorong in the above, in Paragraphs [0096]-[0099] and [0102]-[0103] and the steps before step 1> “else” of Table 2 are exactly corresponding to the procedure in Paragraphs [0119]-[0129] of Specification of Application, although both the normal UE case and the RedCap UE case are not described in step-by-step, neatly.
Further, Paragraph [0096] of Guorong also teaches the part of Claim 1 “identifying that a random access procedure is initiated on a serving cell”
Next, the first part of Claim 1, “receiving, from a base station, … a second initial UL BWP related to the RedCap UE,” can be taught by Paragraphs [0078], [0081]-[0083], [0097] and [0129] and Fig. 2. Paragraph [0078], “the Redcap UE may also use both the initial DL BWP configured for the non-RedCap UE … or another value” and with Fig. 2, Paragraph [0083]“According to operation 102, different from the non-Redcap UE, … (such as SIB1 or other SIBs) before random access is completed (e.g. before or during a random access procedure)” explains the initial downlink BWP for a normal UE and the first initial downlink BWP for RedCap UE are configured separately. Accordingly, as shown in [0097], and [0130], the initial Uplink BWP for a normal UE and the first initial Uplink BWP for RedCap UE are separately configured. Here, “initial” and “first initial” can be considered as “first initial” and “second initial” of Claim 1, respectively.
Therefore, it is clear that the amended Claim 1 is disclosed by Guorong and by the same reasoning, the amended claim 8 is also disclosed by Guorong.
However, since the amended claim 1 and 8 has changed the scope of the previous claim 1 and 8, the new rejection is presented in this instant office action in the below.
Continued Examination Under 37 CFR 1.114
A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 09/11/2025 has been entered.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claims 1, 3-4, 8, and 10-11 are rejected under U.S.C. 102(a)(2) as being anticipated by Guorong LI and et. al (USPub No: US20240224338A1, hereinafter “Guorong”).
Regarding claim 1, Guorong teaches a method performed by a reduced capability (RedCap) user equipment (UE) in a wireless communication system, the method comprising: receiving, from a base station, first configuration information on a first initial uplink (UL) bandwidth part (BWP) and second configuration information on a second initial UL BWP related to the RedCap UE; (Guorong, in Paragraphs [0078] teaches that SIB1 or other system information transmitted by the network device (such as a gNB) may include configuration of an initial DL BWP configured for a non-reduced capability terminal equipment (non-Redcap UE) and the configuration of the initial DL BWP separately configured or defined for the Redcap UE. The Redcap UE may ignore the configuration of the initial DL BWP configured for the non-Redcap UE, and take the initial DL BWP configured separately for the Redcap UE as an initial DL BWP of its own or take the configuration of the initial DL BWP configured separately for the Redcap UE as configuration of an initial DL BWP of its own, for example, the initial DL BWP has a BWP-id of 0; or, the Redcap UE may also use both the initial DL BWP configured for the non- Redcap UE and the initial DL BWP separately configured for the Redcap UE as initial DL BWPs of its own. The two initial DL BWPs may be distinguished by using different BWP-ids, for example, the initial DL BWP configured for the non-Redcap UE has a BWP-id of 0, and the initial DL BWP configured separately for the Redcap UE has a BWP-id of 5 or another value (which may be predefined or may be configured by the network device); or, vice versa. The initial downlink BWP is called as the first initial downlink BWP as described in Fig. 1. The separate configuration example is described in Fig. 2 and in Paragraphs [0081]-[0083]. Accordingly, as described in Paragraphs [0097] and [0130], the first initial uplink BWP (the second configuration in the claim) for RedCap UE and the initial uplink BWP (the first configuration in the claim) for non-RedCap UE (normal UE) are separately configured or defined. Based on this observation, the first configuration information on a first initial uplink (UL) bandwidth part (BWP) and second configuration information on a second initial UL BWP related to the RedCap UE can be received from the base station.) identifying that a random access procedure is initiated on a serving cell; determining whether physical random access channel (PRACH) occasions are configured for an active UL BWP; and based on a determination that the PRACH occasions are not configured for the active UL BWP and the second initial UL BWP related to the RedCap UE is configured by the second configuration information, switching the active UL BWP to the second initial UL BWP related to the RedCap UE (Guorong, in Paragraphs [0096]-[0103], teaches that the reduced capability UE receives a signal by using the first initial downlink BWP during or after an initialization procedure of a random access procedure. For example, during the initialization procedure of the random access procedure, it may be that the reduced capability UE receives the signal by using the first initial downlink BWP (considered as the second initial downlink BWP for the claim) when an initial uplink (UL) BWP (initialUplinkBWP) separately configured for the Redcap UE is used, that is, when the reduced capability UE uses a first initial uplink BWP (considered as the second initial uplink BWP for the claim), the first initial uplink BWP being an initial uplink BWP separately configured or defined for the reduced capability UE. For example, if the Redcap UE deems that the initial DL BWP separately configured for the Redcap UE has a BWP-id of 0, there is no need to modify the BWP operation in Sub-section 5.15 of the MAC Specification (will be attached). Namely, the BWP operation defined in Sub-section 5.15 of the MAC Specification is for the normal UE and that is described in Table 2 when ignoring the underline part. For the RedCap UE, the operation for the normal UE is can be used for the RedCap UE with replacing the initial UL BWP and the initial downlink BWP by the first initial UL BWP for the RedCap UE (is considered as the second initial UL BWP) and the first initial downlink BWP, respectively. Further, in Paragraphs [0103], Guorong teaches that after the initialization procedure of the random access procedure, before executing a random access resource selection procedure, the Redcap UE may switch the downlink BWP to the first initial downlink BWP, or adjust the receiving bandwidth to the first initial downlink BWP. Namely, when the RedCap UE is configured, the downlink BWP is switched to the first downlink BWP and the initial uplink BWP is switched to the first initial uplink BWP in Table 2. Based on the above description, Guorong teaches, in Paragraphs [0096]-[0099] and [0103], that from Table 2, the following pseudo code can be configured:
upon initiation of the random access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure, the MAC entity shall for the selected carrier of this Serving Cell:
Step 1> if PRACH occasions are not configured for the active UL BWP,
Step 2>if non-RedCap UE (normal UE) is configured, switch the active UL BWP to BWP indicated by initialUplinkBWP (the first initial uplink BWP for the claim).
Step 2> if RedCap UE is configured, switch the active UL BWP to BWP indicated by the first initial uplink BWP (the second initial uplink BWP for the claim).
Step 2> if the Serving Cell is an SpCell:
Step 3> if normal UE is configured, switch the active DL BWP to BWP indicated by initialDownlinkBWP (the first initial downlink BWP for the claim or Specfication of Application).
Step 3> if RedCap UE is configured, switch the active DL BWP to BWP indicated by the first downlink BWP (the second initial downlink BWP for the claim or Specfication of Application).
As explained in the above, these steps can be applied for the normal UE and the RedCap UE. It is exactly matched to Paragraphs [0119]-[0129] of Specification of Application. Based on this observation, it is clear that when a random access procedure is initiated on a serving cell, the PRACH occasions are not configured, the second initial UL BWP related to the RedCap UE is configured by the second configuration information, the active UL BWP is switched to the second initial UL BWP related to the RedCap UE.
While Guorong teaches the features of claim 1 as indicated above, the Examiner notes that the claim recites “determining whether physical random access channel (PRACH) occasions are configured for an active UL BWP” This claim contains a contingent limitation. The broadest reasonable interpretation of a method (or process) claim having contingent limitations requires only those steps that must be performed and does not include steps that are not required to be performed because the condition(s) precedent are not met. The limitation starting with "determining whether physical random access channel (PRACH) occasions are configured for an active UL BWP" is a contingent limitation. the claim has been interpreted to not require the conditions stated to be met. See MPEP 2111.04 subsection 11.
Regarding claim 3, Guorong teaches the features defined in the claim 1, -refer to the indicated claim for reference(s).
Guorong further teaches further comprising: receiving, from the base station, third configuration information on a first initial downlink (DL) BWP and fourth configuration information on a second initial DL BWP related to the RedCap UE, (Guorong, in Paragraphs [0078] teaches that SIB1 or other system information (it can be the third configuration or the fourth configuration information) transmitted by the network device (such as a gNB) may include configuration of an initial DL BWP configured for a non-reduced capability terminal equipment (non-Redcap UE, normal UE) and the configuration of the initial DL BWP separately configured or defined for the Redcap UE. The Redcap UE may ignore the configuration of the initial DL BWP configured for the non-Redcap UE, and take the initial DL BWP configured separately for the Redcap UE as an initial DL BWP of its own or take the configuration of the initial DL BWP configured separately for the Redcap UE as configuration of an initial DL BWP of its own, for example, the initial DL BWP has a BWP-id of 0; or, the Redcap UE may also use both the initial DL BWP configured for the non- Redcap UE and the initial DL BWP separately configured for the Redcap UE as initial DL BWPs of its own. The two initial DL BWPs may be distinguished by using different BWP-ids, for example, the initial DL BWP (the first initial DL BWP for the claim) configured for the non-Redcap UE has a BWP-id of 0, and the initial DL BWP configured separately for the Redcap UE has a BWP-id of 5 or another value (which may be predefined or may be configured by the network device); or, vice versa. The initial downlink BWP is called as the first initial downlink BWP (the second initial DL BWP for the claim) as described in Fig. 1. The separate configuration example is described in Fig. 2 and in Paragraphs [0081]-[0083]. Based on this observation, third configuration information on a first initial DL BWP and fourth configuration information on a second initial DL BWP related to the RedCap UE may be received from the base station.) based on a determination that the PRACH occasions are not configured for the active UL BWP, determining whether the serving cell is a special cell (SpCell); and based on a determination that the PRACH occasions are not configured for the active UL BWP, the serving cell is the SpCell, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, switching an active DL BWP to the second initial DL BWP related to the RedCap UE. (Guorong, in Paragraphs [0096]-[0103], teaches that the reduced capability UE receives a signal by using the first initial downlink BWP during or after an initialization procedure of a random access procedure. For example, during the initialization procedure of the random access procedure, it may be that the reduced capability UE receives the signal by using the first initial downlink BWP (considered as the second initial downlink BWP for the claim) when an initial uplink (UL) BWP (initialUplinkBWP) separately configured for the Redcap UE is used, that is, when the reduced capability UE uses a first initial uplink BWP (considered as the second initial uplink BWP for the claim), the first initial uplink BWP being an initial uplink BWP separately configured or defined for the reduced capability UE. For example, if the Redcap UE deems that the initial DL BWP separately configured for the Redcap UE has a BWP-id of 0, there is no need to modify the BWP operation in Sub-section 5.15 of the MAC Specification (will be attached). Namely, the BWP operation defined in Sub-section 5.15 of the MAC Specification is for the normal UE and that is described in Table 2 when ignoring the underline part. For the RedCap UE, the operation for the normal UE is can be used for the RedCap UE with replacing the initial UL BWP and the initial downlink BWP by the first initial UL BWP for the RedCap UE (is considered as the second initial UL BWP) and the first initial downlink BWP, respectively. Further, in Paragraphs [0103], Guorong teaches that after the initialization procedure of the random access procedure, before executing a random access resource selection procedure, the Redcap UE may switch the downlink BWP to the first initial downlink BWP, or adjust the receiving bandwidth to the first initial downlink BWP. Namely, when the RedCap UE is configured, the downlink BWP is switched to the first downlink BWP and the initial uplink BWP is switched to the first initial uplink BWP in Table 2. Based on the above description, Guorong teaches, in Paragraphs [0096]-[0099] and [0103], that from Table 2, the following pseudo code can be configured:
upon initiation of the random access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure, the MAC entity shall for the selected carrier of this Serving Cell:
Step 1> if PRACH occasions are not configured for the active UL BWP,
Step 2>if non-RedCap UE (normal UE) is configured, switch the active UL BWP to BWP indicated by initialUplinkBWP (the first initial uplink BWP for the claim).
Step 2> if RedCap UE is configured, switch the active UL BWP to BWP indicated by the first initial uplink BWP (the second initial uplink BWP for the claim).
Step 2> if the Serving Cell is an SpCell:
Step 3> if normal UE is configured, switch the active DL BWP to BWP indicated by initialDownlinkBWP (the first initial downlink BWP for the claim or Specfication of Application).
Step 3> if RedCap UE is configured, switch the active DL BWP to BWP indicated by the first downlink BWP (the second initial downlink BWP for the claim or Specfication of Application).
As explained in the above, these steps can be applied for the normal UE and the RedCap UE. It is exactly matched to Paragraphs [0119]-[0129] of Specification of Application. Based on this observation, it is clear that when a random access procedure is initiated on a serving cell, the PRACH occasions are not configured for the active UL BWP, the serving cell is the SpCell, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, an active DL BWP is switched to the second itnitial DL BWP related to the RedCap UE.
While Guorong teaches the features of claim 3 as indicated above, the Examiner notes that the claim recites “determining whether the serving cell is a special cell (SpCell)” This claim contains a contingent limitation. The broadest reasonable interpretation of a method (or process) claim having contingent limitations requires only those steps that must be performed and does not include steps that are not required to be performed because the condition(s) precedent are not met. The limitation starting with "determining whether the serving cell is a special cell (SpCell)" is a contingent limitation. the claim has been interpreted to not require the conditions stated to be met. See MPEP 2111.04 subsection 11.
Regarding claim 4, Guorong teaches the features defined in the claim 3, -refer to the indicated claim for reference(s).
Guorong further teaches based on a determination that the PRACH occasions are not configured for the active UL BWP, determining whether the serving cell is a special cell (SpCell); and based on a determination that the PRACH occasions are not configured for the active UL BWP, the serving cell is the SpCell, and a second initial DL BWP related to the RedCap UE is not configured, switching an active DL BWP to the first initial DL BWP. (Guorong, in Paragraphs [0096]-[0103], teaches that the reduced capability UE receives a signal by using the first initial downlink BWP during or after an initialization procedure of a random access procedure. For example, during the initialization procedure of the random access procedure, it may be that the reduced capability UE receives the signal by using the first initial downlink BWP (considered as the second initial downlink BWP for the claim) when an initial uplink (UL) BWP (initialUplinkBWP) separately configured for the Redcap UE is used, that is, when the reduced capability UE uses a first initial uplink BWP (considered as the second initial uplink BWP for the claim), the first initial uplink BWP being an initial uplink BWP separately configured or defined for the reduced capability UE. For example, if the Redcap UE deems that the initial DL BWP separately configured for the Redcap UE has a BWP-id of 0, there is no need to modify the BWP operation in Sub-section 5.15 of the MAC Specification (will be attached). Namely, the BWP operation defined in Sub-section 5.15 of the MAC Specification is for the normal UE and that is described in Table 2 when ignoring the underline part. For the RedCap UE, the operation for the normal UE is can be used for the RedCap UE with replacing the initial UL BWP and the initial downlink BWP by the first initial UL BWP for the RedCap UE (is considered as the second initial UL BWP) and the first initial downlink BWP, respectively. Further, in Paragraphs [0103], Guorong teaches that after the initialization procedure of the random access procedure, before executing a random access resource selection procedure, the Redcap UE may switch the downlink BWP to the first initial downlink BWP, or adjust the receiving bandwidth to the first initial downlink BWP. Namely, when the RedCap UE is configured, the downlink BWP is switched to the first downlink BWP and the initial uplink BWP is switched to the first initial uplink BWP in Table 2. Based on the above description, Guorong teaches, in Paragraphs [0096]-[0099] and [0103], that from Table 2, the following pseudo code can be configured:
upon initiation of the random access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure, the MAC entity shall for the selected carrier of this Serving Cell:
Step 1> if PRACH occasions are not configured for the active UL BWP,
Step 2>if non-RedCap UE (normal UE) is configured, switch the active UL BWP to BWP indicated by initialUplinkBWP (the first initial uplink BWP for the claim).
Step 2> if RedCap UE is configured, switch the active UL BWP to BWP indicated by the first initial uplink BWP (the second initial uplink BWP for the claim).
Step 2> if the Serving Cell is an SpCell:
Step 3> if normal UE is configured, switch the active DL BWP to BWP indicated by initialDownlinkBWP (the first initial downlink BWP for the claim or Specfication of Application).
Step 3> if RedCap UE is configured, switch the active DL BWP to BWP indicated by the first downlink BWP (the second initial downlink BWP for the claim or Specfication of Application).
As explained in the above, these steps can be applied for the normal UE and the RedCap UE. It is exactly matched to Paragraphs [0119]-[0129] of Specification of Application. Based on this observation, it is clear that when a random access procedure is initiated on a serving cell, the PRACH occasions are not configured for the active UL BWP, the serving cell is the SpCell, and the second initial DL BWP related to the RedCap UE is not configured, an active DL BWP is switched to the second itnitial DL BWP related to the RedCap UE.
While Guorong teaches the features of claim 4 as indicated above, the Examiner notes that the claim recites “determining whether the serving cell is a special cell (SpCell)” This claim contains a contingent limitation. The broadest reasonable interpretation of a method (or process) claim having contingent limitations requires only those steps that must be performed and does not include steps that are not required to be performed because the condition(s) precedent are not met. The limitation starting with "determining whether the serving cell is a special cell (SpCell)" is a contingent limitation. the claim has been interpreted to not require the conditions stated to be met. See MPEP 2111.04 subsection 11.
Regarding claim 8, Guorong teaches that a reduced capability (RedCap) user equipment (UE) in a wireless communication system, the UE comprising: a transceiver; and a controller operably connected to the transceiver, the controller configured to: (Guorong, in Fig. 15 and in Paragraph [0253], teaches that FIG. 15 is a schematic diagram of a terminal equipment of the embodiment of the ninth aspect. A terminal equipment 1500 may include a processor 1510 and a memory 1520, the memory 1520 storing data and programs and being coupled to the processor 1510. It should be noted that this figure is illustrative only, and other types of structures may also be used, so as to supplement or replace this structure and achieve a telecommunications function or other functions. For example, the terminal equipment 1500 may be a reduced capability UE. Therefore, it is clear that a reduced capability (RedCap) user equipment (UE) in a wireless communication system is comprising a transceiver and a controller) receive, from a base station, first configuration information on a first initial uplink (UL) bandwidth part (BWP) and second configuration information on a second initial UL BWP related to the RedCap UE; (Guorong, in Paragraphs [0078] teaches that SIB1 or other system information transmitted by the network device (such as a gNB) may include configuration of an initial DL BWP configured for a non-reduced capability terminal equipment (non-Redcap UE) and the configuration of the initial DL BWP separately configured or defined for the Redcap UE. The Redcap UE may ignore the configuration of the initial DL BWP configured for the non-Redcap UE, and take the initial DL BWP configured separately for the Redcap UE as an initial DL BWP of its own or take the configuration of the initial DL BWP configured separately for the Redcap UE as configuration of an initial DL BWP of its own, for example, the initial DL BWP has a BWP-id of 0; or, the Redcap UE may also use both the initial DL BWP configured for the non- Redcap UE and the initial DL BWP separately configured for the Redcap UE as initial DL BWPs of its own. The two initial DL BWPs may be distinguished by using different BWP-ids, for example, the initial DL BWP configured for the non-Redcap UE has a BWP-id of 0, and the initial DL BWP configured separately for the Redcap UE has a BWP-id of 5 or another value (which may be predefined or may be configured by the network device); or, vice versa. The initial downlink BWP is called as the first initial downlink BWP as described in Fig. 1. The separate configuration example is described in Fig. 2 and in Paragraphs [0081]-[0083]. Accordingly, as described in Paragraphs [0097] and [0130], the first initial uplink BWP (the second configuration in the claim) for RedCap UE and the initial uplink BWP (the first configuration in the claim) for non-RedCap UE (normal UE) are separately configured or defined. Based on this observation, the first configuration information on a first initial uplink (UL) bandwidth part (BWP) and second configuration information on a second initial UL BWP related to the RedCap UE can be received from the base station.) identify that a random access procedure is initiated on a serving cell; determine whether physical random access channel (PRACH) occasions are configured for an active UL BWP; and based on a determination that the PRACH occasions are not configured for the active UL BWP and the second initial UL BWP related to the RedCap UE is configured by the second configuration information, switching the active UL BWP to the second initial UL BWP related to the RedCap UE (Guorong, in Paragraphs [0096]-[0103], teaches that the reduced capability UE receives a signal by using the first initial downlink BWP during or after an initialization procedure of a random access procedure. For example, during the initialization procedure of the random access procedure, it may be that the reduced capability UE receives the signal by using the first initial downlink BWP (considered as the second initial downlink BWP for the calim) when an initial uplink (UL) BWP (initialUplinkBWP) separately configured for the Redcap UE is used, that is, when the reduced capability UE uses a first initial uplink BWP (considered as the second initial uplink BWP for the claim), the first initial uplink BWP being an initial uplink BWP separately configured or defined for the reduced capability UE. For example, if the Redcap UE deems that the initial DL BWP separately configured for the Redcap UE has a BWP-id of 0, there is no need to modify the BWP operation in Sub-section 5.15 of the MAC Specification (will be attached). Namely, the BWP operation defined in Sub-section 5.15 of the MAC Specification is for the normal UE and that is described in Table 2 when ignoring the underline part. For the RedCap UE, the operation for the normal UE is can be used for the RedCap UE with replacing the initial UL BWP and the initial downlink BWP by the first initial UL BWP for the RedCap UE (is considered as the second initial UL BWP) and the first initial downlink BWP, respectively. Further, in Paragraphs [0103], Guorong teaches that after the initialization procedure of the random access procedure, before executing a random access resource selection procedure, the Redcap UE may switch the downlink BWP to the first initial downlink BWP, or adjust the receiving bandwidth to the first initial downlink BWP. Namely, when the RedCap UE is configured, the downlink BWP is switched to the first downlink BWP and the initial uplink BWP is switched to the first initial uplink BWP in Table 2. Based on the above description, Guorong teaches, in Paragraphs [0096]-[0099] and [0103], that from Table 2, the following pseudo code can be configured:
upon initiation of the random access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure, the MAC entity shall for the selected carrier of this Serving Cell:
Step 1> if PRACH occasions are not configured for the active UL BWP,
Step 2>if non-RedCap UE (normal UE) is configured, switch the active UL BWP to BWP indicated by initialUplinkBWP (the first initial uplink BWP for the claim).
Step 2> if RedCap UE is configured, switch the active UL BWP to BWP indicated by the first initial uplink BWP (the second initial uplink BWP for the claim).
Step 2> if the Serving Cell is an SpCell:
Step 3> if normal UE is configured, switch the active DL BWP to BWP indicated by initialDownlinkBWP (the first initial downlink BWP for the claim or Specfication of Application).
Step 3> if RedCap UE is configured, switch the active DL BWP to BWP indicated by the first downlink BWP (the second initial downlink BWP for the claim or Specfication of Application).
As explained in the above, these steps can be applied for the normal UE and the RedCap UE. It is exactly matched to Paragraphs [0119]-[0129] of Specification of Application. Based on this observation, it is clear that when a random access procedure is initiated on a serving cell, the PRACH occasions are not configured, the second initial UL BWP related to the RedCap UE is configured by the second configuration information, the active UL BWP is switched to the second initial UL BWP related to the RedCap UE.
Regarding claim 10, Guorong teaches the features defined in the claim 8, -refer to the indicated claim for reference(s).
Guorong further teaches that wherein the controller is further configured to: receive, from the base station via transceiver, third configuration information on a first initial downlink (DL) BWP and fourth configuration information on a second initial DL BWP related to the RedCap UE, (Guorong, in Paragraphs [0078] teaches that SIB1 or other system information (it can be the third configuration or the fourth configuration information) transmitted by the network device (such as a gNB) may include configuration of an initial DL BWP configured for a non-reduced capability terminal equipment (non-Redcap UE, normal UE) and the configuration of the initial DL BWP separately configured or defined for the Redcap UE. The Redcap UE may ignore the configuration of the initial DL BWP configured for the non-Redcap UE, and take the initial DL BWP configured separately for the Redcap UE as an initial DL BWP of its own or take the configuration of the initial DL BWP configured separately for the Redcap UE as configuration of an initial DL BWP of its own, for example, the initial DL BWP has a BWP-id of 0; or, the Redcap UE may also use both the initial DL BWP configured for the non- Redcap UE and the initial DL BWP separately configured for the Redcap UE as initial DL BWPs of its own. The two initial DL BWPs may be distinguished by using different BWP-ids, for example, the initial DL BWP (the first initial DL BWP for the claim) configured for the non-Redcap UE has a BWP-id of 0, and the initial DL BWP configured separately for the Redcap UE has a BWP-id of 5 or another value (which may be predefined or may be configured by the network device); or, vice versa. The initial downlink BWP is called as the first initial downlink BWP (the second initial DL BWP for the claim) as described in Fig. 1. The separate configuration example is described in Fig. 2 and in Paragraphs [0081]-[0083]. Based on this observation, third configuration information on a first initial DL BWP and fourth configuration information on a second initial DL BWP related to the RedCap UE may be received from the base station.) based on a determination that the PRACH occasions are not configured for the active UL BWP, determine whether the serving cell is a special cell (SpCell); and based on a determination that the PRACH occasions are not configured for the active UL BWP, the serving cell is the SpCell, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, switching an active DL BWP to the second initial DL BWP related to the RedCap UE. (Guorong, in Paragraphs [0096]-[0103], teaches that the reduced capability UE receives a signal by using the first initial downlink BWP during or after an initialization procedure of a random access procedure. For example, during the initialization procedure of the random access procedure, it may be that the reduced capability UE receives the signal by using the first initial downlink BWP (considered as the second initial downlink BWP for the claim) when an initial uplink (UL) BWP (initialUplinkBWP) separately configured for the Redcap UE is used, that is, when the reduced capability UE uses a first initial uplink BWP (considered as the second initial uplink BWP for the claim), the first initial uplink BWP being an initial uplink BWP separately configured or defined for the reduced capability UE. For example, if the Redcap UE deems that the initial DL BWP separately configured for the Redcap UE has a BWP-id of 0, there is no need to modify the BWP operation in Sub-section 5.15 of the MAC Specification (will be attached). Namely, the BWP operation defined in Sub-section 5.15 of the MAC Specification is for the normal UE and that is described in Table 2 when ignoring the underline part. For the RedCap UE, the operation for the normal UE is can be used for the RedCap UE with replacing the initial UL BWP and the initial downlink BWP by the first initial UL BWP for the RedCap UE (is considered as the second initial UL BWP) and the first initial downlink BWP, respectively. Further, in Paragraphs [0103], Guorong teaches that after the initialization procedure of the random access procedure, before executing a random access resource selection procedure, the Redcap UE may switch the downlink BWP to the first initial downlink BWP, or adjust the receiving bandwidth to the first initial downlink BWP. Namely, when the RedCap UE is configured, the downlink BWP is switched to the first downlink BWP and the initial uplink BWP is switched to the first initial uplink BWP in Table 2. Based on the above description, Guorong teaches, in Paragraphs [0096]-[0099] and [0103], that from Table 2, the following pseudo code can be configured:
upon initiation of the random access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure, the MAC entity shall for the selected carrier of this Serving Cell:
Step 1> if PRACH occasions are not configured for the active UL BWP,
Step 2>if non-RedCap UE (normal UE) is configured, switch the active UL BWP to BWP indicated by initialUplinkBWP (the first initial uplink BWP for the claim).
Step 2> if RedCap UE is configured, switch the active UL BWP to BWP indicated by the first initial uplink BWP (the second initial uplink BWP for the claim).
Step 2> if the Serving Cell is an SpCell:
Step 3> if normal UE is configured, switch the active DL BWP to BWP indicated by initialDownlinkBWP (the first initial downlink BWP for the claim or Specfication of Application).
Step 3> if RedCap UE is configured, switch the active DL BWP to BWP indicated by the first downlink BWP (the second initial downlink BWP for the claim or Specfication of Application).
As explained in the above, these steps can be applied for the normal UE and the RedCap UE. It is exactly matched to Paragraphs [0119]-[0129] of Specification of Application. Based on this observation, it is clear that when a random access procedure is initiated on a serving cell, the PRACH occasions are not configured for the active UL BWP, the serving cell is the SpCell, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, an active DL BWP is switched to the second itnitial DL BWP related to the RedCap UE.
Regarding claim 11, Guorong teaches the features defined in the claim 8, -refer to the indicated claim for reference(s).
Guorong further teaches that based on a determination that the PRACH occasions are not configured for the active UL BWP, determining whether the serving cell is a special cell (SpCell); and based on a determination that the PRACH occasions are not configured for the active UL BWP, the serving cell is the SpCell, and a second initial DL BWP related to the RedCap UE is not configured, switching an active DL BWP to the first initial DL BWP. (Guorong, in Paragraphs [0096]-[0103], teaches that the reduced capability UE receives a signal by using the first initial downlink BWP during or after an initialization procedure of a random access procedure. For example, during the initialization procedure of the random access procedure, it may be that the reduced capability UE receives the signal by using the first initial downlink BWP (considered as the second initial downlink BWP for the claim) when an initial uplink (UL) BWP (initialUplinkBWP) separately configured for the Redcap UE is used, that is, when the reduced capability UE uses a first initial uplink BWP (considered as the second initial uplink BWP for the claim), the first initial uplink BWP being an initial uplink BWP separately configured or defined for the reduced capability UE. For example, if the Redcap UE deems that the initial DL BWP separately configured for the Redcap UE has a BWP-id of 0, there is no need to modify the BWP operation in Sub-section 5.15 of the MAC Specification (will be attached). Namely, the BWP operation defined in Sub-section 5.15 of the MAC Specification is for the normal UE and that is described in Table 2 when ignoring the underline part. For the RedCap UE, the operation for the normal UE is can be used for the RedCap UE with replacing the initial UL BWP and the initial downlink BWP by the first initial UL BWP for the RedCap UE (is considered as the second initial UL BWP) and the first initial downlink BWP, respectively. Further, in Paragraphs [0103], Guorong teaches that after the initialization procedure of the random access procedure, before executing a random access resource selection procedure, the Redcap UE may switch the downlink BWP to the first initial downlink BWP, or adjust the receiving bandwidth to the first initial downlink BWP. Namely, when the RedCap UE is configured, the downlink BWP is switched to the first downlink BWP and the initial uplink BWP is switched to the first initial uplink BWP in Table 2. Based on the above description, Guorong teaches, in Paragraphs [0096]-[0099] and [0103], that from Table 2, the following pseudo code can be configured:
upon initiation of the random access procedure on a Serving Cell, after the selection of carrier for performing Random Access procedure, the MAC entity shall for the selected carrier of this Serving Cell:
Step 1> if PRACH occasions are not configured for the active UL BWP,
Step 2>if non-RedCap UE (normal UE) is configured, switch the active UL BWP to BWP indicated by initialUplinkBWP (the first initial uplink BWP for the claim).
Step 2> if RedCap UE is configured, switch the active UL BWP to BWP indicated by the first initial uplink BWP (the second initial uplink BWP for the claim).
Step 2> if the Serving Cell is an SpCell:
Step 3> if normal UE is configured, switch the active DL BWP to BWP indicated by initialDownlinkBWP (the first initial downlink BWP for the claim or Specfication of Application).
Step 3> if RedCap UE is configured, switch the active DL BWP to BWP indicated by the first downlink BWP (the second initial downlink BWP for the claim or Specfication of Application).
As explained in the above, these steps can be applied for the normal UE and the RedCap UE. It is exactly matched to Paragraphs [0119]-[0129] of Specification of Application. Based on this observation, it is clear that when a random access procedure is initiated on a serving cell, the PRACH occasions are not configured for the active UL BWP, the serving cell is the SpCell, and the second initial DL BWP related to the RedCap UE is not configured, an active DL BWP is switched to the second itnitial DL BWP related to the RedCap UE.
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 5-6 and 12-13 are rejected under U.S.C. 103 as being unpatentable over Guorong LI and et. al. (USPub No: US20240224338A1, hereinafter “Guorong”) in a view of Dongru LI and et. al. (USPub No: US20240163730A1, hereinafter “Dongru”).
Regarding claim 5, Guorong teaches the features defined in the claim 3, -refer to the indicated claim for reference(s).
Guorong does not teach that based on a determination that a BWP inactivity timer associated with the active DL BWP expires, determining whether a default DL BWP is configured; and based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, switching the active DL BWP to the second initial DL BWP related to the RedCap UE.
However, Dongru teaches that based on a determination that a BWP inactivity timer associated with the active DL BWP expires, determining whether a default DL BWP is configured; (Dongru, in Fig. 2 and in Paragraphs [0135], [0101]-[0107], teaches that in Paragraph [0135], the initial bandwidth part mentioned in embodiments of this application includes at least one of an initial uplink bandwidth part (initial UL BWP) and an initial downlink bandwidth part (initial DL BWP). Namely, in the description, the initial bandwidth part indicates the initial UL BWP and the initial DL BWP. In Paragraph [0109], an example in which the terminal is the reduced capability terminal, the first initial bandwidth part is the initial bandwidth part configured for the reduced capability terminal by the network side device, and the second initial bandwidth part is the initial bandwidth part configured for the non-reduced capability terminal by the network side device is used, application of the target initial bandwidth part in the foregoing specific cases is described. In Paragraphs [0101]-[0102] and [0105]-[0106], the step 202 in Fig. 2 may further include: determining, by the terminal according to the first information, the target initial bandwidth part applied to a specific case in the first initial bandwidth part and/or the second initial bandwidth part, where the specific case includes at least one of the following cases: a bandwidth part inactivity timer (bwp-inactivitytimer) expires, and the terminal is not configured with a default bandwidth part; and the bandwidth part inactivity timer expires (bwp-inactivitytimer), and the default bandwidth part configured by the terminal is an initial bandwidth part. In this observation, it is clear that when the terminal determines a target initial (DL) bandwidth part, the terminal may check whether a BWP inactivity timer associated with an active downlink (DL) BWP expires and if the BWP inactivity timer expires, the terminal may check whether a default DL BWP is configured.) and based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, switching the active DL BWP to the second initial DL BWP related to the RedCap UE. (Dongru, in Fig. 2 and in Paragraph [0114], teaches that if the reduced capability terminal receives a clear indication (for example, configured through the first configuration information) to the target initial bandwidth part applied by the network side device after the RRC connection is released, the reduced capability terminal determines the target initial bandwidth part according to the indication. If there is no clear indication from the network side device, the reduced capability terminal may determine a default initial bandwidth part in the specific case according to the network configuration or protocol specification. In Fig. 2 and in Paragraphs [0122]-[0123], [0127], and [0130]-[0131], Dongru teaches that optionally, after step 202, to be specific, after the terminal determines the target initial bandwidth part, the method further includes: under a specific condition, switching to the target initial bandwidth part, where the first specific condition includes the following case: a bandwidth part inactivity timer expires, and the terminal is not configured with a default bandwidth part. After the terminal determines the target initial bandwidth part in the first initial bandwidth part (RedCap UE case) and/or the second initial bandwidth part (non-RedCap UE case) (as mentioned in Paragraph [0109]) according to the first information, if the foregoing specific condition is met, the terminal switches to the target initial bandwidth part. For example, in some embodiments, after the terminal determines the target initial bandwidth part, if the current active bandwidth part of the terminal is not the target initial bandwidth part, the terminal switches to the target initial bandwidth part. Note that as mentioned in the above, the initial bandwidth part includes at least one initial UL BWP and one DL BWP. In this observation, it is clear that if the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is configured, switching the active DL BWP to the second initial DL BWP related to the RedCap UE.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Guorong and Dongru to include the technique of based on a determination that a BWP inactivity timer associated with the active DL BWP expires, determining whether a default DL BWP is configured; and based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, switching the active DL BWP to the second initial DL BWP related to the RedCap UE of Dongru in the system of combination of Guorong to provide an efficient initial bandwidth part for a reduced capability terminal to increase the system throughput and communication performance, when there are a large quantity of terminal devices accessing a small cell (Dongru, see Paragraphs [0002] to [0004]);
While combination of Guorong and Dongru teaches the features of claim 5 as indicated above, Examiner notes that the claim recites “determining whether a default DL BWP is configured” This claim contains a contingent limitation. The broadest reasonable interpretation of a method (or process) claim having contingent limitations requires only those steps that must be performed and does not include steps that are not required to be performed because the condition(s) precedent are not met. The limitation starting with "determining whether a default DL BWP is configured" is a contingent limitation. the claim has been interpreted to not require the conditions stated to be met. See MPEP 2111.04 subsection 11.
Regarding claim 6, Guorong teaches the features defined in the claim 4, -refer to the indicated claim for reference(s).
Guorong does not teach that based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is not configured, switching the active DL BWP to the first initial DL BWP.
However, Dongru teaches based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is not configured, switching the active DL BWP to the first initial DL BWP (Dongru, in Fig. 2 and in Paragraphs [0122]-[0123], [0127], and [0130]-[0131], teaches that optionally, after step 202, to be specific, after the terminal determines the target initial bandwidth part, the method further includes: under a specific condition, switching to the target initial bandwidth part, where the first specific condition includes the following case: a bandwidth part inactivity timer expires, and the terminal is not configured with a default bandwidth part. After the terminal determines the target initial bandwidth part in the first initial bandwidth part (RedCap UE case) and/or the second initial bandwidth part (non-RedCap UE case) (as mentioned in Paragraph [0109]) according to the first information, if the foregoing specific condition is met, the terminal switches to the target initial bandwidth part. For example, in some embodiments, after the terminal determines the target initial bandwidth part, if the current active bandwidth part of the terminal is not the target initial bandwidth part, the terminal switches to the target initial bandwidth part. Note that as mentioned in the above, the initial bandwidth part includes at least one initial UL BWP and one DL BWP. In this observation, it is clear that if the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is not configured, switching the active DL BWP to the firtst initial DL BWP for non-RedCap UE.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Guorong and Dongru to include the technique of based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is not configured, switching the active DL BWP to the first initial DL BWP of Dongru in the system of combination of Guorong to provide an efficient initial bandwidth part for a reduced capability terminal to increase the system throughput and communication performance, when there are a large quantity of terminal devices accessing a small cell (Dongru, see Paragraphs [0002] to [0004]);
While combination of Guorong and Dongru teaches the features of claim 6 as indicated above, the Examiner notes that the claim recites “determining whether a default DL BWP is configured” This claim contains a contingent limitation. The broadest reasonable interpretation of a method (or process) claim having contingent limitations requires only those steps that must be performed and does not include steps that are not required to be performed because the condition(s) precedent are not met. The limitation starting with "determining whether a default DL BWP is configured" is a contingent limitation. the claim has been interpreted to not require the conditions stated to be met. See MPEP 2111.04 subsection 11.
Regarding claim 12, Guorong teaches the features defined in the claim 10, -refer to the indicated claim for reference(s).
Guorong does not teach that based on a determination that a BWP inactivity timer associated with the active DL BWP expires, determining whether a default DL BWP is configured; and based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, switching the active DL BWP to the second initial DL BWP related to the RedCap UE.
However, Dongru teaches that based on a determination that a BWP inactivity timer associated with the active DL BWP expires, determining whether a default DL BWP is configured; (Dongru, in Fig. 2 and in Paragraphs [0135], [0101]-[0107], teaches that in Paragraph [0135], the initial bandwidth part mentioned in embodiments of this application includes at least one of an initial uplink bandwidth part (initial UL BWP) and an initial downlink bandwidth part (initial DL BWP). Namely, in the description, the initial bandwidth part indicates the initial UL BWP and the initial DL BWP. In Paragraph [0109], an example in which the terminal is the reduced capability terminal, the first initial bandwidth part is the initial bandwidth part configured for the reduced capability terminal by the network side device, and the second initial bandwidth part is the initial bandwidth part configured for the non-reduced capability terminal by the network side device is used, application of the target initial bandwidth part in the foregoing specific cases is described. In Paragraphs [0101]-[0102] and [0105]-[0106], the step 202 in Fig. 2 may further include: determining, by the terminal according to the first information, the target initial bandwidth part applied to a specific case in the first initial bandwidth part and/or the second initial bandwidth part, where the specific case includes at least one of the following cases: a bandwidth part inactivity timer (bwp-inactivitytimer) expires, and the terminal is not configured with a default bandwidth part; and the bandwidth part inactivity timer expires (bwp-inactivitytimer), and the default bandwidth part configured by the terminal is an initial bandwidth part. In this observation, it is clear that when the terminal determines a target initial (DL) bandwidth part, the terminal may check whether a BWP inactivity timer associated with an active downlink (DL) BWP expires and if the BWP inactivity timer expires, the terminal may check whether a default DL BWP is configured.) and based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, switching the active DL BWP to the second initial DL BWP related to the RedCap UE. (Dongru, in Fig. 2 and in Paragraph [0114], teaches that if the reduced capability terminal receives a clear indication (for example, configured through the first configuration information) to the target initial bandwidth part applied by the network side device after the RRC connection is released, the reduced capability terminal determines the target initial bandwidth part according to the indication. If there is no clear indication from the network side device, the reduced capability terminal may determine a default initial bandwidth part in the specific case according to the network configuration or protocol specification. In Fig. 2 and in Paragraphs [0122]-[0123], [0127], and [0130]-[0131], Dongru teaches that optionally, after step 202, to be specific, after the terminal determines the target initial bandwidth part, the method further includes: under a specific condition, switching to the target initial bandwidth part, where the first specific condition includes the following case: a bandwidth part inactivity timer expires, and the terminal is not configured with a default bandwidth part. After the terminal determines the target initial bandwidth part in the first initial bandwidth part (RedCap UE case) and/or the second initial bandwidth part (non-RedCap UE case) (as mentioned in Paragraph [0109]) according to the first information, if the foregoing specific condition is met, the terminal switches to the target initial bandwidth part. For example, in some embodiments, after the terminal determines the target initial bandwidth part, if the current active bandwidth part of the terminal is not the target initial bandwidth part, the terminal switches to the target initial bandwidth part. Note that as mentioned in the above, the initial bandwidth part includes at least one initial UL BWP and one DL BWP. In this observation, it is clear that if the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is configured, switching the active DL BWP to the second initial DL BWP related to the RedCap UE.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Guorong and Dongru to include the technique of based on a determination that a BWP inactivity timer associated with the active DL BWP expires, determining whether a default DL BWP is configured; and based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is configured by the fourth configuration information, switching the active DL BWP to the second initial DL BWP related to the RedCap UE of Dongru in the system of combination of Guorong to provide an efficient initial bandwidth part for a reduced capability terminal to increase the system throughput and communication performance, when there are a large quantity of terminal devices accessing a small cell (Dongru, see Paragraphs [0002] to [0004]).
Regarding claim 13, Guorong teaches the features defined in the claim 11, -refer to the indicated claim for reference(s).
Guorong does not teach that based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is not configured, switching the active DL BWP to the first initial DL BWP.
However, Dongru teaches based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is not configured, switching the active DL BWP to the first initial DL BWP (Dongru, in Fig. 2 and in Paragraphs [0122]-[0123], [0127], and [0130]-[0131], teaches that optionally, after step 202, to be specific, after the terminal determines the target initial bandwidth part, the method further includes: under a specific condition, switching to the target initial bandwidth part, where the first specific condition includes the following case: a bandwidth part inactivity timer expires, and the terminal is not configured with a default bandwidth part. After the terminal determines the target initial bandwidth part in the first initial bandwidth part (RedCap UE case) and/or the second initial bandwidth part (non-RedCap UE case) (as mentioned in Paragraph [0109]) according to the first information, if the foregoing specific condition is met, the terminal switches to the target initial bandwidth part. For example, in some embodiments, after the terminal determines the target initial bandwidth part, if the current active bandwidth part of the terminal is not the target initial bandwidth part, the terminal switches to the target initial bandwidth part. Note that as mentioned in the above, the initial bandwidth part includes at least one initial UL BWP and one DL BWP. In this observation, it is clear that if the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is not configured, switching the active DL BWP to the firtst initial DL BWP for non-RedCap UE.
It would have been obvious for one of ordinary skill in the art, before the effective filing date of the claimed invention, to combine Guorong and Dongru to include the technique of based on a determination that the BWP inactivity timer expires, the default DL BWP is not configured, and the second initial DL BWP related to the RedCap UE is not configured, switching the active DL BWP to the first initial DL BWP of Dongru in the system of combination of Guorong to provide an efficient initial bandwidth part for a reduced capability terminal to increase the system throughput and communication performance, when there are a large quantity of terminal devices accessing a small cell (Dongru, see Paragraphs [0002] to [0004]).
Conclusion
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
Prosecution Insights