CN110286893B

CN110286893B - Service generation method, device, equipment, system and storage medium

Info

Publication number: CN110286893B
Application number: CN201910584200.9A
Authority: CN
Inventors: 王家乐; 袁鹏; 宋愷晟; 朱胜栋; 曹洪伟
Original assignee: Beijing Baidu Netcom Science and Technology Co Ltd; Shanghai Xiaodu Technology Co Ltd
Current assignee: Baidu Online Network Technology Beijing Co Ltd; Shanghai Xiaodu Technology Co Ltd
Priority date: 2019-06-28
Filing date: 2019-06-28
Publication date: 2023-08-15
Anticipated expiration: 2039-06-28
Also published as: CN110286893A

Abstract

The embodiment of the invention provides a service generation method, device, equipment, system and storage medium. The method comprises the following steps: acquiring a description file corresponding to the skills; converting the description file into a skill service code; and deploying the corresponding skill service by utilizing the skill service code. According to the embodiment of the invention, the description file of the skills is directly converted into the skill service codes, and then the corresponding skill service is deployed, so that the rapid generation of the service is facilitated, and the programming difficulty of service development is reduced.

Description

Service generation method, device, equipment, system and storage medium

Technical Field

The present invention relates to the field of computer technologies, and in particular, to a service generating method, apparatus, device, system, and storage medium.

Background

In the development process of scenario skill applications such as games, game planning is required to be compiled, development languages and program compiling tools are selected, a development environment and a bottom layer framework are built, art styles and manufacturing standards are determined, and clients/servers used for development are built. The developer then writes the code accordingly in accordance with the written game plan.

The game planning may include many episodes, so that the development process is complex, the programming needs to be specialized, team cooperation is often needed, personnel are centrally distributed, and development cycles are scheduled.

Disclosure of Invention

The embodiment of the invention provides a service generation method, device, equipment, system and storage medium, which are used for solving one or more technical problems in the prior art.

In a first aspect, an embodiment of the present invention provides a service generating method, including:

acquiring a description file corresponding to the skills;

converting the description file into a skill service code;

and deploying the corresponding skill service by utilizing the skill service code.

In one embodiment, obtaining a description file corresponding to a skill includes:

receiving attribute information of the skills from an originating terminal;

editing business logic of the skills;

and generating a description file corresponding to the skill according to the attribute information and the business logic.

In one embodiment, the converting the description file into a skill service code includes:

after reorganizing the resources in the description file, storing the reorganized resources in a storage end, and acquiring the storage positions of the resources in the storage end;

According to the description file, performing intention registration of the skills to obtain a registration result;

and converting the description file into a skill service code according to the attribute information and the business logic included in the description file and the registration result.

In one embodiment, the deploying the corresponding skill service using the skill service code includes:

storing the skill service code to a designated service deployment end; or alternatively

Storing the skill service code and the description file to a designated service deployment end;

the service deployment end comprises at least one of an object storage system and a content distribution network.

In one embodiment, the method further comprises:

receiving voice to be executed;

identifying intention to be executed from the voice to be executed;

and sending the intention to be executed to a service deployment end, and executing skill service codes corresponding to the intention to be executed by the service deployment end.

In one embodiment, the skills are scenario skills and the description file is a scenario description file.

In a second aspect, an embodiment of the present invention provides a service generating apparatus, including:

The acquisition module is used for acquiring the description file corresponding to the skill;

the conversion module is used for converting the description file into a skill service code;

and the deployment module is used for deploying the corresponding skill service by utilizing the skill service code.

In one embodiment, the acquisition module includes:

the receiving sub-module is used for receiving attribute information of the skills from the development end;

the editing sub-module is used for editing the business logic of the skills;

and the generating sub-module is used for generating a description file corresponding to the skill according to the attribute information and the business logic.

In one embodiment, the conversion module includes:

the reorganization sub-module is used for reorganizing the resources in the description file, storing the reorganized resources in a storage end and acquiring the storage positions of the resources in the storage end;

the booklet annotating module is used for registering the intention of the skills according to the description file to obtain a registration result;

and the conversion sub-module is used for converting the description file into a skill service code according to the attribute information and the business logic included in the description file and the registration result.

In one embodiment, the deployment module is further configured to save the skill service code to a designated service deployment end; or, storing the skill service code and the description file to a designated service deployment end; the service deployment end comprises at least one of an object storage system and a content distribution network.

In one embodiment, the apparatus further comprises:

the receiving module is used for receiving the voice to be executed;

the recognition module is used for recognizing the intention to be executed from the voice to be executed;

the sending module is used for sending the intention to be executed to a service deployment end, and the service deployment end executes skill service codes corresponding to the intention to be executed.

In a third aspect, an embodiment of the present invention provides a service generating system, including:

the development terminal is used for creating skills and storing attribute information of the skills;

the service generating terminal comprises the service generating device with any structure in the embodiment of the invention.

In one embodiment, the system further comprises:

the first storage end is used for storing the description file;

and the second storage end is used for storing the resources in the reorganized description file.

In one embodiment, the system further comprises:

and the service deployment end is used for storing skill service codes of all skills.

In one embodiment, the system further comprises:

the device side is used for detecting the voice to be executed and sending the voice to be executed to the service generating side so as to identify the intention to be executed at the service generating side;

The service deployment end is also used for receiving the intention to be executed, executing the skill service code corresponding to the intention to be executed, and sending corresponding resources to the equipment end in the process of executing the skill service code.

