WO2023226338A1 - 通信方法、装置以及系统 - Google Patents

通信方法、装置以及系统 Download PDF

Info

Publication number
WO2023226338A1
WO2023226338A1 PCT/CN2022/133390 CN2022133390W WO2023226338A1 WO 2023226338 A1 WO2023226338 A1 WO 2023226338A1 CN 2022133390 W CN2022133390 W CN 2022133390W WO 2023226338 A1 WO2023226338 A1 WO 2023226338A1
Authority
WO
WIPO (PCT)
Prior art keywords
rich media
applet
media message
message
information
Prior art date
Application number
PCT/CN2022/133390
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 WO2023226338A1 publication Critical patent/WO2023226338A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1059—End-user terminal functionalities specially adapted for real-time communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/55—Push-based network services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements

Definitions

  • the present application relates to the field of communication, and in particular, to a communication method, device and system.
  • Rich communication suite (RCS) technology introduces chatbot service to realize "message as a service”.
  • RCS Rich communication suite
  • users can complete a one-stop business experience such as service discovery, search, interaction, and payment within the message window, greatly improving operations.
  • the value of business news According to the current rich media communication technology, users and chatbots need to interact multiple times to complete a business process. The operation is cumbersome and the interaction process is long, which affects the user experience.
  • Embodiments of the present application provide a communication method, device and system, which can simplify user operations and improve user experience.
  • the first aspect provides a communication method, which can be executed by a rich media message application server, or can also be executed by a component (such as a chip or circuit) of the rich media message application server, which is not limited.
  • the method may include: the rich media message application server receives a first query request message from the rich media message terminal, the first query request message includes query information, and the query information includes rich media used to describe the user corresponding to the rich media message terminal.
  • the information of the message applet, the rich media message applet is an applet with the rich media message client in the rich media message terminal as the host client; in response to the first query request message, the rich media message application server obtains the rich media message applet information, and sends a first query response message to the rich media message terminal, where the first query response message contains information about the rich media message applet.
  • the rich media message terminal sends a first query request message to the rich media message application server.
  • the first query request message includes query information
  • the query information includes rich media used to describe the user corresponding to the rich media message terminal.
  • Information about the message applet In this way, the rich media message application server can obtain the rich media message applet matching the query information based on the query information, and then provide the rich media message terminal with the information of the rich media message applet. In this way, the rich media message terminal can download and run the rich media message applet based on the information of the rich media message applet, and then implement certain functions through the rich media message applet, simplify user operations, and improve user experience.
  • the rich media message application server obtains the information of the rich media message applet, including: the rich media message application server sends a second query request message to the applet management server, and The second query request message contains query information; the rich media message application server receives the second query response message from the applet management server, and the second query response message contains the information of the rich media message applet.
  • the rich media message application server can generate a second query request message based on the query information in the first query request message, and send the second query request message to the applet management server.
  • the applet management server can determine the information of the rich media message applet that matches the query information based on the query information in the second query request message, and store the rich media message applet.
  • the program information is sent to the mini program management server.
  • the rich media message application server obtains the information of the rich media message applet, including: the rich media message application server obtains the information of the rich media message applet locally based on the query information. information.
  • the rich media message application server can determine the information of the rich media message applet by itself.
  • the method before the rich media messaging application server obtains the information of the rich media messaging applet, the method further includes: the rich media messaging application server determines that the user is allowed to use the rich media messaging applet .
  • the rich media messaging application server can first determine whether the user corresponding to the rich media messaging terminal is allowed to use the rich media messaging applet. When the rich media message application server determines that the user corresponding to the rich media message terminal is allowed to use the rich media message applet, the information of the rich media message applet is then obtained.
  • the rich media message application server determines to allow the user to use the rich media message applet, including: the rich media message application server determines to allow the user to use the rich media message applet according to the user's contract information and/or the operation to which the user belongs. Provider's information, confirm that users are allowed to use rich media messaging applets.
  • the rich media message application server is a message as a platform MaaP or a chatbot Chatbot platform
  • the rich media message terminal communicates with the rich media message application server through a chatbot directory query interface.
  • the rich media message application server receives the first query request message from the rich media message terminal, including: the rich media message application server receives the first query request message through the chat robot directory query interface.
  • the rich media message application server sends a first query response message to the rich media message terminal, including: the rich media message application server sends the first query response message through the chat robot directory query interface.
  • the rich media messaging terminal can query the rich media messaging applet through the chatbot directory query interface. There is no need to add additional configuration parameters or introduce additional interface security authentication processes, which can improve the configuration efficiency and startup efficiency of the rich media messaging terminal. ; In addition, there is no need to add additional user identity authentication processes, which can improve the resource utilization of the rich media messaging system.
  • the first query request message further includes indication information, and the indication information instructs the rich media message application server to provide information about the rich media message applet based on the query information.
  • the second aspect provides a communication method, which can be executed by a rich media message terminal, or can also be executed by a component (such as a chip or circuit) of the rich media message terminal, which is not limited.
  • the method may include: the rich media message terminal sends a first query request message to the rich media message application server, the first query request message includes query information, and the query information is used to describe the rich media message message required by the user corresponding to the rich media message terminal.
  • Program information the rich media message applet is an applet with the rich media message client in the rich media message terminal as the host client; the rich media message terminal receives the first query response message from the rich media message application server, the first query The response message contains the information of the rich media message applet; the rich media message terminal downloads and runs the rich media message applet according to the information of the rich media message applet.
  • the rich media message application server is a message as a platform MaaP or a chatbot Chatbot platform
  • the rich media message terminal communicates with the rich media message application server through a chatbot directory query interface.
  • the rich media messaging terminal sends a first query request message to the rich media messaging application server, including: the rich media messaging terminal sends the first query request through the chatbot directory query interface message; the rich media message terminal receives the first query response message from the rich media message application server, including: the rich media message terminal receives the first query response message through the chat robot directory query interface.
  • the first query request message further includes indication information, and the indication information instructs the rich media message application server to provide information about the rich media message applet based on the query information.
  • the third aspect provides a communication method, which can be executed by the applet management server, or can also be executed by components (such as chips or circuits) of the applet management server, which is not limited.
  • the method may include: the applet management server receives a first query request message from the rich media message terminal, the first query request message includes query information, and the query information includes the rich media message needed to describe the user corresponding to the rich media message terminal.
  • the information of the applet is an applet with the rich media message client in the rich media message terminal as the host client; the applet management server obtains the information of the rich media message applet based on the query information; the applet management server A first query response message is sent to the rich media messaging terminal, where the first query response message contains information about the rich media messaging applet.
  • the rich media message terminal can send a first query request message to the applet management server, where the first query request message contains query information.
  • the applet management server can obtain the rich media message applet matching the query information based on the query information, and then provide the rich media message applet information to the rich media message terminal.
  • the rich media message terminal can download and run the rich media message applet based on the information of the rich media message applet, and then implement certain functions through the rich media message applet, simplify user operations, and improve user experience.
  • the method further includes: the applet management server determines that the user is allowed to use the rich media message applet. program.
  • the applet management server determines to allow the user to use the rich media messaging applet, including: the applet management server determines to allow the user to use the rich media messaging applet based on the user's contract information and/or the user's operator's information. Message, confirm that users are allowed to use rich media messaging applets.
  • the applet management server can first determine whether the user corresponding to the rich media messaging terminal is allowed to use the rich media messaging applet. When the applet management server determines that the user corresponding to the rich media message terminal is allowed to use the rich media message applet, the information of the rich media message applet is then obtained.
  • the rich media message terminal communicates with the applet management server through the applet directory query interface.
  • the applet management server receives the first query request message from the rich media message terminal, including: the applet management server receives the first query request through the applet directory query interface message; the applet management server sends a first query response message to the rich media message terminal, including: the applet management server sends the first query response message through the applet directory query interface.
  • the fourth aspect provides a communication method, which can be executed by a rich media message terminal, or can also be executed by a component (such as a chip or circuit) of the rich media message terminal, which is not limited.
  • the method may include: the rich media messaging terminal sends a first query request message to the applet management server, the first query request message includes query information, and the query information is used to describe the rich media messaging applet required by the user corresponding to the rich media messaging terminal.
  • the rich media message applet is an applet with the rich media message client in the rich media message terminal as the host client; the rich media message terminal receives the first query response message from the applet management server, the first query response message Contains information about the rich media messaging applet; the rich media messaging terminal downloads and runs the rich media messaging applet based on the information about the rich media messaging applet.
  • the rich media message terminal communicates with the applet management server through the applet directory query interface.
  • the rich media message terminal sends a first query request message to the applet management server, including: the rich media message terminal sends the first query request message through the applet directory query interface. ;
  • the rich media message terminal receives the first query response message from the applet management server, including: the rich media message terminal receives the first query response message through the applet directory query interface.
  • a communication method is provided, which method can be executed by a rich media message application server and a rich media message terminal, or can also be performed by a component (such as a chip or circuit) of the rich media message application server and a rich media message terminal.
  • the components of the terminal (such as chips or circuits) execute, and this is not limited.
  • the method may include: the rich media message terminal sends a first query request message to the rich media message application server, the first query request message includes query information, and the query information is used to describe the rich media message message required by the user corresponding to the rich media message terminal.
  • Program information, the rich media message applet is an applet with the rich media message client in the rich media message terminal as the host client; the rich media message application server receives the first query request message, and responds to the first query request message, Obtain the information of the rich media message applet, and send a first query response message to the rich media message terminal, where the first query response message contains the information of the rich media message applet; the rich media message terminal receives the first query response message, and according to the rich media message terminal Information for the Media Messaging Applet Download and run the Rich Media Messaging applet.
  • the rich media message application server is a message as a platform MaaP or a chatbot Chatbot platform
  • the rich media message terminal communicates with the rich media message application server through a chatbot directory query interface.
  • the rich media message terminal sends a first query request message to the rich media message application server, and the rich media message application server receives the first query request message, including: rich media message
  • the terminal sends a first query request message through the chat robot directory query interface, and the rich media message application server receives the first query request message through the chat robot directory query interface;
  • the rich media message application server sends a first query response message to the rich media message terminal, and the rich media message application server
  • the media message terminal receiving the first query response message includes: the rich media message application server sends the first query response message through the chat robot directory query interface, and the rich media message terminal receives the first query response message through the chat robot directory query interface.
  • the first query request message further includes indication information, and the indication information instructs the rich media message application server to provide information about the rich media message applet based on the query information.
  • the query information includes at least one of the following or a keyword contained in at least one of the following: the name of the rich media messaging applet, the type of the rich media messaging applet, The name of the provider of the rich media messaging applet, the service content description or function description of the rich media messaging applet, the languages supported by the rich media messaging client, or the version of the rich media messaging client.
  • the information of the rich media messaging applet includes the download address of the rich media messaging applet.
  • the information of the rich media message applet includes at least one of the following: the identifier of the rich media message applet, the name of the rich media message applet, the rich media message applet The address of the icon, or the version of the Rich Media Messaging applet.
  • a sixth aspect provides a communication device, which is used to perform the method in any of the possible implementations of the first to fifth aspects.
  • the device may include units and/or modules for performing the method in any possible implementation of the first to fifth aspects, such as a processing unit and/or a communication unit.
  • the device is a communication device (such as a rich media message application server, a rich media message terminal, or an applet management server).
  • the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor.
  • the transceiver may be a transceiver circuit.
  • the input/output interface may be an input/output circuit.
  • the device is a chip, chip system or circuit used in a communication device (such as a rich media message application server, a rich media message terminal, or an applet management server).
  • a communication device such as a rich media message application server, a rich media message terminal, or an applet management server.
  • the communication unit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip, chip system or circuit, etc.
  • the processing unit may be at least one processor, processing circuit or logic circuit, etc.
  • a seventh aspect provides a communication device, which includes: at least one processor configured to execute a computer program or instructions stored in a memory to perform the method in any of the possible implementations of the first to fifth aspects.
  • the device further includes a memory for storing computer programs or instructions.
  • the device further includes a communication interface, through which the processor reads the computer program or instructions stored in the memory.
  • the device is a communication device (such as a rich media message application server, a rich media message terminal, or an applet management server).
  • a communication device such as a rich media message application server, a rich media message terminal, or an applet management server.
  • the device is a chip, chip system or circuit used in a communication device (such as a rich media message application server, a rich media message terminal, or an applet management server).
  • a communication device such as a rich media message application server, a rich media message terminal, or an applet management server.
  • An eighth aspect provides a processor for executing the methods provided in the above aspects.
  • processor output, reception, input and other operations can be understood as processor output, reception, input and other operations.
  • transmitting and receiving operations performed by the radio frequency circuit and the antenna, which is not limited in this application.
  • a ninth aspect provides a computer-readable storage medium that stores program code executed by a user device.
  • the program code includes a method for executing any of the possible implementation methods of the above-mentioned first to fifth aspects. .
  • a computer program product containing instructions is provided.
  • the computer program product When the computer program product is run on a computer, it causes the computer to execute the method in any of the possible implementation modes of the first to fifth aspects.
  • An eleventh aspect provides a communication system, including at least one of the aforementioned rich media message application server, rich media message terminal, and applet management server.
  • FIG. 1 is a schematic diagram of a communication system suitable for embodiments of the present application.
  • FIG. 2 is a schematic diagram of another communication system suitable for embodiments of the present application.
  • FIG. 3 is a schematic diagram of another communication system suitable for embodiments of the present application.
  • Figure 4 is a schematic diagram of another communication system suitable for embodiments of the present application.
  • Figure 5 shows a schematic diagram of a user booking a ticket.
  • Figure 6 is a schematic diagram of a communication method 600 provided by an embodiment of the present application.
  • Figure 7 is a schematic diagram of a communication method 700 provided by an embodiment of the present application.
  • Figure 8 is a schematic flowchart of a communication method 800 provided according to an embodiment of the present application.
  • Figure 9 shows a schematic diagram of the rich media applet query effect.
  • Figure 10 is a schematic flowchart of a communication method 1000 provided according to another embodiment of the present application.
  • Figure 11 is a schematic diagram of a communication device 1100 provided by an embodiment of the present application.
  • Figure 12 is a schematic diagram of another communication device 1200 according to an embodiment of the present application.
  • the technical solutions of the embodiments of this application can be applied to various communication systems, such as fifth generation (5th generation, 5G) or new radio (new radio, NR) systems.
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solution provided by this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine type Communication (machine type communication, MTC), and Internet of Things (Internet of things, IoT) communication systems or other communication systems.
  • D2D device-to-device
  • V2X vehicle-to-everything
  • M2M machine-to-machine
  • MTC machine type Communication
  • IoT Internet of Things
  • Rich communication suite (RCS) message follows the rich communication convergence.07 (RCC.07) launched by the global system for mobile communication association (GSMA) Standard specification and rich media communication convergence.71 (rich communication convergence.71, RCC.71) standard specification.
  • RCS messages are an upgrade to traditional text messages.
  • GSMA RCS and related standards breaking through the limitations of traditional text messages on message length. and content format restrictions, supports multiple media formats such as text, pictures, audio, video, location, contacts and documents, and introduces the messaging as a platform (MaaP) platform to promote the integration of vertical industries in the information and communication industry .
  • MaaP platform
  • RCS messages can provide point-to-point messaging and group chat services.
  • RCS message content can also support pictures, audio, video, location, contacts and other forms.
  • RCS messaging can provide enhanced messaging services between individuals and applications, realize “message as a platform", and introduce a new message interaction mode - chat robot, which connects to the terminal through message dialogue and can be provided in the dialog box Search, discovery, interaction, payment and other services, thereby realizing interactive services between customers and end users in enterprises and other industries.
  • rich media messages may be called RCS messages and 5G messages (MSGin5G messages). Rich media messages can be used between IoT devices, therefore, rich media messages can also be called 5G IoT messages. It can be understood that the specific naming of the message does not limit the protection scope of the embodiments of the present application. The following is unification, which is described using rich media messages.
  • Chatbot The presentation form of industry messaging applications in rich media messages, simulating human intelligent dialogue and providing users with industry messaging service functions.
  • MiniApp It is based on web technology (such as JavaScript) and can run in the host mobile application (or host client) on the terminal device without installing it on the terminal device. s application. Among them, the host mobile application (or host client) needs to be installed on the terminal device before it can run, and usually can run multiple (kinds) of small programs.
  • Rich media messaging applet It is an applet that uses the rich media messaging application (or rich media messaging client) running on the terminal device (or rich media messaging terminal) as the host application (or host client) , that is to say, the rich media messaging applet can be downloaded from the network side by the rich media messaging application and then interpreted and executed, without being installed on the terminal device.
  • the applet engine built into the rich media messaging application used to interpret and execute the rich media messaging applet
  • the rich media messaging applet can be decoupled, for example, both can be upgraded independently of the other.
  • the rich media message applet After the rich media message applet is run, it can interact with the server corresponding to the rich media applet to implement services such as service discovery, search, interaction, and payment.
  • FIG. 1 is a schematic diagram of a communication system suitable for embodiments of the present application.
  • the communication system may include: a rich media message application server, an applet management server, and a rich media message terminal.
  • the rich media message terminal can directly communicate with the applet management server, or the rich media message terminal can also communicate with the applet management server through the rich media message application server.
  • the rich media message terminal can directly communicate with the applet management server, or the rich media message terminal can also communicate with the applet management server through the rich media message application server.
  • Rich media message terminal It means a digital mobile communication terminal that supports rich media message services. It is usually installed with a rich media message client, that is, it supports the rich media message service through the rich media message client.
  • the rich media message terminal is just a name, and it can also be generally called: terminal equipment, user equipment (UE), access terminal, subscriber unit, user station, mobile station, mobile station, Remote station, remote terminal, mobile device, user terminal, terminal, wireless communications equipment, user agent or user device.
  • UE user equipment
  • a rich media messaging terminal may be a device that provides voice/data to users, such as a handheld device, a vehicle-mounted device, etc. with wireless connection capabilities.
  • rich media messaging terminals are: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, and virtual reality (VR) devices , augmented reality (AR) equipment, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical surgery, smart grids Wireless terminals in grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, cellular phones, cordless phones, session initiation protocols ( session initiation protocol (SIP) telephone, wireless local loop (WLL) station, personal digital assistant (personal digital assistant (PDA)), handheld device with wireless communication capabilities, computing device or other process connected to a wireless modem Equipment, wearable devices, terminal equipment in the 5G network or terminal equipment in the future evolved public land mobile communication network (public land mobile network, PLMN), etc., the embodiments of this application are not
  • the rich media messaging terminal may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
  • the device used to implement the function of the rich media message terminal may be a rich media message terminal, or may be a device capable of supporting the rich media message terminal to implement the function, such as a chip system or a chip, and the device may be installed In a rich media messaging terminal.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • the rich media message terminal can also be called a 5G message terminal or RCS client (RCS client).
  • RCS client RCS client
  • the following is unification, which is described using a rich media message terminal.
  • Rich media messaging client An application or client with rich media messaging business functions. It has a built-in applet engine. It can query the information of the rich media messaging applet from the network side, download the rich media messaging applet, and run or interpret it. Execute a rich media messaging applet. For ease of understanding, the rich media messaging client is called the host client of the rich media messaging applet.
  • Rich media messaging application server a platform established by communication operators to connect with industry customers, is mainly used to implement functions such as access management, authentication, and multimedia content uploading and storage of industry customers’ Chatbots and messages, allowing industry customers to It can provide users with message services in multiple media formats.
  • the rich media messaging application server can also support rich media messaging applet business authority authentication, that is, determining whether the rich media messaging terminal is allowed to use the rich media messaging applet business.
  • the rich media message application server can be a MaaP platform or an IoT message center.
  • the MaaP platform can also be called a chatbot platform (Chatbot platform), and its naming does not limit the scope of protection of the embodiments of this application. The following is unification, which is described using the MaaP platform. The specific introduction of the MaaP platform will be explained in detail later in conjunction with Figure 2.
  • the applet management server is mainly used to review, authenticate, publish, summarize and store rich media message applet information, provide rich media message applet query services for terminal devices, and provide rich media message applet query services. Packages are stored etc.
  • the applet management server can also be called the applet management platform, or the rich media applet management server or the rich media applet management platform. The following is a unified description using the applet management server. The specific introduction to the mini program management server will be explained in detail later in conjunction with Figure 3.
  • FIG. 2 is a schematic diagram of another communication system suitable for embodiments of the present application.
  • this communication system takes the architecture of a rich media messaging system as an example.
  • the communication system may include a rich media message center, a MaaP platform, and a rich media message terminal.
  • the rich media message center and MaaP platform can be integrated with user data management (such as home subscriber server (HSS), unified data management (UDM) network element), SMS center (i.e.
  • HSS home subscriber server
  • UDM unified data management
  • SMS center i.e.
  • short message server center short message service center
  • SMSC short message service center
  • rich media message exchange gateway phone number mapping (E.164Number URI Mapping, ENUM) or domain name system (domain name system, DNS), security management and control system, business support system, bootstrapping server (bootstrapping server function, BSF) and other docking.
  • phone number mapping E.164Number URI Mapping, ENUM
  • domain name system domain name system, DNS
  • security management and control system business support system
  • business support system bootstrapping server (bootstrapping server function, BSF) and other docking.
  • BSF bootstrapping server function
  • Rich media message center It has the ability to process rich media messages, interfaces with the MaaP platform, and provides industry message functions.
  • the rich media message center includes multiple logical function modules.
  • the rich media message center includes: group chat function, IP multimedia subsystem (IMS) access function, multimedia content storage function and Configure the server.
  • IMS IP multimedia subsystem
  • Each logical function module included in the rich media message center can be deployed independently (that is, these logical function modules can be deployed on different physical devices), or they can be deployed together (that is, these functional modules are all deployed on the same physical device, or are built into the rich media message center), which are not limited by the embodiments of this application.
  • the functions of each exemplary logical function module included in the rich media message center are as follows.
  • IMS access function mainly responsible for user rich media message signaling access and media access and forwarding.
  • Rich media message processing function mainly processes personal messages, industry messages, enhanced call message sending and receiving, session management, message-related business function processing, etc.
  • Multimedia content storage function mainly used to store multimedia message files sent by individual users.
  • Configuration server Also known as device management (DM), it is mainly used to store user business-related data, such as protocol parameters, business parameters, etc.
  • the rich media message terminal can obtain relevant data by accessing the configuration server to configure the service of the rich media message terminal.
  • Group chat function It can include group chat message function and group data management. Among them, the group chat message function can be used to realize the distribution of group chat messages. Group data management can be used to create a group, invite others to join the group, delete group members, dissolve the group, transfer administrator rights, set the group name, set the group avatar and other functions. In addition, group data management can also be used to store and manage group chat-related data information, such as group member list, group name, group avatar, group member status, etc.
  • the rich media message center can also be called the 5G message center (5GMC), or it can also be called the RCS service provider network (RCS service provider network).
  • 5GMC 5G message center
  • RCS service provider network RCS service provider network
  • MaaP platform Connected with the rich media message center to provide industry messaging functions and carry interactive rich media messaging services. As shown in Figure 2, the MaaP platform can include basic functions and operational management. Among them, operation management is mainly used by operators to manage Chatbot activation, permission configuration, etc.
  • the basic functions may include the following exemplary logical function modules.
  • Chatbot directory Mainly used to summarize Chatbot data information, provide algorithm services such as matching and sorting, process Chatbot discovery requests from users, and return search results to users.
  • Chatbot information Mainly used to store Chatbot related information and process Chatbot information queries from users.
  • the relevant information may include corporate information that provides the Chatbot, such as name, trademark, business type, contact information, etc.
  • the relevant information may also include information about the Chatbot or the application itself, such as Chatbot purpose, application purpose, developer information, etc.
  • Multimedia file storage function mainly used to store multimedia message files sent by Chatbot.
  • Chatbot capability opening It is mainly used to uniformly abstract and encapsulate rich media messaging capabilities and provide Chatbot with message access capabilities.
  • the logical function modules included in the MaaP platform can be deployed independently or combined, which is not limited by the embodiments of this application.
  • FIG 3 is a schematic diagram of another communication system suitable for embodiments of the present application.
  • the communication system is an architecture of a rich media messaging system as an example.
  • a small program management server is added.
  • the mini program management server can be deployed independently, or it can be built into the MaaP platform without restrictions.
  • the applet management server may include the following logical function modules.
  • Operation management It is mainly used to review whether the rich media messaging applet meets the rich media messaging applet development specifications, certify the rich media messaging applet, and publish the rich media messaging applet. Users can only query it after it is released.
  • Mini program package storage i.e. rich media message mini program package storage: mainly used to store rich media message mini program packages.
  • Rich media message applet directory i.e., rich media message applet directory: mainly used to summarize and store rich media message applet information.
  • the rich media message applet information may include basic information of the rich media message applet, such as an identifier (ID), name, icon, version, etc.
  • the rich media message applet information may also include detailed information of the rich media message applet, such as the provider (industry customer) of the rich media message applet, business type, contact information, website, and the purpose of the rich media message applet, Developer information, etc.
  • the mini program directory and the Chatbot directory can be the same or different, and there is no restriction.
  • the architecture of the rich media messaging system includes a directory that can be used to summarize Chatbot data information, that is, to implement the Chatbot directory described in Figure 2
  • the function can also be used to summarize and store rich media message applet information, that is, to implement the function of the applet directory described in Figure 3.
  • Mini Program Query Service i.e. Rich Media Message Mini Program Query Service: Mainly used to process rich media message applet query requests from rich media message terminals, provide matching, sorting and other algorithm services, and return query results to users.
  • the query result may include rich media message applet information queried based on the rich media message applet keyword, such as: ID, name, icon, version, etc.
  • FIG 4 is a schematic diagram of another communication system suitable for embodiments of the present application. As shown in Figure 4, this communication system takes the architecture of a rich media messaging system as an example. As shown in Figure 4, compared with Figure 3, in the system shown in Figure 4, the applet management server can directly interface with the rich media message center. For the description of each device, please refer to the previous description and will not be repeated here.
  • Chatbot to interact with users through rich media message centers and MaaP platforms to provide services to users, such as completing functions such as ticket booking, hotel inquiry, and logistics inquiry.
  • FIG 5 is a schematic diagram of user booking.
  • the Chatbot of industry customers can send messages to users in a point-to-point manner, and the users reply messages to the Chatbot to complete the ticket booking function.
  • users need to enter information multiple times to interact with Chatbot, which is cumbersome and requires a long interaction process, which affects the user experience.
  • This application proposes a method to provide rich media message applet query services for rich media message terminals by adding an applet management server in the rich media message system, and then use the rich media message applet to provide services for the rich media message terminal, simplifying User operations shorten the interaction process and improve user experience.
  • the rich media applet is used to provide ticket booking services for the rich media message terminal.
  • the rich media message applet After the rich media message applet is run, the rich media message applet The message terminal can interact with the server corresponding to the rich media applet to realize the ticket booking service.
  • using rich media messaging applets to provide services for rich media messaging terminals can simplify user operations, shorten the interaction process, and improve user experience.
  • Figure 6 is a schematic diagram of a communication method 600 provided by an embodiment of the present application.
  • Method 600 may include the following steps.
  • the rich media message application server receives the first query request message from the rich media message terminal.
  • the rich media message terminal sends the first query request message to the rich media message application server.
  • the rich media message application server is a MaaP or Chatbot platform
  • the rich media message terminal communicates with the rich media message application server through a chatbot directory query interface.
  • the rich media message terminal sends a first query request message to the rich media message application server through the chatbot directory query interface.
  • the rich media message application server receives the first query request from the rich media message terminal through the chatbot directory query interface. information.
  • the rich media messaging terminal can query the rich media messaging applet through the chatbot directory query interface without adding additional configuration parameters or introducing additional interface security authentication processes, which can improve the configuration efficiency and startup efficiency of the rich media messaging terminal.
  • there is no need to add additional user identity authentication processes which can improve the resource utilization of the rich media messaging system.
  • the chat robot directory query interface represents the interface through which the rich media message terminal sends a request to the rich media application server to obtain the chat robot list.
  • the chatbot directory query interface is the Client to Service Provider Chatbot Directory interface (Client to Service Provider Chatbot Directory interface) in GSMA RCC.07. It can be understood that the name of the chatbot directory query interface does not limit the scope of protection of the embodiments of this application. That is, if the name of the interface changes in the future, the changed interface name will also be applicable to the embodiments of this application.
  • the first query request message includes query information.
  • the query information may include information describing the rich media message applet required by the user corresponding to the rich media message terminal, or information related to the rich media message applet queried by the rich media message terminal, or the rich media message applet queried by the rich media message terminal.
  • the rich media message applet is an applet with the rich media message client in the rich media message terminal as the host client.
  • the query information includes at least one of the following or a keyword contained in at least one of the following: the name of the rich media messaging applet, the type of the rich media messaging applet, the name of the provider of the rich media messaging applet, the rich media The service content description or function description of the message applet, the languages supported by the rich media messaging client, or the version of the rich media messaging client, etc.
  • the name of the rich media messaging applet indicates the name of the rich media messaging applet to be queried.
  • the type of rich media messaging applet indicates the type of rich media messaging applet to be queried.
  • -Rich Media Messaging Applet Provider Name indicates the name of the Rich Media Messaging Applet provider to be queried.
  • the service content description or function description of the rich media message applet indicates the service content or function of the rich media message applet to be queried.
  • the service content description or function description of the rich media messaging applet is a uniform resource locator (URL) escape.
  • the languages supported by the Rich Media Messaging client may indicate the preferred language of the Rich Media Messaging applet to be queried.
  • the "pl" parameter is used to represent the language of the rich media messaging applet to be queried. For example, if the language of the rich media messaging terminal is set to English, and the other preferred languages searched by the rich media messaging terminal are Spanish and German, then the query information
  • the version of the rich media messaging client indicates the version of the rich media messaging client in the rich media messaging terminal.
  • the query information may also include the number of rich media message applets, that is, the number of rich media message applets to be queried, such as the "num" parameter.
  • the query information may also include the first matching result that should be included in the query results, such as the "start" parameter.
  • the "start” parameter can use a zero-based index, that is, the first query result is 0; the second query result is 1, and so on. The "start" parameter and the "num” parameter work together to determine the query results to be returned.
  • the query information may also include the mobile station international ISDN number (mobile subscriber ISDN number, MSISDN) of the user corresponding to the rich media message terminal, where ISDN is an integrated service digital network (ISDN).
  • the query information may also include operator information to which the user corresponding to the rich media message terminal belongs, and so on.
  • the first query request message also includes indication information.
  • the instruction information may indicate that the query information includes information describing the rich media message applet required by the user corresponding to the rich media message terminal, or may instruct the rich media message application server to provide the rich media message applet, that is, indicate the rich media message applet.
  • the media messaging application server provides information about a rich media messaging applet that matches the query information or the rich media messaging application server provides a rich media messaging applet described by the querying information.
  • the indication information indicates that the first query request message is used to query the rich media messaging applet, that is, the rich media messaging application server can learn that the first query request message is used to query the rich media messaging applet based on the indication information.
  • the instruction information may also be called a rich media message applet query instruction (for example, recorded as a miniapp parameter), and its naming does not limit the scope of protection of the embodiments of the present application.
  • the first query request message includes the miniapp parameter
  • the first query request message is used to query the rich media message applet; if the first query request message does not include the miniapp parameter, the first query request Messages are used to query the chatbot.
  • the rich media message application server obtains the information of the rich media message applet.
  • the rich media message application server learns that the first query request message is used to query the rich media message applet based on the instruction information in the first query request message. Therefore, the rich media message application server knows based on the instruction information in the first query request message. Query information to obtain information about the rich media messaging applet that matches the query information.
  • the rich media messaging application server obtains the rich media messaging applet that meets the conditions based on the service content description or function description of the rich media messaging applet. For example, if the service content description or function description of the rich media messaging applet is used to instruct the query to book train tickets, the rich media messaging application server obtains the rich media related to booking train tickets based on the service content description or function description. Message applet.
  • the rich media message application server obtains a rich media message applet that satisfies the condition based on the language supported by the rich media message client. That is, the language of the rich media messaging applet matches the language supported by the rich media messaging client included in the query information.
  • the rich media message application server obtains the rich media message applet that satisfies the condition based on the version of the rich media message client. That is, the running version of the rich media messaging applet matches the version of the rich media messaging client included in the query information.
  • the rich media messaging application server obtains the rich media messaging applet that satisfies the condition based on the name of the provider of the rich media messaging applet. That is, the name of the provider of the rich media messaging applet matches the name of the provider of the rich media messaging applet included in the query information.
  • the rich media message application server obtains the information of the rich media message applet, including any of the following implementation methods.
  • the rich media message application server sends a second query request message to the applet management server, and the second query request message contains query information; the rich media message application server receives the second query response message from the applet management server. , the second query response message contains information about the rich media message applet.
  • the rich media message application server can generate a second query request message based on the query information in the first query request message, and send the second query request message to the applet management server.
  • the applet management server can determine the information of the rich media message applet that matches the query information based on the query information in the second query request message, and store the rich media message applet.
  • the program information is sent to the mini program management server.
  • the rich media message application server obtains the information of the rich media message applet locally based on the query information.
  • the rich media message application server can determine the information of the rich media message applet that matches the query information based on the query information in the first query request message.
  • the rich media message application server can obtain the information of the rich media message applet that matches the query information in the first query request message.
  • the method 600 further includes: the rich media message application server determines to allow the user corresponding to the rich media message terminal to use the rich media message applet.
  • the rich media message application server learns based on the indication information in the first query request message that the first query request message is used to query the rich media message server. program, you can first determine whether the user corresponding to the rich media messaging terminal is allowed to use the rich media messaging applet.
  • the rich media message application server determines that the user corresponding to the rich media message terminal is allowed to use the rich media message applet, the information of the rich media message applet that matches the query information is obtained based on any of the above implementation methods, or That is, the information of the rich media message applet described by the query information. If the rich media message application server determines that the user corresponding to the rich media message terminal is prohibited from using the rich media message applet, the rich media message application server may return a query failure or null to the rich media message terminal.
  • the rich media message application server determines to allow the user corresponding to the rich media message terminal to use the rich media message terminal based on the subscription information of the user corresponding to the rich media message terminal and/or the operator information to which the user corresponding to the rich media message terminal belongs.
  • Media messaging applet determines to allow the user corresponding to the rich media message terminal to use the rich media message terminal based on the subscription information of the user corresponding to the rich media message terminal and/or the operator information to which the user corresponding to the rich media message terminal belongs.
  • the rich media message application server sends a first query response message to the rich media message terminal.
  • the first query response message contains the information of the rich media message applet.
  • the rich media message terminal receives the first query response message.
  • the rich media message application server sends a first query response message to the rich media message terminal through the chat robot directory query interface.
  • the rich media message terminal receives the message from the rich media message application server through the chat robot directory query interface. The first query response message.
  • the method 600 also includes step 640: the rich media messaging terminal downloads and runs the rich media messaging applet according to the information of the rich media messaging applet.
  • the rich media message terminal sends a first query request message to the rich media message application server, where the first query request message contains query information.
  • the rich media message application server can obtain the rich media message applet that matches the query information based on the query information, that is, the rich media message applet described by the query information, and then provide the rich media message to the rich media message terminal.
  • Mini program information In this way, the rich media message terminal can download and run the rich media message applet based on the information of the rich media message applet, and then implement certain functions through the rich media message applet, simplify user operations, and improve user experience.
  • the information of the rich media messaging applet includes a download address of the rich media messaging applet.
  • the rich media message terminal or the rich media message client in the rich media message terminal
  • the information about the rich media messaging applet also includes at least one of the following: the identity of the rich media messaging applet, the name of the rich media messaging applet, the address of the icon of the rich media messaging applet, the address of the rich media messaging applet, and the address of the rich media messaging applet. Version.
  • the information of the rich media message applet may also include at least one of the following: provider information of the rich media message applet, or information of the rich media message applet itself.
  • the provider information of the rich media messaging applet may include, for example, at least one of the following: trademark, business type, contact information, and website.
  • the information about the rich media messaging applet itself may include, for example, at least one of the following: the purpose of the rich media messaging applet, information about the developer of the rich media messaging applet, and so on.
  • Figure 7 is a schematic diagram of a communication method 700 provided by an embodiment of the present application.
  • Method 700 may include the following steps.
  • the applet management server receives the first query request message from the rich media message terminal.
  • the rich media message terminal sends the first query request message to the applet management server.
  • the applet management server receives the first query request message from the rich media message terminal through the applet directory query interface. Accordingly, the rich media message terminal sends the first query request message to the applet management server through the applet directory query interface. A query request message.
  • the applet directory query interface represents the interface through which the rich media messaging terminal sends a request to the applet management server to obtain a list of rich media messaging applets. It can be understood that the name of the applet directory query interface does not limit the scope of protection of the embodiments of this application. That is, if the name of the interface changes in the future, the changed interface name will also be applicable to the embodiments of this application.
  • the first query request message includes query information.
  • query information please refer to the relevant description in method 600, which will not be described again here.
  • the applet management server obtains information about the rich media message applet based on the query information.
  • the rich media message applet is an applet with the rich media message client in the rich media message terminal as the host client.
  • the applet management server determines the information of the rich media message applet that matches the query information based on the query information in the first query request message.
  • the method 700 further includes: the applet management server determines that the user corresponding to the rich media messaging terminal is allowed to use the rich media messaging applet.
  • the applet management server may first determine whether the user corresponding to the rich media messaging terminal is allowed to use the rich media messaging applet. When the applet management server determines that the user corresponding to the rich media message terminal is allowed to use the rich media message applet, it then obtains the information of the rich media message applet that matches the query information, that is, the rich media message applet described in the query information. Media applet information. If the applet management server determines that the user corresponding to the rich media messaging terminal is prohibited from using the rich media messaging applet, the applet management server may return a query failure or null to the rich media messaging terminal.
  • the applet management server determines to allow the user corresponding to the rich media message terminal to use rich media based on the contract information of the user corresponding to the rich media message terminal and/or the operator information to which the user corresponding to the rich media message terminal belongs. Message applet.
  • the applet management server sends a first query response message to the rich media message terminal, where the first query response message contains information about the rich media message applet.
  • the rich media message terminal receives the first query response message.
  • the applet management server sends a first query response message to the rich media message terminal through the applet directory query interface, and accordingly, the rich media message terminal receives the first query response message through the applet directory query interface.
  • the method 700 also includes step 740: the rich media messaging terminal downloads and runs the rich media messaging applet according to the information of the rich media messaging applet.
  • the rich media message terminal can send a first query request message to the applet management server, where the first query request message contains query information.
  • the applet management server can obtain the rich media message applet that matches the query information based on the query information, that is, the rich media message applet described by the query information, and then provide the rich media message applet to the rich media message terminal.
  • Program information In this way, the rich media message terminal can download and run the rich media message applet based on the information of the rich media message applet, and then implement certain functions through the rich media message applet, simplify user operations, and improve user experience.
  • FIG 8 is a schematic flowchart of a communication method 800 provided according to an embodiment of the present application.
  • This method 800 can be used to implement the solution of the above method 600.
  • the rich media message application server is a MaaP platform.
  • the method 800 may include the following steps.
  • the rich media message terminal receives the query address.
  • the query address refers to the address where the rich media messaging terminal queries the rich media messaging applet, that is, the address where the rich media messaging terminal sends the first query request message.
  • the rich media messaging terminal can build a default message based on the mobile country code (MCC) and mobile network code (MNC) information in the international mobile subscriber identity (IMSI).
  • MCC mobile country code
  • MNC mobile network code
  • IMSI international mobile subscriber identity
  • the configuration server network domain name (such as a fully qualified domain name (fully qualified domain name, FQDN)).
  • the built configuration server network domain name is config.rcs.mnc.mcc.pub.3gppnetwork.org.
  • the rich media message terminal sends a message, such as an HTTP/HTTPS message, to the configuration server to request the configuration information of the rich media message terminal.
  • the configuration server sends the configuration information of the rich media message terminal to the rich media message terminal.
  • the configuration information includes the query address.
  • the query address is: CHATBOT DIRECTORY.
  • the rich media message terminal requests authentication (authorization) information from the BSF, and accordingly, the BSF sends the authentication information to the rich media message terminal.
  • the rich media message terminal sends the first query request message to the MaaP platform.
  • the rich media message terminal initiates a rich media message applet query request to the MaaP platform.
  • the rich media message terminal sends the first query request message to the MaaP platform through the Client to Service Provider Chatbot Directory interface.
  • the rich media message terminal may directly send the first query request message to the MaaP platform, that is, the first query request message may not pass through the rich media message center.
  • the rich media message terminal generates a first query request message based on the query address (such as CHATBOT DIRECTORY), path value botlist and query parameters received in step 801.
  • the query parameters may include query information and instruction information (such as miniapp parameters).
  • query information and instruction information please refer to the description in method 600, which will not be described again here.
  • the first query request message carries authentication information requested from the BSF.
  • the first query request message is in the following form:
  • the first query request message is in the following form:
  • the MaaP platform initiates user authentication to BSF.
  • the MaaP platform After receiving the first query request message, the MaaP platform can first initiate user authentication to the BSF, and the BSF authenticates the user.
  • BSF sends the authentication result to the MaaP platform.
  • the MaaP platform executes step 805.
  • step 803 and 804 are exemplary descriptions, and the embodiments of the present application are not limited thereto.
  • the MaaP platform can directly execute step 805.
  • the MaaP platform generates a second query request message based on the first query request message.
  • the MaaP platform may parse the first query request message and generate a second query request message based on the query parameters in the first query request message, that is, the query information in the query parameters.
  • MaaP locally configures the mini program management server address, such as https:// ⁇ MINIAPP DIRECTORY ⁇ .
  • the MaaP platform uses the address of the mini program management server, the path value of the mini program resource (such as miniapplist), and the first query request the query information in the message to generate a second query request message.
  • the second query request is of the form:
  • the query parameters in the second query request message may include the query information in the first query request message.
  • the MaaP platform determines that the first query request message is used to query the rich media message applet, the MaaP platform generates a second query request message based on the query information in the first query request message.
  • the MaaP platform may parse the first query request message to determine whether the first query request message is used to query the rich media message applet. For example, if the first query request message carries indication information (such as miniapp parameters), the MaaP platform determines that the first query request message is used to query the rich media message applet; if the first query request message does not carry indication information ( If miniapp parameter), the MaaP platform determines that the first query request message is used to query Chatbot. When the MaaP platform determines that the first query request message is to query a rich media message applet, the MaaP platform generates a second query request message based on the query information in the first query request message. In this way, the occurrence of the first query request can be avoided. When the message is used to query Chatbot, the MaaP platform generates a second query request message, which wastes signaling overhead.
  • indication information such as miniapp parameters
  • the MaaP platform determines that the user corresponding to the rich media message terminal is allowed to query the rich media message applet, the MaaP platform generates a second query request message based on the query information in the first query request message.
  • the MaaP platform can authenticate the rights of users corresponding to the rich media messaging terminal to use the rich media messaging applet business.
  • the MaaP platform determines whether to allow the user corresponding to the rich media message terminal to query rich media messages based on the subscription information of the user corresponding to the rich media message terminal and/or the operator information to which the user corresponding to the rich media message terminal belongs. Applets.
  • the MaaP platform determines that the user corresponding to the rich media message terminal is allowed to query the rich media message applet, the MaaP platform generates a second query request message based on the query information in the first query request message. In this way, banning rich media can be avoided.
  • the user corresponding to the message terminal queries the rich media message applet, but the MaaP platform generates a second query request message, which wastes signaling overhead.
  • the above two scenarios can be used alone or in combination.
  • the MaaP platform determines that the first query request message is used to query the rich media message applet, and allows the user corresponding to the rich media message terminal to query the rich media message applet, then Generate a second query request message according to the query information in the first query request message.
  • the MaaP platform sends a second query request message to the mini program management server.
  • the second query request message is an HTTP GET message (such as an HTTP GET request message).
  • the applet management server determines the rich media message applet based on the query information in the second query request message.
  • the applet management server parses the second query request message, and obtains a rich media message applet that meets the conditions based on the query information in the second query request message.
  • a rich media message applet that meets the conditions based on the query information in the second query request message.
  • the applet management server determines whether the user corresponding to the rich media message terminal is allowed to query the rich media message applet, that is, the applet management server performs permission authentication on the user corresponding to the rich media message terminal to use the rich media message applet service. In one possible implementation, the applet management server determines whether to allow the user corresponding to the rich media message terminal to query the rich media message terminal based on the contract information of the user corresponding to the rich media message terminal and/or the operator information to which the user corresponding to the rich media message terminal belongs. Media messaging applet.
  • the applet management server determines that the user corresponding to the rich media message terminal is allowed to query the rich media message applet, determines the rich media message applet that matches the query information based on the demand parameters in the second query request message, That is, the rich media message applet described by the query information.
  • the applet management server does not need to determine whether the user corresponding to the rich media messaging terminal is allowed to query the rich media messaging applet. For example, if the MaaP platform determines that the user corresponding to the rich media message terminal is allowed to query the rich media message applet, it will send a second query request message to the applet management server; if the applet management server receives the second query sent by the MaaP platform request a message, the applet management server can allow the user corresponding to the rich media message terminal to query the rich media message applet by default.
  • the MaaP platform determines that the user corresponding to the rich media message terminal is prohibited from querying the rich media message applet, it can directly return the query failure or empty result to the rich media message terminal, that is, there is no need to send a second query request message to the applet management server.
  • the applet management server sends rich media message applet information to the MaaP platform.
  • the applet management server sends 200OK to the MaaP platform, and the 200OK includes information about the rich media message applet.
  • the information of the rich media messaging applet may include basic information of the rich media messaging applet, and the basic information of the rich media messaging applet may include the download address of the rich media messaging applet.
  • the basic information of the rich media messaging applet also includes at least one of the following: the ID of the rich media messaging applet, the name of the rich media messaging applet, the address of the icon of the rich media messaging applet, the version of the rich media messaging applet, etc.
  • the basic information of the rich media message applet may also include at least one of the following: the number of returned query objects, the index of the first query result in the current query result set, the number of query objects, indicating the rich media message Whether the applet will be presented to the user as an authenticated rich media messaging applet.
  • the rich media message applet information sent by the applet management server to the MaaP platform is as follows:
  • the information of the rich media message applet may also include detailed information of the rich media message applet.
  • the detailed information of the rich media message applet includes at least one of the following: provider information of the rich media message applet, or rich media message applet information.
  • the provider information of the rich media messaging applet may include, for example, at least one of the following: trademark, business type, contact information, and website.
  • the information about the rich media messaging applet itself may include, for example, at least one of the following: the purpose of the rich media messaging applet, information about the developer of the rich media messaging applet, and so on.
  • the applet management server can simultaneously send the basic information of the rich media message applet and the detailed information of the rich media message applet to the MaaP platform, or the applet management server can also first send the rich media message applet to the MaaP platform. After receiving the request from the rich media message terminal (the request is used to request the detailed information of the rich media message applet), the detailed information of the rich media message applet is sent to the rich media message terminal through the MaaP platform.
  • the applet management server does not query the rich media messaging applet or the query fails, the result is empty.
  • the MaaP platform sends the information of the rich media message applet to the rich media message terminal.
  • the MaaP platform can send the information from the rich media messaging applet to the rich media messaging terminal. For example, the MaaP platform sends 200OK to the rich media messaging terminal, and the 200OK includes information about the rich media messaging applet.
  • Figure 9 is a schematic diagram of the query effect of the rich media message applet.
  • the query results of the rich media message terminal include two.
  • the first query result is: the name of the rich media messaging applet is applet xx, the ID of the rich media messaging applet is 1122331122, and the version of the rich media messaging applet is 1.1.
  • the first query result is: the name of the rich media messaging applet is applet zz, the ID of the rich media messaging applet is 1122331133, and the version of the rich media messaging applet is 1.1.
  • the query result also includes the download address of the rich media message applet.
  • the rich media message terminal (or the rich media message client in the rich media message) can download the rich media message applet based on the download address of the rich media message applet. Media message applet, and then run the rich media message applet. It can be understood that the applet in Figure 9 represents the rich media messaging applet.
  • the rich media message terminal downloads and runs the rich media message applet based on the information of the rich media message applet.
  • the rich media messaging terminal downloads the rich media messaging applet based on the download address of the rich media messaging applet and runs the rich media messaging applet.
  • the rich media message terminal that is, the rich media message client in the rich media message terminal, or the rich media message applet downloaded by the rich media message client
  • the server for example, it can be called a rich media message applet backend server
  • the ticket booking service can be realized through the rich media messaging applet.
  • the embodiment shown in Figure 8 mainly takes the separate deployment of the MaaP platform and the applet management device platform as an example for illustrative explanation, and is not limited to this.
  • the MaaP platform and the applet management device platform can also be co-located.
  • the MaaP platform after receiving the first query request message, the MaaP platform can directly obtain the information of the rich media message applet from the local, and send the determined rich media The information of the message applet is sent to the rich media message terminal.
  • steps 801-810 shown in Figure 8 exemplarily introduces the scenario where the rich media message terminal queries the applet management server for the rich media message applet through the MaaP platform.
  • This method 800 can be implemented through the architecture as shown in Figure 3 .
  • an applet management server is added to the rich media messaging system to store and manage applet information, and provide rich media messaging applet query services for rich media messaging terminals; store and manage rich media messaging applet packages, and Provides rich media message terminal download services for rich media message applet packages.
  • the mini program management server and the MaaP platform can be deployed on the same physical or virtual server, or on different physical or virtual servers, without restrictions.
  • the rich media message terminal carries indication information and query information in the first query request message, and the MaaP platform parses the first query request message, for example, based on the indication information in the first query request message, it determines that it is to query the rich media message applet, and for example A second query request message is generated according to the query information in the first query request message, and a request for querying the rich media message applet (ie, the second query request message) is sent to the applet management server.
  • the applet management server determines a qualified rich media message applet based on the second query request message, and sends the information of the rich media message applet to the MaaP platform, and the MaaP platform returns the information of the rich media message applet to the rich media Message terminal, so that the rich media message terminal can run the rich media message applet.
  • the rich media message terminal can discover the rich media message applet, and then use the rich media message applet to complete functions such as ticket purchasing and customer research, simplifying user operations, shortening the interaction process, and improving user experience.
  • the changes to the existing rich media messaging system are relatively small, which facilitates the promotion and application of the rich media messaging applet in the rich media messaging system.
  • FIG 10 is a schematic flowchart of a communication method 1000 provided according to another embodiment of the present application. This method 1000 can be used to implement the solution of the above method 700. The method 1000 may include the following steps.
  • the rich media message terminal receives the query address.
  • the query address refers to the address where the rich media messaging terminal queries the rich media messaging applet, that is, the address where the rich media messaging terminal sends the first query request message.
  • the rich media messaging terminal can construct a default configuration server network domain name (such as FQDN) based on the MCC and MNC information in the IMSI.
  • the built configuration server network domain name is config.rcs.mnc.mcc.pub.3gppnetwork.org.
  • the rich media message terminal sends a message, such as an HTTP/HTTPS message, to the configuration server to request the configuration information of the rich media message terminal.
  • the configuration server sends the configuration information to the rich media message terminal.
  • the configuration information includes query address information.
  • the query address information is: MINIAPP DIRECTORY.
  • the rich media message terminal requests authentication information from the BSF, and accordingly, the BSF sends the authentication information to the rich media message terminal.
  • the rich media message terminal sends the first query request message to the applet management server.
  • the rich media message terminal generates a first query request message based on the query address (such as MINIAPP DIRECTORY), path value miniapplist and query parameters received in step 1001.
  • the query parameters include query information.
  • query information please refer to the description in method 600, which will not be described again here.
  • the first query request message carries authentication information requested from the BSF.
  • the first query request message is in the following form:
  • the applet management server initiates user authentication to BSF.
  • the applet management server can first initiate user authentication to the BSF, and the BSF authenticates the user.
  • BSF sends the authentication result to the applet management server.
  • step 1005 After receiving the first query request message, the applet management server may directly execute step 1005.
  • the applet management server determines the rich media message applet based on the first query request message.
  • the applet management server may parse the first query request message, and obtain a rich media message applet that meets the conditions based on the query information in the first query request message.
  • the applet management server determines that the user corresponding to the rich media message terminal is allowed to query the rich media message applet
  • the applet management server determines the rich media message described in the query information based on the query information in the first query request message.
  • Media messaging applet
  • the applet management server can authenticate the rights of users corresponding to the rich media messaging terminal to use the rich media messaging applet service.
  • the applet management server determines whether to allow the user corresponding to the rich media message terminal to query the rich media message terminal based on the contract information of the user corresponding to the rich media message terminal and/or the operator information to which the user corresponding to the rich media message terminal belongs.
  • Media messaging applet When the applet management server determines that the user corresponding to the rich media message terminal is allowed to query the rich media message applet, the applet management server determines the rich media message applet based on the query information in the first query request message.
  • the applet management server sends the information of the rich media message applet to the rich media message terminal.
  • the applet management server sends 200OK to the rich media messaging terminal, where the 200OK includes information about the rich media messaging applet.
  • step 808 For information about the rich media message applet, please refer to the relevant description in step 808, which will not be described again here.
  • the applet management server can send the basic information of the rich media message applet and the detailed information of the rich media message applet to the rich media message terminal at the same time, or the applet management server can also send the rich media to the rich media message terminal first.
  • the basic information of the message applet after receiving the request from the rich media message terminal (the request is used to request the detailed information of the rich media message applet), then sends the detailed information of the rich media message applet to the rich media message terminal.
  • the applet management server does not query the rich media messaging applet or the query fails, the result is empty.
  • the rich media message terminal downloads and runs the rich media message applet based on the information of the rich media message applet.
  • the rich media message terminal runs the rich media message applet, and then realizes certain business functions through the rich media message applet, such as realizing service discovery, search, interaction, payment and other business functions through the rich media message applet.
  • certain business functions such as realizing service discovery, search, interaction, payment and other business functions through the rich media message applet.
  • the ticket booking service can be realized through the rich media messaging applet.
  • Step 1007 is similar to step 810 and will not be described again here.
  • the applet management server can store and manage the rich media message applet information, and provide the rich media message applet query service for the rich media message terminal; the applet management server can also store and manage the rich media message applet package. , and provide download services for rich media message applet packages for rich media message terminals.
  • the rich media message terminal carries the query information in the first query request message, and the applet management server determines the rich media message applet that meets the conditions based on the query information, and returns the information of the rich media message applet to the rich media message terminal.
  • the rich media message terminal can discover the rich media message applet, and then use the rich media message applet to complete functions such as ticket purchasing and customer research, simplifying user operations, shortening the interaction process, and improving user experience.
  • each step in the above-mentioned FIG. 8 and FIG. 10 is only an exemplary description and is not strictly limited.
  • the size of the serial numbers of the above-mentioned processes does not mean the order of execution.
  • the execution order of each process should be determined by its functions and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present application.
  • the methods and operations implemented by the device can also be implemented by components of the device (such as chips or circuits), without limitation.
  • embodiments of the present application also provide corresponding devices, and the devices include modules for executing corresponding modules in each of the above method embodiments.
  • the module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above method embodiments are also applicable to the following device embodiments.
  • FIG 11 is a schematic diagram of a communication device 1100 provided by an embodiment of the present application.
  • the device 1100 includes a transceiver unit 1110 and a processing unit 1120.
  • the transceiver unit 1110 may be used to implement corresponding communication functions.
  • the transceiver unit 1110 may also be called a communication interface or communication unit.
  • the processing unit 1120 may be used to perform processing operations, such as generating query messages, running rich media message applets, etc.
  • the device 1100 also includes a storage unit, which can be used to store instructions and/or data, and the processing unit 1120 can read the instructions and/or data in the storage unit, so that the device implements each of the foregoing method embodiments. actions of core network equipment or user equipment.
  • the device 1100 can be the rich media message application server in the aforementioned embodiments (the rich media message application server in Figure 6, the MaaP platform in Figure 8), or it can be the rich media message application server components (such as chips).
  • the device 1100 can implement steps or processes corresponding to those executed by the rich media message application server in the above method embodiment.
  • the transceiver unit 1110 may be used to perform operations related to the transceiver of the rich media message application server in the above method embodiment (such as operations of sending and/or receiving data or messages).
  • the transceiver unit 1110 may be used to perform the steps in Figure 6
  • the operation of receiving the first query request message from the rich media message terminal in step 610 and the operation of sending the first query response message to the rich media message terminal in step 630 can also be used to perform the sending and/or receiving of the MaaP platform in Figure 8 Operations on data or messages.
  • the processing unit 1120 may be configured to perform operations related to processing of the rich media message application server in the above method embodiments, or operations other than sending and receiving (such as operations other than sending and/or receiving data or messages), for example, the processing unit 1120 It can be used to obtain the information of the rich media message applet according to the first query request message.
  • the processing unit 1120 may be configured to perform the operation in step 805 in FIG. 8 .
  • the transceiver unit 1110 is configured to receive a first query request message from a rich media message terminal.
  • the first query request message includes query information, and the query information includes a description of the user's needs corresponding to the rich media message terminal.
  • the information of the rich media message applet, the rich media message applet is an applet with the rich media message client in the rich media message terminal as the host client;
  • the processing unit 1120 is configured to respond to the first query request message, obtain the rich media The information of the message applet;
  • the transceiving unit 1110 is also used to send a first query response message to the rich media message terminal, where the first query response message contains the information of the rich media message applet.
  • the transceiver unit 1110 is also configured to send a second query request message to the applet management server, where the second query request message contains query information; and receive a second query response message from the applet management server, where the second query response message Contains information for the rich media messaging applet.
  • the processing unit 1120 is specifically configured to obtain the information of the rich media messaging applet locally based on the query information.
  • processing unit 1120 is also used to determine whether the user is allowed to use the rich media messaging applet.
  • the processing unit 1120 is specifically configured to determine whether the user is allowed to use the rich media messaging applet based on the user's subscription information and/or the information of the operator to which the user belongs.
  • the query information includes at least one of the following or a keyword contained in at least one of the following: the name of the rich media messaging applet, the type of the rich media messaging applet, the name of the provider of the rich media messaging applet, the rich media The service content description or function description of the message applet, the language supported by the rich media messaging client, or the version of the rich media messaging client.
  • the information of the rich media messaging applet includes the download address of the rich media messaging applet.
  • the information of the rich media messaging applet includes at least one of the following: an identifier of the rich media messaging applet, a name of the rich media messaging applet, an address of an icon of the rich media messaging applet, or a version of the rich media messaging applet .
  • the rich media message application server is a message as a platform MaaP or a chatbot Chatbot platform
  • the rich media message terminal communicates with the rich media message application server through a chatbot directory query interface.
  • the transceiver unit 1110 is specifically configured to receive the first query request message through the chat robot directory query interface; and send the first query response message through the chat robot directory query interface.
  • the first query request message also includes instruction information, and the instruction information instructs the rich media message application server to provide information about the rich media message applet based on the query information.
  • the device 1100 may be the rich media message terminal in the aforementioned embodiments (the rich media message terminal in Figures 6, 7, 8, and 10), or it may be a rich media message terminal. Components (such as chips).
  • the device 1100 can implement steps or processes corresponding to those executed by the rich media message terminal in the above method embodiment.
  • the transceiver unit 1110 may be used to perform operations related to the transceiver of the rich media message terminal in the above method embodiment (such as operations of sending and/or receiving data or messages).
  • the transceiver unit 1110 may be used to perform step 610 in Figure 6
  • the operation of sending the first query request message to the rich media message application server in step 630 and the operation of receiving the first query response message from the rich media message application server in step 630 can also be used to execute the applet in step 710 in Figure 7
  • the operation of the management server sending the first query request message and the operation of receiving the first query response message from the applet management server in step 730 can also be used to perform the rich media message terminal in Figure 8 to send and/or receive data or messages.
  • the operation can also be used to perform the operation of the rich media message terminal in Figure 10 to send and/or receive data or messages.
  • the processing unit 1120 may be used to perform operations related to data and/or information processing of the rich media message terminal in the above method embodiments, or operations other than transceiving (such as operations other than sending and/or receiving data or messages), for example , the processing unit 1120 may be used to perform the operation of step 640 in FIG. 6, and may also be used to perform the operation of step 740 in FIG. 7, and may also be used to perform the operation of step 810 in FIG. 8, and may also be used to perform the operation of FIG. The operation of step 1007 in 10.
  • the transceiver unit 1110 is configured to send a first query request message to the rich media message application server.
  • the first query request message contains query information, and the query information is used to describe what the user corresponding to the rich media message terminal needs.
  • Information about the rich media message applet is an applet with the rich media message client in the rich media message terminal as the host client; the transceiver unit 1110 is also used to receive the first message from the rich media message application server.
  • Query response message the first query response message contains information about the rich media messaging applet; the processing unit 1120 is configured to download and run the rich media messaging applet according to the information about the rich media messaging applet.
  • the query information includes at least one of the following: the name of the rich media messaging applet, the type of the rich media messaging applet, the name of the rich media messaging applet provider, the keywords of the content or function description of the rich media messaging applet, The language supported by the rich media messaging client, or the version of the rich media messaging client.
  • the information of the rich media messaging applet includes the download address of the rich media messaging applet.
  • the information of the rich media messaging applet includes at least one of the following: an identifier of the rich media messaging applet, a name of the rich media messaging applet, an address of an icon of the rich media messaging applet, or a version of the rich media messaging applet .
  • the rich media message application server is a message as a platform MaaP or a chatbot Chatbot platform
  • the rich media message terminal communicates with the rich media message application server through a chatbot directory query interface.
  • the transceiver unit 1110 is specifically configured to send the first query request message through the chat robot directory query interface; and receive the first query response message through the chat robot directory query interface.
  • the first query request message also includes instruction information, and the instruction information instructs the rich media message application server to provide information about the rich media message applet based on the query information.
  • the transceiver unit 1110 is used to send a first query request message to the applet management server.
  • the first query request message contains query information, and the query information is used to describe what the user corresponding to the rich media message terminal needs.
  • Information about the rich media message applet is an applet with the rich media message client in the rich media message terminal as the host client; the transceiver unit 1110 is also used to receive the first query from the applet management server. response message, the first query response message contains the information of the rich media messaging applet; the processing unit 1120 is configured to download and run the rich media messaging applet according to the information of the rich media messaging applet.
  • the query information includes at least one of the following or a keyword contained in at least one of the following: the name of the rich media messaging applet, the type of the rich media messaging applet, the name of the provider of the rich media messaging applet, the rich media The service content description or function description of the message applet, the language supported by the rich media messaging client, or the version of the rich media messaging client.
  • the information of the rich media messaging applet includes the download address of the rich media messaging applet.
  • the information of the rich media messaging applet includes at least one of the following: an identifier of the rich media messaging applet, a name of the rich media messaging applet, an address of an icon of the rich media messaging applet, or a version of the rich media messaging applet .
  • the rich media message terminal communicates with the applet management server through the applet directory query interface.
  • the transceiver unit 1110 is specifically configured to send the first query request message through the applet directory query interface; and receive the first query response message through the applet directory query interface.
  • the device 1100 may be the applet management server in the aforementioned embodiment, or may be a component (such as a chip) of the applet management server.
  • the device 1100 can implement steps or processes corresponding to those executed by the applet management server in the above method embodiment.
  • the transceiver unit 1110 may be used to perform transceiver-related operations (such as operations of sending and/or receiving data or messages) of the applet management server in the above method embodiment.
  • the transceiver unit 1110 may be used to perform step 710 in Figure 7
  • the operation of receiving the first query request message from the rich media message terminal in step 730 and the operation of sending the first query response message to the rich media message terminal in step 730 can also be used to perform the sending and processing of the applet management server in Figures 8 and 10 /or the operation of receiving data or messages.
  • the processing unit 1120 may be used to perform operations related to processing of the applet management server in the above method embodiments, or operations other than sending and receiving (such as operations other than sending and/or receiving data or messages).
  • the processing unit 1120 may In addition to performing the operation of step 730 in Figure 7, it can also be used to perform the operation of step 807 in Figure 8, and can also be used to perform the operation of step 1005 in Figure 10.
  • the transceiver unit 1110 is configured to receive a first query request message from a rich media message terminal.
  • the first query request message includes query information, and the query information includes a description of the user's needs corresponding to the rich media message terminal.
  • the information of the rich media message applet, the rich media message applet is an applet with the rich media message client in the rich media message terminal as the host client;
  • the processing unit 1120 is used to obtain the rich media message applet according to the query information Information;
  • the transceiver unit 1110 is also configured to send a first query response message to the rich media message terminal, where the first query response message contains information about the rich media message applet.
  • processing unit 1120 is also used to determine whether the user is allowed to use the rich media messaging applet.
  • the processing unit 1120 is specifically configured to determine whether the user is allowed to use the rich media messaging applet based on the user's subscription information and/or the information of the operator to which the user belongs.
  • the query information includes at least one of the following or a keyword contained in at least one of the following: the name of the rich media messaging applet, the type of the rich media messaging applet, the name of the provider of the rich media messaging applet, the rich media The service content description or function description of the message applet, the language supported by the rich media messaging client, or the version of the rich media messaging client.
  • the information of the rich media messaging applet includes the download address of the rich media messaging applet.
  • the information of the rich media messaging applet includes at least one of the following: an identifier of the rich media messaging applet, a name of the rich media messaging applet, an address of an icon of the rich media messaging applet, or a version of the rich media messaging applet .
  • the rich media message terminal communicates with the applet management server through the applet directory query interface.
  • the transceiver unit 1110 is specifically configured to receive the first query request message through the applet directory query interface; and send the first query response message through the applet directory query interface.
  • the device 1100 here is embodied in the form of a functional unit.
  • the term "unit” as used herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor, or a group of processors) used to execute one or more software or firmware programs. processor, etc.) and memory, merged logic circuitry, and/or other suitable components to support the described functionality.
  • ASIC application specific integrated circuit
  • processor such as a shared processor, a proprietary processor, or a group of processors
  • memory merged logic circuitry, and/or other suitable components to support the described functionality.
  • the device 1100 can be specifically the rich media message application server in the above embodiment (the rich media message application server in Figure 6, the MaaP platform in Figure 8), or Used to execute various processes and/or steps corresponding to the rich media message application server in the above method embodiments, for example, steps 610-630 in Figure 6, steps 803-806, 808, and 809 in Figure 8.
  • the device 1100 may be specifically a rich media message terminal in the above embodiments (such as the rich media message terminal in Figure 6, Figure 7, Figure 8, and Figure 10), which can be used to perform the rich media messaging in the above method embodiments.
  • the device 1100 can be specifically the applet management server in the above embodiments, and can be used to execute various processes and/or steps corresponding to the applet management server in the above method embodiments, for example, steps 710-710 in Figure 7 730, steps 806-808 in Figure 8, steps 1002-1006 in Figure 10. To avoid repetition, they will not be repeated here.
  • the device 1100 of each of the above solutions has the function of implementing the corresponding steps performed by the rich media message application server (rich media message application server in Figure 6, MaaP platform in Figure 8) in the above method, or, the device 1100 of each of the above solutions Have the function of implementing the corresponding steps performed by the rich media message terminal (such as the rich media message terminal in Figure 6, Figure 7, Figure 8, and Figure 10) in the above method, or the device 1100 of each of the above solutions has the function of implementing the applet in the above method Functions that manage the corresponding steps performed by the server.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiving unit. (machine replacement), other units, such as processing units, etc., can be replaced by processors to respectively perform the sending and receiving operations and related processing operations in each method embodiment.
  • transceiver unit 1110 may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.
  • the device in Figure 11 can be the device in the aforementioned embodiment, or it can be a chip or a chip system, such as a system on chip (SoC).
  • the transceiver unit may be an input-output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip. No limitation is made here.
  • FIG. 12 is a schematic diagram of another communication device 1200 according to an embodiment of the present application.
  • the device 1200 includes a processor 1210.
  • the processor 1210 is configured to execute computer programs or instructions stored in the memory 1220, or read data stored in the memory 1220, to perform the methods in each of the above method embodiments.
  • the device 1200 further includes a memory 1220, which is used to store computer programs or instructions and/or data.
  • the memory 1220 may be integrated with the processor 1210, or may be provided separately.
  • the device 1200 also includes a transceiver 1230, which is used for receiving and/or transmitting signals.
  • the processor 1210 is used to control the transceiver 1230 to receive and/or transmit signals.
  • the device 1200 is used to implement the operations performed by the rich media message application server (the rich media message application server in Figure 6, the MaaP platform in Figure 8) in each of the above method embodiments.
  • the device 1200 is used to implement the operations performed by the rich media message terminal (the rich media message terminal in Figure 6, Figure 7, Figure 8, and Figure 10) in each of the above method embodiments.
  • the device 1200 is used to implement the operations performed by the applet management server in each of the above method embodiments.
  • processors mentioned in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processor, digital signal processor (DSP), application-specific integrated circuit ( application specific integrated circuit (ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • FPGA off-the-shelf programmable gate array
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM). For example, RAM can be used as an external cache.
  • RAM includes the following forms: static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), Double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) and direct Memory bus random access memory (direct rambus RAM, DR RAM).
  • the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component
  • the memory storage module
  • memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.
  • Embodiments of the present application also provide a computer-readable storage medium on which is stored a rich media message application server (such as the rich media message application server in Figure 6, the MaaP platform in Figure 8) used to implement the above method embodiments. ) computer instructions for performing a method.
  • a rich media message application server such as the rich media message application server in Figure 6, the MaaP platform in Figure 8
  • Embodiments of the present application also provide a computer-readable storage medium on which is stored a rich media message terminal used to implement the above method embodiments (such as the rich media message terminal in Figures 6, 7, 8, and 10). ) computer instructions for performing a method.
  • a rich media message terminal used to implement the above method embodiments (such as the rich media message terminal in Figures 6, 7, 8, and 10).
  • Embodiments of the present application also provide a computer-readable storage medium on which computer instructions for implementing the methods executed by the applet management server in each of the above method embodiments are stored.
  • Embodiments of the present application also provide a computer program product, which includes instructions.
  • the instructions When the instructions are executed by a computer, the instructions are implemented by a rich media message application server in the above method embodiments (such as the rich media message application server in Figure 6, the rich media message application server in Figure 8 MaaP platform) implementation method.
  • Embodiments of the present application also provide a computer program product, which includes instructions. When executed by a computer, the instructions are used to implement the rich media message terminal (as shown in Figures 6, 7, 8, and 10) in each of the above method embodiments. Media message terminal) execution method.
  • Embodiments of the present application also provide a computer program product, which includes instructions that, when executed by a computer, implement the methods executed by the applet management server in each of the above method embodiments.
  • Embodiments of the present application also provide a communication system, including the aforementioned rich media message application server (rich media message application server in Figure 6, MaaP platform in Figure 8), rich media message terminal (Figure 6, Figure 7 , the rich media message terminal in Figures 8 and 10) and at least one of the applet management server.
  • rich media message application server rich media message application server in Figure 6, MaaP platform in Figure 8
  • rich media message terminal Figure 6, Figure 7 , the rich media message terminal in Figures 8 and 10
  • applet management server at least one of the applet management server.
  • the disclosed devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device.
  • the computer may be a personal computer, a server, or a network device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means.
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated.
  • the available media may be magnetic media (such as floppy disks, hard disks, magnetic tapes), optical media (such as DVDs), or semiconductor media (such as solid state disks (SSD)), etc.
  • the aforementioned available media include but Not limited to: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种通信方法、装置以及系统。该通信方法包括：富媒体消息应用服务器接收来自富媒体消息终端的第一查询请求消息，第一查询请求消息包含查询信息，查询信息包含用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；响应于第一查询请求，富媒体消息应用服务器获取富媒体消息小程序的信息；富媒体消息应用服务器向富媒体消息终端发送第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息。富媒体消息终端根据富媒体消息小程序的信息可下载并运行富媒体消息小程序，进而通过该富媒体消息小程序实现某些功能，简化用户操作，提升用户体验。

