Mobile phone configuration for TV and film

Abstract

A method for operating a communications device for use in filming TV or film scenes, the device having a display screen; a user interface for receiving user commands; and a native operating system, said native operating system having one or more native application programs, wherein each said native application 5 program comprises means for generating a corresponding respective set of native Screen Views; and the device further comprises a configurator for generating a sequence of Screen Views and actions which are run on said communications device; the method comprising generating sequence of Screen Views comprising a plurality of individual Screen Views which are generated to 0 be run in a predetermined order and / or in response to a set of Commands input by a user. The device may be user activated to generate a sequence of screens or may be remotely activated to move from screen to screen. The content of the screens is predetermined when executed, and any changes to the content or sequence of screens nay be made on set using the same communications device 5 and avoiding the need for post-production editing.

Description

MOBILE PHONE CONFIGURATION FOR TV AND FILMField of the Invention

[0001] The present invention relates to a method and operation of a mobile telecommunications device.Background of the Invention

[0002] In film and television, there are many scenes where actors are called upon to use a smartphone, laptop, tablet or like device either to make a voice call, send or receive messages or texts, or to scroll through apps, in front of the camera, as part of the scene. In many cases, when actors are shown talking on the phone in movies or TV shows, there is actually no one on the other end of the line. Instead, the actor may be speaking to a crew member who is off-camera, or they may be using a pre-recorded voice that they can respond to.

[0003] As there are many viewers, any inconsistencies between what is shown on the screen and the storyline or plot of the TV show or film is likely to be spotted and commented on, perhaps on social media, or in film reviews, and may detract from the viewer experience and authenticity of the scene. Such inconsistencies could include for example that that time shown on the device screen does not match the time according to the plot of the scene; the device battery power drops or increases between contemporaneous scenes without explanation, or other inconsistencies.

[0004] Additionally, what is shown on the smartphone screen may form part of the plot or story line. For example, in a scene where a character needs to make an emergency call, it may need to be shown that there is no signal or that the phone battery is flat, or that the phone rings but is not answered. Modern smartphones laptops or like devices have many different functions and apps, and so device use is complex. Every time a scene needs to be filmed there are many personnel involved and hourly costs are high, so it is expensive and delays production if scenes have to be repeated due to inconsistencies between communications device usage and the plot or storyline. Further, sometimes the errors are not spotted until the scene has been recorded, and it is not economicor practical to repeat a scene, in which case any errors in the communications device screen view may be rectified during post-production, being the final stage in film and programme-making where footage is cut, music, sound and commentary are mixed and visual effects are added.

[0005] Specific methods and embodiments according to the present invention aim to provide a way of configuring a computing device, such as a smartphone, tablet, laptop, desktop or the like to operate in a pre-configured manner using user inputs to initiate a pre-configured sequence of screen views wherein the creation of such pre-configured screen views may be messages, screen views.Summary of the Invention

[0006] According to a first aspect of the present invention, there is provided a communications device comprising: an outer casing; a data processor; a memory device; a data bus; a display screen; a user interface for receiving user commands; and a native operating system, said native operating system having one or more native application programs, wherein each said native application program comprises means for generating a corresponding respective set of native Screen Views; characterised by comprising: a configurator for generating a sequence of Screen Views and Actions which are run on said communications device; said screen views comprising a plurality of individual Screen Views which are generated to be run in overlay to said native application programs in response to said Actions.

[0007] Preferably, said configurator is operable to configure:pre-settable actions which cause progression between successive screens views through said sequence of screens views; and pre-settable actions which cause progression of content within individual said Screen Views.

[0008] Preferably when a sequence of Screen Views is being run, said configurator generates said Screen Views instead of a set of native Screen Views of said native applications.

[0009] Preferably, when a sequence of Screen Views is being run, running said sequence overlays the normal communications operation of native communications applications of said communications device, and the sequence runs in parallel to native operations of the host device.

[0010] Preferably said configurator is operable to configure predetermined device settings which indicate predetermined operating parameters of said communications device.

[0011] Preferably said configurator comprises: a Flow creation module for creating one or more Flows, each said Flow comprising a said sequence of Screen Views and Actions; a Messages configurator for configuring one or more messages within a said Flow; a Voice Call configurator for configuring one or more voice calls within a Flow; a Contacts configurator for configuring one or more contacts; and a Run module for executing a said Flow.

[0012] Preferably said screen configurator comprises a Device Settings configuration module for pre-configuring device settings in one or more Screen Views.

[0013] Preferably said screen configurator comprises a Flow library for storing one or more Flows, each Flow comprising a said sequence of Screen Views.

[0014] Preferably each Flow comprises a set of one or more Screen Views, and / or sequences of Screen Views which, when said Flow is running, are arranged to be generated by a set of predetermined actions. The Screen Viewsand / or sequences of Screen Views can be pre-configured so as to run in a predetermined order, or the Screen Views and / or sequences of Screen views can be pre-set to be activated by Commands, so that a user can call or trigger a next step in a Flow in a different order should they wish to do so by entering a Command on the touch screen interface when the flow is being executed / run.

[0015] Each sequence of Screen Views may comprise individual Screen Views selected from the set:- Message Screen View;- Voice call Screen View;- Contacts Screen View; and- Photo Screen View.

[0016] Each said Message Screen View may comprise a layout having features selected from the set:- an incoming message text box; and- an outgoing message text box.

[0017] A said Voice Call Screen View may comprise a view selected from the set:- a phone keypad having number icons; and- an “on hook” icon and an “off hook” icon.

[0018] A said sequence of Screen Views may be executed by a touch command on said touch sensitive user interface.

[0019] Preferably each said sequence progresses from an earlier screen in said sequence to a successive next screen in said sequence in response to a pre-configured Action selected from the set: a touch command entered on a touch sensitive screen of said device; a timer delay; and a remote activated command received over a wireless communications link from a remote computing device.

[0020] Said Screen Views in said sequence may be arranged in a predetermined order of generation, which the order cannot be changed by a user during execution whilst said sequence is being executed. Alternatively, the order in which individual Screen Views, or individual sequences of Screen Viewscomprising a Flow can be generated in that Flow may be user selectable by entering user Commands during the execution of a Flow. A user can call or trigger a next step in a Flow in a different order upon entering a Command, provided the Screen Views are included in the Flow as configured and saved.

[0021] Preferably in each said sequence comprising a predetermined Message the text and character content of said Message is pre-set and cannot be varied by a user whilst said sequence is being executed.

[0022] Preferably within each said sequence the layout, content, and order or appearance of said Screens is pre-set and cannot be altered by a user during execution of said sequence.

[0023] Each said sequence may comprise a predetermined sequence of Voice Call screens which are pre-set and cannot be changed whilst said sequence is being executed. Alternatively, Voice Call screens can be navigated by a user during execution of Flow in response to commands entered to the host device by the user.

[0024] Within a said sequence, the timing of changes to Screens within the sequence may be pre-configured prior to running the sequence.

[0025] Within a said sequence, the timing of changes from a preceding stage of the sequence to a successive stage of the sequence may be pre- configurable to be activated by a touch command of a user during execution of the flow.

[0026] A sequence may be configured such that during execution of said sequence, a predetermined order of generation of successive Screens in said sequence cannot be changed.

[0027] Alternatively, a sequence may be configured such that during execution of said sequence, an order of generation of successive Screens in said sequence may be controlled by entry of user commands.

[0028] A said sequence may be activatable by a remote command received from a remote computing device.

[0029] Preferably the communications device comprises a hand-held or wearable communications device, for example a smartphone.

[0030] According to a second aspect there is provided a method of operating a host communications device, said method comprising: generating a sequence of Screen Views; wherein each said Screen View is predetermined to be generated in response to a predetermined action.

[0031] An order of generation of said Screen Views may be predetermined.

[0032] An order of generation of said Screen Views may be determined by user command inputs during execution of said sequence.

[0033] Preferably each said Screen View comprises predetermined display content which cannot be changed once said sequence of Screen Views has commenced running.

[0034] Individual messages within a said Screen View are predetermined to be generated in response to a predetermined action type.

[0035] Preferably individual said Screen Views all selected from the set: Message screens;Voice Call screens; and Contact screens.

[0036] A said Message screen may comprise a Message area for displaying incoming and outgoing messages and a Keypad display.

[0037] Preferably said device settings are selected from the set:- signal strength;- battery power level;- service provider;- time; and- date.

[0038] Preferably a said predetermined action is selected from the set: a user command from a user of said host device input via a touch sensitive user interface; a command generated by a timer component of said host device itself after a predetermined time;a command generated by said host device itself in response to a sensor of said host device detecting a movement of said host device; a command generated by said host device itself in response to a sensor of said host device detecting a proximity of said host device to a user’s head; and- a remote command from a remote computing device, said remote command being received over a wireless link.

[0039] When said sequence of screens is being run, running said sequence may overlay the operation of native communications applications of said communications device.

[0040] According to a third aspect there is provided a method of configuring a host communications device to run a pre-configured sequence of communications, said method comprising: creating a Flow comprising sequence of a plurality of Screen Views to be generated; setting a set of Actions to control generation of each individual Screen View of said plurality of Screen Views in said Flow; and setting a content of each individual Screen View within said Flow.

[0041] Said method may comprise setting an order in which each individual Screen View of said plurality of Screen Views is generated within a said Flow.

[0042] Said method may further comprise: setting a mode of activation of each said Screen View in said Flow, wherein said mode of activation is selected from the set: activation by a timer, after a predetermined time; activation by a user input to a touch screen or physical keypad; activation by a remote wireless signal received from a remote computing device.

[0043] Preferably said method comprises setting a set of Device Settings common to each Screen View generated in said Flow.

