Key information

Title
DISPLAY AND EDITING PERSONALIZABLE VIDEO
Application number
20250224
Case type
National
Status
Filed
26.02.2025
Effective date
26.02.2025
Publicly available
27.08.2026
Next annual fee due
28.02.2027
Applicant
SEEN AS (NO)
Inventor
Serhii Palii (NO) et al.
Agent
ACAPO ONSAGERS AS (NO)

Abstract and drawing


Disclaimer: This text has been machine-scanned and may contain errors – please refer to "Publications" for legally binding content.
The present disclosure provides computer-implemented methods and systems relating to displaying personalized video to a user. In a first aspect, a method includes accessing, by a computing device associated with the user, a template file stored at a remote storage location, wherein the template file corresponds to an animated scene that includes a personalizable data object, determining data associated with the user for updating the personalizable data object from a location indicated by the template file, rendering the animated scene using a rendering engine operating on the computing device, wherein the rendering engine uses the template file to render the animated scene with the personalizable data object updated using the data associated with the user and outputs the rendered animated scene as video data, and displaying the video data on a display of the computing device.

Publications


A1
Checking availability of the latest published version...

Documents


Expand Download files (34)
Date
Date Doc. No. Process Case number In/Out Journal description To/from
02.06.2026 14-08 Saksbehandling 20250224 INN 20250244 Norwegian claims ACAPO ONSAGERS AS
02.06.2026 14-07 Saksbehandling 20250224 INN 20250244 Letter to NIPO re to office action ACAPO ONSAGERS AS
02.06.2026 14-06 Saksbehandling 20250224 INN 20250244 Letter to NIPO Request for postponement of grant ACAPO ONSAGERS AS
02.06.2026 14-05 Saksbehandling 20250224 INN 20250244 Amended description marked copy ACAPO ONSAGERS AS
02.06.2026 14-04 Saksbehandling 20250224 INN 20250244 Amended description clean copy ACAPO ONSAGERS AS
02.06.2026 14-03 Saksbehandling 20250224 INN 20250244 Amended claims marked copy ACAPO ONSAGERS AS
02.06.2026 14-02 Saksbehandling 20250224 INN 20250244 Amended claims clean copy ACAPO ONSAGERS AS
02.06.2026 14-01 Saksbehandling 20250224 INN Korrespondanse (Hovedbrev inn) ACAPO ONSAGERS AS
14.03.2026 13-01 Saksbehandling 20250224 UT Substantive examination ACAPO ONSAGERS AS
02.03.2026 12-01 Saksbehandling 20250224 UT Generelt brev uten frist NO ACAPO ONSAGERS AS
26.02.2026 11-02 Saksbehandling 20250224 INN P31570NO00 Enquiry about next communication ACAPO ONSAGERS AS
26.02.2026 11-01 Saksbehandling 20250224 INN Korrespondanse (Hovedbrev inn) ACAPO ONSAGERS AS
25.02.2026 10-02 Saksbehandling 20250224 INN P31570NO00 Rettelse av oppfinners adresse ACAPO ONSAGERS AS
25.02.2026 10-01 Saksbehandling 20250224 INN Korrespondanse (Hovedbrev inn) ACAPO ONSAGERS AS
14.11.2025 08-06 Saksbehandling 20250224 INN P31570NO00 Reply to Official Actoin ACAPO ONSAGERS AS
14.11.2025 08-05 Saksbehandling 20250224 INN P31570NO00 - amended description - marked-up ACAPO ONSAGERS AS
14.11.2025 08-04 Saksbehandling 20250224 INN P31570NO00 - amended description - clean ACAPO ONSAGERS AS
14.11.2025 08-03 Saksbehandling 20250224 INN P31570NO00 - amended claims - marked-up ACAPO ONSAGERS AS
14.11.2025 08-02 Saksbehandling 20250224 INN P31570NO00 - amended claims - clean ACAPO ONSAGERS AS
14.11.2025 08-01 Saksbehandling 20250224 INN Korrespondanse (Hovedbrev inn) ACAPO ONSAGERS AS
23.06.2025 07-02 Saksbehandling 20250224 UT PT report 09:00:21
23.06.2025 07-01 Saksbehandling 20250224 UT Substantive Examination ACAPO ONSAGERS AS
16.04.2025 05-01 Saksbehandling 20250224 UT Generelt brev uten frist NO ACAPO ONSAGERS AS
14.04.2025 06-02 Saksbehandling 20250224 INN PDF_676309305 ACAPO ONSAGERS AS
14.04.2025 06-01 Saksbehandling 20250224 INN Korrespondanse (Hovedbrev inn) ACAPO ONSAGERS AS
13.03.2025 04-03 Saksbehandling 20250224 INN P31570NO00 Declaration, signed ACAPO ONSAGERS AS
13.03.2025 04-02 Saksbehandling 20250224 INN NO General power of attorney, Seen AS ACAPO ONSAGERS AS
13.03.2025 04-01 Saksbehandling 20250224 INN Korrespondanse (Hovedbrev inn) ACAPO ONSAGERS AS
28.02.2025 03-01 Saksbehandling 20250224 UT Formal Examination 1 ACAPO ONSAGERS AS
28.02.2025 02-01 Saksbehandling 20250224 UT Informasjon til oppfinner Dragoș-Paul Marinescu
26.02.2025 01-03 Saksbehandling 20250224 INN P31570NO00 Patent specification ACAPO ONSAGERS AS
26.02.2025 01-02 Saksbehandling 20250224 INN P31570NO00 Drawings ACAPO ONSAGERS AS
26.02.2025 01-01 Saksbehandling 20250224 INN Søknadsskjema Patent ACAPO ONSAGERS AS
09-02 Saksbehandling 20250224 INN Korrespondanse (Hovedbrev inn) ACAPO ONSAGERS AS

Description, claims and drawings


