Data acquisition method and device, terminal and readable storage medium

Abstract

The invention belongs to the technical field of communication, and particularly relates to a data acquisition method and device, a terminal and a readable storage medium, and the method comprises the steps that a rendering engine monitors a target node or a target object; the rendering engine obtains target data according to the target attribute associated with the target node or the target object; wherein the target attribute comprises a time attribute.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a data acquisition method, device, terminal and readable storage medium. Background Art

[0002] The haptic signal processing model in the current scene description (SD) standard is based on triggering haptic actions. The current processing model is not flexible enough in the triggering method of haptic data processing and cannot handle non-interactive scenarios. Summary of the invention

[0003] The embodiments of the present application provide a data acquisition method, device, terminal and readable storage medium, which can solve the problem that the tactile signal processing model is not flexible enough in triggering haptic data processing and cannot handle non-interactive scenarios.

[0004] In a first aspect, a data acquisition method is provided, comprising:

[0005] The rendering engine monitors the target node or target object;

[0006] The rendering engine obtains target data according to the target attribute associated with the target node or target object;

[0007] Wherein, the target attribute includes a time attribute.

[0008] In a second aspect, a data acquisition device is provided, comprising:

[0009] Monitoring module, used for the rendering engine to monitor target nodes or target objects;

[0010] An acquisition module, used by a rendering engine to acquire target data according to a target attribute associated with the target node or target object;

[0011] Wherein, the target attribute includes a time attribute.

[0012] In a third aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be executed on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0013] In a fourth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is used for a rendering engine to monitor a target node or a target object;

[0014] The rendering engine obtains target data according to the target attribute associated with the target node or target object;

[0015] Wherein, the target attribute includes a time attribute.

[0016] In a fifth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0017] In a sixth aspect, a network side device is provided, including a processor and a communication interface, wherein the processor is used for a rendering engine to monitor a target node or a target object;

[0018] The rendering engine obtains target data according to the target attribute associated with the target node or target object;

[0019] Wherein, the target attribute includes a time attribute.

[0020] In a seventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0021] In an eighth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.

[0022] In a ninth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the method as described in the first aspect.

[0023] In an embodiment of the present application, by introducing a target node or target object with a time attribute, the rendering engine obtains the target data according to the time attribute associated with the target node or target object, thereby realizing time-triggered data processing, making data processing more flexible, and time-triggered data processing can handle non-interactive scenarios. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0025] Figure 2 It is a flow chart of the data acquisition method provided in the embodiment of the present application;

[0026] Figure 3 is a schematic diagram of the structure of a data acquisition device provided in an embodiment of the present application;

[0027] Figure 4It is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0028] Figure 5 It is a schematic diagram of the terminal structure provided in an embodiment of the present application;

[0029] Figure 6 This is one of the schematic diagrams of the network side device structure provided in the embodiment of the present application;

[0030] Figure 7 This is the second schematic diagram of the network side device structure provided in the embodiment of the present application. DETAILED DESCRIPTION

[0031] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0032] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.

[0033] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

[0034] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and the NR terminology is used in most of the following descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.

[0035] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be referred to as a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (Wireless Local Area Network, WLAN) access point (Access Point, AP) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0036] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

[0037] In order to better understand the technical solution of this application, the following contents are first introduced:

[0038] Typology of Haptic Immersive Content

[0039] Tactile media content can be divided into four types: story-driven content, experience-driven content, event-driven content, and interaction-driven content.

[0040] For story-driven content, the user can be immersed in the story, such as TV or movies. To enhance the story experience, tactile feedback can be used to highlight moments / important scenes (for example, the user will feel vibration feedback in the earthquake scene and feel the wind in the windy scene).

[0041] GL Transmission Format (glTF) Interactivity extension

[0042] glTF is used for efficient transmission and loading of 3D scenes and models by engines and applications. glTF defines an extensible publishing format that simplifies authoring workflows and interactive services by enabling interoperable use of 3D content across the industry.

[0043] The Moving Picture Expert Group (MPEG) has interactively extended glTF and preliminarily designed standards for interactivity. For tactile scenes, the standards for interactivity are mainly used to describe the interaction between avatars and haptic sources, based on which tactile signals are triggered and generated.

[0044] Interactivity is defined based on behavior, which includes the trigger node and action node. Trigger includes collision condition, proximity condition, visibility condition, and action includes haptic feedback action (set haptic), etc.