[0044] Preferably said Device Settings comprise settings of parameters selected from the set:- battery power level;- signal strength;- service provider;- time; and- date; wherein each said pre-set Device Setting indicates a parameter level represented by said Device Setting, and which does not correspond with a true status of a corresponding parameter according to a native parameter of said host device.

[0045] Said setting of a content within each individual Flow may comprise setting content selected from the set;- Text content;- Photo content; such that during execution of said Flow said content appears in a predetermined order as set, and such that the content cannot be varied during running of said flow, and wherein the timing of the appearance of said content can be varied during running of said Flow by a set of commands.

[0046] Particularly, although not exclusively, the invention relates to a method for configuring a mobile phone to mimic or replicate a normal communication operation and functionality of the phone by creating a predetermined “false” operation of the phone as viewed on a user interface screen of the phone.

[0047] Providing a host communications device in which the selection of Screen Views and in which the progression of Screen Views is pre-set up and pre-configured, and which can be activated either remotely or by commands of the user when the sequence of Screen Views when being run enables efficiency of production on film and TV sets and reduces the need for repeat shooting of a scene due to decisions to change the content of the dialogue represented by the host device.

[0048] By providing a host communications device on which the sequence of predetermined screens is editable on the device itself, changes to screen sequences can be made on set enabling continuation of filming or recording ofscenes with minimal disruption to filming and avoiding the need for editing of screen content in post-production.

[0049] Other aspects are as set out in the claims herein.Brief Description of the Drawings

[0050] For a better understanding of the invention and to show how the same may be carried into effect, there will now be described by way of example only, specific embodiments, methods and processes according to the present invention with reference to the accompanying drawings in which:Figure 1 herein illustrates schematically a portable host communications device according to a first specific embodiment;Figure 2 herein illustrates schematically an internal firmware architecture of the host communications device of Figure 1 herein;Figure 3 herein illustrates schematically a layout of firmware module layers of the communications device of Figure 1 herein;Figure 4 herein illustrates schematically a top level architecture of a Flow Configurator component of the host communications device;Figure 5 herein illustrates schematically sub-components of the Flow Configurator of Figure 4 herein;Figure 6 herein illustrates schematically processes carried out by the Flow Configurator for creating a Flow;Figure 7 herein illustrates schematically a Home Page configuration interface of the Flow Configurator used for creating a Flow;Figure 8 herein illustrates schematically an Add Flow configuration interface of the Flow Configurator for creating a Flow;Figure 9 herein illustrates schematically the Home Page configuration interface after having added a Flow and given the Flow a name;Figure 10 herein illustrates schematically a Device Settings configuration interface enabling a user to configure Device Settings common to all Screens within a Flow;Figure 11 herein illustrates schematically a further portion of the Device Settings configuration interface of Figure 10;Figure 12 herein illustrates schematically a further view of the Device Settings configuration interface of Figure 10 herein,Figure 13 herein illustrates schematically a Module Selection configuration interface for implementing a Build mode for creating or building a Flow;Figure 14 herein illustrates schematically an Add Contact configuration interface within the Device Settings configuration interface;Figure 15 herein illustrates schematically a Device Contacts configuration interface for setting up contact details for use within a Flow;Figure 16 herein illustrates schematically a Contacts configuration interface having icons for setting up incoming and outgoing voice calls within a Flow;Figure 17 herein illustrates schematically an Incoming Call configuration interface for configuring an Incoming Call within a Flow;Figure 18 herein illustrates schematically a further view of the Incoming Call configuration interface set for a secondary action and a hang up delay applied to a first call;Figure 19 herein illustrates schematically the Incoming Call configuration interface of Figures 17 and 18, used to set up a second Incoming Call for Flow;Figure 20 herein illustrates schematically the Incoming Call configuration interface of Figures 17 to 19, used to set up a third Incoming Call in a Flow;Figure 21 herein illustrates schematically an Outgoing Call configuration interface for configuring an outgoing call in a Flow;Figure 22 herein illustrates schematically the Outgoing Call configuration interface a set up for a second example outgoing call;Figure 23 herein illustrates schematically an Outgoing Call configuration interface set up for a second outgoing call;Figure 24 herein illustrates schematically an Outgoing Call configuration interface set up for a third outgoing call;Figure 25 herein illustrates schematically an Outgoing Call configuration interface, in which three calls have already been created within a Flow and are available for execution;Figure 26 herein illustrates schematically a Contacts screen generated within a Flow from which a contact can be selected;Figure 27 herein illustrates schematically an Individual Contact screen generated within a Flow;Figure 28 herein illustrates schematically an Active Call screen generated within a Flow;Figure 29 herein illustrates schematically a Call Ended screen generated within a Flow;Figure 30 herein illustrates schematically a Keypad Screen generated within a Flow;Figure 31 herein illustrates schematically a Messages configuration interface showing a Conversation Messages Setup icon for setting up a sequence of one or more message screens to be generated during a Flow;Figure 32 herein illustrates schematically a second interface for Conversation Messages having options for setting up a push message and setting up a live message;Figure 33 herein illustrates schematically a live message interface for setting up Live Messages;Figure 34 herein illustrates schematically the Conversation Messages configuration interface, showing that four live messages have been set up and are available for use within a Flow;Figure 35 herein illustrates schematically a Push Message interface for setting up a Push Message;Figure 36 herein illustrates schematically a Messages screen generated within a Flow showing three available messages;Figure 37 herein illustrates schematically a Message Screen View within a specific example Flow as the Flow is run;Figure 38 herein illustrates schematically the Message screen of Figure 37, additional text content following on from the Screen View of Figure 37; andFigure 39 herein illustrates schematically a Home Page Screen View generated within a Flow showing a Push Message superimposed on the Home Page.Detailed Description of the Embodiments

[0051] There will now be described by way of example a specific mode contemplated by the inventors. In the following description numerous specific details are set forth in order to provide a thorough understanding. It will be apparent however, to one skilled in the art, that the present invention may be practiced without limitation to these specific details. In other instances, well- known methods and structures have not been described in detail so as not to unnecessarily obscure the description.

[0052] In this specification the term “computer device” includes all electronic devices having a microprocessor, memory, data storage, communications interfaces, and includes amongst other things, desktop computers, laptop computers, notebook computers, mobile phones, smartphones and the like.

[0053] In this specification, the term “mobile communications device” includes any hand portable / human user portable communications device having an email, messaging and / or voice call capability including but not limited to mobile phones, electronic notebooks computers, laptop computers and the like.

[0054] In this specification, the term “configuring user” is used to refer to a person or persons who configures the Flows for execution on the apparatus described herein, and the term “user” is referred to a person who uses the approach is described herein when it is running or executing a Flow sequence of screens.

[0055] In this specification, where the term “native” is used, it refers to a feature or component either in hardware, firmware and or software of a proprietary or generic operating system, and / or computing platform and / or communications device available in the prior art.

[0056] In this specification the term “build” when referring to a Flow means the process of configuring or setting up one or a plurality of Screens which can then be saved and run as or within a Flow.

[0057] Referring to Figure 1 herein, there is illustrated schematically a mobile communications device 100, such as a smartphone. The device comprises an outer casing 101 ; a touch sensitive screen 102; an on / off pushbutton switch which may protrude through the outer casing; a volume up switch which preferably protrudes through the outer casing; and a volume down switch which preferably protrudes through the outer casing.

[0058] Referring to Figure 2 herein, there is illustrated schematically internal components of the communications device 100. The communications device further comprises an application processor 200 comprising a microprocessor control unit 201 , a read only memory (ROM) 202, and a random access memory (RAM) 203; a cellular baseband module 204 comprising a microprocessor control unit 205; a digital signal processor 206; an allocated read only memory 207, an allocated random access memory 208; a cellular radio frequency transceiver 209; a subscriber identity module (SIM) card 210; a Bluetooth® module 211 , the Bluetooth® module comprising a radio transmitterreceiver, a central processing unit 213, an allocation of read only memory 214 and an allocation of random access memory 215; a wireless local area network (WLAN) 216, comprising a radio transmitter receiver 217, a central processing unit 218; an allocation of read only memory 219; a Global Positioning System (GPS) module 221 , comprising a radio transmitter receiver 222, a central processing unit 223, an allocation of read only memory 224, and an allocation of random access memory 225; liquid crystal display (LCD) screen 226; a power supply such as a rechargeable battery power supply 227; and a data and communications bus 228 enabling each of the components and modules to communicate with each other using digital electronic signals.

[0059] Although the microprocessor control unit is shown as discrete components in Figure 2, these components may comprise discrete separate physical components, or may comprise the same physical component, configured to act as two separate microprocessor control units. In the best mode, preferably there are two separate processors (also known as "cores"). One is designed for handling high-performance tasks, while the other is optimized for power efficiency. The combination of these two processors allows for a balance of performance and battery life in a mobile phone.

[0060] The read only memory is that part of the memory which contains the instruction codes or executable instructions that are necessary to run thedevice or module. Whilst the read only memory Devices are shown as separate discrete components, the read only memories may comprise separate individual components, or may comprise a single read only memory partitioned source to allocate separate areas of ROM to the application processor, cellular baseband module, Bluetooth® module, WLAN module and GPS module.

[0061] The RAM is a volatile memory, which is cleared of data when the phone is turned off. The phone processor(s) use RAM to store and quickly retrieve data which it would take a longer time to load if central processing unit had to load data from ROM data storage. The RAM reads and writes data faster than internal storage.

[0062] The data bus 229 allows the different modules and components to communicate with each other and also supplies power to the modules and components which require power.

[0063] The LCD screen 226 whilst providing a display, also allows for touch sensitive use. The LCD screen is covered with a transparent sheet having a grid array of transparent conductors, whereby the static electricity from a person’s finger is enough to generate a signal in the transparent conductors in the vicinity of the person's finger, which is an interpreted as a two-dimensional position on the screen by the application processor 200 in order to accept tactile commands such as a touch or swipe.

