WO2021254103A1 - 一种信息投放方法、装置、设备及计算机可读存储介质 - Google Patents

一种信息投放方法、装置、设备及计算机可读存储介质 Download PDF

Info

Publication number
WO2021254103A1
WO2021254103A1 PCT/CN2021/095669 CN2021095669W WO2021254103A1 WO 2021254103 A1 WO2021254103 A1 WO 2021254103A1 CN 2021095669 W CN2021095669 W CN 2021095669W WO 2021254103 A1 WO2021254103 A1 WO 2021254103A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
delivery
management
display
sub
Prior art date
Application number
PCT/CN2021/095669
Other languages
English (en)
French (fr)
Inventor
赵小喜
梁健权
黄东庆
邵帅
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Publication of WO2021254103A1 publication Critical patent/WO2021254103A1/zh
Priority to US17/740,307 priority Critical patent/US20220270122A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0241—Advertisements
    • G06Q30/0251—Targeted advertisements
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201—Market modelling; Market analysis; Collecting market data
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/953—Querying, e.g. by the use of web search engines
    • G06F16/9535—Search customisation based on user profiles and personalisation
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201—Market modelling; Market analysis; Collecting market data
    • G06Q30/0202—Market predictions or forecasting for commercial activities
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201—Market modelling; Market analysis; Collecting market data
    • G06Q30/0206—Price or cost determination based on market factors