In a fourth aspect, an embodiment of the present invention provides a service generating device, where the function of the device may be implemented by hardware, or may be implemented by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above.

In one possible design, the structure of the device includes a processor and a memory, where the memory is configured to store a program for supporting the device to perform the service generating method described above, and the processor is configured to execute the program stored in the memory. The device may also include a communication interface for communicating with other devices or communication networks.

In a fifth aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer software instructions for use by a service generating device, including a program for executing the above-described service generating method.

One of the above technical solutions has the following advantages or beneficial effects: according to the embodiment of the invention, the description file of the skills is directly converted into the skill service codes, and then the corresponding skill service is deployed, so that the rapid generation of the service is facilitated, and the programming difficulty of service development is reduced.

The foregoing summary is for the purpose of the specification only and is not intended to be limiting in any way. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features of the present invention will become apparent by reference to the drawings and the following detailed description.

Drawings

In the drawings, the same reference numerals refer to the same or similar parts or elements throughout the several views unless otherwise specified. The figures are not necessarily drawn to scale. It is appreciated that these drawings depict only some embodiments according to the disclosure and are not therefore to be considered limiting of its scope.

Fig. 1 shows a flowchart of a service generation method according to an embodiment of the present invention.

Fig. 2 shows a flowchart of a service generation method according to an embodiment of the present invention.

Fig. 3 shows a flowchart of a service generation method according to an embodiment of the present invention.

Fig. 4 shows a block diagram of a service generating apparatus according to an embodiment of the present invention.

Fig. 5 shows a block diagram of a service generating apparatus according to an embodiment of the present invention.

Fig. 6 shows a block diagram of a service generation system according to an embodiment of the invention.

Fig. 7 shows a block diagram of a service generation system according to an embodiment of the present invention.

Fig. 8 shows a block diagram of an example of a service generation system according to an embodiment of the present invention.

Fig. 9 shows a flowchart of an example of a service generation method according to an embodiment of the present invention.

FIG. 10a is a schematic diagram of a template selection interface of the visual editor.

Fig. 10b and 10c are schematic diagrams of a code editing interface of the visual editor.

Fig. 11 shows a block diagram of a service generating apparatus according to an embodiment of the present invention.

Detailed Description

Hereinafter, only certain exemplary embodiments are briefly described. As will be recognized by those of skill in the pertinent art, the described embodiments may be modified in various different ways without departing from the spirit or scope of the present invention. Accordingly, the drawings and description are to be regarded as illustrative in nature and not as restrictive.

Fig. 1 shows a flowchart of a service generation method according to an embodiment of the present invention. As shown in fig. 1, the service generation method includes:

and S11, acquiring a description file corresponding to the skills.

Skills may include the application of internet services on artificial intelligence interaction devices. Take conversational artificial intelligence devices as an example: what the user and device say can be today; the device answers "temperature xxx of today cloudy,..; the weather service in the background of the device can understand the inquiry of the user and give a corresponding solution, and the weather service is a skill.

In one embodiment, the skills are scenario skills and the description file is a scenario description file. Some skills are for example: games, stories, etc. include a scenario of many scene combinations. From the storage end of the file, a skill corresponding scenario description file with scenarios can be read.

And step S12, converting the description file into a skill service code.

In one example, attribute information for skills, business logic, and the like may be included in the description file. And converting attribute information, business logic and the like of the skills into corresponding codes, and organizing the codes according to a certain sequence to form skill service codes.

And step S13, deploying the corresponding skill service by utilizing the skill service code.

Specifically, the service skill code may be saved to a designated service deployment end, or the skill service code may be saved to the designated service deployment end together with the description file.

According to the embodiment of the invention, the description file of the skills is directly converted into the skill service codes, and then the corresponding skill service is deployed, so that the rapid generation of the service is facilitated, and the programming difficulty of service development is reduced.

In one embodiment, as shown in fig. 2, step S11 includes:

Step S21, receiving attribute information of skills from an originating terminal.

The property information of skills is generated when creating skills in an open platform of a conversational artificial intelligence system at the development end, such as DBP (DuerOS BOT Platform, duly BOT platform). Wherein, duerOS is a conversational artificial intelligence operating system, and DBP is an open platform of DuerOS. The BOT may be a chat BOT dialog system. The attribute information of the skills may include at least one of types of the skills, basic information and skill entry intents, and the basic information of the skills may include at least one of names, icons, rights information, announcements, presentation images, and billing information of the skills. The rights information may include authors, manufacturers, etc. The skill entry intent may include an intent to initiate the skill. For example, "open game a", "enter game a", etc.

And S22, editing business logic of the skills.

After the back end receives the attribute information of the skills, a visual editor can be utilized to edit the business logic of the skills. For example, in an interface of the visual editor, a desired template is selected, a presentation device for the skill is selected, components corresponding to the scenes included in the business logic in the description file structure are set, relationships among the components are determined according to the relationships among the scenes, and the like. Wherein, each component in the description file structure comprises one or more of a chapter component, a node component, a card component, a presentation component, a template component, a prompt component, a speaking component, a condition-related status (condition) component, and a user-related status (state) component. The description of each component includes the properties of the component, and each component can be converted into corresponding code.

And S23, generating a description file corresponding to the skills according to the attribute information and the business logic. Specifically, according to the attribute information, each component corresponding to the business logic, the relationship between the components, the attribute of each component, and the like, a description file of structured data in JSON (JavaScript Object Notation ) format or XML (eXtensible Markup Language, extensible markup language) format, and the like, may be generated.