[0064] The radio frequency transmitter-receiver performs two functions. The transmission device drivers write the data to be transmitted in the memory from where the radio operating system components collect them from for example audio for a microphone or image / video from a camera, and position from the GPS module. These data points are then processed by the modem processor according to the transmission protocol used. Transmission is initiated by the radio interface through the transparency hardware and accordance with the information stored in the SIM card 210.

[0065] The receiver hardware, which is part of the baseband processor, receives incoming signals and generates interrupts for the radio interface and the operating system. Both the radio interface and the operating system software run on a baseband or modem processor. After reception, a handshake takes place,then the incoming audio, video and data are processed by the modem processor. The radio operating system components talk to the peripheral device drivers to give the incoming data to the user through the device display, speaker and other user interface components.

[0066] The application processor executes the user applications and related operating system programmes. Applications can include audio, video and players, games, image processing, speech processing, Internet browsers, text editors, messaging services, contacts libraries and the like.

[0067] Typically, the volatile memory in the SD RAM can be in the range of 1 to 2 gigabytes, and there is a larger amount of non-volatile storage in the read only memory, typically more than 10 gigabytes.

[0068] The operating system maybe an Android®, or an Apple® operating system.

[0069] The peripheral input / output (I / O) devices, such as the screen, microphone, speaker and phone jacks and the USB port provide for interaction with a user. Each peripheral I / O device requires its own dedicated software driver. Typical peripheral devices include the liquid crystal display, the touch screen, camera, GPS, speaker, microphone, Bluetooth®, and Wi-Fi.

[0070] The processors are preferably Advanced RISC Machine (ARM) processors which are optimised for trading off low power consumption against performance and have a low physical area count and relatively low transistor count, to avoid excessive battery drain. Typically, such process is run at a speed of between 1 .2 GHz and 2.5 GHz clock speed and are multi-core, either two core or four core.

[0071] Referring to Figure 3 herein there is illustrated schematically a layered software stack architecture 300 for the communications device, based upon an Android® operating system having a Linux® kernel.

[0072] At a first layer, 301 a Linux® kernel comprises code for all the numerous chip architectures and device drivers it supports, in addition to controlling processes, memory, and power management of the microprocessor control units 201 , 205. Cameras, Bluetooth®, Wi-Fi, flash memory, USB, and audio drivers are also controlled by the Linux® kernel. Modules within the Linux®kernel include a display driver 302 for driving the LCD d isplay 102; a camera driver 303 for operating and driving the camera device; a keypad driver 304 for receiving and interpreting key pad instructions from tactile inputs on the touch sensitive screen, corresponding to icons displayed on the LCD display; a power management module 305 for managing device power, sleep power modes, standby power modes and battery charging; a Binder (IPC) driver 306 for the Binder Inter-Process Communication mechanism is a device driver-based IPC mechanism that is used in Android® which allows a process to maintain knowledge of a remote object, without forcing it to stay around. The Binder driver is an Android® addition to the Linux® kernel. Proximity sensors are provided in the Linux® kernel layer which are sensitive to light, so that when obscured by being covered by a hand or by being near a User’s head a proximity signal is generated.

[0073] A hardware abstraction layer 308, comprises a Bluetooth® module 309 for sending and receiving commands instructions and messages using the known Bluetooth® protocol; a GPS module 310 which may send to and receive signals from a GPS satellite system.

[0074] At a third layer 315, there are provided a set of native libraries 316, and a set of Android® runtime libraries 317. The native libraries comprise an SQLite library 318 being an open source database provided in Android® and comprises a lightweight and compact database that does not require a server to run; a WebKit library 319 being a static library for using Android® webchat APIs that are not available for older platform versions; an Audio Manager library 320; a Free Type library 321 ; an SSL library 322; a Service Manager library 323; an open GL / ES library 324; and further libraries 325.

[0075] The Android® runtime libraries comprise core libraries 327; and ART (Android® runtime) libraries 328. Android® runtime (ART) is the managed runtime used by applications and some system services on Android®.

[0076] An Android® framework layer comprises an activity manager module 330; a package manager 331 ; a resource manager 332; a window manager 333; a location manager 334; a content providers module 335; anotification manager 336; a telephony manager 337; and a view system module 338.

[0077] An Android® applications layer 340 comprises native Android® applications 341 ; third party applications 342; and other Android® compatible applications 343.

[0078] In this following description, there are referred to various user interfaces which are touch sensitive to user inputs. These user interfaces comprise a liquid crystal display (LCD) or LED display or the like, which displays letters, icons and visually identifiable figurative displays, and overlaying the liquid crystal or LED display there is provided a transparent grid of electrical conductors, the X, Y coordinate positions of which indicate a position on the screen, and the touching of which causes current in the grid of conductors due to the static electricity of a person's finger pointing at an icon displayed by the display immediately underneath the conductive grid which is interpreted by the keypad drive 304 in a known manner. The touch sensitive user interfaces may be used (a) during the normal operation of the communications device, in which case the touch sensitive user interface has full functionality to interact with the underlying settings, applications of all types, libraries, camera controls, Bluetooth®, graphics, Wi-Fi and GPS functions as provided by the normal operating system of the communication device in known manner when the Screen Configurator is not in use (i.e. normal communications device operation as known in the prior art); (b) configuration of Flows in the Device Settings in which case configuration of functionality is restricted to call upon the underlying component layers of the communications device as shown in Figure 3 herein, in which case commands are accepted for configuration of screen views and screen displays in Flows, with some access to the underlying component layers, for example the Bluetooth® module 309 and the Wi-Fi module 313, in accordance with the specific methods described herein, and (c) to operation within a running Flow in which case only selected commands may be acted upon, and which provide for operation of the limited functionality activated by user input touch commands provided for within a running Flow according to the specific implementations described herein.Architecture

[0079] Referring to Figure 4 herein, there is illustrated schematically a Flow Configurator 400 which resides within the overall system architecture of the mobile communications device at the Applications layer 340, and which can call upon and interact with functional modules of the mobile communications device at lower layers comprising display driver 302, keypad driver 304, Bluetooth® module 309, and Wi-Fi module 313.

[0080] Flow Build Configurator 402 is used to build or create top level Flows using the native OS applications for Messages 403, Phone 404 for voice calls, and Contacts 405. Other native OS applications such as Email may also be included. For each Flow created, behind the Flow is a native application functionality of the native operating system of the host device, and the Flow is built on top of the native application, using a developer interface to provide screen generation and screen functionality provided in the native communications applications of the host device, but without the back end communications functionality of sending and receiving Messages or Voice Calls over a mobile phone network, Wi-Fi connection or the like. Core controller 406 controls execution of the Flows once they are built by the Flow Configurator, as well as controlling the interaction between the Flow Build Configurator and the underlying native modules for messages 403, phone voice calls 404, and contacts 405.

[0081] All incoming and outgoing Messages, creation of messages, user input of messages, voice call dial ups, incoming and outgoing voice calls and operation of incoming out and outgoing voice calls as seen on screen during running of a Flow do not actually result in those Messages, Voice Calls being transmitted through a telecommunications network or the Internet. The Message handling procedures and views generated in the screen views do not activate the underlying message sending and receiving functionality of the native messaging application on the host device. The Voice Call handling procedures generated on the Screen Views within a flow do not use the underlying voice communication capability of the native Voice call functionality on the host device and no voice calls are actually made.

[0082] The generated screen views within the Flows relate to the user functionality of the host device for handling a message, voice call as if a real message, voice call were being made or received. However, the user inputs to the user interface e.g. via the touch sensitive screen, serve to navigate through the individual screen views within a Flow, being a sequence of screen views without activating any of the underlying native telecommunications functionality or messaging functionality provided by the host communications device. The Screen Configurator provides and overlay using its own screen layouts provided in the Screen Configurator to mimic the native telecommunications voice call or text message screens provided by the host communications device, but to provide pre-configured messages and screens and with pre-configured navigation routes through the generated pre-configured screens, within a flow and to provide progression of actions and events within each Screen View.

[0083] Referring to Figure 5 herein, there is illustrated schematically components of the Flow Configurator of Figure 4 herein. The Flow Configurator comprises a Device Settings configuration module 501 for configuring device settings applicable to Screens and Flows; a Message Configuration module 502 for configuring message screens; a Voice Call configuration module 503 for configuring voice calls within flows; a Contacts Configuration module 504 for configuring contacts; a Screen Library 505 which contains layouts for screens; and a Flow Library 506 for storing and saving completed or part completed Flows.Screen Views

[0084] A Screen View comprises a screen generated by the underlying native hardware abstraction layer graphics module 312, display driver 302 in accordance with instructions created by Screen Configurator 343 and includes the visual layout of screens, into which content information, such as telephone numbers, photographs, e-mail addresses, can be displayed. Screen views are flexible with respect to the content information which they can display, but the screen views themselves comprising the architecture of the screen view is preset for each screen view. The architecture of each screen view includes the layout of the screen view and any sub-features of the screen view, for example an active keypad interface, an active On Hook / Off Hook icon, or an active phone icon withina screen view. Individual active touch sensitive features of each Screen View may be enabled to accept such commands or disabled to ignore touch commands by using the Flow Configurator as described herein.Actions

[0085] An Action is a pre-configured event to be carried out within a Flow, including actions to commence and terminate a Flow. Actions comprise the following:- Starting a Flow running / executing- Moving between a screen and the next screen within a Flow- Initiating a Dial up for a Voice Call- Initiating an Answer to a call- Initiating a Hang Up to a call- Initiating an incoming message- Initiating an outgoing message- Generating each character within a Message- Generating screens for any of the following:Incoming Message, Outgoing Message, Incoming Call; Outgoing Call; Contacts.Commands