[0045] For the haptic feedback action conditions, the action defines several parameters for generating and playing haptic signals, as shown in Table 1 and Table 2 below, where Table 1 shows the semantics of the action and Table 2 shows the semantics of the HapticActionNode object.

[0046] Table 1

[0047]

[0048]

[0049] Table 2

[0050]

[0051] Processing model of tactile feedback

[0052] For a scene description file to be processed, the rendering engine performs the following steps:

[0053] (1) Parse the relevant glTF files;

[0054] (2) Check whether MPEG_haptic and MPEG_haptic_material extensions are included in the scene description file;

[0055] (3) Identify tactile feedback related nodes by analyzing the tactile action nodes defined in the interaction extension.

[0056] At runtime, the rendering engine performs the following steps:

[0057] (1) If the trigger node in the haptic behavior triggers a haptic action, the rendering engine obtains the haptic data in the related haptic object through the MAF API;

[0058] (2) The rendering engine renders the tactile data based on the features in the tactile action nodes.

[0059] The data acquisition method provided in the embodiment of the present application is described in detail below through some embodiments and their application scenarios in combination with the accompanying drawings.

[0060] See also Figure 2 The embodiment of the present application provides a data acquisition method, the execution subject of the method is a rendering engine. It should be noted that the rendering engine can be deployed in the cloud (such as a server) or a terminal, and the embodiment of the present application does not limit the specific location of the rendering engine deployment. The method can be specifically executed by the rendering engine in the form of a tactile feedback processing model.

[0061] Methods include:

[0062] Step 201: The rendering engine monitors a target node or a target object;

[0063] Step 202: The rendering engine obtains target data according to the target attribute associated with the target node or target object;

[0064] The rendering engine is used to synthesize and play the audio, video and touch in the scene according to the obtained SD information.

[0065] In some optional implementations, the target attribute includes a time attribute.

[0066] In an embodiment of the present application, by introducing a target node or target object with a time attribute, the rendering engine obtains target data according to the time attribute associated with the target node or target object, realizes time-triggered data processing, and makes data processing more flexible.

[0067] It should be noted that the above-mentioned target data may include tactile data, sound data, video data, etc. The embodiment of the present application does not specifically limit the category of the target data. It can be understood that for the convenience of understanding the solution, the target data is described as tactile data as an example in the following embodiment description.

[0068] In a possible implementation manner, the target node or target object includes at least one of the following:

[0069] (1) haptic source node or haptic source object; the haptic source is a node or object that generates a tactile signal;

[0070] (2) trigger node or trigger object;

[0071] (3) behavior node or behavior object;

[0072] (4)Haptic action node or haptic action object.

[0073] The following describes the specific implementation methods corresponding to different categories of target nodes or target objects:

[0074] Implementation method 1:

[0075] When the target node or target object is a haptic source node or a haptic source object, the rendering engine obtains target data according to target attributes associated with the target node or the target object, including:

[0076] The rendering engine obtains target data according to the first target attribute associated with the haptic source node or the haptic source object;

[0077] The first target attribute includes a time attribute.

[0078] In the embodiment of the present application, a haptic source node or haptic source object (abbreviated as haptic source node / object) is introduced, and the tactile feedback processing model allows the rendering engine to monitor the haptic sourcenode / object and directly obtain and render tactile data according to the properties corresponding to the haptic source node / object. Since the properties of the haptic source node / object include time properties, time-triggered data processing can be achieved in this way.

[0079] Implementation method 2:

[0080] When the target node or target object is a trigger node or trigger object, the rendering engine obtains target data according to the target attribute associated with the target node or target object, including:

[0081] The rendering engine obtains target data according to the second target attribute associated with the trigger node or the trigger object;

[0082] The second target attribute includes a time attribute.

[0083] In the embodiment of the present application, a haptic action is triggered based on a trigger, and then tactile data is obtained and rendered based on the property corresponding to the node / object. In order to support data processing based on time triggering, it is necessary to add a trigger type to the protocol, that is, to add the time attribute of the trigger node / object to describe the trigger condition based on time / scene switching. Since the attributes of the trigger node / object include the time attribute, data processing based on time triggering can be realized in this way.

[0084] Implementation method three:

[0085] When the target node or target object is a behavior node or behavior object, the rendering engine obtains the target data according to the target attribute associated with the target node or target object, including:

[0086] The rendering engine obtains target data according to the third target attribute associated with the behavior node or the behavior object;

[0087] Among them, the third target attribute includes a time attribute.

[0088] In the embodiment of the present application, in order to support time-triggered data processing, it is necessary to add a behavior type in the protocol, that is, to add a time attribute of a behavior node / object to describe the triggering conditions based on time / scene switching. Since the attributes of a behavior node / object include a time attribute, time-triggered data processing can be implemented in this way.

[0089] Implementation method 4:

[0090] When the target node or target object is a haptic action node or a haptic action object, the rendering engine obtains target data according to the target attribute associated with the target node or the target object, including:

[0091] The rendering engine obtains target data according to the fourth target attribute associated with the haptic action node or the haptic action object;

[0092] Among them, the fourth target attribute includes a time attribute.

[0093] In an embodiment of the present application, a haptic action is triggered based on a trigger, and then tactile data is obtained and rendered based on the property corresponding to the node / object. In order to support data processing based on time triggering, it is necessary to increase the type of haptic action in the protocol, that is, to increase the time attribute of the haptic action node / object, which is used to describe the triggering conditions based on time / scene switching. Since the attributes of the haptic action node / object include the time attribute, data processing based on time triggering can be achieved in this way.

[0094] In a possible implementation, the target attribute is in a default state, and the rendering engine obtains target data according to the target attribute associated with the target node or target object, including:

[0095] The rendering engine obtains target data at any time.

[0096] In the embodiment of the present application, the default state is used to indicate that the rendering engine can obtain target data at any time.

[0097] In a possible implementation, the rendering engine monitors the target node or target object, including:

[0098] When the trigger node or the trigger object is in a preset state, the rendering engine monitors the hapticaction node or the haptic action object.

[0099] In an embodiment of the present application, the trigger node / object in the behavior node / object is allowed to be in the default state. When the trigger node or the trigger object is in the preset state, the trigger node or the trigger object is in the triggered state, that is, the default trigger node / object can definitely trigger the haptic action node / object (for example, either based on existing conditions such as collision, or played by time), indicating that the haptic action node / object in the behavior node / object is always in an activated state, and the rendering engine can always obtain and render tactile data according to the property corresponding to the activated haptic action node / object.

[0100] In a possible implementation manner, the time attribute is at least one of the following:

[0101] (1) A first attribute, used to indicate the time when the rendering engine starts rendering the target data;

[0102] The first attribute may be referred to as a start time (startTime), which is used to indicate when the rendering engine starts rendering the media information associated with the node / object.

[0103] (2) The second attribute is used to indicate whether to play the target data immediately when it is ready;

[0104] The second attribute may be called autoplay, and is used to indicate whether the media signal is played immediately when ready; the indication may be made in the form of a flag.

[0105] Optionally, the description file needs to carry at least one of startTime and autoplay.

[0106] (3) a third attribute, used to indicate the time when the target data starts to be played;

[0107] The third attribute may be referred to as a start time offset (startTimeOffset), which is used to indicate at which point in time the timed media starts playing. startTimeOffset indicates the time offset of the source from which the timed media is generated, where 0 corresponds to the beginning of the source.

[0108] (4) a fourth attribute, used to indicate the time when the target data ends playing;

[0109] The fourth attribute may be referred to as endTimeOffset, and is used to indicate at which point in time the timed media ends playback. endTimeOffset indicates the time offset of the source from which the timed media generation begins. The value is provided in seconds, where 0 corresponds to the start time of the source.

[0110] (5) A fifth attribute, used to indicate whether the target data is played repeatedly after the playback ends;

[0111] The fifth attribute may be called a loop, and startTime is used to indicate whether the media signal is played repeatedly after the end of the playing; the indication may be made in the form of a flag.

[0112] (6) A sixth attribute, used to indicate the playback period of the target data.

[0113] The sixth attribute may be referred to as a signal playing period.

[0114] In a possible implementation manner, the target attribute includes a time attribute and a seventh attribute, and the seventh attribute is used to indicate a trigger type of the target data;

[0115] The seventh attribute may be called the playback mode, which is used to indicate the trigger type of the signal feedback associated with the node / object. For example, it includes at least one of the following trigger types: event-based triggering (the event may be, for example, an explosion, etc.), triggering based on a trigger condition defined by interactivity, triggering based on non-events, triggering based on time, triggering based on scenes (the event may be, for example, rainy or snowy weather, etc.), permanent triggering, etc.

