Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Claims 1,3, and 4 are pending.
Claim 2 is cancelled.
Response to Arguments
Applicant respectfully contends that the above mentioned "MBS configuration information" is configuration information for idle/inactive UEs to continuously receive MBS services, but this information does not configure whether the MBS configuration information received in a connected state is continuously available.
However, the examiner respectfully disagrees 0188 In the related art, the UE in the RRC connected state releases all the radio resources configured/established through the RRC dedicated message in the RRC connected state when switching to the RRC idle state. Also in paragraph 0190 Hong discloses To efficiently/continuously perform MBS data reception, the UE receiving MBS data may receive MBS data by storing/maintaining/using the MBS configuration information configured through the RRC dedicated message when switching to the RRC idle state. Therefore, the cited reference discloses MBS configuration continuously used RRC connected state.
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claims 1,3, and 4 are rejected under 35 U.S.C. 103 as being unpatentable over as Hong et al, US 20230380002 A1, in view of Stare et al, US 20230370893 A1.
Regarding claim 1, Hong discloses A communication control method performed by a user equipment supporting multicast broadcast services (MBS) ([0006] a method for processing multicast and broadcast services (MBS) data by a UE.), the communication control method comprising:
receiving, when the user equipment is in Radio Resource Control (RRC) connected state, by the user equipment from a base station([0181-0182] The multicast-based MBS may be basically received by the UE in the RRC connected state. The base station may indicate, to the UE in the RRC connected state, the MBS configuration through an RRC dedicated message, and the UE may receive MBS data based thereupon.),
an RRC Reconfiguration message comprising MBS configuration available for MBS reception in the RRC connected state([0165] The base station may indicate a modified/changed MBS configuration through a dedicated RRC reconfiguration message for one or more UEs in the RRC connected state receiving multicast-based MBS data.);
and receiving an RRC Release message from the base station, the RRC Release message used for transitioning the user equipment from the RRC connected state to an RRC inactive state ([0121] The information may be received by the UE through the RRC connection release message. Upon receiving the RRC connection release message, the UE may switch its state from the RRC connected state to the RRC inactive state or RRC idle state.),
wherein the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state ([0290] [0297] According to another embodiment, the receiver 1430 may receive an RRC connection release message including information for instructing whether to activate the MBS session from the base station before switching to the RRC inactive state. The information may be received by the UE through the RRC connection release message. Upon receiving the RRC connection release message, the controller 1410 may switch its state from the RRC connected state to the RRC inactive state or RRC idle state. Besides, the controller 1410 controls the overall operation of the UE 1400 necessary for MBS configuration and MBS data reception necessary for performing the above-described embodiments.),
and the communication method further comprising: determining to continuously use the MBS configuration received in the RRC connected state, in response to the information included in the RRC Release message indicating that the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state([0188] [0190] In the related art, the UE in the RRC connected state releases all the radio resources configured/established through the RRC dedicated message in the RRC connected state when switching to the RRC idle state. However, it may be preferable that the UE in the RRC idle/inactive state receives the MBS by using the configuration/setting information that has been applied by receiving the RRC reconfiguration message in the RRC connected state. To efficiently/continuously perform MBS data reception, the UE receiving MBS data may receive MBS data by storing/maintaining/using the MBS configuration information configured through the RRC dedicated message when switching to the RRC idle state.).
Hong does not disclose wherein the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state.
However, Stare does disclose wherein the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state([0010][0102-0103] The device further maintains a configuration for receiving the multicast transmission, and continues to receive the multicast transmission in the RRC idle mode or the RRC inactive mode. One possible method that could be employed by the network is to release some UEs from RRC Connected to RRC Inactive or RRC Idle (RRC Inactive/Idle). These UEs could then keep relevant parts of their RRC Connected configuration and continue to receive the MBS service in RRC Inactive/Idle by receiving the same (i.e. without duplication) G-RNTI-based PDCCH and PDSCH signals that are received by RRC Connected UEs.. ).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the teachings of Hong with wherein the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state as taught by Stare. The motivation for doing so would be to increase the total number of UEs that can receive a multimedia broadcast service (MBS) in a cell with required QoS. (Stare, [0005])
Regarding claim 3, Hong discloses A user equipment supporting multicast broadcast services (MBS) ([0006] a method for processing multicast and broadcast services (MBS) data by a UE.), the user equipment comprising:
a receiver configured to receive, when the user equipment is in Radio Resource Control (RRC) connected state, from a base station ([0181-0182] The multicast-based MBS may be basically received by the UE in the RRC connected state. The base station may indicate, to the UE in the RRC connected state, the MBS configuration through an RRC dedicated message, and the UE may receive MBS data based thereupon. ),
an RRC Reconfiguration message comprising MBS configuration available for MBS reception in the RRC connected state ([0165] The base station may indicate a modified/changed MBS configuration through a dedicated RRC reconfiguration message for one or more UEs in the RRC connected state receiving multicast-based MBS data.),
and a controller, wherein the receiver is configured to receive an RRC Release message from the base station, the RRC Release message used for transitioning the user equipment from the RRC connected state to an RRC inactive state ([0121] The information may be received by the UE through the RRC connection release message. Upon receiving the RRC connection release message, the UE may switch its state from the RRC connected state to the RRC inactive state or RRC idle state.),
and the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state ([0290] [0297] According to another embodiment, the receiver 1430 may receive an RRC connection release message including information for instructing whether to activate the MBS session from the base station before switching to the RRC inactive state. The information may be received by the UE through the RRC connection release message. Upon receiving the RRC connection release message, the controller 1410 may switch its state from the RRC connected state to the RRC inactive state or RRC idle state. Besides, the controller 1410 controls the overall operation of the UE 1400 necessary for MBS configuration and MBS data reception necessary for performing the above-described embodiments.),
the controller is configured to determine to continuously use the MBS configuration received in the RRC connected state, in response to the information included in the RRC Release message indicating that the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state([0190] However, it may be preferable that the UE in the RRC idle/inactive state receives the MBS by using the configuration/setting information that has been applied by receiving the RRC reconfiguration message in the RRC connected state. To efficiently/continuously perform MBS data reception, the UE receiving MBS data may receive MBS data by storing/maintaining/using the MBS configuration information configured through the RRC dedicated message when switching to the RRC idle state.).
Hong does not disclose and the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state
However, Stare does disclose and the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state([0010][0102-0103] The device further maintains a configuration for receiving the multicast transmission, and continues to receive the multicast transmission in the RRC idle mode or the RRC inactive mode. One possible method that could be employed by the network is to release some UEs from RRC Connected to RRC Inactive or RRC Idle (RRC Inactive/Idle). These UEs could then keep relevant parts of their RRC Connected configuration and continue to receive the MBS service in RRC Inactive/Idle by receiving the same (i.e. without duplication) G-RNTI-based PDCCH and PDSCH signals that are received by RRC Connected UEs.. ).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the teachings of Hong with wherein the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state as taught by Stare. The motivation for doing so would be to increase the total number of UEs that can receive a multimedia broadcast service (MBS) in a cell with required QoS. (Stare, [0005])
Regarding claim 4, Hong discloses an apparatus configured to control a user equipment supporting multicast broadcast services (MBS) ([0006] a method for processing multicast and broadcast services (MBS) data by a UE.), the apparatus comprising:
a processor and a memory coupled to the processor, the processor configured to([0315] The software code may be stored in a memory unit and driven by a processor.):
receive, when the user equipment is in Radio Resource Control (RRC) connected state, from a base station([0181-0182] The multicast-based MBS may be basically received by the UE in the RRC connected state. The base station may indicate, to the UE in the RRC connected state, the MBS configuration through an RRC dedicated message, and the UE may receive MBS data based thereupon. ),
an RRC Reconfiguration message comprising MBS configuration available for MBS reception in the RRC connected state([0165] The base station may indicate a modified/changed MBS configuration through a dedicated RRC reconfiguration message for one or more UEs in the RRC connected state receiving multicast-based MBS data.),
and receive an RRC Release message from the base station, the RRC Release message used for transitioning the user equipment from the RRC connected state to an RRC inactive state([0121] The information may be received by the UE through the RRC connection release message. Upon receiving the RRC connection release message, the UE may switch its state from the RRC connected state to the RRC inactive state or RRC idle state.),
wherein the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state([0290] [0297] According to another embodiment, the receiver 1430 may receive an RRC connection release message including information for instructing whether to activate the MBS session from the base station before switching to the RRC inactive state. The information may be received by the UE through the RRC connection release message. Upon receiving the RRC connection release message, the controller 1410 may switch its state from the RRC connected state to the RRC inactive state or RRC idle state. Besides, the controller 1410 controls the overall operation of the UE 1400 necessary for MBS configuration and MBS data reception necessary for performing the above-described embodiments.),
and the processor is configured to determine to continuously use the MBS configuration received in the RRC connected state, in response to the information included in the RRC Release message indicating that the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state([0190] However, it may be preferable that the UE in the RRC idle/inactive state receives the MBS by using the configuration/setting information that has been applied by receiving the RRC reconfiguration message in the RRC connected state. To efficiently/continuously perform MBS data reception, the UE receiving MBS data may receive MBS data by storing/maintaining/using the MBS configuration information configured through the RRC dedicated message when switching to the RRC idle state.).
Hong does not disclose wherein the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state.
However, Stare does disclose wherein the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state ([0010][0102-0103] The device further maintains a configuration for receiving the multicast transmission, and continues to receive the multicast transmission in the RRC idle mode or the RRC inactive mode. One possible method that could be employed by the network is to release some UEs from RRC Connected to RRC Inactive or RRC Idle (RRC Inactive/Idle). These UEs could then keep relevant parts of their RRC Connected configuration and continue to receive the MBS service in RRC Inactive/Idle by receiving the same (i.e. without duplication) G-RNTI-based PDCCH and PDSCH signals that are received by RRC Connected UEs.).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to combine the teachings of Hong with wherein the RRC Release message includes information for determining whether the MBS configuration received in the RRC connected state can be continuously used in the RRC inactive state as taught by Stare. The motivation for doing so would be to increase the total number of UEs that can receive a multimedia broadcast service (MBS) in a cell with required QoS. (Stare, [0005])
Conclusion
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to RYA TEON NELSON whose telephone number is (703)756-1942. The examiner can normally be reached 8:00-5:30.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Nishant Divecha can be reached at 571-270-3125. 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.
/RYA TEON NELSON/ Examiner, Art Unit 2419
/Nishant Divecha/Supervisory Patent Examiner, Art Unit 2419
Prosecution Insights