[0086] A Command something which initiates an Action, and can be either:- a User input to a host device when a Flow is executing, for example a touch screen input (a user initiated Command);- a predetermined command which is pre-set pre-configured within a Flow, for example including a time delay to hang up a call, or a time delay to generate an incoming Message;- a remote Command, for example a command generated by the user of a remote computing device when a flow is running on a host device and received over a wireless connection to initiate an action on the host device;- a Proximity command which initiates and Action due to movement of the host device, and / or when in proximity to a user’s head.Flows

[0087] All individual actions are allocated into Flows, where a Flow comprises a predetermined set of Screen Views and a sequence of predetermined / pre-programmed Actions to be run in a predetermined order on Screen Views on the device. Each Flow may be used for an individual scene in a TV or film, and so if an individual set of screen views on for example a smartphone needs to be set up in a particular way to suit a particular scene, that would be pre-configured as a Flow. Any number of Flows may be created using the Core Controller, subject to memory and data storage capacity limitations. Each Flow has a first screen view and a last screen view and may have one or a plurality of screen views between said first screen view and said last screen view. The Screen Views and Actions together make up the Flow and are preconfigured when setting up / configuring the Flow.Configuration of Flows and Execution of Flows

[0088] Each Flow is configured by a user (a configuring user) such as a TV or film crew member and is saved to the host communications device on which it will be executed. The Flow is created on the host communications device on which it is to be run.

[0089] A Flow is initially created and configured by a configuring user, saved to the host device on which it will be run, and then run during a TV or film scene. Ideally, the scene will be recorded correctly the first time, showing the Flow without any errors or mistakes. However, if it is necessary to change the Flow to correct errors or due to script changes during filming / recording, then the Flow can be edited relatively quickly on site using the Flow Configurator which can be hosted on the host communications device on which the Flow being run, or on a remote computer device.

[0090] The Flow is executed on the host communications device either by a second user such as an actor, when a scene is being filmed or recorded and / or by remote commands from a remote computing device over a wireless link. Within the Flow, movement from one Screen to the next can be user activated by touch commands entered by the user to the host communications device running theFlow, or by preset timings configured as part of the Flow, or by remote commands from a remote computing device.

[0091] Within individual screens, changes to content are pre-set during configuration by the configuring user. During execution, the content of individual screens cannot be changed by the user of the host communications device while the Flow is running. Any changes to the content of the Screens or the order in which the Screens appear within the Flow require that the Flow is edited using the Flow Configurator, and the amended Flow is re - executed.

[0092] If editing of the Flow is required during filming, the configuring user needs to activate the Screen Configurator, select the Flow to be edited and select Edit from the user options to re-configure or edit the Flow. The edited Flow can then be re-saved and executed, to continue filming the scene. For changes to the Flow this can be done on-set which means the scene can be recorded with the correct appropriate screen visuals without the need to edit the scene in postproduction after filming or recording has taken place.

[0093] Changes to the Flow can include changes to any of the Screen views in the Flow, any of the content within the Screen Views, and any of the Actions which lead from one screen view to the next. Changes can also include adding or removing any Screen View or sequence of Screen Views to the Flow. Changes to the Flow are made on the host communications device on which the Flow has been created and on which the Flow is run.Creating a Flow (Configuration of a Flow)

[0094] A Flow comprises a set of Screen Views and a set of Actions relating to those Screen Views. The Actions determine the order in which a sequence of Screen Views are presented, their timing in relation to each other, and act for starting and finishing the generation of the Screen Views. A Flow is created using the Flow Configurator. The Flow Configurator accesses existing native operating system functions such as a native Messages application, and native Contacts application, and a native PhoneA / oice Call application to provide the basic screen layout infrastructure but replaces the normal operation of the native application with functions generated by the Flow when the Flow is being executed or run.

[0095] Referring to Figure 6 herein, there is illustrated schematically one example of a process 600 carried out by a configuring user to set up a Flow using the Flow Configurator module. In process 601 , the user sets up the type of screen which the communications device is to generate and display. The screen type can be selected from one or a plurality of predetermined and pre-configured screen types which may be set up to mimic a particular type of device or operating system, for example to mimic an iPhone®, an Android® phone, or a non-descript copyright royalty free device. In this example, the configuring user sets up a Flow where the host device generates a Contacts screen a user looks at a contact, and then the Flow generates a voice phone call from a contact screen. In process 602, the user sets up one or more contacts in the Contacts module. In process 603 a configuring user sets the Actions command types which are used to progress through the Contacts screens during the Flow, which can be either user touch commands, pre-timed movements according to an automated timer, or on receipt of external commands from a remote computing device. The progressions through the Flow include changes to content within each Screen and movement from one Screen to the next. Movement from one screen to the next during execution by the user is a forward-only sequence, meaning that the Screens appear in a predetermined sequence and the user progresses from one Screen to the next in the predetermined order, and within each Screen the content changes in a predetermined order. User control during execution of a Flow is limited to commands to move through the Flow from one Screen to the next and to add content within a screen. In process 604, the configuring user sets up screens for a voice call to be included in the Flow. In process 605, the configuring user sets up Actions to be carried out during the voice call part of the Flow. The Flow is saved 606 in the Flow library 506 to be executed on Command.

[0096] Referring to Figure 7 herein, let me show schematically a Home Page configuration interface 700 of the Flow Configurator used for creating a Flow. On the Home Page, a configuring user can set up device settings using a Device Settings Menu 701 and can set up Flows using a Flow Menu 702. In the example shown, no Flows have been created yet.

[0097] Referring to Figure 8 herein, there is shown schematically an Add Flow configuration interface 800 of the Flow Configurator for creating a Flow as part of the Flow Menu. The Add Flow interface allows a configuring user to create a new flow and name the new Flow. A pop-up keypad 801 is used to enter the Flow name and an Add icon adds the Flow to the Flow Library.

[0098] Figure 9 herein illustrates schematically the Home Page configuration interface after having added a Flow and given the Flow a name. In this case, the flow is named “Scene 1” and there are icons which the configuring user can activate to run the Flow (Go Live) 901 , Build the Flow 902, delete the Flow from the Flow Library 903, and to rearrange 904 the order of the Flow in a list of Flows.Device Settings

[0099] The screen configurator mimics various different communications devices, for example different smartphone types, on the host communications device. The device settings are highly customizable to make the screen on the physical host communications device look like any type of smartphone, or equivalent communications device from a variety of models and from a variety of manufacturers.

[0100] In a Device Settings configuration interface generated by the device settings configuration module 501 a screen type can be selected from a range of Screen Types, including Android®, Apple®, or other non-descript screen type. Each Screen Type replicates a screen view as generated by a particular type of device, for example an Android® generated screen type, as would be generated by a Native Android® Application 341 , but without using that Native Android® Application.

[0101] Based on the particular type of host communications device or smartphone used, the forward-facing camera 311 may be physically positioned on the same side of the screen on the top right, top left or top centre of the screen. The camera aperture cut out in the Screen type can be selected to match the host device on which the Screen View will be generated.

[0102] Referring to Figure 10 herein, there is shown a user interface 1000 for the Device Settings configuration module. In the Device Settings userinterface individual Flows can be created. The Device Settings user interface includes user-configurable icons for:- Signal Strength icon 1001 is configurable in the Device Settings interface to show any level of signal from empty 0% to full 100%. The signal level is set in Device Settings before the Flow goes live, and remains the same during execution of a Flow;- Battery Power icon 1002 allows the user to pre-configure a battery power level showing on the Flow screen display. The battery power level icon can be set at any level initially and stays the same during execution of the Flow. Optionally, in other implementations, the battery power level may be configured to change incrementally during running of a Flow;- Clock 1003 is configurable to show any time required. In the present implementation, the clock is set in Device Settings and the time does not change during a Flow. Optionally, in other implementations, the clock time may also be configured to change incrementally during running of a Flow. The clock time can be set per Flow, so the different Flows show different times or different progressions of time.

[0103] Other selectable parameters for a Flow include:- a set of Operating System command icons 1004 for selection of an operating system. In the example shown, there are individual icons for selecting an Apple® operating system iOS® 1005, an Android® operating system 1106, or a non-specific generic operating system 1007 to use as the basic background environment for the Flow;- a Camera Cutout Location section 1008 for selecting on the Flow screens where the forward-facing camera cut out will be positioned, with icons for selecting the option of either on the left-hand side of the screen 1009, the centre of the screen 1110, or the right-hand side of the screen 1011 , or no cut out at all 1012;- a System Date section 1013 for selecting a date or dates which will appear in the Flow. Any date can be selected, including dates in the past, present or in the future. The date is set in Device Settings before a Flow goes live and stays the same during execution of a Flow;- a System Time setting section 1014 for setting the time to be displayed in during the Flow. The Flow Time as set using the Device Settings interface is also displayed on the time icon 1003 at the top of the Device Settings interface;- a Battery Level indicator setting section 1015 comprising a slidable selector 1016, for setting a battery level to be displayed during running of the Flow. The battery level is set in Device Settings before the Flow goes live and does not change during running the Flow;- a Service Provider section 1017 for setting a service provider background icon to be displayed during running off the Flow. The service provider can be set to a specific service provider, e.g. EE®, Vodaphone® etc. or can be set to be an imaginary false or made-up service provider;- a Signal Strength setting section 1018 for setting a signal strength to be show during running of the Flow. The signal strength setting is set via a slider icon 1019 between 0% and 100%;- a Font Size setting section 1020 comprising user activatable icons for setting a standard font size 1021 , or a large font size 1022 which will be show during running off the Flow;- the positioning of battery level indicator, signal level indicator, and other indicators such as a service provider indicator along a top section of the screen view.