For example, after editing according to the attribute information of the skills and the business logic is completed at the interface of the visual editor, the description file conforming to the description file structure can be automatically generated in response to the operation of clicking the code export control by the developer.

In one embodiment, as shown in fig. 2, step S12 includes:

and S31, reorganizing the resources in the skill description file to obtain reorganized storage positions.

For example, after reorganizing the resources in the description file, storing the reorganized resources in a storage end, and obtaining the storage positions of the resources in the storage end. The storage may include a variety of databases. Storing the images in the description file into an image database, storing the video into a video database, and storing the audio into an audio database. For another example, the web page address and/or web page content in the description file is saved to a web page database.

The databases in the examples may be located on the same device or on different devices. After reorganizing the resources in a certain description file, the storage positions of various resources in the description file are recorded. And includes the storage locations of the required resources in the generated skill service code. If certain resources need to be invoked, the resources may be invoked by their storage locations in the skills services code.

And step S32, performing intention registration of the skills according to the description file to obtain a registration result.

Various intents included in the skill, such as skill entry intents, scene intents corresponding to nodes, etc., may be extracted from the description file and registered with the development terminal. At the development end, it is possible to determine which skill service the intention belongs to, and which server the skill service is stored in, etc., based on the intention. The intent may include a plurality of words, and the words in the intent may be split and registered in a dictionary at the development end. In addition, intent can be generalized and the same intent can be associated with similar words.

And step S33, converting the description file into a skill service code according to the description file, the reorganized storage position and the registration result.

For example, the description file is converted into a skill service code based on the attribute information and business logic of the skills included in the description file, the storage location after the resource reorganization, and the intention registration result. Code templates of some programming languages can be preset, and in the coding process, a description file is converted into codes in a certain programming language format by using a code generator of the programming language.

In one embodiment, in step S13, the service may be deployed in a variety of ways:

and in the first mode, the skill service codes are stored in a designated service deployment end.

And secondly, storing the skill service codes and the description files to a designated service deployment terminal.

The service deployment end may include an object storage system, such as a BOS (Baidu Object Storage, object storage) system, and may also include a CDN (Content Delivery Network ), and the like.

In one embodiment, as shown in fig. 3, the method further comprises:

step S41, receiving voice to be executed.

Step S42, recognizing intention to be executed from the voice to be executed. For example, the identified intent to be performed may be a skill entry intent, or an intent of a certain scene of a skill.

Step S43, the intention to be executed is sent to a service deployment end, and the service deployment end executes skill service codes corresponding to the intention to be executed.

In an application scenario, after the device side picks up the voice to be executed of the user, the voice may be sent to the voice recognition module. The speech recognition module may perform ASR (Automatic Speech Recognition ) processing on the speech to obtain text, and NLU (Natural Language Understanding, natural speech understanding) processing on the text to obtain intent to be executed. The voice recognition module can be arranged in an independent server, and can also be arranged in a development end, a service generation end, a service deployment end and the like. After the intention to be executed is identified from the voice to be executed, searching the skill service to which the intention belongs, and sending the intention to a service deployment end where the skill service is deployed. And the service deployment end executes the skill service code corresponding to the intention. During execution of the code, corresponding resources may be returned to the device side. For example, the sound box picks up "i want to play game a" sent by the user, sends the voice to the service generating end, and determines that the intention to be executed is to open game a after performing voice recognition. The intention to be executed is sent to the server where game a is deployed. In the server, the code of game a is found according to the intention to be executed. And executing the code of the game A, and returning a main interface of the game A to the sound box, wherein the main interface can comprise images, characters, sound effects, videos and the like. Then, according to the operation (such as voice, gesture or mouse operation) of the user on the game a, the current intention of the user is identified, the code corresponding to the current intention is executed, and the resource corresponding to the current intention in the game a is returned step by step.

Fig. 4 shows a block diagram of a service generating apparatus according to an embodiment of the present invention. As shown in fig. 4, the service generating apparatus may include:

an obtaining module 51, configured to obtain a description file corresponding to the skill;

a conversion module 52 for converting the description file into a skill service code;

and a deployment module 53, configured to deploy a corresponding skill service by using the skill service code.

In one embodiment, as shown in fig. 5, the obtaining module 51 includes:

a receiving sub-module 511, configured to receive attribute information of the skills from an originating terminal;

an editing sub-module 512 for editing business logic of the skills;

and the generating sub-module 513 is configured to generate a description file corresponding to the skill according to the attribute information and the business logic.

In one embodiment, attribute information for skills is generated when an open platform of a conversational artificial intelligence system at the development end, such as a DBP, creates the skills. The attribute information of the skills may include at least one of types of the skills, basic information and skill entry intents, and the basic information of the skills may include at least one of names, icons, rights information, announcements, presentation images, and billing information of the skills. The rights information may include authors, manufacturers, etc. The skill entry intent may include an intent to initiate the skill. For example, "open game a", "enter game a", etc.

In one embodiment, the conversion module 52 includes:

a reorganizing submodule 521, configured to reorganize the resources in the description file, store the reorganized resources in a storage end, and obtain a storage position of the resources in the storage end;

a booklet annotating module 522, configured to register the intention of the skill according to the description file, so as to obtain a registration result;

a conversion sub-module 523, configured to convert the description file into a skill service code according to the attribute information and the business logic included in the description file, and the registration result.