[0116] Exemplarily, the Playback mode can be selected from continuous and event, the continuous mode is triggered continuously, and the event mode is triggered based on an event.

[0117] The data acquisition method provided in the embodiment of the present application can be executed by a data acquisition device. In the embodiment of the present application, the data acquisition device provided in the embodiment of the present application is described by taking the data acquisition method executed by the data acquisition device as an example.

[0118] See also Figure 3 , the present application embodiment provides a data acquisition device, including:

[0119] Monitoring module 301, used for the rendering engine to monitor target nodes or target objects;

[0120] An acquisition module 302 is used for the rendering engine to acquire target data according to a target attribute associated with the target node or target object;

[0121] Wherein, the target attribute includes a time attribute.

[0122] Optionally, the target node or target object includes at least one of the following:

[0123] Haptic source node or haptic source object;

[0124] trigger node or trigger object;

[0125] behavior node or behavior object;

[0126] A haptic action node or a haptic action object.

[0127] Optionally, when the target node or target object is the haptic source node or haptic source object, the acquisition module is used to:

[0128] The rendering engine obtains the target data according to a first target attribute associated with the haptic source node or the haptic source object;

[0129] The first target attribute includes a time attribute.

[0130] Optionally, when the target node or target object is the trigger node or trigger object, the acquisition module is used to:

[0131] The rendering engine obtains the target data according to a second target attribute associated with the trigger node or the trigger object;

[0132] The second target attribute includes a time attribute.

[0133] Optionally, when the target node or target object is the behavior node or behavior object, the acquisition module is used to:

[0134] The rendering engine obtains the target data according to a third target attribute associated with the behavior node or the behavior object;

[0135] Wherein, the third target attribute includes a time attribute.

[0136] Optionally, when the target node or target object is the haptic action node or haptic action object, the acquisition module is used to:

[0137] The rendering engine obtains the target data according to a fourth target attribute associated with the haptic action node or the haptic action object;

[0138] Wherein, the fourth target attribute includes a time attribute.

[0139] Optionally, the target attribute is in a default state, and the acquisition module is used to:

[0140] The rendering engine obtains the target data at any time.

[0141] Optionally, the acquisition module is used to:

[0142] When the trigger node or the trigger object is in a preset state, the rendering engine monitors the haptic action node or the haptic action object.

[0143] Optionally, the time attribute includes at least one of the following:

[0144] A first attribute is used to indicate the time when the rendering engine starts rendering the target data;

[0145] The second attribute is used to indicate whether to play the target data immediately when it is ready;

[0146] The third attribute is used to indicate the time when the target data starts to be played;

[0147] The fourth attribute is used to indicate the time when the target data ends playing;

[0148] The fifth attribute is used to indicate whether the target data is played repeatedly after the playback ends;

[0149] The sixth attribute is used to indicate the playback period of the target data.

[0150] Optionally, the target attribute includes at least one of a time attribute and a seventh attribute, and the seventh attribute is used to indicate a trigger type of the target data;

[0151] The data acquisition device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal, or it can be other devices other than a terminal. Exemplarily, the terminal can include but is not limited to the types of terminals 11 listed above, and other devices can be servers, network attached storage (Network Attached Storage, NAS), etc., which are not specifically limited in the embodiment of the present application.

[0152] The data acquisition device provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0153] like Figure 4 As shown, the embodiment of the present application further provides a communication device 400, including a processor 401 and a memory 402, and the memory 402 stores a program or instruction that can be run on the processor 401. For example, when the communication device 400 is a terminal, the program or instruction is executed by the processor 401 to implement the various steps of the above method embodiment, and can achieve the same technical effect. When the communication device 400 is a network side device, the program or instruction is executed by the processor 401 to implement the various steps of the above method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0154] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps in the method embodiment. The terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the terminal embodiment and can achieve the same technical effect. Specifically, Figure 5 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0155] The terminal 500 includes but is not limited to: a radio frequency unit 501, a network module 502, an audio output unit 503, an input unit 504, a sensor 505, a display unit 506, a user input unit 507, an interface unit 508, a memory 509 and at least some of the components of a processor 510.