[0104] Referring to Figures 11 and 12 herein, there is illustrated schematically a lower portion of the Device Settings user interface, accessible by touching the screen of the communications device and scrolling down. The Device Settings interface further comprises:- an optional Navigation Style setting section 1100 for setting how navigation by a user during the running of the flow will be conducted, either by gestures, activated by selecting a Gestures selection icon 1101 , or using buttons as selected by a Buttons selection icon 1102;- a Background Wallpaper section 1103 which maybe pre-populated with a selection of images or photographs to choose from, which will bedisplayed as the background on the screen during the flow, and onto which application icons and other information are added;- a Set Up Bluetooth® Keyboard section 1104 including a Trigger Incoming Call Key selector 1105, and a Trigger Incoming Message Key selector 1106.

[0105] Settings of the above device settings in relation to the amount or level of the relevant corresponding parameter indicated by the signal strength icon, battery power level icon, clock, system date, battery level, service provider and / or signal strength has no correspondence with the corresponding parameters of the host communications device. For example, setting the battery level indicated to display a low battery level does not show the true battery level of the host communications device, unless by coincidence the true battery level just happens to be at the level set in the device settings. Similarly, setting the level of these signal strength indicator to any particular level does not correspond with the actual level of signal being received / sent by the host communications device, except by coincidence. In the general case the settings of the above device settings in relation to the amount or level of the relevant parameter indicated has no connection to the actual level of those parameters experienced by the host communications device.

[0106] Referring to Figure 12 herein, configuring user can test whether the Trigger Incoming Call Key works correctly.

[0107] Referring to Figure 13 herein, there is illustrated schematically a Module Selection configuration interface within a Build mode for building a Flow. The selected Modules generate the Screen Views. In the Example shown, there is an active phone module 1301 and an active Messages module 1302 which can be selected to configure into a Flow.Contacts

[0108] Referring to Figures 14 to 15 herein, in process 602 the Contacts configurator module is operable for setting up one or a plurality of Contacts which can be used within the Flows.

[0109] Figure 14 herein shows schematically the Device Contacts user interface 1400 into which a contact name, phone number and other details canbe entered and saved to the communications device. The device contacts user interface comprises a User Name section 1401 for entering a user's name, which typically would be the person setting up the Flow, or could be the name of an actor who will use the Flow in a scene; an Add Contact section 1402 into which is entered a contact name, optionally a phone number of the contact, optionally a picture of the contact, and optionally a poster image of the contact. The Contact Picture may be retrieved from an image taken by the camera of the device or another device, and stored on the communications device, and similarly, the full screen poster image may be retrieved from a gallery or library stored on the communications device. Full screen poster images are relevant to mimicking an Apple® iPhone® or an iOS® device. Activating the Add icon 1403 adds the contact to a library of contacts stored within the Screen Configurator.

[0110] Referring to Figure 15 herein, once contact details are added, they appear in a Contacts List 1500 along with other contacts. Each listed contact has an associated message icon 1501 , can be deleted by activating a delete icon 1502, and can be re-ordered in order of appearance in the list using a re- order icon 1503 the list which appears next to each individual contact. Each contact is generally a fictitious contact, that is to say the contact person may be a character in a TV scene or film scene and the phone number given maybe a fictitious telephone number which, if dialled would not lead to phoning a real phone. Real phone numbers could be used, but generally would be avoided.

[0111] The message icon 1503 is used to create both received and sent messages, so that when a Flow for a contact, for example Jimmy, is activated to run, the user (actor) will be able to see past messages both sent and received from the contact, and the scripted past history conversation with that contact can be viewed.

[0112] The entire Device Settings, Device Contacts interfaces look the same whether the screen Configurator is being run on an Android® based platform, or on an iOS® based platform on the communications device.

[0113] When running a Flow using the Screen Configurator, the screen view on the communications device will look like an Android® operating system device if that has been selected for the Flow, or will look like an iOS® operatingsystem device if that option has been selected for the flow, or will look like any other operating system selected in the Device Settings module when the Flow is being run, irrespective of what the underlying operating system of the communications device actually is at the device’s operating system layers.

[0114] Typically, a user would not select an Android® background in Device Settings to run a Flow on an iOS® device and vice versa, a user would also not select an iOS® background setting to run on an Android® device, but the options in device settings to select either and Android® or iOS® background are provided so that the screen Configurator can be used on either type of device platform. Similarly, there is the option of a non-descript generic background, which can be used if for legal reasons, e.g. copyright, the background screen view in the Flow cannot be seen to be a proprietary operating system such as Android® or iOS®.

[0115] The Contacts List is available across all Flows, so that a user setting up multiple Flows corresponding to multiple scenes in a TV show or film only needs to set up a contact once and does not have to re-enter the contacts data for each newly created Flow.Font Size

[0116] The font size is generally set to be the same size within each Flow. The font size can be set to a large font size, for example to show messages on the screen where filming the scene in which the communications device is used requires that the viewers can see the text message clearly, and having a normal size font would be too small to and not give the required visibility. In the preferred implementation, the font size variation only changes the font size within displayed messages and does not change the rest of the font sizes for other areas of the screen.Navigation Style

[0117] Some older version Android® phones have a three-button navigation function, whereas newer version Android® phones have a swipe function in order to navigate. The two options of gestures (swipe) navigation and 3 Buttons navigation are provided in order to replicate either newer or older version Android® phones data both.Backqround Wallpaper

[0118] The optional background wallpaper setting allows a background image to be displayed on screen. The background wallpaper setting is one provided within the screen Configurator and does not affect the background wallpaper setting / image of the underlying communications device when used with its native operating system.Camera Cut Out Position

[0119] Based upon the type of device being portrayed in the Flow, the device may have a user-facing camera located on the top left, top right or top centre of the screen, or may have no camera at all. The location of the camera portrayed in the Flow is set using the Camera Setting section of the Device Settings configurator interface to coincide with the physical position of the real camera on the host device so that the other indicator icons (status bar and time icons) on the same level are re arranged so as not to appear at the physical camera position of the host device. For communications devices which do not have a physical user facing camera on the user screen, the camera-like display icon mimics a user facing camera and the location of the camera icon can be selected from the above locations. For communications devices which are fitted with a physical user facing camera for taking selfies, the camera icon may be set to be not present, as the physical camera on the device screen already provides the appearance of a user facing camera.Time & Date Indicator Position

[0120] As the Camera cut out position is varied from left to right, the location on the top of the screen of the time and date display is also moved so as not to clash with the camera cut out position.Signal Indicator Position

[0121] As the camera cut out position on the top of the screen is varied from left to right to centre, the signal indicator is repositioned automatically by the Screen Configurator so as not to clash with the camera cut out position or with the position of any other indicators, for example time and date, battery power level, or service provider indicator.Other Top Line Indicator Icons

[0122] Normally for a particular device type, if there is a forward-facing user facing camera at the top of the screen then there are icons and indicators also occupying the top of the screen. The position of the other indicators depends upon the physical layout of the screen of the physical communications device and the operating system and operating system version which the communications device is running.

[0123] In order to mimic or replicate a screen view of a particular operating system layout the camera cut out position can be moved from either left to centre to right of the top of the screen when configuring a Flow. When setting a camera cut out position within a flow, other icon types which may be present on the top section of the screen are automatically re-arranged / re-ordered in position along the top section of the screen so as to avoid clashing with the position of the camera cut out. Other icon indicator types may include cloud indicators, Wi-Fi active indicators, Bluetooth® active indicators.Battery Power Level Indicator

[0124] Within a Flow, the battery power level indicator can be set to indicate either a full battery, an empty battery or any level in between. Setting of the battery level indicator has no correspondence at all to the actual battery level of the communications device, but rather is a dummy or false battery level presented as an overlay to the actual device battery level, to be consistent with the story line of the scene to which the Flow is being created to match. Within a Flow, the battery level indicator can be configured to reduce or increase over time as required by the storyline of the scene being filmed / captured.

[0125] The level at which the battery power level indicator is set to show within a Flow has no connection or bearing to the actual battery power level of the host device and is displayed instead of the native battery power level indicator provided as part of the native operating system of the host communications device.Bluetooth® Setup

[0126] The Bluetooth® settings allow for a second remote device, for example a Bluetooth keyboard, or another mobile phone in connection with thecommunications device using a Bluetooth® link to send a signal to trigger various events during a Flow. This enables a second person on set to trigger for example a message or call during a scene being filmed without the actor having to touch their phone / communications device. For example, Flow itself can be triggered by a Bluetooth® command from a remote device, or an action within a Flow can be triggered from a remote device. In the best mode, events which can be triggered by an incoming Bluetooth® command include triggering an Incoming Call Key or triggering an Incoming Message Key. Pre-configuring of incoming calls and incoming messages is carried out by a user using the Setup Bluetooth® Keyboard section of the Device Settings user interface. For example, a user of the remote Bluetooth® device can press a key (number 1 for example) on the keyboard of the remote Bluetooth® device, which sends a Bluetooth® message to the mobile communications device which in use, triggers a move on to the next part of a Flow being run on the mobile communications device which can be that the device receives an incoming call.Screen View Creation

[0127] Each Screen in a Flow is created as a combination of icons and layouts using the native User Interface (III) applications provided in the operating system of the device, for example the native III creating applications provide in Android®, iOS®, or whichever operating system is used on the device. The views are configured by a developer, and a user of the Screen Configurator has no control over the layout of the Screen View other than by requesting a developer to modify the view. Any configuration of the screen view is a configuration of the basic Screen View as provided in the Screen Configurator at the point of manufacture.Screen Configuration

[0128] The basic visual layout and presentation of each screen it will appear when running a Flow is pre-configured by a developer within the Messages configuration module 502, Phone configuration module 503 or Contacts Configuration Module 504 and is based upon the type of screen presentation or visual layout which would be generated by the native OS application provided by the manufacturer of the host device.