In one embodiment, the deployment module 53 is further configured to save the skill service code to a designated service deployment end; or, storing the skill service code and the description file to a designated service deployment end; the service deployment end comprises at least one of an object storage system and a content distribution network.

In one embodiment, the apparatus further comprises:

a receiving module 61 for receiving a voice to be executed;

the recognition module 62 is configured to recognize an intention to be executed from the voice to be executed;

and the sending module 63 is configured to send the intention to be executed to a service deployment end, where the service deployment end executes a skill service code corresponding to the intention to be executed.

The functions of each module in the service generating device in the embodiment of the present invention may be referred to the corresponding description in the service generating method, which is not described herein.

Fig. 6 shows a block diagram of a service generation system according to an embodiment of the invention. As shown in fig. 6, the service generation system may include:

an development terminal 71 for creating skills and saving attribute information of the skills. Attribute information of skills may be generated when an open platform of the conversational artificial intelligence system, such as a DBP, creates the skills. Wherein, the attribute information of the skills can comprise at least one of types of the skills, basic information and skill entrance intention, and the basic information of the skills can comprise at least one of names, icons, rights information, word-of-art, presentation images and charging information of the skills. The rights information may include authors, manufacturers, etc. The skill entry intent may include an intent to initiate the skill. For example, "open game a", "enter game a", etc.

The service generating terminal 72 includes the service generating apparatus of any one of the structures in the above embodiments.

In one embodiment, as shown in fig. 7, the system further comprises:

a first storage end 73 for storing a description file;

A second storage 74, configured to store the reorganized resources in the description file.

In one embodiment, the system further comprises:

a service deployment end 75, configured to store skill service codes of the skills.

In one embodiment, the system further comprises:

the device end 76 is configured to detect a voice to be executed, and send the voice to be executed to the service generating end 72, so as to identify an intention to be executed at the service generating end 72;

the service deployment end 75 is further configured to receive the intent to be executed, execute a skill service code corresponding to the intent to be executed, and send corresponding resources to the device end in the process of executing the skill service code.

The functions of each device in the service generation system in the embodiment of the present invention may be referred to the corresponding description in the service generation method, which is not described herein.

Application example one

Taking game development as an example, the service generation system may be a game development integration system for a conversational AI (Artificial Intelligence ) system. The game development integrated system of the conversational AI system can be an adventure game/story integrated development environment/platform facing role playing, thereby realizing the unprogrammed development of the voice skill game/story, and a user can perform the relevant development operation of the voice skill without programming.

The developer can select templates or custom business logic through the system, and generate scenario description files in a visual editing mode. The system can generate corresponding skill service codes according to the scenario description file and complete deployment. The developer may conduct online simulation and true machine testing to verify a particular application. Through visual editing scenario, the service updating technology can update online service, and personalized synthesis of TTS (Text To Speech) can improve the infectivity of the service and make the application more personalized. In addition, for the existing scripted game, the existing game script can be converted and transplanted into a file conforming to the scenario description file structure of the scheme, so that codes are generated and deployment is completed, and conversational voice service is realized.

As shown in fig. 8, the architecture of the system is as follows:

and a view layer for realizing the function of a visual editor and outputting the scenario description file. Only scenario description files can be edited at the view layer, and scenario description files are not stored. For example, scenario description files are stored to the BOS. The view layer may receive attribute information of skills from the development side. The visual editor can be utilized to realize the contents such as text, graphics and the like of the business logic of the front-end user design and editing skills at the view layer.

And a service (service) layer for providing distribution and return of the requests from the view layer to the controller layer and sending the output result of the visual editor to the controller layer to play a role in transfer. The generated scenario description file can be saved to the storage layer through the service layer.

And a controller (controller) layer for generating codes according to the scenario description file and deploying services. The controller layer may include a service generation side.

A storage layer, such as a DAO (data access object ) layer, may serve as a platform database for storing scenario description files for skills.

External services may include, for example, BOS, TTS generation services, audio databases, image libraries, and the like. Wherein the BOS store can be pushed directly to the CDN (Content Delivery Network ). The audio database, the image library may store audio, images, etc. after the scenario description file is reformed. The TTS generation service may convert text in the scenario description file that needs to be converted to speech.

In addition, the system can also interact with the equipment end through an open platform. For example, the BOT engine interacts with the device side through integration in a development platform such as DBP.

Wherein, the controller layer mainly realizes the following functions:

1) A code is generated. And reading the scenario description file to obtain the structure, the content, the configuration and the like of the scenario description file. Code for a PHP (Hypertext Preprocessor ) or other programming language is generated at the controller layer.

2) And (5) resource conversion. The resources in the scenario description file are reorganized and then put in a designated position, DAO (data access object ) layer, CDN, etc. In the coding process, resources such as images, audio and the like in the scenario description file are split and tidied again through a controller layer. For example, the images in the resource are transferred to a new storage device, text in the resource as speech output is converted into text by TTS, SSML (Speech Synthesis Markup Language ) splicing is performed, and the like. The rearranged resources are then stored to a designated location, e.g., in a different DAO layer, external service. This may include the storage location of the resource to be rearranged in the generated code.