[0156] Those skilled in the art will appreciate that the terminal 500 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 510 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 5 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0157] It should be understood that in the embodiment of the present application, the input unit 504 may include a graphics processing unit (GPU) 5041 and a microphone 5042, and the graphics processor 5041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 506 may include a display panel 5061, and the display panel 5061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 507 includes a touch panel 5071 and at least one of other input devices 5072. The touch panel 5071 is also called a touch screen. The touch panel 5071 may include two parts: a touch detection device and a touch controller. Other input devices 5072 may include, but are not limited to, a physical keyboard, function keys (such as a volume control button, a switch button, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0158] In the embodiment of the present application, after receiving downlink data from the network side device, the radio frequency unit 501 can transmit the data to the processor 510 for processing; in addition, the radio frequency unit 501 can send uplink data to the network side device. Generally, the radio frequency unit 501 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0159] The memory 509 can be used to store software programs or instructions and various data. The memory 509 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 509 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory x09 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0160] The processor 510 may include one or more processing units; optionally, the processor 510 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 510.

[0161] Wherein, the processor 510 is used for the rendering engine to monitor the target node or target object;

[0162] Processor 510, configured for a rendering engine to obtain target data according to a target attribute associated with the target node or target object;

[0163] Wherein, the target attribute includes a time attribute.

[0164] Optionally, the target node or target object includes at least one of the following:

[0165] Haptic source node or haptic source object;

[0166] trigger node or trigger object;

[0167] behavior node or behavior object;

[0168] A haptic action node or a haptic action object.

[0169] Optionally, when the target node or the target object is the haptic source node or the haptic source object, the processor 510 is configured to:

[0170] The rendering engine obtains the target data according to a first target attribute associated with the haptic source node or the haptic source object;

[0171] The first target attribute includes a time attribute.

[0172] Optionally, when the target node or target object is the trigger node or trigger object, the processor 510 is configured to:

[0173] The rendering engine obtains the target data according to a second target attribute associated with the trigger node or the trigger object;

[0174] The second target attribute includes a time attribute.

[0175] Optionally, when the target node or target object is the behavior node or behavior object, the processor 510 is configured to:

[0176] The rendering engine obtains the target data according to a third target attribute associated with the behavior node or the behavior object;

[0177] Wherein, the third target attribute includes a time attribute.

[0178] Optionally, when the target node or target object is the haptic action node or haptic action object, the processor 510 is configured to:

[0179] The rendering engine obtains the target data according to a fourth target attribute associated with the haptic action node or the haptic action object;

[0180] Wherein, the fourth target attribute includes a time attribute.

[0181] Optionally, the target attribute is in a default state, and the processor 510 is configured to:

[0182] The rendering engine obtains the target data at any time.

[0183] Optionally, the processor 510 is configured to:

[0184] When the trigger node or the trigger object is in a preset state, the rendering engine monitors the haptic action node or the haptic action object.

[0185] Optionally, the time attribute includes at least one of the following:

[0186] A first attribute is used to indicate the time when the rendering engine starts rendering the target data;

[0187] The second attribute is used to indicate whether to play the target data immediately when it is ready;

[0188] The third attribute is used to indicate the time when the target data starts to be played;

[0189] The fourth attribute is used to indicate the time when the target data ends playing;

[0190] The fifth attribute is used to indicate whether the target data is played repeatedly after the playback ends;

[0191] The sixth attribute is used to indicate the playback period of the target data.

[0192] Optionally, the target attribute includes at least one of a time attribute and a seventh attribute, and the seventh attribute is used to indicate a trigger type of the target data;

[0193] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the method embodiment and achieve the same or corresponding technical effect. To avoid repetition, it will not be repeated here.

[0194] The embodiment of the present application also provides a network side device, including a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the steps of the method embodiment. The network side device embodiment corresponds to the above-mentioned network side device method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the network side device embodiment and can achieve the same technical effect.

[0195] Specifically, the embodiment of the present application also provides a network side device. Figure 6 As shown, the network side device 600 includes: an antenna 61, a radio frequency device 62, a baseband device 63, a processor 64 and a memory 65. The antenna 61 is connected to the radio frequency device 62. In the uplink direction, the radio frequency device 62 receives information through the antenna 61 and sends the received information to the baseband device 63 for processing. In the downlink direction, the baseband device 63 processes the information to be sent and sends it to the radio frequency device 62. The radio frequency device 62 processes the received information and sends it out through the antenna 61.

[0196] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 63, which includes a baseband processor.