Disclaimer: This text has been machine-scanned and may contain errors – please refer to "Publications" for legally binding content. Description
DISPLAY AND EDITING PERSONALIZABLE VIDEOTECHNICAL FIELD[1] The present disclosure relates to computer-implemented methods, systems, and computer readable media for displaying personalized video to a user and for editing personalized video for display to a user.BACKGROUND[2] Until recently, media content has been impersonal. TV, radio, newspapers, magazines were all made for a mass market. Email and online networks provided increased possibilities for tailoring content to individuals, but this was often limited to text data or, at most, simple imagery. Recently, with improved computation and machine processes, it has been possible to personalize video content, and various industries have begun to adopt such customization, including marketing, entertainment, education, and customer service.[3] Personalized video is commonly created by using remote servers to render the content en masse before delivering the video to the end user devices across the internet. Such an approach presents several challenges. First, it requires significant computational resources on the server side to generate and process individual videos for each user. This can lead to scalability issues when dealing with large numbers of users or complex video content. Second, the process of rendering and delivering personalized videos from servers can introduce latency, potentially impacting the user experience, especially in scenarios where real-time or near-real-time personalization is desired.[4] These challenges have been partially addressed by making use of on-demand server-side rendering. When a user desires to watch a video including personalizable content, the server begins rendering and streams the content while the rendering process is still in progress, usually using widely-adopted web streaming technologies such as HTTP Live Streaming (HLS) or Dynamic Adaptive Streaming over HTTP (DASH). This may reduce waiting times, but does not address computational resource use and in fact may make the situation worse, especially where demand is high.[5] These challenges may impact the end users, the content creators, and the content owners. Further challenges may also prevent themselves that impact these groups, including high, prohibitive costs associated with generating personalized video, privacy and security concerns around the transfer of potentially sensitive information, and a lack of flexibility in designing personalized video.[6] Accordingly, there is a need for improved generation and display of personalized video.SUMMARY[7] According to a first aspect, there is provided a computer-implemented method for displaying personalized video to a user. The method comprises: accessing, by a computing device associated with the user, a template file stored at a remote storage location, wherein the template file corresponds to an animated scene that includes a personalizable data object; determining, by the computing device, data associated with the user for updating the personalizable data object from a location indicated by the template file; rendering the animated scene using a rendering engine operating on the computing device, wherein the rendering engine uses the template file to render the animated scene with the personalizable data object updated using the data associated with the user and outputs the rendered animated scene as video data; and displaying the video data on a display of the computing device.[8] By performing the method, personalized video is displayed for viewing by the user on the display of the computing device. Personalization of video content is desirable to enable a tailored experience to be provided to a user in many different settings. Personalized video may be beneficial when used in marketing and advertising, such as to directly refer to the user during a video, e-commerce such as to generate product demonstrations or recommendations, education and training to adapt learning materials to the user, entertainment such as for improving a user experience during viewing of film or tv content, or during gameplay, such as during mobile games whether they are offline or online, social media for personalizing communications between users or year-in-review content, customer services such as for automated query responses or for onboarding, human resources processes such as onboarding, other onboarding circumstances such as during a customer journey, and during travel, such as on flights, in manual, semi-autonomous, or autonomous road or other vehicles, or during simulated travel. In some examples, personalized video and the techniques described herein may be used to enable users to view video content in different languages, dialects, or tones. There are many other uses of personalized video and the uses of personalized video herein are not limited to those described above.[9] As used herein, the term "personalized video" may refer to video content that is customized or tailored for a specific user. Personalized video may incorporate userspecific data, preferences, or characteristics to create a tailored viewing experience. This may include, but is not limited to, inserting user-specific images, text, video or other content into the video, adapting the video's narrative or visual style based on user preferences, or modifying elements of the video to reflect user-specific information, context, or real-time information that is relevant to the user. For example, the user’s name, location, interests, or other personal information may be incorporated into the video. The video may be personalized by including personalized audio that accompanies the imagery in the video.[10] The video data described herein incorporates the personalization. In other words, the data used for personalization is integrated or embedded within the video, so that the video is itself personalized, rather than displaying a generic video with personalization laid over or superimposed over the generic video. By incorporating the personalization into the video data, a much wider range of effects and personalization is possible, and the user experience is improved to a greater extent. In particular, the content displayed to the user is more convincing and may be considered more cinematic or more engaging because of that.[11] In the method described above and the methods described herein more generally, video data for the personalized video is rendered on the computing device associated with the user. Accordingly, the computational resources of the computing device are used for the rendering and the rendering is therefore performed locally rather than at a remote server. By performing rendering locally, the requirement for large amounts of rendering and processing to be performed by remote servers is reduced.[12] Reducing server-side processing requirements may offer several advantages in the context of personalized video content delivery. For example, rendering at client devices enables improved scalability. Where large amounts of video data is to be delivered, other systems that utilize server-side rendering may have limited amounts of computation to use, and may therefore be restricted in how much data can concurrently be rendered. By handing this task off to client devices, the number of devices that can concurrently render devices is increased without requiring proportional increases in server capacity. Furthermore, storage requirements may be lessened as there is less need to store large amounts of personalized video data. Power requirements for servers may also be lessened, and network loads can also be reduced. In turn, these improvements may also result in greater cost-effectiveness.[13] Further advantages associated with performing rendering at the computing device associated with the user may include reduced latency, as sending template files rather than complete rendered video files reduces the amount of data being transferred, improved offline capabilities, as the data can be received in advance and used to render when desired, improved privacy and security of data because sensitive information may not be being transmitted across networks remote from the user and/or may not be stored remotely from the user (i.e. in a country having different privacy requirements and thereby contravening one or more privacy laws such as GDPR), and the ability to optimize the video for specific devices. Each of these may lead to improvements in the user’s experience. In some examples, client-side rendering may result in fewer round trips being placed to servers, further reducing latency.[14] The user may be an end user of the computing device. The personalized video may be personalized to the user. The user may be associated with the computing device by being an owner of the computing device. The user may be associated with the computing device by being logged in to a profile corresponding to the user on the computing device or by data relating to the user being stored by the computing device. The user may be associated with the computing device by the user viewing a display of the computing device or by the user being proximal to the display of the computing device. For example, the computing device may comprise an advertising display and the user may be viewing the advertising display and/or may be within a predetermined proximity to the advertising display.[15] The method is implemented at or by a computing device. The computing device may be referred to as a client device, an end-user device, or a local computing device. The computing device may be a mobile device, such as a mobile phone, a tablet computer, or a laptop computer of the user. The computing device may be a static computer. The computing device may comprise a system within a particular location, such as a processor and screen used for displaying advertisements or other features to a user. The computing device may comprise part of all of internal hardware of a wider device, such as an autonomous vehicle. [16] The computing device may be referred to as a first computing device and may form part of a wider system comprising a plurality of computing devices. In such an example, the steps of the method may be performed by multiple computing devices associated with different users. The first computing device may determine first data and may output first video data. Accordingly, the method may comprise, accessing, by a further computing device associated with a further user, the template file stored at the remote storage location; determining, by the further computing device, further data associated with the further computing device for updating the personalizable data object from the location indicated by the template file; rendering the animated scene using the rendering engine operating on the further computing device, wherein the rendering engine uses the template file to render the animated scene with the personalizable data object updated using the further data associated with the further computing device and outputs the rendered animated scene as further video data; and displaying the further video data on a display of the further computing device. In such an example, both computing devices utilize the same template file and rendering engine in order to render the video, but the data used for personalization is different, and therefore the video data is different on each device. As a result, each user gets a different experience that is personalized to them, but the processing is performed locally at each computing device.[17] The template file may be a structured data file that contains information and instructions for creating the animated scene. The template file may include various elements such as scene layout and composition data, placeholders for personalizable data objects, animation parameters and timelines, references to data assets such as images, textures, or 3D models, scripting or logic for dynamic content generation, metadata about the scene, such as duration, resolution, or frame rate, scene graphs, and/or instructions for integrating personalized data into the scene. The template file may also contain information about how to retrieve data for updating the personalizable data objects, such as specifying API endpoints or local storage locations from which personalized data is to be retrieved.[18] The template file may have a format that can be parsed and interpreted by the rendering engine. The format may be a data interchange format. The format may be or may be based on XML, JSON, or a custom binary format optimized for efficient processing. [19] The use of template files may allow for separation of the scene structure from the personalized content, enabling efficient updates and modifications to the animated scene without altering the core rendering logic as well as providing an efficient way for communicating data to the computing device for rendering. This approach may facilitate the creation of diverse personalized video content while maintaining a consistent rendering process across different scenes and personalizations. The template file may have a small file size, which may also be useful for use with mobile computing devices or those that have limited memory capacities.[20] The template file may be accessed by the computing device by the computing device making an API call to the remote storage location. The computing device may be sent data indicating a template file to retrieve from the remote storage location. For example, the computing device may download an application from the remote storage and the application may include the template file. Alternatively, the computing device may be served a webpage within a browser application or may access a page in a downloaded application and data associated with the accessed page may indicate where the template file is to be retrieved from or may indicate the template file.[21] As used herein, the term "remote storage location" refers to any data storage system or service that is physically separate from the computing device accessing the stored data and is accessible via a network connection. This may include, but is not limited to, cloud-based storage services, networked file servers, content delivery networks, or any other storage system that can be accessed remotely over a network infrastructure such as the internet, local area networks, or wide area networks. The computing device may communicate with or access data from the remote storage location over a wide area network such as the internet. The remote storage location may also be a combination of multiple storage systems or services working together to provide distributed and redundant storage capabilities.[22] An animated scene may refer to a visual representation of a sequence of images or frames that, when displayed in rapid succession, create the illusion of motion and change over time. In the context of the techniques described herein, an animated scene may include various visual elements such as characters, objects, backgrounds, and effects that can be manipulated and rendered to produce dynamic, moving content. The animated scene may be composed of multiple layers, each containing different elements that can be independently animated or modified. These layers may include vector graphics, raster images, 3D models, particle systems, video objects, or other visual components that contribute to the overall composition of the scene.[23] In some implementations, the animated scene may incorporate keyframe animation techniques, where key points in the animation are defined and intermediate frames are automatically generated to create smooth transitions between these points. The scene may also utilize procedural animation, where movement and changes are generated algorithmically based on predefined rules or parameters.[24] In the context of the methods described herein, the animated scene includes a personalizable data object and may include more than one personalizable data object. The personalizable data object may be dynamically updated with user-specific information. As used herein, the term "personalizable data object" refers to a component or element within the animated scene that can be dynamically modified or updated with user-specific information or data. The personalizable data object may include, but is not limited to a text element, an image placeholder, a video placeholder, a color scheme, a model or character, a graphical element such as a chart or graph, an animated sequence, or a background.[25] Data associated with the user may include personal information, preferences, or behavioral data. This may encompass user profile details, account information, browsing history, purchase history, or social media activity. User-associated data may be stored locally on the device, retrieved from a remote server, or collected through user input. In some cases, the data may be a combination of multiple types, allowing for more sophisticated and nuanced personalization of the video content. The specific data used may depend on the nature of the personalized video, user permissions, and the capabilities of the computing device. The data associated with the computing device may comprise at least one of: image data, text data, shape data, or video data.[26] As used herein, the term "rendering" may refer to the process of generating video data from a set of input data, instructions, or models that includes the template file and data associated with the user. Rendering may involve transforming abstract descriptions of scenes, objects, or visual elements into concrete visual content that can be displayed on a screen or other output device. This process may include calculations for lighting, shading, texturing, and other visual properties to create a final image or frame.[27] As used herein, the term "rendering engine" may refer to a software component or system designed to process and generate visual content from input data or instructions. A rendering engine may be responsible for interpreting and executing instructions to create visual output, such as images, animations, or video frames. The rendering engine may support 3D graphics rendering. It may incorporate various rendering techniques such as rasterization, ray tracing, or real-time global illumination to produce high-quality visual output. The rendering engine may also include features for handling animations, particle systems, physics simulations, or other dynamic elements that contribute to the final rendered scene. In some implementations, it may support shader programming to allow for custom visual effects and optimizations.[28] The video data output from the rendering engine may comprise a complete video or may comprise part of a video. At least some of the video data may be output while other video data is being displayed on the display. In other words, a stream of video data may be output from the rendering engine and displayed as it is output. The output video data may be cached in a local cache of the computing device or buffered in a buffer of the computing device prior to display.[29] The method may further include rendering the animated scene, at least in part, at a graphics processing unit of the computing device. The animated scene may be rendered using both a central processing unit and the graphics processing unit of the computing device.[30] Utilizing the graphics processing unit of the user's device allows for efficient rendering of complex animated scenes, enabling high-quality personalized video content to be generated in real-time.[31] The animated scene may include at least one three-dimensional effect. The three-dimensional effect may be applied to an object, to create a three-dimensional object. The three-dimensional effect may be an effect between two or more objects. A three-dimensional effect may refer to a visual technique that creates the illusion of depth and dimensionality in a two-dimensional image or animation. This may include techniques such as perspective rendering, shading, lighting, texturing, parallax effects, or stereoscopic imaging to simulate the appearance of objects existing in a threedimensional space.[32] The three-dimensional effect may be applied to the personalizable data object. Thus, the personalizable data object may be a three-dimensional element within the scene. The three-dimensional effect may be visible once rendered a personalized video. [33] The animated scene may be a three-dimensional animated scene. The animated scene may comprise a plurality of three-dimensional elements or objects and may be referred to as a three-dimensional model. The three-dimensional model may include a three-dimensional camera from which perspective the eventual video data is rendered.[34] The rendering engine may be a three-dimensional rendering engine. The rendering engine may be configured to render a three-dimensional scene or model to create a two-dimensional video. The rendering engine may be configured to utilize a scene graph or other data to ensure that the three-dimensional scene or model acts or moves in the appropriate way.[35] The animated scene may be rendered at run-time. Expressed another way, video data is output in real-time as an application or program within which the video data is to be displayed is executing and/or in response to user input. The rendering may be performed dynamically in response to receiving user input at the computing device. The rendering may be performed in response to a trigger, such as the user providing data associated with the user or by the user selecting a particular option on a webpage. The trigger may be a change in real-time data. This approach allows for greater flexibility and responsiveness compared to pre-rendered content. Such an approach may also avoid unnecessary computation and reduce the amount of data that is pre-stored. Rendering may also be performed in response to computational resource use at the computing device, further enhancing flexibility.[36] Displaying the video data may comprise displaying the video data in series with one or more further blocks of video data. The one or more further blocks of video data and the output video data may together form a full personalized video. The one or more further blocks of video data may be video data that has been rendered according to the steps of the method or may be video data retrieved from elsewhere that are not personalized. Accordingly, the video data rendered and displayed using the methods described above may be restricted to video data including personalizable data objects, while other video data can be streamed from a remote storage location. Breaking the video into blocks in this way optimizes the use of the computing device’s resources. The template file may include details of the other blocks of video data to be displayed, so that these can be retrieved and displayed with the video data output from the rendering engine. [37] The template file may correspond to more than one animated scene, and therefore to more than one block of video data. The rendering engine may be configured to render the blocks of video data independently and to include different data associated with the user. Accordingly, the rendering engine may render first video data and second video data based on the same template file.[38] The method may further comprise accessing, by the computing device, at least one data asset indicated by the template file, wherein the rendering engine renders the animated scene by integrating the data associated with the user with the at least one data asset. The at least one data asset may comprise at least one of video data or image data. Integrating the data associated with the user with the at least one data asset may comprise making the data associated with the user appear as though it is part of the data asset to the user. The integration may comprise editing a texture, movement, size, or other feature of the data to match or be similar to that of the data asset. Integrating the data associated with the user with the at least one data asset may comprise providing a three-dimensional effect within the animated scene that is applied to both the data and the data asset.[39] The data associated with the user may comprise at least one of: image data, text data, shape data, or video data.[40] The rendering engine may be a web application. Where the rendering engine is a web application, the method may further comprise: requesting, by the computing device, access to a web resource from a remote server that includes the animated scene; and receiving, by the computing device from the remote server, the web resource, the template file, and the rendering engine. Web applications enable efficient implementation of the rendering engine without the need for plug-ins or specialist software to be downloaded to the computing device. The rendering engine may be able to be used on the computing device without using plug-ins or installing specific software[41] The rendering engine may be a web assembly. The web assembly or web application may use a graphics API. For example, the web assembly or application may use a WebGL graphics API or a WebGPU graphics API. Such web assemblies may be able to make use of the graphics processing unit of the computing device, thereby enabling improved performance and real-time interaction.[42] The rendering engine may be compiled to a web assembly using a compiler. The rendering engine may have interfaces for interaction between the computing device and the rendering engine. Such interfaces may be achieved using bindings such as Emscripten bindings. Interfaces may be linked to functions associated with the rendering engine, such as viewing functions which may include a play function, a pause function, a rewind or fast forward function, a next video function, or editing functions, which may include functions for moving or editing objects or elements of the animated scene. When called, interfaces of the rendering engine may enable the functions to be utilized by the computing device. Different interfaces may be called depending on the user or the computing device. For example, an editing user may access the rendering engine and have editing functions called by the rendering engine to enable editing of the animated scene, while a viewing user may have viewing functions but not editing functions enabled.[43] The web application may operate in a browser application on the computing device. Alternatively, the web application may form part of a software application installed on the computing device.[44] The web resource may be a webpage or a software application. Requesting access to the webpage may comprise attempting to navigate to the webpage using a URL. Requesting access to the software application may comprise requesting to download the software application from an app store or via a webpage. The software application may be different to the rendering engine.[45] Determining the data associated with the user may comprise at least one of: receiving input from the user at the computing device that comprises the data associated with the user; retrieving the data associated with the user from a local memory location of the computing device that is associated with the web resource; retrieving the data associated with the user from a remote storage location associated with the web resource via a network connection; or determining the data associated with the user from a URL entered into a browser application at the computing device.[46] The web application may implement the rendering engine as a virtual machine. The web application may make use of memory and/or computational resources associated with the application in which the web application operates. Utilizing a virtual machine and/or making use of resources of the browser or software application avoids creating data that would occupy resources after the video has been displayed and the application closed.[47] The rendering engine may have one or more functions for allowing the animated scene to be edited, and the one or more functions may be enabled or disabled dependent on a user of the computing device. Such a rendering engine may allow different levels of user interaction and content creation, supporting both viewing and editing use cases using the same rendering engine. This may allow for an editing user to render an animated scene in real time while editing, so that what will be seen by the end user can also be viewed during editing.[48] The computing device may be a first computing device, and the method may further comprise, before accessing the template file with the first computing device: accessing, by a second computing device associated with an editing user, the template file; rendering the animated scene using the rendering engine operating on the second computing device, wherein the rendering engine uses the template file to render the animated scene with the personalizable data object updated using predetermined data and outputs the rendered animated scene as video data; and displaying the video data on a display of the second computing device. Rendering the same animated scene at two different computing devices for different purposes may improve the editing and viewing experiences. Implementing the rendering engine in both devices may enable a straightforward and efficient process, as well as ensuring that what is rendered subsequently is accurate to what was intended. Furthermore, as the rendering engine operates at the computing devices and rendering is performed locally, the rendering during editing may be performed more quickly and efficiently than previously possible as there is less need for round trips with servers.[49] The template file may be stored in local storage at the second computing device. This may further enhance the process, enabling fast access to the animated scene and quick rendering.[50] The method may further comprise, before accessing the template file with the first computing device: receiving input relating to an update to the animated scene at the second computing device; updating, by the second computing device, the template file in the local storage to reflect the update to the animated scene; in response to the template file being updated: re-rendering the animated scene using the rendering engine using the updated template file; and displaying the video data on a display of the first computing device; and storing the updated template file at the remote storage location for accessing by the first computing device.[51] According to a second aspect, there is provided a computer-implemented method for editing a personalizable animated scene. The method comprises: storing, by a first computing device associated with an editing user, a template file in local storage of the first computing device, wherein the template file corresponds to an animated scene that includes a personalizable data object; receiving input relating to an update to the animated scene at the first computing device; updating, by the first computing device, the template file in the local storage to reflect the update to the animated scene; in response to the template file being updated: rendering the animated scene using a rendering engine operating on the first computing device, wherein the rendering engine uses the updated template file to render the animated scene with the personalizable data object updated using predetermined data and outputs the rendered animated scene as video data; and displaying the video data on a display of the first computing device; and storing the updated template file at a remote storage location for accessing by a second computing device associated with a viewing user, wherein the second computing device is configured to use the rendering engine to render the animated scene with the personalizable data object updated using data associated with the viewing user.[52] This method enables real-time editing and preview of personalizable animated scenes, allowing content creators to efficiently design and update templates for personalized video content. The ability to immediately render and view changes using the same rendering engine that will be used by end-users ensures consistency between the editing and viewing experiences.[53] The above method of the second aspect may include features associated with the first aspect described above. At least some of the steps of the second aspect may be combined with the first aspect. The first aspect may also include features of the second aspect.[54] The local storage in which the template file is stored may be local memory of the first computing device, and may comprise a cache or buffer of the first computing device. The local storage may be a memory location associated with a browser application of the first computing device.[55] The template file may comprise an existing template file or a new template file. An existing template file may be a template file that corresponds to a pre-generated animated scene, and may have been exported from motion effects software. The method may comprise exporting the template file from the motion effects software to the local storage at the first computing device. The template file may also be stored in local storage by retrieving it from other storage or by accessing it from a repository or remote storage. The template file may be a new template file, and so may be blank initially and have limited prepopulated data. Such a template file may be used to create an animated scene from scratch using the editing functions exposed within the rendering engine.[56] The input may be an indication from the user of a part of the animated scene to edit. The input may relate to the personalizable data object or to another data object or element of the animated scene. The input may relate to a sequence or movement within the animated scene.[57] Updating the template file may comprise writing or rewriting part of the template file to indicate the update made according to the input.[58] By rendering the animated scene in response to the template file being updated, the user may be able to quickly view what an end user may view. The rendering and display may be performed automatically and in real time or periodically.[59] In this aspect, the second computing device may be associated with another editing user and may provide editing functionality.[60] Upon the updated template file being stored at the remote storage location, the remote storage location may push the updated template file to the second computing device or transmit an indication to the second computing device that the template file has been updated. Alternatively, the second computing device may repeatedly call the remote storage location to check for updates to the template file. Accordingly, a second computing device that previously accessed the template file and is viewing the animated scene or a personalized video rendered from the template file may, in real-time, receive the updated template file and perform re-rendering to enable faster updates to the animated scene and personalized video than would otherwise be possible.[61] According to a third aspect, there is provided a computer-implemented method for enabling display of a personalized video to a user. The method comprises: receiving, at a server, a request for access to a web resource from a computing device, wherein the web resource is configured to display a personalized video on the computing device; transmitting, to the computing device by the server, the web resource, a template file that corresponds to an animated scene that includes a personalizable data object, and a rendering engine for rendering the animated scene as a personalized video, wherein: the rendering engine is configured to run within the web resource at the computing device, and is configured to use the template file to render the animated scene with the personalizable data object updated using data associated with the user and to output the rendered animated scene as video data within the web resource.[62] This method facilitates the efficient distribution of personalized video content by transmitting the components (template, rendering engine, and web resource) to the user's device, enabling client-side rendering and personalization. This approach reduces server-side processing requirements and allows for more responsive and interactive personalized video experiences.[63] Features associated with the first to third aspects may be combined as desired.[64] According to a fourth aspect, there is provided a system comprising: one or more processors; and a memory storing instructions, that, when implemented by the one or more processors, cause the system to perform a method as described above in any of the first to third aspects.[65] According to a fifth aspect, there is provided computer readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method as described above in any of the first to third aspects.[66] According to a sixth aspect, there is provided a system for displaying personalized video to an end user. The system comprises: a first computing device, wherein the first computing device is configured to provide editing functionality to a first user for generating an animated scene that includes a personalizable data object, wherein the first computing device renders the animated scene as video and displays the video to the user synchronously with said editing; and a second computing device, wherein the second computing device is configured to provide viewing functionality to a second user for viewing personalized video corresponding to the animated scene, wherein the second computing device renders the animated scene with the personalizable data object updated to include data associated with the second user as personalized video and displays the personalized video to the user, wherein the first computing device and the second computing device render the animated scene using the same rendering engine.[67] This system provides a unified platform for both creating and viewing personalized video content, ensuring consistency between the editing and viewing experiences by using the same rendering engine. This approach streamlines the content creation and distribution process, enabling efficient production and delivery of personalized video content. [68] The second computing device may also be configured to provide editing functionality to a second user, as well as viewing functionality. Accordingly, two users may be able to edit the same animated scene in real-time.[69] Features of the sixth aspect may be combined with features of any preceding aspect. For example, an underlying file corresponding to the animated scene may be stored locally at the first computing device during said editing and may be used by the rendering engine to render the animated scene. Similarly, the underlying file may be sent to the second computing device from remote storage for use in rendering the animated scene using the same rendering engine.[70] According to a further aspect, there is provided a system for displaying personalized video to an end user. The system comprises: a first computing device, wherein the first computing device is configured to provide editing functionality to a first user for generating an animated scene that includes a personalizable data object, wherein the first computing device renders the animated scene as video, displays the video to the user synchronously with said editing; and a remote server or storage location, wherein the first computing device is configured to store an underlying file corresponding to the animated scene at the remote server or storage location for retrieval and rendering as video by a second computing device. The first computing device and the second computing device may render the animated scene using the same rendering engine. The underlying file may be a file that can be rendered at the second computing device to provide video corresponding to the animated scene. The first computing device may be configured to render the animated scene using the underlying file stored locally at the first computing device prior to storage at the remote server or storage location. The second computing device may, in this example, be a computing device associated with another editing user.[71] According to a yet further aspect, there is provided a system for displaying personalized video to an end user. The system comprises: a second computing device, wherein the second computing device is configured to provide viewing functionality to a second user for viewing personalized video corresponding to an animated scene, wherein the second computing device renders the animated scene with a personalizable data object updated to include data associated with the second user as personalized video and displays the personalized video to the user; and a remote server or storage location, wherein the second computing device is configured to retrieve an underlying file corresponding to the animated scene from the remote server or storage location and render the video using a rendering engine.[72] There may further be provided a system comprising a first computing device, a second computing device, and a remote server or storage location as described in the aspects above.BRIEF DESCRIPTION OF DRAWINGS[73] Figure 1 is a pictorial diagram of a system and method for generating and displaying personalized video to users.[74] Figures 2A and 2B show a webpage within a browser application displaying different frames of a personalized video.[75] Figures 3A to 3D show a webpage within a browser application during editing of a personalized video.[76] Figure 4 is a block diagram of a system and method for generating and displaying personalized video to a user.[77] Figure 5 is a flow chart of the method for displaying personalized video to the user.[78] Figure 6 is a block diagram of a system and method for editing personalizable video for display to a user.[79] Figure 7 is a flow chart of the method for editing personalizable video for display to the user.[80] Common reference numerals are used throughout the figures to indicate similar features.DETAILED DESCRIPTION[81] The present disclosure relates to methods and systems by which personalizable video is created, edited, rendered, and displayed. The techniques described herein provide a process by which personalizable and personalized videos are displayed to users using client-side rendering rather than server-side rendering. This is achieved by using template files and a rendering engine that can be used by client-side devices to perform rendering of three-dimensional scenes including custom data relating to the user. At least some of the techniques described herein leverage web resources and web applications that are able to run as part of webpages or software applications and which utilize graphics processing capabilities of the device on which they are running to perform rendering. The output, which is a coherent video of an animated scene with the custom data integrated within it, is able to be displayed to the user with low latency.[82] By implementing client-side rendering using a rendering engine in this way, it also becomes possible for creators and editors of animated scenes to render and display personalizable video synchronously with the editing process. This is achieved because the same rendering engine is run at client devices as well as computing devices used by editors or creators. This enables much faster visual feedback as changes are made to the animated scene, as well as consistency between what will be seen by the end user and what is seen by the creator or editor.[83] To facilitate explanation of these techniques, Fig. 1 shows a system 100 for displaying personalized video content across multiple computing devices. The system 100 includes a plurality of computing devices associated with different users, including a first computing device 102 associated with a first user 104, a second computing device 106 associated with a second user 108, and a third computing device 110 associated with a third user 112.[84] The system 100 also includes a remote storage location 114. The computing devices 102, 106, 110 are able to exchange data with the remote storage location 114 via a network 116, as illustrated by communication links 118.[85] The system 100 depicted in Fig. 1 is illustrative and may include different numbers of computing devices, networks, and remote storage locations.[86] In Fig. 1, the first user 104 is an editing user, who is editing or creating an animated scene at the first computing device 102. The animated scene includes at least one personalizable data object. The personalizable data object may be a text field or other object that can be populated with custom data relating to an end user. Accordingly, the animated scene is a scene that, when rendered, will be a personalized video for the end user.[87] The first computing device 102 is configured to provide editing functionality to the first user 104 for creating or editing the animated scene. The first user 104 can access and modify a template file corresponding to the animated scene. The first computing device 102 uses a rendering engine to display the animated scene to the first user 104 during the editing process. The rendering engine running at the first computing device 102 exposes editing functions to enable the first user 104 to edit the animated scene, and renders the animated scene in real-time to enable the first user 104 to have visual feedback during editing. In Fig.1, the first computing device 102 is displaying the animated scene to the first user 104 on a display device.[88] As will be described later in this description, the first computing device 102 may be configured to access the template file from the remote storage location 114 via the network 116 as well as data assets and/or personalization data for rendering the animated scene. After editing is complete, or during editing, the first computing device 102 stores the template file corresponding to the edited animated scene in the remote storage location 114 for subsequent access by the first computing device 102 or other computing devices within the system 100.[89] The first computing device 102 is an example of how computing devices locally may be used for rendering animated scenes for editing purposes to provide real-time visual feedback for editing processes and alignment with how rendered animated scenes will be viewed by end users. There may be many different first computing devices 102 providing editing processes. Different editing users may edit different animated scenes and videos at different computing devices using the rendering engine and access to the remote servers and remote storage location. In addition or alternatively, the techniques described herein may enable multiple different editing users such as user 104 using different computing devices such as first computing device 102 to edit the same animated scene simultaneously and render the animated scene in real-time to provide feedback. By utilizing the rendering engine from a web resource and the data flows as will be described later, any computing device may be used for such editing purposes.[90] The second and third users 108, 112 are end users who view the personalized video on their devices 106, 110. The second computing device 106 and the third computing device 110 are configured to provide viewing functionality to the second user 108 and the third user 112, respectively. These computing devices 106, 110 access the template file from the remote storage location 114 and use the same rendering engine as the first computing device 102 to render the animated scene. The second and third computing devices 106, 110 may also access data assets and/or personalization information from the remote storage location 114 via the network.[91] Each computing device determines data associated with its respective user for updating the personalizable data object. This data may be retrieved from a location indicated by the template file and may include image data, text data, shape data, audio data, and/or video data. The computing devices also access at least one data asset indicated by the template file, which may comprise video data or image data.[92] The rendering engine on each computing device uses the template file to render the animated scene with the personalizable data object updated using the data associated with the respective user. This process results in the display of personalized videos on each device: a first personalized video 120A on the first computing device 102, a second personalized video 120B on the second computing device 106, and a third personalized video 120C on the third computing device 110.[93] In the personalized videos 120A, 120B, and 120C, the names displayed are three-dimensionally rendered and personalized to each individual user. This demonstrates how the system 100 enables the creation of customized content for multiple users while utilizing a common template and rendering engine across different devices. The first personalized video 120A on the first computing device 102, in this example, is populated with placeholder information for a first name of a user, which is “Alice”, and so a three-dimensional rendering of the animated scene is being displayed that reads “Hi Alice”. The second and third users 108, 112 are viewing their respective personalized videos 120B, 120C which include personalized name information. The second user 108 is therefore being displayed a video 120B by the second computing device 106 that reads “Hi Bob”, while the third user 112 is being displayed a video 120C by the third computing device 110 that reads “Hi Carol”.[94] The first computing device 102 may receive input from the first user 104 to change the placeholder information so that they can view how different names or information may be displayed within the scene. Such editing is enabled by the different functions that are exposed on the first computing device 102.[95] The system 100 may also include a server that receives requests from the computing devices and transmits resources in response. The server may transmit the template file, the rendering engine, and other components to enable the display of personalized videos on each computing device, as will be described in more detail below.[96] Before the methods and interactions between the devices are described in more detail, Figs.2A to 2B and 3A to 3D show examples of how personalized videos may be displayed to an end user (Figs.2A to 2B) or edited and displayed to an editing user (Figs. 3A to 3D). These examples are shown in the context of a browser application and webpages that are configured to provide playback or editing and playback functionality to users for the personalized video. While browser applications are used to demonstrate these features herein, in other examples the personalized video may be delivered by other web resources, such as via a software application downloaded from an app store or marketplace such as the Google® Play Store or the Apple® App Store.[97] Fig. 2A and Fig. 2B provide illustrated examples showing how personalized video may be displayed to users such as the second user 108 and the third user 112 using the second computing device 106 and the third computing device 110, respectively.[98] Figs. 2A and 2B show a browser application 200 on a computing device (not shown) displaying a webpage 202 to which a user (not shown) of the computing device on which the browser application 200 has navigated or been directed. A web address 204, which may be referred to as a uniform resource locator or URL, is shown in an address bar of the browser application 200. The browser application 200 has used the web address 204 to navigate to and request access to the webpage 202 from a remote server (not shown).[99] The web address 204 includes data 206 associated with the user for personalizing a personalizable data object of the animated scene. In this example, the data 206 is a first name, “Daniel”, of the user. The user may have obtained the web address 204 from another resource, such as a preceding webpage in which he was asked to enter his name and which then directed him to the web address 204 or which provided the web address 204 for copying or as a link to navigate to the webpage 202. Alternatively, the user may have been sent the web address in an email or other electronic communication from a company that already held that information for the user.[100] The webpage 202 includes a media interface 208, which may be referred to as a media player or a media player interface, and is configured to display a personalized video to the user via the media interface 208. The media interface 208 includes several control elements: a playback control 212, a progress indicator 214, an audio control 216, and a display control 218. These controls allow the user to interact with the personalized video 210, controlling playback, volume, and display settings. The functionalities of the media interface 208 are exposed for display on the webpage 202 and interaction with by the user via the computing device by the web application that implements the rendering engine and media interface 208. The web application or the webpage is configured to expose the correct functionalities for the webpage 202. The web application may, for example, use a compiler such as Emscripten, and bindings of the compiler may be used to expose the functionalities. How the different functionalities are exposed may depend upon the implementation. The web application itself may be configured to expose the correct functionalities, implementing the rendering engine as well as the functionalities that are designated for the user or the webpage being accessed. In such a circumstance, different web applications containing the same rendering engine may be associated with different webpages. Alternatively, the web application may have all functionalities incorporated, and the webpage loading the web application may be configured to expose the desired functionalities.[101] Figs. 2A and 2B show the personalized video 210 at two different times. Fig. 2A shows the video at a first time, and Fig.2B shows the video at a second, later time, as indicated by the progress bar 214.[102] The personalized video 210 shows a scene containing a swimming pool 220 with steps 222 leading into it and a floor 224. Waves 226 of the water within the swimming pool 220 can be seen rippling. Within the scene, there is a rubber ring 228 that casts a shadow 230 on the floor 224. This scene is provided as an example only and the techniques described herein may be applied to any animated scene.[103] The scene also includes a personalizable data object 232, which in this instance is a text object. In the video 210, the object 232 has been rendered and personalized to include the user’s first name, as indicated in the data 206 associated with the user in the web address 204. The data object 232 is rendered so as to appear as part of the floor 224 of the swimming pool 220, so that the waves 226 pass over the name, the rubber ring 228 obscures the name as it floats across the surface of the water in the pool 220, and so that shadows on the floor 224 of the pool 220, such as the shadow 230 of the rubber ring 228 are cast onto the name. The movement of the waves 226, the rubber ring 228 and the shadow 230 can all be seen between Figs.2A and 2B, while the data object 232 containing the name remains in the same place. In other words, the data object 232 is integrated into the scene and has multiple threedimensional effects applied to it. Although not visible here, the texture of the name may also match that of the floor of the pool, further integrating the name into the scene.[104] Accordingly, the personalizable data object 232 can be described as being rendered into the scene and forms part of the personalized video, rather than being merely overlaid or placed on top of a generic or non-personalized video. The personalizable data object 232 forms part of the animated scene that is subsequently rendered locally at the user’s computing device using a rendering engine, as is described in more detail below.[105] The animated scene may include any three-dimensional effects or interactions between different elements. The animated scene may be a three-dimensional model and a scene graph may indicate transitions between different frames of the scene. Accordingly, different three-dimensional effects or objects may be integrated, especially in relation to personalizable data objects, which may have depth, shadows, or other three-dimensional characteristics.[106] While Figs 2A to 2B show how an end user may view a personalized video 210, Figs. 3A to 3D show how an animated scene may be rendered and edited at a computing device by an editing user, such as the first user 104 using the first computing device 102.[107] In each of Figs.3A to 3D, a browser application 300 is shown on a computing device (not shown) displaying a webpage 302 to which a user (not shown) of the computing device on which the browser application 300 has navigated or been directed. A web address 304, which may be referred to as a uniform resource locator or URL, is shown in an address bar of the browser application 300. The browser application 300 has used the web address 304 to navigate to and request access to the webpage 302 from a remote server (not shown).[108] In contrast to the webpage 202 in Figs. 2A to 2B, the webpage 302 is a webpage for editing an animated scene. The webpage 302 therefore contains a media interface 308 where a personalizable video 310A and editing functionalities are displayed. The media interface 308 is different to the media interface 208, as it has different functions exposed. The media interface 308 includes a playback control 312 for controlling video playback. Below the playback control 312, multiple scenes 314 are arranged as selectable blocks, representing different segments of an overall personalizable video. The other scenes may be non-personalizable video or personalizable video. Accordingly, the personalizable video 310A relating to the particular selected scene 314 may be displayed in series with other animated scenes or other blocks of videos. An editing toolbar 316 is positioned to one side of the media interface 308, providing various editing tools to the user. As with the playback functionalities in the webpage 202, the functionalities on the webpage 302 are also exposed by a web assembly implementing the rendering engine and media interface 308 on the webpage 302. The functionalities may be exposed using a compiler, such as Emscripten and bindings. The functionalities may be specific to the webpage, such that accessing page 302 via address 304 allows editing functionalities to be exposed and accessing webpage 202 via address 204 allows playback functionalities to be exposed with the editing functionalities being hidden to the end user. The editing functionalities may enable editing of the underlying template file, as will be described below in more detail in relation to Figs.6 and 7.[109] The personalizable video 310A displays elements similar to those seen in Fig. 2A and Fig.2B, including a swimming pool 320, a floor 324, a rubber ring 328, and a shadow 330 cast by the rubber ring 328. A personalizable data object 332 is visible within the scene, integrated in the same way as in Figs.2A and 2B as part of the floor 324 of the swimming pool 320. In this example, the object 332 is rendered with a placeholder name “Emily”.[110] In Fig.3A, the webpage 302 is displaying the rendered animated scene as the personalized video 310A. The personalized video 310A is displayed to the editing user so that they have visual feedback relating to what an end user may see. This is achieved by running the same rendering engine for editing and viewing purposes and exposing different functionalities dependent on which resource is being accessed.[111] The user may wish to edit the animated scene, and so may select one of the scenes 314. This may lead to an editing screen such as in Fig. 3B, which illustrates how the user may modify the personalizable data object 332. In Fig.3B, a frame 311 of the animated scene is shown, with a content frame 334 displayed around the personalizable data object 332. The content frame 334 shows that the personalizable data object 332 has been selected and can now be edited. An object editing frame 336 is positioned on the right side of the interface, providing controls for customizing the personalizable data object 332. The object editing frame 336 shows a text input field labeled "First_Name" with "Emily" entered as the placeholder value and sliders for controlling, for example, orientation, size, font, color, etc., of the object 332.[112] The user may choose to edit parameters or properties of the placeholder. An example of this is shown in Fig. 3C, in which a value and a position of the personalizable data object 332 have been edited within the frame 311. The personalizable data object 332 now displays the text "Frank," demonstrating how the user 104 can preview different names within the scene and at different positions. The content frame 334 and object editing frame 336 remain visible, allowing for continued editing of the personalizable data object 332.[113] Once the user has completed editing the frame 311, they may return to viewing the video 310. The computing device is configured to re-render the updated video. Edits and updates, such as shown in Fig.3C, are used by the rendering engine to edit the underlying template file stored in local storage of the computing device. As a result, as shown in Fig. 3D, once editing is complete, the rendering engine is able to render an updated personalized video 310B, with the personalizable data object 332 in a different position and utilizing different data for the personalization. By the rendering engine running locally at the computing device and within the resource, it is possible for the user to effectively see real-time updates as edits are made.[114] If the re-rendered video is suitable, the template file may then be exported to remote storage location for access via webpages such as webpage 202 for end users to be displayed the personalized video 310B, including the relocated personalizable data object 332. As the field of the object 332 remains the first name, the first name of each user will be used to update this field during personalization and rendering. The template file may also be exported to remote storage location on the go, such that changes made to the locally stored template file are also exported to the remote storage location.[115] Figs. 3A to 3D show editing an existing animated scene. The animated scene may be exported from motion graphics software such as Adobe After Effects as a template file and imported for use in the editing webpage 302. The template file may be created using a plug-in or other software based on a three-dimensional model or animation generated in the motion graphics software. For example, the Bodymovin plug-in or a plug-in that is based on Bodymovin and adapted to enable some additional three-dimensional properties to be converted to a template file may be used to generate a template file. The template file may be exported according to a particular schema in a data interchange format. For example, the template file may be written in a JSON or other data interchange format, and may be based on a LottieFiles schema or may be a custom schema. The template file enables the animated scene, i.e. the motion graphics, created in the software to be re-rendered by the rendering engine. Accordingly, the template file may be considered to be a compressed, encoded, or serialized file corresponding to the animated scene and contains instructions for reconstructing the animated scene. In these scenarios, the template file may be retrieved from a remote storage location and stored locally at the computing device, before being re-stored after editing.[116] Editing webpages such as webpage 302 may also provide functionality for creating new animated scenes. In such an example an effectively ‘blank’ template file (i.e. with no data relating to the animated scene, but may be generated and stored locally, and the template file may then be populated as the animated scene is created within the webpage. The animated scene may be rendered as desired so that the editing user is able to better visualize how the resulting personalized video will be displayed. Once complete, the populated template file can be stored in a remote storage location for subsequent editing or for access by end user computing devices.[117] Although not depicted in these figures, audio elements may also be added, such as music and voice over for the video. Audio elements may be personalized in addition to the video. Audio elements may be received separately to the rendering engine and template file, and/or may be rendered by the rendering engine, for example using FFmpeg server-side and HTML/JavaScript audio features at the client-side such as inline JavaScript calls from C++ code, creating HTML Audio Elements. Audio elements may be received separately by making a separate API call. The audio elements may be generated at a remote server, with the rendering engine implementing a call to the remote server that indicates data for personalization of the audio elements (if any) and audio assets for rendering the audio elements. The rendering engine may also be configured to synchronize the audio to the video and vary the audio relative to the video dependent on how the rendering of the video progresses and//or whether there are performance variations at the computing device. In some examples, an alternative rendering engine may be received for rendering audio elements.[118] In some examples, another editing user, i.e. a second editing user, may also be viewing the same or a similar webpage to webpage 302 (albeit having different user personalizations and settings, achieved using different permissions). As the first editing user performs the task described above in relation to Figs.3A to 3D, the template file may be exported, in real-time to the remote storage location, and simultaneously retrieved or received by a computing device being used by the second editing user. Accordingly, that computing device may then re-render the updated template file, to effectively show the changes. The second editing user would therefore see a change from what is shown in Fig.3A to what is shown in Fig.3D, allowing real-time co-editing and simultaneous feedback for multiple editing users. A process for dealing with editing conflicts may be implemented to ensure that conflicting changes are not made to the same template file, or alternatively a locking system may be implemented to allow one user to edit an animated scene at a time.[119] Figs. 4 to 7 describe systems and methods performed to enable such display of personalized video content. Fig. 4 illustrates a block diagram of a system 400 for displaying personalized video content. The system 400 includes a client computing device 402 associated with a user 404, a remote server 406, and a remote storage location 408.[120] The client computing device 402 is shown as having components including a display interface 410, a central processor 412, a graphics processor 414, and a memory module 416. The display interface 410 in this example is a touchscreen, such that the client computing device 402 is able to display content to the user through the display interface 410 as well as receive user input through the display interface 410. In other examples, a display and input interface of the computing device may be separated, such as a screen and keyboard and mouse arrangement for a laptop.[121] The system 400 facilitates various data exchanges between its components to facilitate display of a personalized video to the user 404. Initially, as indicated by arrow 418, user input is provided to the computing device 402 by the user 404 to request access to a web resource. The web resource is one that is configured to display a personalized video to the user. This may comprise, for example, requesting access to a webpage such as webpage 202 using a browser application and a web address or requesting that a software application is downloaded to the computing device 402. The software application may be requested using a web resource also.[122] In response, the computing device 402 transmits an access request 420 to the remote server 406, which may be referred to as a web server. At 422, the remote server 406 accesses a template file stored in the remote storage location 408 corresponding to an animated scene including at least one personalizable data object that is to be displayed to the user 404 as a personalized video.[123] The template file contains various elements and instructions for creating and rendering the animated scene. It may include scene layout information, placeholders for personalizable data objects, animation parameters, and references to data assets such as images, textures, or 3D models. The template file may also contain scripting or logic for dynamic content generation, metadata about the scene such as duration and resolution, and instructions for integrating personalized data. The template file may specify API endpoints or local storage locations from which personalized data is to be retrieved. It may also include information about how to apply various visual effects, transitions, or interactions to the personalizable data objects within the scene.[124] The template file has a structured format that can be parsed and interpreted by the rendering engine. This format may be based on data interchange formats like JSON or XML, or may use a custom binary format optimized for efficient processing. The template file may include a scene graph or other data structures to define the relationships and behaviors of objects within the animated scene. Accordingly, the template file may be relatively small in size compared to the final rendered video, as it primarily contains instructions and references rather than the full video data. This approach may allow for efficient transfer and storage of the template file, particularly when used with mobile devices or in scenarios with limited bandwidth. The use of template files may also enable separation of the scene structure from the personalized content, allowing for efficient updates and modifications to the animated scene without altering the core rendering logic.[125] After retrieving the template file, the server 406 serves 424 the webpage, the template file, and a rendering engine for rendering the personalized video based on the template file to the computing device 402.[126] The rendering engine received from the remote server 406 is configured to run within the web resource at the client computing device 402. This web resource may be a webpage or a software application. In some examples, the rendering engine operates as a web application within a browser application on the client computing device 402. Alternatively, the web application may form part of a software application installed on the client computing device 402. The web application utilizes memory and resources associated with the browser or software application to perform the rendering. In particular, the web application makes use of the graphics processor 414 of the computing device 402, as well as the central processor 412, to perform the rendering. The web application may be a web assembly, and specifically a graphics web assembly or graphics API, such as WebGL or WebGPU. The rendering engine may be implemented as a virtual machine within the browser application. These features allow for efficient execution of the rendering process on various client computing devices regardless of their specific hardware configurations. [127] The rendering engine may be implemented or run to begin the process of generating the personalized video upon arrival at the computing device, upon the user requesting that the video is played, or upon another trigger event, such as the user opening the software application, selecting an option, or inputting data associated with the user to the computing device 402.[128] The rendering engine parses the template file to identify data assets and data associated with the user with which it can render the animated scene and output the personalized video. The template file indicates locations from which data assets and data associated with the user can be retrieved.[129] At least some of the locations may be local to the computing device 402, such as in memory 416 or, for data relating to the user, as part of the web address as described in relation to Figs.2A and 2B. Alternatively or additionally, at least some of the locations may be remote locations, such as remote storage location 408. Remote storage location 408 may be, for example, a data repository, database of user information, and/or cloud storage. Where some or all of the data is stored at a remote storage locations, the computing device 402 retrieves the data assets and/or data associated with the user from the remote storage location 408. In Fig.4, this is depicted as two calls and responses shown as steps 426 and 428 for data assets and steps 430 and 432 for data associated with the user. Of course, in some examples these calls may be made together or as multiple calls. These calls may be API calls, HTTP calls, or calls according to another data exchange protocol.[130] The data assets may, for example, be images, videos, text, textures, or other features for building and rendering the animated scene. Audio assets may also be retrieved in this way to enable building of the audio elements that accompany the video. Video data assets may be encoded and decoded for transmission in this way, using an encoding and decoding toolkit or API set such as the NVIDIA Codec SDK serverside and by creating HTML Video Elements or by using a WebCodecs API client-side.[131] Upon retrieving the data for building the animated scene, the rendering engine renders the animated scene including the data associated with the user using the graphics processor 414 of the computing device 402 and outputs personalized video data. As noted above, the rendering engine is implemented as a web application, particularly a web assembly or WASM, within the computing device, enabling it to make use of the computing device’s hardware to facilitate rendering of the video. The rendering engine utilizes the template file, which provides details of how the animated scene is constructed using different data assets and the transitions through it according to a scene graph, as well as where to place personalized data objects and how they integrate into the scene. The rendering engine may, for example, utilize video data assets such as HTMLVideoElements and render them as a texture within the frame being rendered.[132] The video data is then displayed 434 on the display interface 410 of the computing device 402 to the user 404, as described above in relation to Fig. 1 and Figs. 2A to 2B.[133] The operations of a computing device associated with a user for displaying a personalized video, such as the second or third computing devices 106, 110 in Fig.1, the computing device 402 in Fig.4, or the computing devices displaying what is shown in Figs.2A and 2B may be expressed in a flow chart. Fig.5 shows such a method 500 for displaying personalized video to a user.[134] The method 500 begins at step 502, where the computing device requests access to a web resource from a remote server. This web resource includes an animated scene. The animated scene includes at least one personalizable data object, such as data object 232 in Fig. 2. At a step 504, the computing device receives the web resource, a template file, and a rendering engine from the remote server.[135] The rendering engine received by the computing device may be compiled to web assembly using Emscripten. This may allow the rendering engine to run efficiently within a web browser environment. The rendering engine may use WebGL as a graphic API when instantiated as a WebAssembly module, enabling hardware-accelerated graphics rendering.[136] At step 506, the computing device runs the rendering engine. The rendering engine may expose interfaces for interaction using Emscripten bindings (embind), which allows JavaScript code to interact with the C++ code of the rendering engine.[137] Step 508 involves parsing the template file by the rendering engine. During this step, the rendering engine analyzes the structure and content of the template file to prepare for rendering the animated scene.[138] Step 510, the computing device accesses data assets indicated by the template file, based on parsing the template file. These data assets may include images, videos, or other media elements for building the animated scene. [139] At step 512 the computing device determines data associated with the user. This data may be retrieved from a location specified in the template file and is used to personalize the animated scene.[140] Steps 510 and 512 are depicted as being performed concurrently, but may be performed at different times in some examples.[141] At step 514, having retrieved data assets and data associated with the user, the rendering engine renders the animated scene. This step is performed, at least in part, at a graphics processing unit of the computing device. The rendering engine is capable of rendering multiple projects sequentially, allowing for complex, multi-part animations. The rendering engine is configured to render three-dimensional models or scenes to video, enabling three-dimensional effects and objects.[142] During the rendering process, the rendering engine may create HTML Audio Elements for audio handling. This enables synchronized audio playback with the visual elements of the animated scene.[143] At step 516, the computing device displays the rendered video. The rendered video is presented through a player application that has functionality for play, stop, seek, and audio handling, providing a complete video playback experience.[144] Fig. 6 illustrates a system 600 for editing and personalizing video content. The system 600 includes a computing device 602 associated with a user 604, a remote server 606, and a remote storage 608. The remote storage 608 may be the same remote storage 408 utilized by the web server 406 in Fig.4.[145] The computing device 602 comprises several components that enable video editing and personalization. These components include a display interface 610, a processor 612, a graphics processor 614, and a memory module 616. The display interface 610 in this example is a touchscreen, such that the client computing device 602 is able to display content to the user through the display interface 610 as well as receive user input through the display interface 610. In other examples, a display and input interface of the computing device may be separated, such as a screen and keyboard and mouse arrangement for a laptop. The processor 612 and graphics processor 614 work in conjunction to process and render the video content, while the memory module 616 stores data during the editing process. The hardware of the computing device 602 is generally similar to the hardware of the computing device 402 associated with the user 404, while the functionality of the computing device 602 is different, as will be explained below. [146] The system 600 facilitates various interactions between its components to enable video editing and personalization. Initially, the user 604 navigates 618 to a web resource that is used for editing animated scenes at the computing device 602. The user 604 may be requested to log in to the web resource. In response, the computing device 602 may request access to the web resource from the remote server 606. Accessing the web resource comprises navigating to a webpage or to a software application that facilitates a network connection as part of its functionality. As part of navigating, the user 604 may indicate an animated scene or plurality of animated scenes to be edited or viewed and the request 620 may indicate these animated scenes.[147] Upon receiving the request, the remote server 606 initiates a data transfer 622, retrieving the template file or files corresponding to the animated scene or scenes from remote storage 608. The server then delivers the web resource, template file(s), and a rendering engine to the computing device 602 through resource delivery 624. The rendering engine is generally the same rendering engine as used on the computing device 402 in Fig.4, albeit with some different functionality exposed for use by the user on the computing device 602. The rendering engine therefore renders the animated scene(s) in the same way as any other device, as the same rendering engine is utilized client-side.[148] Upon receipt of the template file(s) the computing device 602 stores the template file(s) in memory 616. The template file(s) may be cached for ease of access. Storing the template file locally enables fast updating and rendering.[149] As in Fig.4, the computing device 602 may subsequently retrieve data assets indicated in the template file at 626 and 628 from the remote storage 608. This may be achieved using calls and responses, such as API, HTTP, or other data exchange protocol calls. The computing device 602 may retrieve personalization data also in this step, although this is not depicted here. Generally, the computing device 602 may also use placeholder data for rendering personalizable data objects within the animated scene rather than gathering personal data relating to the user. The placeholder data may be retrieved as a data asset, may already be present within the template file, or may be input by the user 604 during use of the webpage.[150] The computing device 602 renders and display the video to the user, as indicated by video output 630. The user 604 is therefore able to review the existing animated scene as it would be viewed by an end user such as user 404, as explained above in relation to Fig.3A.[151] The user 604 may wish to edit the animated scene, and may provide input 632 to the computing device 602 via the display interface 610 to edit the animated scene.[152] Upon receiving the input 632, the computing device 602 is configured to update the template file stored locally in memory 616, while the user 604 views the modifications on the display interface 610 of the computing device 602 as described above in relation to Figs.3B and 3C.[153] Throughout this process, the template file may be updated in local storage, as well as the updates being communicated and stored 636 in the remote storage location 608. Alternatively, the template file may be stored 636 after modifications are complete. This allows for persistent storage and retrieval of the latest version of the template file. The template file may be associated with a particular web resource by the web server 606 or 406 or within a data structure in the remote storage location 608.[154] Once the user has modified the animated scene, the rendering engine is configured to re-render the scene as video data and display it to the user at 634.[155] The operation of a computing device for editing an animated scene such as computing device 602 can be described by a flow chart. Fig.7 illustrates a method 700 for editing personalizable video content. The method 700 represents a flow chart of actions performed by a computing device when the user is editing a template for personalizable video content for subsequent viewing as a personalized video by an end user.[156] The method 700 begins at a step 702, where the computing device requests access to a web resource for editing the animated scene from a remote server. At step 704, the computing device receives the web resource, the template file, and the rendering engine from the remote server.[157] Step 706 involves storing the template file in local storage of the computing device. After step 706 and before step 708, as described in relation to Fig. 6, the computing device may render the animated scene for previewing by the user, although in some examples only a frame may be viewed for editing.[158] At step 708, the computing device receives input relating to an update to the animated scene from the user. This input may include modifications to a personalizable data object or other elements of the animated scene. [159] Step 710 involves updating the template file in the local storage to reflect the update to the animated scene. The computing device modifies the template file based on the input received from the user.[160] At step 712, the computing device parses the updated template file. This step prepares the updated template file for rendering by analyzing its structure and content.[161] Step 714 involves accessing data assets indicated by the updated template file. The computing device retrieves any images, videos, or other media elements for the updated animated scene.[162] At step 716, the computing device determines data for previewing the updated animated scene. This may include placeholder data or sample personalization data to demonstrate how the animated scene appears with different inputs. This data may be considered to be associated with the editing user.[163] At step 718, the computing device renders the updated animated scene using the rendering engine. The computing device processes the updated template file, data assets, and preview data to generate a visual representation of the edited animated scene.[164] At step 720, the computing device displays the rendered video as a preview to the user. This allows the user to see the results of the edits in real-time.[165] Step 722 involves storing the updated template file at the remote storage location. This ensures that the latest version of the template file is available for use in creating personalized videos for the end users.[166] The systems and methods described herein may be implemented in any form of computing or electronic device. The term "computing device," as used herein, encompasses any device with processing capabilities sufficient to execute instructions. This includes, but is not limited to, personal computers, servers, mobile devices, personal digital assistants, and similar devices.[167] Such devices may include one or more processors, such as microprocessors, controllers, or other suitable types of processors, capable of executing instructions to control the device's operation. For example, in some implementations using a systemon-a-chip architecture, the processors may include fixed-function blocks (hardware accelerators) that perform parts of the method in hardware rather than software or firmware. Platform software, such as an operating system or similar, may be installed to support the execution of application software. [168] The described functionality may be implemented in hardware, software, or any combination thereof. When implemented in software, the instructions or code can be stored on or transmitted via a computer-readable medium. Such media include computer-readable storage media, which may be volatile or non-volatile, removable or non-removable, and implemented using any technology for storing information such as program code, data structures, or other data. Examples include, but are not limited to, ROM, EEPROM, RAM, magnetic or optical storage, flash memory, or any other storage medium accessible by a computer. Communication media that facilitate the transfer of software, such as via coaxial cables, fiber optics, DSL, or wireless signals, may also be considered part of computer-readable media.[169] Alternatively, or in addition, some or all of the described functionality may be implemented using hardware logic components. Examples include, but are not limited to, application-specific integrated circuits, system-on-a-chip systems, fieldprogrammable gate arrays, application-specific standard products, and complex programmable logic devices. In some cases, software instructions may also be implemented in dedicated circuits, such as programmable logic arrays or digital signal processors.[170] The computing device may operate as a standalone system or as part of a distributed system, where tasks are performed collectively by multiple devices connected via a network. Such devices may communicate over a network connection to perform the described functionality. For instance, software may be stored on a remote computer and accessed by a local device, which may download and execute portions of the software as needed. Similarly, some instructions may be processed locally, while others may execute on remote systems or networks. In some cases, the computing device may be remote and accessible via a communication interface. Storage of program instructions may also be distributed across a network or stored in a combination of local and remote locations. For example, software may reside on a remote computer and be accessed by a local terminal, or the system may execute some software locally while other components operate on remote servers.[171] Features of any of the examples or embodiments outlined above may be combined to create additional examples or embodiments without losing the intended effect. It should be understood that the description of an embodiment or example provided above is by way of example only, and various modifications could be made by one skilled in the art. Furthermore, one skilled in the art will recognize that numerous further modifications and combinations of various aspects are possible. Accordingly, the described aspects are intended to encompass all such alterations, modifications, and variations that fall within the scope of the appended claims.
Claims
CLAIMS1. A computer-implemented method for displaying personalized video to a user, the computer-implemented method comprising:accessing, by a computing device associated with the user, a template file stored at a remote storage location, wherein the template file corresponds to an animated scene that includes a personalizable data object;determining, by the computing device, data associated with the user for updating the personalizable data object from a location indicated by the template file;rendering the animated scene using a rendering engine operating on the computing device, wherein the rendering engine uses the template file to render the animated scene with the personalizable data object updated using the data associated with the user and outputs the rendered animated scene as video data; and displaying the video data on a display of the computing device.2. The computer-implemented method of claim 1, wherein rendering the animated scene is performed, at least in part, at a graphics processing unit of the computing device.3. The computer-implemented method of claim 1 or claim 2, wherein the animated scene includes at least one three-dimensional effect.4. The computer-implemented method of claim 3, wherein the three-dimensional effect is applied to the personalizable data object.5. The computer-implemented method of any preceding claim, wherein the animated scene is a three-dimensional animated scene, and wherein the rendering engine is a three-dimensional rendering engine.6. The computer-implemented method of any preceding claim, wherein the animated scene is rendered at run-time.7. The computer-implemented method of any preceding claim, wherein displaying the video data comprises displaying the video data in series with one or more further blocks of video data.8. The computer-implemented method of any preceding claim, further comprising accessing, by the computing device, at least one data asset indicated by the template file, wherein the rendering engine renders the animated scene by integrating the data associated with the user with the at least one data asset.9. The computer-implemented method of claim 8, wherein the at least one data asset comprises at least one of video data or image data.10. The computer-implemented method of any preceding claim, wherein the data associated with the user comprises at least one of: image data, text data, shape data, or video data.11. The computer-implemented method of any preceding claim, wherein the rendering engine is a web application, and wherein the method further comprises: requesting, by the computing device, access to a web resource from a remote server that includes the animated scene; andreceiving, by the computing device from the remote server, the web resource, the template file, and the rendering engine.12. The computer-implemented method of claim 11, wherein the web application operates in a browser application on the computing device.13. The computer-implemented method of claim 11, wherein the web application forms part of a software application installed on the computing device.14. The computer-implemented method of any of claims 11 to 13, wherein the web resource is a webpage or a software application.15. The computer-implemented method of any of claims 11 to 15, wherein determining the data associated with the user comprises at least one of:receiving input from the user at the computing device that comprises the data associated with the user;retrieving the data associated with the user from a local memory location of the computing device that is associated with the web resource;retrieving the data associated with the user from a remote storage location associated with the web resource via a network connection; ordetermining the data associated with the user from a URL entered into a browser application at the computing device.16. The computer-implemented method of any of claims 11 to 15, wherein the web application implements the rendering engine as a virtual machine.17. The computer-implemented method of any preceding claim, wherein the rendering engine has one or more functions for allowing the animated scene to be edited, and wherein the one or more functions are enabled or disabled dependent on a user of the computing device.18. The computer-implemented method of any preceding claim, wherein the computing device is a first computing device, and wherein the method further comprises, before accessing the template file with the first computing device:accessing, by a second computing device associated with an editing user, the template file;rendering the animated scene using the rendering engine operating on the second computing device, wherein the rendering engine uses the template file to render the animated scene with the personalizable data object updated using predetermined data and outputs the rendered animated scene as video data; and displaying the video data on a display of the second computing device.19. The computer-implemented method of claim 18, wherein the template file is stored in local storage at the second computing device.20. The computer-implemented method of claim 19, wherein the method further comprises, before accessing the template file with the first computing device:receiving input relating to an update to the animated scene at the second computing device;updating, by the second computing device, the template file in the local storage to reflect the update to the animated scene;in response to the template file being updated:re-rendering the animated scene using the rendering engine using the updated template file; anddisplaying the video data on a display of the first computing device; and storing the updated template file at the remote storage location for accessing by the first computing device.21. A computer-implemented method for editing a personalizable animated scene, the computer-implemented method comprising:storing, by a first computing device associated with an editing user, a template file in local storage of the first computing device, wherein the template file corresponds to an animated scene that includes a personalizable data object;receiving input relating to an update to the animated scene at the first computing device;updating, by the first computing device, the template file in the local storage to reflect the update to the animated scene;in response to the template file being updated:rendering the animated scene using a rendering engine operating on the first computing device, wherein the rendering engine uses the updated template file to render the animated scene with the personalizable data object updated using predetermined data and outputs the rendered animated scene as video data; anddisplaying the video data on a display of the first computing device; and storing the updated template file at a remote storage location for accessing by a second computing device associated with a viewing user, wherein the second computing device is configured to use the rendering engine to render the animated scene with the personalizable data object updated using data associated with the viewing user.22. A computer-implemented method for enabling display of a personalized video to a user, the computer-implemented method comprising:receiving, at a server, a request for access to a web resource from a computing device, wherein the web resource is configured to display a personalized video on the computing device;transmitting, to the computing device by the server, the web resource, a template file that corresponds to an animated scene that includes a personalizable data object, and a rendering engine for rendering the animated scene as a personalized video, wherein:the rendering engine is configured to run within the web resource at the computing device, and is configured to use the template file to render the animated scene with the personalizable data object updated using data associated with the user and to output the rendered animated scene as video data within the web resource.23. A system comprising:one or more processors; anda memory storing instructions, that, when implemented by the one or more processors, cause the system to perform the method of any preceding claim.24. A computer readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any of claims 1 to 22.25. A system for displaying personalized video to an end user, the system comprising:a first computing device, wherein the first computing device is configured to provide editing functionality to a first user for generating an animated scene that includes a personalizable data object, wherein the first computing device renders the animated scene as video and displays the video to the user synchronously with said editing; anda second computing device, wherein the second computing device is configured to provide viewing functionality to a second user for viewing personalized video corresponding to the animated scene, wherein the second computing device renders the animated scene with the personalizable data object updated to include data associated with the second computing device as personalized video and displays the personalized video to the user,wherein the first computing device and the second computing device render the animated scene using the same rendering engine.
Drawings