During the coding process, registration of intent and dictionary may also be performed. For example, entry intents of skills and intents corresponding to respective scenes are extracted from scenario description files. These intents are registered with an open platform of a conversational artificial intelligence system, such as a DBP. Each intent may include one or more words that are saved to an open platform dictionary system. Thus, in the open platform, if user voice is received, the user voice can be identified to obtain intention, and the skill to which the intention belongs can be determined. In addition, related utterances representing different expressions of the same intent may also be saved to the dictionary system. After the service is deployed, if the open platform receives the user voice, the affiliated skill can be found according to the intention in the voice, and the intention is sent to a server for processing in which the skill is deployed.

3) The service deployment, the controller layer saves the generated execution code to the appointed server, and also saves the description file and the code to the appointed server. When the code of the service is executed, the resource can be read from the description file corresponding to the code, and the resource can also be read from the storage position of the database indicated by the code.

As shown in fig. 9, the specific flow of service development is as follows:

s101, creating skills on an open platform of the conversational artificial intelligence system.

S102, distributing new skill types

S103, saving the basic skill information.

S104, saving skill intention information.

Wherein an open platform of a conversational artificial intelligence system, such as DBP (DuerOS Bot Platform), may use the functionality of a visual editor. DuerOS is a conversational artificial intelligence operating system, and DBP is an open platform for DuerOS. The BOT may be a chat BOT dialog system.

Among other things, skills may include Web Services (Web Services) based internet applications, such as game Services, story Services, etc., which may also be referred to as application Services.

Skill types may include a variety of, for example: games, stories, etc.

The skill profile may include: names such as "game A", icons, authors, whether to charge, manufacturer, announce the words, rights information, display images, etc.

The skill intent information may include a skill entry intent. The skill entry intent may express how to enter the skill. For example, "open game a", "i want to play child game a".

The present service can be distinguished from other services according to attribute information such as skill type, skill basic information, and skill entry intention.

S105, creating a scenario description file in a game factory. The scenario description file is also simply referred to as script (script). For example: after the game factory receives attribute information such as skill type, skill basic information, skill entrance intention and the like of the skill from the open platform, a scenario description file with a certain structure can be generated. The scenario description file includes attribute information and business logic of the skill. The business logic of a skill may include various scenarios of the skill. For example, the business logic of a game skill includes what the game skill needs to demonstrate in each scenario. As another example, business logic for a story skill includes story content for each scene of the story skill.

S106, the generated scenario description file can be stored in a designated position such as a BOS system.

And S107, if the scenario description file is updated, uploading the updated file to an object storage system such as a BOS system, and generating and storing a storage address such as a URL (Uniform Resource Locator ) corresponding to the scenario description file in the BOS.

S108, the scenario description file can be converted into skill service codes by using a code generator during coding. May be converted into code in a variety of different programming languages, such as PHP or other programming languages. And in the coding process, reorganizing the resources in the scenario description file and storing the resources in the appointed position.

During the coding process, the intent expression may be updated. Updating intent expressions can be understood as a generalization process. For example: an intention is called "entering a door", which can be generalized as "entering a door" and "entering a door", and a certain intention is updated to various common expressions, so that the same intention is represented by the various expressions.

The scenario description file generated is unchanged, and the intention expression is updated when the scenario description file is coded and the service is deployed. In this way, one intention can correspond to a plurality of expressions when servicing on-line. For example, a skill entry intent at visual editing includes only entry, and the intent of "entry" may be expressed "enter", "walk in" or the like for a number of different purposes at coding.

Service deployment is then performed: and storing the codes to a designated server, and releasing the codes to be online after the codes pass the verification. After the online operation is completed, the scenario description file can be pushed to a server where the codes are deployed.

Application example two

The scenario description file is similar to a directed graph (DAG, directed Acyclic Graph). The directed graph may be split from the root node into a binary tree or other tree structure, proceeding down different branches, step by step, depending on the conditions. The flow of each scenario of business logic is represented by a series of symbols. Each scene may include multiple links or steps. Each node may be described in a different manner. For example, the root node may include a skill entry intent. The next level node of the root node may include the next scene after entering the skill.

For example, scenario descriptions are made for scenes of a "guess" game, each of which is embodied in a scenario description file. Assuming that a first scene included in the 'number guessing' game is a first party number and a second scene is a second party number, pictures, music, characters which need to be displayed by each scene can be embodied in a scenario description file in the form of nodes and the like.

The specific service logic of the game is implemented in a scenario description file, and the scenario description file also comprises attribute information of the exterior of the game: portal information, name, intellectual property, manufacturer, word of art, equity information, presentation image, etc.

The scenario description file may be described in XML or JSON format, etc. Wherein the file may comprise a plain text description, the presentation portion of the description file being generated by visual editing. The code may be generated in one-touch using the description file.

The scenario description file structure may include components of chapter (session), node (node), card (card), show (show), template (template), hint (hit), speech (speech), condition-related status (condition), user-related status (state), etc. Wherein card, show, template belongs to a presentation form, show may represent a presentation form related to DPL (DuerOS Presentation Language, duros presentation language), and other extension forms. hit indicates guidance prompt, speech indicates speech. state represents a state in the scenario that is currently relevant to the user, such as physical strength. conditions are related to environmental changes, conditions, calculations, etc. For example, there is wind, insufficient cargo, etc.

The attributes corresponding to each component, such as JSON format description, may be preset. For example, the properties of the chapter component may include: game name, game type, nodes included, background image, chapter identification, welcome node, etc. For another example, the attributes of the node components may include a node identification, a node name, a node type, a scenario to which the node corresponds, and so on. The properties of the presentation component may include properties of templates, DPL descriptions, and the like. The specific content of these attributes may be set in the interface of the visual editor.

