DETAILED ACTION
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 § 112
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.
Claim 5 is 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.
Regarding claim 5, the phrase “a same” renders the claim(s) indefinite because the claim(s) include(s) elements not actually disclosed (those encompassed by "or the like"), thereby rendering the scope of the claim(s) unascertainable. See MPEP § 2173.05(d).
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 –
Claims 1-4, 7-20 are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Zang et al [US 2025/0291419]
Claim 1. A haptics media file encapsulation method (the encapsulated haptic media file, see Fig. 5, para [0004, 0030, 0047]), the method comprising:
acquiring a haptics media bitstream corresponding to a target haptics media signal (the request haptic media file, bitstream track or media stream format MIHS 64, 71, see Figs. 2-5, para [0024, 0029, 0030, 0047, 0174); and
encapsulating the haptics media bitstream into a haptics media file see Fig. 5, TABLE-US-00007, para [0004, 0047, 0055, 0071, 0096]),
wherein the haptics media file comprises at least two tracks, each track comprising
haptics media data of at least one data type in the haptics media bitstream based on a preset data class and a first metadata of the haptics media data indicating the data type of the haptics media data (the metadata information associated with the perception includes the haptic material attribute as 2D, 3D, and texture arrays of different attributes are combined to form a specific haptic perception, see Fig. 2, TABLE2, TABLE 5, para [0005, 0024, 0032, 0033, 0047, 0065]). The haptic media file, media type and/or haptic metadata includes a plurality of tracks into which the haptic media is encapsulated file, and the index value of the bitstream track is 1, and including the bitstream track is 1, see TABLE 15, para [0071-0073, 0096, 0101, 0135, 0162, 0170]).
Claim 2. The method according to claim 1, wherein the first metadata comprises quantity information of data types and identification information of the data types of the haptics media data in the track (the haptic media files based on media format data types including audio and video types, a media stream identification scheme such as identification marker, see para [0022, 0047, 0051, 0071, 0091, 0173, 0174]).
Claim 3. The method according to claim 2, wherein the preset data class comprises at least one of the following: a perception class and a level class (the perceptual and haptic channel information as main description content in a data structure, while the encoding part 42 focuses on a haptic frequency band, a haptic effect, and a keyframe as main description content in the data structure, such as media type similar to audio, video, a human readable JSON format, MIHS formats 64, 71 and texture format or media type syntax element such as haptic/mp4 and video/mp4 preset value, see TABLE 7, Figs. 4, 5, para [0024, 0027-0030, 0037, 0051, 0163-0165, 0247, 0248]),
a channel class (the haptic channel perception and channel-level, see Figs. 2, 3, para [0024, 0025]), and
a priority class (the first-order media type similar to audio and video, see para [0027, 0248], and TABLE 8 Syntax element Data name type Description triggers Array Includes definitions of all triggers used in the 3D scene. Actions Array includes definitions of all actions used in the 3D scene. Behaviors Array Includes definitions of all behaviors used in the scene. One behavior consists of a control parameter, a priority weight, and an optional interrupt action that are of a paired trigger and action. Table 8 only lists partial content related to support for the haptic media, and the MPEG interactivity description module (MPEG interactivity) 902 may also include other first-level syntax elements. (See TABLE 8, para [0057, 0085-0087, 0092]).
Claim 4. The method according to claim 3, wherein when the preset data class is the perception class, the first metadata further comprises attribute information of a perception type of the haptics media data in the track (as cited in respect to claims 1 and 3 above, and wherein the metadata information associated with the perception includes the haptic material attribute as 2D, 3D, and texture arrays of different attributes are combined to form a specific haptic perception, see Fig. 2, TABLE2, TABLE 5, para [0005, 0024, 0032, 0033, 0047, 0065]).
Claim 7. The method according to claim 1, wherein the first metadata comprises indication information of the preset data class (as cited in respect to claims 1 and 3 above, wherein the haptic media file, haptic channel and/or media stream includes some advanced metadata, see para [0024]), and
the first metadata is stored in a data box corresponding to a track-level sample entry of the track (read upon the MPEG haptic 801 may index the accessor description module in an accessor list of the scene description document to obtain description information of an accessor for accessing rendering data that is of the haptic media file and stored in the buffer (as box). (see Fig. 6, para [0031]). When the track array (buffer.MPEG buffer circular tracks) of the MPEG circular buffer of the buffer description module includes a plurality of tracks, the pipeline should perform necessary processing on all referenced tracks to generate a data format requested by the buffer description module. If a media file referenced in the track (buffer.MPEG buffer circular tracks) in the track array of the MPEG circular buffer of the buffer description module has a plurality of alternative versions (alternatives), each alternative version (alternatives) should record a selection status of the track. (See TABLE 7, Fig. 2, 7, para [0052-0055, 0071-0073, 0096]).
Claim 8. The method according to claim 1, wherein the first metadata is stored in a data box corresponding to a data-type-level sample entry of the track, and the data box corresponding to the data-type-level sample entry comprises indication information of the preset data class. (As cited in respect to claims 1, 3 and 7 above, and wherein the haptic media file/class audio data and video data such as haptic/mp4 and video/mp4 , haptic value and/or preset value indicating on the display engine 11, see Fig. 1, para [0020, 0021, 0045, 0047, 0086, 0163-0165]).
Claim 9. The method according to claim 1, wherein the track comprises at least one target sample group, and each target sample group comprises one target sample or a plurality of consecutive target samples in the track (the target haptic object description module from a moving picture experts group (MPEG) haptic description module in the scene description document according to the index value of the target haptic object description module (see abstract). In order to facilitate delivery of the scene description document to the client, the ISO/IEC 23090-14 defines how to encapsulate a glTF file and related data in the ISOBMFF file as non-time-varying data and time-varying data, for example, as a track sample. (See para [0021]). In some embodiment, the animation description module (animation) 917 may describe, through at least one of position movement, angle rotation, and size scaling, the animation added to the node. (See Fig. 7, para [0049, 0076-0079]).
Claim 10. The method according to claim 9, wherein the target sample does not comprise haptics media data (read upon the target haptic object MPEG media allows referencing an external media stream transmitted through protocols such as the RTP/Secure Real-time Transport Protocol (SRTP) and MPEG-DASH. In order to address a media stream without knowing an actual protocol scheme, a host name, or a port value, the ISO/IEC 23090-14 defines a new URL scheme (see abstract, para [0022]).
Claim 11. The method according to claim 1, wherein the haptics media file further comprises a metadata track, the metadata track comprises a second metadata of the haptics media bitstream (as cited in respect to claim 1 above, and wherein the haptic media file based on a second haptic object description module, see para [0085, 0087]), and
the second metadata indicates encoding information of the haptics media bitstream (as cited in respect to claim 1 above, and wherein the haptic data model includes encoding part 42 and haptic signal encoder 600 see Figs. 2-5, para [0024, 0027-0030]).
Claim 12. The method according to claim 1, wherein the track further comprises a second metadata of the haptics media bitstream, and the second metadata indicates encoding information of the haptics media bitstream (as cited in respect to claim 1 above, and wherein the second haptic object array or second metadata, see para [0087]).
Claim 13. An electronic device, comprising a memory and a processor (see para [0006]), the memory having a computer program stored therein; and the processor, when executing the computer program (see para [0006, 0007]), causing the electronic device to implement a haptics media file encapsulation method including: acquiring a haptics media bitstream corresponding to a target haptics media signal; and encapsulating the haptics media bitstream into a haptics media file, wherein the haptics media file comprises at least two tracks, each track comprising haptics media data of at least one data type in the haptics media bitstream based on a preset data class and first metadata of the haptics media data indicating the data type of the haptics media data (as cited in respect to claim 1 above).
Claim 14. The electronic device according to claim 13, wherein the first metadata comprises quantity information of data types and identification information of the data types of the haptics media data in the track (as cited in respect to claim 2 above).
Claim 15. The electronic device according to claim 13, wherein the first metadata is stored in a data box corresponding to a track-level sample entry of the track, and the first metadata comprises indication information of the preset data class (as cited in respect to claim 7 above).
Claim 16. The electronic device according to claim 13, wherein the first metadata is stored in a data box corresponding to a data-type-level sample entry of the track, and the data box corresponding to the data-type-level sample entry comprises indication information of the preset data class (as cited in respect to claim 8 above).
Claim 17. The electronic device according to claim 13, wherein the track comprises at least one target sample group, and each target sample group comprises one target sample or a plurality of consecutive target samples in the track (as cited in respect to claim 9 above).
Claim 18. The electronic device according to claim 13, wherein the haptics media file further comprises a metadata track, the metadata track comprises second metadata of the haptics media bitstream, and the second metadata indicates encoding information of the haptics media bitstream (as cited in respect to claim 11 above).
Claim 19. The electronic device according to claim 13, wherein the track further comprises second metadata of the haptics media bitstream, and the second metadata indicates encoding information of the haptics media bitstream (as cited in respect to claim 12 above).
Claim 20. A non-transitory computer-readable storage medium, having a computer program stored therein, the computer program, when executed by a processor of a computer device (see para [0009]), causing the computer device to implement a haptics media file encapsulation method including:
acquiring a haptics media bitstream corresponding to a target haptics media signal; and
encapsulating the haptics media bitstream into a haptics media file, wherein the haptics media file comprises at least two tracks, each track comprising haptics media data of at least one data type in the haptics media bitstream based on a preset data class and first metadata of the haptics media data indicating the data type of the haptics media data (as cited in respect to claim 1 above).
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 5, 6 are rejected under 35 U.S.C. 103 as being unpatentable over Zang et al [US 2025/0291419] in view of Hirabayyashi et al [US 2025/0260839].
Claim 5. The method according to claim 3, wherein when the preset data class is the channel class, the first metadata further comprises channel group flag information of the haptics media data in the track (as cited in respect to claims 1 and 3 above). But
Zang et al fails to disclose the channel group flag information indicates whether the haptics media data belongs to a same channel group. However,
Zang et al teaches that in order to enable the scene description document to correctly describe relevant haptic information in the 3D scene, some embodiments of the present disclosure independently extend the MPEG interactivity description module (MPEG interactivity) 902 in the scene description document. The MPEG interactivity description module (MPEG interactivity) 902 is configured to describe interaction describe interaction triggering, an interaction action, and a correlation between the interaction triggering and the interaction action. First-level syntax elements in the MPEG interactivity description module (MPEG interactivity) 902 are defined in following Table 8. (See para [0056, 0057]).
Hirabayashi et al suggests that in the first information processing device, the generation unit may store the flag information for identifying that the medium associated with the 3D data is the interaction type medium in the distribution file as information defining the interaction type medium (see Fig. 50, para [0272]). Then, in the second information processing device, the extraction unit may extract the coded data of the interaction type medium associated with the 3D data on the basis of the flag information (see Fig. 50, para [0273]). It is possible for the second information processing device to easily grasp whether or not the medium associated with the 3D data is the interaction type medium by referring to the Flags. Thus, the second information processing device can extract the coded data of the interaction type medium associated with the 3D data from the distribution file on the basis of information of the Flags. Thus, the interaction type medium can be correctly distributed as the interaction type medium. That is, it is possible to suppress a reduction in distribution performance for media data associated with 3D data (see Figs. 21, 32, 51, para [0276]).
Therefore, it would have been obvious to one skill in the art before the effective filing date of the invention to implement or substitute the whether or not the haptics medium associated with the 3D data is the correct interaction type medium by referring to the flags of Hirabayashi et al to the MPEG interactivity description module in the scene description document of the haptic information in 3D scene of Zang et al for providing accuracy and reliable of haptic information type, since the analogous art is not limit to references in the field of endeavor of the invention as the haptic media purpose.
Claim 6. The method according to claim 5, wherein the channel class further indicates a perception type of the haptics media data in the track, and the first metadata further comprises identification information of the perception type and attribute information of the perception type of the haptics media data in the track (as cited in respect to claims 1 and 2 above, wherein the media stream identification including an identification marker of 3D scene, see para [0022, 0091]).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
Zhang et al discloses the media file processing method determining a grayscale map track and haptic signal tracks corresponding to video data, wherein the grayscale map track includes a grayscale map corresponding to each frame in the video data, the grayscale map corresponding to each frame is used for characterizing a position distribution of a haptic region corresponding to each frame, and each haptic signal track includes a haptic signal corresponding to each haptic region in the video data; generating a first mapping table according to each grayscale value in the grayscale map tracks and the haptic signal tracks; encapsulating the first mapping table, the grayscale map track, the haptic signal tracks, and the video data to obtain a target media file.
[US 2026/0259610]
Any inquiry concerning this communication or earlier communications from number is (571) 272-2972. The examiner can normally be reached on Mon-Fri from 8:00 AM to 3:00 PM. If attempts to reach the examiner by telephone are unsuccessful, the examiner's supervisor, Mr. Wang Quan-Zhen can be reached on (571) 272-3114.
Examiner interviews are available via telephone, 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.
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.
/VAN T TRIEU/
Primary Examiner, Art Unit 2685
09/10/2026
Prosecution Insights