[0129] The user-configurable parts of the screen configuration are provided by the Device Settings module 501 within the Flow configurator 402. The following parameters are configurable within the screen configurator by a user:

[0130] Messages - the user can configure the text content of Messages, including characters such as emoji; the time delays between touch screen inputs of the user to the host device and the appearance of successive characters in a text message in response to those touches; the user can configure the time delay before receiving an incoming response text message from a (virtual) Contact; and how to terminate a text message, whether by time out or by a user touch onto the screen.

[0131] Push Messages - the user can configure the text content of the push message as it is pushed onto screen, as well as the text content of the underlying message. The user can configure whether the Push Message is activated on a timer, during running of the Flow in which it is contained, or whether the Push Message is activated by an external event, such as an externally received signal from a remote device.

[0132] Voice calls, incoming - the user can configure the timing of the incoming voice call, and the hang up of the incoming voice call, that is whether the voice call can be terminated by the user of the host device or whether the voice call terminates by pre-configuring a timer to terminate the voice call. The user can configure the Voice Call to be initiated either:- from a Contact Page;- from a Keypad Page; or- from a Message page.

[0133] Voice calls, outgoing - the user can configure whether the outgoing voice call is activated by the user via the Contacts, or via the Voice Call telephone keypad.User Control

[0134] Setting User control means that a User of the host device will be able to decide when to hang up a call during a Flow. Hanging up a call in a Flow means that the Flow moves on to the next Screen, which could be a phonekeypad screen as shown in Figure 29. In User Control, the user decides when to take the next action in the Flow, by means of a user input to the touch screen.Proximity Control

[0135] When Proximity Control is set anywhere within the Flow, when the Flow is being executed, if the User moves the host device next to their head, the screen will automatically go dark or blank to mimic the known smartphone feature of the screen going blank whenever the smartphone is in the vicinity of the User’s ear. The Flow is configured to use the gyroscope information from the native gyroscope on the host device and / or the proximity sensor to cause the screen to go blank when there is upward movement of the host device, or when a close proximity to the User’s head is sensed. As soon as the host device is moved away from the User’s head the call will be ended in response to that movement. By Call ended, it means that the Flow moves on to the next screen in the series, which is preset to be a Call Ended screen, such as the pre-set home page of the host device in the Flow.Configuration of Incoming Phone Calls

[0136] Referring to Figure 16 herein, there is shown a Voice Calls configuration interface 1600 for creating and configuring voice calls within a Flow. A configuring user creates a new incoming call by selecting a “Create a new incoming Call” menu 1601 on the interface, which leads to a configuration interface as shown in Figure 17 in which parameters of the incoming call can be selected.

[0137] Referring to Figure 17 herein, the selectable parameters for an incoming call include:- a Call Title 1701 ;- an Incoming Contact 1702 being the pre-set Contact from whom the call is to be received within the Flow;- an Action Reguired if the Call is Answered 1703;- a Secondary Action 1704; and- a Hang Up Delay 1705.

[0138] The Action Required if the Call is Answered is the action if the User answers the call. If the User answers the call, then there needs to be a Secondary Action set to determine what happens next in the Flow.

[0139] The Secondary Action can be set from the following:- the User hangs up;- the Caller hangs up;- User Control, which means that it is under control of the User when they choose to hang up;- Proximity Control.

[0140] Referring to Figure 18 herein, there is shown an interface of the Voice Call configuration module 504 in which a call is pre-configured so that when executed or run, the Caller (Contact Jimmy in this case) hangs up after 4 seconds from commencement of the call. This means that when the Flow is running, 4 seconds after the call has been answered, a Screen View showing that the caller Jimmy has hung up will be generated.

[0141] Referring to Figure 19 herein, there is shown an interface of the Voice Call configuration module 503 in which a second incoming call within a Flow is set up. In this case the caller Contact Peter is selected as being the hypothetical incoming caller. Within a Flow, the sequence of screens can be configured to include one or a plurality of incoming calls. For example, when the Flow is set up to generate a first Incoming Call, which is then hung up as part of the predetermined sequence of Flow screens, a second Incoming Call can be pre-configured to occur after the first incoming call. For example, the Incoming Calls can be pre-configured so that every time a user presses the “1” icon on the keyboard, this triggers the next pre-configured incoming call screen sequence to be generated. Again, the pre-configuration is set up so that the configuring user can decide what happens to the second Incoming Call during execution of the Flow. This may be, as before, if it is set to be User control, then the User during execution can decide whether to accept or reject the call, or if Other User Hangs Up is pre-configured, when the sequence is executed, the screen will show that the caller has hung up. The time delay to generate a screen view showing thatthe Caller has hung up can be pre-set using the Voice Call configuration module 503.

[0142] Since the Incoming Call is not a real call made over a public telephone network, but rather a pre-configured sequence of screens set up to replicate the screen views which would be generated in that situation, there is no actual real caller nor actual real contact, but the Flow gives the viewer or User the impression that there is a real call. The Flow replicates the behavior of a communications device during a real call but is actually a predetermined sequence of screen generations.

[0143] Referring to Figure 20 herein there is shown the Incoming Call configuration interface as configured to set up a Flow for a third call in a sequence of screens showing incoming calls. In the third call, a third contact Penelope is selected to show as the caller, the Flow is set so that an action by the User is needed to move on to the next screen after an incoming call screen, and a secondary action of Proximity Control is set so that the call terminates and moves on to the next screen when the proximity sensor detects that the User has placed the host device next to their head. When executed this part of the Flow will show a screen for an incoming call, which the User will accept by touching the touch screen. Then when the User holds the phone to their ear, the proximity sensor in the native sensor set of the host device activates the next screen in the Flow which is a hang up screen.Configuration of Outgoing Phone Calls

[0144] Referring to Figure 16 herein, outgoing calls can be added to a Flow by selecting an Outgoing Calls menu 1602 on a phone calls interface 1600. Selecting an outgoing call leads through to the Outgoing Calls interface 2100.

[0145] Referring to Figure 21 herein, there is shown an outgoing calls configuration interface 2100. The outgoing calls interface comprises a first section 2101 which selects how the outgoing call will be triggered. In this case, the Outgoing Call is set to be activated by selecting a contact from the Contacts module. An Initial Action is set as “control the outgoing call”, which means that when the flow is running, the user will control when to activate the outgoing call. A Primary Action is set to control termination of the call as being Other UserHangs Up. This means that the Flow will show that the recipient Contact subject of the call has hung up rather than the User. A delay section 2102 allows the configuring user to set up a time delay after commencement of the call before the Flow shows the Contact who is recipient of the call hanging up.

[0146] Referring to Figure 22 herein, there is shown the outgoing calls configuration interface set up to control a second example outgoing call.

[0147] The second outgoing call is set to be triggered by selecting a Contact from the Contacts module. The Call is set to be answered by the Contact answering the call (Other User Answers) with a delay of 3 seconds, which means that when the flow is running, the host device will show an outgoing call being made by selecting a contact, and then the outgoing call being answered after a delay of 3 seconds. A Secondary Action is set to be User Control.

[0148] Referring to Figure 23 herein, there is shown the Outgoing Call set up interface which is set up for a second outgoing call. In the second outgoing call, the outgoing call is triggered by the user selecting a contact during the running of the flow, an initial action is set such that the other user answers the call after a delay of three seconds. The interface shown in Figure 23 shows the keypad interface which generates when selecting Hang Up Delay in order to input the number of seconds hang up delay after the call has been answered.

[0149] Referring to Figure 24 herein, there is shown the Outgoing Call configuration interface set up for a third outgoing call in which the call is activated by the user selecting a contact in a preceding screen within the Flow, an initial action of “Other User Answers” is selected, meaning that after a predetermined answer delay, set in this case at 5 seconds, the next screen is generated, showing that the called Contact has answered the call. In this case, termination of the call has been set up such that the Contact called hangs up, which is triggered by proximity control in which the user moves the host device to their head, and then holds the user device low again, which causes the Flow to move on to the next screen which may be a screen as shown in Figure 29 herein where a call has ended.

[0150] Referring to Figure 25 herein, there is illustrated the Voice Calls configuration interface of Figure 16, where three calls have already been configured and are available for execution within a Flow.Example of a setting up a Flow for an outgoing voice call

[0151] Taking as an example configuration of a Flow comprising a plurality of Screen Views generated to depict an outgoing Voice Call, the Flow may be set up as follows:

[0152] The configuring user in the Device Settings module creates a new Flow naming it Scene 1 . The configuring user builds the Flow using the Build icon 902 which leads through to selection of modules from the interface shown in Figure 10.

[0153] Screen View 1 - the configuring user can set up the Flow to initiate the outgoing voice call in various ways from different starting points. All Flows start on a blank / black screen, and then move on to a phone call if reguired and triggered, or to the Lock screen then a Home Screen if user activated. When configuring the device, the configuring user selects the first screen in the Flow (Scene 1 Figure 9) depending on how the voice call is to be initiated. In this example, the configuring user selects the Contacts module (see Figure 14 herein) to add a Contacts Screen as the first screen in the Flow. The configuring user sets up how to move from the first screen as by a user input on the touch screen. When the Flow seguence is run, this will cause the Flow to move on to the second screen in the Flow in response to a touch command on the touchscreen by the user.