In the scenario description file structure, nodes are important components. The node types may include: welcome nodes, end nodes, exit nodes, interactive nodes (node classes for various conversations), and automatic skip nodes. Wherein the welcome node may correspond to a root node, such as a skill entry. The exit node may correspond to a case where a portion of the play needs to be exited. The interaction nodes may correspond to various conversational scenarios. The automatic jump node may correspond to a transitional scenario. For example, clicking "i want to go to chant", the screen scrolls, and the introduction about chant "chant is" chant. For another example, after the game is cleared, the game automatically jumps to scenes such as welcome you, and then jumps to the next interaction node. The node corresponding to the next scene can be automatically jumped to by the automatic jump node, and the user does not need to interact.

The scenario description file may include a plurality of chapters, each of which may include a plurality of nodes, and each node may correspond to a scene. The attribute content of the node can be set according to the scene. For example, a node is added, and attribute contents in the node indicating what one says, whether there is interaction, another scene (corresponding node) entered, and the like are set. After all scenes (corresponding nodes) and execution sequences included in the game are edited, clicking generation is carried out, scenario description files of the game can be generated, and then description file generation codes are analyzed.

In scenario description files, presentation class scenes may be described using DPL. For example, a game scenario includes: the user says "enter hotel", after which the guaranty says "what you want to eat", and the user says "I want to eat beef". Background service, a guaranty says "beef AA money" and shows a beef image "one-dish beef" implemented by DPL description, a guaranty says "do you want to eat this one-dish beef? ", and then returns to the system. Wherein, dialogue, beef image, etc. to be displayed in the description file can be described by DPL.

Information of the devices can also be set in the visual editor so that the service can adapt to different presentation devices. For example, when the voice of the user at the device side reaches the skill service through the conversational AI system, the skill service may generate a DPL description for the device side according to the screen type, in addition to returning an effective voice broadcast, and return the DPL description to the conversational AI system. The open platform of the conversational AI system converts the DPL description into specific information, and displays the specific information on a screen of the equipment side. The screen types may include: with a screen, without a screen, screen size, etc. Examples of generating DPL descriptions from screen types include: suppose that an image and an audio need to be presented at the device side. The DPL description of the graph and audio is stored on the root node, with audio returned only for non-screen speakers and audio and images returned for screen speakers.

In one example, assume that the game name is "game xx," and the business logic of the game includes multiple scenarios.

Scene one: after entering the game, "welcome to game xx, please say start the game" is presented, and after entering the game again, "welcome to game simulation again, please say continue the game" is presented. The displayed content can be displayed in a plurality of component modes such as card, show, speech and the like. The scenario may use a welcome node.

Scene II: after entering a certain restaurant in the game, the game shows "you come to the restaurant, ask what you want to eat", and after entering the restaurant again, shows "you come to the restaurant again, ask what you want to eat". The displayed content can be displayed in a plurality of component modes such as card, show, speech and the like. The scenario may use an interaction node.

Scene III: when the user needs to log out of the game, the game is logged out after the user confirms that 'you confirm how to log out of the game'. The displayed content can be displayed in a plurality of component modes such as card, show, speech and the like. The scenario may use an exit node.

According to the scenes, the nodes corresponding to the scenes are respectively determined, the content of each attribute in the nodes is set, and a description file comprising a logic description pseudo code in a JSON format is generated. The description file may include game names, nodes, scenes of the game, etc.

The service generation system provided by the embodiment of the invention is suitable for the interaction scene of the intelligent voice equipment with the screen, and can obtain good visual interaction experience on the display equipment with limited computing and storage resources. The service generation system of the embodiment of the invention is also suitable for the interaction scene of the equipment without the screen.

The scenario description file in the embodiment of the invention can be generated by using a visual editor.

As shown in fig. 10a, 10b, and 10c, the interface of the visual editor may be divided into a template selection interface and a code editing interface.

Illustratively, as shown in FIG. 10a, a user may do the following at the template selection interface:

1) A new presentation form is created from scratch. For example, in response to a selection operation of the new creation option "create from scratch", a jump is made to a page that creates a new presentation form.

2) Up-passage code files or resource files, etc. For example, in response to a selection operation of the upload file option "up passcode", a jump is made to a page of the up passcode file or resource file.

3) A default presentation form or template for the system is selected. For example, in response to a selection operation of a certain template, the selected template is loaded.

At the template selection interface, the user may select a favorite layout template to create skills, may upload a passcode file or create skills from scratch. Layout templates include a variety of, for example, simple pictures, long text, short text, and mixtures of graphics and text.

As shown in fig. 10b, the following operations may be performed at the code editing interface:

1) And the fields which can be displayed are directly displayed through the page display block diagram.

For example, the left side shows a clear frame structure and hierarchical relationship; the right side directly prompts the user of the modifiable fields, which can be edited within the text box.

2) After the global attribute is selected, a code framework affecting the global, such as a file, a style and a resource, is displayed, and the user modification modifies the global presentation state.

3) Different devices are selected. For example, a user clicking on the top device selection control will appear to be different simulator effects below (the screen types of the individual devices may be different).

4) The code is derived. The upper right corner is a code export control that the user can click on to export the code of the file.

Fig. 10c is a schematic diagram after switching to code editing. After the code editing is switched, the bottom part can be the whole operation section of the code editing. The code may be modified within this operational interval.

Advantages of using a visual editor include:

1. the complex front-end editing interface is displayed through a flow block diagram, the hierarchical structure is clear, direct editing can be clicked, and the operation is convenient.

