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 .
Claim Rejections - 35 USC § 102
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.
Claim(s) 1-13 is/are rejected under 35 U.S.C. 102 as being by Chong US 20200374742
1. A method for policy generation, comprising:
during a process of establishing or modifying a data tunnel (Chong: [0266] request message or the session policy control request message is used to request to establish a service-related dedicated tunnel or a service-related session), generating, by a first device,
a session management policy, wherein the session management policy comprises computing power information (Chong: [0250, 0266, 0566, 0613, 0625] generate at least one piece of quality of service QoS description information of a service, For example, the access network element sends an air interface related parameter type and a parameter requirement (for example, a spectrum used by a DRB and air interface channel power) in the target QoS information to the terminal device); and
sending, by the first device, the session management policy (Chong: [0266, 0566, 0613, 0625] the access network element may further send a part or all of the content of the target QoS information of the access network element to the terminal device. For example, the access network element sends an air interface related parameter type and a parameter requirement (for example, a spectrum used by a DRB and air interface channel power) in the target QoS information to the terminal device).
2. The method according to claim 1, wherein the computing power information comprises at least one of the following: data type, algorithm information, computing amount, computing amount per unit time, computing time, computing type, or peak computing amount (Chong: [0250, 0613, 0625] - date type).
3. The method according to claim 1, wherein generating, by the first device, the session management policy comprises: generating, by the first device, the session management policy based on at least one of the following: a session policy generation request obtained by the first device, first policy information obtained locally by the first device, or second policy information obtained by the first device from a second device (Chong: fig. 16-18, [0266, 0623-0625, 0366] - policy control function).
4. The method according to claim 3, wherein at least one of the session policy generation request, the first policy information, and the second policy information applied in the process of generating the session management policy by the first device comprises: computing power information (Chong: [0612-0613, 0623-0625] - target QoS information).
5. The method according to claim 3, wherein before generating, by the first device, the session management policy, the method further comprises: receiving, by the first device, the session policy generation request from a session management unit (Chong: [0469, 0612-0613, 0623-0625] - SMF sends the target QoS description information to the PCF).
6. The method according to claim 5, wherein during the process of establishing the data tunnel, the session policy generation request is generated after the session management unit receives a data tunnel establishment request sent by the terminal, wherein the data tunnel establishment request comprises the computing power information (Chong: fig. 16-18, [0266, 286, 0369, 0366, 0470-0472, 0566, 0620-0625]).
7. The method according to claim 5, wherein during the process of modifying the data tunnel, the policy generation request is used to trigger the first device to modify or update the session management policy (Chong: fig. 17a-18a [0472] - adjust a policy).
8. The method according to claim 1, wherein sending, by the first device, the session management policy comprises: sending, by the first device, the session management policy to the terminal, wherein the session management policy is a session management policy applied to the
terminal (Chong: [0393, 0613, 0620] sending the target QoS information to the session management function network element or a terminal device).
9. The method according to claim 8, wherein sending, by the first device, the session management policy to the terminal comprises: sending, by the first device, the session management policy to the terminal through the session management unit (Chong: fig. 3-4 [0385-0393] - sending the target QoS information to the session management function network element or a terminal device).
10. The method according to claim 1, wherein sending, by the first device, the session management policy comprises: sending, by the first device, the session management policy to a target device, wherein the session management policy is a session management policy applied to the target device; and the target device comprises any one of the following: a session management unit, a data tunnel gateway, or a wireless access unit (Chong: [0190, 0640] - e.g., sending, by the policy control function network element, the at least one piece of first QoS description information to a session management function network element).
11. The method according to claim 1, wherein the session management policy comprises a Quality of Service (QoS) parameter, wherein the QoS parameter comprises the computing power information (Chong: [0020, 0250, 0266, 0566, 0613, 0625] - QoS parameters include e.g., a guaranteed flow bit rate (GFBR)).
12. The method according to claim 11, wherein when the session management policy comprises a first identifier, a set of QoS parameters corresponding to the first identifier comprises the computing power information (Chong: [0126, 0250, 0252] - QoS parameters set).
13. The method according to claim 11, wherein the QoS parameter comprises at least one of the following: a first identifier; an allocation and retention priority (ARP); a reflective QoS attribute (RQA); a guaranteed flow bit rate (GFBR); a maximum flow bit rate (MFBR); a notification control parameter; a maximum packet loss rate; or computing power information, wherein the first identifier is used to identify a set of QoS parameters (Chong: [0126, 0250, 0266, 0566, 0613, 0625, 0730, 0734] - an allocation/retention priority (ARP) requirement ; a guaranteed flow bit rate (GFBR)).
Response to Arguments
Applicant's arguments filed on 1/6/26 have been fully considered but they are not persuasive.
Applicant Argument:
Applicant respectfully elects Group I (claims 1-13) with traversal.
Response to Arguments:
With respect to the above argument, Examiner would like to draw attention to that
the Applicant’s traversal has been considered but it not persuasive. The elected Group I is directed to method related to a first network node (e.g., data tunnel gateway), whereas non-elected Groups is/are directed to method of a SMF node and a terminal node which are totally distinct and related to separate function(s). Thus, for the above reason, the restriction requirement is maintained.
Remark:
The examiner stresses that the claims are too broad and require detail or specialization of the steps as recited in the claims. Alone and as claimed, the limitations are too open.
Examiner has cited particular portions of the references as applied to each claim limitation for the convenience of the applicant. Although the specified citations are representative of the teachings of the art and are applied to the specific limitations within the individual claim, other passages and figures may apply as well. It is respectfully requested from the applicant in preparing responses, to fully consider the references in entirety as potentially teaching all or part of the claimed invention, as well as the context of the passage as taught by the prior art or disclosed by the Examiner.
Regarding all other arguments presented by applicant, the arguments are substantially the same as those which have already been addressed above and in the interest of brevity; the Examiner directs the applicant to those responses above.
In addition, an interview could expedite the prosecution.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Sulaiman Nooristany whose telephone number is (571) 270-1929. The examiner can normally be reached on M-F from 9 to 5. If attempts to reach the examiner by telephone are unsuccessful, the examiner's supervisor, Jeffrey Rutkowski, can be reached on (571) 270-1215. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free).
/SULAIMAN NOORISTANY/Primary Examiner, Art Unit 2415