DETAILED ACTION
This communication is response to the application filed 01/23/2024. Claims 1, 2, 4-9, 13-16, 20, 21, 24, 26-28, 31, 32, and 75. The amendment filed on 01/23/2024 is acknowledged and entered.
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 .
Information Disclosure Statement
The information disclosure statement (IDS) submitted on 01/23/2024 is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Claim Objections
Claim 4 and 15 are objected to because of the following informalities: “wherein wherein” recited in lines 5-6 of claim 4 should be changed to “wherein” and “method claims 2” recited in lines 1-2 of claim 15 should be changed to “method according to claim 2”. Appropriate correction is required.
Claim Rejections - 35 USC § 102
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1, 2, 8, 14, 15, 21, 22, 27, and 75 is/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by US 2024/0155420 to ZHANG et al. (hereafter Zhang).
Regarding claim 1, Zhang discloses a quality of service (QoS) flow scheduling method, performed by a first network device (see Zhang, ¶ 0005: improved methods, systems, devices, and apparatuses that -support configuration for asymmetric quality of service (QoS) flows), comprising:
determining a candidate configuration set for a QoS flow (see Zhang, ¶ 0006: establishing a connection with a base station, where the connection corresponds to a QoS flow for communications between the UE and the base station, receiving control signaling including a configuration for the QoS flow in response to establishing the connection; ¶ 0090: The core network 130-a may signal the configuration for the QoS flow 210 to the base station 105-a (e.g., the RAN) via the communication link 215 (e.g., an N2 link). The base station 105-a may transmit control signaling via the communication link 205 to forward the QoS flow configuration 220 to the UE 115-a; ¶ 0098: The flow direction characteristic, and one or more other QoS characteristics for a respective QoS flow 210, may be determined by the base station 105-a, the UE 115-a, or both based on a mapping (e.g., a one-to-one mapping) between a QoS ID (e.g., a 5G QoS ID (5QI)) and the QoS characteristics),
wherein the candidate configuration set comprises a plurality of parameter configurations for the QoS flow (see Zhang, ¶ 0006: where the configuration includes a set of one or more parameters specific to a direction of the QoS flow, and communicating data in the direction of the QoS flow in accordance with the set of one or more parameters; ¶ 0091: The QoS flow configuration 220 may configure each QoS flow 210 with a QoS ID, a set of QoS parameters, a set of QoS characteristics, or any combination thereof; ¶ 0098: a set of one or more QoS parameters indicated via the QoS flow configuration 220 may include the QoS ID, and each QoS ID value may correspond to a set of QoS characteristics, one or more of which may be configured to indicate a QoS flow direction).
Regarding claim 2, Zhang discloses the QoS flow scheduling method according to claim 1, wherein the candidate configuration set comprises at least one of:
one or more collaborative parameter configurations, which are one or more parameter configurations for multi-QoS-flow collaborative scheduling; or one or more non-collaborative parameter configurations, which are one or more parameter configurations for independently scheduling the QoS flow (see Zhang, ¶ 0100: the core network 130-a may configure a downlink direction for the QoS flow 210-a. The core network 130-a may signal a set of one or more parameters for the flow direction to the base station 105-a (e.g., the RAN). The set of one or more parameters may include a QoS ID for the QoS flow 210-a. The base station 105-a may forward the QoS flow configuration 220 including the set of one or more parameters to the UE 115-a. The base station 105-a and the UE 115-a may determine that the flow direction of the QoS flow 210-a is downlink based on a mapping, such as the mapping illustrated in Table 1, between the QoS ID and a flow direction characteristic configured to indicate the direction; ¶ 0101: the core network 130-a may configure an asymmetric QoS flow 210. That is, the core network 130-a may configure parameters or characteristics specific to an uplink direction in a bidirectional QoS flow 210 that are different from parameters or characteristics specific to a downlink direction in the QoS flow 210. For example, one or more bit rate parameters, such as a GFBR, an MFBR, or both may be configured specifically for uplink or downlink. In some examples, the SMF of the core network 130-a may receive an indication of policy and charging control (PCC) rules for data packets in the wireless communications system 200. The SMF may determine different GFBR values, MFBR values, or both for uplink and downlink data in a QoS flow 210 based on the PCC rules);
wherein the one or more non-collaborative parameter configurations comprise a plurality of parameter configurations for independently scheduling the QoS flow in different scenarios (see Zhang, ¶ 0103: By setting the GFBR, the MFBR, or both to zero, the core network 130-a (e.g., the SMF) may indicate that a direction of the QoS flow 210 is unidirectional (e.g., an implicit indication of the QoS flow direction). The base station 105-a may allocate resources for the unidirectional QoS flow 210 accordingly; ¶ 0106: The core network 130-a may additionally or alternatively configure separate communication parameters for uplink and downlink directions in the QoS flow 210, to provide support for asymmetric data traffic in a QoS flow 210; ¶ 0120: By supporting a QoS configuration that includes parameters specific to a direction of the QoS flow, the processor of the device 405 may support communication of asymmetric data traffic. Communicating asymmetric data traffic via a same QoS flow instead of different QoS flows may reduce processing and provide for more efficient utilization of communication resources).
Regarding claim 8, Zhang discloses the QoS flow scheduling method according to claim 2,further comprising: collaboratively scheduling, based on determining that there is a QoS flow collaborative scheduling requirement, at least two QoS flows to be collaboratively scheduled according to the one or more collaborative parameter configurations, wherein the at least two QoS flows to be collaboratively scheduled comprise the QoS flow (see Zhang, ¶ 0088: By indicating a direction of a QoS flow and setting QoS parameters that are specific to flow direction, the network may reduce overhead and improve utilization of communication resources for QoS flows, particularly when one direction of traffic has higher or lower QoS requirements than another direction of traffic; ¶ 0093: the core network 130-a may configure a first bidirectional QoS flow 210 according to a first set of QoS characteristics for the uplink data and a second bidirectional QoS flow 210 according to a second set of QoS characteristics for the downlink data. That is, the core network 130-a may allocate different QoS flows 210 separately for uplink and downlink traffic (e.g., to efficiently utilize radio resources); ¶ 0110: The control signaling may include a configuration for the QoS flow. The configuration may include a set of one or more parameters specific to a direction of the QoS flow. In some examples, the configuration may indicate direction-specific parameters for multiple QoS flows. The parameters may include a QoS ID, a flow direction parameter, one or more GFBR parameters, one or more MFBR parameters, other QoS parameters, or any combination thereof. A value of the QoS ID may be mapped to one or more QoS characteristics).
Regarding claim 14, Zhang discloses the QoS flow scheduling method according to claim 2,further comprising: restoring, based on receiving non-collaboration control information, to independently schedule at least two QoS flows that is being collaboratively scheduled; wherein he at least two QoS flows that is being collaboratively scheduled comprises the QoS flow (see Zhang, ¶ 0088: By indicating a direction of a QoS flow and setting QoS parameters that are specific to flow direction, the network may reduce overhead and improve utilization of communication resources for QoS flows, particularly when one direction of traffic has higher or lower QoS requirements than another direction of traffic; ¶ 0093: the core network 130-a may configure a first bidirectional QoS flow 210 according to a first set of QoS characteristics for the uplink data and a second bidirectional QoS flow 210 according to a second set of QoS characteristics for the downlink data. That is, the core network 130-a may allocate different QoS flows 210 separately for uplink and downlink traffic (e.g., to efficiently utilize radio resources); ¶ 0110: The control signaling may include a configuration for the QoS flow. The configuration may include a set of one or more parameters specific to a direction of the QoS flow. In some examples, the configuration may indicate direction-specific parameters for multiple QoS flows. The parameters may include a QoS ID, a flow direction parameter, one or more GFBR parameters, one or more MFBR parameters, other QoS parameters, or any combination thereof. A value of the QoS ID may be mapped to one or more QoS characteristics).
Regarding claim 15, Zhang discloses the QoS flow scheduling method according to claim 2,further comprising: adjusting, based on a change in an independent scheduling scenario and according to the one or more non-collaborative parameter configurations, the one or more non-collaborative parameter configuration being adopted for independently scheduling the QoS flow (see Zhang, ¶ 0045: The base station may receive the indication of the direction and allocate radio resources for the QoS flow in the indicated direction. The direction may be unidirectional (e.g., uplink or downlink) or bidirectional (e.g., uplink and downlink). The base station may transmit a configuration for the QoS flow to a UE when the UE establishes a connection with the network, when a QoS flow is modified, when a new QoS flow is established, or any combination thereof; ¶ 0129: to support receiving the control signaling, the connection establishment component 625 may be configured as or otherwise support a means for receiving the control signaling based on establishing the connection with the base station, an establishment of the QoS flow, a modification of the QoS flow, or any combination thereof).
Regarding claim 21, it is rejected for the same reasons as set forth in claim 1.
Regarding claim 22, it is rejected for the same reasons as set forth in claim 2.
Regarding claim 27, it is rejected for the same reasons as set forth in claim 8.
Regarding claim 75, it is rejected for the same reasons as set forth in claim 1. Although phrased as an apparatus claim, the claim is nevertheless simple repetitions of the subject matter of claim 1.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
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) 4 and 26 is/are rejected under 35 U.S.C. 103 as being unpatentable over Zhang in view of US 2022/0386179 to Dhammawat et al. (hereafter Dhammawat).
Regarding claim 4, Zhang discloses the QoS flow scheduling method according to claim 1, but does not explicitly disclose wherein determining the candidate configuration set for the QoS flow comprises: receiving a QoS request message, wherein the QoS request message comprises configuration information on the candidate configuration set for the QoS flow, and wherein the QoS request message comprises at least one of a QoS setup request message or a QoS modify request message; or determining the candidate configuration set based on a protocol.
However, Dhammawat discloses wherein determining the candidate configuration set for the QoS flow comprises: receiving a QoS request message, wherein the QoS request message comprises configuration information on the candidate configuration set for the QoS flow, and wherein the QoS request message comprises at least one of a QoS setup request message or a QoS modify request message; or determining the candidate configuration set based on a protocol (see Dhammawat, ¶ 0130: UPF 106 may send, to SMF 126 based on the detecting, a message which indicates a request for QoS Flow handling due to flow degradation; ¶ 0131: SMF 126 may select a lower-priority QoS Flow that has a lower priority than the dedicated QoS Flow and/or other QoS Flows routed via UPF 106. SMF 126 may send, to UPF 106, a message which indicates a session modification request, for deleting the selected QoS Flow or for modifying (downgrading or lowering) a QoS of the selected QoS Flow; ¶ 0133: In response to the detection of the traffic, UPF 106 may send, to SMF 126, a message which indicates a request for creating a dedicated QoS Flow for traffic for the application for UE 102).
Thus, it would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to implement the above teaching as taught by Dhammawat and incorporate it into the system of Zhang for efficient resource utilization in the communication system (see Dhammawat, ¶ 0005).
Regarding claim 26, it is rejected for the same reasons as set forth in claim 4.
Allowable Subject Matter
Claims 5, 9, 13, 16, 20, 24, 28, 31, and 32 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
US 2022/0248257 to BAO et al. discloses method for configuring a quality of service parameter is applied to a network-side device and includes: configuring a mapping relationship between a QoS parameter set and an SLRB parameter set for a terminal; in a case that a QoS parameter of the terminal matches none of configured QoS parameter sets, allowing the terminal to trigger RRC connection establishment; or indicating a default SLRB parameter set to the terminal, where the default SLRB parameter set is to be used by the terminal in a case that a QoS parameter of the terminal matches none of configured QoS parameter sets. In the implicit manner, in a case that the default SLRB parameter set is not included in the configuration information and that a QoS parameter of a to-be-initiated service matches none of the QoS parameter sets in the configuration information, RRC connection establishment may be triggered.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to RASHEED GIDADO whose telephone number is (571)270-7645. The examiner can normally be reached Monday - Friday 8AM-5PM EST.
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, Ricky Ngo can be reached at 571-272-3139. 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.
/RASHEED GIDADO/ Primary Examiner, Art Unit 2464