2. Different devices can be selected, so that the display effect of the different devices can be simulated, and the simulation display effect of the different devices can be displayed in real time for each editing.

3. And the frame diagram and the code selection presentation are supported to be displayed, so that the development efficiency is greatly improved.

4. Support code export, build-in rich templates.

5. Splitting the modules of the core logic part, and directly editing codes after selection.

Application example three

The scenario description file may be automatically converted into PHP code. The corresponding PHP code is generated, for example, from each component in the scenario description file structure, the logical relationship of each component, and the like. During the code generation process, resource conversion may be performed. For example: if the image is given in the description file, the image may be deposited to the CDN. If text is given in the scenario description file, the text is converted into sound. In addition, intent and dictionary registration may also be performed. The intent is extracted from the scenario description file, intent registration is completed, and dictionary registration is performed by using a common conversation similar to the intent.

The generated skill service code is then deployed to a designated server. Such as deploying a skill service to one of the storage spaces generated by an open platform, such as a DBP, of a conversational artificial intelligence system. When performing the skill service, the conversation text resource may be returned to the open platform, which ultimately returns to the device side (e.g., a smart speaker). The servers to which the skill service is deployed may be determined using an algorithm. How to deploy the service is determined, for example, based on how many servers are on the cloud, load conditions, space conditions, new application servers, multiplexing one or more servers, and so forth. After the service is deployed, the service is audited, and the service can be online after the audit is passed.

Further, in the visual editor, the editing intent or dictionary may be clicked. The speech may become an event similar to the event generated by a mouse click, i.e., the intent of the skill service to register. The open platform of the conversational artificial intelligence system recognizes the intent of the user's speech via ASR and NLU. The identified intent is sent to the server where the generated code is located. After receiving the intention, the server executes the code corresponding to the intention.

For example, a user speaks "open game A" speech into a speaker that converts the speech into intent by sending it to an open platform. The open platform can find out the game A skill service to which the intention belongs according to the information registered by the intention, so that the intention is sent to a server where the game A skill service is deployed. After receiving the intention, the server executes the skill service code corresponding to the intention. And returning the execution result to the open platform. If there is a DPL description, the open platform can be visually presented through the DPL. The open platform sends this service resource, such as sound, image, etc., to the intelligent speaker or other device side.

This example illustrates the conversion of scenario description files into PHP codes, with similar implementation for other programming languages. The PHP code may include a plurality of PHP format files therein. Such as ". Php" ending file. The specific PHP code content is included in these files.

For example, a controller file such as an entry, an event handling class, an intent event handling root class, an intent handling class, a node resolution class, a BOT class may be included in the directory structure of PHP code. The directory structure of the PHP may also include configuration files, CI (Continuous Integration, persistent integration) files, story (store) files, lib library files, etc.

The intent processing class may include PHP formatted files of various intents. For example, startintent. Class. Php represents start intent, corresponding to welcome node. The restart intent is represented by restartintent. answer content. Class. Php represents answer intent, corresponding to user answer. repeat. repeat. The sessionsendrequest.class.php represents the end intention, corresponding to the end node.

The node resolution class may include PHP format files for a variety of nodes. For example, a base node (b-node. Class. Php), an end node (endnode. Class. Php), an exit node (quick node. Class. Php), a node resolver (nodeparser. Class. Php), a normal node (normal node. Class. Php), a problem node (query node. Class. Php), a status node (conditional node. Class. Php), a random node (randomnode. Class. Php), a child node (child node. Class. Php), a welcome node (welcome node), a start node (startnode. Class. Php), and the like.

A certain scene in the scenario description file needs audio, and the scenario description file may directly include text (converted into voice through TTS service), or may also give URL or audio file. The URL is typically a verified, accessible web page address. For example: if it is required to describe that the user asks "have had no meal", the song is put, and the audio file or URL of the song to be played is included in the scenario description file.

With the code generator, corresponding executable code can be automatically generated with scenario description files and deployed onto an open platform of a conversational AI system, such as DBP, intent and dictionary registration of skill services involved during the period, resource conversion, etc. can be seen from the relevant description of the above embodiments.

Application example four

For the existing scripts such as the scripts of the scenario game, the existing scripts can be directly converted into the content of the scenario description file structure according to the embodiment of the invention through metadata mapping and file uploading, so that services which can be executed on equipment ends such as intelligent voice equipment and the like are generated.

The process of graft transformation may include:

1. metadata mapping. Existing scripts may be referred to as files to be migrated. And mapping and associating the metadata in the existing script with the metadata in the scenario description file structure.

Wherein the metadata of the existing script may include data similar to each component in the scenario description file structure in the embodiment of the present invention. For example, metadata for an existing script may include attribute information for the name, author, vendor, icon, etc. of the game. The names, authors, vendors, icons of the games for which scripts exist are respectively associated with the names, authors, vendors, icons of the skills in the scenario description file structure.

Metadata for existing scripts may also include specific scenarios. For example: a first scene in the metadata of the existing script is associated with a root node in the scenario description file structure, and a second scene in the metadata of the existing script is associated with a child node of the root node in the scenario description file structure.

For example, the content of a scene, episode, link, etc. in a file to be migrated may correspond to attribute information of a chapter or node in a scenario description file structure. For another example, a question in a file to be migrated may correspond to attribute information of a speech (speech) in the file to be migrated.

