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 .
DETAILED ACTION
This office action is in response to the original application filed on 11/14/2022.
Claims 16-35 are rejected.
Claim 1-15 are canceled.
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.
Claims 16-35 are rejected under 35 U.S.C 103 as being unpatentable over “3GPP TSG-SA WG6 Meeting #37-e, E-meeting, 8 May 2020, S6-200764, Convida Wireless LCC, Solution to the Key Issue of Message Segmentation and Reassembly, 3GPP TR 23.700 v0.5.0” (hereinafter as “S6-200764”) in view of Casaccia (US 2003/0035440)
Regarding Claim 16, “S6-200764” teaches a method performed by a source node in a wireless communication system, the method comprising:
receiving a message related to an application (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, step 1, an Application Server sends a message to a MSGin5G Server that targets an Application Client on a UE);
identifying whether a size of the message related to the application exceeds a maximum allowed packet size (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 2 the MSGin5G Server compares the size of the received message to the maximum allowed packet size of the access network transport of the targeted UE and detects that the size exceeds the limit);
segmenting the message related to the application into one or more segmented messages based on the maximum allowed packet size (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 2 if the size of the received message exceeds the maximum allowed packet size, then the MSGin5G Sever segments the received message into a set of segmented messages such that each segmented message can fit within an individual access network transport packet);
transmitting, to a destination node, the one or more segmented messages (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 3 the MSGin5G Server sends each segmented message to the targeted UE within an individual access network transport packet);
PNG
media_image1.png
622
848
media_image1.png
Greyscale
“S6-200764” does not explicitly teach the below limitations:
receiving a confirmation message associated with the message related to the application, wherein result information included in the confirmation message is determined based on the one or more segmented messages.
However Casaccia teaches the below limitations:
receiving a confirmation message associated with the message related to the application, wherein result information included in the confirmation message is determined based on the one or more segmented messages (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK message is interpreted as being the confirmation message).
PNG
media_image2.png
570
710
media_image2.png
Greyscale
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the invention of “S6-200764” by adding a confirmation message in response to the transmission of a segmented message as taught by Casaccia. Because “S6-200764” and Casaccia teach segmented messaging, and specifically Casaccia teaches a confirmation message in response to the transmission of a segmented message for the benefit of the analogous art of segmented message transmission (Casaccia, abstract).
Regarding Claim 17, “S6-200764” and Casaccia further teach wherein the one or more segmented messages comprise a segmentation set identifier indicating the one or more segmented messages are associated with the message related to the application, and a segment sequence number, and (“S6-200764”, Table 6.X.1.2-1: Segmentation and Reassembly Information Elements, “Segmentation Set Identifier” identifies all segmented messages associated within the same set of segmented messages, “Segment Sequence Number” refers to an incrementing counter that indicates the sequence number of each segmented message within a set of segmented messages),
wherein a reassembly of the one or more segmented messages is performed based on the segmentation set identifier and the segment sequence number (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 4 the MSGin5G Client receives all the segmented messages and reassembles them into a single MSGin5G message based on the information elements defined in Table 6.X.1.2-1).
Regarding Claim 18, “S6-200764” and Casaccia further teach further comprising:
receiving a segment recovery request message from the destination node based on at least one missed segmented message among the one or more segmented messages (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK message is interpreted as the confirmation message and the segment recovery request message);
transmitting a segment recovery acknowledgement message to the destination node (Casaccia, Fig 9B, paragraph 83, in response to the transmitter receiving the NAK at time t11, the transmitter retransmits the segment at time t12, the retransmission of the segment is interpreted as the segment recovery acknowledgement message); and
transmitting the at least one missed segmented message to the destination node (Casaccia, Fig 9B, paragraph 83, in response to the transmitter receiving the NAK at time t11, the transmitter retransmits the segment at time t12).
Regarding Claim 19, “S6-200764” and Casaccia further teach wherein the recovery request message comprises a segmentation set identifier indicating the at least one missed segmented message is associated with the message related to the application, and a list of segment range indicating a segment sequence of the at least one missed segmented message (“S6-200764”, Table 6.X.1.2-1: Segmentation and Reassembly Information Elements, “Segmentation Set Identifier” identifies all segmented messages associated within the same set of segmented messages, “Segment Sequence Number” refers to an incrementing counter that indicates the sequence number of each segmented message within a set of segmented messages, Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, it is interpreted that the identifying of the missing segments of Casaccia is via the identifiers from “S6-200764”).
Regarding Claim 20, “S6-200764” and Casaccia further teach wherein the result information of the confirmation message is determined based on whether the transmission of the at least one missed segmented message is successful (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK is interpreted as being the confirmation message).
Regarding Claim 21, “S6-200764” and Casaccia further teach wherein the confirmation message comprises a segmentation set identifier indicating the one or more segmented messages are associated with the message related to the application, and the result information indicating whether a reassembly of the one or more segmented messages is successful (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK message is interpreted as being the confirmation message)
Regarding Claim 22, “S6-200764” and Casaccia further teach further comprising:
transmitting, to the destination node, an acknowledge message related to the confirmation message (Casaccia, Fig 9B, paragraph 83, in response to the transmitter receiving the NAK at time t11, the transmitter retransmits the segment at time t12, the retransmission of the segment is interpreted as an acknowledgement to the NAK).
Regarding Claim 23, “S6-200764” teaches a method performed by a destination node in a wireless communication system, the method comprising:
receiving, from a source node, one or more segmented messages associated with a message related to an application, wherein the one or more segmented messages are segmented when a size of the message related to the application exceeds a maximum allowed packet size (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 2 if the size of the received message exceeds the maximum allowed packet size, then the MSGin5G Sever segments the received message into a set of segmented messages such that each segmented message can fit within an individual access network transport packet, in step 3 the MSGin5G Server sends each segmented message to the targeted UE within an individual access network transport packet);
“S6-200764” does not explicitly teach the below limitation:
transmitting a confirmation message associated with the message related to the application, wherein result information included in the confirmation message is determined based on the one or more segmented messages.
However Casaccia teaches the below limitation:
transmitting a confirmation message associated with the message related to the application, wherein result information included in the confirmation message is determined based on the one or more segmented messages (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK message is interpreted as being the confirmation message).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the invention of “S6-200764” by adding a confirmation message in response to the transmission of a segmented message as taught by Casaccia. Because “S6-200764” and Casaccia teach segmented messaging, and specifically Casaccia teaches a confirmation message in response to the transmission of a segmented message for the benefit of the analogous art of segmented message transmission (Casaccia, abstract).
Regarding Claim 24, “S6-200764” and Casaccia further teach wherein the one or more segmented messages comprise a segmentation set identifier indicating the one or more segmented messages are associated with the message related to the application, and a segment sequence number (“S6-200764”, Table 6.X.1.2-1: Segmentation and Reassembly Information Elements, “Segmentation Set Identifier” identifies all segmented messages associated within the same set of segmented messages, “Segment Sequence Number” refers to an incrementing counter that indicates the sequence number of each segmented message within a set of segmented messages), and
wherein a reassembly of the one or more segmented messages is performed based on the segmentation set identifier and the segment sequence number (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 4 the MSGin5G Client receives all the segmented messages and reassembles them into a single MSGin5G message based on the information elements defined in Table 6.X.1.2-1).
.
Regarding Claim 25, “S6-200764” and Casaccia further teach further comprising:
transmitting a segment recovery request message based on at least one missed segmented message among the one or more segmented messages (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK message is interpreted as the confirmation message and the segment recovery request message);
receiving a segment recovery acknowledgment message to the destination node (Casaccia, Fig 9B, paragraph 83, in response to the transmitter receiving the NAK at time t11, the transmitter retransmits the segment at time t12, the retransmission of the segment is interpreted as the segment recovery acknowledgement message); and
receiving the at least one missed segmented message (Casaccia, Fig 9B, paragraph 83, in response to the transmitter receiving the NAK at time t11, the transmitter retransmits the segment at time t12).
Regarding Claim 26, “S6-200764” and Casaccia further teach wherein the recovery request message comprises a segmentation set identifier indicating the at least one missed segmented message is associated with the message related to the application, and a list of segment range indicating a segment sequence of the at least one missed segmented message (“S6-200764”, Table 6.X.1.2-1: Segmentation and Reassembly Information Elements, “Segmentation Set Identifier” identifies all segmented messages associated within the same set of segmented messages, “Segment Sequence Number” refers to an incrementing counter that indicates the sequence number of each segmented message within a set of segmented messages, Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, it is interpreted that the identifying of the missing segments of Casaccia is via the identifiers from “S6-200764”).
Regarding Claim 27, “S6-200764” and Casaccia further teach wherein the result information of the confirmation message is determined based on whether the transmission of the at least one missed segmented message is successful (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK is interpreted as being the confirmation message).
Regarding Claim 28, “S6-200764” and Casaccia further teach wherein the confirmation message comprises a segmentation set identifier indicating the one or more segmented messages are associated with the message related to the application, and the result information indicating whether a reassembly of the one or more segmented messages is successful (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK message is interpreted as being the confirmation message).
Regarding Claim 29, “S6-200764” and Casaccia further teach further comprising:
receiving, from the destination node, an acknowledge message related to the confirmation message (Casaccia, Fig 9B, paragraph 83, in response to the transmitter receiving the NAK at time t11, the transmitter retransmits the segment at time t12, the retransmission of the segment is interpreted as an acknowledgement to the NAK).
Regarding Claim 30, “S6-200764” teaches a source node in a wireless communication system, the source nod comprising:
a communicator (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, step 1, an Application Server sends a message to a MSGin5G Server that targets an Application Client on a UE, hence the MSGin5G Server has a transceiver to receive this message); and
at least one processor coupled to the communicator and configured to (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 2 the MSGin5G Server compares the size of the received message to the maximum allowed packet size of the access network transport of the targeted UE and detects that the size exceeds the limit, hence the MSGin5G Server has a processor to perform these actions):
receive a message related to an application (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, step 1, an Application Server sends a message to a MSGin5G Server that targets an Application Client on a UE);
identify whether a size of the message related to the application exceeds a maximum allowed packet size (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 2 the MSGin5G Server compares the size of the received message to the maximum allowed packet size of the access network transport of the targeted UE and detects that the size exceeds the limit);
segment the message related to the application into one or more segmented messages based on the maximum allowed packet size (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 2 if the size of the received message exceeds the maximum allowed packet size, then the MSGin5G Sever segments the received message into a set of segmented messages such that each segmented message can fit within an individual access network transport packet);
transmit, to a destination node, the one or more segmented messages (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 3 the MSGin5G Server sends each segmented message to the targeted UE within an individual access network transport packet);
“S6-200764” does not explicitly teach the below limitations:
receive a confirmation message associated with the message related to the application, wherein result information included in the confirmation message is determined based on the one or more segmented messages.
However Casaccia teaches the below limitations:
receive a confirmation message associated with the message related to the application, wherein result information included in the confirmation message is determined based on the one or more segmented messages (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK message is interpreted as being the confirmation message).
It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the invention of “S6-200764” by adding a confirmation message in response to the transmission of a segmented message as taught by Casaccia. Because “S6-200764” and Casaccia teach segmented messaging, and specifically Casaccia teaches a confirmation message in response to the transmission of a segmented message for the benefit of the analogous art of segmented message transmission (Casaccia, abstract).
Regarding Claim 31, “S6-200764” and Casaccia further teach wherein the one or more segmented messages comprise a segmentation set identifier indicating the one or more segmented messages are associated with the message related to the application, and a segment sequence number (“S6-200764”, Table 6.X.1.2-1: Segmentation and Reassembly Information Elements, “Segmentation Set Identifier” identifies all segmented messages associated within the same set of segmented messages, “Segment Sequence Number” refers to an incrementing counter that indicates the sequence number of each segmented message within a set of segmented messages),
wherein a reassembly of the one or more segmented messages is performed based on the segmentation set identifier and the segment sequence number (“S6-200764”, Fig 6.X.1.2-1: MT MSGin5G Message Segmentation and Reassembly, in step 4 the MSGin5G Client receives all the segmented messages and reassembles them into a single MSGin5G message based on the information elements defined in Table 6.X.1.2-1).
.
Regarding Claim 32, “S6-200764” and Casaccia further teach the at least one processor further configured to:
receive a segment recovery request message from the destination node based on at least one missed segmented message among the one or more segmented messages (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK message is interpreted as the confirmation message and the segment recovery request message);
transmit a segment recovery acknowledgement message to the destination node (Casaccia, Fig 9B, paragraph 83, in response to the transmitter receiving the NAK at time t11, the transmitter retransmits the segment at time t12, the retransmission of the segment is interpreted as the segment recovery acknowledgement message); and
transmit the at least one missed segmented message to the destination node (Casaccia, Fig 9B, paragraph 83, in response to the transmitter receiving the NAK at time t11, the transmitter retransmits the segment at time t12).
Regarding Claim 33, “S6-200764” and Casaccia further teach wherein the recovery request message comprises a segmentation set identifier indicating the at least one missed segmented message is associated with the message related to the application, and a list of segment range indicating a segment sequence of the at least one missed segmented message (“S6-200764”, Table 6.X.1.2-1: Segmentation and Reassembly Information Elements, “Segmentation Set Identifier” identifies all segmented messages associated within the same set of segmented messages, “Segment Sequence Number” refers to an incrementing counter that indicates the sequence number of each segmented message within a set of segmented messages, Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, it is interpreted that the identifying of the missing segments of Casaccia is via the identifiers from “S6-200764”).
Regarding Claim 34, “S6-200764” and Casaccia further teach wherein the confirmation message comprises a segmentation set identifier indicating the one or more segmented messages are associated with the message related to the application, and the result information indicating whether a reassembly of the one or more segmented messages is successful (Casaccia, Fig 9B, paragraph 83, the receiver receives the message from time t2 to t3, a NAK message is sent by the receiver from t3 to t4, the NAK message identifies the missing segment of the transmitted message, the NAK message is interpreted as being the confirmation message).
Regarding Claim 35, “S6-200764” and Casaccia further teach further comprising:
transmitting, to the destination node, an acknowledge message related to the confirmation message (Casaccia, Fig 9B, paragraph 83, in response to the transmitter receiving the NAK at time t11, the transmitter retransmits the segment at time t12, the retransmission of the segment is interpreted as an acknowledgement to the NAK).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to THAD N DEFAUW whose telephone number is (571)272-6905. The examiner can normally be reached on Monday-Thursday 8:30 am - 5:00 pm.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Charles Jiang can be reached on (571) 270-7191. 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. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/T.N.D/ Examiner, Art Unit 2412
/CHARLES C JIANG/ Supervisory Patent Examiner, Art Unit 2412