Description

通信方法、装置以及系统
本申请要求于2022年05月26日提交中国专利局、申请号为202210579914.2、申请名称为“通信方法、装置以及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信领域，尤其涉及一种通信方法、装置以及系统。
背景技术
富媒体通信套件(rich communication suite，RCS)技术引入聊天机器人(Chatbot)服务，实现“消息即服务”。具体来说，通信技术与互联网技术、人工智能融合，带来全新人机交互模式，用户在消息窗口内就能完成服务发现、搜索、交互、支付等一站式的业务体验，极大提升运营商行业消息的价值。按照目前的富媒体通信技术，用户与聊天机器人需要多次交互，才可以完成一个业务流程，操作繁琐，交互过程长，影响用户体验。
发明内容
本申请实施例提供一种通信方法、装置以及系统，能够简化用户操作，提升用户体验。
第一方面，提供了一种通信方法，该方法可以由富媒体消息应用服务器执行，或者，也可以由富媒体消息应用服务器的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法可以包括：富媒体消息应用服务器接收来自富媒体消息终端的第一查询请求消息，第一查询请求消息包含查询信息，查询信息包含用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；响应于第一查询请求消息，富媒体消息应用服务器获取富媒体消息小程序的信息，以及向富媒体消息终端发送第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息。
基于上述技术方案，富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息，该第一查询请求消息包含查询信息，查询信息包含用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息。这样，富媒体消息应用服务器可基于该查询信息获取与该查询信息相匹配的富媒体消息小程序，进而向富媒体消息终端提供富媒体消息小程序的信息。这样，富媒体消息终端可根据富媒体消息小程序的信息下载并运行富媒体消息小程序，进而通过该富媒体消息小程序实现某些功能，简化用户操作，提升用户体验。
结合第一方面，在第一方面的某些实现方式中，富媒体消息应用服务器获取富媒体消息小程序的信息，包括：富媒体消息应用服务器向小程序管理服务器发送第二查询请求消息，第二查询请求消息包含查询信息；富媒体消息应用服务器接收来自小程序管理服务器的第二查询响应消息，第二查询响应消息包含富媒体消息小程序的信息。
基于上述技术方案，富媒体消息应用服务器可基于第一查询请求消息中的查询信息，生成第二查询请求消息，并向小程序管理服务器发送该第二查询请求消息。小程序管理服务器收到该第二查询请求消息后，可以基于该第二查询请求消息中的查询信息，确定与该查询信息相匹配的富媒体消息小程序的信息，并将该富媒体消息小程序的信息发送给小程序管理服务器。
结合第一方面，在第一方面的某些实现方式中，富媒体消息应用服务器获取富媒体消息小程序的信息，包括：富媒体消息应用服务器根据查询信息，从本地获取富媒体消息小程序的信息。
基于上述技术方案，富媒体消息应用服务器可自身确定富媒体消息小程序的信息。
结合第一方面，在第一方面的某些实现方式中，在富媒体消息应用服务器获取富媒体消息小程序的信息之前，方法还包括：富媒体消息应用服务器确定允许用户使用富媒体消息小程序。
基于上述技术方案，富媒体消息应用服务器收到富媒体消息终端发送的第一查询请求消息后，可先判断是否允许该富媒体消息终端对应的用户使用富媒体消息小程序。在富媒体消息应用服务器确定允许该富媒体消息终端对应的用户使用富媒体消息小程序的情况下，再获取富媒体消息小程序的信息。
结合第一方面，在第一方面的某些实现方式中，富媒体消息应用服务器确定允许用户使用富媒体消息小程序，包括：富媒体消息应用服务器根据用户的签约信息和/或用户所属的运营商的信息，确定允许用户使用富媒体消息小程序。
结合第一方面，在第一方面的某些实现方式中，富媒体消息应用服务器为消息即平台MaaP或聊天机器人Chatbot平台，富媒体消息终端与富媒体消息应用服务器通过聊天机器人目录查询接口通信。
结合第一方面，在第一方面的某些实现方式中，富媒体消息应用服务器接收来自富媒体消息终端的第一查询请求消息，包括：富媒体消息应用服务器通过聊天机器人目录查询接口接收第一查询请求消息；富媒体消息应用服务器向富媒体消息终端发送第一查询响应消息，包括：富媒体消息应用服务器通过聊天机器人目录查询接口发送第一查询响应消息。
基于上述技术方案，富媒体消息终端可通过聊天机器人目录查询接口查询富媒体消息小程序，无需增加额外的配置参数、引入额外的接口安全认证流程，可以提升富媒体消息终端的配置效率和启动效率；此外，无需增加额外的用户身份认证流程，可以提升富媒体消息系统的资源利用率。
结合第一方面，在第一方面的某些实现方式中，第一查询请求消息还包含指示信息，指示信息指示富媒体消息应用服务器根据查询信息提供富媒体消息小程序的信息。
第二方面，提供了一种通信方法，该方法可以由富媒体消息终端执行，或者，也可以由富媒体消息终端的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法可以包括：富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息，第一查询请求消息包含查询信息，查询信息用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；富媒体消息终端接收来自富媒体消息应用服务器的第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息；富媒体消息终端根据富媒体消息 小程序的信息下载并运行富媒体消息小程序。
结合第二方面，在第二方面的某些实现方式中，富媒体消息应用服务器为消息即平台MaaP或聊天机器人Chatbot平台，富媒体消息终端与富媒体消息应用服务器通过聊天机器人目录查询接口通信。
结合第二方面，在第二方面的某些实现方式中，富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息，包括：富媒体消息终端通过聊天机器人目录查询接口发送第一查询请求消息；富媒体消息终端接收来自富媒体消息应用服务器的第一查询响应消息，包括：富媒体消息终端通过聊天机器人目录查询接口接收第一查询响应消息。
结合第二方面，在第二方面的某些实现方式中，第一查询请求消息还包含指示信息，指示信息指示富媒体消息应用服务器根据查询信息提供富媒体消息小程序的信息。
第二方面及各个可能的设计的有益效果可以参考第一方面相关的描述，在此不予赘述。
第三方面，提供了一种通信方法，该方法可以由小程序管理服务器执行，或者，也可以由小程序管理服务器的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法可以包括：小程序管理服务器接收来自富媒体消息终端的第一查询请求消息，第一查询请求消息包含查询信息，查询信息包含用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；小程序管理服务器根据查询信息获取富媒体消息小程序的信息；小程序管理服务器向富媒体消息终端发送第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息。
基于上述技术方案，富媒体消息终端可向小程序管理服务器发送第一查询请求消息，该第一查询请求消息包含查询信息。这样，小程序管理服务器可基于该查询信息获取与该查询信息相匹配的富媒体消息小程序，进而向富媒体消息终端提供富媒体消息小程序的信息。这样，富媒体消息终端可根据富媒体消息小程序的信息下载并运行富媒体消息小程序，进而通过该富媒体消息小程序实现某些功能，简化用户操作，提升用户体验。
结合第三方面，在第三方面的某些实现方式中，在小程序管理服务器根据查询信息获取富媒体消息小程序的信息之前，方法还包括：小程序管理服务器确定允许用户使用富媒体消息小程序。
结合第三方面，在第三方面的某些实现方式中，小程序管理服务器确定允许用户使用富媒体消息小程序，包括：小程序管理服务器根据用户的签约信息和/或用户所属的运营商的信息，确定允许用户使用富媒体消息小程序。
基于上述技术方案，小程序管理服务器收到富媒体消息终端发送的第一查询请求消息后，可先判断是否允许该富媒体消息终端对应的用户使用富媒体消息小程序。在小程序管理服务器确定允许该富媒体消息终端对应的用户使用富媒体消息小程序的情况下，再获取富媒体消息小程序的信息。
结合第三方面，在第三方面的某些实现方式中，富媒体消息终端与小程序管理服务器通过小程序目录查询接口通信。
结合第三方面，在第三方面的某些实现方式中，小程序管理服务器接收来自富媒体消息终端的第一查询请求消息，包括：小程序管理服务器通过小程序目录查询接口接收第一 查询请求消息；小程序管理服务器向富媒体消息终端发送第一查询响应消息，包括：小程序管理服务器通过小程序目录查询接口发送第一查询响应消息。
第四方面，提供了一种通信方法，该方法可以由富媒体消息终端执行，或者，也可以由富媒体消息终端的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法可以包括：富媒体消息终端向小程序管理服务器发送第一查询请求消息，第一查询请求消息包含查询信息，查询信息用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；富媒体消息终端接收来自小程序管理服务器的第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息；富媒体消息终端根据富媒体消息小程序的信息下载并运行富媒体消息小程序。
结合第四方面，在第四方面的某些实现方式中，富媒体消息终端与小程序管理服务器通过小程序目录查询接口通信。
结合第四方面，在第四方面的某些实现方式中，富媒体消息终端向小程序管理服务器发送第一查询请求消息，包括：富媒体消息终端通过小程序目录查询接口发送第一查询请求消息；富媒体消息终端接收来自小程序管理服务器的第一查询响应消息，包括：富媒体消息终端通过小程序目录查询接口接收第一查询响应消息。
第四方面及各个可能的设计的有益效果可以参考第三方面相关的描述，在此不予赘述。
第五方面，提供了一种通信方法，该方法可以由富媒体消息应用服务器和富媒体消息终端执行，或者，也可以由富媒体消息应用服务器的组成部件(例如芯片或者电路)和富媒体消息终端的组成部件(例如芯片或者电路)执行，对此不作限定。
该方法可以包括：富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息，第一查询请求消息包含查询信息，查询信息用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；富媒体消息应用服务器接收第一查询请求消息，并响应于第一查询请求消息，获取富媒体消息小程序的信息，以及向富媒体消息终端发送第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息；富媒体消息终端接收第一查询响应消息，并根据富媒体消息小程序的信息下载并运行富媒体消息小程序。
其中，关于富媒体消息应用服务器可参考第一方面中的描述，关于富媒体消息终端可参考第二方面中的描述，在此不予赘述。
结合第五方面，在第五方面的某些实现方式中，富媒体消息应用服务器为消息即平台MaaP或聊天机器人Chatbot平台，富媒体消息终端与富媒体消息应用服务器通过聊天机器人目录查询接口通信。
结合第五方面，在第五方面的某些实现方式中，富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息，富媒体消息应用服务器接收第一查询请求消息，包括：富媒体消息终端通过聊天机器人目录查询接口发送第一查询请求消息，富媒体消息应用服务器通过聊天机器人目录查询接口接收第一查询请求消息；富媒体消息应用服务器向富媒体消息终端发送第一查询响应消息，富媒体消息终端接收第一查询响应消息，包括：富媒体消息应用服务器通过聊天机器人目录查询接口发送第一查询响应消息，富媒体消息终端通过 聊天机器人目录查询接口接收第一查询响应消息。
结合第五方面，在第五方面的某些实现方式中，第一查询请求消息还包含指示信息，指示信息指示富媒体消息应用服务器根据查询信息提供富媒体消息小程序的信息。
第五方面的有益效果可以参考第一方面相关的描述，在此不予赘述。
结合第一方面至第五方面，在某些实现方式中，查询信息包括以下至少一项或以下至少一项所包含的关键字：富媒体消息小程序的名称、富媒体消息小程序的类型、富媒体消息小程序的提供商的名称、富媒体消息小程序的服务内容描述或功能描述、富媒体消息客户端支持的语言、或富媒体消息客户端的版本。
结合第一方面至第五方面，在某些实现方式中，富媒体消息小程序的信息包括富媒体消息小程序的下载地址。
结合第一方面至第五方面，在某些实现方式中，富媒体消息小程序的信息包括以下至少一项：富媒体消息小程序的标识、富媒体消息小程序的名称、富媒体消息小程序的图标的地址、或富媒体消息小程序的版本。
第六方面，提供一种通信装置，该装置用于执行上述第一方面至第五方面任一种可能实现方式中的方法。具体地，该装置可以包括用于执行第一方面至第五方面任一种可能实现方式中的方法的单元和/或模块，如处理单元和/或通信单元。
在一种实现方式中，该装置为通信设备(如富媒体消息应用服务器，又如富媒体消息终端，又如小程序管理服务器)。当该装置为通信设备时，通信单元可以是收发器，或，输入/输出接口；处理单元可以是至少一个处理器。可选地，收发器可以为收发电路。可选地，输入/输出接口可以为输入/输出电路。
在另一种实现方式中，该装置为用于通信设备(如富媒体消息应用服务器，又如富媒体消息终端，又如小程序管理服务器)的芯片、芯片系统或电路。当该装置为用于通信设备的芯片、芯片系统或电路时，通信单元可以是该芯片、芯片系统或电路上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等；处理单元可以是至少一个处理器、处理电路或逻辑电路等。
第七方面，提供一种通信装置，该装置包括：至少一个处理器，用于执行存储器存储的计算机程序或指令，以执行上述第一方面至第五方面任一种可能实现方式中的方法。可选地，该装置还包括存储器，用于存储的计算机程序或指令。可选地，该装置还包括通信接口，处理器通过通信接口读取存储器存储的计算机程序或指令。
在一种实现方式中，该装置为通信设备(如富媒体消息应用服务器，又如富媒体消息终端，又如小程序管理服务器)。
在另一种实现方式中，该装置为用于通信设备(如富媒体消息应用服务器，又如富媒体消息终端，又如小程序管理服务器)的芯片、芯片系统或电路。
第八方面，提供一种处理器，用于执行上述各方面提供的方法。
对于处理器所涉及的发送和获取/接收等操作，如果没有特殊说明，或者，如果未与其在相关描述中的实际作用或者内在逻辑相抵触，则可以理解为处理器输出和接收、输入等操作，也可以理解为由射频电路和天线所进行的发送和接收操作，本申请对此不做限定。
第九方面，提供一种计算机可读存储介质，该计算机可读介质存储用户设备执行的程序代码，该程序代码包括用于执行上述第一方面至第五方面任一种可能实现方式中的方 法。
第十方面，提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，使得计算机执行上述第一方面至第五方面任一种可能实现方式中的方法。
第十一方面，提供一种通信系统，包括前述的富媒体消息应用服务器、富媒体消息终端、小程序管理服务器中的至少一项。
附图说明
图1是适用于本申请实施例的一通信系统的示意图。
图2是适用于本申请实施例的另一通信系统的示意图。
图3是适用于本申请实施例的另一通信系统的示意图。
图4是适用于本申请实施例的另一通信系统的示意图。
图5示出了用户订票的一示意图。
图6是本申请实施例提供的一种通信方法600的示意图。
图7是本申请实施例提供的一种通信方法700的示意图。
图8是根据本申请一实施例提供的通信方法800的示意性流程图。
图9示出了富媒体小程序查询效果的示意图。
图10是根据本申请另一实施例提供的通信方法1000的示意性流程图。
图11是本申请实施例提供的一种通信装置1100的示意性图。
图12是本申请实施例提供另一种通信装置1200的示意图。
具体实施方式
下面将结合附图，对本申请实施例中的技术方案进行描述。
本申请实施例的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)或新无线(new radio，NR)系统。本申请提供的技术方案还可以应用于未来的通信系统，如第六代移动通信系统。本申请提供的技术方案还可以应用于设备到设备(device to device，D2D)通信，车到万物(vehicle-to-everything，V2X)通信，机器到机器(machine to machine，M2M)通信，机器类型通信(machine type communication，MTC)，以及物联网(internet of things，IoT)通信系统或者其他通信系统。
为便于理解本申请实施例，首先对本申请中涉及到的术语做简单说明。
1、富媒体通信套件(rich communication suite，RCS)消息：遵循全球移动通信系统协会(global system for mobile communication association，GSMA)推出的富媒体通信融合.07(rich communication convergence.07，RCC.07)标准规范和富媒体通信融合.71(rich communication convergence.71，RCC.71)标准规范。RCS消息是对传统短信的升级，RCS消息在继承经典消息服务号码体系、电信级验证、覆盖广、触达率高等优势的基础上，基于GSMA RCS及相关标准实现，突破了传统短信对信息长度和内容格式的限制，支持文本、图片、音频、视频、位置、联系人和文档等多种媒体格式，引入了消息即平台(messaging as a platform，MaaP)平台，促进信息通信行业垂直行业的融合。
对于终端用户，RCS消息可提供点到点消息和群聊服务，RCS消息的内容形式除文本外，还可以支持图片、音频、视频、位置、联系人等多种形式。对于行业客户，RCS消 息可提供增强的个人与应用间消息服务，实现“消息即平台”，并且引入了新的消息交互模式—聊天机器人，以消息对话的方式连接终端，在对话框即可提供搜索、发现、交互、支付等服务，从而实现企业等行业客户与终端用户的交互服务。
作为示例，富媒体消息可称为RCS消息、5G消息(MSGin5G message)。富媒体消息可用于物联网设备之间，因此，富媒体消息也可称为5G物联网消息。可以理解，消息的具体命名不对本申请实施例的保护范围造成限定。下文为统一，用富媒体消息进行描述。
2、聊天机器人(Chatbot)：富媒体消息中行业消息应用的呈现形式，模拟人类智能对话，向用户提供行业消息服务功能。
3、小程序(MiniApp)：是一种基于web技术(web technology)(如JavaScript)实现的、不需要在终端设备安装即可在终端设备上的宿主移动应用程序(或宿主客户端)中运行的应用程序。其中，宿主移动应用程序(或宿主客户端)需要在终端设备安装后才可以运行，通常可以运行多个(种)小程序。
4、富媒体消息小程序：是以终端设备(或称为富媒体消息终端)上运行的富媒体消息应用程序(或富媒体消息客户端)为宿主应用程序(或宿主客户端)的小程序，也就是说，富媒体消息小程序可由富媒体消息应用程序从网络侧下载后解释执行，无需被安装到终端设备上。可选地，富媒体消息应用程序中内置的小程序引擎(用于解释执行富媒体消息小程序)和富媒体消息小程序可解耦，例如，二者均可独立于对方升级。富媒体消息小程序运行后，可与富媒体小程序对应的服务器进行交互，实现服务发现、搜索、交互、支付等业务。
为便于理解本申请实施例，下面结合图1至图4详细说明适用于本申请实施例的通信系统。
图1是适用于本申请实施例的一通信系统的示意图。如图1所示，该通信系统可以包括：富媒体消息应用服务器、小程序管理服务器、富媒体消息终端。其中，富媒体消息终端可以直接与小程序管理服务器通信，或者，富媒体消息终端也可以通过富媒体消息应用服务器与小程序管理服务器通信。下面简单介绍各设备。
1、富媒体消息终端：表示支持富媒体消息业务的数字移动通信终端，通常安装有富媒体消息客户端，也就是通过富媒体消息客户端支持富媒体消息业务。
可以理解，富媒体消息终端仅是一种命名，其也可以一般性地称为：终端设备、用户设备(user equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。
富媒体消息终端可以是一种向用户提供语音/数据的设备，例如，具有无线连接功能的手持式设备、车载设备等。目前，一些富媒体消息终端的举例为：手机(mobile phone)、平板电脑、笔记本电脑、掌上电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备，虚拟现实(virtual reality，VR)设备、增强现实(augmented reality，AR)设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程手术(remote medical surgery)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal  digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、可穿戴设备，5G网络中的终端设备或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端设备等，本申请实施例对此并不限定。
作为示例而非限定，在本申请实施例中，该富媒体消息终端还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
本申请实施例中，用于实现富媒体消息终端的功能的装置可以是富媒体消息终端，也可以是能够支持富媒体消息终端实现该功能的装置，例如芯片系统或芯片，该装置可以被安装在富媒体消息终端中。本申请实施例中，芯片系统可以由芯片构成，也可以包括芯片和其他分立器件。
此外，富媒体消息终端也可以称为5G消息终端或者RCS客户端(RCS client)。下文为统一，用富媒体消息终端进行描述。
2、富媒体消息客户端：具有富媒体消息业务功能的应用程序或客户端，内置有小程序引擎，可从网络侧查询富媒体消息小程序的信息、下载富媒体消息小程序、运行或者解释执行富媒体消息小程序。为便于理解，将富媒体消息客户端称为富媒体消息小程序的宿主客户端。
3、富媒体消息应用服务器，通信运营商建立的对接行业客户的平台，主要用于实现行业客户Chatbot和消息的接入管理、鉴权、行业消息中多媒体内容上传与存储等功能，使行业客户可以为用户提供多种媒体格式的消息服务。富媒体消息应用服务器还可支持富媒体消息小程序业务权限认证，也即确定是否允许富媒体消息终端使用富媒体消息小程序业务。
作为示例，富媒体消息应用服务器可以为MaaP平台或物联网消息中心等。其中，MaaP平台还可称为聊天机器人平台(Chatbot platform)，其命名不对本申请实施例的保护范围造成限定。下文为统一，用MaaP平台进行描述。关于MaaP平台的具体介绍，后面结合图2详细说明。
4、小程序管理服务器，主要用于负责富媒体消息小程序的审核、认证、发布、汇总与存储富媒体消息小程序信息、为终端设备提供富媒体消息小程序查询服务、对富媒体消息小程序包进行存储等。小程序管理服务器也可称为小程序管理平台，或者称为或富媒体小程序管理服务器或富媒体小程序管理平台，下文为统一，用小程序管理服务器描述。关于小程序管理服务器的具体介绍，后面结合图3详细说明。
图2是适用于本申请实施例的另一通信系统的示意图。如图2所示，该通信系统以富媒体消息系统的架构为例。该通信系统可以包括富媒体消息中心、MaaP平台、以及富媒体消息终端。富媒体消息中心和MaaP平台可以与用户数据管理(如归属用户服务器(home  subscriber server，HSS)，又如统一数据管理(unified data management，UDM)网元)、短信中心(即短消息服务器中心(short message service center，SMSC))、富媒体消息互通网关、电话号码映射(E.164Number URI Mapping，ENUM)或域名系统(domain name system，DNS)、安全管控系统、业务支撑系统、引导服务器(bootstrapping server function，BSF)等对接。关于富媒体消息终端可能的形式，可以参考图1中关于终端设备的描述，此处不再赘述。下面简单介绍其余设备。
1、富媒体消息中心：具备处理富媒体消息的能力，与MaaP平台对接，提供行业消息功能。如图2所示，富媒体消息中心包括多个逻辑功能模块，作为示例，富媒体消息中心包括：群聊功能、IP多媒体子系统(IP multimedia subsystem，IMS)接入功能、多媒体内容存储功能和配置服务器。富媒体消息中心包括的各个逻辑功能模块可以独立部署(即这些逻辑功能模块可以部署在不同的物理设备上)，或者也可以合并部署(即这些功能模块都部署在同一个物理设备上，或者说都内置于富媒体消息中心)，本申请实施例不予限制。富媒体消息中心包括的各个示例性的逻辑功能模块的功能如下。
1)IMS接入功能：主要负责用户富媒体消息信令接入和媒体接入和转发。
2)富媒体消息处理功能：主要处理个人消息、行业消息、增强通话消息的收发，进行会话管理、消息相关业务功能处理等。
3)多媒体内容存储功能：主要用于存储个人用户发送的多媒体消息文件。
4)配置服务器：或者称为设备管理(device management，DM)，主要用于存储用户业务相关数据，如协议参数、业务参数等。富媒体消息终端可通过访问配置服务器获取相关数据对富媒体消息终端进行业务配置。
5)群聊功能：可包括群聊消息功能和群数据管理。其中，群聊消息功能，可用于实现群聊消息的分发。群数据管理，可用于实现创建群、邀请他人加入群、删除群成员、解散群、转移管理员权限、设置群名称、设置群头像等功能。此外，群数据管理还可用于存储、管理群聊相关数据信息，如群成员列表、群名称、群头像、群成员身份等。
富媒体消息中心，也可称为5G消息中心(5G message center，5GMC)，或者也可称为RCS服务提供商网络(RCS service provider network)，下文为统一，用富媒体消息中心描述。
2、MaaP平台：与富媒体消息中心对接，提供行业消息功能，承载交互式富媒体消息业务。如图2所示，MaaP平台可包括基础功能和运营管理。其中，运营管理，主要用于运营商对Chatbot进行开通、权限配置等管理，基础功能可包括如下示例性逻辑功能模块。
1)Chatbot目录：主要用于汇总Chatbot数据信息，提供匹配、排序等算法服务，处理来自用户的Chatbot发现请求，向用户返回搜索结果。
2)Chatbot信息：主要用于存储Chatbot的相关信息，处理来自用户的Chatbot信息查询。该相关信息可包括提供该Chatbot的企业信息，如名称、商标、业务类型、联系方式等。该相关信息还可包括Chatbot或应用本身的信息，如Chatbot用途、应用用途、开发方信息等。
3)多媒体文件存储功能：主用于存储Chatbot下发的多媒体消息文件。
4)Chatbot能力开放：主要用于将富媒体消息能力进行统一抽象封装，对Chatbot提供消息接入能力。
类似地，MaaP平台所包含的逻辑功能模块可以独立部署，也可以合并部署，本申请实施例不予限制。
图3是适用于本申请实施例的另一通信系统的示意图。如图3所示，该通信系统为富媒体消息系统的架构为例。如图3所示，与图2相比，在图3所示的系统中，增加了小程序管理服务器。
小程序管理服务器可独立部署，或者也可内置在MaaP平台，不予限制。小程序管理服务器可包括如下逻辑功能模块。
1)运营管理：主要用于审核富媒体消息小程序是否符合富媒体消息小程序开发规范、认证富媒体消息小程序、发布富媒体消息小程序，发布后用户才能查询到。
2)小程序包存储(即富媒体消息小程序包存储)：主要用于存储富媒体消息小程序包。
3)富媒体消息小程序目录(即富媒体消息小程序目录)：主要用于汇总与存储富媒体消息小程序信息。该富媒体消息小程序信息可包括该富媒体消息小程序的基本信息，如包括标识(identifier，ID)、名称、图标、版本等。该富媒体消息小程序信息还可包括富媒体消息小程序的详细信息，如包括富媒体消息小程序的提供商(行业客户)、业务类型、联系方式、网站，以及富媒体消息小程序用途、开发方信息等。
可以理解，小程序目录和Chatbot目录可以相同，也可以不同，不予限制。以小程序目录和Chatbot相同为例，一种可能的情况，在富媒体消息系统的架构中，包括一目录，该目录可以用于汇总Chatbot数据信息，即实现图2中所述的Chatbot目录的功能，还可以用于汇总与存储富媒体消息小程序信息，即实现图3中所述的小程序目录的功能。
4)小程序查询服务(即富媒体消息小程序查询服务)：主要用于处理富媒体消息终端的富媒体消息小程序查询请求，提供匹配、排序等算法服务，向用户返回查询结果。该查询结果可包括根据富媒体消息小程序关键字查询到的富媒体消息小程序信息，如：ID、名称、图标、版本等。
图4是适用于本申请实施例的另一通信系统的示意图。如图4所示，该通信系统以富媒体消息系统的架构为例。如图4所示，与图3相比，在图4所示的系统中，小程序管理服务器可直接与富媒体消息中心对接。关于各设备的描述，可参考前面的描述，此处不再赘述。
目前，行业客户以Chatbot的形式与用户通过富媒体消息中心、MaaP平台进行消息交互，以为用户提供服务，如完成一些如订票、酒店查询、物流查询等功能。
图5是用户订票的一示意图。如图5中的(1)所示，行业客户的Chatbot可以以点对点方式向用户发送消息，用户向Chatbot回复消息，从而完成订票功能。从图5中的(1)可看出，用户需输入多次信息与Chatbot进行交互，操作繁琐，交互过程长，影响用户体验。
本申请提出一种方式，通过在富媒体消息系统中增加小程序管理服务器，为富媒体消息终端提供富媒体消息小程序查询服务，进而采用富媒体消息小程序为富媒体消息终端提供服务，简化用户操作，缩短交互过程，提升用户体验。作为示例，仍以用户订票为例，如图5中的(2)所示，通过采用富媒体小程序来为富媒体消息终端提供订票服务，在富媒体消息小程序运行后，富媒体消息终端可与富媒体小程序对应的服务器进行交互，从而 实现订票业务。从图5可以看出，采用富媒体消息小程序为富媒体消息终端提供服务，可以简化用户操作，缩短交互过程，提升用户体验。
可以理解，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
上面对本申请中涉及到的术语做了简单说明，下文实施例中不再赘述。
下文将结合附图详细说明本申请实施例提供的方法。
图6是本申请实施例提供的一种通信方法600的示意图。方法600可以包括如下步骤。
610，富媒体消息应用服务器接收来自富媒体消息终端的第一查询请求消息。
相应地，富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息。
一种可能的实现方式，富媒体消息应用服务器为MaaP或Chatbot平台，富媒体消息终端与富媒体消息应用服务器通过聊天机器人目录查询接口通信。
例如，富媒体消息终端通过聊天机器人目录查询接口向富媒体消息应用服务器发送第一查询请求消息，相应地，富媒体消息应用服务器通过聊天机器人目录查询接口接收来自富媒体消息终端的第一查询请求消息。这样，富媒体消息终端可通过聊天机器人目录查询接口查询富媒体消息小程序，无需增加额外的配置参数、引入额外的接口安全认证流程，可以提升富媒体消息终端的配置效率和启动效率。此外，无需增加额外的用户身份认证流程，可以提升富媒体消息系统的资源利用率。
其中，聊天机器人目录查询接口，表示富媒体消息终端向富媒体应用服务器发送请求获取聊天机器人列表的接口。作为示例，聊天机器人目录查询接口例如为GSMA RCC.07中的客户端到服务提供商聊天机器人目录接口(Client to Service Provider Chatbot Directory interface)。可以理解，聊天机器人目录查询接口的名称不对本申请实施例的保护范围造成限定，也即在未来，若该接口的名称发生改变，改变后的接口名称也适用于本申请实施例。
其中，第一查询请求消息包含查询信息。
查询信息，可包括用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，或富媒体消息终端查询的富媒体消息小程序的相关信息，或富媒体消息终端查询的富媒体消息小程序要满足的需求信息。其中，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序。
可选地，查询信息包括以下至少一项或以下至少一项包含的关键字：富媒体消息小程序的名称、富媒体消息小程序的类型、富媒体消息小程序的提供商的名称、富媒体消息小程序的服务内容描述或功能描述、富媒体消息客户端支持的语言、或富媒体消息客户端的版本等。
其中每一项介绍如下。
-富媒体消息小程序的名称表示要查询的富媒体消息小程序的名称。
-富媒体消息小程序的类型表示要查询的富媒体消息小程序的类型。
-富媒体消息小程序的提供商的名称表示要查询的富媒体消息小程序的提供商的名称。
-富媒体消息小程序的服务内容描述或功能描述表示要查询的富媒体消息小程序的服 务内容或功能。该富媒体消息小程序的服务内容描述或功能描述为统一资源定位符(uniform resource locator，URL)转义的。
-富媒体消息客户端支持的语言可表示要查询的富媒体消息小程序的首选语言。假设用“pl”参数表示要查询的富媒体消息小程序的语言，例如，如果富媒体消息终端的语言设置为英语，并且富媒体消息终端搜索的其他首选语言是西班牙语和德语，那么查询信息中的“pl”参数可设置为：pl＝en&pl＝es&pl＝de。
-富媒体消息客户端的版本表示富媒体消息终端中富媒体消息客户端的版本。
可以理解，上述为示例性说明，本申请实施例不限于此。例如，查询信息还可以包括富媒体消息小程序的数量，也即要查询的富媒体消息小程序的数量，如记为“num”参数。再例如，查询信息还可以包括查询结果中应包含的第一个匹配结果，如记为“start”参数。作为示例，“start”参数可使用基于零的索引，也即第一个查询结果是0；第二个查询结果是1，依此类推。该“start”参数和“num”参数可一起工作，以确定要返回的查询结果。再例如，查询信息还可以包括富媒体消息终端对应的用户的移动台国际ISDN号码(mobile subscriber ISDN number，MSISDN)，其中，ISDN为综合业务数字网(integrated service digital network，ISDN)。再例如，查询信息还可以包括富媒体消息终端对应的用户所属的运营商信息等。
可选地，该第一查询请求消息还包括指示信息。
其中，该指示信息，可指示查询信息包含用于描述富媒体消息终端对应的用户需要的富媒体消息小程序的信息，或者可指示富媒体消息应用服务器提供富媒体消息小程序，也即指示富媒体消息应用服务器提供与查询信息相匹配的富媒体消息小程序的信息或富媒体消息应用服务器提供查询信息所描述的富媒体消息小程序。换句话说，指示信息指示该第一查询请求消息用于查询富媒体消息小程序，也即富媒体消息应用服务器根据该指示信息可获知该第一查询请求消息用于查询富媒体消息小程序。指示信息也可称为富媒体消息小程序查询指示(如记为miniapp参数)，其命名不对本申请实施例的保护范围造成限定。
一种可能的实现方式，若第一查询请求消息中包括miniapp参数，则第一查询请求消息用于查询富媒体消息小程序；若第一查询请求消息中不包括miniapp参数，则第一查询请求消息用于查询聊天机器人。可以理解，上述为示例性说明，本申请实施例不限于此。
620，响应于第一查询请求消息，富媒体消息应用服务器获取富媒体消息小程序的信息。
举例来说，富媒体消息应用服务器根据第一查询请求消息中的指示信息，获知该第一查询请求消息用于查询富媒体消息小程序，因此，富媒体消息应用服务器根据第一查询请求消息中的查询信息，获取与该查询信息相匹配的富媒体消息小程序的信息。
例如，若该查询信息包括富媒体消息小程序的服务内容描述或功能描述，则富媒体消息应用服务器根据该富媒体消息小程序的服务内容描述或功能描述，获取满足条件的富媒体消息小程序。举例来说，若该富媒体消息小程序的服务内容描述或功能描述用于指示查询订火车票，则富媒体消息应用服务器根据该服务内容描述或功能描述，获取与订火车票相关的富媒体消息小程序。
再例如，若该查询信息包括富媒体消息客户端支持的语言，则富媒体消息应用服务器根据该富媒体消息客户端支持的语言，获取满足条件的富媒体消息小程序。也就是说，该 富媒体消息小程序的语言与查询信息中包括的富媒体消息客户端支持的语言相匹配。
再例如，若该查询信息包括富媒体消息客户端的版本，则富媒体消息应用服务器根据该富媒体消息客户端的版本，获取满足条件的富媒体消息小程序。也就是说，该富媒体消息小程序的运行版本与查询信息中包括的富媒体消息客户端的版本相匹配。
再例如，若该查询信息包括富媒体消息小程序的提供商的名称，则富媒体消息应用服务器根据该富媒体消息小程序的提供商的名称，获取满足条件的富媒体消息小程序。也就是说，该富媒体消息小程序的提供商的名称与查询信息中包括的富媒体消息小程序的提供商的名称相匹配。
可以理解，上述为示例性说明，本申请实施例不限于此。
可选地，富媒体消息应用服务器获取富媒体消息小程序的信息，包括以下任一实现方式。
一种可能的实现方式，富媒体消息应用服务器向小程序管理服务器发送第二查询请求消息，第二查询请求消息包含查询信息；富媒体消息应用服务器接收来自小程序管理服务器的第二查询响应消息，第二查询响应消息包含富媒体消息小程序的信息。
基于该实现方式，富媒体消息应用服务器可基于第一查询请求消息中的查询信息，生成第二查询请求消息，并向小程序管理服务器发送该第二查询请求消息。小程序管理服务器收到该第二查询请求消息后，可以基于该第二查询请求消息中的查询信息，确定与该查询信息相匹配的富媒体消息小程序的信息，并将该富媒体消息小程序的信息发送给小程序管理服务器。
另一种可能的实现方式，富媒体消息应用服务器根据查询信息，从本地获取富媒体消息小程序的信息。
基于该实现方式，富媒体消息应用服务器可基于第一查询请求消息中的查询信息，自己确定该查询信息相匹配的富媒体消息小程序的信息。
基于上述任一实现方式，富媒体消息应用服务器可以获取到与第一查询请求消息中的查询信息相匹配的富媒体消息小程序的信息。
可选地，在富媒体消息应用服务器获取富媒体消息小程序的信息之前，方法600还包括：富媒体消息应用服务器确定允许富媒体消息终端对应的用户使用富媒体消息小程序。
举例来说，富媒体消息应用服务器收到富媒体消息终端发送的第一查询请求消息后，若基于该第一查询请求消息中的指示信息获知该第一查询请求消息用于查询富媒体消息小程序，则可先判断是否允许该富媒体消息终端对应的用户使用富媒体消息小程序。在富媒体消息应用服务器确定允许该富媒体消息终端对应的用户使用富媒体消息小程序的情况下，再基于上述任一实现方式获取与该查询信息相匹配的富媒体消息小程序的信息，也即查询信息所描述的富媒体消息小程序的信息。若富媒体消息应用服务器确定禁止该富媒体消息终端对应的用户使用富媒体消息小程序的情况下，则富媒体消息应用服务器可向富媒体消息终端返回查询失败或返回空。
一种可能的实现方式，富媒体消息应用服务器根据富媒体消息终端对应的用户的签约信息和/或富媒体消息终端对应的用户所属的运营商信息，确定允许富媒体消息终端对应的用户使用富媒体消息小程序。
630，富媒体消息应用服务器向富媒体消息终端发送第一查询响应消息，第一查询响 应消息包含富媒体消息小程序的信息。
相应地，富媒体消息终端接收该第一查询响应消息。
一种可能的实现方式，富媒体消息应用服务器通过聊天机器人目录查询接口向富媒体消息终端发送第一查询响应消息，相应地，富媒体消息终端通过聊天机器人目录查询接口接收来自富媒体消息应用服务器的第一查询响应消息。
可选地，方法600还包括步骤640：富媒体消息终端根据富媒体消息小程序的信息下载并运行富媒体消息小程序。
基于本申请实施例，富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息，该第一查询请求消息包含查询信息。这样，富媒体消息应用服务器可基于该查询信息获取与该查询信息相匹配的富媒体消息小程序，也即该查询信息所描述的富媒体消息小程序，进而向富媒体消息终端提供富媒体消息小程序的信息。这样，富媒体消息终端可根据富媒体消息小程序的信息下载并运行富媒体消息小程序，进而通过该富媒体消息小程序实现某些功能，简化用户操作，提升用户体验。
可选地，富媒体消息小程序的信息包括富媒体消息小程序的下载地址。这样，富媒体消息终端(或者富媒体消息终端中的富媒体消息客户端)可以根据该富媒体消息小程序的下载地址下载富媒体消息小程序。
可选地，富媒体消息小程序的信息还包括以下至少一项：富媒体消息小程序的标识、富媒体消息小程序的名称、富媒体消息小程序的图标的地址、富媒体消息小程序的版本。
可以理解，上述为示例性说明，本申请实施例不限于此。例如，富媒体消息小程序的信息还可以包括以下至少一项：富媒体消息小程序的提供商信息、或者富媒体消息小程序本身的信息。其中，富媒体消息小程序的提供商信息例如可包括以下至少一项：商标、业务类型、联系方式、网站。其中，富媒体消息小程序本身的信息例如可包括以下至少一项：富媒体消息小程序的用途、富媒体消息小程序的开发方信息等。
图7是本申请实施例提供的一种通信方法700的示意图。方法700可以包括如下步骤。
710，小程序管理服务器接收来自富媒体消息终端的第一查询请求消息。
相应地，富媒体消息终端向小程序管理服务器发送第一查询请求消息。
一种可能的实现方式，小程序管理服务器通过小程序目录查询接口接收来自富媒体消息终端的第一查询请求消息，相应地，富媒体消息终端通过小程序目录查询接口向小程序管理服务器发送第一查询请求消息。
其中，小程序目录查询接口，表示富媒体消息终端向小程序管理服务器发送请求获取富媒体消息小程序列表的接口。可以理解，小程序目录查询接口的名称不对本申请实施例的保护范围造成限定，也即在未来，若该接口的名称发生改变，改变后的接口名称也适用于本申请实施例。
其中，第一查询请求消息包含查询信息。关于查询信息可参考方法600中的相关描述，此处不再赘述。
720，小程序管理服务器根据查询信息获取富媒体消息小程序的信息。
其中，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序。
小程序管理服务器根据第一查询请求消息中的查询信息，自身确定与该查询信息相匹 配的富媒体消息小程序的信息。
可选地，在小程序管理服务器获取富媒体消息小程序的信息之前，方法700还包括：小程序管理服务器确定允许富媒体消息终端对应的用户使用富媒体消息小程序。
举例来说，小程序管理服务器收到富媒体消息终端发送的第一查询请求消息后，可先判断是否允许该富媒体消息终端对应的用户使用富媒体消息小程序。在小程序管理服务器确定允许该富媒体消息终端对应的用户使用富媒体消息小程序的情况下，再获取与该查询信息相匹配的富媒体消息小程序的信息，也即查询信息所描述的富媒体小程序的信息。若小程序管理服务器确定禁止该富媒体消息终端对应的用户使用富媒体消息小程序，则小程序管理服务器可向富媒体消息终端返回查询失败或返回空。
一种可能的实现方式，小程序管理服务器根据富媒体消息终端对应的用户的签约信息和/或富媒体消息终端对应的用户所属的运营商信息，确定允许富媒体消息终端对应的用户使用富媒体消息小程序。
730，小程序管理服务器向富媒体消息终端发送第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息。
相应地，富媒体消息终端接收该第一查询响应消息。
一种可能的实现方式，小程序管理服务器通过小程序目录查询接口向富媒体消息终端发送第一查询响应消息，相应地，富媒体消息终端通过小程序目录查询接口接收该第一查询响应消息。
可选地，方法700还包括步骤740：富媒体消息终端根据富媒体消息小程序的信息下载并运行富媒体消息小程序。
关于富媒体消息小程序的信息可参考方法600中的描述，此处不再赘述。
基于本申请实施例，富媒体消息终端可向小程序管理服务器发送第一查询请求消息，该第一查询请求消息包含查询信息。这样，小程序管理服务器可基于该查询信息获取与该查询信息相匹配的富媒体消息小程序，也即该查询信息所描述的富媒体消息小程序，进而向富媒体消息终端提供富媒体消息小程序的信息。这样，富媒体消息终端可根据富媒体消息小程序的信息下载并运行富媒体消息小程序，进而通过该富媒体消息小程序实现某些功能，简化用户操作，提升用户体验。
为便于理解，下面介绍适用于本申请实施例的可能的流程。
图8是根据本申请一实施例提供的通信方法800的示意性流程图。该方法800可以用于实现上述方法600的方案。在该方法800中，富媒体消息应用服务器为MaaP平台。该方法800可以包括如下步骤。
801，富媒体消息终端接收查询地址。
其中，该查询地址，指的是富媒体消息终端查询富媒体消息小程序的地址，也即富媒体消息终端发送第一查询请求消息的地址。
举例来说，富媒体消息终端可根据国际移动用户识别码(international mobile subscriber identify，IMSI)中的移动国家码(mobile country code，MCC)和移动网络码(mobile network code，MNC)信息，构建默认的配置服务器网络域名(如全限定域名(fully qualified domain name，FQDN))。作为示例，构建的配置服务器网络域名为config.rcs.mnc.mcc.pub.3gppnetwork.org。然后，富媒体消息终端向配置服务器发送消息， 如HTTP/HTTPS消息，以请求富媒体消息终端的配置信息，相应地，配置服务器向富媒体消息终端发送富媒体消息终端的配置信息。其中，该配置信息包括查询地址。作为示例，该查询地址为：CHATBOT DIRECTORY。
可选地，富媒体消息终端向BSF请求认证(authorization)信息，相应地，BSF向富媒体消息终端发送认证信息。
802，富媒体消息终端向MaaP平台发送第一查询请求消息。
富媒体消息终端向MaaP平台发起富媒体消息小程序查询请求，如富媒体消息终端通过Client to Service Provider Chatbot Directory interface向MaaP平台发送第一查询请求消息。富媒体消息终端可直接向MaaP平台发送第一查询请求消息，也即该第一查询请求消息可不经过富媒体消息中心。
一种可能的实现方式，富媒体消息终端根据步骤801中收到的查询地址(如CHATBOT DIRECTORY)、路径值botlist和查询参数生成第一查询请求消息。其中，查询参数可包括查询信息和指示信息(如miniapp参数)。关于查询信息和指示信息，可参考方法600中的描述，此处不再赘述。可选地，该第一查询请求消息携带从BSF请求的认证信息。
作为一示例，该第一查询请求消息的形式如下：
https://{CHATBOT DIRECTORY}/botlist？miniapp＝1&q＝％E6％89％93％BD&i＝％2BABCDEFGHIJKLM&client_version＝RCSAndrd-4.0
在上述示例中，“miniapp＝1”，表示该第一查询请求消息用于查询富媒体消息小程序，也即“miniapp＝1”是一个指示信息，指示MaaP平台根据该第一查询请求消息中的查询信息(如“q＝％E6％89％93％BD&i＝％2BABCDEFGHIJKLM&client_version＝RCSAndrd-4.0”)提供富媒体消息小程序的信息。
作为另一示例，该第一查询请求消息的形式如下：
https://{CHATBOT DIRECTORY}/botlist？type＝miniapp&q＝％E6％89％93％BD&i＝％2BABCDEFGHIJKLM&client_version＝RCSAndrd-4.0
在上述示例中，“type＝miniapp”，表示该第一查询请求消息用于查询富媒体消息小程序，也即“type＝miniapp”是一个指示信息，指示MaaP平台根据该第一查询请求消息中的查询信息(如“q＝％E6％89％93％BD&i＝％2BABCDEFGHIJKLM&client_version＝RCSAndrd-4.0”)提供富媒体消息小程序的信息。
可以理解，上述两个示例为示例性说明，属于上述示例的变形，都适用于本申请实施例。
803，MaaP平台向BSF发起用户认证。
MaaP平台收到第一查询请求消息后，可先向BSF发起用户认证，由BSF对用户进行认证。
804，BSF向MaaP平台发送认证结果。
若认证结果显示认证成功，则MaaP平台执行步骤805。
可以理解，上述步骤803和804为示例性说明，本申请实施例不限于此。例如，MaaP平台收到第一查询请求消息后，可直接执行步骤805。
805，MaaP平台根据第一查询请求消息，生成第二查询请求消息。
在步骤805中，MaaP平台可解析第一查询请求消息，并根据第一查询请求消息中的 查询参数，也即查询参数中的查询信息，生成第二查询请求消息。
举例来说，MaaP本地配置小程序管理服务器地址，如https://{MINIAPP DIRECTORY}，MaaP平台根据小程序管理服务器的地址、小程序资源的路径值(如记为miniapplist)、以及第一查询请求消息中的查询信息，生成第二查询请求消息。作为示例，第二查询请求的形式如下：
https://{MINIAPP DIRECTORY}/miniapplist？q＝％E6％89％93％BD&i＝％2BABCDEFGHIJKLM&client_version＝RCSAndrd-4.0
其中，第二查询请求消息中的查询参数可包括第一查询请求消息中的查询信息。
可选地，MaaP平台确定该第一查询请求消息是用于查询富媒体消息小程序的情况下，MaaP平台根据第一查询请求消息中的查询信息，生成第二查询请求消息。
具体来说，MaaP平台可解析该第一查询请求消息，以确定该第一查询请求消息是否用于查询富媒体消息小程序。例如，若第一查询请求消息中携带了指示信息(如miniapp参数)，则MaaP平台确定该第一查询请求消息用于查询富媒体消息小程序；若第一查询请求消息中未携带指示信息(如miniapp参数)，则MaaP平台确定该第一查询请求消息用于查询Chatbot。在MaaP平台确定该第一查询请求消息是查询富媒体消息小程序的情况下，MaaP平台再根据第一查询请求消息中的查询信息生成第二查询请求消息，这样，可以避免发生第一查询请求消息用于查询Chatbot的情况下，MaaP平台却生成第二查询请求消息，浪费信令开销。
可选地，MaaP平台确定允许富媒体消息终端对应的用户查询富媒体消息小程序的情况下，MaaP平台根据第一查询请求消息中的查询信息，生成第二查询请求消息。
具体来说，MaaP平台可对富媒体消息终端对应的用户使用富媒体消息小程序业务进行权限认证。一种可能的实现方式，MaaP平台根据富媒体消息终端对应的用户的签约信息和/或富媒体消息终端对应的用户所属的运营商信息，确定是否允许富媒体消息终端对应的用户查询富媒体消息小程序。在MaaP平台确定允许富媒体消息终端对应的用户查询富媒体消息小程序的情况下，MaaP平台再根据第一查询请求消息中的查询信息生成第二查询请求消息，这样，可以避免发生禁止富媒体消息终端对应的用户查询富媒体消息小程序，MaaP平台却生成第二查询请求消息，浪费信令开销。
可以理解，上述两个情形可以单独使用，也可以结合使用。例如，上述两个情形结合使用时，也即MaaP平台确定该第一查询请求消息用于查询富媒体消息小程序，且允许富媒体消息终端对应的用户查询富媒体消息小程序的情况下，再根据第一查询请求消息中的查询信息生成第二查询请求消息。
806，MaaP平台向小程序管理服务器发送第二查询请求消息。
作为示例，该第二查询请求消息为HTTP GET消息(如HTTP GET request消息)。
807，小程序管理服务器根据第二查询请求消息中的查询信息，确定富媒体消息小程序。
小程序管理服务器解析第二查询请求消息，并且根据第二查询请求消息中的查询信息，获取满足条件的富媒体消息小程序。关于确定富媒体消息小程序的方案可参考步骤620中的相关描述，此处不再赘述。
可选地，小程序管理服务器确定是否允许富媒体消息终端对应的用户查询富媒体消息 小程序，也即小程序管理服务器对富媒体消息终端对应的用户使用富媒体消息小程序业务进行权限认证。一种可能的实现方式，小程序管理服务器根据富媒体消息终端对应的用户的签约信息和/或富媒体消息终端对应的用户所属的运营商信息，确定是否允许富媒体消息终端对应的用户查询富媒体消息小程序。若小程序管理服务器确定允许富媒体消息终端对应的用户查询富媒体消息小程序，则小程序管理服务器根据第二查询请求消息中的需求参数，确定与查询信息相匹配的富媒体消息小程序，也即查询信息所描述的富媒体消息小程序。
可以理解，若MaaP平台确定是否允许富媒体消息终端对应的用户查询富媒体消息小程序，则小程序管理服务器也可以不用确定是否允许富媒体消息终端对应的用户查询富媒体消息小程序。举例来说，若MaaP平台确定允许富媒体消息终端对应的用户查询富媒体消息小程序，则向小程序管理服务器发送第二查询请求消息；若小程序管理服务器收到MaaP平台发送的第二查询请求消息，则小程序管理服务器可默认允许富媒体消息终端对应的用户查询富媒体消息小程序。若MaaP平台确定禁止富媒体消息终端对应的用户查询富媒体消息小程序，则可直接向富媒体消息终端返回查询失败或结果为空，即不用再向小程序管理服务器发送第二查询请求消息。
808，小程序管理服务器向MaaP平台发送富媒体消息小程序的信息。
例如，小程序管理服务器向MaaP平台发送200OK，该200OK包括富媒体消息小程序的信息。
作为示例，富媒体消息小程序的信息可包括富媒体消息小程序的基本信息，富媒体消息小程序的基本信息包括富媒体消息小程序的下载地址。富媒体消息小程序的基本信息还包括以下至少一项：富媒体消息小程序的ID、富媒体消息小程序的名称、富媒体消息小程序的图标的地址、富媒体消息小程序的版本等。进一步可选地，富媒体消息小程序的基本信息还可包括以下至少一项：返回的查询对象数、第一个查询结果在当前查询结果集合中的索引、查询对象的数量、指示富媒体消息小程序是否将作为身份已验证的富媒体消息小程序呈现给用户。
一种可能的形式，小程序管理服务器向MaaP平台发送的富媒体消息小程序的信息如下：
Figure PCTCN2022133390-appb-000001
Figure PCTCN2022133390-appb-000002
可以理解，上述为示例性说明，本申请实施例不限于此。例如，富媒体消息小程序的信息还可包括富媒体消息小程序的详细信息，富媒体消息小程序的详细信息包括以下至少一项：富媒体消息小程序的提供商信息、或者富媒体消息小程序本身的信息。其中，富媒体消息小程序的提供商信息例如可包括以下至少一项：商标、业务类型、联系方式、网站。其中，富媒体消息小程序本身的信息例如可包括以下至少一项：富媒体消息小程序的用途、富媒体消息小程序的开发方信息等。
还可以理解，小程序管理服务器可以同时向MaaP平台发送富媒体消息小程序的基本信息和富媒体消息小程序的详细信息，或者，小程序管理服务器也可以先向MaaP平台发送富媒体消息小程序的基本信息，在收到富媒体消息终端的请求后(该请求用于请求富媒体消息小程序的详细信息)，再通过MaaP平台向富媒体消息终端发送富媒体消息小程序的详细信息。
可选地，若小程序管理服务器未查询到富媒体消息小程序或者查询失败，则结果返回空。
809，MaaP平台向富媒体消息终端发送富媒体消息小程序的信息。
MaaP平台收到富媒体消息小程序的信息后，可将该富媒体消息小程序的信息发给富媒体消息终端。例如，MaaP平台向富媒体消息终端发送200OK，该200OK包括富媒体消息小程序的信息。
图9是富媒体消息小程序查询效果的示意图。
如图9所示，富媒体消息终端的查询结果包括2个。第一个查询结果为：富媒体消息小程序的名称为小程序xx，富媒体消息小程序的ID为1122331122，富媒体消息小程序的版本为1.1。第一个查询结果为：富媒体消息小程序的名称为小程序zz，富媒体消息小程序的ID为1122331133，富媒体消息小程序的版本为1.1。此外，该查询结果中还包括富媒体消息小程序的下载地址，富媒体消息终端(或者说富媒体消息中的富媒体消息客户端)可以基于该富媒体消息小程序的下载地址，下载该富媒体消息小程序，进而运行该富媒体消息小程序。可以理解，图9中的小程序即表示富媒体消息小程序。
810，富媒体消息终端根据富媒体消息小程序的信息下载并运行富媒体消息小程序。
举例来说，富媒体消息终端基于富媒体消息小程序的下载地址下载富媒体消息小程序，并运行该富媒体消息小程序。例如，如图8所示，富媒体消息终端(也即富媒体消息终端中的富媒体消息客户端，或者说富媒体消息客户端下载的富媒体消息小程序)通过与富媒体消息小程序对应的服务器(如可称为富媒体消息小程序后台服务器)交互，实现运行该富媒体消息小程序，进而通过该富媒体消息小程序实现某些业务功能，如通过该富媒体消息小程序实现服务发现、搜索、交互、支付等业务功能。以图5为例，通过富媒体消息小程序，可实现订票业务。
可以理解，图8所示实施例主要以MaaP平台和小程序管理设备平台分开部署为例进 行示例性说明，对此不予限制。例如，MaaP平台和小程序管理设备平台也可以合设，在该情况下，MaaP平台收到第一查询请求消息后，可直接从本地获取富媒体消息小程序的信息，并将确定的富媒体消息小程序的信息发送给富媒体消息终端。
上文结合图8所示的步骤801-810示例地介绍了富媒体消息终端通过MaaP平台向小程序管理服务器查询富媒体消息小程序的场景，该方法800可通过如图3所示的架构实现。基于上述实施例，在富媒体消息系统中增加小程序管理服务器，存储和管理小程序信息，并为富媒体消息终端提供富媒体消息小程序查询服务；存储和管理富媒体消息小程序包，并为富媒体消息终端提供富媒体消息小程序包的下载服务。小程序管理服务器和MaaP平台可以部署在同一物理或虚拟服务器上，也可以部署在不同的物理或虚拟服务器上，不予限制。富媒体消息终端在第一查询请求消息中携带指示信息和查询信息，MaaP平台解析该第一查询请求消息，如基于第一查询请求消息中的指示信息判断是查询富媒体消息小程序，又如根据第一查询请求消息中的查询信息生成第二查询请求消息，并向小程序管理服务器发送查询富媒体消息小程序的请求(即第二查询请求消息)。小程序管理服务器基于该第二查询请求消息，确定符合条件的富媒体消息小程序，并向MaaP平台发送富媒体消息小程序的信息，MaaP平台将该富媒体消息小程序的信息返回给富媒体消息终端，从而富媒体消息终端可运行该富媒体消息小程序。这样，使得富媒体消息终端可以发现富媒体消息小程序，进而可以采用富媒体消息小程序完成诸如购票、客户调研之类的功能，简化用户操作，缩短交互过程，提升用户体验。此外，对现有富媒体消息系统改动较小，便于富媒体消息小程序在富媒体消息系统中的推广应用。
图10是根据本申请另一实施例提供的通信方法1000的示意性流程图。该方法1000可以用于实现上述方法700的方案。该方法1000可以包括如下步骤。
1001，富媒体消息终端接收查询地址。
其中，该查询地址，指的是富媒体消息终端查询富媒体消息小程序的地址，也即富媒体消息终端发送第一查询请求消息的地址。
举例来说，富媒体消息终端可根据IMSI中的MCC和MNC信息，构建默认的配置服务器网络域名(如FQDN)。作为示例，构建的配置服务器网络域名为config.rcs.mnc.mcc.pub.3gppnetwork.org。然后，富媒体消息终端向配置服务器发送消息，如HTTP/HTTPS消息，以请求富媒体消息终端的配置信息，相应地，配置服务器向富媒体消息终端发送配置信息。其中，该配置信息包括查询地址信息。作为示例，该查询地址信息为：MINIAPP DIRECTORY。
可选地，富媒体消息终端向BSF请求认证信息，相应地，BSF向富媒体消息终端发送认证信息。
1002，富媒体消息终端向小程序管理服务器发送第一查询请求消息。
一种可能的实现方式，富媒体消息终端根据步骤1001中收到的查询地址(如MINIAPP DIRECTORY)、路径值miniapplist和查询参数生成第一查询请求消息。其中，查询参数包括查询信息。关于查询信息，可参考方法600中的描述，此处不再赘述。可选地，该第一查询请求消息携带从BSF请求的认证信息。
作为示例，该第一查询请求消息的形式如下：
https://{MINIAPP DIRECTORY}/miniapplist？q＝％E6％89％93％BD& i＝％2BABCDEFGHIJKLM&client_version＝RCSAndrd-4.0
1003，小程序管理服务器向BSF发起用户认证。
小程序管理服务器收到第一查询请求消息后，可先向BSF发起用户认证，由BSF对用户进行认证。
1004，BSF向小程序管理服务器发送认证结果。
若认证结果显示认证成功，则小程序管理服务器执行步骤1005。
可以理解，上述步骤1003和1004为示例性说明，本申请实施例不限于此。例如，小程序管理服务器收到第一查询请求消息后，可直接执行步骤1005。
1005，小程序管理服务器根据第一查询请求消息，确定富媒体消息小程序。
在步骤1005中，小程序管理服务器可解析第一查询请求消息，并根据第一查询请求消息中的查询信息，获取满足条件的富媒体消息小程序。
可选地，小程序管理服务器确定允许富媒体消息终端对应的用户查询富媒体消息小程序的情况下，小程序管理服务器根据第一查询请求消息中的查询信息，确定该查询信息所描述的富媒体消息小程序。
具体来说，小程序管理服务器可对富媒体消息终端对应的用户使用富媒体消息小程序业务进行权限认证。一种可能的实现方式，小程序管理服务器根据富媒体消息终端对应的用户的签约信息和/或富媒体消息终端对应的用户所属的运营商信息，确定是否允许富媒体消息终端对应的用户查询富媒体消息小程序。在小程序管理服务器确定允许富媒体消息终端对应的用户查询富媒体消息小程序的情况下，小程序管理服务器再根据第一查询请求消息中的查询信息确定富媒体消息小程序。
1006，小程序管理服务器向富媒体消息终端发送富媒体消息小程序的信息。
例如，小程序管理服务器向富媒体消息终端发送200OK，该200OK包括富媒体消息小程序的信息。
关于富媒体消息小程序的信息可参考步骤808中的相关描述，此处不再赘述。
可以理解，小程序管理服务器可以同时向富媒体消息终端发送富媒体消息小程序的基本信息和富媒体消息小程序的详细信息，或者，小程序管理服务器也可以先向富媒体消息终端发送富媒体消息小程序的基本信息，在收到富媒体消息终端的请求后(该请求用于请求富媒体消息小程序的详细信息)，再向富媒体消息终端发送富媒体消息小程序的详细信息。
可选地，若小程序管理服务器未查询到富媒体消息小程序或者查询失败，则结果返回空。
1007，富媒体消息终端根据富媒体消息小程序的信息下载并运行富媒体消息小程序。
富媒体消息终端运行该富媒体消息小程序，进而通过该富媒体消息小程序实现某些业务功能，如通过该富媒体消息小程序实现服务发现、搜索、交互、支付等业务功能。以图5为例，通过富媒体消息小程序，可实现订票业务。
步骤1007与步骤810类似，此处不再赘述。
上文结合图10所示的步骤1001-1007示例地介绍了富媒体消息终端直接向小程序管理服务器查询富媒体消息小程序的场景，该方法1000可通过如图4所示的架构实现。基于上述实施例，小程序管理服务器可存储和管理富媒体消息小程序信息，并为富媒体消息 终端提供富媒体消息小程序查询服务；小程序管理服务器还可存储和管理富媒体消息小程序包，并为富媒体消息终端提供富媒体消息小程序包的下载服务。富媒体消息终端在第一查询请求消息中携带查询信息，小程序管理服务器根据该查询信息确定满足条件的富媒体消息小程序，并将该富媒体消息小程序的信息返回给富媒体消息终端。这样，使得富媒体消息终端可以发现富媒体消息小程序，进而可以采用富媒体消息小程序完成诸如购票、客户调研之类的功能，简化用户操作，缩短交互过程，提升用户体验。
可以理解，上述图8和图10中各个步骤仅是示例性说明，对此不作严格限定。此外，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
还可以理解，在本申请的各实施例中涉及到一些消息名称，其命名不对本申请实施例的保护范围造成限定。
还可以理解，本申请的各实施例中的一些可选的特征，在某些场景下，可以不依赖于其他特征，也可以在某些场景下，与其他特征进行结合，不作限定。
还可以理解，上述各个方法实施例中，由设备实现的方法和操作，也可以由可由设备的组成部件(例如芯片或者电路)来实现，不作限定。
相应于上述各方法实施例给出的方法，本申请实施例还提供了相应的装置，所述装置包括用于执行上述各个方法实施例相应的模块。该模块可以是软件，也可以是硬件，或者是软件和硬件结合。可以理解的是，上述各方法实施例所描述的技术特征同样适用于以下装置实施例。
图11是本申请实施例提供的一种通信装置1100的示意图。该装置1100包括收发单元1110和处理单元1120。收发单元1110可以用于实现相应的通信功能。收发单元1110还可以称为通信接口或通信单元。处理单元1120可以用于进行处理操作，如生成查询消息、运行富媒体消息小程序等。
可选地，该装置1100还包括存储单元，该存储单元可以用于存储指令和/或数据，处理单元1120可以读取存储单元中的指令和/或数据，以使得装置实现前述各个方法实施例中核心网设备或用户设备的动作。
在第一种设计中，该装置1100可以是前述实施例中的富媒体消息应用服务器(如图6中的富媒体消息应用服务器，图8中的MaaP平台)，也可以是富媒体消息应用服务器的组成部件(如芯片)。该装置1100可实现对应于上文方法实施例中的富媒体消息应用服务器执行的步骤或者流程。其中，收发单元1110可用于执行上文方法实施例中富媒体消息应用服务器的收发相关的操作(如发送和/或接收数据或消息的操作)，例如，收发单元1110可用于执行图6中的步骤610中接收来自富媒体消息终端的第一查询请求消息的操作、步骤630中向富媒体消息终端发送第一查询响应消息的操作，还可以用于执行图8中MaaP平台的发送和/或接收数据或消息的操作。处理单元1120可用于执行上文方法实施例中富媒体消息应用服务器的处理相关的操作，或者除收发之外的操作(如发送和/或接收数据或消息之外的操作)，例如，处理单元1120可用于根据第一查询请求消息获取富媒体消息小程序的信息。再例如，处理单元1120可用于执行图8中的步骤805中的操作。
一种可能的实现方式，收发单元1110，用于接收来自富媒体消息终端的第一查询请 求消息，第一查询请求消息包含查询信息，查询信息包含用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；处理单元1120用于响应于第一查询请求消息，获取富媒体消息小程序的信息；收发单元1110，还用于向富媒体消息终端发送第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息。
可选地，收发单元1110，还用于向小程序管理服务器发送第二查询请求消息，第二查询请求消息包含查询信息；接收来自小程序管理服务器的第二查询响应消息，第二查询响应消息包含富媒体消息小程序的信息。
可选地，处理单元1120，具体用于根据查询信息，从本地获取富媒体消息小程序的信息。
可选地，处理单元1120，还用于确定允许用户使用富媒体消息小程序。
可选地，处理单元1120，具体用于根据用户的签约信息和/或用户所属的运营商的信息，确定允许用户使用富媒体消息小程序。
示例地，查询信息包括以下至少一项或以下至少一项所包含的关键字：富媒体消息小程序的名称、富媒体消息小程序的类型、富媒体消息小程序的提供商的名称、富媒体消息小程序的服务内容描述或功能描述、富媒体消息客户端支持的语言、或富媒体消息客户端的版本。
示例地，富媒体消息小程序的信息包括富媒体消息小程序的下载地址。
示例地，富媒体消息小程序的信息包括以下至少一项：富媒体消息小程序的标识、富媒体消息小程序的名称、富媒体消息小程序的图标的地址、或富媒体消息小程序的版本。
示例地，富媒体消息应用服务器为消息即平台MaaP或聊天机器人Chatbot平台，富媒体消息终端与富媒体消息应用服务器通过聊天机器人目录查询接口通信。
可选地，收发单元1110，具体用于通过聊天机器人目录查询接口接收第一查询请求消息；通过聊天机器人目录查询接口发送第一查询响应消息。
示例地，第一查询请求消息还包含指示信息，指示信息指示富媒体消息应用服务器根据查询信息提供富媒体消息小程序的信息。
在第二种设计中，该装置1100可以是前述实施例中的富媒体消息终端(如图6、图7、图8、图10中的富媒体消息终端)，也可以是富媒体消息终端的组成部件(如芯片)。该装置1100可实现对应于上文方法实施例中的富媒体消息终端执行的步骤或者流程。其中，收发单元1110可用于执行上文方法实施例中富媒体消息终端的收发相关的操作(如发送和/或接收数据或消息的操作)，例如，收发单元1110可用于执行图6中的步骤610中向富媒体消息应用服务器发送第一查询请求消息的操作、步骤630中接收来自富媒体消息应用服务器的第一查询响应消息的操作，还可以用于执行图7中的步骤710中向小程序管理服务器发送第一查询请求消息的操作、步骤730中接收来自小程序管理服务器的第一查询响应消息的操作，还可以用于执行图8中的富媒体消息终端发送和/或接收数据或消息的操作，还可以用于执行图10中的富媒体消息终端发送和/或接收数据或消息的操作。处理单元1120可用于执行上文方法实施例中富媒体消息终端的数据和/或信息处理相关的操作，或者除收发之外的操作(如发送和/或接收数据或消息之外的操作)，例如，处理单元1120可用于执行图6中的步骤640的操作，还可以用于执行图7中的步骤740的操 作，还可以用于执行图8中的步骤810的操作，还可以用于执行图10中的步骤1007的操作。
一种可能的实现方式，收发单元1110，用于向富媒体消息应用服务器发送第一查询请求消息，第一查询请求消息包含查询信息，查询信息用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；收发单元1110，还用于接收来自富媒体消息应用服务器的第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息；处理单元1120，用于根据富媒体消息小程序的信息下载并运行富媒体消息小程序。
示例地，查询信息包括以下至少一项：富媒体消息小程序的名称、富媒体消息小程序的类型、富媒体消息小程序提供商的名称、富媒体消息小程序内容或功能描述的关键词、富媒体消息客户端支持的语言、或富媒体消息客户端的版本。
示例地，富媒体消息小程序的信息包括富媒体消息小程序的下载地址。
示例地，富媒体消息小程序的信息包括以下至少一项：富媒体消息小程序的标识、富媒体消息小程序的名称、富媒体消息小程序的图标的地址、或富媒体消息小程序的版本。
示例地，富媒体消息应用服务器为消息即平台MaaP或聊天机器人Chatbot平台，富媒体消息终端与富媒体消息应用服务器通过聊天机器人目录查询接口通信。
可选地，收发单元1110，具体用于通过聊天机器人目录查询接口发送第一查询请求消息；通过聊天机器人目录查询接口接收第一查询响应消息。
示例地，第一查询请求消息还包含指示信息，指示信息指示富媒体消息应用服务器根据查询信息提供富媒体消息小程序的信息。
另一种可能的实现方式，收发单元1110，用于向小程序管理服务器发送第一查询请求消息，第一查询请求消息包含查询信息，查询信息用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；收发单元1110，还用于接收来自小程序管理服务器的第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息；处理单元1120，用于根据富媒体消息小程序的信息下载并运行富媒体消息小程序。
示例地，查询信息包括以下至少一项或以下至少一项所包含的关键字：富媒体消息小程序的名称、富媒体消息小程序的类型、富媒体消息小程序的提供商的名称、富媒体消息小程序的服务内容描述或功能描述、富媒体消息客户端支持的语言、或富媒体消息客户端的版本。
示例地，富媒体消息小程序的信息包括富媒体消息小程序的下载地址。
示例地，富媒体消息小程序的信息包括以下至少一项：富媒体消息小程序的标识、富媒体消息小程序的名称、富媒体消息小程序的图标的地址、或富媒体消息小程序的版本。
示例地，富媒体消息终端与小程序管理服务器通过小程序目录查询接口通信。
可选地，收发单元1110，具体用于通过小程序目录查询接口发送第一查询请求消息；通过小程序目录查询接口接收第一查询响应消息。
在第三种设计中，该装置1100可以是前述实施例中的小程序管理服务器，也可以是小程序管理服务器的组成部件(如芯片)。该装置1100可实现对应于上文方法实施例中的小程序管理服务器执行的步骤或者流程。其中，收发单元1110可用于执行上文方法实 施例中小程序管理服务器的收发相关的操作(如发送和/或接收数据或消息的操作)，例如，收发单元1110可用于执行图7中的步骤710中接收来自富媒体消息终端的第一查询请求消息的操作、步骤730中向富媒体消息终端发送第一查询响应消息的操作，还可以用于执行图8和图10中小程序管理服务器的发送和/或接收数据或消息的操作。处理单元1120可用于执行上文方法实施例中小程序管理服务器的处理相关的操作，或者除收发之外的操作(如发送和/或接收数据或消息之外的操作)，例如，处理单元1120可用于执行图7中的步骤730的操作，还可以用于执行图8中的步骤807的操作，还可以用于执行图10中的步骤1005的操作。
一种可能的实现方式，收发单元1110，用于接收来自富媒体消息终端的第一查询请求消息，第一查询请求消息包含查询信息，查询信息包含用于描述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，富媒体消息小程序为以富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；处理单元1120，用于根据查询信息获取富媒体消息小程序的信息；收发单元1110，还用于向富媒体消息终端发送第一查询响应消息，第一查询响应消息包含富媒体消息小程序的信息。
可选地，处理单元1120，还用于确定允许用户使用富媒体消息小程序。
可选地，处理单元1120，具体用于根据用户的签约信息和/或用户所属的运营商的信息，确定允许用户使用富媒体消息小程序。
示例地，查询信息包括以下至少一项或以下至少一项所包含的关键字：富媒体消息小程序的名称、富媒体消息小程序的类型、富媒体消息小程序的提供商的名称、富媒体消息小程序的服务内容描述或功能描述、富媒体消息客户端支持的语言、或富媒体消息客户端的版本。
示例地，富媒体消息小程序的信息包括富媒体消息小程序的下载地址。
示例地，富媒体消息小程序的信息包括以下至少一项：富媒体消息小程序的标识、富媒体消息小程序的名称、富媒体消息小程序的图标的地址、或富媒体消息小程序的版本。
示例地，富媒体消息终端与小程序管理服务器通过小程序目录查询接口通信。
可选地，收发单元1110，具体用于通过小程序目录查询接口接收第一查询请求消息；通过小程序目录查询接口发送第一查询响应消息。
可以理解，各单元执行上述相应步骤的具体过程在上述各方法实施例中已经详细说明，为了简洁，在此不再赘述。
还可以理解，这里的装置1100以功能单元的形式体现。这里的术语“单元”可以指应用特有集成电路(application specific integrated circuit，ASIC)、电子电路、用于执行一个或多个软件或固件程序的处理器(例如共享处理器、专有处理器或组处理器等)和存储器、合并逻辑电路和/或其它支持所描述的功能的合适组件。在一个可选例子中，本领域技术人员可以理解，装置1100可以具体为上述实施例中的富媒体消息应用服务器(如图6中的富媒体消息应用服务器，图8中的MaaP平台)，可以用于执行上述各方法实施例中与富媒体消息应用服务器对应的各个流程和/或步骤，例如，图6中的步骤610-630，图8中的步骤803-806、808、809。或者，装置1100可以具体为上述实施例中的富媒体消息终端(如图6、图7、图8、图10中的富媒体消息终端)，可以用于执行上述各方法实施例中与富媒体消息终端对应的各个流程和/或步骤，例如，图6中的步骤610、630-640， 图7中的步骤710、730-740，图8中的步骤801-802、809-810，图10中的步骤1001-1002、1006-1007。或者，装置1100可以具体为上述实施例中的小程序管理服务器，可以用于执行上述各方法实施例中与小程序管理服务器对应的各个流程和/或步骤，例如，图7中的步骤710-730，图8中的步骤806-808，图10中的步骤1002-1006。为避免重复，在此不再赘述。
上述各个方案的装置1100具有实现上述方法中富媒体消息应用服务器(如图6中的富媒体消息应用服务器，图8中的MaaP平台)所执行的相应步骤的功能，或者，上述各个方案的装置1100具有实现上述方法中富媒体消息终端(如图6、图7、图8、图10中的富媒体消息终端)所执行的相应步骤的功能，或者，上述各个方案的装置1100具有实现上述方法中小程序管理服务器所执行的相应步骤的功能。所述功能可以通过硬件实现，也可以通过硬件执行相应的软件实现。所述硬件或软件包括一个或多个与上述功能相对应的模块；例如收发单元可以由收发机替代(例如，收发单元中的发送单元可以由发送机替代，收发单元中的接收单元可以由接收机替代)，其它单元，如处理单元等可以由处理器替代，分别执行各个方法实施例中的收发操作以及相关的处理操作。
此外，上述收发单元1110还可以是收发电路(例如可以包括接收电路和发送电路)，处理单元可以是处理电路。
需要指出的是，图11中的装置可以是前述实施例中的设备，也可以是芯片或者芯片系统，例如：片上系统(system on chip，SoC)。其中，收发单元可以是输入输出电路、通信接口；处理单元为该芯片上集成的处理器或者微处理器或者集成电路。在此不做限定。
图12是本申请实施例提供另一种通信装置1200的示意图。该装置1200包括处理器1210，处理器1210用于执行存储器1220存储的计算机程序或指令，或读取存储器1220存储的数据，以执行上文各方法实施例中的方法。可选地，处理器1210为一个或多个。
可选地，如图12所示，该装置1200还包括存储器1220，存储器1220用于存储计算机程序或指令和/或数据。该存储器1220可以与处理器1210集成在一起，或者也可以分离设置。可选地，存储器1220为一个或多个。
可选地，如图12所示，该装置1200还包括收发器1230，收发器1230用于信号的接收和/或发送。例如，处理器1210用于控制收发器1230进行信号的接收和/或发送。
作为一种方案，该装置1200用于实现上文各个方法实施例中由富媒体消息应用服务器(如图6中的富媒体消息应用服务器，图8中的MaaP平台)执行的操作。
作为另一种方案，该装置1200用于实现上文各个方法实施例中由富媒体消息终端(如图6、图7、图8、图10中的富媒体消息终端)执行的操作。
作为另一种方案，该装置1200用于实现上文各个方法实施例中由小程序管理服务器执行的操作。
可以理解，本申请实施例中提及的处理器可以是中央处理单元(central processing unit，CPU)，还可以是其他通用处理器、数字信号处理器(digital signal processor，DSP)、专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
还可以理解，本申请实施例中提及的存储器可以是易失性存储器和/或非易失性存储器。其中，非易失性存储器可以是只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，RAM)。例如，RAM可以用作外部高速缓存。作为示例而非限定，RAM包括如下多种形式：静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，DR RAM)。
需要说明的是，当处理器为通用处理器、DSP、ASIC、FPGA或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件时，存储器(存储模块)可以集成在处理器中。
还需要说明的是，本文描述的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由富媒体消息应用服务器(如图6中的富媒体消息应用服务器，图8中的MaaP平台)执行的方法的计算机指令。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由富媒体消息终端(如图6、图7、图8、图10中的富媒体消息终端)执行的方法的计算机指令。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述各方法实施例中由小程序管理服务器执行的方法的计算机指令。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由富媒体消息应用服务器(如图6中的富媒体消息应用服务器，图8中的MaaP平台)执行的方法。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由富媒体消息终端(如图6、图7、图8、图10中的富媒体消息终端)执行的方法。
本申请实施例还提供一种计算机程序产品，包含指令，该指令被计算机执行时以实现上述各方法实施例中由小程序管理服务器执行的方法。
本申请实施例还提供一种通信系统，包括前述的富媒体消息应用服务器(如图6中的富媒体消息应用服务器，图8中的MaaP平台)、富媒体消息终端(如图6、图7、图8和图10中的富媒体消息终端)、小程序管理服务器中的至少一项。
上述提供的任一种装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅是示意性的，例如，所述单元的划分，仅 仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。此外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。例如，所述计算机可以是个人计算机，服务器，或者网络设备等。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD)等。例如，前述的可用介质包括但不限于：U盘、移动硬盘、只读存储器(read-only memory，ROM)、随机存取存储器(random access memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (35)

  1. 一种通信方法，其特征在于，包括：
    富媒体消息应用服务器接收来自富媒体消息终端的第一查询请求消息，所述第一查询请求消息包含查询信息，所述查询信息包含用于描述所述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，所述富媒体消息小程序为以所述富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；
    响应于所述第一查询请求消息，所述富媒体消息应用服务器获取所述富媒体消息小程序的信息，以及向所述富媒体消息终端发送第一查询响应消息，所述第一查询响应消息包含所述富媒体消息小程序的信息。
  2. 根据权利要求1所述的方法，其特征在于，所述富媒体消息应用服务器获取所述富媒体消息小程序的信息，包括：
    所述富媒体消息应用服务器向小程序管理服务器发送第二查询请求消息，所述第二查询请求消息包含所述查询信息；
    所述富媒体消息应用服务器接收来自所述小程序管理服务器的第二查询响应消息，所述第二查询响应消息包含所述富媒体消息小程序的信息。
  3. 根据权利要求1所述的方法，其特征在于，所述富媒体消息应用服务器获取所述富媒体消息小程序的信息，包括：
    所述富媒体消息应用服务器根据所述查询信息，从本地获取所述富媒体消息小程序的信息。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，在所述富媒体消息应用服务器获取所述富媒体消息小程序的信息之前，所述方法还包括：
    所述富媒体消息应用服务器确定允许所述用户使用所述富媒体消息小程序。
  5. 根据权利要求4所述的方法，其特征在于，所述富媒体消息应用服务器确定允许所述用户使用所述富媒体消息小程序，包括：
    所述富媒体消息应用服务器根据所述用户的签约信息和/或所述用户所属的运营商的信息，确定允许所述用户使用所述富媒体消息小程序。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述查询信息包括以下至少一项或以下至少一项所包含的关键字：所述富媒体消息小程序的名称、所述富媒体消息小程序的类型、所述富媒体消息小程序的提供商的名称、所述富媒体消息小程序的服务内容描述或功能描述、所述富媒体消息客户端支持的语言、或所述富媒体消息客户端的版本。
  7. 根据权利要求1至6中任一项所述的方法，其特征在于，所述富媒体消息小程序的信息包括所述富媒体消息小程序的下载地址。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述富媒体消息小程序的信息包括以下至少一项：所述富媒体消息小程序的标识、所述富媒体消息小程序的名称、所述富媒体消息小程序的图标的下载地址、或所述富媒体消息小程序的版本。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述富媒体消息应用服 务器为消息即平台MaaP或聊天机器人Chatbot平台，所述富媒体消息终端与所述富媒体消息应用服务器通过聊天机器人目录查询接口通信。
  10. 根据权利要求9所述的方法，其特征在于：
    所述富媒体消息应用服务器接收来自富媒体消息终端的第一查询请求消息，包括：所述富媒体消息应用服务器通过所述聊天机器人目录查询接口接收所述第一查询请求消息；
    所述富媒体消息应用服务器向所述富媒体消息终端发送第一查询响应消息，包括：所述富媒体消息应用服务器通过所述聊天机器人目录查询接口发送所述第一查询响应消息。
  11. 根据权利要求9或10所述的方法，其特征在于，所述第一查询请求消息还包含指示信息，所述指示信息指示所述富媒体消息应用服务器根据所述查询信息提供所述富媒体消息小程序的信息。
  12. 一种通信方法，其特征在于，包括：
    富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息，所述第一查询请求消息包含查询信息，所述查询信息用于描述所述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，所述富媒体消息小程序为以所述富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；
    所述富媒体消息终端接收来自所述富媒体消息应用服务器的第一查询响应消息，所述第一查询响应消息包含所述富媒体消息小程序的信息；
    所述富媒体消息终端根据所述富媒体消息小程序的信息下载并运行所述富媒体消息小程序。
  13. 根据权利要求12所述的方法，其特征在于，所述查询信息包括以下至少一项或以下至少一项所包含的关键字：所述富媒体消息小程序的名称、所述富媒体消息小程序的类型、所述富媒体消息小程序的提供商的名称、所述富媒体消息小程序的服务内容描述或功能描述、所述富媒体消息客户端支持的语言、或所述富媒体消息客户端的版本。
  14. 根据权利要求12或13所述的方法，其特征在于，所述富媒体消息小程序的信息包括所述富媒体消息小程序的下载地址。
  15. 根据权利要求12至14中任一项所述的方法，其特征在于，所述富媒体消息小程序的信息包括以下至少一项：所述富媒体消息小程序的标识、所述富媒体消息小程序的名称、所述富媒体消息小程序的图标的地址、或所述富媒体消息小程序的版本。
  16. 根据权利要求12至15中任一项所述的方法，其特征在于，所述富媒体消息应用服务器为消息即平台MaaP或聊天机器人Chatbot平台，所述富媒体消息终端与所述富媒体消息应用服务器通过聊天机器人目录查询接口通信。
  17. 根据权利要求16所述的方法，其特征在于，
    所述富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息，包括：
    所述富媒体消息终端通过所述聊天机器人目录查询接口发送所述第一查询请求消息；
    所述富媒体消息终端接收来自所述富媒体消息应用服务器的第一查询响应消息，包括：
    所述富媒体消息终端通过所述聊天机器人目录查询接口接收所述第一查询响应消息。
  18. 根据权利要求16或17所述的方法，其特征在于，所述第一查询请求消息还包含指示信息，所述指示信息指示所述富媒体消息应用服务器根据所述查询信息提供所述富媒 体消息小程序的信息。
  19. 一种通信方法，其特征在于，包括：
    富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息，所述第一查询请求消息包含查询信息，所述查询信息用于描述所述富媒体消息终端对应的用户所需要的富媒体消息小程序的信息，所述富媒体消息小程序为以所述富媒体消息终端中的富媒体消息客户端为宿主客户端的小程序；
    所述富媒体消息应用服务器接收所述第一查询请求消息，并响应于所述第一查询请求消息，获取所述富媒体消息小程序的信息，以及向所述富媒体消息终端发送第一查询响应消息，所述第一查询响应消息包含所述富媒体消息小程序的信息；
    所述富媒体消息终端接收所述第一查询响应消息，并根据所述富媒体消息小程序的信息下载并运行所述富媒体消息小程序。
  20. 根据权利要求19所述的方法，其特征在于，所述富媒体消息应用服务器获取所述富媒体消息小程序的信息，包括：
    所述富媒体消息应用服务器向小程序管理服务器发送第二查询请求消息，所述第二查询请求消息包含所述查询信息；
    所述小程序管理服务器向所述富媒体消息应用服务器发送第二查询响应消息，所述第二查询响应消息包含所述富媒体消息小程序的信息；
    所述富媒体消息应用服务器接收所述第二查询响应消息。
  21. 根据权利要求19所述的方法，其特征在于，所述富媒体消息应用服务器获取所述富媒体消息小程序的信息，包括：
    所述富媒体消息应用服务器根据所述查询信息，从本地获取所述富媒体消息小程序的信息。
  22. 根据权利要求19至21中任一项所述的方法，其特征在于，在所述富媒体消息应用服务器获取所述富媒体消息小程序的信息之前，所述方法还包括：
    所述富媒体消息应用服务器确定允许所述用户使用所述富媒体消息小程序。
  23. 根据权利要求22所述的方法，其特征在于，所述富媒体消息应用服务器确定允许所述用户使用所述富媒体消息小程序，包括：
    所述富媒体消息应用服务器根据所述用户的签约信息和/或所述用户所属的运营商的信息，确定允许所述用户使用所述富媒体消息小程序。
  24. 根据权利要求19至23中任一项所述的方法，其特征在于，所述查询信息包括以下至少一项或以下至少一项所包含的关键字：所述富媒体消息小程序的名称、所述富媒体消息小程序的类型、所述富媒体消息小程序的提供商的名称、所述富媒体消息小程序的服务内容描述或功能描述、所述富媒体消息客户端支持的语言、或所述富媒体消息客户端的版本。
  25. 根据权利要求19至24中任一项所述的方法，其特征在于，所述富媒体消息小程序的信息包括所述富媒体消息小程序的下载地址。
  26. 根据权利要求19至25中任一项所述的方法，其特征在于，所述富媒体消息小程序的信息包括以下至少一项：所述富媒体消息小程序的标识、所述富媒体消息小程序的名称、所述富媒体消息小程序的图标的下载地址、或所述富媒体消息小程序的版本。
  27. 根据权利要求19至26中任一项所述的方法，其特征在于，所述富媒体消息应用服务器为消息即平台MaaP或聊天机器人Chatbot平台，所述富媒体消息终端与所述富媒体消息应用服务器通过聊天机器人目录查询接口通信。
  28. 根据权利要求27所述的方法，其特征在于，
    所述富媒体消息终端向富媒体消息应用服务器发送第一查询请求消息，所述富媒体消息应用服务器接收所述第一查询请求消息，包括：
    所述富媒体消息终端通过所述聊天机器人目录查询接口发送所述第一查询请求消息，所述富媒体消息应用服务器通过所述聊天机器人目录查询接口接收所述第一查询请求消息；
    所述富媒体消息应用服务器向所述富媒体消息终端发送第一查询响应消息，所述富媒体消息终端接收所述第一查询响应消息，包括：
    所述富媒体消息应用服务器通过所述聊天机器人目录查询接口发送所述第一查询响应消息，所述富媒体消息终端通过所述聊天机器人目录查询接口接收所述第一查询响应消息。
  29. 根据权利要求27或28所述的方法，其特征在于，所述第一查询请求消息还包含指示信息，所述指示信息指示所述富媒体消息应用服务器根据所述查询信息提供所述富媒体消息小程序的信息。
  30. 一种通信装置，其特征在于，包括执行如权利要求1至29中任一项所述方法的单元或模块。
  31. 一种通信装置，其特征在于，包括至少一个处理器，
    所述至少一个处理器用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求1至11中任一项所述的方法；或者，
    所述至少一个处理器用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求12至18中任一项所述的方法；或者，
    所述至少一个处理器用于执行存储器中存储的计算机程序，以使得所述装置执行如权利要求19至29中任一项所述的方法。
  32. 一种通信系统，其特征在于，包括富媒体消息应用服务器和富媒体消息终端，
    其中，所述富媒体消息应用服务器用于执行如权利要求1至11中任一项所述的方法，所述富媒体消息终端用于执行如权利要求12至18中任一项所述的方法。
  33. 根据权利要求32所述的通信系统，其特征在于，所述系统还包括小程序管理服务器，所述小程序管理服务器用于与所述富媒体消息应用服务器通信。
  34. 一种计算机可读存储介质，其特征在于，包括计算机程序，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求1至11中任一项所述的方法；或者，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求12至18中任一项所述的方法；或者，
    当所述计算机程序在计算机上运行时，使得所述计算机执行如权利要求19至29中任一项所述的方法。
  35. 一种计算机程序产品，其特征在于，所述计算机程序产品中包括计算机程序代码， 其特征在于：
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求1至11中任一项所述的方法；或者，
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求12至18中任一项所述的方法；或者，
    当所述计算机程序代码在计算机上运行时，使得计算机实现上述权利要求19至29中任一项所述的方法。
PCT/CN2022/133390 2022-05-26 2022-11-22 通信方法、装置以及系统 WO2023226338A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210579914.2A CN117176698A (zh) 2022-05-26 2022-05-26 通信方法、装置以及系统
CN202210579914.2 2022-05-26

Publications (1)

Publication Number Publication Date
WO2023226338A1 true WO2023226338A1 (zh) 2023-11-30

Family

ID=88918312

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/133390 WO2023226338A1 (zh) 2022-05-26 2022-11-22 通信方法、装置以及系统

Country Status (2)

Country Link
CN (1) CN117176698A (zh)
WO (1) WO2023226338A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040006592A1 (en) * 1999-05-27 2004-01-08 International Business Machines Corporation System and method for tracking user interactions and navigation during rich media presentations
CN111478956A (zh) * 2020-04-01 2020-07-31 百度在线网络技术（北京）有限公司 小程序包的部署、预览方法和装置
CN111767069A (zh) * 2020-06-30 2020-10-13 北京百度网讯科技有限公司 小程序处理方法、服务器、设备及存储介质
CN112311818A (zh) * 2019-07-25 2021-02-02 腾讯科技（深圳）有限公司 一种小程序数据包的下载方法、装置、终端及存储介质
CN113179415A (zh) * 2021-04-20 2021-07-27 北京异乡旅行网络科技有限公司 基于腾讯im的h5网站直播方法、装置及存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040006592A1 (en) * 1999-05-27 2004-01-08 International Business Machines Corporation System and method for tracking user interactions and navigation during rich media presentations
CN112311818A (zh) * 2019-07-25 2021-02-02 腾讯科技（深圳）有限公司 一种小程序数据包的下载方法、装置、终端及存储介质
CN111478956A (zh) * 2020-04-01 2020-07-31 百度在线网络技术（北京）有限公司 小程序包的部署、预览方法和装置
CN111767069A (zh) * 2020-06-30 2020-10-13 北京百度网讯科技有限公司 小程序处理方法、服务器、设备及存储介质
CN113179415A (zh) * 2021-04-20 2021-07-27 北京异乡旅行网络科技有限公司 基于腾讯im的h5网站直播方法、装置及存储介质

Also Published As

Publication number Publication date
CN117176698A (zh) 2023-12-05

Similar Documents

Publication Publication Date Title
US11991255B2 (en) Interworking service for the restful internet of things
US11444986B2 (en) Device triggering
EP3259898B1 (en) Message bus service directory
US11871333B2 (en) Wireless network service type
US10673680B2 (en) Electronic device providing dialog contents, server and method thereof
CN110178354A (zh) 消息会话中继协议／超文本传输协议文件传输
JP2019531652A (ja) 代理セルラレスローミング
US8861503B2 (en) Method and system for synchronizing data between mobile terminal and internet phone
EP3482296A1 (en) Message retargeting in machine-to-machine service layer communications
WO2023143574A1 (zh) 设备选择的方法以及装置
US9860736B1 (en) Providing network resource access based on a purpose identifier
WO2023226338A1 (zh) 通信方法、装置以及系统
WO2023241198A1 (zh) 通信方法、装置以及系统
WO2023143560A1 (zh) 设备选择的方法以及装置
WO2023241093A1 (zh) 一种富媒体消息交互的方法、客户端、云设备及通信系统
WO2023141973A1 (en) Negotiation mechanism for authentication procedures in edge computing
WO2024065503A1 (en) Negotiation of authentication procedures in edge computing
CN117812140A (zh) 用于获取终端信息的方法和装置

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: 22943525

Country of ref document: EP

Kind code of ref document: A1