DETAILED ACTION
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 7/15/2026 has been entered. In response to amendment filed on 7/15/2026, claims 1- 29 were cancelled and claims 30 and 49 are amended and claim 50 is added as a new claim. Claims 30- 50 are pending for examinations.
Response to Arguments
Applicant’s arguments with respect to claim(s) filed in the remarks on 2/27/2026 have been considered but are moot because the new ground of rejection does not rely on any reference applied in the prior rejection of record for any teaching or matter specifically challenged in the argument. Applicant has changed all independent claims by adding new limitations hence examiner believes that the scope has been changed. Therefor examiner has considered new reference Takeda et al. (US Pub. No. 2021/0127356 A1).
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 30 and 49 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 30- 32, 40 of U.S. Patent No. 12464545 in view of Takeda et al. (US Pub. No. 2021/0127356 A1).
Although the claims at issue are not identical, they are not patentably distinct from each other because please see table below:
Current APP# 18028623
US Pat. No. 12464545
30. A method of enhancing a scheduling process for multicast broadcast services (MBS), comprising:
receiving, by a user equipment (UE), via a physical downlink shared channel (PDCSH), one or more configuration messages for the MBS services, the one or more configuration messages comprising:
discontinuous reception (DRX) configuration parameters associated with a first MBS service; and
semi-persistent scheduling (SPS) configuration parameters associated with a second MBS service;
receiving, by the UE, first multicast broadcast data associated with the first MBS service, based on scheduling information determined by monitoring a physical downlink control channel (PDCCH) using the DRX configuration parameters; and
receiving, by the UE, second multicast broadcast data, associated with the second MBS service, based on the SPS configuration parameters,
wherein thePDCCH channel is associated with a common sub-band for MBS, the common sub-band being configuredwithin a bandwidth part(BWP) configured for the UE.
30. A method of enhancing a scheduling process for multicast broadcast service (MBS) services, comprising: receiving, by a user equipment (UE), one or more configuration messages for the MBS services via a physical downlink shared channel (PDSCH), the one or more configuration messages comprising: discontinuous reception (DRX) configuration parameters associated with a first MBS service; and semi-persistent scheduling (SPS) configuration parameters associated with a second MBS service; receiving, by the UE, first multicast broadcast data associated with the first MBS service based on scheduling information determined by monitoring (i.e. by UE in downlink side a control channel i.e. PDCCH) a control channel using the DRX configuration parameters; and receiving, by the UE, second multicast broadcast data associated with the second MBS service based on the SPS configuration parameters, wherein the SPS configuration parameters comprise an offset parameter indicating an offset of a hybrid automatic repeat request (HARQ) process, and wherein receiving, by the UE, second multicast broadcast data comprises receiving the second multicast broadcast data based on the offset parameter.
31. The method of claim 30, wherein receiving second multicast broadcast data associated with the second MBS service based on the SPS configuration parameters comprises determining radio resources for the second MBS service in response to receiving the SPS configuration parameters and without receiving an activation signaling for the SPS configuration parameters.
32. The method of claim 30, wherein receiving second multicast broadcast data associated with the second MBS service based on the SPS configuration parameters comprises determining radio resources for the second MBS service in response to receiving the SPS configuration parameters and receiving an activation signaling for the SPS configuration parameters.
49. An apparatus for utilization in wireless communications comprising:
an antenna for use in transmission of electromagnetic signals;
a memory for maintaining computer-readable code; and
a processor for executing the computer-readable code that causes the apparatus to:
receive, via a physical downlink shared channel (PDCSH), one or more configuration messages for the MBS services, the one or more configuration messages comprising:
discontinuous reception (DRX) configuration parameters associated with a first MBS service; and
semi-persistent scheduling (SPS) configuration parameters associated with a second MBS service;
receive first multicast broadcast data associated with the first MBS service, based on scheduling information determined by monitoring a control channel using the DRX configuration parameters; and
receive second multicast broadcast data, associated with the second MBS service, based on the SPS configuration parameters,
wherein the PDCCH is associated with a common sub-band for MBS, the common sub-band being configured within a bandwidth part(BWP) configured for the UE.
40. An apparatus for utilization in wireless communications comprising: an antenna for use in transmission of electromagnetic signals; a memory for maintaining computer-readable code; and
a processor for executing the computer-readable code that causes the apparatus to:
receive one or more configuration message for multicast broadcast services (MBS) services via a physical downlink shared channel (PDSCH), the one or more configuration message comprising discontinuous reception (DRX) configuration parameters associated with a first MBS service and semi-persistent scheduling (SPS) configuration parameters associated with a second MBS service;
receive first multicast broadcast data associated with the first MBS service based on scheduling information determined by monitoring (i.e. by UE in downlink side a control channel i.e. PDCCH) a control channel using the DRX configuration parameters; and
receive second multicast broadcast data associated with the second MBS service based on the SPS configuration parameters,
wherein the SPS configuration parameters comprise an offset parameter indicating an offset of a hybrid automatic repeat request (HARQ) process, and
wherein receiving the second multicast broadcast data comprises receiving the second multicast broadcast data based on the offset parameter.
30. A method of enhancing a scheduling process for multicast broadcast service (MBS) services, comprising: receiving, by a user equipment (UE), one or more configuration messages for the MBS services via a physical downlink shared channel (PDSCH), the one or more configuration messages comprising: discontinuous reception (DRX) configuration parameters associated with a first MBS service; and semi-persistent scheduling (SPS) configuration parameters associated with a second MBS service; receiving, by the UE, first multicast broadcast data associated with the first MBS service based on scheduling information determined by monitoring (i.e. by UE in downlink side a control channel i.e. PDCCH) a control channel using the DRX configuration parameters; and receiving, by the UE, second multicast broadcast data associated with the second MBS service based on the SPS configuration parameters, wherein the SPS configuration parameters comprise an offset parameter indicating an offset of a hybrid automatic repeat request (HARQ) process, and wherein receiving, by the UE, second multicast broadcast data comprises receiving the second multicast broadcast data based on the offset parameter.
31. The method of claim 30, wherein receiving second multicast broadcast data associated with the second MBS service based on the SPS configuration parameters comprises determining radio resources for the second MBS service in response to receiving the SPS configuration parameters and without receiving an activation signaling for the SPS configuration parameters.
32. The method of claim 30, wherein receiving second multicast broadcast data associated with the second MBS service based on the SPS configuration parameters comprises determining radio resources for the second MBS service in response to receiving the SPS configuration parameters and receiving an activation signaling for the SPS configuration parameters.
Here U.S. Patent No. 12464545 is silent regarding amended limitations, “wherein the PDCCH is associated with a common sub-band for MBS, the common sub-band being configured within a bandwidth part(BWP) configured for the UE”; however Takeda in context with [0045] (i.e. …. the multicast BWP may be a UE-common BWP configured to be used by all UE (i.e. common sub-band) computing devices in communication with the base station….) teaches in [0046].. the UE-common BWP may have the same SCS and CP length of an active UE-specific BWP and the UE-common BWP may be fully contained within the UE-specific BWP (i.e. common sub-band). In such cases, the UE may monitor the physical downlink control channel (PDCCH) search space sets for unicast (C-RNTI) and for multicast (G-RNTI) for the same serving cell and the network (e.g., the base station) can schedule either unicast or multicast (or both) simultaneously at the same time. In some embodiments, search space (SS) sets for unicast and multicast may be configured in the UE-specific BWP and UE-common BWP configurations separately and respectively. In some embodiments, the UE may be configured to monitor the PDCCH for unicast and the PDCCH for multicast in the SS sets in both the UE-specific BWP and UE-common BWP configurations for the same serving cell at the same time. Monitoring both the PDCCH for unicast and the PDCCH for multicast in the SS sets may reduce a likelihood of PDCCH blocking; further see [0047]. Also refer to [0110- 0115] about UE-common BWP, multicast PDCCH/search space sets and multicast BWP placement within the UE-specific BWP; also discussed about multicast/UE-common/virtual BWP portion of the carrier bandwidth used for multicast scheduling and PDCCH monitoring (i.e. common sub-band for MBS).
It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Takeda with the teachings of U.S. Patent No. 12464545 to make system more effective. Having a mechanism wherein the PDCCH is associated with a common sub-band for MBS, the common sub-band being configured within a bandwidth part(BWP) configured for the UE; greater way resources can be managed/utilized in the communication system.
Claim Rejections - 35 USC § 103
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
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) 30- 32, 37, 43- 44, 47- 50 is/are rejected under 35 U.S.C. 103 as being unpatentable over Latheef et al. (US Pub. No. 2023/0276471 A1), hereafter Fasil in view of Takeda et al. (US Pub. No. 2021/0127356 A1).
Regarding claim 30, Fasil teaches a method of enhancing a scheduling process for multicast broadcast service (MBS) services (see Title managing MBS services), comprising:
receiving, by a user equipment (UE), via a physical downlink shared channel (PDCSH), one or more configuration messages for the MBS services, the one or more configuration messages comprising (see [0055].. the BS 102 dynamically allocates Physical Resource Blocks over at least one of, a BWP from the plurality of BWPs, and a CFR from the plurality of CFRs to provide the one or more MBS services to the UE 104 (i.e. user equipment) at each scheduling occasion using a Physical Downlink Control Channel (PDCCH). The BS 102 allocates the PRBs on the PDSCH; further see [0063]… Further, the BS 102 configures the UE 104 with a configuration of the SPS MBS services (referred hereinafter as SPS MBS services configuration) through at least one of an RRC reconfiguration message and the MCCH message. The SPS MBS services configuration may include at least one of, but is not limited to periodicity, a number of Hybrid automatic repeat request (HARM) processes, a PDSCH aggregation factor which is the number of repetitions of SPS MBS PDSCH, a BWP, a G-CS-RNTI, a modulation and coding scheme table, and so on. The SPS MBS configuration may be indicated with an index, for example, an MBS-SPS-ConfigIndex. The UE 104 determines the specific SPS MBS service from the corresponding G-CS-RNTI; further see [0068] the BS 102 may use the SPS scheduling of the one or more MBS services in conjunction with the DRX configurations of the one or more MBS services, which further reduces load on the PDCCH. In another example, the SPS MBS services (i.e., the SPS scheduled MBS services) may be activated and deactivated through the PDCCH. When the SPS MBS service is activated, the UE 104 stores a downlink assignment as a configured downlink assignment. While, when the SPS MBS service is deactivated, the UE 104 clears the configured downlink assignment and/or indicate an acknowledgement to the BS 102; also refer to [0051, 0076- 0080 and 0094- 0098]):
discontinuous reception (DRX) configuration parameters associated with a first MBS service (in context with just discussed above in [0062]; pls refer to [0063].. further provide the DRX configurations to the UE 104 over the one or more MCCHs. The DRX configurations depict a DRX cycle for the UE 104, which depicts an ON duration and an OFF duration of the UE 104 for receiving the one or more MBS services. The DRX configurations provide flexibility for the BS 102 to schedule the MBS services/sessions (i.e. first MBS service) during any Transmission Time Interval (TTI) or a slot within an ON duration of the corresponding DRX cycle; further see [0066, 0086, 0101-0104].); and
semi-persistent scheduling (SPS) configuration parameters associated with a second MBS service (already discussed above in [0062].. a configuration of the SPS MBS services (referred hereinafter as SPS MBS services configuration)..; further see [0067] …. the BS 102 may use the SPS for scheduling of the one or more MBS services. In an example, the BS 102 may provide the SPS for the scheduling of example MBS services like IoT applications, which may be periodic and light in nature for the data traffic. In an embodiment, the MBS specific SPS on the PDSCH is supported for the scheduling of the multicast services (i.e. second MBS service); further see [0059-0066, 0068]);
receiving, by the UE, first multicast broadcast data associated with the first MBS service, based on scheduling information determined by monitoring a physical downlink control channel (PDCCH) using the DRX configuration parameters (see [0068] … the BS 102 may use the SPS scheduling of the one or more MBS services in conjunction with the DRX configurations of the one or more MBS services, which further reduces load on the PDCCH (i.e. control channel here). In another example, the SPS MBS services (i.e., the SPS scheduled MBS services) may be activated and deactivated through the PDCCH. In another example, the SPS MBS services (i.e., the SPS scheduled MBS services) may be activated and deactivated through the PDCCH…; further see [0101].. In another example, the processing circuitry 306 receives the one or more MBS services from the BS 102 at each scheduling occasion using the PDCCH, on the BS 102 allocating the PRBs over at least one of, the BWP and the CFR; further see [0102- 0104]); and
receiving, by the UE, second multicast broadcast data, associated with the second MBS service, based on the SPS configuration parameters (see [0062]…The UE 104 identifies the group scheduling configured for each group using the identifier. In an example, a number of SPS MBS services (i.e., the MBS services scheduled with the SPS); further see [0067] the BS 102 may use the SPS for scheduling of the one or more MBS services. In an example, the BS 102 may provide the SPS for the scheduling of example MBS services like IoT applications, which may be periodic and light in nature for the data traffic. In an embodiment, the MBS specific SPS on the PDSCH is supported for the scheduling of the multicast services; further see [0060- 0061, 0063- 0068].).
Here Fasil is silent regarding amended limitations, “wherein the PDCCH is associated with a common sub-band for MBS, the common sub-band being configured within a bandwidth part(BWP) configured for the UE” (i.e. though teaches in [0054- 0058, 0084, 0101] about BEPs/CFRs (common frequency resources) and PDCCH based allocation for MBS but fails to describe “common sub-band”); however Takeda in context with [0045] (i.e. …. the multicast BWP may be a UE-common BWP configured to be used by all UE (i.e. common sub-band) computing devices in communication with the base station….) teaches in [0046].. the UE-common BWP may have the same SCS and CP length of an active UE-specific BWP and the UE-common BWP may be fully contained within the UE-specific BWP (i.e. common sub-band). In such cases, the UE may monitor the physical downlink control channel (PDCCH) search space sets for unicast (C-RNTI) and for multicast (G-RNTI) for the same serving cell and the network (e.g., the base station) can schedule either unicast or multicast (or both) simultaneously at the same time. In some embodiments, search space (SS) sets for unicast and multicast may be configured in the UE-specific BWP and UE-common BWP configurations separately and respectively. In some embodiments, the UE may be configured to monitor the PDCCH for unicast and the PDCCH for multicast in the SS sets in both the UE-specific BWP and UE-common BWP configurations for the same serving cell at the same time. Monitoring both the PDCCH for unicast and the PDCCH for multicast in the SS sets may reduce a likelihood of PDCCH blocking; further see [0047]. Also refer to [0110- 0115] about UE-common BWP, multicast PDCCH/search space sets and multicast BWP placement within the UE-specific BWP; also discussed about multicast/UE-common/virtual BWP portion of the carrier bandwidth used for multicast scheduling and PDCCH monitoring (i.e. common sub-band for MBS).
It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Takeda with the teachings of Fasil to make system more effective. Having a mechanism wherein the PDCCH is associated with a common sub-band for MBS, the common sub-band being configured within a bandwidth part(BWP) configured for the UE; greater way resources can be managed/utilized in the communication system.
Regarding claim 31, Fasil in view of Takeda teaches as per claim 30, wherein Fasil teaches the SPS configuration parameters comprise first configuration parameters of a first SPS configuration associated with the second MBS service; in context with [0062] pls refer to [0067].. may use the SPS for scheduling of the one or more MBS services. In an example, the BS 102 may provide the SPS for the scheduling of example MBS services like IoT applications , which may be periodic and light in nature for the data traffic. In an embodiment, the MBS specific SPS on the PDSCH is supported for the scheduling of the multicast services.
Regarding claim 32, Fasil in view of Takeda teaches as per claim 31, wherein Fasil teaches the SPS configuration parameters correspond to one or more SPS configurations comprising the first SPS configuration; see [0062]... . In an example, a number of SPS MBS services (i.e., the MBS services scheduled with the SPS) supported simultaneously is determined by the UE capability and the UE 104 indicates the number of supported SPS MBS services to the BS 102 through at least one of a UE capability information message, a UE assistance information message, and an MBS interest indication message. Further, the BS 102 configures the UE 104 with a configuration of the SPS MBS services (referred hereinafter as SPS MBS services configuration).
Regarding claim 37, Fasil in view of Takeda teaches as per claim 31, wherein Fasil teaches the SPS configuration parameters comprise at least one parameter indicating that the SPS configuration parameters are associated with the second MBS service; in context with [0062] pls refer to [0067].. may use the SPS for scheduling of the one or more MBS services. In an example, the BS 102 may provide the SPS for the scheduling of example MBS services like IoT applications, which may be periodic and light in nature for the data traffic. In an embodiment, the MBS specific SPS on the PDSCH is supported for the scheduling of the multicast services.
Regarding claim 43, Fasil in view of Takeda teaches as per claim 30, wherein Fasil teaches: the one or more configuration messages comprise a first parameter and a second parameter; and receiving at least one of the first multimedia broadcast data or the second multicast broadcast data is based on the first parameter and the second parameter; see [0062]…The UE 104 identifies the group scheduling configured for each group using the identifier. In an example, a number of SPS MBS services (i.e., the MBS services scheduled with the SPS); further see [0067] the BS 102 may use the SPS for scheduling of the one or more MBS services. In an example, the BS 102 may provide the SPS for the scheduling of example MBS services like IoT applications, which may be periodic and light in nature for the data traffic. In an embodiment, the MBS specific SPS on the PDSCH is supported for the scheduling of the multicast services; further see [0068]..
Regarding claim 44, Fasil in view of Takeda teaches as per claim 30, wherein Fasil teaches the multicast broadcast configuration parameter is received via a multicast control channel; in context with [0062]; pls refer to [0063].. further provide the DRX configurations to the UE 104 over the one or more MCCHs (i.e. control channel here). The DRX configurations depict a DRX cycle for the UE 104, which depicts an ON duration and an OFF duration of the UE 104 for receiving the one or more MBS services. ..
Regarding claim 47, Fasil in view of Takeda teaches as per claim 44, wherein Fasil teaches further comprising receiving one or more messages including scheduling information for receiving the multicast control channel; in context with [0062]; pls refer to [0063].. further provide the DRX configurations to the UE 104 over the one or more MCCHs (i.e. control channel here). The DRX configurations depict a DRX cycle for the UE 104, which depicts an ON duration and an OFF duration of the UE 104 for receiving the one or more MBS services. ..
Regarding claim 48, Fasil in view of Takeda teaches as per claim 47, wherein Fasil teaches the one or more messages comprise a broadcast message; see [0081].. broadcasts the different MBS control and configuration information corresponding to the plurality of MBS services to the UEs 104 over the mapped plurality of different MCCHs.
Regarding claim 49, Fasil teaches an apparatus for utilization in wireless communications comprising:
an antenna for use in transmission of electromagnetic signals;
a memory for maintaining computer-readable code; and
a processor for executing the computer-readable code that causes the apparatus to (see Title managing MBS services):
receive, via a physical downlink shared channel (PDCSH), one or more configuration messages for the MBS services, the one or more configuration messages comprising (see [0055].. the BS 102 dynamically allocates Physical Resource Blocks over at least one of, a BWP from the plurality of BWPs, and a CFR from the plurality of CFRs to provide the one or more MBS services to the UE 104 (i.e. user equipment) at each scheduling occasion using a Physical Downlink Control Channel (PDCCH). The BS 102 allocates the PRBs on the PDSCH; further see [0063]… Further, the BS 102 configures the UE 104 with a configuration of the SPS MBS services (referred hereinafter as SPS MBS services configuration) through at least one of an RRC reconfiguration message and the MCCH message. The SPS MBS services configuration may include at least one of, but is not limited to periodicity, a number of Hybrid automatic repeat request (HARM) processes, a PDSCH aggregation factor which is the number of repetitions of SPS MBS PDSCH, a BWP, a G-CS-RNTI, a modulation and coding scheme table, and so on. The SPS MBS configuration may be indicated with an index, for example, an MBS-SPS-ConfigIndex. The UE 104 determines the specific SPS MBS service from the corresponding G-CS-RNTI; further see [0068] the BS 102 may use the SPS scheduling of the one or more MBS services in conjunction with the DRX configurations of the one or more MBS services, which further reduces load on the PDCCH. In another example, the SPS MBS services (i.e., the SPS scheduled MBS services) may be activated and deactivated through the PDCCH. When the SPS MBS service is activated, the UE 104 stores a downlink assignment as a configured downlink assignment. While, when the SPS MBS service is deactivated, the UE 104 clears the configured downlink assignment and/or indicate an acknowledgement to the BS 102; also refer to [0051, 0076- 0080 and 0094- 0098]):
discontinuous reception (DRX) configuration parameters associated with a first MBS service (in context with just discussed above in [0062]; pls refer to [0063].. further provide the DRX configurations to the UE 104 over the one or more MCCHs. The DRX configurations depict a DRX cycle for the UE 104, which depicts an ON duration and an OFF duration of the UE 104 for receiving the one or more MBS services. The DRX configurations provide flexibility for the BS 102 to schedule the MBS services/sessions (i.e. first MBS service) during any Transmission Time Interval (TTI) or a slot within an ON duration of the corresponding DRX cycle; further see [0066, 0086, 0101-0104].); and
semi-persistent scheduling (SPS) configuration parameters associated with a second MBS service (already discussed above in [0062].. a configuration of the SPS MBS services (referred hereinafter as SPS MBS services configuration)..; further see [0067] …. the BS 102 may use the SPS for scheduling of the one or more MBS services. In an example, the BS 102 may provide the SPS for the scheduling of example MBS services like IoT applications, which may be periodic and light in nature for the data traffic. In an embodiment, the MBS specific SPS on the PDSCH is supported for the scheduling of the multicast services (i.e. second MBS service); further see [0059-0066, 0068]);
receive, first multicast broadcast data associated with the first MBS service, based on scheduling information determined by monitoring a physical downlink control channel (PDCCH) using the DRX configuration parameters (see [0068] … the BS 102 may use the SPS scheduling of the one or more MBS services in conjunction with the DRX configurations of the one or more MBS services, which further reduces load on the PDCCH (i.e. control channel here). In another example, the SPS MBS services (i.e., the SPS scheduled MBS services) may be activated and deactivated through the PDCCH. In another example, the SPS MBS services (i.e., the SPS scheduled MBS services) may be activated and deactivated through the PDCCH…; further see [0101].. In another example, the processing circuitry 306 receives the one or more MBS services from the BS 102 at each scheduling occasion using the PDCCH, on the BS 102 allocating the PRBs over at least one of, the BWP and the CFR; further see [0102- 0104]); and
receive, second multicast broadcast data, associated with the second MBS service, based on the SPS configuration parameters (see [0062]…The UE 104 identifies the group scheduling configured for each group using the identifier. In an example, a number of SPS MBS services (i.e., the MBS services scheduled with the SPS); further see [0067] the BS 102 may use the SPS for scheduling of the one or more MBS services. In an example, the BS 102 may provide the SPS for the scheduling of example MBS services like IoT applications, which may be periodic and light in nature for the data traffic. In an embodiment, the MBS specific SPS on the PDSCH is supported for the scheduling of the multicast services; further see [0060- 0061, 0063- 0068].).
Here Fasil is silent regarding amended limitations, “wherein the PDCCH is associated with a common sub-band for MBS, the common sub-band being configured within a bandwidth part(BWP) configured for the UE” (i.e. though teaches in [0054- 0058, 0084, 0101] about BEPs/CFRs (common frequency resources) and PDCCH based allocation for MBS but fails to describe “common sub-band”); however Takeda in context with [0045] (i.e. …. the multicast BWP may be a UE-common BWP configured to be used by all UE (i.e. common sub-band) computing devices in communication with the base station….) teaches in [0046].. the UE-common BWP may have the same SCS and CP length of an active UE-specific BWP and the UE-common BWP may be fully contained within the UE-specific BWP (i.e. common sub-band). In such cases, the UE may monitor the physical downlink control channel (PDCCH) search space sets for unicast (C-RNTI) and for multicast (G-RNTI) for the same serving cell and the network (e.g., the base station) can schedule either unicast or multicast (or both) simultaneously at the same time. In some embodiments, search space (SS) sets for unicast and multicast may be configured in the UE-specific BWP and UE-common BWP configurations separately and respectively. In some embodiments, the UE may be configured to monitor the PDCCH for unicast and the PDCCH for multicast in the SS sets in both the UE-specific BWP and UE-common BWP configurations for the same serving cell at the same time. Monitoring both the PDCCH for unicast and the PDCCH for multicast in the SS sets may reduce a likelihood of PDCCH blocking; further see [0047]. Also refer to [0110- 0115] about UE-common BWP, multicast PDCCH/search space sets and multicast BWP placement within the UE-specific BWP; also discussed about multicast/UE-common/virtual BWP portion of the carrier bandwidth used for multicast scheduling and PDCCH monitoring (i.e. common sub-band for MBS).
It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Takeda with the teachings of Fasil to make system more effective. Having a mechanism wherein the PDCCH is associated with a common sub-band for MBS, the common sub-band being configured within a bandwidth part(BWP) configured for the UE; greater way resources can be managed/utilized in the communication system.
Regarding claim 50, Fasil in view of Takeda teaches as per claim 30, wherein the common sub-band is configured with a control resource set (CORESET) and a search space for receiving the scheduling information; Takeda in context with [0045] (i.e. …. the multicast BWP may be a UE-common BWP configured to be used by all UE (i.e. common sub-band) computing devices in communication with the base station….) teaches in [0046].. the UE-common BWP may have the same SCS and CP length of an active UE-specific BWP and the UE-common BWP may be fully contained within the UE-specific BWP (i.e. common sub-band). In such cases, the UE may monitor the physical downlink control channel (PDCCH) search space sets for unicast (C-RNTI) and for multicast (G-RNTI) for the same serving cell and the network (e.g., the base station) can schedule either unicast or multicast (or both) simultaneously at the same time. In some embodiments, search space (SS) sets for unicast and multicast may be configured in the UE-specific BWP and UE-common BWP configurations separately and respectively. In some embodiments, the UE may be configured to monitor the PDCCH for unicast and the PDCCH for multicast in the SS sets in both the UE-specific BWP and UE-common BWP configurations for the same serving cell at the same time. Monitoring both the PDCCH for unicast and the PDCCH for multicast in the SS sets may reduce a likelihood of PDCCH blocking; further see [0047]. Also refer to [0110- 0115] about UE-common BWP, multicast PDCCH/search space sets and multicast BWP placement within the UE-specific BWP; also discussed about multicast/UE-common/virtual BWP portion of the carrier bandwidth used for multicast scheduling and PDCCH monitoring (i.e. common sub-band for MBS);
now refer to [0093]… each respective virtual BWP may be identified by a starting resource block and a length of resource blocks within the UE-specific BWP for that respective UE computing device. In some embodiments, each respective virtual BWP may be identified by one or more CORESET bandwidth configurations based on a configuration of that respective UE computing device. In some embodiments, the respective UE computing device may have a single CORESET for multicast and a lowest resource block index and a highest resource block index of the CORESET corresponds to the virtual BWP….; further see [0088].. . In some embodiments, the multicast BWP sending module 410 may be configured to, for each of the one or more UE computing devices in communication with the base station, an indication of a search space set for multicast to the respective UE computing device in response to determining that the UE-common BWP has a SCS and CP length as the UE-specific BWP and the UE-common BWP is fully contained within the UE specific BWP…; further see [0046].. UE may monitor the physical downlink control channel (PDCCH) search space sets for unicast (C-RNTI) and for multicast (G-RNTI) for the same serving cell and the network (e.g., the base station) can schedule either unicast or multicast (or both) simultaneously at the same time. In some embodiments, search space (SS) sets for unicast and multicast may be configured in the UE-specific BWP and UE-common BWP configurations separately and respectively. In some embodiments, the UE may be configured to monitor the PDCCH for unicast and the PDCCH for multicast in the SS sets in both the UE-specific BWP and UE-common BWP configurations for the same serving cell at the same time. Monitoring both the PDCCH for unicast and the PDCCH for multicast in the SS sets may reduce a likelihood of PDCCH blocking; also see [0045].
Claim(s) 33 is/are rejected under 35 U.S.C. 103 as being unpatentable over Latheef et al. (US Pub. No. 2023/0276471 A1), hereafter Fasil in view of Takeda et al. (US Pub. No. 2021/0127356 A1) in view of Shi et al. WO 2016/127648 A1; see IDS filed on 8/27/2025 page 2.
Regarding claim 33, Fasil in view of Takeda teaches as per claim 32, but Fasil fails to teach about wherein the SPS configuration parameters correspond to a common cell; however Shi states on page 4 about …Optionally, the specific semi-persistent scheduling opportunity of the UE and the semi-persistent scheduling opportunity common to the cell include a semi-persistent scheduling opportunity period or a semi-persistent scheduling subframe bitmap parameter. It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Shi with the teachings of Fasil in view of Takeda to make system more effective. Having a mechanism wherein the SPS configuration parameters correspond to a common cell; greater way resources can be managed/utilized in the communication system.
Claim(s) 34 is/are rejected under 35 U.S.C. 103 as being unpatentable over Latheef et al. (US Pub. No. 2023/0276471 A1), hereafter Fasil in view of Takeda et al. (US Pub. No. 2021/0127356 A1) in view of Shi et al. WO 2016/127648 A1; see IDS filed on 8/27/2025 page 2 and in further view of Guo et al. (US Pat. No. 12114264 B2).
Regarding claim 34, Fasil in view of Takeda and Shi teaches as per claim 33, but Fasil fails to teach about wherein the SPS configuration parameters correspond to a same BWP of the same cell; however Guo states in col. 79 lines 1- 13 about … In some implementations, a specific BWP has one or more of the following characteristic: 1) A BWP with the minimum BWP index, or maximum BWP index, or no BWP index 2) A BWP with the narrowest bandwidth, or the smallest PRB 3) A initial or default BWP 4) A specific BWP is same with BWP for SPS DL scheduling, or the BWP for SPS DL scheduling after DL SPS (semi-persistent scheduling) scheduling is actived or before DL SPS scheduling... It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Guo with the teachings of Fasil in view of Takeda and Shi to make system more effective. Having a mechanism wherein the SPS configuration parameters correspond to a same BWP of the same cell; greater way resources can be managed/utilized in the communication system.
Claim(s) 35 is/are rejected under 35 U.S.C. 103 as being unpatentable over Latheef et al. (US Pub. No. 2023/0276471 A1), hereafter Fasil in view of Takeda et al. (US Pub. No. 2021/0127356 A1) and further in view of Elshafie et al. (US Pub. No. 2022/0095363 A1), hereafter Ahmed.
Regarding claim 35, Fasil in view of Takeda teaches as per claim 32, but Fasil fails to teach about wherein the SPS configuration parameters comprise at least one parameter indicating sub-slot-based transmission for the second multicast broadcast data; however Ahmed states about … the UE can be configured with a downlink grant indicating the resources for SPS downlink transmissions. The downlink grant may also indicate a configured K1 value that indicates a number of slots or sub-slots, after the SPS downlink transmission, at which to transmit feedback corresponding to the SPS downlink transmission. Where the symbol or slot for feedback is indicated as downlink (e.g., in the slot format or in a grant for additional SPS downlink transmissions)…. It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Ahmed with the teachings of Fasil in view of Takeda to make system more effective. Having a mechanism wherein the SPS configuration parameters comprise at least one parameter indicating sub-slot-based transmission for the second multicast broadcast data; greater way resources can be managed/utilized in the communication system.
Claim(s) 36 is/are rejected under 35 U.S.C. 103 as being unpatentable over Latheef et al. (US Pub. No. 2023/0276471 A1), hereafter Fasil in view of Takeda et al. (US Pub. No. 2021/0127356 A1) and further in view of Kung et al. TW 202046752 A; see attached translated copy.
Regarding claim 36, Fasil in view of Takeda teaches as per as per claim 32, but Fasil fails to teach about wherein the SPS configuration parameters comprise at least one parameter indicating repetition of a multicast broadcast transport block for a plurality of times in a SPS occasion; however Kung states on page 15 about … 23.14.1.2 Support V2X communication via Uu For V2X communication in the uplink, the eNB can configure a maximum of 8 SPS configurations with different parameters, and all SPS configurations can be active at the same time. The eNB signals the activation/deactivation of each SPS configuration through the PDCCH. Use the existing logical channel priority order for Uu. For V2X communication, UE assistance information can be provided to the eNB. The eNB configures the reporting of UE auxiliary information. The UE assistance information includes parameters related to SPS configuration (for example, a set of preferred SPS intervals, timing offset of subframe 0 relative to SFN 0, LCID, and maximum TB size based on the observed service mode). The UE implementation scheme determines the triggering of UE auxiliary information transmission. For example, when the estimated periodicity and/or timing offset of packet arrival changes, the UE is allowed to report UE assistance information. For V2X communication via Uu, SR masks based on traditional mechanisms can be used. For unicast transmission of V2X messages, V2X messages can be transmitted through non-GBR bearers and GBR bearers. In order to meet the QoS requirements of V2X message delivery for V2X services, the non-GBR QCI value and GBR QCI value of the V2X message are used, as specified in TS 23.285 [72]. In order to broadcast V2X messages, SC-PTM or MBSFN transmission can be used. In order to reduce the SC-PTM/MBSFN delay, the shorter (SC-) MCCH repetition period of SC-PTM/MBSFN, the modification period of SC-PTM/MBSFN and the MCH scheduling period of MBSFN are supported. It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Kung with the teachings of Fasil in view of Takeda to make system more standardized. Having a mechanism wherein the SPS configuration parameters comprise at least one parameter indicating repetition of a multicast broadcast transport block for a plurality of times in a SPS occasion; greater way more standardized approach can be carried out in the communication system.
Claim(s) 38- 39 are rejected under 35 U.S.C. 103 as being unpatentable over Latheef et al. (US Pub. No. 2023/0276471 A1), hereafter Fasil in view of Takeda et al. (US Pub. No. 2021/0127356 A1) and further in view of Park et al. (US Pub. No. 2015/0282126 A1).
Regarding claim 38, Fasil in view of Takeda teaches as per claim 30, but Fasil fails to teach about wherein receiving the second r multicast broadcast data is based on receiving downlink control information indicating activation of the first SPS configuration; however Park in context with [0149] states in [0120- 0122] about … performs SPS transmission and reception with the subframe periodicity and offset indicated by the SPS information using resource assignment information indicated by the PDCCH upon receiving a PDCCH indicating activation (or reactivation) (more specifically, upon detecting a PDCCH masked with an SPS C-RNTI) and stops SPS transmission and reception upon receiving a PDCCH indicating SPS release…. SPS transmission and reception is resumed with the subframe periodicity and offset indicated by the SPS information using resource assignment information indicated by the PDCCH, upon receiving a PDCCH indicating activation (or reactivation).. It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Park with the teachings of Fasil in view of Takeda to make system more standardized. Having a mechanism wherein receiving the second multicast broadcast data is based on receiving downlink control information indicating activation of the first SPS configuration; greater way more standardized approach can be carried out in the communication system.
Regarding claim 39, Fasil in view of Takeda and Park teaches as per claim 38, further comprising determining radio resources of the second multicast broadcast data based on the downlink control information and the first configuration parameters; Park in context with [0149] states in [0120- 0122] about … performs SPS transmission and reception with the subframe periodicity and offset indicated by the SPS information using resource assignment information indicated by the PDCCH upon receiving a PDCCH indicating activation (or reactivation) (more specifically, upon detecting a PDCCH masked with an SPS C-RNTI) and stops SPS transmission and reception upon receiving a PDCCH indicating SPS release…. SPS transmission and reception is resumed with the subframe periodicity and offset indicated by the SPS information using resource assignment information indicated by the PDCCH, upon receiving a PDCCH indicating activation (or reactivation)..
Claim(s) 40 is rejected under 35 U.S.C. 103 as being unpatentable over Latheef et al. (US Pub. No. 2023/0276471 A1), hereafter Fasil in view of Takeda et al. (US Pub. No. 2021/0127356 A1) and furhter in view of Samsung , “On Stage-2 aspects and overview of NR MBS”, R2-2007672; see IDS filed on 6/26/2023 page 1.
Regarding claim 40, Fasil in view of Takeda teaches as per claim 31, but Fasil fails to state about wherein receiving the second multicast broadcast data includes receiving the first configuration parameters without receiving an activation downlink control information for the SPS configuration; however Samsung teaches in page 3 2.2…The primary objective of this NR MBS WI is to specify a group scheduling mechanism to receive broadcast/ multicast services. LTE supports two group scheduling mechanisms – PMCH based eMBMS scheduling, and DRX based SC-PTM scheduling. The former is a semi static type of scheduling while (i.e. second service not associated with DRX config parameters and no need to monitor control channel here) the latter is more of a dynamic nature (i.e. second service here associated with DRX and also needs to monitor control channel) and hence, more resource efficient. SC-PTM is designed around a group scheduling mechanism where each supported multicast service is allocated a scheduling configuration and a unique identifier to receive the data…. It is possible that network way be able to provide a semi-static periodic scheduling for these packets. For such services, support of semi persistent scheduling of MBS traffic seems sensible. SPS for MBS (i.e. not monitoring the control channel since resources are allocated once and reuses those same resources at fixed) may serve as an alternative to DRX based scheduling. MBS SPS can also be used in conjunction with DRX to further reduce the load on PDCCH. It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Samsung with the teachings of Fasil in view of Takeda to make system more effective. Having a mechanism wherein receiving the second multicast broadcast data includes receiving the first configuration parameters without receiving an activation downlink control information for the SPS configuration; greater way resources can be managed/utilized in the communication system.
Claim(s) 41- 42 are rejected under 35 U.S.C. 103 as being unpatentable over Latheef et al. (US Pub. No. 2023/0276471 A1), hereafter Fasil in view of Takeda et al. (US Pub. No. 2021/0127356 A1) and further in view of Miao (US Pub. No. 2022/0191934 A1).
Regarding claim 41, Fasil in view of Takeda teaches as per claim 31, but Fasil fails to teach about wherein the first configuration parameters comprise an offset parameter and a periodicity parameter, and wherein receiving, by the UE, second multicast broadcast data includes receiving the second multicast broadcast data based on the offset parameter and the periodicity parameter; however Miao teaches in [0006] about the first RACH configuration provides a base RACH configuration, and the second RACH configuration includes one or more RACH extensions defined relative to the base RACH configuration. The one or more RACH extensions include one or more of: a scaling factor for a periodicity of the base RACH configuration, a frame offset with respect to a frame index of the base RACH configuration, a subframe offset with respect to a subframe index of the base RACH configuration, or a slot offset with respect to a slot index of the base RACH configuration; further see [0046- 0051]. It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Miao with the teachings of Fasil in view of Takeda to make system more standardized. Having a mechanism wherein the first configuration parameters comprise an offset parameter and a periodicity parameter, and wherein receiving, by the UE, second multicast broadcast data includes receiving the second multicast broadcast data based on the offset parameter and the periodicity parameter; greater way more standardized approach can be carried out in the communication system.
Regarding claim 42 Fasil in view of Takeda and Miao teaches as per claim 41, wherein the offset parameter is an offset to a system frame number with a first value; Miao see [0046- 0051].
Claim(s) 45- 46 is/are rejected under 35 U.S.C. 103 as being unpatentable over Latheef et al. (US Pub. No. 2023/0276471 A1), hereafter Fasil in view of Takeda et al. (US Pub. No. 2021/0127356 A1) and further in view of Wu (US Pat. No. 12477313 B2).
Regarding claim 45, Fasil in view of Takeda teaches as per claim 44, but Fasil silent about wherein the multicast control channel is configured on a first BWP; and the first MBS service or the second MBS service is configured for reception in a second BWP; however Wu teaches in col. 7 lines 50- 60 about an MTCH of a service that the terminal is interested in is sent in BWP-2, and the terminal receives the MTCH of the service that the terminal is interested in BWP-2 after receiving, in BWP-1, an MCCH message of the service that the terminal is interested in. An update indication “N” of the MCCH message is sent in BWP-2. After receiving, in BWP-2, the update indication of the MCCH message, the terminal receives, in BWP-1, updated MCCH information, and then receives, in BWP-2, the MTCH of the service that the terminal is interested in. It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Wu with the teachings of Fasil in view of Takeda to make system more standardized. Having a mechanism wherein the multicast control channel is configured on a first BWP; and the first MBS service or the second MBS service is configured for reception in a second BWP; greater way more standardized approach can be carried out in the communication system.
Regarding claim 46, Fasil in view of Takeda teaches as per claim 44, but Fasil is silent about the multicast control channel is configured on a BWP; and the MBS service and the second MBS service are configured for reception in the BWP; however Wu teaches in col. 7 lines 50- 60 about an MTCH of a service that the terminal is interested in is sent in BWP-2, and the terminal receives the MTCH of the service that the terminal is interested in BWP-2 after receiving, in BWP-1, an MCCH message of the service that the terminal is interested in. An update indication “N” of the MCCH message is sent in BWP-2. After receiving, in BWP-2, the update indication of the MCCH message, the terminal receives, in BWP-1, updated MCCH information, and then receives, in BWP-2, the MTCH of the service that the terminal is interested in. It would have been obvious to one with ordinary skill, in the art before the effective filing date of the claimed invention was made to consider the teachings of Wu with the teachings of Fasil in view of Takeda to make system more standardized. Having a mechanism about the multicast control channel is configured on a BWP; and the MBS service and the second MBS service are configured for reception in the BWP; greater way more standardized approach can be carried out in the communication system.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Please see PTO-892 form for considered prior arts for record.
Reference Chen teaches in [0099] about a common frequency resource(s) (or an associated MBS BWP) for a group-common PDCCH/Physical Downlink Shared Channel (PDSCH) may be configured or defined. The group-common PDCCH/PDSCH may be used for MBS data reception. If no common frequency resource is configured or defined, a UE may consider the initial BWP as the default common frequency resource for a group-common PDCCH/PDSCH.
Reference Liu et al. (US Pub. No. 2021/0250918 A1) teaches in [0078] about a common frequency resource (e.g., BWP) for MB (e.g., for group-common PDCCH/PDSCH), as indicated in the frequency domain resource assignment field, can be shared with (e.g., defined within) the frequency resource of a dedicated unicast frequency domain resource assignment (e.g., BWP), which can allow for supporting simultaneous reception of unicast and MB communications in the same slot.
Reference Lin et al. (US Pub. No. 2023/0093727 A1) teaches about .. if the network configures multiple CORESETs per BWP per cell to a UE (e.g., a UE interested in a certain MBS or an MB S-capable UE), one or more CORESET(s) may be dedicatedly used for the MBS. The multiple configured CORESETs may include UE-specific CORESET(s), common CORESET(s), and MBS-specific CORESET(s). In one implementation, the UE may receive an RRC message that indicates a CORESET dedicated for the MBS from a BS. The UE may monitor a PDCCH in the CORESET dedicated for the MBS for MB S-related control information. In one implementation, the RRC message may further indicate a BWP dedicated for the MBS (also referred to as the MBS BWP in the present disclosure). The CORESET dedicated for the MBS may be in the BWP dedicated for the MBS.; further see [0068, 0071].. different search spaces may be associated with different MBSs, sessions, or TMGIs. For example, different search spaces associated with the same CORESET may be used to indicate different MBSs (or different sessions, or different TMGIs). If the MBS-interested UE wants to acquire the control information corresponding to the MBS in which it is interested, it may monitor the shared CORESET in the search space assigned to the MBS (or session, or TMGI). In one implementation, the CORESET dedicated for the MBS may be associated with multiple search spaces, and each search space has a search space ID. Each search space ID may be associated with at least one MBS ID; further see [0218].. for MBS performed by a UE according to an example implementation of the present disclosure. .. the UE receives, from a BS, an RRC message that indicates a CORESET dedicated for the MBS. … the UE monitors a PDCCH in the CORESET for MBS-related control information. The CORESET dedicated for the MBS is beneficial for DCI decoding reliability since only MBS-related DCI can be transmitted in the CORESET dedicated for the MBS. In one implementation, the CORESET may be associated with multiple search spaces, and each of the search spaces has a search space ID. Each search space ID may be associated with at least one MBS ID. Each MBS ID may correspond to a type of MBS, such as public safety, mission-critical services, V2X applications, IPTV, and IoT applications. In one implementation, the UE monitors the PDCCH in a common search space (CSS) associated with the CORESET. In one implementation, the RRC message received in action 202 may further indicate that the CSS is dedicated for the MBS.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to PARTH PATEL whose telephone number is (571)270-1970. The examiner can normally be reached 7 a.m. -7 p.m. PST.
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, Jae Y. Lee can be reached at 5712703936. 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.
PARTH PATEL
Primary Examiner
Art Unit 2479
/PARTH PATEL/Primary Examiner, Art Unit 2479
Prosecution Insights