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 Objections
Claim 15 is objected to because of the following informalities:
Claim 15 (see line 3), recites: “geometric assets of the first cene and a third…,” however should recite: “geometric assets of the first scene and a third…,”.
Appropriate correction is required.
Specification
Title of the Invention
The title of the invention is not descriptive. A new title is required that is clearly indicative of the invention to which the claims are directed.
The following title is suggested:
SYSTEMS FOR RENDERING A FIRST SCENE IN A SECOND SCENE GRAPH FORMAT BASED ON CONVERSION UTILIZING A METADATA FRAMEWORK
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1-6 are rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter. The claim(s) does/do not fall within at least one of the four categories of patent eligible subject matter because claim 1 is directed to: “A method for processing immersive media, the method being executed by at least one processor…:,” comprising the steps of: obtaining, receiving, converting and rendering, which are nothing more than software instructions. Software instructions are non-statutory under 35 U.S.C..
Claims 2-6 depend from claim 1 and comprise further steps, for example claim 6 comprises the steps of storing, describing and stores; therefore claims 2-6 have the same problem as claim 1 and are rejected under the same rationale.
Allowable Subject Matter
Claims 7-18 are allowed.
The following is an examiner’s statement of reasons for allowance:
Regarding claim 7, the prior art doesn’t teach:
obtaining code configured to cause the at least one processor to obtain a metadata framework to preserve scene information stored in a scene graph during a process of scene graph translation, the metadata framework comprising a first subsystem that includes metadata information associated with animation of one or more assets in a first scene, wherein the first subsystem comprises animation parameters including one or more of:
data type indicating a type of data that is provided to an animator or renderer;
period indicating a time pattern for an animation;
pattern indicating input/output times or key frames for the animation as an array of time samples; and
end time indicating a time at which the animation stops;
receiving code configured to cause the at least one processor to receive scene graph information of the first scene in a first scene graph format to be converted into a second scene graph format;
converting code configured to cause the at least one processor to convert the first scene into the second scene graph format using the metadata framework; and
rendering code configured to cause the at least one processor to render the first scene in the second scene graph format based on the converting.
Regarding claim 13, the prior art doesn’t teach:
obtain a metadata framework to preserve scene information stored in a scene graph during a process of scene graph translation, the metadata framework comprising a first subsystem that includes information associated with a logical sequence of data in a first scene, parameters of the first subsystem comprising one or more of:
a first binary data container that is used to store various types of data;
a second binary data container comprised of a GL transmission format binary file; and
a third binary data container used in a OpenSubdiv library for storing vertex data during subdivision surface evaluation;
receive scene graph information of the first scene in a first scene graph format to be converted into a second scene graph format;
convert the first scene into the second scene graph format using the metadata framework; and
render the first scene in the second scene graph format based on the converting.
Any comments considered necessary by applicant must be submitted no later than the payment of the issue fee and, to avoid processing delays, should preferably accompany the issue fee. Such submissions should be clearly labeled “Comments on Statement of Reasons for Allowance.”
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
CARMEL (US2006/0122819A1) discloses [0021] In another exemplary embodiment, an NSG provides the mapping between: (1) a graphical scene graph (GSG), such as OpenInventor, OpenGL Optimizer, Performer, and the like, or any other graphical scene graph application program interface (API); and (2) a haptic scene graph (HSG) or an interaction scene graph (ISG). In this second embodiment, the HSG is typically a scene graph of the type used for fast collision detection between virtual objects in a simulated two-dimensional (2D) or three-dimensional (3D) environment. In this embodiment, the NSG is constructed to map the haptic scene graph (HSG) and the graphical scene graph (GSG). There is a transformation in each NSG node that is a function that converts a homogeneous transformation matrix in HSG form into a transformation matrix in the desired GSG form. This transformation is invertible, and the direction of the update is controlled by a flag, indicator, or other control device. In some instances, the transformation may be a unity or identity transformation; WOO (US2005/0234946A1) discloses an apparatus and method for reconstructing 3D graphics data is provided. The apparatus includes a parsing unit to parse 3D graphics data, an aligning unit to align objects of a scene graph having nodes storing geometric information and material information that corresponds to the geometric information included in the 3D graphics data parsed by the parsing unit and hierarchy information regarding the nodes, using predetermined detail information of the material information as a reference, and a rendering unit to interpret the objects of the scene graph aligned by the aligning unit to convert the 3D graphics data into 2D graphics data. Therefore, the present invention can omit the operation of repeatedly storing the same material information by classifying each node of the scene graph according to the material information; JIANG (US2020/0334893A1) discloses a method for implementing virtual scene conversion. The method in the embodiments includes: displaying an initial virtual scene, a first scene conversion trigger set, and partial information of at least one target virtual scene in a screen area, a scene conversion trigger being used for implementing conversion between associated different virtual scenes; determining, in a case that a trigger operation on the first scene conversion trigger is received, the target virtual scene and a second scene conversion trigger set based on the first scene conversion trigger operation in the initial virtual scene, the second scene conversion trigger set including at least one second scene conversion trigger associated with a plurality of determined target virtual scenes; and rendering and displaying the target virtual scene and the second scene conversion trigger set in the screen area. The embodiments of this application are used for improving adaptability of different services and increasing application scenarios; ALLYN (US2018/0189243A1) discloses server-side chart layout for web applications is provided. Output of a server-side layout engine is exposed on the web via a server-side web service and a client-side web player that communicates with the web service. The web player is operative to send chart definitions to the web service, and receive a scene graph of a resultant chart layout. The scene graph includes normalized and annotated information to draw the chart, animate transitions, implement interactivities, and provide standardized accessibility locally within a web client. Aspects enable chart fidelity across native and browser endpoints, and provide faster chart load and render performance that is unaffected by growth of data size or expansions in provided chart features; DING (CN 114119824 A) discloses a method and system for generating three-dimensional scene by multiple three-dimensional format data, the method comprises: constructing a three-dimensional format data automaticconversion engine, the three-dimensional format data automatic conversion engine converts the three-dimensional format data into FBX format data; using the automatic slicing tool to slice the FBXformat data according to the grid and the position, the FBX format data after slicing according tothe position and the slice size to form block data; automatically leading the block data into theUnreal Engine to generate the static grid body by the automatic leading-in tool; using batchautomatic LOD tool, the generated static grid body batch automatic LOD, optimizing scene renderingperformance. The invention realizes the streamlined scene generating tool, the program automaticallygenerates the multiple three-dimensional format data to generate Unreal Engine scene, without manualprocessing, repeatedly using the original data, not needing to re-model, without any other humanresource, It is greatly convenient for the application and upgrading of the digital twinning industry; Berthelot, et al. "Scene graph adapter: an efficient architecture to improve interoperability between 3D formats and 3D applications engines." Proceedings of the 16th International Conference on 3D Web Technology. 2011, discloses a generic architecture which enables the loading of several 3D formats in most 3D application engines. The purpose of this work is to solve the interoperability issue among 3D formats raised by the multiplicity of formats. We propose a programming interface, the Scene Graph Adapter, that allows mixing several 3D formats in a single application without transcoding. The Scene Graph Adapter is composed of two API; a first one that wraps each 3D format and a second one that wraps rendering engines. Wrappers created thanks to these API can be reused in other applications based on the Scene Graph Adapter. The paper introduces our approach and gives an implementation example.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MAURICE L MCDOWELL, JR whose telephone number is (571)270-3707. The examiner can normally be reached Mon-Fri: 2pm-10pm.
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, Said A. Broome can be reached at 571-272-2931. 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.
/MAURICE L. MCDOWELL, JR/Primary Examiner, Art Unit 2612
Prosecution Insights