DETAILED ACTION
1. The following Office Action is based on the preliminary amendment filed on April 22, 2024, having claims 1-3, 7, 10, 16-17, 20, 24-26, 28, 31, 37-41, and 43 (claims 4-6, 8-9, 11-15, 18-19, 21-23, 27, 29-30, 32, 34-36, 42, and 44-65 were cancelled), and drawing figures 1-8.
Notice of Pre-AIA or AIA Status
2. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Specification
3. The abstract of the disclosure is objected to because of the following informalities:
The acronym QoS recited in lines 3-4 of the abstract must be written as “Quality of Service (QoS)” the first time it is recited in the abstract.
The term “and/or” recited in line 4 of the abstract must be written as “or.” The phrases “QoS” and “QoS requirement” have the same meaning. Therefore, one of the phrases must be deleted from the abstract.
A corrected abstract of the disclosure is required and must be presented on a separate sheet, apart from any other text. See MPEP § 608.01(b).
Claim Objections
4. Claims 1, 7, 10, 16-17, 20, 24-26, 28, 33, 40-41, and 43 are objected to because of the following informalities:
The word “scenario” recited in line 3 of claim 1 must be deleted from the claim because it is unnecessary to understand the claim. Furthermore, the word is not affirmative because it implies that the limitation may be true (happening) or false (not happening).
The acronym QoS recited in lines 4-5 of claim 1 must be written as “Quality of Service (QoS)” the first time it is recited in the claim.
The term “and/or” recited in line 3 of claim 7 must be deleted to render the claim affirmative. The phrase following “and/or” is recited twice in the claim. Deletion of one of phrases is recommended.
The term “and/or” recited in line 6 of claim 7 must be replaced by the phrase “at least one of” at the beginning of the claim to render the following limitations/conditions affirmative.
The term “and/or” recited in lines 4 and 12 of claim 10 must be replaced by the phrase “at least one of” at the beginning of the claim to render the following limitations/conditions affirmative.
A dash (-) must be added between the words “threshold” and “based” in line 9 of claim 10 to conform with English grammar rules.
The period (.) following the word “request” in line 10 of claim 10 must be replaced by a comma (,) to comply with English punctuation rules.
Claim 10 recites the limitation “the set of configuration (sic)” in lines 12-13. The word “configuration” must be spelled “configurations” (plural form) to conform with English grammar.
The word “out” located between the words “one” and “of” in line 2 of claim 16 must be deleted to render the claim affirmative.
Claim 17 recites the limitation “transmit and/or receive signals to and/or from a relaying transceiver” in lines 2-3. The limitation must be amended to recite “transmit signals to or receiving signals from a relaying transceiver” to render the claim affirmative.
Claim 17 recites the limitation recites the limitation “update and/or reconfigure” in line 8. The term “and/or” should be changed to “or.”
The term “and/or” recited in lines 5 and 8 of claim 17 must be replaced by the phrase “at least one of” at the beginning of the claim to render the following limitations/conditions affirmative.
Claim 17 recites the limitation “a (sic) update” in line 9. The word “a” must be replaced by the “an” to comply with English grammar.
The term “and/or” recited in lines 4 and 15 of claim 20 must be replaced by the phrase “at least one of” at the beginning of the claim to render the following limitations/conditions affirmative.
Claim 20 recites the limitation “a channel busy ratio, CBR” in line 7. The limitation must be written as “a channel busy ratio (CBR)” to make it clear that CBR is the acronym of the preceding words.
The term “and/or” recited between “CBR” and “channel” in line 7 of claim 20 must be replaced by the word “or” to render the claim affirmative.
Claim 20 recites the limitation “a channel occupancy rate, CR” in line 7. The limitation must be written as “a channel occupancy rate (CR)” to make it clear that CR is the acronym of the preceding words.
The word “Wherein” recited in line 2 of claim 24 should be written in lowercase letters.
The word “scenario” recited in line 3 of claim 25 must be deleted from the claim because it is unnecessary to understand the claim. Furthermore, the word is not affirmative because it implies that the limitation may be true (happening) or false (not happening).
The acronym QoS recited in lines 7-8 of claim 25 must be written as “Quality of Service (QoS)” the first time it is recited in the claim.
The term “and/or” recited in claims 26, 28, 33, and 40 must be replaced by the phrase “at least one of” to render the claims affirmative.
Claim 28 recites the limitation “PC5 configuration and/or a Uu configuration” in lines 4-5. The term “and/or” must be replaced by the word “or.”
Claim 41 recites the limitation recites the limitation “update and/or reconfigure” in lines 2, 4, and 6. The term “and/or” should be changed to “or.”
The term “and/or” recited in line 4 of claim 41 must be replaced by the phrase “at least one of” to render the claims affirmative.
A dash (-) must be added between the words “event” and “based” in line 9 of claim 41 to conform with English grammar rules.
The term “and/or” recited in lines 4, 14, and 16 of claim 43 must be replaced by the phrase “at least one of” to render the claims affirmative.
Claim 43 recites the limitation “a channel busy ratio, CBR” in lines 6 and 19. The limitation must be written as “a channel busy ratio (CBR)” to make it clear that CBR is the acronym of the preceding words.
The term “and/or” recited between “CBR” and “channel” in lines 6 and 19 of claim 43 must be replaced by the word “or” to render the claim affirmative.
Claim 43 recites the limitation “a channel occupancy rate, CR” in lines 6 and 19. The limitation must be written as “a channel occupancy rate (CR)” to make it clear that CR is the acronym of the preceding words.
Appropriate correction is required.
Claim Rejections - 35 USC § 112
5. The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 1-3, 7, 10, 16-17, 20, 24-26, 28, 31, 37-41, and 43 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claim 1 recites the limitation “QoS and/or QoS requirement” in lines 4-5. The limitation renders the claim vague and indefinite because “QoS” and “QoS requirement” have the same meaning. One of the recitations must be deleted from the claim.
Claim 25 recites the limitation “QoS and/or QoS requirement” in lines 7-8. The limitation renders the claim vague and indefinite because “QoS” and “QoS requirement” have the same meaning. One of the recitations must be deleted from the claim.
Claim Rejections - 35 USC § 102
6. In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(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, 7, 10, 16-17, 20, 24-26, 28, 37-41, and 43 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Sun et al. (US 2024/0049104 A1).
For claim 1, Sun discloses a transceiver (Fig 1, remote UE 106) of a wireless communication system, wherein the transceiver is configured to operate in a sidelink in-coverage, out of coverage ([0024] UE 106 is located outside the cell coverage of base station 102) or partial coverage scenario,
wherein the transceiver is configured to operate, in dependence on a QoS and/or QoS requirement of the transceiver ([0079-0080] remote UE 106 operates based on E2E QoS requirements set by relay UE 104 or base station 102), using a selected configuration ([0081] last 3 lines, the relay UE selects a QoS enforcement configuration received from the base station).
For claim 2, Sun discloses the transceiver is configured to receive the selected configuration from a relaying transceiver or a base station of the wireless communication network ([0080] the relay UE sends a QoS message to the remote UE, wherein the QoS message may be identical to the QoS configuration that the relay UE received from the base station).
For claim 3, Sun discloses the transceiver is configured to receive the selected configuration via a configuration message ([0080] the relay UE 104 sends a QoS message to the remote UE 106).
For claim 7, Sun discloses the selected configuration is selected out of a set of configurations ([0051] the relay UE selects one or more QoS configurations for first hop and second hop from a splitting table comprising one or more sets of configurations),
and/or wherein the selected configuration is selected out of a set of configurations, wherein at least a proper subset of configurations of the set of configurations are associated with different QoS requirements of the transceiver ([0051] the relay UE selects one or more QoS configurations for first hop and second hop from a splitting table comprising one or more sets of configurations, wherein the different QoS requirements comprise different values for CBR for the first hop or second hop for communications with the remote UE (i.e., the transceiver)),
and/or wherein at least a proper subset of configurations of the set of configurations are associated with different communication conditions ([0051] the relay UE selects one or more QoS configurations for first hop and second hop from a splitting table comprising one or more sets of configurations, wherein the different QoS requirements comprise different values for CBR for the first hop or second hop for communications with the remote UE (i.e., the transceiver)); [0054-0055] the different CBR values to correspond to different link conditions as measured by the relay UE),
For claim 10, Sun discloses the transceiver is configured to report the QoS requirement to a relaying transceiver or a base station of the wireless communication network ([0082] the transceiver of the remote UE 106 transmits the QoS requirement to the relay UE 104),
and/or wherein the transceiver is configured to report the QoS requirement to a relaying transceiver or a base station of the wireless communication network, wherein the transceiver is configured to report the QoS requirement: event based ([0080] and [0082] the remote UE 106 transmits the QoS requirement to the relay UE after (event-based) receiving the QoS capability message from the relay UE), periodically, threshold based, responsive to a reporting request, or responsive to QoS requirements,
and/or wherein the transceiver is configured to select a configuration out of the set of configuration indicated/signaled by a relaying transceiver ([0080-0081] the relay UE transmits a selected QoS configuration to the remote UE based on a configuration message received from the base station) or base station or another transceiver of the wireless communication system, to acquire the selected configuration.
For claim 16, Sun discloses the QoS requirement is at least one of latency, data rate, reliability ([0082] PER (packet error rate)), different data flows or resource types, priority level ([0082] priority).
For claim 17, Sun discloses the transceiver is configured to transmit and/or receive signals to and/or from a relaying transceiver or base station of the wireless communication system using the selected configuration ([0080] the remote UE transmits and receives signals from the relay UE based on the QoS message received from the relay UE),
and/or wherein the set of configurations are stored in a memory of the transceiver or wherein the set of configurations are provided to the transceiver by a relaying transceiver or base station of the wireless communication network,
and/or wherein the transceiver is configured to update and/or reconfigure one or more configurations of the set of configurations responsive to a reception of a update and or reconfiguration information ([0080] and [0082] the remote UE 106 transmits the QoS requirement to the relay UE after (event-based) receiving the QoS capability message from the relay UE).
For claim 20, Sun discloses the transceiver is configured to report its operating status to a relaying transceiver or a base station of the wireless communication system ([0082] the transceiver 106 transmits its QoS requirement to the relay UE 104, wherein the QoS requirement comprises PDB (packet delay budget) of the transceiver 106 which is the acceptable latency for the transceiver),
and/or wherein the wherein the transceiver is configured to report its operating status to a relaying transceiver or a base station of the wireless communication system, wherein the operating status includes at least one out of a channel busy ratio, CBR, and/or channel occupancy rate, CR at the transceiver, a load of the transceiver, a buffer status of the transceiver, a queueing latency of the transceiver ([0082] the transceiver 106 transmits its QoS requirement to the relay UE 104, wherein the QoS requirement comprises PDB (packet delay budget) of the transceiver 106 which is the acceptable latency for the transceiver), a packet error rate of the transceiver ([0082] PER (packet error rate)), a number of HARQ retransmissions of the transceiver, a measurement report of the transceiver,
and/or wherein the transceiver is configured to report its operating status to a relaying transceiver or a base station of the wireless communication system, wherein the transceiver is configured to report its operating status: event based, periodically, threshold based, or responsive to an operating status reporting request ([0080] and [0082] the remote UE 106 transmits the QoS requirement to the relay UE after (event-based) receiving the QoS capability message from the relay UE).
For claim 24, Sun discloses the transceiver is configured to report a packet delay budget to a relaying transceiver of the wireless communication system ([0082] PDB = packet delay budget).
For claim 25, Sun discloses a relaying transceiver (Fig 1, relay UE 104) of a wireless communication system, wherein the relaying transceiver is configured to operate in a sidelink in-coverage ([0024] relay UE 104 is in cell coverage of base station 102), out of coverage or partial coverage scenario,
wherein the relaying transceiver is configured to relay signals between a transceiver and a base station or another transceiver of the wireless communication system (Fig 1 and [0078] the relay UE relay packets between the base station and remote UE 106),
wherein the relaying transceiver is configured to operate, in dependence on a QoS or/and QoS requirement of the transceiver, using a selected configuration ([0081] the relay UE relays packets to remote UE 106 based on a E2E QoS requirement which is based on a QoS enforcement configuration received from the base station).
For claim 26, Sun discloses the relaying transceiver is configured to receive the selected configuration from a base station of the wireless communication network ([0081] relay UE receives the selected QoS enforcement configuration from the base station),
and/or wherein the relaying transceiver is configured to receive the selected configuration via a configuration message ([0081] the base station transmits the QoS enforcement configuration via dedicated RRC message).
For claim 28, Sun discloses the relaying transceiver is configured to relay the selected configuration to the transceiver ([0086-0087] based on the splitting table configurations received from the base station, the relay UE may adjust and assign (i.e., sends a configuration message) QoS requirements for the remote UE 106),
and/or wherein the selected configuration includes a PC5 configuration and/or a Uu configuration ([0087] the first hop and second hop QoS requirements involves PC5 (sidelink) connection between the relay UE and the remote UE 106, or between the remote UE 106 and a target UE 108).
For claim 33, Sun discloses the QoS requirement is reported from the transceiver to the relaying transceiver ([0082] the remote UE 106 transmits the QoS requirement to the relay UE after (event-based) receiving the QoS capability message from the relay UE).
and/or wherein the relaying transceiver is configured to select a configuration out of the set of configurations in dependence on the QoS requirement of the transceiver, to acquire the selected configuration ([0086-0087] based on the splitting table configurations received from the base station, the relay UE may adjust/select and assign (i.e., sends a selected configuration message) QoS requirements for the remote UE 106).
For claim 37, Sun discloses the relaying transceiver is configured to signal the selected configuration to the transceiver ([0087] the relay UE may adjust and assign (i.e., sends a selected configuration message) QoS requirements for the remote UE 106).
For claim 38, Sun discloses the relaying transceiver is configured to relay signals between the transceiver and the base station using the selected configuration ([0081] the relay UE relays packets to remote UE 106 based on a E2E QoS requirement which is based on a QoS enforcement configuration received from the base station).
For claim 39, Sun discloses the relaying transceiver is configured to provide the set of configurations to the transceiver ([0086-0087] based on the splitting table configurations received from the base station, the relay UE may adjust and assign (i.e., sends a configuration message) QoS requirements for the remote UE 106).
For claim 40, Sun discloses the relaying transceiver is configured to determine at least a part of the set of configurations itself ([0087] the relay UE (by itself) may adjust and assign (i.e., sends a configuration message) QoS requirements for the remote UE 106) and/or wherein the set of configurations are provided to the relaying transceiver by the base station ([0086] the set of configurations are from a splitting table (page 5, table 1) received from the base station).
For claim 41, Sun discloses the relaying transceiver is configured to update and/or reconfigure one or more configurations of the set of configurations in the transceiver ([0087] the relay UE (by itself) may adjust and assign (i.e., sends a configuration message) QoS requirements for the remote UE 106 based on [0086] the set of configurations listed in a splitting table (page 5, table 1) received from the base station).
and/or wherein the relaying transceiver is configured to update and/or reconfigure one or more configurations of the set of configurations in the transceiver, wherein the relaying transceiver is configured to update and/or reconfigure one or more configurations of the set of configurations in the transceiver periodically, event based, or responsive to a request for reconfiguration received from the transceiver ([0087] the relay UE (by itself) may adjust and assign (i.e., sends a configuration message) QoS requirements for the remote UE 106 based on [0086] the set of configurations listed in a splitting table (page 5, table 1) received from the base station).
For claim 43, Sun discloses the relaying transceiver is configured to receive an operating status report from the transceiver ([0080] and [0082] the remote UE 106 transmits the QoS requirement to the relay UE after (event-based) receiving the QoS capability message from the relay UE),
and/or wherein the relaying transceiver is configured to receive an operating status report from the transceiver, wherein the operating status includes at least one out of a channel busy ratio, CBR, and/or channel occupancy rate, CR at the transceiver, a load of the transceiver, a buffer status of the transceiver, a queueing latency of the transceiver ([0082] the transceiver 106 transmits its QoS requirement to the relay UE 104, wherein the QoS requirement comprises PDB (packet delay budget) of the transceiver 106 which is the acceptable latency for the transceiver), a packet error rate of the transceiver ([0082] PER (packet error rate)), a number of HARQ retransmissions of the transceiver, a measurement report of the transceiver,
and/or wherein the relaying transceiver is configured to report its operating status to the base station of the wireless communication system ([0079] the relay UE 104 reports its QoS capability to the base station),
and/or wherein the relaying transceiver is configured to report its operating status to the base station of the wireless communication system, wherein the operating status includes at least one out of a channel busy ratio, CBR, and/or channel occupancy rate, CR at the relaying transceiver, a load of the relaying transceiver, a buffer status of the relaying transceiver, a queueing latency of the relaying transceiver, ([0082] the transceiver 106 transmits its QoS requirement to the relay UE 104, wherein the QoS requirement comprises PDB (packet delay budget) of the transceiver 106 which is the acceptable latency for the transceiver), a packet error rate of the transceiver ([0082] PER (packet error rate)), a number of HARQ retransmissions of the relaying transceiver, a measurement report of the relaying transceiver.
Claim Rejections - 35 USC § 103
7. 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.
Claim 31 is rejected under 35 U.S.C. 103 as being unpatentable over Sun et al. (US 2024/0049104 A1) in view of Wu et al. (US 2022/0312376 A1).
For claim 31, Sun does not expressly disclose the selected configuration defines a mapping between Uu and PC5 radio bearers.
Wu, from the same or similar field of endeavor, teaches the selected configuration defines a mapping between Uu and PC5 radio bearers ([0102] the relay UE stores configuration information for communication with the remote UE, wherein the configuration information comprises a Uu bearer mapping operating between the relay UE and the network node). Thus, it would have been obvious to one skilled in the art to include Uu bearer mapping information in the selected configurations of the network of Sun based on the teachings of Wu at the time of the invention.
Conclusion
8. The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. See PTO-892 form.
9. Any inquiry concerning this communication or earlier communications from the examiner should be directed to Elisabeth B Magloire whose telephone number is (571)272-5601. The examiner can normally be reached M-F 8 AM-5 PM ET.
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, Sujoy K Kundu can be reached at 571-272-8586. 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.
/ELISABETH BENOIT MAGLOIRE/Primary Examiner, Art Unit 2471