Priority


No priority

Patent classes


IPC classesH04N 21/00H04N 21/81H04N 21/2343H04N 21/40H04N 21/414H04N 21/472H04N 21/222H04N 21/45H04N 21/458CPC classesH04N 21/00H04N 21/8146H04N 21/2343H04N 21/23439H04N 21/40H04N 21/414H04N 21/41407H04N 21/47205H04N 21/2223H04N 21/234345H04N 21/4532H04N 21/458

Citations


WO 2024059895 A1 (A1)US 2024087204 A1 (A1)EP 3674925 A1 (A1)US 2013147913 A1 (A1)US 2016212482 A1 (A1)US 2006259588 A1 (A1)US 2024314396 A1 (A1)US 2020336231 A1 (A1)EP 3912160 A1 (A1)US 2015221000 A1 (A1)US 2016029002 A1 (A1)

Applicants, owners and inventors


Applicants
SEEN AS
Nedre Slottsgate 10 0157 OSLO NO (OSLO Municipality, Oslo county)Org. number: 919061340
Inventors
Serhii Palii
Eckersbergs gate 15 0266 OSLO NO (OSLO Municipality, Oslo county)
Frank-Vegar Mortensen
Måneveien 28 1337 SANDVIKA NO (BÆRUM Municipality, Akershus county)
Gabor Lossos
Eiksveien 67 1361 ØSTERÅS NO (BÆRUM Municipality, Akershus county)
Ronald Heyerdahl Griffin
Herslebs gate 15B 0561 OSLO NO (OSLO Municipality, Oslo county)
Sahil Bajaj
Marstrandgata 4 0566 OSLO NO (OSLO Municipality, Oslo county)
Marcus Eckert
Ebersstrasse 35 10827 BERLIN DE
Lekë Dobruna
St. Qamil Hoxha No. 12/6, 10000 PRISHTINA XX
Dragoș-Paul Marinescu
Strada Vulturilor 21 077180 TUNARI, ILFOV RO

Agent


ACAPO ONSAGERS AS
ACAPO ONSAGERS AS

Org. number: 932214636

Name and address are automatically synchronized with the Brønnøysund Register Centre.

Open in The Brønnøysund Register Centre
Edvard Griegs vei 1 5059 BERGEN NO (BERGEN Municipality, Vestland county)
Org. number: 932214636
Reference: P31570NO00

Status history


Payment history


Oppositions and appeals


No oppositions or appeals

Administrative limitation


No administrative limitation

Liens and licences


No liens or licenses registered

Gazette entries


No Gazette entries foundOnly events from 2024.03.04 and onwards are shown.