Definitions

  • This application relates to information processing technology in the Internet field, and in particular to an information delivery method, device, equipment, and computer-readable storage medium.
  • the delivery system is usually used to deliver the information on the delivery device and display it on the display device to achieve the delivery of the information on the display device.
  • the delivery system used is usually implemented in an agile way. Since the agile method adopted is a human-centered, iterative, and gradual development method, the functional modules in the delivery system are highly coupled, and the code and framework need to be continuously refactored to cope with changing business needs; therefore, information The complexity of delivery is relatively high.
  • the embodiments of the present application provide an information delivery method, device, device, and computer-readable storage medium, which can simplify the information delivery process and improve the efficiency of information delivery.
  • the embodiment of the present application provides an information delivery method, which is executed by a delivery device, and includes:
  • At least one management sub-information corresponding to at least one management sub-module is obtained, wherein the information management sub-module and the at least one management sub-module are independent based on the result of sub-domain division of the delivery management field.
  • the delivery management field is a field used to manage the delivered information in the delivery field plan;
  • the processing result display the target delivery information on the delivery management interface, and based on the displayed target delivery information, instruct the display device to display the target delivery information according to an independent module corresponding to the delivery display area, where the delivery display area is
  • the delivery field is a field used to display the delivered information.
  • An embodiment of the present application also provides an information delivery method, which is executed by a display device, and includes:
  • the target release information is the information released by the placement device according to the respective independent modules corresponding to the placement management domain, and the placement management domain is the placement domain.
  • the information playing submodule displays the target placement information on the information display interface
  • the information display sub-module, the device information sub-module, the information query sub-module, and the information play sub-module are independent modules obtained based on the result of sub-domain division of the display area.
  • the display area is the area used for displaying the information to be dropped in the placement area.
  • the embodiment of the present application provides a release device for information release, including:
  • the information management sub-module is configured to receive the delivery operation acting on the delivery control on the delivery management interface, and respond to the delivery operation to obtain target delivery information;
  • the sub-information acquisition module is configured to acquire at least one management sub-information corresponding to at least one management sub-module according to the target delivery information; wherein the information management sub-module and the at least one management sub-module are based on the delivery management field
  • Each of the mutually independent modules obtained as a result of sub-domain division, where the delivery management field is a field that is divided from the delivery field based on the delivery process and used to manage the delivered information;
  • a processing module configured to process the at least one management sub-information through the at least one management sub-module
  • the information display module is configured to display the target delivery information on the delivery management interface according to the processing result, and instruct the display device to display the target delivery information based on independent modules corresponding to the delivery display field based on the displayed target delivery information ,
  • the placement display field is a field in the placement field that is used to display the placed information.
  • the embodiment of the present application provides a display device for information placement, including:
  • the information display sub-module is configured to respond to the information display request, display the information display interface, and instruct the device information sub-module to obtain display device information;
  • the information query sub-module is configured to obtain target delivery information corresponding to the display device information.
  • the target delivery information is the information delivered by the delivery device according to the respective independent modules corresponding to the delivery management field, and the delivery management field is the delivery The field used to manage the released information in the field;
  • the information playing submodule is configured to display the target placement information on the information display interface; wherein, the information display submodule, the device information submodule, the information query submodule, and the information playing submodule
  • Each of the mutually independent modules is obtained based on the result of sub-domain division of the placement display field, and the placement display field is a field in the placement field used to display information to be placed.
  • the embodiment of the present application provides a delivery device for information delivery, including:
  • the first memory is used to store executable instructions
  • the first processor is configured to execute the executable instruction stored in the first memory to implement the information delivery method applied to the delivery device provided in the embodiment of the present application.
  • the embodiment of the present application provides a display device for information delivery, including:
  • the second memory is used to store executable instructions
  • the second processor is configured to execute the executable instructions stored in the second memory to implement the information delivery method applied to the display device provided in the embodiment of the present application.
  • An embodiment of the present application provides a computer-readable storage medium, which is characterized in that it stores executable instructions for causing a first processor to execute, to implement an information delivery method applied to a delivery device; or for causing a second processing When the device is executed, the information delivery method applied to the display device is realized.
  • the delivery device processes the target delivery information according to each independent module in the delivery management field, so as to complete the delivery of the target delivery information on the delivery device, and then Make the display device display the target delivery information according to the independent modules corresponding to the delivery display field; and since the independent modules in the delivery management field are obtained based on the results of the sub-domain division of the delivery management field, the respective mutual corresponding modules in the delivery display field The independent modules are obtained based on the results of sub-domain division of the display field. Therefore, the coupling degree of each functional module used to display the target information is low, which can simplify the information delivery process and improve the efficiency of information delivery.
  • FIG. 1 is a schematic diagram of an optional architecture of an information delivery system provided by an embodiment of the present application
  • FIG. 2 is a schematic diagram of the composition structure of a placing device provided by an embodiment of the present application.
  • FIG. 3 is a schematic diagram of the composition structure of a display device provided by an embodiment of the present application.
  • FIG. 4 is an optional flowchart of an information delivery method provided by an embodiment of the present application.
  • Fig. 5 is a schematic diagram of an exemplary delivery management interface provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of another exemplary delivery management interface provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of an exemplary result of a division of a delivery field provided by an embodiment of the present application.
  • FIG. 8a is another optional flowchart of the information delivery method provided by an embodiment of the present application.
  • Fig. 8b is an exemplary schematic diagram of displaying target placement information provided by an embodiment of the present application.
  • Fig. 8c is another exemplary schematic diagram of displaying target placement information provided by an embodiment of the present application.
  • FIG. 9 is another optional flowchart of the information delivery method provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of an exemplary subdomain division result of the delivery management field provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of an exemplary multiple management contexts provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of an exemplary management model corresponding to an information management context provided by an embodiment of the present application.
  • FIG. 13 is a schematic diagram of an exemplary package creation logic provided by an embodiment of the present application.
  • FIG. 14 is another optional flowchart of the information delivery method provided by an embodiment of the present application.
  • FIG. 15 is a schematic diagram of an exemplary sub-domain division result of a placement display area provided by an embodiment of the present application.
  • FIG. 16 is an exemplary schematic diagram of multiple display contexts provided by an embodiment of the present application.
  • FIG. 17 is a schematic flowchart of an exemplary information release system provided by an embodiment of the present application.
  • FIG. 18 is a diagram of an exemplary information delivery architecture provided by an embodiment of the present application.
  • Fig. 19 is an exemplary information delivery interaction diagram provided by an embodiment of the present application.
  • first ⁇ second involved only distinguishes similar objects, and does not represent a specific order for the objects. Understandably, “first ⁇ second” can be interchanged when allowed. The specific order or sequence is changed so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein.
  • DDD Domain Driven Design
  • Bounded Context refers to the separate applicability of the domain model; through the bounded context, team members can clearly share consistent content and content that can be independently developed.
  • the bounding context includes terms and application scenarios, as well as nouns and verbs; among them, nouns can be used to name domain objects, such as commodities, orders, etc., corresponding to entity objects; verbs indicate an action or event, such as an order has been placed , Order has been paid, etc., corresponding to field events or orders.
  • the bounded context is usually referred to as context for short; and the management context and the display context involved in the embodiments of the present application are all bounded contexts.
  • Entity refers to the object distinguished from other objects by its unique identifier, and is the basic element of the domain model, such as an order.
  • Value object refers to an object that is distinguished from other objects by its attributes, such as a kind of tile.
  • the attributes used to distinguish other objects are size and material; it can be shared in the domain model. When there are other When the value object is needed in a place, a copy of the value object can be passed as a parameter to realize sharing in other places.
  • a special entity is a data access window provided by the corresponding context to the external context; that is, in the corresponding context, other contexts access all entities and value objects of the corresponding context through the aggregate root.
  • IoT devices refer to hardware devices that can access the Internet, such as shared power banks, shared umbrellas, shared bicycles, and face-swiping devices.
  • the display device may be an IoT device.
  • Information delivery refers to the process by which the delivery object places the information to be delivered on the IoT device in order to obtain delivery revenue.
  • Design Pattern also known as software design pattern, is a summary of code design experience that has been used repeatedly and known to most people after classification and cataloging. The use of design patterns is to reusable code, make it easier for others to understand, ensure code reliability, and program reusability. Among them, there are many design patterns, such as factory pattern, waterfall flow pattern, adapter pattern and prototype pattern.
  • Factory mode Also known as the creation mode, it is a way to create objects. Through the factory mode, it is convenient to create complex objects of the same type of interface products.
  • Waterfall flow model A project development architecture. The development process is carried out in sequence through a series of stages. From the analysis of system requirements to product release and maintenance, each stage will generate cyclic feedback; in the waterfall flow model, the software The development of the project is divided into various development stages: requirement analysis, requirement definition, basic design, detailed design, coding, unit test, combined test, system test, etc., and adopts a milestone method to strictly define the input and output of each development stage If the required output is not reached, the next stage of work will not start.
  • Adapter mode The process of adapting the interface of a functional module (such as a class) to a specified form. Through the adapter model, functional modules that cannot jointly implement business functions due to incompatible interfaces can be combined to achieve specified functions.
  • Prototype mode It is a kind of creational design mode. By passing a prototype object to the object created by the launch, the object created by the launch can be created by requesting the prototype object to copy the prototype object itself.
  • Sub-domain refers to the result of division corresponding to the business domain, and the sub-domain corresponds to a smaller problem domain.
  • sub-domains can be divided into three types of sub-domains according to their importance and functional attributes. They are: core domain, general domain, and support domain.
  • the core domain is the subdomain that determines the core competitiveness of the product and the company, and is the main factor for business success and the company's core competitiveness
  • the general domain refers to the general function that is used by multiple subdomains at the same time without too many personalized demands
  • the supporting domain is a subdomain that neither contains the functions that determine the core competitiveness of the product and the company, nor does it contain general functions.
  • Anticorruption Layer A context interacts with another context through some adaptations and transformations, also known as an adaptation layer. In a context, sometimes it is necessary to access the external context, and the access to the external context is usually escaped through the anti-corrosion layer.
  • the delivery system is usually used to deliver the information on the delivery device and display it on the display device to achieve the delivery of the information on the display device.
  • the delivery system used is usually implemented in an agile way. Because the agile method adopted is a human-centric, iterative, and gradual development method, the functional modules in the delivery system are highly coupled. , It is necessary to constantly refactor code and framework to cope with changing business requirements; therefore, the complexity of information delivery is high.
  • the use of agile methods can ensure efficiency in the early stage of the delivery system, since in-depth research and modeling of the delivery field is not carried out, the later stage of the delivery system can only continuously refactor the code and framework to meet changing business needs .
  • the overall system has high complexity and low maintainability; furthermore, when using the delivery system to deliver information on the display device, multiple interactions between multiple functional modules with high coupling are required, which results in high resource consumption .
  • the embodiments of the present application provide an information delivery method, device, device, and computer-readable storage medium, which can reduce the coupling degree of various functional modules in the delivery system, simplify the information delivery process, improve the efficiency of information delivery, and reduce information
  • the complexity of delivery reduces resource consumption.
  • the following describes exemplary applications of the information delivery equipment (including delivery equipment and display equipment) provided by the embodiments of the application.
  • Both the delivery equipment and the display equipment provided in the embodiments of the application can be implemented as smart phones, tablets, and laptops.
  • Various types of user terminals can also be implemented as servers, as well as terminals and servers.
  • an exemplary application when the placement device is implemented as a terminal and a server, and the display device is implemented as a terminal and a server will be described.
  • Figure 1 is an optional schematic diagram of an information delivery system provided by an embodiment of the present application; as shown in Figure 1, in order to support an information delivery application, in the information delivery system 100, the server 100-1 passes through the network Connect the terminal 100-2 (the server 100-1 and the terminal 100-2 jointly constitute the delivery device of the embodiment of the present application) and the terminal 100-3 (the server 100-1 and the terminal 100-3 jointly constitute the display device of the embodiment of the present application) ;
  • the network can be a wide area network or a local area network, or a combination of the two;
  • the information delivery system 100 also includes a database 100-4 for executing the information delivery method provided by the embodiments of the present application on the server 100-1 At the time, data support is provided to the server 100-1.
  • the terminal 100-2 is configured to receive a delivery operation acting on a delivery control on a delivery management interface, and the information management submodule obtains target delivery information in response to the delivery operation; and sends the target delivery information to the server 100-1 via the network. It is also used to receive the processing result sent by the server 100-1 through the network, and display the target delivery information on the delivery management interface based on the processing result; send the target delivery information to the server 100-1 based on the displayed target delivery information through the network The delivery status of is set to the request in delivery.
  • the server 100-1 is configured to receive target posting information sent by the terminal 100-2 via the network; according to the target posting information, obtain at least one management sub-information corresponding to at least one management sub-module; wherein, the information management sub-module and the at least one management sub-module Modules are independent modules based on the results of sub-domain division of the delivery management field.
  • the delivery management field is the field that is divided from the delivery field based on the delivery process to manage the delivery information; at least one management sub-module is responsible for at least A management sub-information is processed.
  • the database 100-4 stores the associated information of the target placement information and the display device, so that the processing result is sent to the terminal 100-2 through the network; it is also used to receive the terminal 100- through the network.
  • a request is sent to set the delivery status of the target delivery information as delivering, and the delivery status of the target delivery information in the database 100-4 is set as delivering. It is also used to obtain the information display request sent by the terminal 100-3 through the network, respond to the information display request through the information display submodule, and instruct the device information submodule to obtain display device information; and obtain the display device from the database 100-4 through the information query submodule The target delivery information corresponding to the information.
  • the target delivery information is the information delivered by the delivery equipment according to the respective independent modules corresponding to the delivery management field; the information playback sub-module sends the target delivery information to the terminal 100-3 through the network to complete the target delivery
  • the placement of information in the display device; among them, the information display submodule, the device information submodule, the information query submodule, and the information playback submodule are independent modules based on the results of the subdomain division of the display area.
  • the terminal 100-3 is configured to send an information display request to the server through the network; it is also configured to receive the target posting information sent by the server 100-1 in response to the information display request through the network, and display the target posting information on the information display interface.
  • the delivery device 400 includes: at least one first processor 410, a first memory 450, and at least one first processor 410; The network interface 420 and the first user interface 430.
  • the various components in the placing device 400 are coupled together through the first bus system 440.
  • the first bus system 440 is used to implement connection and communication between these components.
  • the first bus system 440 also includes a power bus, a control bus, and a status signal bus.
  • various buses are marked as the first bus system 440 in FIG. 2.
  • the first processor 410 may be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, Discrete hardware components, etc., where the general-purpose processor may be a microprocessor or any conventional processor.
  • DSP Digital Signal Processor
  • the general-purpose processor may be a microprocessor or any conventional processor.
  • the first user interface 430 includes one or more first output devices 431 that enable the presentation of media content, including one or more speakers and/or one or more visual display screens.
  • the first user interface 430 also includes one or more first input devices 432, including user interface components that facilitate user input, such as a keyboard, a mouse, a microphone, a touch screen display, a camera, and other input buttons and controls.
  • the first memory 450 includes volatile memory or non-volatile memory, and may also include both volatile and non-volatile memory.
  • the non-volatile memory may be a read only memory (ROM, Read Only Memory), and the volatile memory may be a random access memory (RAM, Random Access Memory).
  • the first memory 450 described in the embodiment of the present application intends to include any suitable type of memory.
  • the first memory 450 optionally includes one or more storage devices that are physically remote from the first processor 410.
  • the first memory 450 can store data to support various operations. Examples of these data include programs, modules, and data structures, or a subset or superset thereof, as illustrated below.
  • the first operating system 451 includes system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;
  • the first network communication module 452 is used to reach other computing devices via one or more (wired or wireless) first network interfaces 420.
  • Exemplary first network interfaces 420 include: Bluetooth, wireless compatibility authentication (Wi-Fi) ), and Universal Serial Bus (USB, Universal Serial Bus), etc.;
  • the first display module 453 is used to enable the presentation of information (for example, for operating peripheral devices and displaying User interface for content and information);
  • the first input processing module 454 is configured to detect one or more user inputs or interactions from one of the one or more first input devices 432 and translate the detected inputs or interactions.
  • the delivery device for information delivery (hereinafter referred to as the delivery device) provided in the embodiments of the present application can be implemented in software.
  • FIG. 2 shows the delivery device 455 stored in the first memory 450, which It can be software in the form of programs and plug-ins, including the following software modules: information management sub-module 4551, sub-information acquisition module 4552, processing module 4553, information display module 4554, and management realization module 4555. The functions of each module will be described below.
  • the display device 200 includes: at least one second processor 210, a second memory 250, and at least one second processor 210; The network interface 220 and the second user interface 230.
  • the various components in the display device 200 are coupled together through the second bus system 240.
  • the second bus system 240 is used to implement connection and communication between these components.
  • the second bus system 240 also includes a power bus, a control bus, and a status signal bus.
  • various buses are marked as the second bus system 240 in FIG. 3.
  • the second processor 210 may be an integrated circuit chip with signal processing capabilities, such as general-purpose processors, digital signal processors, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc., among which,
  • the general-purpose processor may be a microprocessor or any conventional processor or the like.
  • the second user interface 230 includes one or more second output devices 231 that enable the presentation of media content, including one or more speakers and/or one or more visual display screens.
  • the second user interface 230 also includes one or more second input devices 232, including user interface components that facilitate user input, such as a keyboard, a mouse, a microphone, a touch screen display, a camera, and other input buttons and controls.
  • the second memory 250 includes volatile memory or non-volatile memory, and may also include both volatile and non-volatile memory.
  • the non-volatile memory may be a read-only memory
  • the volatile memory may be a random access memory.
  • the second memory 250 described in the embodiment of the present application intends to include any suitable type of memory.
  • the second memory 250 optionally includes one or more storage devices that are physically distant from the second processor 210.
  • the second memory 250 can store data to support various operations. Examples of these data include programs, modules, and data structures, or a subset or superset thereof, as illustrated below.
  • the second operating system 251 includes system programs for processing various basic system services and performing hardware-related tasks, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks;
  • the second network communication module 252 is used to reach other computing devices via one or more (wired or wireless) second network interfaces 220.
  • Exemplary second network interfaces 220 include: Bluetooth, wireless compatibility authentication, and universal string Line bus, etc.;
  • the second display module 253 is used to enable the presentation of information (for example, for operating peripheral devices and displaying User interface for content and information);
  • the second input processing module 254 is configured to detect one or more user inputs or interactions from one of the one or more second input devices 232 and translate the detected inputs or interactions.
  • the display device for information placement (hereinafter referred to as the display device) provided by the embodiments of the present application may be implemented in software.
  • FIG. 3 shows the display device 255 stored in the second memory 250, which It can be software in the form of programs and plug-ins, including the following software modules: information display submodule 2551, device information submodule 2552, information query submodule 2553, information playback submodule 2554, and display realization module 2555. Each module will be explained below Function.
  • the placing device and display device provided in the embodiment of the present application may be implemented in hardware.
  • the placing device and display device provided in the embodiment of the present application may be a processor in the form of a hardware decoding processor. , It is programmed to execute the information delivery method provided in the embodiments of this application.
  • a processor in the form of a hardware decoding processor may adopt one or more application specific integrated circuits (ASIC, Application Specific Integrated Circuit), DSP, and programmable Logic device (PLD, Programmable Logic Device), complex programmable logic device (CPLD, Complex Programmable Logic Device), field programmable gate array (FPGA, Field-Programmable Gate Array) or other electronic components.
  • FIG. 4 is an optional flowchart of the information delivery method provided by an embodiment of the present application, and will be described in conjunction with the steps shown in FIG. 4.
  • the delivery device receives the delivery operation acting on the delivery control, and responds to the delivery operation through the information management submodule to obtain target delivery information.
  • the delivery object when the delivery object performs information delivery, an application for delivering information is run on the delivery device, and the delivery management interface is also displayed.
  • the delivery control is set on the delivery management interface, and the delivery control is used to receive corresponding operations to trigger the delivery of information; therefore, when the delivery object operates the delivery control on the delivery management interface, the delivery device also receives Now comes the drop operation that acts on the drop control.
  • the delivery device includes a functional module for delivering information, that is, the information management sub-module, the delivery device uses the information management sub-module to respond to the received delivery operation, and can obtain the information to be delivered.
  • Information is target delivery information.
  • the delivery object is an object that delivers information to the display device through the delivery device, such as a merchant or a delivery administrator.
  • the delivery management interface refers to the interface used to implement information delivery management.
  • the information delivery management here includes the processing of adding, deleting, checking, and modifying information, and taking the processing of adding information as an example to describe the processing process of information delivery management.
  • the delivery control is at least one touchable control.
  • the delivery object when the delivery object performs information delivery, enter the delivery copy, delivery merchant, delivery device, delivery duration and other information and click the OK button to enter the delivery copy, delivery merchant,
  • the control of the delivery device, delivery time and other information and the OK button constitute the delivery control;
  • the corresponding delivery operation refers to the operation used to trigger the delivery control, such as input operation, click operation, selection operation, gesture operation, etc., or A combination of multiple operations.
  • the delivery management interface is supported by the information management sub-module to realize information delivery management.
  • the target delivery information refers to the delivered information, such as electronic posters, interactive posters (posters that can interact with users), and mini programs.
  • the target delivery information can include information content, delivery type, delivery batch number, delivery At least one of information such as time, delivery merchant number, delivery status, etc.
  • FIG. 5 is a schematic diagram of an exemplary delivery management interface provided by an embodiment of the present application; as shown in FIG. 5, the electronic poster list interface 51 corresponding to the electronic poster type delivery information is shown.
  • the "New e-poster" button 511 drop control
  • the electronic poster list interface 51 also displays a control 512 for querying the batch number and the merchant number.
  • the two input boxes in the control 512 respectively display the prompt information of Please enter the batch number and the merchant number), and the list of posted information 513; among them, for the released information
  • Each piece of information in the information list 513 also displays the corresponding preview (displayed pictures), delivery type (pictures, etc.), delivery batch number ("xxxx"), delivery time (2020-10-2717:05:58) ), delivery merchant number ("xxxxxxxxxxxxxxxx”), delivery status (offline), and available operations (view, modify, and delivery (when the delivery status is offline, the operation is delivery, and when the delivery status is delivery, the operation is down String).
  • FIG. 6 is a schematic diagram of another exemplary delivery management interface provided by an embodiment of the present application; as shown in FIG. 6, it shows the interactive poster list interface 61 corresponding to the delivery information of the interactive poster type. Interface), the interactive poster list interface 61 displays the "+New interactive poster” button 611 (dropping control), when you click (drop operation) the "+New interactive poster” button 611 to add a new interactive poster (target placement information) At the time, it can realize the placement of new interactive posters on the display equipment.
  • the posted information 612 is also displayed on the interactive poster list interface 61. Each piece of information in the posted information 612 displays a corresponding preview (for example, picture), posting status (posting), and posting time. (2020-10-28 15:49:39), the attributes of the interactive poster (poster name: picture) and the batch number ("xxxxx").
  • the delivery device obtains at least one management sub-information corresponding to the at least one management sub-module according to the target delivery information.
  • the delivery device further includes at least one management sub-module, and the at least one management sub-module is used to process the information to be delivered to realize the delivery of the delivered information on the delivery device; thus, the delivery device obtains After the target delivery information, at least one management sub-module is used to process the target delivery information separately to complete the delivery of the target delivery information on the delivery device; here, at least one management sub-module separately processes the target delivery information to implement the delivery on the delivery device
  • the release of the target first obtain the information to be processed by each management sub-module in at least one management sub-module; when the corresponding pending information is obtained for all the management sub-modules, the information to be processed is also obtained.
  • At least one piece of information to be processed corresponding to at least one management sub-module, and the at least one piece of information to be processed is at least one piece of management sub-information; wherein, at least one piece of management sub-module corresponds to at least one piece of management sub-information one-to-one.
  • the information management sub-module and at least one management sub-module are independent modules based on the results of sub-domain division in the delivery management field. The area where the information is managed.
  • At least one management sub-module includes at least one of an information attribute sub-module, a placement relationship sub-module, an information risk sub-module, an information counting sub-module, and an information storage sub-module; accordingly, at least one management sub-information It includes at least one of target information attributes, target placement relationships, target risk information, target count limit information, and target storage information.
  • the information attribute sub-module refers to the functional module used to manage the attributes of the target posting information; in at least one management sub-information, the corresponding management sub-information is the target information attribute, and the target information attribute refers to the target posting information
  • the placement relationship sub-module refers to the functional module used to manage the placement relationship of the target placement information; in at least one management sub-information, the corresponding management sub-information is the target placement relationship, and the target placement relationship refers to the target placement information.
  • the associated delivery object and display device that is, the target delivery information is the information of which merchant delivers to which display device.
  • the information risk sub-module refers to the functional module used to evaluate whether the target release information meets the preset prescribed conditions; in at least one management sub-information, the corresponding management sub-information is target risk information, and the target risk information refers to the target release
  • the risk information of the information for example, meets the preset prescribed conditions or does not meet the preset prescribed conditions, etc.; the preset prescribed conditions can be the judgment conditions for whether the target posting information is the content allowed to be posted, such as functional applications, promotion of activities, etc. .
  • the information counting submodule refers to a functional module used to determine the posting authority based on the target posting information corresponding to the target posting quantity.
  • the posting permission may include posting permission and prohibition; in at least one management sub-information, the corresponding management
  • the sub-information is the target count limit information, and the target count limit information refers to the maximum number of restricted delivery and the currently delivered number.
  • the information storage sub-module refers to the functional module for storing the information to be stored corresponding to the target posting information; in at least one management sub-information, the corresponding management sub-information is target storage information, and the target storage information refers to the target posting information corresponding to The information to be stored, such as the video or picture that is posted.
  • the delivery device processes at least one management sub-information through at least one management sub-module.
  • each management sub-module in the delivery device after at least one management sub-module in the delivery device obtains at least one one-to-one correspondence of at least one management sub-information, each management sub-module processes the corresponding management sub-information to complete the target delivery information in The delivery of delivery equipment. Therefore, the delivery device can obtain the processing result of the successful delivery including the target delivery information, and at this time, the subsequent S404 is executed. It is easy to know that the processing result obtained by the delivery device may also be that the delivery of the target delivery information fails. At this time, the delivery process is ended.
  • the information risk sub-module obtains target risk information corresponding to the target release information.
  • the release process ends; and when the target release information is determined to comply with the target risk information
  • the information counting sub-module obtains the target count limit information corresponding to the target count limit information.
  • the posting process ends; and when the target count limit information determines the target count limit information
  • the information is not limited by the quantity, update the currently delivered quantity, and obtain the target information attribute of the target delivery information through the information attribute submodule and store it, and obtain the target delivery relationship corresponding to the target delivery information through the delivery relationship submodule and store it , And obtain and store the target storage information corresponding to the target delivery information through the information storage sub-module; in this way, the delivery of the target delivery information on the delivery device is completed.
  • the display device can call the target placement information according to the respective independent modules corresponding to the placement display field to achieve the placement of the target placement information on the display device.
  • the placement display field also belongs to the placement field, which means that the placement field includes two independent parts: the placement management field and the placement display field.
  • the delivery area 71 includes the delivery management area 711 and the delivery display area 712; among them, the delivery management area 711 refers to the business area corresponding to the delivery object, which manages delivery information, including viewing, creating, deleting, and modifying And so on; and the placement display area 712 refers to the business area corresponding to the display device, which is used to display the target placement information of the placement object through the placement device on the IoT device.
  • the delivery device displays the target delivery information on the delivery management interface based on the processing result.
  • the delivered target delivery information will be displayed on the delivery management interface, so as to proceed according to the displayed target delivery information.
  • the management of delivery information for example, delivery, viewing, offline, modification and deletion, etc.; among them, the targeted delivery information for the display, for example, the information displayed in the posted information list 513 in Figure 5, has been launched in Figure 6 The information displayed in the information 612.
  • the delivery device performs delivery processing based on the displayed target delivery information, for example, for the target delivery information
  • the display will be triggered (indicated)
  • the device executes the processing of displaying the target placement information, that is, the display device displays the target placement information according to the respective independent modules corresponding to the placement display field to complete the placement of the target placement information on the display device; where the placement display field is used in the placement field In the field where the posted information is displayed.
  • Fig. 8a is another optional flowchart of the information delivery method provided by an embodiment of the present application; referring to Fig. 8a, the information delivery method includes:
  • the display device responds to the information display request through the information display submodule, displays the information display interface, and instructs the device information submodule to obtain display device information.
  • the display device when the target target has been created on the target device, and the target status is updated to be in progress, if the display device runs the application for displaying the target information, the display device will also receive The information display request is reached; since the display device includes a functional module for triggering the display of the posted information, that is, the information display sub-module, the display device can use the information display sub-module to respond to the information display request and display the information used to display the posted information
  • the information display submodule is used to combine other functional modules in the display device (such as the device information submodule, the information query submodule, and the information playback submodule) to display the posted information; the device information submodule is used to obtain Display the identification information of the device.
  • the display device obtains target delivery information corresponding to the display device information through the information query submodule.
  • the information display submodule instructs the information query submodule to obtain the delivery information associated with the display device information; because the delivery object has completed the target on the delivery device side The delivery of the delivery information, therefore, the delivery information associated with the display device information includes target delivery information; thus, the information query submodule of the display device can obtain the target delivery information.
  • the information query sub-module is used to query the delivery information corresponding to the display device;
  • the target delivery information is the information delivered by the delivery device according to the respective independent modules corresponding to the delivery management field, and the delivery management field is used in the delivery field. In the field of managing the information released.
  • the display device displays the target placement information on the information display interface through the information playback submodule, so as to complete the placement of the target placement information on the display device.
  • the information display submodule instructs the information playback submodule to display the target placement information on the information display interface; at this time, the display of the target placement information is completed.
  • the placement of the device is as shown in the target placement information 81 in Fig. 8b and the target placement information 82 in Fig. 8c.
  • the information playback sub-module is used to play the released information; in addition, the information display sub-module, the device information sub-module, the information query sub-module, and the information playback sub-module are each obtained based on the results of the sub-domain division of the display field Modules that are independent of each other, and the display area is the area where the information to be published is divided from the area based on the placement process.
  • FIG 9 is another optional flowchart of the information delivery method provided in the embodiment of the present application; refer to Figure 9, in the embodiment of the present application, S901-S905 is also included before S401; that is, the delivery device On the delivery management interface, before receiving the delivery operation acting on the delivery control, the information delivery method further includes S901-S905, and each step is described separately below.
  • the delivery device divides the delivery management field into sub-domains according to the delivery demand use cases to obtain multiple information management sub-domains.
  • the delivery device before the delivery device performs the delivery of the target delivery information, it also includes a process in which the delivery device uses the delivery demand use case to obtain an application for delivery information based on a domain-driven design method.
  • the delivery field includes two independent business areas: the delivery management field and the delivery display area; for the delivery management field, the delivery equipment is divided into sub-domains according to the delivery demand use cases, and the divided sub-domains are multiple information management sub-domains. area.
  • the delivery demand use case refers to the business knowledge in the delivery field.
  • multiple information management subdomains include at least one of information storage subdomain, information counting subdomain, information attribute subdomain, information risk subdomain, and placement relationship subdomain, and a placement management subdomain; among them, placement
  • the management subdomain refers to the core domain for managing the delivered information
  • the information storage subdomain refers to the support domain for storing the delivered information
  • the information counting subdomain refers to the support domain for counting the amount of information delivered
  • the information attribute subdomain refers to the delivery
  • the attribute of the information corresponds to the support domain
  • the information risk subdomain refers to the support domain that determines whether the posted information meets the preset prescribed conditions
  • the placement relationship subdomain refers to the support domain corresponding to the placement object and display device associated with the posted information.
  • the delivery management field 101 includes 6 information management sub-domains: delivery management sub-domains Domain 1011, information storage subdomain 1012, information counting subdomain 1013, information attribute subdomain 1014, information risk subdomain 1015, and placement relationship subdomain 1016; and, the placement management subdomain 1011 is the core domain, and the information storage subdomain 1012, The information counting subdomain 1013, the information attribute subdomain 1014, the information risk subdomain 1015, and the placement relationship subdomain 1016 are all supporting domains of the placement management subdomain 1011.
  • the delivery device determines the business scope of multiple information management subdomains according to the delivery demand use case, and determines the business scope of the multiple information management subdomains as multiple management contexts.
  • the delivery device after the delivery device obtains multiple information management subdomains, it determines the business scope corresponding to each information management subdomain in the multiple information management subdomains according to the use cases of the delivery requirements, and thus obtains each information management subdomain.
  • the bounded context corresponding to the subdomain is referred to herein as the management context; thus, multiple management contexts corresponding to multiple information management subdomains are obtained.
  • multiple management contexts include at least one of information storage context, information counting context, information attribute context, information risk context and placement relationship context, and information management context; and, multiple management contexts and multiple information management
  • the information management context is the bound context of the delivery management subdomain
  • the information storage context is the bound context of the information storage subdomain
  • the information counting context is the bound context of the information counting subdomain
  • the information attribute context is the information attribute subdomain.
  • the bounding context of the domain the information risk context is the bounding context of the information risk subdomain
  • the placement relationship context is the bounding context of the placement relationship subdomain.
  • the delivery management sub-domain is the core domain
  • the information storage sub-domain, the information counting sub-domain, the information attribute sub-domain, the information risk sub-domain, and the placement relationship sub-domain are all supporting domains. Therefore, the information storage sub-domain, the information counting sub-domain Domain, information attribute subdomain, information risk subdomain, and placement relationship subdomain, respectively corresponding to the information management context, information storage context, information counting context, information attribute context, information risk context, and placement relationship context, are all related to the placement management subdomain There is a dependency on the information management context of.
  • FIG. 11 is an exemplary schematic diagram of multiple management contexts provided by an embodiment of the present application; as shown in FIG. 11, the delivery management domain 101 includes 6 information management sub-domains : Delivery management sub-domain 1011, information storage sub-domain 1012, information counting sub-domain 1013, information attribute sub-domain 1014, information risk sub-domain 1015, and placement relationship sub-domain 1016; corresponding to 6 management contexts respectively: information management context 111, The information storage context 112, the information counting context 113, the information attribute context 114, the information risk context 115, and the placement relationship context 116.
  • Delivery management sub-domain 1011 Delivery management sub-domain 1011, information storage sub-domain 1012, information counting sub-domain 1013, information attribute sub-domain 1014, information risk sub-domain 1015, and placement relationship sub-domain 1016
  • 6 management contexts respectively: information management context 111, The information storage context 112, the information counting context 113, the information attribute context 114, the information risk context 115, and the placement relationship context 116.
  • the information storage context 112 the information counting context 113, the information attribute context 114, the information risk context 115, and the placement relationship context 116 all have a dependency relationship with the information management context 111, and there is also a relationship between the information count context 113 and the placement relationship context 116.
  • Dependency there is also a relationship between the information count context 113 and the placement relationship context 116.
  • the delivery device analyzes the model elements corresponding to each management context in the multiple management contexts according to the delivery demand use case, so as to obtain multiple management models corresponding to the multiple management contexts.
  • the delivery device after the delivery device obtains multiple management contexts, since the delivery demand use case records each application scenario of information delivery, and the multiple management contexts represent the business scope of each information management subdomain, therefore, According to each management context, the corresponding model elements can be obtained from the delivery demand use cases, and the obtained model elements can be combined into the management model corresponding to each management context, so that when the acquisition of the model elements of multiple management contexts is completed At this time, multiple management models corresponding to multiple management contexts are obtained one-to-one.
  • the delivery device encodes based on multiple management models to obtain a delivery management application including an information management sub-module and at least one management sub-module.
  • each management model obtains information for the functional modules corresponding to each information management subdomain.
  • the functional modules corresponding to each information management subdomain can be obtained, and the The obtained combination of all the functional modules (the information management sub-module and the at least one management sub-module) corresponding to all the information management sub-domains will also obtain the application for the delivery of information on the delivery device side, here, referred to as delivery management application ;
  • the delivery management application includes the above-mentioned information management sub-module and at least one management sub-module, it is easy to know that the information management sub-module corresponds to the delivery management sub-domain, at least one management sub-module and at least one sub-domain (stored by the information Sub-domain, information counting sub-domain, information attribute sub-domain, information risk sub-domain, and placement relationship sub-domain) correspondence; and multiple management sub-modules correspond to multiple management models one-to-one, multiple management
  • the sub-module includes an information management sub-
  • the delivery device runs the delivery management application, and displays the delivery management interface.
  • the delivery management application is run, and then the delivery management interface is displayed, so as to realize the delivery of information on the delivery device side according to the displayed delivery management interface.
  • S904 can be implemented through S9041-S9043; that is, the delivery device analyzes the model elements corresponding to each management context in multiple management contexts according to the delivery demand use case, so as to obtain the corresponding model elements corresponding to the multiple management contexts.
  • Multiple management models including:
  • the delivery device analyzes the model elements corresponding to the current management context according to the delivery demand use case, so as to obtain the current management aggregate root, the current management entity, and the current management value object.
  • the model element corresponding to each management context includes the aggregate root, entity, and value object; here, the delivery device uses any one of the multiple management contexts as the current management context to obtain the corresponding model element,
  • the obtained aggregate root, entity, and value object corresponding to the current management context are, in order, the current management aggregate root, the current management entity, and the current management value object. It is easy to know that the current management context is any management context among multiple management contexts.
  • the delivery device combines the current management aggregation root, the current management entity, and the current management value object into a current management model corresponding to the current management context.
  • the delivery device obtains the current management aggregate root, current management entity, and current management value object corresponding to the current management context, it combines the current management aggregate root, current management entity, and current management value object to obtain the combined result That is, the current management model corresponding to the current management context.
  • the delivery device obtains the current management model according to the current management context, and completes the acquisition of the management model corresponding to each management context in the multiple management contexts, it also obtains the one-to-one correspondence with the multiple management contexts.
  • Multiple management models; easy to know, multiple management models include the current management model.
  • the current management entity when the current management context is an information management context, the current management entity includes a posting record entity, and the current management value object includes an information attribute value object, a posting relationship value object, an information storage value object, an information count value object, and information At least one of the risk value objects.
  • FIG. 12 is a schematic diagram of an exemplary management model corresponding to an information management context provided by an embodiment of the present application; as shown in FIG. 12, the management model corresponding to the information management context 121 includes an aggregate root 1221 The placement record entity 1222, the information attribute value object 1223, and the placement relationship value object 1224.
  • the posting record entity 1222 includes information such as posting information identification and posting status
  • the information attribute value object 1223 includes information such as posting information address, posting information copy, and posting information type
  • the posting relationship value object 1224 includes displaying device information and posting information. Objects etc.
  • the current management context includes the current management adaptation layer.
  • the current management adaptation layer is the adaptation layer corresponding to the current management context. It is used to realize the escape between the external context and the current management context.
  • the management context provides a unified interface for accessing the external context.
  • S9041 can be implemented through S90411-S90413, that is, the delivery device analyzes the model elements corresponding to the current management context according to the delivery demand use case, so as to obtain the current management aggregate root, current management entity, and current management value object, including S90411- S90413, each step will be described separately below.
  • the delivery device obtains its own model elements from the current management context according to the delivery demand use case.
  • the model element when the delivery device obtains the model element corresponding to the current management context according to the delivery demand use case, the model element may be. At this time, if the delivery device obtains the current management context from the current management context according to the delivery demand use case, The model element that manages the context also gets its own model element.
  • the delivery device obtains external model elements from the external context according to the delivery demand use case and the current management adaptation layer.
  • the model element when the delivery device obtains the model element corresponding to the current management context according to the delivery demand use case, the model element may come from an external context. At this time, the delivery device obtains corresponding information by accessing the external context, and Through the current management adaptation layer to escape the corresponding information obtained, the external model element is also obtained.
  • escaping refers to the process of converting to the semantic information required by the current management context; for example, when the context of a field passes through the merchant information adaptation layer to query the external context for the information of the merchant, the merchant information adaptation layer will Information, the characteristic information in the context of the translation cost field, for example, the information of the merchant queried from the external context includes A, B, C...G and other types, while the context in this field only needs to know A, B and For the other three types, the merchant information adaptation layer maps the merchant information queried from the external context to the semantics in the cost field, thus ensuring internal unity and conciseness.
  • the preset external context is a bounded context that belongs to a different domain (a domain outside the delivery domain) from the current management context; the own model element and the external model element are model elements corresponding to the current management context.
  • the delivery device obtains the current management aggregation root, the current management entity, and the current management value object from its own model elements and external model elements.
  • the model element includes its own model element and an external model element.
  • the delivery device obtains its own model original and external model elements, extracts entities and value objects from its own model elements and external model elements, and also obtains the current management aggregate root, current management entity, and current management value object .
  • S904 can also be implemented through S9044-S9046; that is, the delivery device is coded based on multiple management models to obtain a delivery management application that includes an information management sub-module and at least one management sub-module, including S9044- S9046, each step will be described separately below.
  • the delivery device generates creation logic corresponding to each management model according to multiple management models.
  • model elements are implemented by creating model elements; therefore, when the delivery equipment is coded according to the management model, it generates information about the model for each management model.
  • the creation logic of the element to realize the delivery of information through the creation logic.
  • the delivery device uses a preset design mode to encapsulate the creation logic, thereby obtaining multiple optimized creation logics corresponding to multiple management models.
  • a preset design mode is set in the delivery device, or the preset design mode can be obtained, so as to use the preset design mode to encapsulate the creation logic of each management model, and the encapsulated creation logic That is, the optimization creation logic corresponding to each management model; therefore, there are multiple optimization creation logics corresponding to multiple management models; wherein, multiple management models correspond to multiple optimization creation logics in a one-to-one correspondence.
  • the preset design mode is a design mode, such as factory design mode, adapter mode, and prototype mode.
  • the delivery device encodes based on multiple optimization creation logics to obtain a delivery management application including an information management sub-module and at least one management sub-module.
  • the delivery device after the delivery device obtains multiple optimization creation logics, it implements the encoding of multiple optimization creation logics for different types, and thus a delivery management application including an information management sub-module and at least one management sub-module is obtained. .
  • FIG. 13 is a schematic diagram of an exemplary package creation logic provided by an embodiment of the present application; as shown in FIG. 13, the content class 131 is the information corresponding to the management model shown in FIG. Class 131 1311("+insert delivery record():int", “+update delivery record():int”, “+get delivery record():int”, “+insert material content():int”, “ +Update material content ():int”, “+Get material content():int”, “+Insert placement relationship():int”, “+Update placement relationship():int” and “+Get placement relationship() :int) is the creation logic obtained based on Figure 12.
  • 1312 (“+create release():int”, “+update release():int” and “+release details():int”) are The encapsulated creation logic of creation logic 1311 (optimized creation logic); when the preset design mode is factory mode, the logic for creating different content may be inconsistent and the required content attributes are different.
  • creation logic of different posting information may be different, and the required attributes may also be different.
  • the overall complexity can be simplified.
  • FIG. 14 is another optional flowchart of the information delivery method provided in the embodiment of the present application; refer to FIG. 14, in the embodiment of the present application, S1401-S1405 are included before S801. , The following describes each step separately.
  • the display device divides the display area into sub-domains according to the use cases of the placement requirements to obtain multiple information display sub-domains.
  • the display device before the display device displays the target placement information, it also includes a process in which the display device uses the placement demand use case to obtain an application for displaying the placement information based on a domain-driven design approach.
  • the display device divides the subdomains according to the use cases of the placement requirements, and each of the divided subdomains is multiple information display subdomains.
  • the multiple information display subdomains include the placement display subdomain, the information query subdomain, the device information subdomain, and the information playback subdomain; among them, the placement display subdomain refers to the core domain of the displayed information, and the information query The subdomain refers to the supporting domain for querying the information to be posted, the device information subdomain refers to the supporting domain for querying the information of the display device, and the information playing subdomain refers to the supporting domain for playing the released information.
  • FIG. 15 is a schematic diagram of an exemplary sub-domain division result of the placement display area provided by an embodiment of the present application; as shown in FIG. 15, the placement display area 151 includes 4 information display sub-domains: placement display sub-domains: Domain 1511, information query subdomain 1512, device information subdomain 1513, and information playback subdomain 1514; and, the placement display subdomain 1511 is the core domain, and the information query subdomain 1512, device information subdomain 1513, and information playback subdomain 1514 are all It is the supporting domain for the display subdomain 1511.
  • the display device determines the business scope of multiple information display subdomains according to the use case of the delivery requirement, and determines the business scope of the multiple information display subdomains as multiple display contexts.
  • the display device After the display device obtains multiple information display subdomains, it determines the business scope corresponding to each information display subdomain in the multiple information display subdomains according to the use cases of delivery requirements, and thus obtains each information display
  • the bounded context corresponding to the subdomain is referred to herein as the display context; thus, multiple display contexts corresponding to multiple information display subdomains are obtained.
  • multiple display contexts include information display context, information query context, device information context, and information playback context; moreover, multiple display contexts and multiple information display subdomains correspond to each other, that is, the information display context is the placement display
  • the information display context is the placement display
  • the information query context is the bounding context of the information query subdomain
  • the device information context is the bounding context of the device information subdomain
  • the information playing context is the bounding context of the information playing subdomain.
  • the placement and display subdomain is the core domain
  • the information query subdomain, device information subdomain, and information playback subdomain are all supporting domains, therefore, the information query subdomain, device information subdomain, and information playback subdomain correspond to
  • the information query context, device information context, and information playback context all have a dependency relationship with the information display context of the placement display subdomain.
  • FIG. 16 is an exemplary schematic diagram of multiple display contexts provided by an embodiment of the present application; as shown in FIG. 16, the placement display area 151 includes 4 information display sub-domains : Placement display subdomain 1511, information query subdomain 1512, device information subdomain 1513, and information playback subdomain 1514; corresponding to 4 display contexts: information display context 161, information query context 162, device information context 163, and information playback context 164. Among them, the information query context 162, the device information context 163, and the information playback context 164 all have a dependency relationship with the information display context 161.
  • the display device analyzes the model elements corresponding to each display context in the multiple display contexts according to the use case of the delivery requirement, so as to obtain multiple display models corresponding to the multiple display contexts.
  • the display device after the display device obtains multiple display contexts, since the placement requirement use case records each application scenario of information placement, and the multiple display contexts represent the business scope of each information display subdomain, therefore, According to each display context, the corresponding model elements can be obtained from the placement demand use cases, and the obtained model elements can be combined into the display model corresponding to each display context, so that when the acquisition of the model elements of multiple display contexts is completed At the same time, multiple display models corresponding to multiple management contexts are obtained.
  • the display device encodes based on multiple display models to obtain a delivery display application including an information display submodule, a device information submodule, an information query submodule, and an information playback submodule.
  • each display model obtains information for the function module corresponding to each information display subdomain.
  • the function module corresponding to each information display subdomain can be obtained.
  • the obtained combination of all the functional modules corresponding to all the information display subdomains also obtains the application used to display the display information on the display device side, here, it is called the display application; and the display application includes the above information display
  • the sub-module, the device information sub-module, the information query sub-module, and the information playback sub-module are easy to know, the information display sub-module corresponds to the placement display sub-domain, the device information sub-module corresponds to the device information sub-domain, and the information query sub-module corresponds to the device information Corresponding to the sub-domain, the information playing sub-module corresponds to the information playing sub-domain.
  • the display device runs a display application to generate an information display request.
  • the display device after the display device obtains the display application, it runs the display application to generate an information display request, so as to realize the display of the published information on the display device according to the generated information display request.
  • the display device in S1403 analyzes the model elements corresponding to each context in multiple display contexts according to the use cases of placement requirements, so as to obtain multiple display models corresponding to multiple display contexts, and also obtains the aggregation root and entity
  • the sum value object realizes the acquisition of the display model; that is to say, the delivery device analyzes the model elements corresponding to the current display context according to the delivery demand use case, so as to obtain the current display aggregation root, current display entity, and current display value object.
  • the current display context is Any one of multiple display contexts; combine the current display aggregation root, current display entity, and current display value object into the current display model corresponding to the current display context; when the processing of each display context in the multiple display contexts is completed At this time, multiple display models corresponding to multiple display contexts are obtained, and the multiple display models include the current display model.
  • the display device in S1404 is encoded based on multiple display models, and when the display application including the information display sub-module, the device information sub-module, the information query sub-module, and the information playback sub-module is obtained, it is also through the adaptation layer and presets. The implementation of the design mode will not be repeated here in the embodiment of the application.
  • the information delivery system corresponding to the delivery display application and delivery management application can be implemented in a waterfall mode in addition to the implementation of the above-mentioned DDD.
  • the different areas divided include content management sub-domains (delivery management sub-domains), content storage sub-domains (information storage sub-domains), content counting sub-domains (information counting sub-domains), and content attribute sub-domains ( Information attribute sub-domain), content risk sub-domain (information risk sub-domain), and placement relationship sub-domain content management domain (delivery management domain), as well as including device content display sub-domain (placement display sub-domain), content query sub-domain ( Information query sub-domain), device information sub-domain and content playing sub-domain (information playing sub-domain) device content display area (drop display area).
  • the content management field and the device content display field are two independent fields in the delivery field; among them, the content management field: the field where the merchant manages the content, including viewing, creating, deleting, etc.; the device content display field: the merchant’s The area where content is displayed on IoT devices.
  • the content management subdomain is the core of the entire field, supported by 5 subdomains:
  • Content attribute subdomain the domain of related attributes such as unique identification and status;
  • Distribution relationship subdomain the field of related information about content distribution, such as which devices and merchants are distributed to;
  • Content risk sub-domain The content is created by merchants, and there may be some non-compliance situations that need to be managed;
  • Content counting sub-domain the area that needs to limit the number of merchants
  • Content storage subdomain The domain where the content is stored, such as images, videos, and so on.
  • the device content display sub-domain is the core of the entire field, supported by 3 sub-domains:
  • Device information subdomain the domain for querying the information of the current device
  • Content query sub-domain query which content is available on the current device
  • Content playback subdomain The domain where the content will be played.
  • the corresponding entities, value objects, and aggregate roots are analyzed for each boundary context, and the analyzed entities, value objects, and aggregate roots are combined to obtain each The refined model (multiple management models and multiple display models) corresponding to the bounded context.
  • FIG. 18 is an exemplary information placement architecture diagram provided by an embodiment of the present application; as shown in FIG. 18, the merchant 18-1 ( Target delivery) Create delivery content 18-3 (target delivery information) through the management interface 18-211 (delivery management interface) displayed on the delivery device 18-21 in the information delivery system 18-2 to establish the delivery content and the IoT device 18 -22 (display device) association; here, the process of creating the content 18-3 is similar to the process of creating a new electronic poster described in FIG.
  • the delivery content 18-3 When the delivery status of the delivery content 18-3 is set to delivery through the management interface 18-211, the delivery content 18-3 will be displayed on the IoT device 18-22; at this time, the merchant 18-1 has also completed the delivery content 18-3 is placed on IoT device 18-22.
  • FIG. 19 is an exemplary information placement interaction diagram provided by an embodiment of the present application; as shown in FIG. 19, the exemplary information placement process includes:
  • the delivery device in response to the creation operation (posting operation) acting on the new button (posting control), the delivery device obtains the delivery content (target delivery information) based on the encapsulated creation logic (information management submodule) in the content management field.
  • the delivery device processes the delivered content based on the encapsulated creation logic (at least one management sub-module) in the content management field.
  • the delivery device finishes processing the delivery content, it stores the associated data between the delivery content and the display device in a database.
  • the delivery device displays the delivery content on the management interface based on the associated data.
  • the delivery device updates the delivery status of the delivery content in the database to delivery.
  • the IoT device obtains the delivery status from the database as the delivery content being delivered based on the encapsulated creation logic (information display sub-module, device information sub-module, and information query sub-module) in the field of device content display.
  • the encapsulated creation logic information display sub-module, device information sub-module, and information query sub-module
  • the IoT device displays the delivered content based on the encapsulated creation logic (information playback submodule) in the device content display field.
  • the software module stored in the delivery device 455 of the first memory 450 may include :
  • the information management sub-module 4551 is configured to receive the delivery operation acting on the delivery control on the delivery management interface, and respond to the delivery operation to obtain target delivery information;
  • the sub-information acquisition module 4552 is configured to acquire at least one management sub-information corresponding to at least one management sub-module according to the target delivery information; wherein, the information management sub-module and the at least one management sub-module are based on the delivery management field
  • Each of the mutually independent modules obtained as a result of the sub-domain division of, the delivery management field is a field used to manage the delivered information in the delivery field;
  • the processing module 4553 is configured to process the at least one management sub-information through the at least one management sub-module;
  • the information display module 4554 is configured to display the target delivery information on the delivery management interface according to the processing result, and instruct the display device to display the target delivery information according to an independent module corresponding to the delivery display field based on the displayed target delivery information,
  • the placement display field is a field in the placement field for displaying the placed information.
  • the at least one management sub-module includes at least one of an information attribute sub-module, a placement relationship sub-module, an information risk sub-module, an information counting sub-module, and an information storage sub-module; the at least one management sub-module
  • the sub-information includes at least one of target information attributes, target placement relationships, target risk information, target count limit information, and target storage information.
  • the delivery device 455 further includes a management realization module 4555 configured to divide the delivery management field into sub-domains according to the delivery demand use case to obtain multiple information management sub-domains.
  • the delivery demand use case Including the business knowledge of the delivery domain; determining the business scope of the multiple information management sub-domains according to the delivery demand use case, and determining the business scope of the multiple information management sub-domains as multiple management contexts;
  • the use case of the delivery requirement is described, and the model elements corresponding to each management context in the multiple management contexts are analyzed to obtain multiple management models corresponding to the multiple management contexts; coding is performed based on the multiple management models to obtain
  • the information management sub-module and the delivery management application of the at least one management sub-module, the multiple management sub-modules correspond to the multiple management models, and the multiple management sub-modules include the information management sub-module and the At least one management sub-module; run the delivery management application and display the delivery management interface.
  • the management realization module 4555 is also configured to analyze the model elements corresponding to the current management context according to the delivery demand use case, so as to obtain the current management aggregate root, the current management entity, and the current management value object.
  • the current management context is any one of the multiple management contexts; combining the current management aggregation root, the current management entity, and the current management value object into the current management corresponding to the current management context Model; when the processing of each of the multiple management contexts is completed, the multiple management models corresponding to the multiple management contexts are obtained, and the multiple management models include the current management model.
  • the multiple information management subdomains include at least one of an information storage subdomain, an information counting subdomain, an information attribute subdomain, an information risk subdomain, and a placement relationship subdomain, and a placement management subdomain ;
  • the delivery management sub-domain refers to the core domain for managing the delivered information
  • the information storage sub-domain refers to the support domain that stores the delivered information
  • the information counting sub-domain refers to the number of statistics delivered Supporting domain
  • the information attribute subdomain refers to the supporting domain corresponding to the attribute of the posted information
  • the information risk subdomain refers to the supporting domain for determining whether the posted information satisfies a preset prescribed condition
  • the placement relationship subdomain is Refers to the delivery object associated with the delivered information and the support domain corresponding to the display device
  • the multiple management contexts include at least one of an information storage context, an information counting context, an information attribute context, an information risk context, and a delivery relationship context, and information management Context.
  • the current management entity when the current management context is the information management context, the current management entity includes a posting record entity, and the current management value object includes an information attribute value object, a posting relationship value object, and an information storage value At least one of an object, an information count value object, and an information risk value object.
  • the current management context includes the current management adaptation layer; the management realization module 4555 is further configured to obtain its own model elements from the current management context according to the delivery demand use case;
  • the delivery demand use case and the current management adaptation layer obtain external model elements from an external context, and the self model element and the external model element are model elements corresponding to the current management context; from the self model element And in the external model element, acquiring the current management aggregate root, the current management entity, and the current management value object.
  • the management implementation module 4555 is further configured to generate the creation logic corresponding to each management model according to the multiple management models; use a preset design mode to encapsulate the creation logic to obtain the Multiple optimization creation logics corresponding to the multiple management models; encoding based on the multiple optimization creation logics to obtain the delivery management application including the information management sub-module and the at least one management sub-module.
  • the software module stored in the display device 255 of the second memory 250 may include :
  • the information display submodule 2551 is configured to respond to an information display request, display an information display interface, and instruct the device information submodule 2552 to obtain display device information;
  • the information query sub-module 2553 is configured to obtain target placement information corresponding to the display device information.
  • the target placement information is the information that the placement device releases according to the respective independent modules corresponding to the placement management domain, and the placement management domain is The field used to manage the released information in the placement field;
  • the information playing submodule 2554 is configured to display the target placement information on the information display interface, so as to complete the placement of the target placement information on the display device; wherein, the information display submodule 2551, the device The information sub-module 2552, the information query sub-module 2553, and the information play sub-module 2554 are mutually independent modules obtained based on the results of the sub-domain division of the placement display area, and the placement display area is used in the placement area. In the field where the posted information is displayed.
  • the display device 255 further includes a display realization module 2555, which is configured to divide the delivery display area into sub-domains according to the delivery demand use case to obtain multiple information display sub-domains.
  • the delivery demand use case Including the business knowledge of the delivery domain; determining the business scope of the multiple information display subdomains according to the delivery demand use case, and determining the business scope of the multiple information display subdomains as multiple display contexts; Describe the use case of delivery requirements, analyze the model elements corresponding to each of the multiple display contexts, so as to obtain multiple display models corresponding to the multiple display contexts; perform encoding based on the multiple display models to obtain The information display submodule, the device information submodule, the information query submodule, and the delivery display application of the information playback submodule; run the delivery display application to generate the information display request.
  • the multiple information display subdomains include a placement display subdomain, an information query subdomain, a device information subdomain, and an information playback subdomain;
  • the placement display subdomain refers to the core of the displayed information Domain
  • the information query subdomain refers to the support domain for querying the posted information
  • the device information subdomain refers to the support domain for querying the information of the posted device
  • the information playback subdomain refers to the support for playing the posted information Domain
  • the multiple display contexts include information display context, information query context, device information context, and information playback context.
  • the display implementation module 2555 is further configured to analyze the model elements corresponding to the current display context according to the delivery demand use case, so as to obtain the current display aggregation root, the current display entity, and the current display value object.
  • the current display context is any one of the multiple display contexts; the current display aggregation root, the current display entity, and the current display value object are combined into the current display corresponding to the current display context Model; when the processing of each of the multiple display contexts is completed, the multiple display models corresponding to the multiple display contexts are obtained, and the multiple display models include the current display model.
  • the embodiment of the present application provides a computer-readable storage medium storing executable instructions, and the executable instructions are stored therein.
  • the first processor When the executable instructions are executed by a first processor, the first processor will cause the first processor to execute the provided embodiments of the present application.
  • the information delivery method applied to the delivery device for example, the information delivery method shown in FIG. 4; when the executable instruction is executed by the second processor, the second processor will cause the second processor to execute the application display provided in the embodiment of the application.
  • the information delivery method of the device for example, the information delivery method shown in FIG. 8a.
  • the computer-readable storage medium may be FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories.
  • Various equipment may be FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories.
  • Various equipment may be FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories.
  • Various equipment may be FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; it may also include one or any combination of the foregoing memories.
  • executable instructions may be in the form of programs, software, software modules, scripts or codes, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and their It can be deployed in any form, including being deployed as an independent program or as a module, component, subroutine or other unit suitable for use in a computing environment.
  • executable instructions may but do not necessarily correspond to files in the file system, and may be stored as part of files that save other programs or data, for example, in HyperText Markup Language (HTML, HyperText Markup Language) documents
  • HTML HyperText Markup Language
  • One or more scripts in are stored in a single file dedicated to the program in question, or in multiple coordinated files (for example, a file storing one or more modules, subroutines, or code parts).
  • executable instructions can be deployed to be executed on one computing device, or on multiple computing devices located in one location, or on multiple computing devices that are distributed in multiple locations and interconnected by a communication network Executed on.
  • the delivery device processes the target delivery information according to each independent module in the delivery management field to complete the delivery of the target delivery information on the delivery device.
  • the display device displays the target placement information according to the respective independent modules corresponding to the placement display field; and since the respective independent modules in the placement management field are obtained based on the results of the sub-domain division of the placement management field, each of the placement display fields corresponds to each other.
  • the independent modules are obtained based on the results of sub-domain division of the display area. Therefore, the coupling of the functional modules used to display the target information is low, which can simplify the information delivery process, improve the efficiency of information delivery, and reduce information The complexity of delivery.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Game Theory and Decision Science (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Economics (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种信息投放方法、装置、设备及计算机可读存储介质；方法包括：投放设备在投放管理界面上，接收作用在投放控件上的投放操作，通过信息管理子模块响应投放操作，获取目标投放信息（S401）；投放设备依据目标投放信息，获取至少一个管理子模块对应的至少一个管理子信息（S402）；投放设备通过至少一个管理子模块对至少一个管理子信息进行处理（S403）；投放设备基于处理结果在投放管理界面上，展示目标投放信息（S404）。

Description

一种信息投放方法、装置、设备及计算机可读存储介质
相关申请的交叉引用
本申请基于申请号为202010553240.X、申请日为2020年06月17日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本申请涉及互联网领域中的信息处理技术，尤其涉及一种信息投放方法、装置、设备及计算机可读存储介质。
背景技术
目前，通过投放的信息(比如，多媒体信息)获取产品收益的需求越来越多；而信息的投放，通常是通过投放***或投放应用实现的，因此，投放***或投放应用与信息的投放具有强相关性。
一般来说，为了实现信息投放，通常通过投放***在投放设备上进行信息的投放，并在展示设备上展示，来实现信息在展示设备的投放。然而上述信息投放的过程，所采用的投放***通常是采用敏捷方式实现的。由于所采用的敏捷方式是一种以人为核心、迭代、循序渐进的开发方式，投放***中各功能模块的耦合度高，需要不断重构代码、框架，以应对不断变化的业务需求；因此，信息投放的复杂度较高。
发明内容
本申请实施例提供一种信息投放方法、装置、设备及计算机可读存储介质，能够简化信息投放的流程，提升信息投放的效率。
本申请实施例的技术方案是这样实现的：
本申请实施例提供一种信息投放方法，所述方法由投放设备执行，包括：
在投放管理界面上，接收作用在投放控件上的投放操作，通过信息管理子模块响应所述投放操作，获取目标投放信息；
依据所述目标投放信息，获取至少一个管理子模块对应的至少一个管理子信息，其中，所述信息管理子模块和所述至少一个管理子模块为基于投放管理领域的子域划分结果得到的独立的模块，所述投放管理领域为投放领域划中用于对投放的信息进行管理的领域；
通过所述至少一个管理子模块对所述至少一个管理子信息进行处理；
依据处理结果在所述投放管理界面上，展示所述目标投放信息，基于展示的目标投放信息，指示展示设备依据投放展示领域对应的独立的模块展示所述目标投放信息，所述投放展示领域为所述投放领域中用于对投放的信息进行展示的领域。
本申请实施例还提供一种信息投放方法，所述方法由展示设备执行，包括：
通过信息展示子模块响应信息展示请求，展示信息展示界面，指示设备信息子模块 获取展示设备信息；
通过信息查询子模块获取所述展示设备信息对应的目标投放信息，所述目标投放信息为投放设备依据投放管理领域对应的各个互相独立的模块所投放的信息，所述投放管理领域为投放领域中用于对投放的信息进行管理的领域；
所述信息播放子模块在所述信息展示界面上展示所述目标投放信息；
其中，所述信息展示子模块、所述设备信息子模块、所述信息查询子模块和所述信息播放子模块为基于投放展示领域的子域划分结果得到的各个互相独立的模块，所述投放展示领域为所述投放领域中用于对投放的信息进行展示的领域。
本申请实施例提供一种用于信息投放的投放装置，包括：
信息管理子模块，配置为在投放管理界面上，接收作用在投放控件上的投放操作，响应所述投放操作，获取目标投放信息；
子信息获取模块，配置为依据所述目标投放信息，获取至少一个管理子模块对应的至少一个管理子信息；其中，所述信息管理子模块和所述至少一个管理子模块为基于投放管理领域的子域划分结果得到的各个互相独立的模块，所述投放管理领域为基于投放流程从投放领域划分出的用于对投放的信息进行管理的领域；
处理模块，配置为通过所述至少一个管理子模块对所述至少一个管理子信息进行处理；
信息展示模块，配置为依据处理结果在所述投放管理界面上，展示所述目标投放信息，基于展示的目标投放信息指示展示设备依据投放展示领域对应的各个互相独立的模块展示所述目标投放信息，所述投放展示领域为所述投放领域中用于对投放的信息进行展示的领域。
本申请实施例提供一种用于信息投放的展示装置，包括：
信息展示子模块，配置为响应信息展示请求，展示信息展示界面，指示设备信息子模块获取展示设备信息；
信息查询子模块，配置为获取所述展示设备信息对应的目标投放信息，所述目标投放信息为投放设备依据投放管理领域对应的各个互相独立的模块所投放的信息，所述投放管理领域为投放领域中用于对投放的信息进行管理的领域；
信息播放子模块，配置为在所述信息展示界面上展示所述目标投放信息；其中，所述信息展示子模块、所述设备信息子模块、所述信息查询子模块和所述信息播放子模块为基于投放展示领域的子域划分结果得到的各个互相独立的模块，所述投放展示领域为所述投放领域中用于对投放的信息进行展示的领域。
本申请实施例提供一种用于信息投放的投放设备，包括：
第一存储器，用于存储可执行指令；
第一处理器，用于执行所述第一存储器中存储的可执行指令时，实现本申请实施例提供的应用于投放设备的信息投放方法。
本申请实施例提供一种用于信息投放的展示设备，包括：
第二存储器，用于存储可执行指令；
第二处理器，用于执行所述第二存储器中存储的可执行指令时，实现本申请实施例提供的应用于展示设备的信息投放方法。
本申请实施例提供一种计算机可读存储介质，其特征在于，存储有可执行指令，用于引起第一处理器执行时，实现应用于投放设备的信息投放方法；或者用于引起第二处理器执行时，实现应用于展示设备的信息投放方法。
本申请实施例至少具有以下有益效果：在进行目标投放信息的投放时，投放设备依据投放管理领域的各个互相独立的模块对目标投放信息进行处理，以完成目标投放信息 在投放设备的投放，进而使展示设备依据投放展示领域对应的各个互相独立的模块展示目标投放信息；而由于投放管理领域的各个互相独立的模块是基于投放管理领域的子域划分结果得到的，投放展示领域对应的各个互相独立的模块是基于投放展示领域的子域划分结果得到的，因此，用于展示目标投放信息的各功能模块的耦合度低，从而能够简化信息投放的流程，提升信息投放的效率。
附图说明
图1是本申请实施例提供的信息投放***的一个可选的架构示意图；
图2是本申请实施例提供的一种投放设备的组成结构示意图；
图3是本申请实施例提供的一种展示设备的组成结构示意图；
图4是本申请实施例提供的信息投放方法的一个可选的流程示意图；
图5是本申请实施例提供的一种示例性的投放管理界面示意图；
图6是本申请实施例提供的另一种示例性的投放管理界面示意图；
图7是本申请实施例提供的一种示例性的投放领域划分结果示意图；
图8a是本申请实施例提供的信息投放方法的另一个可选的流程示意图；
图8b是本申请实施例提供的一种示例性的展示目标投放信息的示意图；
图8c是本申请实施例提供的另一种示例性的展示目标投放信息的示意图；
图9是本申请实施例提供的信息投放方法的又一个可选的流程示意图；
图10是本申请实施例提供的一种示例性的投放管理领域的子域划分结果的示意图；
图11是本申请实施例提供的一种示例性的多个管理上下文的示意图；
图12是本申请实施例提供的一种示例性的信息管理上下文对应的管理模型示意图；
图13是本申请实施例提供的一种示例性的封装创建逻辑的示意图；
图14是本申请实施例提供的信息投放方法的再一个可选的流程示意图；
图15是本申请实施例提供的一种示例性的投放展示领域的子域划分结果的示意图；
图16是本申请实施例提供的一种示例性的多个展示上下文的示意图；
图17是本申请实施例提供的一种示例性的获取信息投放***的流程示意图；
图18是本申请实施例提供的一种示例性的信息投放架构图；
图19是本申请实施例提供的一种示例性的信息投放交互图。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请作进一步地详细描述，所描述的实施例不应视为对本申请的限制，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例，都属于本申请保护的范围。
在以下的描述中，涉及到“一些实施例”，其描述了所有可能实施例的子集，但是可以理解,“一些实施例”可以是所有可能实施例的相同子集或不同子集，并且可以在不冲突的情况下相互结合。
在以下的描述中，所涉及的术语“第一\第二”仅仅是区别类似的对象，不代表针对对象的特定排序，可以理解地，“第一\第二”在允许的情况下可以互换特定的顺序或先后次序，以使这里描述的本申请实施例能够以除了在这里图示或描述的以外的顺序实施。
除非另有定义，本申请实施例所使用的所有的技术和科学术语与属于本申请的技术领域的技术人员通常理解的含义相同。本申请实施例中所使用的术语只是为了描述本申请实施例的目的，不是旨在限制本申请。
对本申请实施例进行进一步详细说明之前，对本申请实施例中涉及的名词和术语进行说明，本申请实施例中涉及的名词和术语适用于如下的解释。
1)领域驱动设计(Domain Driven Design，DDD)：一种基于业务中的领域建立领域模型，并通过领域模型(Domain Model)设计和指导软件开发的一种方法；其中，领域模型是指能够精确反映业务中的领域中的某一知识元素的载体，是对领域内的概念类或现实世界中对象的可视化表示，通过分析问题领域(比如，投放领域)本身，发掘重要的业务领域概念，并建立业务领域概念之间的关系。在本申请实施例中，可以在投放领域中采用DDD实现信息投放。
2)限界上下文(Bounded Context，BC)：是指领域模型的分隔适用性；通过限界上下文，能够使团队成员清楚地共享一致的内容以及可以独立开发的内容。通常，限界上下文包括术语、应用场景，还包括名词和动词；其中，名词可以用于对领域对象命名，如商品、订单等，对应实体对象；动词则表示一个动作或事件，如商品已下单、订单已付款等，对应领域事件或者命令。另外，限界上下文通常简称为上下文；以及本申请实施例中所涉及的管理上下文和展示上下文，均是一种限界上下文。
3)实体：是指用其唯一标识来与其他对象进行区分的对象，是领域模型的基本元素，比如一条订单。
4)值对象：是指用其属性来与其他对象进行区分的对象，比如一种瓷砖，用于区分其他对象的属性为大小和材质等；在领域模型中是可以被共享的，当有其他地方需要用到值对象时，可以将值对象的副本作为参数传递，以实现在其他地方的共享。
5)聚合根：一个特殊的实体，是对应上下文提供给外部的上下文的一个数据访问窗口；也就是说，在对应上下文中，其他上下文，通过聚合根来访问该对应上下文的所有实体和值对象。
6)物联网(Internet of things，IoT)设备：是指可以接入互联网的硬件设备，比如，共享充电宝，共享雨伞，共享单车，刷脸设备等。在本申请实施例中，展示设备可以是一种IoT设备。
7)信息投放：是指投放对象将待投放信息投放在IoT设备上，以获取投放收益的过程。
8)设计模式(Design Pattern)，又称软件设计模式，是一套被反复使用、多数人知晓的、经过分类编目的、代码设计经验的总结。使用设计模式是为了可重用代码、让代码更容易被他人理解、保证代码可靠性、程序的重用性。其中，设计模式包括多种，比如，工厂模式、瀑布流模式、适配器模式和原型模式等。
9)工厂模式：又称为创建模式，是一种创建对象的方式，通过工厂模式，能够方便创建同种类型接口产品的复杂对象。
10)瀑布流模式：一个项目开发架构，开发过程是通过设计一系列阶段顺序展开的，从***需求分析开始直到产品发布和维护，每个阶段都会产生循环反馈；在瀑布流模式中，将软件项目的开发分隔成各个开发阶段：需求分析，要件定义，基本设计，详细设计，编码，单体测试，结合测试，***测试等，并采用里程碑的方式，严格定义了各开发阶段的输入和输出，如果达不到要求的输出，下一阶段的工作就不展开。
11)适配器模式：将一个功能模块(比如，类)的接口适配成指定的形式的过程，通过适配器模型，能够使得因为接口不兼容而不能共同实现业务功能的功能模块结合，实现指定功能。
12)原型模式：是一种创建型设计模式，通过将一个原型对象传给发动创建的对象，使得发动创建的对象通过请求原型对象拷贝原型对象自身来实施创建。
13)子域：是指业务的领域对应的划分后的结果，子域对应更小的问题域。一般来 说，子域可以根据自身重要性和功能属性划分为三类子域，它们分别是：核心域、通用域和支撑域。其中，核心域是决定产品和公司核心竞争力的子域，是业务成功的主要因素和公司的核心竞争力；通用域是指没有太多个性化的诉求，同时被多个子域使用的通用功能子域；支撑域是既不包含决定产品和公司核心竞争力的功能，也不包含通用功能的子域。
14)防腐层(Anticorruption Layer)：一个上下文通过一些适配和转换与另一个上下文交互，亦称适配层。在一个上下文中，有时需要对外部上下文进行访问，通常会通过防腐层来对外部上下文的访问进行转义。
一般来说，为了实现信息投放，通常通过投放***在投放设备上进行信息的投放，并在展示设备上展示，来实现信息在展示设备的投放。然而上述信息投放的过程，所采用的投放***通常是采用敏捷方式实现的，由于所采用的敏捷方式是一种以人为核心、迭代、循序渐进的开发方式，投放***中各功能模块的耦合度高，需要不断重构代码、框架，以应对不断变化的业务需求；因此，信息投放的复杂度高。
另外，利用敏捷方式虽然能在投放***的获取初期保证效率，但是由于未对投放领域进行深入研究和建模，投放***的获取后期仅能不断重构代码、框架，以应对不断变化的业务需求。整体的***复杂度高，可维护性低；进而，利用投放***进行信息在展示设备上的投放时，需在耦合度高的多个功能模块之间进行多次交互，因此，导致资源消耗大。
基于此，本申请实施例提供一种信息投放方法、装置、设备和计算机可读存储介质，能够降低投放***中各功能模块的耦合度，简化信息投放的流程，提升信息投放的效率，降低信息投放的复杂度，减小资源消耗。下面说明本申请实施例提供的用于信息投放的设备(包括投放设备和展示设备)的示例性应用，本申请实施例提供的投放设备和展示设备均可以实施为智能手机、平板电脑、笔记本电脑等各种类型的用户终端，也可以实施为服务器，还可以实施为终端和服务器。下面，将说明投放设备实施为终端和服务器，以及展示设备实施为终端和服务器时的示例性应用。
参见图1，图1是本申请实施例提供的信息投放***的一个可选的架构示意图；如图1所示，为支撑一个信息投放应用，在信息投放***100中，服务器100-1通过网络连接终端100-2(服务器100-1和终端100-2共同构成本申请实施例的投放设备)和终端100-3(服务器100-1和终端100-3共同构成本申请实施例的展示设备)；其中，网络可以是广域网或者局域网，又或者是二者的组合；另外，该信息投放***100中还包括数据库100-4，用于在服务器100-1执行本申请实施例提供的信息投放方法时，向服务器100-1提供数据支持。
终端100-2，用于在投放管理界面上，接收作用在投放控件上的投放操作，信息管理子模块响应投放操作，获取目标投放信息；通过网络将目标投放信息发送至服务器100-1。还用于通过网络接收服务器100-1发送的处理结果，并基于处理结果在投放管理界面上，展示投放的目标投放信息；基于展示的目标投放信息通过网络向服务器100-1发送将目标投放信息的投放状态设置为投放中的请求。
服务器100-1，用于通过网络接收终端100-2发送的目标投放信息；依据目标投放信息，获取至少一个管理子模块对应的至少一个管理子信息；其中，信息管理子模块和至少一个管理子模块为基于投放管理领域的子域划分结果得到的各个互相独立的模块，投放管理领域为基于投放流程从投放领域划分出的用于对投放的信息进行管理的领域；至少一个管理子模块对至少一个管理子信息进行处理，此时，数据库100-4中就存储了目标投放信息与展示设备的关联信息，从而，通过网络向终端100-2发送处理结果；还用于通过网络接收终端100-2发送的将目标投放信息的投放状态设置为投放中的请求， 将数据库100-4中目标投放信息的投放状态设置为投放中。还用于通过网络获取终端100-3发送的信息展示请求，通过信息展示子模块响应信息展示请求，指示设备信息子模块获取展示设备信息；通过信息查询子模块从数据库100-4中获取展示设备信息对应的目标投放信息，目标投放信息为投放设备依据投放管理领域对应的各个互相独立的模块所投放的信息；通过信息播放子模块通过网络向终端100-3发送目标投放信息，以完成目标投放信息在展示设备的投放；其中，信息展示子模块、设备信息子模块、信息查询子模块和信息播放子模块为基于投放展示领域的子域划分结果得到的各个互相独立的模块。
终端100-3，用于通过网络向服务器发送信息展示请求；还用于通过网络接收服务器100-1针对信息展示请求发送的目标投放信息，在信息展示界面上展示目标投放信息。
参见图2，图2是本申请实施例提供的一种投放设备的组成结构示意图；如图2所示，投放设备400包括：至少一个第一处理器410、第一存储器450、至少一个第一网络接口420和第一用户接口430。投放设备400中的各个组件通过第一总线***440耦合在一起。可理解，第一总线***440用于实现这些组件之间的连接通信。第一总线***440除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图2中将各种总线都标为第一总线***440。
第一处理器410可以是一种集成电路芯片，具有信号的处理能力，例如通用处理器、数字信号处理器(DSP，Digital Signal Processor)，或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等，其中，通用处理器可以是微处理器或者任何常规的处理器等。
第一用户接口430包括使得能够呈现媒体内容的一个或多个第一输出装置431，包括一个或多个扬声器和/或一个或多个视觉显示屏。第一用户接口430还包括一个或多个第一输入装置432，包括有助于用户输入的用户接口部件，比如键盘、鼠标、麦克风、触屏显示屏、摄像头、其他输入按钮和控件。
第一存储器450包括易失性存储器或非易失性存储器，也可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(ROM，Read Only Memory)，易失性存储器可以是随机存取存储器(RAM，Random Access Memory)。本申请实施例描述的第一存储器450旨在包括任意适合类型的存储器。第一存储器450可选地包括在物理位置上远离第一处理器410的一个或多个存储设备。
在一些实施例中，第一存储器450能够存储数据以支持各种操作，这些数据的示例包括程序、模块和数据结构或者其子集或超集，下面示例性说明。
第一操作***451，包括用于处理各种基本***服务和执行硬件相关任务的***程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务；
第一网络通信模块452，用于经由一个或多个(有线或无线)第一网络接口420到达其他计算设备，示例性的第一网络接口420包括：蓝牙、无线相容性认证(Wi-Fi)、和通用串行总线(USB，Universal Serial Bus)等；
第一显示模块453，用于经由一个或多个与第一用户接口430相关联的第一输出装置431(例如，显示屏、扬声器等)使得能够呈现信息(例如，用于操作***设备和显示内容和信息的用户接口)；
第一输入处理模块454，用于对一个或多个来自一个或多个第一输入装置432之一的一个或多个用户输入或互动进行检测以及翻译所检测的输入或互动。
在一些实施例中，本申请实施例提供的用于信息投放的投放装置(以下简称为投放装置)可以采用软件方式实现，图2示出了存储在第一存储器450中的投放装置455， 其可以是程序和插件等形式的软件，包括以下软件模块：信息管理子模块4551、子信息获取模块4552、处理模块4553、信息展示模块4554和管理实现模块4555，将在下文中说明各个模块的功能。
参见图3，图3是本申请实施例提供的一种展示设备的组成结构示意图；如图3所示，展示设备200包括：至少一个第二处理器210、第二存储器250、至少一个第二网络接口220和第二用户接口230。展示设备200中的各个组件通过第二总线***240耦合在一起。可理解，第二总线***240用于实现这些组件之间的连接通信。第二总线***240除包括数据总线之外，还包括电源总线、控制总线和状态信号总线。但是为了清楚说明起见，在图3中将各种总线都标为第二总线***240。
第二处理器210可以是一种集成电路芯片，具有信号的处理能力，例如通用处理器、数字信号处理器，或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等，其中，通用处理器可以是微处理器或者任何常规的处理器等。
第二用户接口230包括使得能够呈现媒体内容的一个或多个第二输出装置231，包括一个或多个扬声器和/或一个或多个视觉显示屏。第二用户接口230还包括一个或多个第二输入装置232，包括有助于用户输入的用户接口部件，比如键盘、鼠标、麦克风、触屏显示屏、摄像头、其他输入按钮和控件。
第二存储器250包括易失性存储器或非易失性存储器，也可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器，易失性存储器可以是随机存取存储器。本申请实施例描述的第二存储器250旨在包括任意适合类型的存储器。第二存储器250可选地包括在物理位置上远离第二处理器210的一个或多个存储设备。
在一些实施例中，第二存储器250能够存储数据以支持各种操作，这些数据的示例包括程序、模块和数据结构或者其子集或超集，下面示例性说明。
第二操作***251，包括用于处理各种基本***服务和执行硬件相关任务的***程序，例如框架层、核心库层、驱动层等，用于实现各种基础业务以及处理基于硬件的任务；
第二网络通信模块252，用于经由一个或多个(有线或无线)第二网络接口220到达其他计算设备，示例性的第二网络接口220包括：蓝牙、无线相容性认证、和通用串行总线等；
第二显示模块253，用于经由一个或多个与第二用户接口230相关联的第二输出装置231(例如，显示屏、扬声器等)使得能够呈现信息(例如，用于操作***设备和显示内容和信息的用户接口)；
第二输入处理模块254，用于对一个或多个来自一个或多个第二输入装置232之一的一个或多个用户输入或互动进行检测以及翻译所检测的输入或互动。
在一些实施例中，本申请实施例提供的用于信息投放的展示装置(以下简称为展示装置)可以采用软件方式实现，图3示出了存储在第二存储器250中的展示装置255，其可以是程序和插件等形式的软件，包括以下软件模块：信息展示子模块2551、设备信息子模块2552、信息查询子模块2553、信息播放子模块2554和展示实现模块2555，将在下文中说明各个模块的功能。
在另一些实施例中，本申请实施例提供的投放装置和展示装置可以采用硬件方式实现，作为示例，本申请实施例提供的投放装置和展示装置可以是采用硬件译码处理器形式的处理器，其被编程以执行本申请实施例提供的信息投放方法，例如，硬件译码处理器形式的处理器可以采用一个或多个应用专用集成电路(ASIC，Application Specific Integrated Circuit)、DSP、可编程逻辑器件(PLD，Programmable Logic Device)、复杂可编程逻辑器件(CPLD，Complex Programmable Logic Device)、现场可编程门阵列 (FPGA，Field-Programmable Gate Array)或其他电子元件。
下面，说明本申请实施例提供的信息投放方法。
参见图4，图4是本申请实施例提供的信息投放方法的一个可选的流程示意图，将结合图4示出的步骤进行说明。
S401、投放设备在投放管理界面上，接收作用在投放控件上的投放操作，通过信息管理子模块响应投放操作，获取目标投放信息。
在本申请实施例中，当投放对象进行信息投放时，在投放设备上运行用于投放信息的应用，也就展示了投放管理界面。此时，由于投放管理界面上设置有投放控件，而投放控件用于接收对应的操作以触发信息的投放；因此，当投放对象在投放管理界面上对投放控件进行操作时，投放设备也就接收到了作用在投放控件上的投放操作。又由于投放设备中包括用于投放信息的功能模块，即信息管理子模块，因此，投放设备利用信息管理子模块对接收到的投放操作进行响应，就能够获得待投放的信息，该待投放的信息即目标投放信息。
需要说明的是，投放对象为通过投放设备向展示设备上投放信息的对象，比如，商户或投放管理员等。投放管理界面是指用于实现信息投放管理的界面，这里的信息投放管理包括信息的增删查改等处理，以增加信息的处理为例描述信息投放管理的处理过程。投放控件是至少一个可触控的控件，比如，当投放对象进行信息投放时，输入投放文案、投放商户、投放设备、投放时长等信息并点确定按钮时，用于输入投放文案、投放商户、投放设备、投放时长等信息的控件和确定按钮就组成了投放控件；对应的投放操作是指用于触发投放控件的操作，比如，输入操作、点击操作、选择操作、手势操作等操作，或是多个操作的组合。投放管理界面以信息管理子模块为支撑实现信息投放管理。而目标投放信息即投放的信息，比如，电子海报、互动海报(可以和用户有互动操作的海报)和小程序等，而该目标投放信息可以包括信息内容、投放类型、投放批次号、投放时间、投放商户号和投放状态等信息中的至少一种。
示例性地，参见图5，图5是本申请实施例提供的一种示例性的投放管理界面示意图；如图5所示，示出的为电子海报类型的投放信息对应的电子海报列表界面51(投放管理界面)，在电子海报列表界面51中显示有“新建电子海报”按钮511(投放控件)，当点击(投放操作)“新建电子海报”按钮511进行新的电子海报(目标投放信息)添加时，则能够实现新的电子海报在展示设备上的投放。另外，电子海报列表界面51上还显示有关于投放批次号和投放商户号查询的控件512(另外，针对控件512中的两个输入框侧边分别对应显示有投放批次号和投放商户号的提示信息，并且，在控件512中的两个输入框中分别显示有请输入投放批次号和请输入投放商户号的提示信息)，以及已投放的信息列表513；其中，针对已投放的信息列表513中的每条信息，还显示有对应的预览(展示的图片)、投放类型(图片等)、投放批次号(“xxxx”)、投放时间(2020-10-2717:05:58)、投放商户号(“xxxxxxxxxxxxxx”)、投放状态(下线)和可进行的操作(查看、修改和投放(投放状态为下线时，操作为投放，投放状态为投放中时，操作为下线)。
参见图6，图6是本申请实施例提供的另一种示例性的投放管理界面示意图；如图6所示，示出的为互动海报类型的投放信息对应的互动海报列表界面61(投放管理界面)，该互动海报列表界面61中显示有“+新建互动海报”按钮611(投放控件)，当点击(投放操作)“+新建互动海报”按钮611进行新的互动海报(目标投放信息)添加时，则能够实现新的互动海报在展示设备上的投放。另外，互动海报列表界面61上还显示有已投放的信息612，其中，已投放的信息612中的每条信息，显示有对应的预览(比如，图片)、投放状态(投放中)、投放时间(2020-10-28 15:49:39)、互动海报的属性(海报名称：图片)和投放批次号(“xxxxx”)。
S402、投放设备依据目标投放信息，获取至少一个管理子模块对应的至少一个管理子信息。
在本申请实施例中，投放设备中还包括至少一个管理子模块，该至少一个管理子模块用于对待投放的信息进行处理以实现投放的信息在投放设备上的投放；从而，投放设备获得了目标投放信息之后，利用至少一个管理子模块分别对目标投放信息进行处理，以完成目标投放信息在投放设备的投放；这里，至少一个管理子模块分别对目标投放信息进行处理以实现在投放设备上的投放时，先针对目标投放信息，获取至少一个管理子模块中每个管理子模块所待处理的信息；当针对所有管理子模块均获得了对应的待处理的信息时，也就获得了与至少一个管理子模块对应的至少一个待处理的信息，该至少一个待处理的信息即至少一个管理子信息；其中，至少一个管理子模块与至少一个管理子信息一一对应。
需要说明的是，信息管理子模块和至少一个管理子模块为基于投放管理领域的子域划分结果得到的各个互相独立的模块，投放管理领域为基于投放流程从投放领域划分出的用于对投放的信息进行管理的领域。
还需要说明的是，至少一个管理子模块包括信息属性子模块、投放关系子模块、信息风险子模块、信息计数子模块和信息存储子模块中的至少一种；相应地，至少一个管理子信息包括目标信息属性、目标投放关系、目标风险信息、目标计数限制信息和目标存储信息中的至少一种。
其中，信息属性子模块是指用于对目标投放信息的属性进行管理的功能模块；在至少一个管理子信息中，所对应的管理子信息为目标信息属性，该目标信息属性是指目标投放信息的信息标识、投放状态、网络地址和投放时间等属性。
投放关系子模块是指用于对目标投放信息的投放关系进行管理的功能模块；在至少一个管理子信息中，所对应的管理子信息为目标投放关系，该目标投放关系是指目标投放信息所关联的投放对象和展示设备，即目标投放信息是由哪个商户投放给哪些展示设备的信息。
信息风险子模块是指用于评估目标投放信息是否满足预设规定条件的功能模块；在至少一个管理子信息中，所对应的管理子信息为目标风险信息，该目标风险信息是指投放目标投放信息的风险信息，比如，符合预设规定条件或不符合预设规定条件等；其中预设规定条件可以为目标投放信息是否为允许投放的内容的判断条件，比如为功能应用、活动的推广等。
信息计数子模块是指用于基于目标投放信息对应的投放对象的投放数量确定投放权限的功能模块，其中，投放权限可以包括允许投放和禁止投放；在至少一个管理子信息中，所对应的管理子信息为目标计数限制信息，目标计数限制信息是指限制投放的最大数量和当前已投放的数量。
信息存储子模块是指用于存储目标投放信息对应的待存储信息的功能模块；在至少一个管理子信息中，所对应的管理子信息为目标存储信息，该目标存储信息是指目标投放信息对应的待存储信息，比如，投放的视频或图片等。
S403、投放设备通过至少一个管理子模块对至少一个管理子信息进行处理。
在本申请实施例中，投放设备中的至少一个管理子模块获得了一一对应的至少一个管理子信息之后，各管理子模块针对对应的管理子信息进行处理，也就完成了目标投放信息在投放设备的投放。从而，投放设备能够获得包括目标投放信息的投放成功的处理结果，此时执行后续的S404。易知，投放设备所获得的处理结果还可以是目标投放信息的投放失败，此时，结束投放流程。
示例性地，信息风险子模块获取目标投放信息对应的目标风险信息，当根据目标风 险信息确定目标投放信息不符合预设规定条件时，结束投放流程；而当根据目标风险信息确定目标投放信息符合预设规定条件时，信息计数子模块获取目标投放信息对应的目标计数限制信息，当依据目标计数限制信息确定目标投放信息受到数量限制时，结束投放流程；而当依据目标计数限制信息确定目标投放信息未受到数量限制时，更新当前已投放的数量，并通过信息属性子模块获取目标投放信息的目标信息属性并进行存储，以及通过投放关系子模块获取目标投放信息对应的目标投放关系并进行存储，以及通过信息存储子模块获取目标投放信息对应的目标存储信息并进行存储；如此，也就完成了目标投放信息在投放设备的投放。
这里，所投放的目标投放信息在投放设备上完成投放之后，展示设备就能够依据投放展示领域对应的各个互相独立的模块调用目标投放信息，以实现目标投放信息在展示设备上的投放。
需要说明的是，投放展示领域也属于投放领域，也就是说投放领域包括相互独立的两部分：投放管理领域和投放展示领域。如图7所示，投放领域71包括投放管理领域711和投放展示领域712；其中，投放管理领域711是指投放对象端对应的业务领域，对投放信息进行管理，包括查看、创建、删除和修改等；而投放展示领域712是指展示设备端对应的业务领域，用于将投放对象通过投放设备投放的目标投放信息展示在IoT设备上。
S404、投放设备基于处理结果在投放管理界面上，展示目标投放信息。
也就是说，在处理结果为目标投放信息投放成功时，即投放设备完成了目标投放信息的投放之后，在投放管理界面上，会展示所投放的目标投放信息，以根据展示的目标投放信息进行投放信息的管理(比如，投放、查看、下线、修改和删除等)；其中，针对展示的目标投放信息，比如，图5中已投放的信息列表513中显示的信息，图6中已投放的信息612中显示的信息。
需要说明的是，投放设备基于展示的目标投放信息进行投放处理时，比如，针对目标投放信息，通过点击投放按钮，将目标投放信息的投放状态更新为投放中时，则会触发(指示)展示设备执行展示该目标投放信息的处理，即展示设备依据投放展示领域对应的各个互相独立的模块展示目标投放信息，以完成目标投放信息在展示设备的投放；其中，投放展示领域为投放领域中用于对投放的信息进行展示的领域。
参见图8a，图8a是本申请实施例提供的信息投放方法的另一个可选的流程示意图；参见图8a，该信息投放方法包括：
S801、展示设备通过信息展示子模块响应信息展示请求，展示信息展示界面，指示设备信息子模块获取展示设备信息。
在本申请实施例中，当投放对象完成了目标投放对象在投放设备的创建，并将投放状态更新为投放中时，如果在展示设备上运行用于展示投放信息的应用，展示设备也就接收到了信息展示请求；由于展示设备中包括用于触发投放信息展示的功能模块，即信息展示子模块，因此，展示设备能够利用信息展示子模块响应该信息展示请求，展示用于展示投放信息的信息展示界面，并指示设备信息子模块对展示设备的设备信息进行获取；这里，所获取到的展示设备的设备信息即展示设备信息，比如，展示设备的设备编号和设备型号等设备标识。
需要说明的是，信息展示子模块用于结合展示设备中的其他功能模块(比如设备信息子模块、信息查询子模块和信息播放子模块)对投放的信息进行展示；设备信息子模块用于获取展示设备的标识信息。
S802、展示设备通过信息查询子模块获取展示设备信息对应的目标投放信息。
在本申请实施例中，设备信息获取子模块获得了展示设备信息之后，信息展示子模 块指示信息查询子模块获取与展示设备信息所关联的投放信息；由于投放对象在投放设备侧已完成了目标投放信息的投放，因此，与展示设备信息所关联的投放信息中包含目标投放信息；从而，展示设备的信息查询子模块能够获取到该目标投放信息。
需要说明的是，信息查询子模块用于查询展示设备对应的投放信息；目标投放信息为投放设备依据投放管理领域对应的各个互相独立的模块所投放的信息，而投放管理领域为投放领域中用于对投放的信息进行管理的领域。
S803、展示设备通过信息播放子模块在信息展示界面上展示目标投放信息，以完成目标投放信息在展示设备的投放。
在本申请实施例中，信息查询子模块获得了目标投放信息之后，信息展示子模块指示信息播放子模块在信息展示界面上展示该目标投放信息；此时，也就完成了目标投放信息在展示设备的投放，如图8b中的目标投放信息81和图8c中的目标投放信息82。
需要说明的是，信息播放子模块用于播放投放的信息；另外，信息展示子模块、设备信息子模块、信息查询子模块和信息播放子模块为基于投放展示领域的子域划分结果得到的各个互相独立的模块，投放展示领域为基于投放流程从投放领域划分出的对投放的信息进行展示的领域。
参见图9，图9是本申请实施例提供的信息投放方法的又一个可选的流程示意图；参见图9，在本申请实施例中，S401之前还包括S901-S905；也就是说，投放设备在投放管理界面上，接收作用在投放控件上的投放操作之前，该信息投放方法还包括S901-S905，下面对各步骤分别进行说明。
S901、投放设备依据投放需求用例，对投放管理领域进行子域划分，得到多个信息管理子域。
在本申请实施例中，在投放设备进行目标投放信息的投放之前，还包括投放设备利用投放需求用例基于领域驱动设计方式获取用于投放信息的应用的过程。首先，由于投放领域包括两个独立的业务领域：投放管理领域和投放展示领域；针对投放管理领域，投放设备依据投放需求用例进行子域划分，所划分出的各个子域即多个信息管理子域。这里，投放需求用例是指投放领域的业务知识。
需要说明的是，多个信息管理子域包括信息存储子域、信息计数子域、信息属性子域、信息风险子域和投放关系子域中的至少一个，以及投放管理子域；其中，投放管理子域是指管理投放的信息的核心域，信息存储子域是指存储投放的信息的支撑域，信息计数子域是指统计投放的信息的数量的支撑域，信息属性子域是指投放的信息的属性对应的支撑域，信息风险子域是指确定投放的信息是否满足预设规定条件的支撑域，投放关系子域是指投放的信息关联的投放对象和展示设备对应的支撑域。
参见图10，图10是本申请实施例提供的一种示例性的投放管理领域的子域划分结果的示意图；如图10所示，投放管理领域101包括6个信息管理子域：投放管理子域1011、信息存储子域1012、信息计数子域1013、信息属性子域1014、信息风险子域1015和投放关系子域1016；并且，投放管理子域1011为核心域，信息存储子域1012、信息计数子域1013、信息属性子域1014、信息风险子域1015和投放关系子域1016均为投放管理子域1011的支撑域。
S902、投放设备依据投放需求用例，确定多个信息管理子域的业务范围，将多个信息管理子域的业务范围确定为多个管理上下文。
在本申请实施例中，投放设备获得了多个信息管理子域之后，依据投放需求用例确定多个信息管理子域中每个信息管理子域对应的业务范围，也就获得了每个信息管理子域对应的限界上下文，这里称为管理上下文；从而，也就获得了多个信息管理子域对应的多个管理上下文。
需要说明的是，多个管理上下文包括信息存储上下文、信息计数上下文、信息属性上下文、信息风险上下文和投放关系上下文中的至少一个，以及信息管理上下文；并且，多个管理上下文和多个信息管理子域一一对应，即信息管理上下文为投放管理子域的限界上下文，信息存储上下文为信息存储子域的限界上下文，信息计数上下文为信息计数子域的限界上下文，信息属性上下文为信息属性子域的限界上下文，信息风险上下文为信息风险子域的限界上下文，投放关系上下文为投放关系子域的限界上下文。这里，由于投放管理子域为核心域，信息存储子域、信息计数子域、信息属性子域、信息风险子域和投放关系子域均为支撑域，因此，信息存储子域、信息计数子域、信息属性子域、信息风险子域和投放关系子域，分别对应的信息管理上下文、信息存储上下文、信息计数上下文、信息属性上下文、信息风险上下文和投放关系上下文，均与投放管理子域的信息管理上下文存在依赖关系。
示例性地，参见图11，基于图10，图11是本申请实施例提供的一种示例性的多个管理上下文的示意图；如图11所示，投放管理领域101包括6个信息管理子域：投放管理子域1011、信息存储子域1012、信息计数子域1013、信息属性子域1014、信息风险子域1015和投放关系子域1016；依次分别对应6个管理上下文：信息管理上下文111、信息存储上下文112、信息计数上下文113、信息属性上下文114、信息风险上下文115和投放关系上下文116。其中，信息存储上下文112、信息计数上下文113、信息属性上下文114、信息风险上下文115和投放关系上下文116均与信息管理上下文111具有依赖关系，以及信息计数上下文113和投放关系上下文116之间也具有依赖关系。
S903、投放设备依据投放需求用例，分析多个管理上下文中各管理上下文分别对应的模型元素，从而得到与多个管理上下文对应的多个管理模型。
在本申请实施例中，投放设备获得了多个管理上下文之后，由于投放需求用例中记载了信息投放的各个应用场景，而多个管理上下文表征了每个信息管理子域的业务范围，从而，依据每个管理上下文，能够从投放需求用例中获取到对应的模型元素，并将获取到的模型元素组合为每个管理上下文对应的管理模型，从而当完成了多个管理上下文的模型元素的获取时，也就得到了与多个管理上下文一一对应的多个管理模型。
S904、投放设备基于多个管理模型进行编码，得到包括信息管理子模块和至少一个管理子模块的投放管理应用。
需要说明的是，每个管理模型为每个信息管理子域对应的功能模块的获取信息，通过该管理模型进行计算机语言的编码，就能够得到每个信息管理子域对应的功能模块，而将所获得的所有信息管理子域对应的所有功能模块(信息管理子模块和所述至少一个管理子模块)组合，也就得到了投放设备侧用于投放信息的应用，这里，称为投放管理应用；并且，该投放管理应用中包括上述的信息管理子模块和至少一个管理子模块，易知，信息管理子模块与投放管理子域对应，至少一个管理子模块与至少一个子域(由信息存储子域、信息计数子域、信息属性子域、信息风险子域和投放关系子域中的至少一个组成的)对应；以及，多个管理子模块与多个管理模型一一对应，多个管理子模块包括信息管理子模块和所述至少一个管理子模块。
S905、投放设备运行投放管理应用，展示投放管理界面。
在本申请实施例中，投放设备获得了投放管理应用之后，运行该投放管理应用，也就展示出了投放管理界面，以根据展示的投放管理界面实现信息在投放设备侧的投放。
在本申请实施例中，S904可通过S9041-S9043实现；也就是说，投放设备依据投放需求用例，分析多个管理上下文中各管理上下文分别对应的模型元素，从而得到与多个管理上下文对应的多个管理模型，包括：
S9041、投放设备依据投放需求用例，分析当前管理上下文对应的模型元素，从而 得到当前管理聚合根、当前管理实体和当前管理值对象。
在本申请实施例中，每个管理上下文对应的模型元素包括聚合根、实体和值对象；这里，投放设备将多个管理上下文中的任一管理上下文作为当前管理上下文进行对应模型元素的获取，所获取到的当前管理上下文对应的聚合根、实体和值对象，依次为当前管理聚合根、当前管理实体和当前管理值对象。易知，当前管理上下文为多个管理上下文中的任一管理上下文。
S9042、投放设备将当前管理聚合根、当前管理实体和当前管理值对象，组合为当前管理上下文对应的当前管理模型。
需要说明的是，投放设备获得了当前管理上下文对应的当前管理聚合根、当前管理实体和当前管理值对象之后，将当前管理聚合根、当前管理实体和当前管理值对象组合，所获得的组合结果即当前管理上下文对应的当前管理模型。
S9043、当投放设备完成对多个管理上下文中各管理上下文的处理时，得到与多个管理上下文对应的多个管理模型。
需要说明的是，当投放设备依据当前管理上下文获取当前管理模型的过程，完成了多个管理上下文中各管理上下文对应的管理模型的获取时，也就获得了与多个管理上下文一一对应的多个管理模型；易知，多个管理模型包括当前管理模型。
在本申请实施例中，当前管理上下文为信息管理上下文时，当前管理实体包括投放记录实体，当前管理值对象包括信息属性值对象、投放关系值对象、信息存储值对象、信息计数值对象和信息风险值对象中的至少一种。
示例性地，参见图12，图12是本申请实施例提供的一种示例性的信息管理上下文对应的管理模型示意图；如图12所示，信息管理上下文121对应的管理模型包括聚合根1221、投放记录实体1222、信息属性值对象1223和投放关系值对象1224。并且，投放记录实体1222中包括投放信息标识和投放状态等信息，信息属性值对象1223中包括投放信息地址、投放信息文案和投放信息类型等信息，投放关系值对象1224中包括展示设备信息和投放对象等。
在本申请实施例中，当前管理上下文包括当前管理适配层，该当前管理适配层即当前管理上下文对应的适配层，用于实现外部上下文与当前管理上下文之间的转义，为当前管理上下文提供了访问外部上下文的统一接口。此时，S9041可通过S90411-S90413实现，也就是说，投放设备依据投放需求用例，分析当前管理上下文对应的模型元素，从而得到当前管理聚合根、当前管理实体和当前管理值对象，包括S90411-S90413，下面对各步骤分别进行说明。
S90411、投放设备依据投放需求用例，从当前管理上下文中获取自身模型元素。
在本申请实施例中，投放设备在依据投放需求用例获取当前管理上下文对应的模型元素时，该模型元素可能是，此时，如果投放设备依据投放需求用例，从当前管理上下文中获取来自于当前管理上下文的模型元素，也就获取到了自身模型元素。
S90412、投放设备依据投放需求用例和当前管理适配层，从外部上下文中获取外部模型元素。
在本申请实施例中，投放设备在依据投放需求用例获取当前管理上下文对应的模型元素时，该模型元素可能是来自于外部上下文，此时，投放设备通过访问外部上下文，获取对应的信息，并通过当前管理适配层对获取到的对应的信息进行转义，也就获得了外部模型元素。
这里，转义指转换为当前管理上下文所需的语义信息的过程；比如，当一领域的上下文通过商户信息适配层，向外部上下文查询商户的信息时，商户信息适配层将外部上下文的信息，翻译成本领域的上下文中的特性信息，例如，从外部上下文查询到的商户 的信息包括A、B、C……G等多种类型，而本领域内的上下文只需要知道A、B和其他这3种类型，商户信息适配层则将从外部上下文查询到的商户的信息，映射成本领域内的语义，如此，保证了内部的统一和简洁。
需要说明的是，预设外部上下文为与当前管理上下文属于不同领域(投放领域之外的领域)的限界上下文；自身模型元素和外部模型元素为当前管理上下文对应的模型元素。
S90413、投放设备从自身模型元素和外部模型元素中，获取当前管理聚合根、当前管理实体和当前管理值对象。
在本申请实施例中，模型元素包括自身模型元素和外部模型元素。
需要说明的是，投放设备获得了自身模型原始和外部模型元素中，从自身模型元素和外部模型元素中提取实体和值对象，也就得到了当前管理聚合根、当前管理实体和当前管理值对象。
在本申请实施例中，S904还可通过S9044-S9046实现；也就是说，投放设备基于多个管理模型进行编码，得到包括信息管理子模块和至少一个管理子模块的投放管理应用，包括S9044-S9046，下面对各步骤分别进行说明。
S9044、投放设备依据多个管理模型，生成每个管理模型对应的创建逻辑。
需要说明的是，由于模型元素在信息投放的应用场景中，是通过对模型元素进行创建来实现的信息的投放；因此，投放设备根据管理模型进行编码时，针对每个管理模型，生成关于模型元素的创建逻辑，以通过创建逻辑实现信息的投放。
S9045、投放设备利用预设设计模式，封装创建逻辑，从而得到与多个管理模型对应的多个优化创建逻辑。
在本申请实施例中，投放设备中设置有预设设计模式，或者能够获取到该预设设计模式，以利用该预设设计模式对每个管理模型的创建逻辑进行封装，封装后的创建逻辑即每个管理模型对应的优化创建逻辑；从而，针对多个管理模型，对应存在多个优化创建逻辑；其中，多个管理模型与多个优化创建逻辑一一对应。
这里，预设设计模式是一种设计模式，比如，工厂设计模式、适配器模式和原型模式等。
S9046、投放设备基于多个优化创建逻辑进行编码，得到包括信息管理子模块和至少一个管理子模块的投放管理应用。
在本申请实施例中，投放设备获得了多个优化创建逻辑之后，针对不同的类型实现多个优化创建逻辑的编码，也就得到了包括信息管理子模块和至少一个管理子模块的投放管理应用。
示例性地，参见图13，图13是本申请实施例提供的一种示例性的封装创建逻辑的示意图；如图13所示，内容类131为图12示出的管理模型对应的信息，内容类131中1311(“+***投放记录():int”、“+更新投放记录():int”、“+获取投放记录():int”、“+***素材内容():int”、“+更新素材内容():int”、“+获取素材内容():int”、“+***投放关系():int”、“+更新投放关系():int”和“+获取投放关系():int”)为基于图12获得的创建逻辑，内容类131中1312(“+创建投放():int”、“+更新投放():int”和“+投放详情():int”)为创建逻辑1311的封装后的创建逻辑(优化创建逻辑)；当预设设计模式为工厂模式时，由于创建不同内容的逻辑可能不一致，所需的内容属性不同，因此，基于工厂类132(“+CreateContent():内容”)对封装后的创建逻辑1312进行分类创建；这里，分为三类：电子海报工厂类1331(“+CreateContent():内容”)、互动海报工厂类1332(“+CreateContent():内容”)和小程序配置工厂类1333(“+CreateContent():内容”)，分别对应的内容类为电子海报内容类1341(“+创建投放():int”、“+更新投放():int”和“+投放详情():int”)、 互动海报内容类1342(“+创建投放():int”、“+更新投放():int”和“+投放详情():int”)和小程序配置内容类1343(“+创建投放():int”、“+更新投放():int”和“+投放详情():int”)。将不同的创建逻辑、所需的参数封装起来，可以让整体的复杂度得到简化，从而，电子海报内容类1341、互动海报内容类1342和小程序配置内容类1343通过封装后的创建逻辑1312实现不同种类内容的创建。
可以理解的是，不同投放信息的创建逻辑可能不同，所需的属性也可能不同，通过预设设计模式将将不同的创建逻辑、所需的参数封装起来，可以让整体的复杂度得到简化。
在本申请实施例中，参见图14，图14是本申请实施例提供的信息投放方法的再一个可选的流程示意图；参见图14，在本申请实施例中，S801之前还包括S1401-S1405，下面对各步骤分别进行说明。
S1401、展示设备依据投放需求用例，对投放展示领域进行子域划分，得到多个信息展示子域。
在本申请实施例中，在展示设备进行目标投放信息的展示之前，还包括展示设备利用投放需求用例基于领域驱动设计方式获取用于展示投放信息的应用的过程。首先，针对投放领域中的投放展示领域，展示设备依据投放需求用例进行子域划分，所划分出的各个子域即多个信息展示子域。
需要说明的是，多个信息展示子域包括投放展示子域、信息查询子域、设备信息子域和信息播放子域；其中，投放展示子域是指展示投放的信息的核心域，信息查询子域是指查询投放的信息的支撑域，设备信息子域是指查询展示设备的信息的支撑域，信息播放子域是指播放投放的信息的支撑域。
参见图15，图15是本申请实施例提供的一种示例性的投放展示领域的子域划分结果的示意图；如图15所示，投放展示领域151包括4个信息展示子域：投放展示子域1511、信息查询子域1512、设备信息子域1513和信息播放子域1514；并且，投放展示子域1511为核心域，信息查询子域1512、设备信息子域1513和信息播放子域1514均为投放展示子域1511的支撑域。
S1402、展示设备依据投放需求用例，确定多个信息展示子域的业务范围，将多个信息展示子域的业务范围确定为多个展示上下文。
在本申请实施例中，展示设备获得了多个信息展示子域之后，依据投放需求用例确定多个信息展示子域中每个信息展示子域对应的业务范围，也就获得了每个信息展示子域对应的限界上下文，这里称为展示上下文；从而，也就获得了多个信息展示子域对应的多个展示上下文。
需要说明的是，多个展示上下文包括信息展示上下文、信息查询上下文、设备信息上下文和信息播放上下文；并且，多个展示上下文和多个信息展示子域一一对应，即信息展示上下文为投放展示子域的限界上下文，信息查询上下文为信息查询子域的限界上下文，设备信息上下文为设备信息子域的限界上下文，信息播放上下文为信息播放子域的限界上下文。这里，由于投放展示子域为核心域，信息查询子域、设备信息子域和信息播放子域均为支撑域，因此，信息查询子域、设备信息子域和信息播放子域，分别对应的信息查询上下文、设备信息上下文和信息播放上下文，均与投放展示子域的信息展示上下文具有依赖关系。
示例性地，参见图16，基于图15，图16是本申请实施例提供的一种示例性的多个展示上下文的示意图；如图16所示，投放展示领域151包括4个信息展示子域：投放展示子域1511、信息查询子域1512、设备信息子域1513和信息播放子域1514；分别对应4个展示上下文：信息展示上下文161、信息查询上下文162、设备信息上下文163 和信息播放上下文164。其中，信息查询上下文162、设备信息上下文163和信息播放上下文164均与信息展示上下文161具有依赖关系。
S1403、展示设备依据投放需求用例，分析多个展示上下文中各展示上下文分别对应的模型元素，从而得到与多个展示上下文对应的多个展示模型。
在本申请实施例中，展示设备获得了多个展示上下文之后，由于投放需求用例中记载了信息投放的各个应用场景，而多个展示上下文表征了每个信息展示子域的业务范围，从而，依据每个展示上下文，能够从投放需求用例中获取到对应的模型元素，并将获取到的模型元素组合为每个展示上下文对应的展示模型，从而当完成了多个展示上下文的模型元素的获取时，也就得到了与多个管理上下文一一对应的多个展示模型。
S1404、展示设备基于多个展示模型进行编码，得到包括信息展示子模块、设备信息子模块、信息查询子模块和信息播放子模块的投放展示应用。
需要说明的是，每个展示模型为每个信息展示子域对应的功能模块的获取信息，通过该展示模型进行计算机语言的编码，就能够得到每个信息展示子域对应的功能模块，而将所获得的所有信息展示子域对应的所有功能模块组合，也就得到了展示设备侧用于展示投放信息的应用，这里，称为投放展示应用；并且，该投放展示应用中包括上述的信息展示子模块、设备信息子模块、信息查询子模块和信息播放子模块，易知，信息展示子模块与投放展示子域对应，设备信息子模块与设备信息子域对应，信息查询子模块与设备信息子域对应，信息播放子模块与信息播放子域对应。
S1405、展示设备运行投放展示应用，生成信息展示请求。
在本申请实施例中，展示设备获得了投放展示应用之后，运行该投放展示应用，也就生成了信息展示请求，以根据生成的信息展示请求实现投放的信息在展示设备侧的展示。
需要说明的是，S1403中展示设备依据投放需求用例，分析多个展示上下文中各上下文分别对应的模型元素，从而得到与多个展示上下文对应的多个展示模型，同样是通过获得聚合根、实体和值对象实现展示模型的获取的；也就是说，投放设备依据投放需求用例，分析当前展示上下文对应的模型元素，从而得到当前展示聚合根、当前展示实体和当前展示值对象，当前展示上下文为多个展示上下文中的任一展示上下文；将当前展示聚合根、当前展示实体和当前展示值对象，组合为当前展示上下文对应的当前展示模型；当完成对多个展示上下文中各展示上下文的处理时，得到与多个展示上下文对应的多个展示模型，多个展示模型包括当前展示模型。
另外，S1404中展示设备基于多个展示模型进行编码，得到包括信息展示子模块、设备信息子模块、信息查询子模块和信息播放子模块的投放展示应用时，同样也是通过适配层以及预设设计模式实现的，本申请实施例在此不再赘述。
在本申请实施例中，投放展示应用和投放管理应用所对应的信息投放***，除了利用上述的DDD实现之后，还可以采用瀑布流模式实现。
下面，将说明本申请实施例在一个实际的应用场景中的示例性应用；参见图17，当采用DDD实现信息投放时，按照DDD实现本申请实施例的信息投放***时，包括如下步骤：
S1701、根据整体的需求(投放需求用例)将投放领域划分为不同领域，并确定不同领域对应的限界上下文。
需要说明的是，所划分的不同领域为包括内容管理子域(投放管理子域)、内容存储子域(信息存储子域)、内容计数子域(信息计数子域)、内容属性子域(信息属性子域)、内容风险子域(信息风险子域)和投放关系子域的内容管理领域(投放管理领域)，以及包括设备内容展示子域(投放展示子域)、内容查询子域(信息查询子域)、设备信 息子域和内容播放子域(信息播放子域)的设备内容展示领域(投放展示领域)。并且，内容管理领域和设备内容展示领域为投放领域中两个互相独立的领域；其中，内容管理领域：商户对内容进行管理的领域，包括查看、创建、删除等；设备内容展示领域：商户的内容在IoT设备上进行展示的领域。
另外，对于内容管理领域，内容管理子域作为整个领域的核心，由5个子域支撑：
内容属性子域：唯一标识和状态等相关属性的领域；
投放关系子域：内容投放的相关信息的领域，如投放给了哪些设备、哪些商户等；
内容风险子域：内容是商户创作的，可能存在一些不合规的情况，需要进行管理的领域；
内容计数子域：需要对商户投放数量进行限制的领域；
内容存储子域：储存投放内容的领域，如投放的图片、视频等。
而对于设备内容展示领域，设备内容展示子域作为整个领域的核心，有3个子域支撑：
设备信息子域：查询当前设备的信息的领域；
内容查询子域：查询当前设备有哪些内容投放的领域；
内容播放子域：将投放的内容播放出来的领域。
接下来，通过不同领域对应的业务范围，也就确定了不同领域对应的限界上下文。
S1702、分析不同领域对应的限界上下文的实体、值对象和聚合根，得到各限界上下文对应的细化模型。
需要说明的是，依据整体的需要，对每个限界上下文分析出对应的实体、值对象和聚合根(模型元素)，并将分析出的实体、值对象和聚合根组合，也就得到了各限界上下文对应的细化模型(多个管理模型和多个展示模型)。
S1703、根据细化模型获取对应的创建逻辑，并利用工厂模式对创建逻辑进行封装，以根据封装后的创建逻辑进行代码实现，得到信息投放***(投放管理应用和投放展示应用)。
下面，继续说明基于信息投放***进行信息投放的示例性应用；参见图18，图18是本申请实施例提供的一种示例性的信息投放架构图；如图18所示，商户18-1(投放对象)通过信息投放***18-2中的投放设备18-21上展示的管理界面18-211(投放管理界面)创建投放内容18-3(目标投放信息)，以建立投放内容与IoT设备18-22(展示设备)的关联；这里，投放内容18-3的创建过程与图5中描述的新建电子海报的过程类似，本申请实施例在此不再赘述。当通过管理界面18-211将投放内容18-3的投放状态设置为投放中时，则在IoT设备18-22上展示投放内容18-3；此时，商户18-1也就完成了投放内容18-3在IoT设备18-22上的投放。
基于图18，参见图19，图19是本申请实施例提供的一种示例性的信息投放交互图；如图19所示，该示例性的信息投放过程包括：
S1901、投放设备响应于作用在新建按钮(投放控件)上的创建操作(投放操作)，基于内容管理领域中封装后的创建逻辑(信息管理子模块)获取投放内容(目标投放信息)。
S1902、投放设备基于内容管理领域中封装后的创建逻辑(至少一个管理子模块)对投放内容进行处理。
S1903、投放设备在完成对投放内容的处理时，在数据库中存储投放内容与展示设备的关联数据。
S1904、投放设备基于关联数据在管理界面展示投放内容。
S1905、投放设备响应于投放内容的投放状态的设置操作，将数据库中投放内容的 投放状态更新为投放中。
S1906、IoT设备基于设备内容展示领域中封装后的创建逻辑(信息展示子模块、设备信息子模块和信息查询子模块)，从数据库中获取投放状态为投放中的投放内容。
S1907、IoT设备基于设备内容展示领域中封装后的创建逻辑(信息播放子模块)展示投放内容。
可以理解的是，通过领域驱动设计方法实现信息投放***时，信息投放***的耦合程度降低；信息投放中各个功能模块之间相互独立，职责清晰，可维护性高；业务逻辑变动时，对信息投放***的整体改动量少。
下面继续说明本申请实施例提供的投放装置455的实施为软件模块的示例性结构，在一些实施例中，如图2所示，存储在第一存储器450的投放装置455中的软件模块可以包括：
信息管理子模块4551，配置为在投放管理界面上，接收作用在投放控件上的投放操作，响应所述投放操作，获取目标投放信息；
子信息获取模块4552，配置为依据所述目标投放信息，获取至少一个管理子模块对应的至少一个管理子信息；其中，所述信息管理子模块和所述至少一个管理子模块为基于投放管理领域的子域划分结果得到的各个互相独立的模块，所述投放管理领域为投放领域中用于对投放的信息进行管理的领域；
处理模块4553，配置为通过所述至少一个管理子模块对所述至少一个管理子信息进行处理；
信息展示模块4554，配置为依据处理结果在所述投放管理界面上，展示所述目标投放信息，基于展示的目标投放信息指示展示设备依据投放展示领域对应的独立的模块展示所述目标投放信息，以完成所述目标投放信息在所述展示设备的投放，所述投放展示领域为所述投放领域中用于对投放的信息进行展示的领域。
在本申请实施例中，所述至少一个管理子模块包括信息属性子模块、投放关系子模块、信息风险子模块、信息计数子模块和信息存储子模块中的至少一种；所述至少一个管理子信息包括目标信息属性、目标投放关系、目标风险信息、目标计数限制信息和目标存储信息中的至少一种。
在本申请实施例中，所述投放装置455还包括管理实现模块4555，配置为依据投放需求用例，对所述投放管理领域进行子域划分，得到多个信息管理子域，所述投放需求用例包括所述投放领域的业务知识；依据所述投放需求用例，确定所述多个信息管理子域的业务范围，将所述多个信息管理子域的业务范围确定为多个管理上下文；依据所述投放需求用例，分析所述多个管理上下文中各管理上下文分别对应的模型元素，从而得到与所述多个管理上下文对应的多个管理模型；基于所述多个管理模型进行编码，得到包括所述信息管理子模块和所述至少一个管理子模块的投放管理应用，多个管理子模块与所述多个管理模型对应，所述多个管理子模块包括所述信息管理子模块和所述至少一个管理子模块；运行所述投放管理应用，展示所述投放管理界面。
在本申请实施例中，所述管理实现模块4555，还配置为依据所述投放需求用例，分析当前管理上下文对应的模型元素，从而得到当前管理聚合根、当前管理实体和当前管理值对象，所述当前管理上下文为所述多个管理上下文中的任一管理上下文；将所述当前管理聚合根、所述当前管理实体和所述当前管理值对象，组合为所述当前管理上下文对应的当前管理模型；当完成对所述多个管理上下文中各管理上下文的处理时，得到与所述多个管理上下文对应的所述多个管理模型，所述多个管理模型包括所述当前管理模型。
在本申请实施例中，所述多个信息管理子域包括信息存储子域、信息计数子域、信 息属性子域、信息风险子域和投放关系子域中的至少一个，以及投放管理子域；其中，所述投放管理子域是指管理投放的信息的核心域，所述信息存储子域是指存储投放的信息的支撑域，所述信息计数子域是指统计投放的信息的数量的支撑域，所述信息属性子域是指投放的信息的属性对应的支撑域，所述信息风险子域是指确定投放的信息是否满足预设规定条件的支撑域，所述投放关系子域是指投放的信息关联的投放对象和展示设备对应的支撑域；所述多个管理上下文包括信息存储上下文、信息计数上下文、信息属性上下文、信息风险上下文和投放关系上下文中的至少一个，以及信息管理上下文。
在本申请实施例中，所述当前管理上下文为所述信息管理上下文时，所述当前管理实体包括投放记录实体，所述当前管理值对象包括信息属性值对象、投放关系值对象、信息存储值对象、信息计数值对象和信息风险值对象中的至少一种。
在本申请实施例中，所述当前管理上下文包括当前管理适配层；所述管理实现模块4555，还配置为依据所述投放需求用例，从所述当前管理上下文中获取自身模型元素；依据所述投放需求用例和所述当前管理适配层，从外部上下文中获取外部模型元素，所述自身模型元素和所述外部模型元素为所述当前管理上下文对应的模型元素；从所述自身模型元素和所述外部模型元素中，获取所述当前管理聚合根、所述当前管理实体和所述当前管理值对象。
在本申请实施例中，所述管理实现模块4555，还配置为依据所述多个管理模型，生成每个管理模型对应的创建逻辑；利用预设设计模式，封装所述创建逻辑，从而得到与所述多个管理模型对应的多个优化创建逻辑；基于所述多个优化创建逻辑进行编码，得到包括所述信息管理子模块和所述至少一个管理子模块的所述投放管理应用。
下面继续说明本申请实施例提供的展示装置255的实施为软件模块的示例性结构，在一些实施例中，如图3所示，存储在第二存储器250的展示装置255中的软件模块可以包括：
信息展示子模块2551，配置为响应信息展示请求，展示信息展示界面，指示设备信息子模块2552获取展示设备信息；
信息查询子模块2553，配置为获取所述展示设备信息对应的目标投放信息，所述目标投放信息为投放设备依据投放管理领域对应的各个互相独立的模块所投放的信息，所述投放管理领域为投放领域中用于对投放的信息进行管理的领域；
信息播放子模块2554，配置为在所述信息展示界面上展示所述目标投放信息，从而完成所述目标投放信息在所述展示设备的投放；其中，所述信息展示子模块2551、所述设备信息子模块2552、所述信息查询子模块2553和所述信息播放子模块2554为基于投放展示领域的子域划分结果得到的各个互相独立的模块，所述投放展示领域为所述投放领域中用于对投放的信息进行展示的领域。
在本申请实施例中，所述展示装置255还包括展示实现模块2555，配置为依据投放需求用例，对所述投放展示领域进行子域划分，得到多个信息展示子域，所述投放需求用例包括所述投放领域的业务知识；依据所述投放需求用例，确定所述多个信息展示子域的业务范围，将所述多个信息展示子域的业务范围确定为多个展示上下文；依据所述投放需求用例，分析所述多个展示上下文中各展示上下文分别对应的模型元素，从而得到与所述多个展示上下文对应的多个展示模型；基于所述多个展示模型进行编码，得到包括所述信息展示子模块、所述设备信息子模块、所述信息查询子模块和所述信息播放子模块的投放展示应用；运行所述投放展示应用，生成所述信息展示请求。
在本申请实施例中，所述多个信息展示子域包括投放展示子域、信息查询子域、设备信息子域和信息播放子域；所述投放展示子域是指展示投放的信息的核心域，所述信息查询子域是指查询投放的信息的支撑域，所述设备信息子域是指查询被投放设备的信 息的支撑域，所述信息播放子域是指播放投放的信息的支撑域；所述多个展示上下文包括信息展示上下文、信息查询上下文、设备信息上下文和信息播放上下文。
在本申请实施例中，所述展示实现模块2555，还配置为依据所述投放需求用例，分析当前展示上下文对应的模型元素，从而得到当前展示聚合根、当前展示实体和当前展示值对象，所述当前展示上下文为所述多个展示上下文中的任一展示上下文；将所述当前展示聚合根、所述当前展示实体和所述当前展示值对象，组合为所述当前展示上下文对应的当前展示模型；当完成对所述多个展示上下文中各展示上下文的处理时，得到与所述多个展示上下文对应的所述多个展示模型，所述多个展示模型包括所述当前展示模型。
本申请实施例提供一种存储有可执行指令的计算机可读存储介质，其中存储有可执行指令，当可执行指令被第一处理器执行时，将引起第一处理器执行本申请实施例提供的应用于投放设备的信息投放方法，例如，如图4示出的信息投放方法；当可执行指令被第二处理器执行时，将引起第二处理器执行本申请实施例提供的应用于展示设备的信息投放方法，例如，如图8a示出的信息投放方法。
在一些实施例中，计算机可读存储介质可以是FRAM、ROM、PROM、EPROM、EEPROM、闪存、磁表面存储器、光盘、或CD-ROM等存储器；也可以是包括上述存储器之一或任意组合的各种设备。
在一些实施例中，可执行指令可以采用程序、软件、软件模块、脚本或代码的形式，按任意形式的编程语言(包括编译或解释语言，或者声明性或过程性语言)来编写，并且其可按任意形式部署，包括被部署为独立的程序或者被部署为模块、组件、子例程或者适合在计算环境中使用的其它单元。
作为示例，可执行指令可以但不一定对应于文件***中的文件，可以可被存储在保存其它程序或数据的文件的一部分，例如，存储在超文本标记语言(HTML，Hyper Text Markup Language)文档中的一个或多个脚本中，存储在专用于所讨论的程序的单个文件中，或者，存储在多个协同文件(例如，存储一个或多个模块、子程序或代码部分的文件)中。
作为示例，可执行指令可被部署为在一个计算设备上执行，或者在位于一个地点的多个计算设备上执行，又或者，在分布在多个地点且通过通信网络互连的多个计算设备上执行。
综上所述，通过本申请实施例，在进行目标投放信息的投放时，投放设备依据投放管理领域的各个互相独立的模块对目标投放信息进行处理，以完成目标投放信息在投放设备的投放，进而使展示设备依据投放展示领域对应的各个互相独立的模块展示目标投放信息；而由于投放管理领域的各个互相独立的模块是基于投放管理领域的子域划分结果得到的，投放展示领域对应的各个互相独立的模块是基于投放展示领域的子域划分结果得到的，因此，用于展示目标投放信息的各功能模块的耦合度低，从而能够简化信息投放的流程，提升信息投放的效率，降低信息投放的复杂度。
以上所述，仅为本申请的实施例而已，并非用于限定本申请的保护范围。凡在本申请的精神和范围之内所作的任何修改、等同替换和改进等，均包含在本申请的保护范围之内。

Claims (17)

  1. 一种信息投放方法，所述方法由投放设备执行，包括：
    在投放管理界面上，接收作用在投放控件上的投放操作，通过信息管理子模块响应所述投放操作，获取目标投放信息；
    依据所述目标投放信息，获取至少一个管理子模块对应的至少一个管理子信息，其中，所述信息管理子模块和所述至少一个管理子模块为基于投放管理领域的子域划分结果得到的各个互相独立的模块，所述投放管理领域为投放领域中用于对投放的信息进行管理的领域；
    通过所述至少一个管理子模块对所述至少一个管理子信息进行处理；
    依据处理结果在所述投放管理界面上，展示所述目标投放信息，基于展示的目标投放信息指示展示设备依据投放展示领域对应的各个互相独立的模块展示所述目标投放信息，所述投放展示领域为所述投放领域中用于对投放的信息进行展示的领域。
  2. 根据权利要求1所述的方法，其中，
    所述至少一个管理子模块包括信息属性子模块、投放关系子模块、信息风险子模块、信息计数子模块和信息存储子模块中的至少一种；
    所述至少一个管理子信息包括目标信息属性、目标投放关系、目标风险信息、目标计数限制信息和目标存储信息中的至少一种。
  3. 根据权利要求1或2所述的方法，其中，所述在投放管理界面上，接收作用在投放控件上的投放操作之前，所述方法还包括：
    依据投放需求用例，对所述投放管理领域进行子域划分，得到多个信息管理子域，所述投放需求用例包括所述投放领域的业务知识；
    依据所述投放需求用例，确定所述多个信息管理子域的业务范围，并将所述多个信息管理子域的业务范围确定为多个管理上下文；
    依据所述投放需求用例，分析所述多个管理上下文中各管理上下文分别对应的模型元素，得到与所述多个管理上下文对应的多个管理模型；
    基于所述多个管理模型进行编码，得到包括所述信息管理子模块和所述至少一个管理子模块的投放管理应用，多个管理子模块与所述多个管理模型对应，所述多个管理子模块包括所述信息管理子模块和所述至少一个管理子模块；
    运行所述投放管理应用，展示所述投放管理界面。
  4. 根据权利要求3所述的方法，其中，所述依据所述投放需求用例，分析所述多个管理上下文中各管理上下文分别对应的模型元素，得到与所述多个管理上下文对应的多个管理模型，包括：
    依据所述投放需求用例，分析当前管理上下文对应的模型元素，得到当前管理聚合根、当前管理实体和当前管理值对象，所述当前管理上下文为所述多个管理上下文中的任一管理上下文；
    将所述当前管理聚合根、所述当前管理实体和所述当前管理值对象，组合为所述当前管理上下文对应的当前管理模型；
    当完成对所述多个管理上下文中各管理上下文的处理时，得到与所述多个管理上下文对应的所述多个管理模型，所述多个管理模型包括所述当前管理模型。
  5. 根据权利要求4所述的方法，其中，所述多个信息管理子域包括信息存储子域、信息计数子域、信息属性子域、信息风险子域和投放关系子域中的至少一个，以及投放管理子域；
    其中，所述投放管理子域是指管理投放的信息的核心域，所述信息存储子域是指存 储投放的信息的支撑域，所述信息计数子域是指统计投放的信息的数量的支撑域，所述信息属性子域是指投放的信息的属性对应的支撑域，所述信息风险子域是指确定投放的信息是否满足预设规定条件的支撑域，所述投放关系子域是指投放的信息关联的投放对象和展示设备对应的支撑域；
    所述多个管理上下文包括信息存储上下文、信息计数上下文、信息属性上下文、信息风险上下文和投放关系上下文中的至少一个，以及信息管理上下文。
  6. 根据权利要求5所述的方法，其中，所述当前管理上下文为所述信息管理上下文时，所述当前管理实体包括投放记录实体，所述当前管理值对象包括信息属性值对象、投放关系值对象、信息存储值对象、信息计数值对象和信息风险值对象中的至少一种。
  7. 根据权利要求4所述的方法，其中，所述当前管理上下文包括当前管理适配层；
    所述依据所述投放需求用例，分析当前管理上下文对应的模型元素，得到当前管理聚合根、当前管理实体和当前管理值对象，包括：
    依据所述投放需求用例，从所述当前管理上下文中获取自身模型元素；
    依据所述投放需求用例和所述当前管理适配层，从预设外部上下文中获取外部模型元素，所述自身模型元素和所述外部模型元素为所述当前管理上下文对应的模型元素；
    从所述自身模型元素和所述外部模型元素中，获取所述当前管理聚合根、所述当前管理实体和所述当前管理值对象。
  8. 根据权利要求3所述的方法，其中，所述基于所述多个管理模型进行编码，得到包括所述信息管理子模块和所述至少一个管理子模块的投放管理应用，包括：
    依据所述多个管理模型，生成每个管理模型对应的创建逻辑；
    利用预设设计模式，封装所述创建逻辑，得到与所述多个管理模型对应的多个优化创建逻辑；
    基于所述多个优化创建逻辑进行编码，得到包括所述信息管理子模块和所述至少一个管理子模块的所述投放管理应用。
  9. 一种信息投放方法，所述方法由展示设备执行，包括：
    通过信息展示子模块响应信息展示请求，展示信息展示界面，指示设备信息子模块获取展示设备信息；
    通过信息查询子模块获取所述展示设备信息对应的目标投放信息，所述目标投放信息为投放设备依据投放管理领域对应的各个互相独立的模块所投放的信息，所述投放管理领域为投放领域中用于对投放的信息进行管理的领域；
    通过信息播放子模块在所述信息展示界面上展示所述目标投放信息；
    其中，所述信息展示子模块、所述设备信息子模块、所述信息查询子模块和所述信息播放子模块为基于投放展示领域的子域划分结果得到的各个互相独立的模块，所述投放展示领域为所述投放领域中用于对投放的信息进行展示的领域。
  10. 根据权利要求9所述的方法，其中，所述通过信息展示子模块响应信息展示请求之前，所述方法还包括：
    依据投放需求用例，对所述投放展示领域进行子域划分，得到多个信息展示子域，所述投放需求用例包括所述投放领域的业务知识；
    依据所述投放需求用例，确定所述多个信息展示子域的业务范围，将所述多个信息展示子域的业务范围确定为多个展示上下文；
    依据所述投放需求用例，分析所述多个展示上下文中各展示上下文分别对应的模型元素，得到与所述多个展示上下文对应的多个展示模型；
    基于所述多个展示模型进行编码，得到包括所述信息展示子模块、所述设备信息子模块、所述信息查询子模块和所述信息播放子模块的投放展示应用；
    运行所述投放展示应用，生成所述信息展示请求。
  11. 根据权利要求10所述的方法，其中，
    所述多个信息展示子域包括投放展示子域、信息查询子域、设备信息子域和信息播放子域；
    所述投放展示子域是指展示投放的信息的核心域，所述信息查询子域是指查询投放的信息的支撑域，所述设备信息子域是指查询展示设备的信息的支撑域，所述信息播放子域是指播放投放的信息的支撑域；
    所述多个展示上下文包括信息展示上下文、信息查询上下文、设备信息上下文和信息播放上下文。
  12. 根据权利要求10或11所述的方法，其中，所述依据所述投放需求用例，分析所述多个展示上下文中各展示上下文分别对应的模型元素，得到与所述多个展示上下文对应的多个展示模型，包括：
    依据所述投放需求用例，分析当前展示上下文对应的模型元素，得到当前展示聚合根、当前展示实体和当前展示值对象，所述当前展示上下文为所述多个展示上下文中的任一展示上下文；
    将所述当前展示聚合根、所述当前展示实体和所述当前展示值对象，组合为所述当前展示上下文对应的当前展示模型；
    当完成对所述多个展示上下文中各展示上下文的处理时，得到与所述多个展示上下文对应的所述多个展示模型，所述多个展示模型包括所述当前展示模型。
  13. 一种用于信息投放的投放装置，包括：
    信息管理子模块，配置为在投放管理界面上，接收作用在投放控件上的投放操作，响应所述投放操作，获取目标投放信息；
    子信息获取模块，配置为依据所述目标投放信息，获取至少一个管理子模块对应的至少一个管理子信息，其中，所述信息管理子模块和所述至少一个管理子模块为基于投放管理领域的子域划分结果得到的各个互相独立的模块，所述投放管理领域为基于投放流程从投放领域划分出的用于对投放的信息进行管理的领域；
    处理模块，配置为通过所述至少一个管理子模块对所述至少一个管理子信息进行处理；
    信息展示模块，配置为依据处理结果在所述投放管理界面上，展示所述目标投放信息，基于展示的目标投放信息指示展示设备依据投放展示领域对应的各个互相独立的模块展示所述目标投放信息，所述投放展示领域为所述投放领域中用于对投放的信息进行展示的领域。
  14. 一种用于信息投放的展示装置，包括：
    信息展示子模块，配置为响应信息展示请求，展示信息展示界面，指示设备信息子模块获取展示设备信息；
    信息查询子模块，配置为获取所述展示设备信息对应的目标投放信息，所述目标投放信息为投放设备依据投放管理领域对应的各个互相独立的模块所投放的信息，所述投放管理领域为投放领域中用于对投放的信息进行管理的领域；
    信息播放子模块，配置为在所述信息展示界面上展示所述目标投放信息；其中，所述信息展示子模块、所述设备信息子模块、所述信息查询子模块和所述信息播放子模块为基于投放展示领域的子域划分结果得到的各个互相独立的模块，所述投放展示领域为所述投放领域中用于对投放的信息进行展示的领域。
  15. 一种用于信息投放的投放设备，包括：
    第一存储器，用于存储可执行指令；
    第一处理器，用于执行所述第一存储器中存储的可执行指令时，实现权利要求1至8任一项所述的信息投放方法。
  16. 一种用于信息投放的展示设备，包括：
    第二存储器，用于存储可执行指令；
    第二处理器，用于执行所述第二存储器中存储的可执行指令时，实现权利要求9至12任一项所述的信息投放方法。
  17. 一种计算机可读存储介质，存储有可执行指令，用于引起第一处理器执行时，实现权利要求1至8任一项所述的信息投放方法；或者用于引起第二处理器执行时，实现权利要求9至12任一项所述的信息投放方法。
PCT/CN2021/095669 2020-06-17 2021-05-25 一种信息投放方法、装置、设备及计算机可读存储介质 WO2021254103A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/740,307 US20220270122A1 (en) 2020-06-17 2022-05-09 Information delivery method, apparatus, and device, and computer-readable storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010553240.X 2020-06-17
CN202010553240.XA CN113807877A (zh) 2020-06-17 2020-06-17 一种信息投放方法、设备及存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/740,307 Continuation US20220270122A1 (en) 2020-06-17 2022-05-09 Information delivery method, apparatus, and device, and computer-readable storage medium

Publications (1)

Publication Number Publication Date
WO2021254103A1 true WO2021254103A1 (zh) 2021-12-23

Family

ID=78892665

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/095669 WO2021254103A1 (zh) 2020-06-17 2021-05-25 一种信息投放方法、装置、设备及计算机可读存储介质

Country Status (3)

Country Link
US (1) US20220270122A1 (zh)
CN (1) CN113807877A (zh)
WO (1) WO2021254103A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114742576B (zh) * 2022-03-17 2024-05-31 北京有竹居网络技术有限公司 信息推送方法、装置和电子设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103729778A (zh) * 2013-12-12 2014-04-16 广州市网威信息技术有限公司 全渠道广告精准投放***及其方法
CN105046527A (zh) * 2015-07-16 2015-11-11 北京掌阔移动传媒科技有限公司 一种基于Facebook的广告投放方法和***
CN105117187A (zh) * 2015-08-13 2015-12-02 小米科技有限责任公司 多媒体信息展示方法和装置
US20160212234A1 (en) * 2013-08-19 2016-07-21 Beijing Gridsum Technology Co., Ltd. Method and device for monitoring push effect of push information
CN110874763A (zh) * 2019-10-22 2020-03-10 广州原子网络科技有限公司 智能广告精准投放***

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20160212234A1 (en) * 2013-08-19 2016-07-21 Beijing Gridsum Technology Co., Ltd. Method and device for monitoring push effect of push information
CN103729778A (zh) * 2013-12-12 2014-04-16 广州市网威信息技术有限公司 全渠道广告精准投放***及其方法
CN105046527A (zh) * 2015-07-16 2015-11-11 北京掌阔移动传媒科技有限公司 一种基于Facebook的广告投放方法和***
CN105117187A (zh) * 2015-08-13 2015-12-02 小米科技有限责任公司 多媒体信息展示方法和装置
CN110874763A (zh) * 2019-10-22 2020-03-10 广州原子网络科技有限公司 智能广告精准投放***

Also Published As

Publication number Publication date
US20220270122A1 (en) 2022-08-25
CN113807877A (zh) 2021-12-17

Similar Documents

Publication Publication Date Title
US10705942B1 (en) Simulated testing of API
US11936745B2 (en) Automated platform provisioning system
US20160044132A1 (en) Systems and Methods for RWD App Store Based Collaborative Enterprise Information Management
US20140129457A1 (en) An interactive organizational decision-making and compliance facilitation portal
CN108519952A (zh) 一种分布式的web自动化测试***及方法
CN109582307A (zh) 基于统一入口的活动创建方法、装置、设备及存储介质
CN115640045B (zh) 基于领域驱动设计的低代码开发平台及业务***创建方法
US10198537B2 (en) Method and system for implementing intelligent system diagrams
US10419566B2 (en) System and method for displaying AR content
US11010200B2 (en) Finite state machine driven workflows
US11640307B2 (en) Process initiation
WO2021254103A1 (zh) 一种信息投放方法、装置、设备及计算机可读存储介质
CN115857886A (zh) 基层政务应用的低代码开发平台
Meijers Hands-On Azure Digital Twins: A practical guide to building distributed IoT solutions
Dragoicea et al. Integrating HLA and service-oriented architecture in a simulation framework
CN116167730A (zh) 一种bim协同可视化管理方法
TW201725542A (zh) 表單管理系統及方法
CN113934408A (zh) 数据服务平台及其生成应用程序接口的方法
CN110648081A (zh) 用于计算***的业务建模方法、装置和计算机***
JP2023501850A (ja) ビジネス監査報知方法及びゲートウェイ、電子機器、読取可能な媒体及びコンピュータプログラム
US9268533B2 (en) Method and apparatus for enabling layered property definition in traditional and cloud computing environments
Sreeram Azure Serverless Computing Cookbook: Build and monitor Azure applications hosted on serverless architecture using Azure functions
KR20200082024A (ko) 업무 화면 생성 방법 및 이를 수행하는 시스템
Liu Web information transfer between android client and server
Raines et al. Platform as a service: A 2010 marketplace analysis

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21825544

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 28/04/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21825544

Country of ref document: EP

Kind code of ref document: A1