[0154] Screen view 2 - Voice keypad screen. The configuring user sets up second screen of the Flow to be a keypad for a Voice Call by selecting the Phone module (See figure 13). When the flow is run, a phone keypad screen (See Figure 30) will be generated as the second screen in the seguence. The configuring user sets how the second screen will accept the next command. The screen is configured so that the next touch of the touchscreen by the user will cause a keypad to appear and so that for each successive touch of the touchscreen, a number will appear in the number bar of the screen. The numbers are preconfigured during set up so that when the Flow is run, wherever the user touchesthe screen, the same sequence of numbers in the displayed phone number will appear. The appearance of the numbers is pre-set so the number appearing on screen is not dependent on the user actually touching the correct number icon on the display. Rather each time the touchscreen interface is touched, the next number in the pre-set number will be generated on the display. The user does not have to hit specific keys for the predetermined phone number to be generated. Therefore, if an actor using the host device types or mistypes a number, the number appearing on screen will still come up with the pre-set number as entered by the configure during set up. In use, the pre-set telephone number is generated and displayed on the screen one character at a time so that when run, each time the user touches the screen, a further character of the number is generated until the full number is present on the screen. A delay is set so that any further accidental touches, or an excessive number of touches after completing the number generation do not cause the screen to move on to the next screen. A delay is set by the configuring user for the Flow to move on to a next screen which is a phone dialling screen.

[0155] Screen view 3 - The third screen in the sequence is a phone number dialled screen or Phone call in progress screen, as shown in Figure 28, I which has icons for Mute, Keypad, Speaker, +add call, Hold, Contacts and Off Hook / On Hook. Screen 3 is pre-set to be maintained either by setting a timer after which the screen moves on to the next screen, or by moving to the next screen in response to a user touching the touch screen to move on to the next screen.Operation in Use - Executing a Flow

[0156] In Figure 3 herein, an example of a communications device based upon the Android® operating system is described. However, the communications device may alternatively comprise an Apple® operating system. The screen configuration modules according to specific methods and implementations according to the invention are applicable whatever the underlying operating system of the communications device. Further the screen configuration module may generate views based upon an operating system which is not the native operating system of the communications device. For example, screen views in a format created by an Apple® operating system may be generated on acommunications device having an Android® or an Apple® operating system, or an Android® screen view or an Apple® screen view may be generated by the configuration modules on a communications device having an underlying Apple® operating system.

[0157] Once a Flow has been created and saved to the memory of the mobile communications device, the Flow can be executed / run. In a TV or film scene, an actor uses the mobile device, for example a smartphone. After configuration there are two ways in which to make the Flow go live for use. Firstly, the user can use the Device Settings interface as shown in Figure 9 and activate the Go Live icon 901 . Secondly, in the Home Page interface as shown in Figure 10, there is Scene 1 Go Live icon which when selected will cause the Flow to become live and ready for use.

[0158] When a Flow is set to being Live, the host device goes into a locked state. This is a default Ready state in which the host device is ready to run a Flow. In a film scene the host device may be in a User’s pocket in the Ready mode wating for the User to take the phone out of their pocket and start the Flow. If the User taps the screen anywhere, and the host device wakes up and shows a Locked screen as if the host device were locked and still in the pocket. The locked screen is the first screen in the Flow. A touch or swipe by the User moves the Flow on to the next (second) screen in the Flow which is a Home Page screen. The Home Page can be set up to be either an iOS Apple® screen or an Android® screen, and can be a non-descript Home Page which is dissimilar to that of any particular manufacturer, or can be a copy of a proprietary brand screen such as a Samsung home page screen. The User may select from the icons presented on the Home Page screen a Contacts icon. Selecting the contacts icon moves the Flow on to the next (third) screen in the Flow.

[0159] Referring to Figure 26 herein, there is shown a Contacts screen of the Flow which in this example has a keypad at the bottom of the screen. This mimics what a conventional phone would do when going into the Contacts screen. In this example, there is one Voice Call pre-set up in the Flow, and the Flow is set up so that the call can be triggered in two ways. In this example, the Flow was set up such that a call would happen, but it was not specified at theconfiguration stage which Contact the call would be made to. In this example the Flow has been pre-configured so that the User can select which Contact to call. The User selects Jimmy in this example form the contacts listed on the Contacts screen.

[0160] Referring to Figure 27 herein, the host device then moves on to the next screen 2700 showing the contact details for contact Jimmy. Dialing up Jimmy can be activated by touching the phone handset icon 2701. In this example the Flow is pre-configured with a delay of 4 seconds before the Flow moves on to the next screen as shown in Figure 28 herein which shows that Jimmy has answered his phone. There is no sound through the host device because the video production team will put the sound on in the scene afterwards, in post-production so the Flow is just the screens. The User can turn the speaker phone up on the screen and the screen shows the increased volume, although as there is no sound activated, nothing can be heard through the host device. All the other icon keys also work, such as Hold or Mute, and when activated by the User the screen icons change to reflect the command, just as with a conventional phone, but the commanded changes do not have any effect on the underlying function of putting the call on hold as the duration of the call is predetermined, and touching the Mute icon does not mute any call as there is no voice call audio in this pre-set example Flow.

[0161] In this Flow example, Proximity is set to end the call so that when the User moves the host device to their ear and then moves it back again, the inbuilt proximity sensor of the host device detects the change in light levels and this is used in the Flow as the command to end the call, meaning that the Flow moves on to the next screen which is an otherwise blank screen as shown in Figure 29 herein, mimicking that the call has hung up. In this example the User decides when to hang up by their action of removing the host device from proximity to their ear, and the next screen in the Flow showing a red telephone icon shows the call has hung up.

[0162] The Flow replicates the screen views which would be generated as if a real voice call had been made but in a predetermined manner and with the User during the Flow only having limited control of the call, and there being noaudio call present. In this example Flow, as there is no specific Contact predetermined in the Flow, but the Contact is set to be User selectable, the Flow could be re-run and this time Penelope could be selected as the contact, in which case the Flow would run through the screen sequence the same as described above but showing Penelope as the contact. The sequence of screens would be the same, the delays the same and the User initiated end of the call would be activated in the same way, independently of how the call Flow is started.

[0163] Similarly, in another example a Voice Call screen can be activated from a preceding Keypad screen as shown in Figure 30 herein by a User touching numbers on the keypad. The number of touches required to move on to the next screen can be pre-configured, and as the User touches the screen for each touch, a number appears in the number box. In one implementation, the keypad is not pre-configured to generate predetermined numbers irrespective of which keypad number icons the user actually touches, but rather generates a display of the number which the user inputs. In other implementations, the Flow can be configured such that it does not matter which numbers the User actually touches as the actual number displayed is pre-set in the Configuration stage.Terminating Execution of a Flow

[0164] To end the running of a Flow, the User swipes upwards on the touchscreen. This command ends the running of the Flow and returns the host device back to its native operation in which the native communications applications 341 resume their native operation.

[0165] Depending upon how the flow has been configured, a Flow can be activated either by the actor touching the screen or by a remote Bluetooth® command from a remote Bluetooth® device operated by a second person.

[0166] Referring to Figures 36 to 38 herein, there is illustrated three individual screen views in a single predetermined Flow. In this example, in Figure 25, a Flow is set up and opened / initiated by a user of the mobile device, such as an actor, by touching the touch screen. Alternatively, the Flow may be initiated by a remote user of a Bluetooth® connected device, by sending a Bluetooth® message to the mobile device. The user touch-swipes the screen of the mobile device to un-blank the device so that the screen content becomes visible to theuser. A first screen in the flow shows a home page screen, with a messages app icon, amongst other icons, and the signal level, battery power meter and time and / or date. The user touches specific icons on the screen which causes the running Flow to move on to the next screen as shown in Figure 25. Touching a specific icon causes the Flow to move on to the next screen view. In the view shown in Figure 25, the pre-written Flow is to answer a message from contact Penelope. To move to the next screen, the actor touches the Penelope part of the screen, which moves the Flow on to the next view.Configuring a Flow containing a message screen sequence

[0167] Referring to Figure 31 herein is showna Messages configuration interface 3100 showing a Conversation Messages Setup icon 3102 for setting up a sequence of one or more message screens to be generated during a Flow. In the Messages configuration interface, there are shown existing contacts. A new conversation message can be set up by entering the Conversation Messages Set Up menu 3102.

[0168] Referring to Figure 32 herein, the next interface in the Conversation Messages configuration interface has submenus 3201 , 3202 for setting up either a Push Message or a Live Message.

[0169] Figure 33 herein there is illustrated schematically a Live Message configuration interface for setting up Live Messages. The interface comprises a section 3301 for configuring either a sent message or a received message, or both, including a text box for writing the text of the message; and an Add control 3303 for adding the text message to the flow. There is also provided a Message Delay input section 3304 so that a configuring user can input a delay between successive messages in a Live Messages list 3305. The configuring user can add a delay before receiving the predetermined reply message.

[0170] Figure 34 herein illustrates schematically the Conversation Messages configuration interface, showing that no Push Messages and four live messages have been set up and are available for use within a Flow.

[0171] Figure 35 herein illustrates schematically a Push Message interface for setting up a Push Message. The interface includes a menu 3501 for selectinga contact; a text entry box 3502 for entering a text message; And a switch control 3503 to lock the screen of the host device when a push message arrives.Executing a Message Flow.

[0172] Once a flow containing a message screen seguence has been saved to the Flow Library, the saved Flow can be executed or run on the host communications device. The Flow can be initiated by a command, such as the user activating the “Go Live” icon 1303 as shown in Figure 13, or from the Home Page configuration interface “Go Live” control 901 as shown in Figure 9.

[0173] Referring to Figure 36 herein, there is illustrated schematically a Messages screen generated within a Flow showing three separate message strings with three different contacts. This screen would be presented to a user the host device when running a flow containing that Screen View. The action of moving on to the next screen here in the flow could be initiated by various different commands will stop either the user can touch the Penelope section 3601 the flow has been configured to move on to the next screen by that action, or if the flow has been configured so that the screen moves on after a predetermined time delay, then the screen moves automatically on to the next screen in this case, as shown in Figure 37.