2. Existing scripts are uploaded to an open platform at the originating end, such as DBP. And analyzing the script by the DBP according to the mapping relation to generate the content which accords with the scenario description file structure, namely the scenario description file. And then automatically generating codes and deploying services by using the scenario description file.

And establishing a mapping relation between the scenes in the existing script and chapter components, node components and the like of the scenario description file structure of the scheme. The existing script is then used to generate a file that conforms to a scenario description file structure that is similar to a DAG (directed graph). Therefore, the existing scripts can be fully multiplexed, scenario description files can be quickly generated, and services at equipment ends such as intelligent voice interaction equipment can be quickly realized.

Fig. 11 shows a block diagram of a service generating apparatus according to an embodiment of the present invention. As shown in fig. 11, the apparatus includes: memory 910 and processor 920, memory 910 stores a computer program executable on processor 920. The processor 920 implements the service generation method in the above-described embodiment when executing the computer program. The number of the memories 910 and the processors 920 may be one or more.

The apparatus further comprises:

and the communication interface 930 is used for communicating with external equipment and carrying out data interaction transmission.

The memory 910 may include high-speed RAM memory or may further include non-volatile memory (non-volatile memory), such as at least one disk memory.

If the memory 910, the processor 920, and the communication interface 930 are implemented independently, the memory 910, the processor 920, and the communication interface 930 may be connected to each other and perform communication with each other through buses. The bus may be an industry standard architecture (ISA, industry Standard Architecture) bus, a peripheral component interconnect (PCI, peripheral Component Interconnect) bus, or an extended industry standard architecture (EISA, extended Industry Standard Architecture) bus, among others. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one thick line is shown in FIG. 11, but not only one bus or one type of bus.

Alternatively, in a specific implementation, if the memory 910, the processor 920, and the communication interface 930 are integrated on a chip, the memory 910, the processor 920, and the communication interface 930 may communicate with each other through internal interfaces.

An embodiment of the present invention provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements a method as in any of the above embodiments.

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.

Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present invention, the meaning of "a plurality" is two or more, unless explicitly defined otherwise.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.

Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable read-only memory (CDROM). In addition, the computer readable medium may even be paper or other suitable medium on which the program is printed, as the program may be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory.

It is to be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.

Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.

In addition, each functional unit in the embodiments of the present invention may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product. The storage medium may be a read-only memory, a magnetic or optical disk, or the like.

The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any person skilled in the art will readily recognize that various changes and substitutions are possible within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.

Claims

1. A service generation method, comprising:

receiving attribute information of skills from an originating terminal;

selecting templates required by skills in an interface of a visual editor;

selecting a skill display device;

setting each corresponding component of the scene included in the business logic in the description file structure; each component in the description file structure comprises one or more of a chapter component, a node component, a card component, a display component, a template component, a prompt component, a speaking component, a condition-related state component and a user-related state component;

determining the relation among the components according to the relation among the scenes;

generating a description file corresponding to the skills according to the attribute information, the components corresponding to the business logic, the relation among the components and the attribute of the components;

extracting intention included in skills from the description file, registering the intention to a development end, and obtaining a registration result;

converting the description file into a skill service code according to the attribute information, the business logic and the registration result included in the description file;

2. The method of claim 1, wherein deploying the corresponding skills service using the skills service code comprises:

3. The method as recited in claim 1, further comprising:

receiving voice to be executed;

identifying intention to be executed from the voice to be executed;

4. A method according to any one of claims 1 to 3, wherein the skills are scenario-like skills and the profile is a scenario profile.

5. A service generating apparatus, comprising:

the information receiving module is used for receiving attribute information of skills from the development end;

the template selection module is used for selecting templates required by skills in an interface of the visual editor;

the device selection module is used for selecting the skill display device;

the component setting module is used for setting each component corresponding to the scene included in the business logic in the description file structure; each component in the description file structure comprises one or more of a chapter component, a node component, a card component, a display component, a template component, a prompt component, a speaking component, a condition-related state component and a user-related state component;

the relation determining module is used for determining the relation among the components according to the relation among the scenes;

the file generation module is used for generating a description file corresponding to the skills according to the attribute information, the components corresponding to the business logic, the relation among the components and the attribute of the components;

The resource storage module is used for reorganizing the resources in the description file, storing the reorganized resources in the storage end and acquiring the storage position of the resources in the storage end;

the intention registration module is used for extracting intention included in skills from the description file, registering the intention to the development end and obtaining a registration result;

the file conversion module is used for converting the description file into a skill service code according to the attribute information, the business logic and the registration result which are included in the description file;

6. The apparatus of claim 5, wherein the deployment module is further configured to save the skill service code to a designated service deployment side; or, storing the skill service code and the description file to a designated service deployment end; the service deployment end comprises at least one of an object storage system and a content distribution network.

7. The apparatus as recited in claim 6, further comprising:

the receiving module is used for receiving the voice to be executed;

8. The apparatus of any one of claims 5 to 7, wherein the skills are scenario-like skills and the profile is a scenario profile.

9. A service generation system, comprising:

a service generating end comprising the service generating apparatus of any one of claims 5 to 8.

10. The system of claim 9, further comprising:

the first storage end is used for storing the description file;

11. The system of claim 9, further comprising:

12. The system of claim 11, further comprising:

13. A service generating apparatus, comprising:

one or more processors;

a memory for storing one or more programs;

the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-4.

14. A computer readable storage medium storing a computer program, which when executed by a processor implements the method of any one of claims 1 to 4.