[0197] The baseband device 63 may include, for example, at least one baseband board on which a plurality of chips are arranged. Figure 6 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory y5 through a bus interface to call the program in the memory 65 to execute the network device operations shown in the above method embodiment.

[0198] The network side device may further include a network interface 66, which is, for example, a Common Public Radio Interface (CPRI).

[0199] Specifically, the network side device 600 of the embodiment of the present invention further includes: instructions or programs stored in the memory 65 and executable on the processor 64, and the processor 64 calls the instructions or programs in the memory 65 to execute Figure 5 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0200] Specifically, the embodiment of the present application also provides a network side device. Figure 7 As shown, the network side device 700 includes: a processor 701, a network interface 702 and a memory 703. The network interface 702 is, for example, a common public radio interface (CPRI).

[0201] Specifically, the network side device 700 of the embodiment of the present invention further includes: an instruction or program stored in the memory 703 and executable on the processor 701, and the processor 701 calls the instruction or program in the memory 703 to execute Figure 5 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0202] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned method embodiment are implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0203] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk. In some examples, the readable storage medium may be a non-transient readable storage medium.

[0204] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0205] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0206] The embodiments of the present application further provide a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes of the above-mentioned method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described here.

[0207] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0208] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

[0209] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.

Claims

1. A data acquisition method, characterized in that: include: The rendering engine monitors the target node or target object; The rendering engine obtains target data according to the target attribute associated with the target node or target object; Wherein, the target attribute includes a time attribute.

2. The method according to claim 1, characterized in that The target node or target object includes at least one of the following: Haptic source haptic source node or haptic source object; Trigger trigger node or trigger object; Behavior behavior node or behavior object; Haptic action haptic action node or haptic action object.

3. The method according to claim 1, characterized in that The target attribute is in a default state, and the rendering engine obtains target data according to the target attribute associated with the target node or target object, including: The rendering engine obtains the target data at any time.

4. The method according to claim 2, characterized in that: The rendering engine monitors the target node or target object, including: In a case where the trigger node or the trigger object is set to a default state, the rendering engine monitors the haptic action node or the haptic action object.

5. The method according to any one of claims 1 to 4, characterized in that: The time attribute includes at least one of the following: A first attribute is used to indicate the time when the rendering engine starts rendering the target data; The second attribute is used to indicate whether to play the target data immediately when it is ready; The third attribute is used to indicate the time when the target data starts to be played; The fourth attribute is used to indicate the time when the target data ends playing; The fifth attribute is used to indicate whether the target data is played repeatedly after the playback ends; The sixth attribute is used to indicate the playback period of the target data.

6. The method according to any one of claims 1 to 5, characterized in that: The target attributes further include a seventh attribute, and the seventh attribute is used to indicate a trigger type of the target data.

7. A data acquisition device, characterized in that: include: Monitoring module, used for the rendering engine to monitor target nodes or target objects; An acquisition module, used by a rendering engine to acquire target data according to a target attribute associated with the target node or target object; Wherein, the target attribute includes a time attribute.

8. The device according to claim 7, characterized in that The target node or target object includes at least one of the following: Haptic source node or haptic source object; trigger node or trigger object; behavior node or behavior object; A haptic action node or a haptic action object.

9. The device according to claim 7, characterized in that The target attribute is in a default state, and the acquisition module is used to: In the case where the trigger node or trigger object is set to a default state, the rendering engine obtains the target data at any time.

10. The device according to claim 8, characterized in that When the trigger node or the trigger object is in a preset state, the trigger node or the trigger object is in a triggered state, and the acquisition module is used to: The rendering engine monitors the haptic action node or the haptic action object.

11. The method according to any one of claims 7 to 10, characterized in that: The time attribute includes at least one of the following: A first attribute is used to indicate the time when the rendering engine starts rendering the target data; The second attribute is used to indicate whether to play the target data immediately when it is ready; The third attribute is used to indicate the time when the target data starts to be played; The fourth attribute is used to indicate the time when the target data ends playing; The fifth attribute is used to indicate whether the target data is played repeatedly after the playback ends; The sixth attribute is used to indicate the playback period of the target data.

12. The method according to any one of claims 7 to 11, characterized in that The target attributes further include a seventh attribute, and the seventh attribute is used to indicate a trigger type of the target data.

13. A communication device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the data acquisition method according to any one of claims 1 to 6 are implemented.

14. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the data acquisition method according to any one of claims 1 to 6 are implemented.

Images