[0174] Referring to Figure 37 herein, there is shown a next Message screen view 3700 within the Flow which is seguenced to appear after the preceding view of Figure 36. In the screen display of Figure 37, the touch sensitive screen is active such that touching the letters on the keypad causes letters to appear in the text bar 3701 , with one touch of the screen generating one letter at a time up to the maximum number of characters in the pre-configured message, in this case being “hi, how are you?” comprising 16 characters including spaces. Each single touch of the screen by the user results in the message generating one more character or space in the message, but irrespective of which actual letter icons on the keypad the user activates, as the message is pre-written it will still be the same. Touching different letters on the keypad will not result in different letters appearing in the text box. Further, a minimum time delay between touch commands can be set so that the messagegenerates one character at a time even if there is a quick succession double touch, so as to maintain realism that the user is actually sending a message.

[0175] Referring to Figure 38 herein, there is shown a next successive screen view in the Flow, after a user has made further touch inputs to the screen. A reply message “I’m great thank you 9 are you around today?” is added as the screen view starts, and further touches of the screen by the user.

[0176] The appearance of the third screen view of Figure 38 may be pretimed during configuration to appear a pre-set time after the final screen touch by the user in the preceding screen of Figure 37. This allows a realistic time for the imaginary sender of the text message (Penelope in this case) to write the message and for it to be received by the user’s communications device. Actually, the message has not been sent by Penelope, who may be another character in the scene being filmed, but rather has been pre-written into the Flow to appear in a predetermined sequence of screen views.

[0177] The user touching the screen may then activate the appearance of the response text in this case shown as “yes I’m here all day< ” by making successive touches of the screen, where the screen configurator accepts each touch of the screen as being a command to generate an individual letter within the message, subject to a minimum pre-set time between touches, until the full pre- written message has been generated and displayed.

[0178] Running of the Flow having views as shown in Figures 36 to 38 does not affect the native operation of any other native messaging application which may be present on the mobile communications device, such as the native messaging application Google Messages® in the case of an Android® phone, or the Apple iMessage® application, other than by suspending viewing that native operation whilst the Flow is running.Parameters Summary

[0179] The following objects are managed and operated on by the Screen Configurator:- Actions- Message View;- Screen View;- Incoming Voice Call;- Outgoing Voice Call;- Incoming Message; - Outgoing Message;- Message Exchange; and- Contact- Voice Call- Command

[0180] Whilst the above embodiments and methods have been described in relation to a mobile communication is device of the mobile phone or smartphone type, and in relation to a single operating system type (Android®), the most communication device may be any type of computing device having the necessary hardware and firmware to carry out the methods described herein, for example including but not limited to a tablet type computer, Smartphone or the like.

Claims

Claims1 . A communications device comprising: an outer casing; a data processor; a memory device; a data bus; a display screen; a user interface for receiving user commands; and a native operating system, said native operating system having one or more native application programs, wherein each said native application program comprises means for generating a corresponding respective set of native Screen Views; characterised by comprising: a configurator for generating a set of Screen Views and Actions which are run on said communications device; said Screen Views comprising a plurality of individual Screen Views which are generated to be run in overlay to said native application program in response to said Actions.

2. The communications device as claimed in claim 1 , in which said configurator is operable to configure:- pre-settable Actions which cause progression between successive screens views through said sequence of screens views; and- pre-settable Actions which cause progression of content within individual said Screen Views.

3. The communications device as claimed in claim 1 , in which when a sequence of said Screen Views is being run, said configurator generates said Screen Views instead of a set of native Screen Views of said native applications.

4. The communications device as claimed in claim 1 , in which when a sequence of said Screen Views is being run, running said sequence overlays the normal communications operation of native communications applications of said communications device.

5. The communications device as claimed in claim 1 , wherein said configurator is operable to configure predetermined device settings which indicate predetermined operating parameters of said communications device.

6. The communications device as claimed in claim 1 , wherein said configurator comprises: a Flow creation module for creating one or more Flows, each said Flow comprising a said sequence of Screen Views and Actions; a Messages configurator for configuring one or more messages within a said Flow; a Voice Call configurator for configuring one or more voice calls within aFlow; a Contacts configurator for configuring one or more contacts; anda Run module for executing a said Flow.

7. The communications device as claimed in any one of the preceding claims wherein said screen configurator comprises a Device Settings configuration module for pre-configuring device settings in one or more Screen Views.

8. The communications device as claimed in any one of the preceding claims wherein said screen configurator comprises a Flow library for storing one or more Flows, each Flow comprising a sequence of said Screen Views.

9. The communications device as claimed in claim 6, wherein each Flow comprises a sequence of one or more Screen Views, which are arranged to be generated in a pre-ordered sequence one after another.

10. The communications device as claimed in any one of the preceding claims, wherein a sequence of said Screen Views comprises individual Screen Views selected from the set:- Message Screen View;- Voice Call Screen View- Contacts Screen View; and- Photo Screen View.

11. The communications device as claimed in claim 8, wherein each said Message Screen View comprises a layout having features selected from the set:- an incoming message text box; and- an outgoing message text box.-SO-12. The communications device as claimed in claim 8, wherein a said Voice Call Screen View comprises a view selected from the set:- a phone keypad having number icons; and- an “on hook” icon and an “off hook” icon.

13. The communications device as claimed in any one of the preceding claims wherein a sequence of said Screen Views is executed by a touch command on said touch sensitive user interface.

14. The communications device as claimed in any one of the preceding claims wherein a sequence of said Screen Views progresses from an earlier screen in said sequence to a successive next screen in said sequence in response to a pre-configured command selected from the set:- a touch command entered on a touch sensitive screen of said device;- a timer delay;- a remote activated command received over a wireless communications link from a remote computing device; and- a proximity sensor.

15. The communications device as claimed in any one of the preceding claims wherein in a sequence of said Screen Views, each said Screen View is generated in response to a predetermined action.

16. The communications device as claimed in any one of the preceding claims wherein in a sequence of Screen Views comprising a predetermined Message the text and character content of said Message is pre-set and cannot be varied by a user whilst said sequence is being executed.

17. The communications device as claimed in any one of the preceding claims wherein within a sequence of said Screen Views the layout, content, andorder or appearance of said Screens is pre-set and cannot be altered by a user during execution of said sequence.

18. The communications device as claimed in any one of the preceding claims wherein a sequence of said Screen Views comprises a predetermined sequence of Voice Call screens which are pre-set and cannot be changed whilst said sequence is being executed.

19. The communications device as claimed in any one of the preceding claims wherein within a said sequence, the timing of changes to Screens within the sequence are pre-configurable prior to running the sequence.

20. The communications device as claimed in any one of the preceding claims wherein within a sequence of said Screen Views the timing of changes from a preceding stage of the sequence to a successive stage of the sequence is pre-configurable to be activated by a touch command of a user during execution of said sequence.21 . The communications device as claimed in any one of the preceding claims wherein during execution of a sequence of Screen Views, an order of generation of successive Screens in said sequence is determined by a set of preconfigured actions.

22. The communications device as claimed in any one of the preceding claims wherein a said sequence is activatable by a remote command received from a remote computing device.

23. The communications device as claimed in any one of the preceding claims, comprising a hand-held communications device.

24. A method of operating a host communications device, said method comprising:generating a sequence of Screen Views; wherein each said Screen View is predetermined to be generated in response to a predetermined Action.

25. The method of operating a host communications device as claimed in claim 24, wherein each said Screen View comprises predetermined display content which cannot be changed once said sequence of Screen Views has commenced running.

26. The method of operating a host communications device as claimed in claim 24, wherein individual messages within a said Screen View are predetermined to be generated in response to a predetermined command type.

27. The method of operating a host communications device as claimed in claim 24, wherein individual said Screen Views all selected from the set:- Message screens;- Voice Call screens; and- Contact screens.

28. The method as claimed in claim 24, wherein a said Message screen comprises a Message area for displaying incoming and outgoing messages and a Keypad display.

29. The method of operating a host communications device as claimed in claim 24, wherein said device settings are selected from the set:- signal strength;- battery power level;- service provider;- time;- date; and- operating system.

30. The method of operating a host communications device as claimed in claim 24, wherein said predetermined action is selected from the set: a user command from a user of said host device input via a touch sensitive user interface; a command generated by a timer component of said host device itself after a predetermined time; a command generated by said host device itself in response to a sensor of said host device detecting a movement of said host device; a command generated by said host device itself in response to a sensor of said host device detecting a proximity of said host device to a user’s head; and a remote command from a remote computing device, said remote command being received over a wireless link.31 . The method of operating a host communications device as claimed in claim 24, which when said sequence of screens is being run, running said sequence overlays normal communications operation of native communications applications of said communications device.

32. A method of configuring a host communications device to run a preconfigured sequence of communications, said method comprising: creating a Flow comprising sequence of a plurality of Screen Views to be generated;setting a set of Actions to control generation of each individual Screen View of said plurality of Screen Views in said Flow; and setting a content of each individual Screen View within said Flow.

33. The method as claimed in claim 32, further comprising: setting a mode of activation of each said Screen View in said Flow, wherein said mode of activation is selected from the set: activation by a timer, after a predetermined time; activation by a user input to a touch screen or physical keypad; activation by a remote wireless signal received from a remote computing device.

34. The method as claimed in claim 32 comprising setting a set of Device Settings common to each Screen View generated in said Flow.

35. The method as claimed in claim 34, wherein said Device Settings comprise settings of parameters selected from the set:- battery power level;- signal strength;- service provider;- time;- Date; and- Operating system.wherein each said pre-set Device Setting indicates a parameter level represented by said Device Setting, and which does not correspond with a true status of a corresponding parameter according to a native parameter of said host device.

36. The method as claimed in claim 32, wherein said setting of a content within each individual said Flow comprises setting content selected from the set: - Text content;- Photo content; such that during execution of said Flow said content appears in a predetermined order as set, and such that the content cannot be varied during running of said flow, and wherein the timing of the appearance of said content can be varied during running of said Flow by a set of commands.